[SOLVED] xorg doesn't run after upgrade from 14.0 to 14.1

zux · 03-02-2014, 02:28 PM

The problem is almost like this one:
http://www.linuxquestions.org/questi...er-4175496398/
only the driver is intel.
here is the log Xorg.0.log

KDM does start, but after successful login it just restarts.
what could be the problem?

Didier Spaier · 03-02-2014, 03:02 PM

What happens if you boot at run level 3 then type "startx"?

ReaperX7 · 03-02-2014, 03:34 PM

Did you create a new KDM configuration after the upgrade or did you keep the 14.0 configuration?

When you upgrade any UNIX OS to a newer version, you should always backup current configurations and then restore the defaults. After you create a new configuration then you use the old configuration to switch the settings to your own.

slkrover · 03-02-2014, 06:57 PM

Had the same problem with nvidia. I downloaded the drive on a different computer and put it on a usb and installed it before x started.

zux · 03-02-2014, 10:21 PM

Quote:

Originally Posted by Didier Spaier

What happens if you boot at run level 3 then type "startx"?

this is where stuff gets really interesting, it dies asking for a non existing nvidia library....
i had nvidia video card on this pc earlier, but it's long gone. could there be some config files left somewhere?
I tried cleaning out all of /etc/X11 and /usr/share/X11/ but with no luck

enorbet · 03-02-2014, 10:21 PM

OP title line is incorrect since xorg did start or the KDM login greeter wouldn't show. What is failing is the particular DE chosen to load. First step should be to try others, assuming you have some installed as is common on a recommended install. If that fails or you don't have any other WM/DEs installed, try to login as another user. Either create a new one if one doesn't exist or just briefly try root login.

You can try checking /var/log/Xorg.0.log but I'm betting that shows no errors. You need something like XSession errors if the above doesn't give you a clue.

zux · 03-02-2014, 10:22 PM

Quote:

Originally Posted by ReaperX7

Did you create a new KDM configuration after the upgrade or did you keep the 14.0 configuration?

When you upgrade any UNIX OS to a newer version, you should always backup current configurations and then restore the defaults. After you create a new configuration then you use the old configuration to switch the settings to your own.

where is KDM configuration files?
I did try to create a new clean user, but that did not help
also tried to remove package "kde-workspace" and the mannually delete /etc/kde/kdm
reinstalled "kde-workspace" but nothing changed

zux · 03-02-2014, 10:48 PM

ok, this keeps getting more and more interesting
tried running startx from runlevel 3 and it runned desktop manager TWM.
in that, i tried running kde system configuration tool, but it dies with an error about missing libnvidia-tlz.so.280.13
then tried to run pkgtool to change the default desktop manager, but only TWM is available...
now idea where to look now...

enorbet · 03-02-2014, 11:12 PM

Quote:

Originally Posted by zux

ok, this keeps getting more and more interesting
tried running startx from runlevel 3 and it runned desktop manager TWM.
in that, i tried running kde system configuration tool, but it dies with an error about missing libnvidia-tlz.so.280.13
then tried to run pkgtool to change the default desktop manager, but only TWM is available...
now idea where to look now...

You're right. This is getting more and more interesting since it seems like Xorg gets started OK but KDE is halting due to some config hangover from nVidia. Couple suggestions------

1) assuming you did the Full Install, KDE is default, but you also should have others such as Xfce4. So, from the runlevel 3 login, try direct commands like

Code:

"startxfce4" or "startfluxbox" or even "startkde"

be careful as you will be in as root but should get some useful info.

2) The KDM configuration files are usually in "/usr/share/config/kdm/kdmrc" but I'm not sure how much good that will do you other than allowing you to add Xfce and Fluxbox to the KDM boot menu. I'm some surprised they aren't there already as I have only ever had hoops to jump through for Enlightenment, largely because the launch command for it changed with E17. To automatically add other WM/DEs to KDM requires a "foo.desktop" file in a folder whose name I forget but will check.

You may be able to sidestep this issue (or several issues) by issuing

Code:

 genkdmconf --help

but I'm guessing you may have to research uninstalling the nvidia driver since it not only installs nvidia.ko but several Mesa and GLX libraries.

zux · 03-02-2014, 11:47 PM

Quote:

Originally Posted by enorbet

You're right. This is getting more and more interesting since it seems like Xorg gets started OK but KDE is halting due to some config hangover from nVidia. Couple suggestions------

1) assuming you did the Full Install, KDE is default, but you also should have others such as Xfce4. So, from the runlevel 3 login, try direct commands like

Code:

"startxfce4" or "startfluxbox" or even "startkde"

be careful as you will be in as root but should get some useful info.

2) The KDM configuration files are usually in "/usr/share/config/kdm/kdmrc" but I'm not sure how much good that will do you other than allowing you to add Xfce and Fluxbox to the KDM boot menu. I'm some surprised they aren't there already as I have only ever had hoops to jump through for Enlightenment, largely because the launch command for it changed with E17. To automatically add other WM/DEs to KDM requires a "foo.desktop" file in a folder whose name I forget but will check.

You may be able to sidestep this issue (or several issues) by issuing

Code:

 genkdmconf --help

but I'm guessing you may have to research uninstalling the nvidia driver since it not only installs nvidia.ko but several Mesa and GLX libraries.

startxfce4 ends wanting nvidia...
startfluxbox and startkde both don't start saying that they cannot connect to display.
kdm does have other desktop envoronments at it's menu, the pkgconfig doesn't.
running kde or xfce from kdm menu results in the same way, back to kdm login.

