sony-vaio-z-series team mailing list archive

[Raphael Gradenwitz <raphael@xxxxxxxxxxxxxxxxx>]

Hello Christophe,

Am Montag, den 21.12.2009, 21:04 +0000 schrieb
domakmail-ubuntu@xxxxxxxx:
> I've done what you said. The nvidia driver was deinstalled but the
> Xorg didn't fail when restart (I don't understand because I check with
> lspci I had only the nvidia card). By the way the background gradation
> of the login screen was not as usual, as if I had only a few colors.

Yes, that I guess is the so caled 'vesa' (low graphics) mode. You must
have become a little window asking you if you want to enter in this mode
or if you rather want to (beside some other options) 'Exit to console
login'. That would have been the right one.

> 
> So I rerun the janitor and reinstall nvidia driver 1.85 from the repo.
> Every thing is ok with nvidia.

Its your Laptop, you can install what you want ;-)

> with Intel, the switch-x-to is not anymore in infinite-loop.
> 
> the only thing is that glxinfo says:
> name of display: :0.0
> Xlib:  extension "GLX" missing on display ":0.0".
> Xlib:  extension "GLX" missing on display ":0.0".
> 

I encounter troubles of this kind directly after installation of the
nvidia driver but a simple reboot (stamina/intel) fixes that and glx
works fine under both.

> This is the same thing that when I reinstall my system from scratch.
> At this step I've created the symbolic link

Who told you to do so?

> (I will not do this error again):

Good ;-)

libGLcore is not used in stamina/intel mode thus not diverted or linked:
> domak@domakistan-laptop:~$ ll /usr/lib/libGL*
> lrwxrwxrwx 1 root root       22 2009-12-21 21:02 /usr/lib/libGLcore.so.1 -> libGLcore.so.185.18.36
> -rw-r--r-- 1 root root 18972488 2009-10-26 11:16 /usr/lib/libGLcore.so.185.18.36

As you can see, the 'switch-x-to' script could find the REAL target and
could link that one but here is a file missing, the symlink
"/usr/lib/libGL.so -> libGL.so.1"
that may be the reason why your GLX was failing

> lrwxrwxrwx 1 root root       13 2009-12-21 21:12 /usr/lib/libGL.so.1 -> libGL.so.1000
> lrwxrwxrwx 1 root root       28 2009-12-21 21:12 /usr/lib/libGL.so.1000 -> nvidia/libGL.so.1.2.xlibmesa
> -rw-r--r-- 1 root root   792992 2009-10-26 11:16 /usr/lib/libGL.so.185.18.36


> domak@domakistan-laptop:~$ ll /usr/lib/nvidia/
> total 1080
> -rw-r--r-- 1 root root 527256 2009-10-14 00:17 libGL.so.1.2.xlibmesa
> lrwxrwxrwx 1 root root     12 2009-12-21 20:18 libGL.so.1.xlibmesa -> libGL.so.1.2
> -rw-r--r-- 1 root root 422064 2009-11-14 18:53 libglx.so.xserver-xorg-core
> -rw-r--r-- 1 root root 133896 2009-10-26 11:16 libnvidia-cfg.so.185.18.36
> -rwxr-xr-x 1 root root   5064 2009-10-26 11:16 tls_test
> -rw-r--r-- 1 root root   4920 2009-10-26 11:16 tls_test_dso.so
> 
> So the following link is broken:
> lrwxrwxrwx 1 root root     12 2009-12-21 20:18 libGL.so.1.xlibmesa -> libGL.so.1.2
> 
No it is NOT broken, it just does not point to an existing target since
the target was renamed with a sufix (the name of the original package it
belongs to). The 'switch-x-to' script reads the target and assumes the
dirname of the original place in order to find the name of the diverted
target. If someone now 'fixes' this (normaly not used) symlink, the
switch script will fail and may walk in an infinite loop.

