LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   [SOLVED] Switched to radeon but ksmserver still looking for libnvidia-tls.so (https://www.linuxquestions.org/questions/slackware-14/%5Bsolved%5D-switched-to-radeon-but-ksmserver-still-looking-for-libnvidia-tls-so-4175648095/)

roberto967 02-11-2019 03:35 PM
[SOLVED] Switched to radeon but ksmserver still looking for libnvidia-tls.so
 
I uninstalled my old nvidia because it was useless with the latest kernel (I also phisically removed the hardware) and I switched to the radeon vga shipped with the motherboard.

I'm able to run X and kdm, I can get the kde's login form, but once I enter my password it fails to load my desktop and the kde login is presented again, regardless of the user I try to login with. The same happens if I try with a newly created user, and also removing my .kde folder.

My .xsession-errors shows ksmserver complaining because of the missing libnvidia-tls.so.340.104 and I can't figure out why it's still looking for the nvidia library....

Thanks in advance for any hint

volkerdi 02-11-2019 04:01 PM
Try reinstalling the mesa package.

NathanBarley 02-11-2019 05:59 PM
I had a problem like this with xfce4-session when I switched to an AMD GPU, I'm sorry to say I can't quite remember how I fixed it, but it might have been something to do with rebuilding ldcache.

I can't think of any other reason something would want that a redundant library if it wasn't built against it.

roberto967 02-12-2019 07:00 AM
Quote:
Originally Posted by volkerdi (Post 5960759)
Try reinstalling the mesa package.
thanks, Pat. Unfortunately reinstalling mesa didn't help.

roberto967 02-12-2019 07:16 AM
Quote:
Originally Posted by NathanBarley (Post 5960787)
I had a problem like this with xfce4-session when I switched to an AMD GPU, I'm sorry to say I can't quite remember how I fixed it, but it might have been something to do with rebuilding ldcache.

I can't think of any other reason something would want that a redundant library if it wasn't built against it.
do no worry, this exact same thing already happened to me once, and I don't even remember how I fixed it. :)

Anyway rebuilding ld cache didn't help

NathanBarley 02-12-2019 07:53 AM
On thing that may help is the information in the README with the Nvidia blob Slackbuild - it has some good information on the changes the Nvidia makes vs. Xorg/Mesa:

Quote:
Before uninstalling or upgrading this package, it is important that
you execute 'nvidia-switch --remove', which will switch back to the
stock xorg files and remove all links created by nvidia-switch during
installation. If you forget to do this, you might have to do the switch
manually, since 'nvidia-switch --install' may fail, resulting in xorg
not working. Here are the affected files:

/usr/lib[64]/libGL.so.1.2
/usr/lib[64]/libGL.la
/usr/lib[64]/libGLESv1_CM.so.1.0.0
/usr/lib[64]/libGLESv2.so.2.0.0
/usr/lib[64]/libEGL.so.1.0.0
/usr/lib[64]/xorg/modules/libwfb.so
/usr/lib[64]/xorg/modules/extensions/libglx.so

Simply remove the dead nvidia symlinks and and reinstall the mesa and
xorg-server packages. See 'nvidia-switch --help'.
I have a feeling there are others, though.

This is one of the reasons I switched to AMD in the first place. Hope you get it all sorted.

Petri Kaukasoina 02-12-2019 08:20 AM
In addition to mesa, reinstall the xorg-server package.

igadoter 02-12-2019 08:47 AM
Just install your nvidia card and run nvidia-switch as above suggested. There is with nvidia proprietary driver option to uninstall driver. Personally I would do : 1) add nvidia engine 2) re-install driver 3) uninstall driver 4) remove nvidia engine. Instead of trying to fix manually.

NathanBarley 02-12-2019 11:07 AM
Quote:
Originally Posted by igadoter (Post 5961009)
Just install your nvidia card and run nvidia-switch as above suggested. There is with nvidia proprietary driver option to uninstall driver. Personally I would do : 1) add nvidia engine 2) re-install driver 3) uninstall driver 4) remove nvidia engine. Instead of trying to fix manually.
Even this can cause some challenges. I used the Nvidia .run installer a couple of years back when I had a GPU that was not supported by the then available Slackbuild.

Although the --uninstall switch works there were lots of little problems with various libGL libraries that were frustrating to troubleshoot. The GLVND component is particularly infuriating to understand. You might think you're returning your system to the previous state, but in my case this definitely did not happen.

In the end I used the big hammer option and just reinstalled 14.2. It was quicker than trying to figure out what was going on.

roberto967 02-12-2019 11:11 AM
There was indeed a lot of garbage in /usr/lib64/libG* despite the fact that I reinstalled mesa and xorg

I restored a couple of symbolic links that were left by nvidia:

Code:
libGEL.so.1.0.0 -> libEGL.so.340.104
libGL.so.1 -> libGL.so.340.104
It was sufficient to link them again as follows

Code:
rm libEGL.so.340.104 libGL.so.340.104
rm libGEL.so.1.0.0
ln -s libEGL.so.1.0.0 libGEL.so.1.0.0
rm libGL.so.1
ln -s libGL.so.1.2.0 libGL.so.1
Thanks everyone for helping me to solve this issue.


All times are GMT -5. The time now is 12:35 PM.