nvidia current

[effenberg0x0]

Ok, I'm still testing here but:

- You have xserver 1.12.99.902 (1.13.0 RC 2), which may be the source of the problem. All your other stuff works with 1.12.1.902 (1.12.2 RC 2).

- More importantly (this is where I'm getting at recently - see http://ubuntuforums.org/showthread.php?t=2038500), look at your logs here:

[ 27.115] (II) NVIDIA GLX Module 304.32 Thu Aug 2 19:03:23 PDT 2012
[ 27.115] Loading extension GLX
[ 27.115] (II) LoadModule: "nvidia"
[ 27.115] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
[ 27.115] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 27.115] compiled for 4.0.2, module version = 1.0.0
[ 27.115] Module class: X.Org Video Driver
[ 27.118] (EE) NVIDIA: Failed to load the NVIDIA kernel module. Please check your
[ 27.118] (EE) NVIDIA: system's kernel log for additional error messages.
[ 27.118] (II) UnloadModule: "nvidia"
[ 27.118] (II) Unloading nvidia

This is the point. Why doesnt it find and load your proper nvidia module? In all testing I've done so far, it comes from a problem with module aliases.
Your output shows us that "nvidia" is set as an alias to nvidia-current-updates.ko in your modprobe conf files. And you do have this module at /lib/modules/3.5.0-8-generic/updates/dkms/nvidia_current_updates.ko.

My guess is that one can fix this by creating a softlink, like I did in the thread I mentioned above. The difference is that I was using NVidia's binary driver, which has a different naming convention.

What I mean is this: If you have softlinks at /lib/modules/3.5.0-8-generic/kernel/drivers/video and /lib/modules/3.5.0-8-generic/kernel/drivers/video/nvidia that point to /lib/modules/3.5.0-8-generic/updates/dkms/nvidia_current_updates.ko, X will manage to load NVidia module.

TEST:

sudo ln -s /lib/modules/3.5.0-8-generic/updates/dkms/nvidia_current_updates.ko /lib/modules/3.5.0-8-generic/kernel/drivers/video/nvidia.ko
sudo ln -s /lib/modules/3.5.0-8-generic/kernel/drivers/video/nvidia.ko /lib/modules/3.5.0-8-generic/kernel/drivers/video/nvidia_current.ko
sudo ln -s /lib/modules/3.5.0-8-generic/kernel/drivers/video/nvidia.ko /lib/modules/3.5.0-8-generic/kernel/drivers/video/nvidia_current_updates.ko

sudo ln -s /lib/modules/3.5.0-8-generic/updates/dkms/nvidia_current_updates.ko /lib/modules/3.5.0-8-generic/kernel/drivers/video/nvidia/nvidia.ko
sudo ln -s /lib/modules/3.5.0-8-generic/kernel/drivers/video/nvidia.ko /lib/modules/3.5.0-8-generic/kernel/drivers/video/nvidia/nvidia_current.ko
sudo ln -s /lib/modules/3.5.0-8-generic/kernel/drivers/video/nvidia.ko /lib/modules/3.5.0-8-generic/kernel/drivers/video/nvidia/nvidia_current_updates.ko

sudo reboot now

UNDO CHANGES (If it fails to fix things)
OBS: It will only remove the softlinks we created, not the modules.

sudo rm -rf /lib/modules/3.5.0-8-generic/kernel/drivers/video/nvidia.ko
sudo rm -rf /lib/modules/3.5.0-8-generic/kernel/drivers/video/nvidia_current.ko
sudo rm -rf /lib/modules/3.5.0-8-generic/kernel/drivers/video/nvidia_current_updates.ko

sudo rm -rf /lib/modules/3.5.0-8-generic/kernel/drivers/video/nvidia/nvidia.ko
sudo rm -rf /lib/modules/3.5.0-8-generic/kernel/drivers/video/nvidia/nvidia_current.ko
sudo rm -rf /lib/modules/3.5.0-8-generic/kernel/drivers/video/nvidia/nvidia_current_updates.ko

Let me know the results please.

Thanks!
Effenberg

[flipper T]

hi

followed your instructions, rebooted, no change as far as i can tell.

must go now, sleepy, but will be back soon.

[effenberg0x0]

If anyone wants to jump in, my questions right now are:

- There is a percentage of people with w non-usable set of xserver+unity+compiz+kernel+nvidia module+nvidia drivers, this is normal. But why do we now suddenly see a relevant and apparetly growing percentage of users with Xorg/Kernel log pointing out problems finding NVidia module? Where is this coming from?

- So far, I can only guess it has something to do with the way module aliases get after the users switch between NVidia from binary installer, nvidia-current, nvidia-current-updates, nouveau, xorg-edgers, etc.

