[drm:radeon_init[radeon]] ERROR No UMS support in radeon module!: booting issue [solved]

This post is in continuation with my previous blog post about “A connection to the bus can’t be made: booting issue”. So, as soon as I got rid of my prior booting error I got another one. But this time it was more specific (related to Radeon device) and easy to find out the solution over the web. Here is what worked for me.

1. Machine Specs

https://www.sony.com.sg/electronics/support/laptop-pc-vpc-series/vpcea45fg/specifications

2. Problem

* Type: Booting time issue
* Effect: Slow booting
* Error Message:

[drm:radeon_init[radeon]] ERROR No UMS support in radeon module! [Solved]

* Brief Explanation: After updating my <GNU/Linux>. I am getting this error while booting. Making the booting slow.

3. Cause

After going through this, I found out that the reason is with graphic drivers. I didn’t follow the solution listed there but did something more straightforward.

4. Solution

Install/update/upgrade graphic drivers. That’s it! I followed the instruction of Joshua Besneatte in this answer https://askubuntu.com/questions/1066105/how-to-install-amd-graphic-drivers-on-ubuntu-18-04 which are as follows:

sudo apt update
sudo apt upgrade
sudo apt autoremove
sudo apt autoclean

Now, add the AMD updates PPA and update:

sudo add-apt-repository ppa:oibaf/graphics-drivers
sudo apt-get update
sudo apt upgrade

Then reconfigure your packages to be safe:

sudo apt install --reinstall xserver-xorg-video-amdgpu
sudo dpkg --configure -a
sudo dpkg-reconfigure gdm3 ubuntu-session xserver-xorg-video-amdgpu

Now simply reboot. It worked for me. 🙂

Next: Failed to connect to lvmetad: booting issue

5. Conclusion

I believe that getting the updated graphic drivers is the permanent solution to the error discussed in my previous post. Because somewhere I knew from the start that the problem is associated with GPU drivers. Because I was able to boot perfectly with Linux Mint in compatible mode (that is without GPU acceleration).

I gone through 2 booting issues one after another. Still, I don’t know why these errors were attacking me back to back, one by one, just message kept on changing. Because still, I was not getting clear and fast booting. Quiet hilariously, after resolving this issue, again I was dealing with another one, and this time the message was:

failed to connect to lvmetad

Solution in the next post.

I hope this post will help someone and may they not get into the next error in queue like me. But if you know any other solution regarding the same issue, please do write in the comments section below, that would be helpful for someone else.

Thanks for reading! 🙂

• All
• Booting
• Linux