Badly installed nvidia-driver (Problem with symlinks)
Hello,
I'm new to Slackware Linux. I installed Slackware64 14.2 yesterday on my PC. I usually don't write on forums, so I hope it's the correct place to post this question. I have an nvidia graphics card and so I installed the proprietary drivers from Slackbuilds.org (nvidia-driver and nvidia-kernel). But after rebooting, my desktop environment didn't start correctly. It seems like the symlinks are being resetted wrongly by ldconfig (executed on boot by /etc/rc.d/rc.M) If I then rerun the installation skript (nvidia-switch --install), I can start my desktop environment. Code:
/sbin/ldconfig (this command is in the start script /etc/rc.d/rc.M) Thanks for helping |
The libraries may get mixed up between open source and blob if you make a mistake with removing nvidia in that setup from my experience. I prefer to use the long lived branch nvidia .run installer file if it works. http://www.nvidia.com/object/unix.html
Save the .run file because some updates will require a reinstall. |
Yes, with the nvidia .run installer it worked perfectly. Thanks
|
Welcome to the forum.
You should use "Thread Tools" at the top of the original post to mark this thread as SOLVED. |
Just noticed this thread. This was reported on the SBo mailing list and to me directly, as maintainer, and I will be posting a fix this weekend. This ldconfig issue took me by surprise due to Nvidia's naming scheme for the GLVND versions of the drivers.
|
same problem here
Hi to all, I have the same problem with nvidia drivers libs conflicting with mesa ones...
I'd like to ask if it is safe to just removepkg mesa (& mesa-compat-32) I've lost a bit of time to figure out what the problem was exactly, since I usually use the web as last resort. Initially I though that nvidia-switch was just taking fool of me every boot, then I've noticed it was indeed ldconfig's fault. so, what will happen if I remove mesa? do nvidia drivers or openGL in general rely on something that is NOT whitin nvidia packages? will this prevent ldconfig from bothering my nvidia libraries? thanks in advance if someone has the answer |
I would not do that.
The README to the nvidia slackbuilds states that you should run "nvidia-switch --remove" prior to installing the package. You can be a lazy scut (which I fully admit that I have been) and not do it; that works most of the time. When it doesn't work, it's pretty painful to fix the resulting issues (as I have found out more than once, which tells you how lazy of a scut I am). |
Quote:
Hi, how it's possible to do nvidia-switch --remove before actually installing nvidia-driver? probably i'm not understanding something I think you're right, maybe removing mesa would be too extreme.... mv *.-xorg somewhere else will maybe work? will ldconfig complain upon boot? last questions, is there a way to tell ldconfig HOW to handle that bounch of library? like blacklisting them or something along those lines? |
hi Spike8605, welcome to LQ.
this has already been fixed by kingbeowulf a few days ago and will go in at the next public update https://slackbuilds.org/cgit/slackbu...804a941628dc51 |
Quote:
as far as I can understand, according to this patch, nvidia-switch will move files not to *-xorg but to xorg-* so that alphabetically they came after *-nvidia and therefore ldconf will keep the link as per-install right? so I can safetly move those xorg files somewhere else until the update is committed to the slackbuild site? also, do you know when the patch will be avaible in slackbuild 14.2 site? thanks again |
Quote:
Quote:
|
Quote:
in the meanwhile, since I like to break and then fix things, I'll move the files manually before boot and see what will break (if anything at all) :D Kind Regards |
As a reminder, the nvidia-driver libs only conflict with a few Mesa and Xorg libs. Also, mesa contains a number of libs and files utilized by ANY GPU driver you may install, so you can't just remove it. Given how the driver packages from Nvidia are organized, it is tedious to not only keep track of the libs but also which ones conflict with Xorg and Mesa.
In a worse case scenario, if you forget to 'nvidia-switch --remove' before 'removepkg nvidia-driver', just remove any dangling 'xorg' labelled files. Then you simply need to reinstall the original mesa, mesa-compat32 (if installed) and xorg-server packages from the your Slackware tree. This also applies to the Nvidia provided binary installer: they just move the lib conflicts to /var/lib/nvidia. I've added an option to nvidia-switch to assist in this process. To remove SBo nvidia-driver and fully restore the original packages. Simply put a copy of: Quote:
Code:
nvidia-switch --remove Simple. Piece of cake. |
Hello again and sorry for the delay, I was enjoying Slack so much that I forgot about this thread :D
Quote:
Quote:
I already like a lot the way the Slackbuilds system (and Slack in general) work! Thanks again for the hints and the slackbuild fix, I will update the drivers as soon as I will feel the need (if ain't broke... ;) ) *now let's go back to remove that cursed pulseaudio thingie..... :D Bye! |
All times are GMT -5. The time now is 09:08 PM. |