- When that is in fact the problem, one has a couple alternatives to fix it: See As seen here: http://ubuntuforums.org/showthread.php?t=2038500

- NVidia binary installer seems to auto check/fix modules to some extent (blacklists nouveau, for example). But it does not fix previous nvidia* aliases. Jockey has been under changes, it could be it. Is anyone keeping up with how its nvidia python handler deals with modules aliases?

- NVidia recently added dkms support. But I can't quite understand how dkms could be a part in this problem.

Regards,
Effenberg

EDIT: Is anyone interested on joining efforts to code a NVidia diagnostic/fix shell script that consolidates all or most of the common issues and workarounds we know about it? I think it can be useful for us testers, for support people, and as a sort of specification for further developments in Jockey/handlers. It's not something hard to do and maybe we can generalize it to ATI / Intel too.

[mc4man]

While I'm not using nvidia atm normally -
installing the current Ubuntu package - any attempt to draw anything on the screen kills X in a 3d session (unity 3d, classic with effects, gnome-shell.
So the first time from nouveau to nvidia in unity 3d, because I don't use the Desktop I can successfully login, & use compiz as long as nothing is (re)-drawn (switch viewports
As soon as anything is attempted, even just a tooltip from launcher, then xserver is killed & go back to login screen
(Feels just like if one ran a kill xserver command.

This happens with Xorg 1.13.0 RC 2, (proposed) or RC 3 (the ppa), haven't tried the Xorg source in main as that would involve more than I want to do atm,

The most prevalent error I see is fairly generic -
XIO: fatal IO error 4 (Interrupted system call) on X server ":0"

[effenberg0x0]

While I'm not using nvidia atm normally -
installing the current Ubuntu package - any attempt to draw anything on the screen kills X in a 3d session (unity 3d, classic with effects, gnome-shell.
So the first time from nouveau to nvidia in unity 3d, because I don't use the Desktop I can successfully login, & use compiz as long as nothing is (re)-drawn (switch viewports
As soon as anything is attempted, even just a tooltip from launcher, then xserver is killed & go back to login screen
(Feels just like if one ran a kill xserver command.

This happens with Xorg 1.13.0 RC 2, (proposed) or RC 3 (the ppa), haven't tried the Xorg source in main as that would involve more than I want to do atm,

The most prevalent error I see is fairly generic -
XIO: fatal IO error 4 (Interrupted system call) on X server ":0"

I know this error message: AFAIK, this XIO error is never the problem. It is raised when when something tries to talk to X but X is already closed. As it happens when you have stuff in your X startup script but X dies too fast.

A suggestion: What if you login, switch to any VT, then DISPLAY=:0.0 compiz --replace, go back to VT7 and let it crash? Maybe compiz would give us some output we could use in the VT.

Or explore compiz --debug, but you would also need the dgbsym to step it through gdb. Check https://wiki.ubuntu.com/DebuggingCompiz. It can be a lot of fun

Regards,
Effenberg

[mc4man]

Doesn't really have anything to do with compiz here, it's simply nvidia-current 304.32-0ubuntu3 won't work in a 3d session with xserver 1.13 (RC2 or 3
Reverting back to the xserver-xorg that's currently in main, ( 1.12.1.902 (1.12.2 RC 2) and the nvidia driver works fine.

[VinDSL]

If anyone wants to jump in, my questions right now are [...]

Doesn't really have anything to do with compiz here, it's simply nvidia-current 304.32-0ubuntu3 won't work in a 3d session with xserver 1.13[...]

Exactly!

nvidia-current 304.3x works fine with LXDE/Openbox (on top of Ubu 12.10) but the Unity and GS DEs fail to load.

vindsl@Zuul:~$ apt-cache policy nvidia-current
nvidia-current:
  Installed: 304.32-0ubuntu3
  Candidate: 304.32-0ubuntu3
  Version table:
 *** 304.32-0ubuntu3 0
        500 http://mirrors.se.eu.kernel.org/ubuntu/ quantal/restricted i386 Packages
        100 /var/lib/dpkg/status
     304.32-0ubuntu1~xedgers~quantal1 0
        500 http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu/ quantal/main i386 Packages

vindsl@Zuul:~$ apt-cache policy lxde
lxde:
  Installed: 0.5.0-4ubuntu3
  Candidate: 0.5.0-4ubuntu3
  Version table:
 *** 0.5.0-4ubuntu3 0
        500 http://mirrors.se.eu.kernel.org/ubuntu/ quantal/universe i386 Packages
        100 /var/lib/dpkg/status

vindsl@Zuul:~$ apt-cache policy openbox
openbox:
  Installed: 3.5.0-4
  Candidate: 3.5.0-4
  Version table:
 *** 3.5.0-4 0
        500 http://mirrors.se.eu.kernel.org/ubuntu/ quantal/universe i386 Packages
        100 /var/lib/dpkg/status

vindsl@Zuul:~$ echo && echo "~ VinDSL Unity Debug Script 12.5.20 (vindsl.com) ~" && echo -n "Current Date/Time: " && date && echo -n "Distro Release: " && lsb_release -sd && echo -n "Kernel Release: " || cat /etc/*release && uname -s -r && echo -n "Unity Release: " && unity --version && echo && /usr/lib/nux/unity_support_test -p -f && echo || echo && dpkg -s mesa-utils && echo || echo && echo "Xserver Xorg Core Branch" && apt-cache policy xserver-xorg-core | grep Installed && echo

~ VinDSL Unity Debug Script 12.5.20 (vindsl.com) ~
Current Date/Time: Wed Aug  8 04:07:03 MST 2012
Distro Release: Ubuntu quantal (development branch)
Kernel Release: Linux 3.6.0-030600rc1-generic
Unity Release: unity 6.0.0

OpenGL vendor string:   NVIDIA Corporation
OpenGL renderer string: GeForce 7600 GT/AGP/SSE2
OpenGL version string:  2.1.2 NVIDIA 304.32

Not software rendered:    yes
Not blacklisted:          yes
GLX fbconfig:             yes
GLX texture from pixmap:  yes
GL npot or rect textures: yes
GL vertex program:        yes
GL fragment program:      yes
GL vertex buffer object:  yes
GL framebuffer object:    yes
GL version is 1.4+:       yes

Unity 3D supported:       yes

Package: mesa-utils
Status: install ok installed
Priority: optional
Section: x11
Installed-Size: 132
Maintainer: Ubuntu X-SWAT <ubuntu-x@lists.ubuntu.com>
Architecture: i386
Source: mesa-demos
Version: 8.0.1+git20110129+d8f7d6b-0ubuntu2
Replaces: xbase-clients (<< 6.8.2-38)
Depends: libc6 (>= 2.4), libgl1-mesa-glx | libgl1, libx11-6
Description: Miscellaneous Mesa GL utilities
 This package provides several basic GL utilities built by Mesa, including
 glxinfo and glxgears.
Homepage: http://mesa3d.sourceforge.net/

Xserver Xorg Core Branch
  Installed: 2:1.12.99.903+git20120801.afa53fe7-0ubuntu0ricotz

vindsl@Zuul:~$

Only problem I'm currently having is with fontconfig...

vindsl@Zuul:~$vindsl@Zuul:~$ apt-cache policy fontconfig
fontconfig:
  Installed: 2.10.1-0ubuntu2
  Candidate: 2.10.1-0ubuntu2
  Version table:
 *** 2.10.1-0ubuntu2 0
        500 http://mirrors.se.eu.kernel.org/ubuntu/ quantal/main i386 Packages
        100 /var/lib/dpkg/status

vindsl@Zuul:~$ fc-match
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 103: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 138: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf", line 9: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf", line 21: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf", line 9: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf", line 21: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/89-tlwg-loma-synthetic.conf", line 12: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf", line 9: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf", line 21: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/90-fonts-nanum.conf", line 9: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/90-fonts-nanum.conf", line 22: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/90-fonts-nanum.conf", line 22: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/90-fonts-nanum.conf", line 22: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/90-fonts-nanum.conf", line 26: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/90-fonts-nanum.conf", line 31: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/90-fonts-nanum.conf", line 40: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/90-fonts-unfonts-core.conf", line 11: Having multiple values in <test> isn't supported and may not works as expected
vindsl@Zuul:~$

This fontconfig prob seems to be universal, affecting all Linux distros, not just Debian-based ones, judging by the results on various search engines.

[effenberg0x0]

VinDSL, mc4man

My bad, when I saw reports that people could use unity 2D but not Unity 3D I thought of Compiz. I had not paid attention to reports of no 3D also in other DEs.

Regards,
Effenberg

[dino99]

This fontconfig prob seems to be universal, affecting all Linux distros, not just Debian-based ones, judging by the results on various search engines.

Have had this issue too, but as the errors comments says, its deprecated : simply rename (or delete) .fonts.conf file & .fontconfig folder, then the new paths will be used instaed

[VinDSL]

Have had this issue too, but as the errors comments says, its deprecated : simply rename (or delete) .fonts.conf file & .fontconfig folder, then the new paths will be used instaed

Sweet!

I'll try that...