I just switched over to the LTS Kernel for Arch Linux in order to install the AMD Catalyst Drivers. Now after I installed the Kernel when I tried to boot the System it froze at "[OK] Reached Target Graphical Interface". This happens with either Kernel when I try to boot it and I can still switch to a Terminal login and logging in through that work fine but GDM won't start. I've seen a lot of other people with the same issue but for different reasons like the nvidia nouveau drivers for example
I had that same issue after something for catalyst was updated and it wouldn't work with the lts kernel anymore. I had to go back to the standard kernel. Boot into your computer with the install usb/disc and arch-chroot into your environment and see if the standard kernel works.
Switch to the terminal login, disable GDM, reboot and login again then 'startx' - if X fails to start it'll print the errors - easier to troubleshoot
@Baz thats maybe unnecasary.
Logs will be in /var/log/Xorg.0.log or journalctl
For the xorg log do cat /var/log/Xorg.0.log | grep -i ee
That will print any errors.
This is happening because your trying to use the catalyst drivers, there crap. What do you need them for?
I haven't installed the Catalyst drivers yet and I need them so I can actually do some gaming on Linux. I know the Fury X isn't where it should be on Linux and the drivers are awful but right now I think I'm using the Mesa Drivers and with those Gnome doesn't even have animations and they're are generally crap
Ah well if you have a fury x and installed the lts kernel its not supported as theres no open drivers for that kernel release that supports it. You need to install the catalyst drivers with the lts kernel, or the xf86-video-amdgpu (which arent in arch) drivers with the latest kernel. fyi, you can play games on the open drivers.
the logs i mentioned above will tell you what the exact error is.
its a bug with gdm and catalyst, use another display manager or use the oss drivers.
Well if it's bug with gdm and catalyst then why do I get this issue without having the catalyst drivers installed yet is what I'm wondering
hmm maybe try a different dm to figure out if the issue has anything to do with gdm.
EDIT: do a journalctl -xe -u gdm.service and post the output.
Ok I'll try that. What other dm would you recommend?
ldm
EDIT: but honestly if you use gnome you shoudl probably stick to gdm and just use ldm to debug the issue.
Ok thanks
Thank you so much ldm fixed the issue and now I might actually switch DEs because of the gdm issues. Maybe I'll go for kde plasma
if its the same issue that i had wit gdm and catalyst there is a patch in the aur that fixes it.
EDIT: its not actually gdms fault that this is happening, its the amd driver thats the problem. Though I didnt think it would happen with the oss driver. And as others have mentioned, the lts kernel wont work with the furyX.
I would prefer to use the oss drivers but I saw that it's really slow with GCN 1.2 cards so I'll have to use catalyst for now. I think I may just install the drivers and switch to KDE because I wanted to give that one a try anyways
EDIT: Do you mean it won't work with the lts kernel at all or just not with the integrated driver?
Im not really sure to be honest. There are actually 3 amd drivers for linux. One is the normal oss one. The second one is the normal proprietary one directly from amd which does not work for everything above 3.19 I believe.
Then we have the new amdgpu, an oss driver directly from amd which is in the kernel itself (thats why u need a newer kernel). This driver has different userspace implementations, a proprietary one from amd (which i think is just catalyst) and one oss one. Im not quite sure if catalyst uses amdgpu or the old catalyst driver in your case, although since u are on a newer kernel it should use amdgpu. Im not even sure if catalyst (the driver, not the userspace stuff) even supports GCN 1.2. Lets just assume that its doenst. In that case the lts kernel wont work at all.
The current amd driver situation is a pretty big mess and we can only hope amd is gonna step up, add more cards to amdgpu and improve the performance to at least the level we got on windows right now.
Well if I got that right in the Catalyst wiki the driver provided seems to be catalyst 15.9 which works with the Fury X so I'm gonna try to install that and if that doesn't work I'll try the oss driver. Also on Ubuntu Gnome 15.04 (and 15.10 with the old kernel) so I'm assuming it will work with the lts kernel because of the community patches. Also do you know how to downgrade xorg by any chance? Because when I add the 116 repository and update it doesn't want to install xorg 116
EDIT: I ended up downgrading by simply running sudo pacman -Suu and it worked
Ok I managed to install the Catalyst drivers but I've got 2 catalyst control centers and neither one of them will open
Open up terminal and type amdcccle, does it load it then? If so then it just means your shortcuts are buggered. Also be sure you have done a sudo amdconfig --initial -f (I think thats it) so your desktop config file is ready.
When I run amcccle I get the following error:
"amdcccle: error while loading shared libraries: libQtGui.so.4: cannot open shared object file: No such file or directory"
And yes I did run sudo aticonfig --initial -f