> I check the log
> domak@domakistan-laptop:~$ grep EE /var/log/Xorg.0.log 
>     (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (II) Loading extension MIT-SCREEN-SAVER
> (EE) Failed to load module "i810" (module does not exist, 0)

What is this searching for i810? You need i915!

> (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver
> not found)

OK, that faults seem to be from the boot before where you booted in vesa
mode (with uninstalled nvidia driver)

> 
> but i don't understant the mention to nvidia cause
> domak@domakistan-laptop:~$ lspci | grep VGA
> 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
> 
> domak@domakistan-laptop:~$ dpkg-divert --list

[unneeded lines disposed]

> diversion of /usr/lib/libGL.so.1 to /usr/lib/nvidia/libGL.so.1.xlibmesa by nvidia-glx-185
> diversion of /usr/lib/libGL.so.1.2 to /usr/lib/nvidia/libGL.so.1.2.xlibmesa by nvidia-glx-185
> diversion of /usr/lib/xorg/modules/extensions/libglx.so to /usr/lib/nvidia/libglx.so.xserver-xorg-core by nvidia-glx-185
> diversion of /usr/lib32/libGL.so to /usr/lib32/nvidia/libGL.so.xlibmesa by nvidia-glx-185
> diversion of /usr/lib32/libGL.so.1 to /usr/lib32/nvidia/libGL.so.1.xlibmesa by nvidia-glx-185
> diversion of /usr/lib32/libGL.so.1.2 to /usr/lib32/nvidia/libGL.so.1.2.xlibmesa by nvidia-glx-185

What does this file her? It is Part of the nvidia driver and should not
apear in /usr/lib/xorg/modules/extensions. It is not a part of
'libgl1-mesa-glx' (xlibmesa) like it is sufixed nore part of
xserver-xorg.core. One more 'self made problem'? ;-)

> diversion of /usr/lib/xorg/modules/extensions/libGLcore.so to /usr/lib/nvidia/libGLcore.so.xlibmesa by nvidia-glx-185
> 


> domak@domakistan-laptop:~$ ll /etc/X11/
> total 76
> drwxr-xr-x 2 root root  4096 2009-10-27 21:48 app-defaults
> drwxr-xr-x 2 root root  4096 2009-10-27 21:48 cursors
> -rw-r--r-- 1 root root    14 2009-10-27 21:50 default-display-manager
> drwxr-xr-x 6 root root  4096 2009-10-27 21:42 fonts
> -rw-r--r-- 1 root root 17394 2009-06-23 00:57 rgb.txt
> lrwxrwxrwx 1 root root    13 2009-11-28 13:01 X -> /usr/bin/Xorg
> drwxr-xr-x 3 root root  4096 2009-10-27 21:48 xinit
> drwxr-xr-x 2 root root  4096 2009-10-27 21:32 xkb

You took the option to create an xorg.conf.failsafe (the system did for
you) instead of 'Exit to console login' like I dexcribed:

> -rw-r--r-- 1 root root   269 2009-12-12 12:30 xorg.conf.failsafe
> -rw-r--r-- 1 root root   218 2009-12-21 21:02 xorg.conf.NVIDIA
> drwxr-xr-x 2 root root  4096 2009-12-04 20:43 Xresources
> -rwxr-xr-x 1 root root  3730 2008-06-25 04:05 Xsession
> drwxr-xr-x 2 root root  4096 2009-12-04 20:43 Xsession.d
> -rw-r--r-- 1 root root   265 2008-06-25 04:05 Xsession.options
> -rw-r--r-- 1 root root    13 2009-08-25 02:43 XvMCConfig
> -rw------- 1 root root   601 2009-10-27 21:34 Xwrapper.config
> 
> 
> I don't understand what I'm doing wrong. I'm exactly in the same case
> when I've resinstalled from scratch. 

Don't tell me that you have installed from scratch in the meantime ;-)

> It's not a big problem (nvidia is ok, and I don't really need glx on
> intel) but I'm curious to understant what happens.

[fullquotes disposed]

Try the newest version of the janitor script, first take the option
change nvidia installation, uninstall and then look if everything is
there where it has to be:

No nvidia related diversions,

No file
/usr/lib/xorg/modules/extensions/libGLcore.so
since that one is not part of any package

Does the lowermost symlink "/usr/lib/libGL.so -> libGL.so.1" exist?

If everything is there and glx works fine (maybe you have to reboot)
than run the janitor script again and begin installing your nvidia.

Now please do not change anything by hand if you want more support from
my side or at least report the changes you made exactly and


peace!

Regards,

Raphael