Hi,
So yesterday I got the updater applet telling me I have over 2000 updates. I clicked ok and after a few hours I returned home and I couldn’t log in anymore. I was getting 3 boxes with question marks instead of the KDE loading animation.
After hours of pain, installing\reinstalling\uninstalling a combination of fglrx, kernels, recovery mode, etc I got it working somehow but I still have problems like:
If my pc goes into stand by, when resuming I can’t enter my password in the password prompt! I have a mouse cursor but I can’t type any character and I can’t click the users icons. I have to CTRL+ALT+F1 and press CTRL+SHIFT+F7 to restart the GUI.
Sometimes my graphical interface crashes, I get a login page, enter my password then I’m thrown into a console login prompt. I have to restart the graphical interface with the key combination.
This 42.2 update broke my system :|.
Can you guys help me out figuring out how to fix it?
Here are my specs:
AMD A10 7700K with integrated R7 GPU
10GB RAM
120GB SSD main storage
160GB HDD second storage
x64
uname -a
Linux linux-jspa.site 4.4.27-2-default #1 SMP Thu Nov 3 14:59:54 UTC 2016 (5c21e7c) x86_64 x86_64 x86_64 GNU/Linux
KDE Plasma 5.8.2
KDE Framewoorks 5.26.0
Kernel 4.4.27.2-default
Yes:(.
I remember something about adding odd respositories when I tried making Chrome Remote Desktop working on openSUSE. I think I somehow screwed up the repositories.
yes and no, you need to run zypper dup --with (the oss repo), then with packman then run zypper up
but you better post your repo list eith the -d switch
in principle you should do zypper dup --from 2 but there have been quite a few updates and rolling back a kernel might not be the best idea
after the above has finished reboot, then add the ati repo and install the ati drivers (I’m an nvidia user I have no idea about ati) and add packman doing a vendor change with it, or ask here when you’re done
Ok, did that and then I rebooted.
I got straight to a console prompt and while typing my username the KDE logo splash showed up and logged me in, strange, there is no splash screen or it is missing maybe?
I now added the packman repo. Should I go in Software Management, Packman and use the Switch system packages to versions from this repository (Packman)?
Regarding AMD drivers, I read FGLRX is not supported in 42.2 and I shouldn’t use it. I’ll have to do more reading on wich driver should I use for my AMD APU GPU.
Yes do the switch to packman it is needed for all proprietary file formats
the AMD drivers are a bit confusing at the moment the AMDGPU-PRO driver seems to still be in development. They have also dropped support for some older chips I guess
[/quote]I’ll have to do more reading on wich driver should I use for my AMD APU GPU.[/QUOTE]
What output do you have for:
/sbin/lspci -nnk| egrep 'VGA|3D|Display' -A3
You should be fine with the oss radeon stack.
Depending upon the actual underlining graphics adapter, you may be able to use the amdgpu driver (either the oss amdgpu or the hybrid amdgpu-pro)
I’ll have to do more reading on wich driver should I use for my AMD APU GPU.[/QUOTE]
What output do you have for:
/sbin/lspci -nnk| egrep 'VGA|3D|Display' -A3
You should be fine with the oss radeon stack.
Depending upon the actual underlining graphics adapter, you may be able to use the amdgpu driver (either the oss amdgpu or the hybrid amdgpu-pro)[/QUOTE]
There should be more lines of text produced by the grep option switch … specifically, it would have listed what kernel drivers are (currently) available to use, as well as indicating which one is being used. If there is no other output for the adapter, it would likely have ended up displaying a couple more line for the next pci device listed by lspci.
If there were no other lines, neither radeon nor amdgpu kernel driver is currently loaded, and you would be using the generic (and very basic) fbdev driver. What do you see in your xorg log? paste its contents to susepast and provide a link.
On the good news front, your Sea Islands (“CIK”) based adapter is supported by the amdgpu. So you’ll be able to use either the oss or pro version. Though, for Leap, the default kernel is likely too old to yet include support in the oss amdgpu for your particular device (and the same applies to the rest of the driver stack components that are necessary (i.e. all the user space drivers and etc)). Next release, however, you’ll be good right out of the box, so to speak with the oss amdgpu driver. In the meantime, you can try to get the pro driver to work. And, at the very least, you want to get the radeon driver stack going if what I wrote above about the kernel driver not being loaded is happening.
You should be good with radeon right now … As mentioned, the amdgpu stack is an option. But right now, getting it will take jumping through some hoops … in future that won’t be the case.
Ok what I noticed is that the performance is extremely bad now, and I mean just browsing this forum on Chromium with 1 tab open and a 120% zoom causes stuttering when scrolling up and down. Also even moving desktop icons while clicking and dragging them is very choppy! The KDE menu doesn’t open smoothly also. The overall performance of KDE is very bad comparing to 42.1. I have the Huyango type wallpaper on my displays and even the animation when the wallpaper changes is not smooth, what the hell?
