[SOLVED] AMD APU processors and Linux distributions
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
chip-specific drivers are in process of being phased out
Another option is the generic modesetting driver built into the server since version 1.17.x. It's where the focus of Xorg driver for Intel gfx development has shifted. Easiest way I know to configure that the modesetting driver be used in *buntu is to purge whichever of xserver-xorg-video-radeon, xserver-xorg-video-amdgpu and/or xserver-xorg-video-ati are installed. If the modesetting driver turns out not to help, it's easy enough to boot in rescue mode and reinstall the other(s).
I know this is pretty old, but as far as I can tell, this problem still affects multiple people out there, and no one has found a solution.
As a summary: During boot, the X server crashes, and the computer either shuts down or reboots only to crash again at the same point. This affects only AMD dual GPU setups with a dGPU and iGPU (a very common set up). Boot may be rescued by invoking the nomodeset boot parameter. This disables all GPU(s) functions, and replaces them with software emulation. While this is sufficient to get into the system for recovery and troubleshooting, it is not an acceptable working solution.
No one seems to have mentioned this yet, but a partial workaround is to set radeon.dpm=0 parameter instead of nomodeset. This disables graphics card switching, which means it disables the dGPU. This boots normally, and you get the function of your iGPU. This is an acceptable working solution for very light use (browsing, playing videos < 4k resolution, music). It is however, not acceptable as a final solution. In mose cases iGPUs are very weak, and even things like resizing application windows will cause lag. Enabling the dGPU after boot immediately crashes the X server.
This problem has been around for 6 months now, and occurred around (maybe caused by) the deprecation of UMS (Userspace Mode Setting). There has been zero progress on it. I would appreciate any advice.
P.S. my setup works perfectly on all version of Windows, and used to work on *buntu up to 15.10 perfectly, until the release of 16.04 which caused this problem even in earlier versions of *buntu (among a whole host of other issues).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.