genkdmconf says that it does not know how to create missing GreeterUID

enorbet · 03-03-2014, 04:40 AM

Perhaps a new config file is responsible but it is clear that there are remnants from your nVidia driver lying around. I'm some curious as to what Xorg.0.log is saying about "not being able to connect to display" but it is probably more constructive to

1)look at your "/etc/X11/xorg.conf" file to see if there remains a call from there for some nVidia library

2) rename it so a new one is built
or
3) run "xorgsetup"

BTW if you know what NVIDIA-xxxx-.run file you used to install nVidia originally it is possible to run it with the "--uninstall" switch which may fix the issue as well. I'm wracking my brain to figure out why this only popped up after an upgrade since I assume it has been working with whatever new videocard you're using. Seems like it has to be a config file somewhere but I never let new configs load until after I'm up and running. Did you rename any or all from "foo.conf.new" in the upgrade?

zux · 03-03-2014, 05:14 AM

there is no /etx/X11/xorg.conf and nothing in /etc/X11/xorg.conf.d
I cleaned the all out as step first

ruuned xorgsetup, it created /etc/X11/xorg.conf
as I am not at the pc now, i can only test remotly, startxfce4 is still asking about nvidia, but i cannot test kdm login since a cannot access the keyboard

I found some NVIDIA-xxx-.run installers and tried those with the uninstall options, and it did remove something, but that did not help.

it did work before the upgrade, but i can't rule out that i have made some mistakes in the upgrade process itself. I runned "slackpkg new_config" after the upgrade and manually selected actions for each *.new config files. I applied the new configs to almost all configs, except for rc.local.

Correct me if i'm wrong, if a have a new clean user, the only problems can be some configs in /etc/ ? maybe i can run a diff from a clean install and manually look at every difference?

zux · 03-03-2014, 06:00 AM

I searched my system for leftover nvidia files, found and deleted this:

Code:

rm /usr/lib/libGL.so.280.13-nvidia

after that i could not launch X because of missing libGL, i searched for packages containing libGL and ended up reinstalling these:

Code:

slackpkg reinstall glew glu mesa

and that solved the issue

I still have no idea why it worked before upgrade or how could I have broken it during the upgrade, but it works now, so thanks for advices.

enorbet · 03-03-2014, 06:13 AM

Please forgive me but I'm falling asleep so I don't know how helpful this will be. Yes configs are in "/etc" and it may be instructive to compare to a clean install but I can't escape this nagging sense that something else is going on, either altogether or in addition to.

I looked at my "/var/log/nvidia-installer.log" and unless one runs the optional built in program to setup "/etc/X11/xorg.conf" it is entirely confined to "/usr". Most of what it does is in building the kernel module so 95% of it is all in "/usr/src/linux/". Only at the very end is there this

Code:

 Installing both new and classic TLS OpenGL libraries.
-> Parsing log file:
-> done.
-> Validating previous installation:
-> done.
-> Uninstalling NVIDIA Accelerated Graphics Driver for Linux-x86 (1.0-33120 (331.20)):
-> done.
-> Uninstallation of existing driver: NVIDIA Accelerated Graphics Driver for Linux-x86 (331.20) is complete.
-> nvidia-installer will install the libvdpau and libvdpau_trace libraries that were included with this installer package. These libraries are available separately through the libvdpau project and will be removed from the NVIDIA Linux driver installer package in the future, so it is recommended that VDPAU users install libvdpau separately, e.g. by using packages available from their distributions, or by building from the sources available at:

http://people.freedesktop.org/~aplattner/vdpau
-> Searching for conflicting X files:
-> done.
-> Searching for conflicting OpenGL files:
-> done.
-> Installing 'NVIDIA Accelerated Graphics Driver for Linux-x86' (331.20):
   executing: '/sbin/ldconfig'...
   executing: '/sbin/depmod -aq'...
   ignored deprecated option -q
-> done.
-> Driver file installation is complete.
-> Running post-install sanity check:
-> done.
-> Post-install sanity check passed.
-> Shared memory test passed.
-> Running runtime sanity check:
-> done.
-> Runtime sanity check passed.
-> Would you like to run the nvidia-xconfig utility to automatically update your X configuration file so that the NVIDIA X driver will be used when you restart X?  Any pre-existing X configuration file will be backed up. (Answer: Yes)
-> Your X configuration file has been successfully updated.  Installation of the NVIDIA Accelerated Graphics Driver for Linux-x86 (version: 331.20) is now complete.

So I'm wondering if yours replaced any conflicting files or if you need VDPAU for intel_drv. At this point I don't see how a conf file in "/etc" can create the issue of looking for and not finding an nVidia based library. This seems like something lacking in the Intel xorg driver or supporting libraries causing some kind of fallback issue.

I'm more inclined to think the update to xorg is lacking in one of these areas or both - the Intel driver and/or VDPAU. Maybe compare versions of "intel_drv" or try Intel's latest?

Maybe tomorrow after some sleep I will be clearer and of more help. Best wishes

zux · 03-03-2014, 11:56 AM

you probably missed the SOLVED mark because of lack of sleep

i believe that nvidia creates the libGL library and replaces the actual link to it's own version of it. now why did it work before the upgrade and not after remains a mistery. upgrading might have reversed some link or the new version started using other link, but the upgrade did not replace it, because it was there?