[SOLVED] Nvidia don't start after upgrade of xorg and nvidia driver.
SlackwareThis Forum is for the discussion of Slackware 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.
Nvidia don't start after upgrade of xorg and nvidia driver.
Hi,
I use Slackware64 14.1 (not current), using the nvidia driver installed through the automatic nvidia installer (from slackbuild), for display.
However, after I upgraded all my packages (both slackbuilds and officials), including nvidia and xorg, after rebooting xorg don't load and I am stuck in runlevel 3. Running 'startx' is only answered by 'xinit: unable to connect to X server: Connection refused'
Here is the xorg.0.log file in the attachment:
Also, strangely sbopkg simply don't work anymore and bash don't seem to recognize its existence anymore, although I checked that sbopkg is still running. It should be related to the massive upgrade that I did before nvidia failed to work.
What should I do in order to make nvidia work again? Should I try to reinstall nvidia? (In this case, the sbopkg issue should first be solved...)
Can you tell us about how you upgraded your packages more specifically? What version of nvidia kernel/driver did you upgrade to? What versions where you running? Can you tell us what video card you have?
Code:
lspci | grep VGA
Did you follow the directions for upgrading the nvidia driver?
Quote:
Included is a script called nvidia-switch, which is used to switch from the
xorg driver to the nvidia driver, but it will not edit xorg.conf for you;
you have to do that manually. The nvidia-switch script is installed to
/usr/sbin. NOTE: Although nvidia-switch is aware of a COMPAT32 environment,
its use therein is not supported.
Usage of nvidia-switch:
nvidia-switch --install <--> install the nvidia files and save the
stock xorg files.
nvidia-switch --remove <--> remove the nvidia files and symlinks and
restore the stock xorg files.
You do NOT have to run nvidia-switch after installing the package.
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]/xorg/modules/extensions/{libglx.so libglx.la}
Simply remove the dead nvidia symlinks and rename the saved '-xorg' appended files.
I upgraded to the new version of nvidia driver, using the slackbuild version 352.30 (from 340.24) installed through sbopkg. Then, I forgot to check the changelog. However, I took the precaution of keeping the old configuration files, whilst using the new ones from the upgrade.
In this case, how should I remove the dead nvidia symlinks? I cannot find a file called /usr/lib64/libGL.so.1.2. However, I found /usr/lib64/xorg/modules/extensions/libglx.la and /usr/lib64/xorg/modules/extensions/libglx.so.
If the newer drivers are like the older ones..it may need to be patched with -current now in 4.x. I saw on the other forum such as arch and gentoo of the conflict to reinstall the driver
yes a long time ago slackware 14.1 had an xorg update you will need to uninstall nvidia reinstall mesa then reinstall nvidia driver. the reason why it has broke the links.
this also tells me your update was a long time coming also.
Code:
Tue Dec 23 00:05:23 UTC 2014
patches/packages/ntp-4.2.8-x86_64-1_slack14.1.txz: Upgraded.
In addition to bug fixes and enhancements, this release fixes
several high-severity vulnerabilities discovered by Neel Mehta
and Stephen Roettger of the Google Security Team.
For more information, see:
https://www.kb.cert.org/vuls/id/852879
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-9293
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-9294
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-9295
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-9296
(* Security fix *)
patches/packages/php-5.4.36-x86_64-1_slack14.1.txz: Upgraded.
This update fixes bugs and security issues.
#68545 (NULL pointer dereference in unserialize.c).
#68594 (Use after free vulnerability in unserialize()). (CVE-2014-8142)
#68283 (fileinfo: out-of-bounds read in elf note headers). (CVE-2014-3710)
For more information, see:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3710
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8142
(* Security fix *)
patches/packages/xorg-server-1.14.3-x86_64-3_slack14.1.txz: Rebuilt.
This update fixes many security issues discovered by Ilja van Sprundel,
a security researcher with IOActive.
For more information, see:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8091
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8092
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8093
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8094
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8095
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8096
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8097
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8098
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8099
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8100
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8101
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8102
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8103
(* Security fix *)
patches/packages/xorg-server-xephyr-1.14.3-x86_64-3_slack14.1.txz: Rebuilt.
patches/packages/xorg-server-xnest-1.14.3-x86_64-3_slack14.1.txz: Rebuilt.
patches/packages/xorg-server-xvfb-1.14.3-x86_64-3_slack14.1.txz: Rebuilt.
Beyond this issue of Nvidia, it seems that something very strange occured.
After unsuccessful attempt at installing the nvidia driver through the slackbuilds, I simply used the official installer from nvidia website. Despite numerous errors at the installer, I finally was able to boot at X11. Then, mate-desktop was unavailable. Soon, I found out why I coudn't use sbopkg anymore and why nvidia was disabled.
Every packages that I've installed through means other than the official Slackware repository seem to be gone. For some reason, the massive upgrade that I did, eliminated all those packages.
Since when using clean-system, I took the precaution of keeping the old config files replaced by the new files, is it possible to recover those packages? And why such thing occured?
Is there a mean to recover those packages? Why did it occured? I have previously updated Slackware in the same way (without blacklist), without any disaster.
You can install again the third-party packages, if you saved them somewhere. Else, you'll have to rebuild them
Quote:
Why did it occured?
"man slackpkg" says:
Code:
clean-system
This action removes all of the packages that don't belong to a
standard Slackware installation. With this option, you can clean
up your system, removing third-party packages as well as any pack
ages that were removed from the official Slackware package set.
If you have some third party (or custom built) packages that you
would like to keep, you can temporarily add them to the list of
blacklisted packages before you run the 'clean-system' action.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.