Failed to load module "nvidia"

[Lynn Schock]

I am using Intrepid Alpha 5. After installing Nvidia restricted driver #71, and then rebooting I get the following error messages:
Failed to load /usr/lib/xorg/modules/drivers/nvidia-drivers
Failed to load module "nvidia" (load failed 7)
Failed to load No drivers available
I have attached the log that was created by Intrepid when the driver failed to load.

When I install Nvidia restricted driver #173, and then reboot, the screen goes black and the monitor shuts down. I assume that it is also failing to load the Nvidia driver. When this happens there is no chance to make a log.

My Nvidia card is: Geforce 5900
I have two monitors:
Sony SDM-HS74P Digital
Sony SDM-M81 Analog

I have looked through the bug reports and forums, and I can't find a fix that appears to address this particular issue.

I am currently back to the driver that comes with Intrepid which runs on my digital monitor without, of course, acceleration or dual monitor capability.

I would appreciate any help that could be provided

[lspci]
01:00.0 VGA compatible controller: nVidia Corporation NV35 [GeForce FX 5900] (rev a1)
     Subsystem: Chaintech Computer Co. Ltd Device 1945
[ 0.485570] PCI: 0000:00:00.0 reg 10 32bit mmio: [d0000000, d7ffffff]
[ 0.778675] pci 0000:00:00.0: BAR 0: can't allocate resource
[ 0.788755] agpgart-amd64 0000:00:00.0: AGP bridge [1106/3188]
[ 0.793048] agpgart-amd64 0000:00:00.0: AGP aperture is 128M @ 0xd0000000

[Lynn Schock (schocklynn)]

Now, when I try to install the latest Nvidia driver, I get the following error messages when I restart the computer:
EE Problem parsing config file
EE Error parsing the config file

I have attached the log that was created when I rebooted,and got those messages.
Again, I am back to the default graphics driver.

I haven't edited any configuration files. The installer appears to be just not working.
Is this a bug in the installer?
Thanks for any help that you can offer
Lynn Schock

[Alberto Milone (albertomilone)]

According to the 1st log which you attached, you tried to use nvidia-glx-71:
(II) NVIDIA GLX Module 71.86.04 Mon Jan 21 11:12:04 PST 2008

This driver doesn't with Intrepid yet:
(II) Loading /usr/lib/xorg/modules/drivers//nvidia_drv.so
dlopen: /usr/lib/xorg/modules/drivers//nvidia_drv.so: undefined symbol: miZeroLineScreenIndex

See bug 251107:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-71/+bug/251107

The 2nd log reports this failure:
Parse error on line 12 of section Files in file /etc/X11/xorg.conf
 "RgbPath" is not a valid keyword in this section.

which was caused by nvidia-xconfig which put these (now invalid) lines in your /etc/X11/xorg.conf:

Section "Files"
    RgbPath "/usr/X11R6/lib/X11/rgb"
EndSection

My suggestion is:
1) use driver nvidia-glx-173 (do not use nvidia-xconfig but rely on either EnvyNG or Jockey)
2) remove the "Files" section (the three lines posted above)
3) restart either the Xserver or your computer.

[Lynn Schock (schocklynn)]

Thank you for your Email. Before I received your Email, I changed from
the 64 bit version of Intrepid to the 32 bit version (upgrading from a
Hardy 32 bit install) thinking that might help the problem which it
didn't.
Now when I attempt to install (using Jockey) the nvidia-glx driver
(version 173) - the xserver does not load, the screen goes black, and
the monitor shuts off.

Before I rebooted after using Jockey, I checked /etc/X11/xorg.conf using
gedit. The lines you refer to:

Section "Files"
> RgbPath "/usr/X11R6/lib/X11/rgb"
> EndSection
>
> are not there anymore so, of course I did not delete them.
>
> When I tried to use Envy NG after installing it with Synaptic, Envy crashed. I believe that
> your are aware of this problem because I saw your response at bug #22717.
>
> I did notice when I installed Envy that three packages are installed:
> Envy-core
> Envy-gtk
> fglrx-modaliases
>
> Does Jockey also install fglrx-modaliases, and could that be the problem?
>
> I know I don't know what to do. Any help that you could give would be greatly appreciated.
>

[Alberto Milone (albertomilone)]

On Saturday 27 September 2008 01:02:29 Lynn Schock wrote:
> Thank you for your Email. Before I received your Email, I changed from
> the 64 bit version of Intrepid to the 32 bit version (upgrading from a
> Hardy 32 bit install) thinking that might help the problem which it
> didn't.
> Now when I attempt to install (using Jockey) the nvidia-glx driver
> (version 173) - the xserver does not load, the screen goes black, and
> the monitor shuts off.
>
> Before I rebooted after using Jockey, I checked /etc/X11/xorg.conf using
> gedit. The lines you refer to:
>
> > Section "Files"
> >
> > RgbPath "/usr/X11R6/lib/X11/rgb"
> > EndSection
> >
> > are not there anymore so, of course I did not delete them.
> >
Ok, this time it must be a different problem then.

>
> Does Jockey also install fglrx-modaliases, and could that be the problem?
>
No, this is not a problem.

> I know I don't know what to do. Any help that you could give would be
> greatly appreciated.

type:
sudo sh nvidia-bug-report.sh

and attach the nvidia-bug-report.log which you will find in the same directory
in which you typed the command.

[Lynn Schock (schocklynn)]

When I typed sudo sh nvidia-bug-report.sh
and then entered my password I got:
sh: Can't open nvidia-bug-report.sh

I then reactivated the Nvidia driver version 173, rebooted,and again got
the black screen.

After repairing the Xserver in recovery mode,
I tried typing again: sudo sh nvidi-bug-report.sh, and again
got sh: Can't open nvidia-bug-report.sh

One thing that I noticed when I reactivated version 173 is that when I
selected it, the bottom of the hardware driver screen states that a
different version of the driver is in use. Is there any signifigance to
that?

I also tried again running nvidia-xconfig as root and editing
/etc/X11/xorg.conf

When I ran nvidia-xconfig, I got a message that there must be a driver
line, but when used gedit to edit /etc/X11/xorg.conf there was a driver
line and the word "nvidia". In addition, the section you told me to
delete in your first message was there:

Section "Files"
> > >
> > > RgbPath "/usr/X11R6/lib/X11/rgb"
> > > EndSection
>
> I deleted that section, and rebooted, and again got the black screen.
>
> What should I do now?
>
>

On Sat, 2008-09-27 at 08:27 +0000, Alberto Milone wrote:
> On Saturday 27 September 2008 01:02:29 Lynn Schock wrote:
> > Thank you for your Email. Before I received your Email, I changed from
> > the 64 bit version of Intrepid to the 32 bit version (upgrading from a
> > Hardy 32 bit install) thinking that might help the problem which it
> > didn't.
> > Now when I attempt to install (using Jockey) the nvidia-glx driver
> > (version 173) - the xserver does not load, the screen goes black, and
> > the monitor shuts off.
> >
> > Before I rebooted after using Jockey, I checked /etc/X11/xorg.conf using
> > gedit. The lines you refer to:
> >
> > > Section "Files"
> > >
> > > RgbPath "/usr/X11R6/lib/X11/rgb"
> > > EndSection
> > >
> > > are not there anymore so, of course I did not delete them.
> > >
> Ok, this time it must be a different problem then.
>
> >
> > Does Jockey also install fglrx-modaliases, and could that be the problem?
> >
> No, this is not a problem.
>
> > I know I don't know what to do. Any help that you could give would be
> > greatly appreciated.
>
> type:
> sudo sh nvidia-bug-report.sh
>
> and attach the nvidia-bug-report.log which you will find in the same directory
> in which you typed the command.
>

[Alberto Milone (albertomilone)]

Sorry, the correct command is:
sudo nvidia-bug-report.sh

[Lynn Schock (schocklynn)]

I have attached the nvidia-bug-report that I made today. I created this report after repairing the xserver,and rebooting, but it looks like it pertains to driver 173. I hope this reveals whatever problem I have.
Thanks for your help.

[Alberto Milone (albertomilone)]

I can't see the problem in the log.

Can you reproduce the problem (i.e. the black screen) and type sudo nvidia-bug-report.sh again, please?

[Lynn Schock (schocklynn)]

I have attached a new nvidia-bug-report that I created from the tty in recovery mode after getting the black screen in normal booting. This report was created before using recovery mode to repair and reconfigure the xserver. I hope this shows the problem.

[Alberto Milone (albertomilone)]

Unfortunately the log stops at this point:
(II) LoadModule: "glx"

(II) Loading /usr/lib/xorg/modules/extensions//libglx.so

which is too early to see what failed.

Let's try this:

Set the driver to "nvidia" in the Device section of your /etc/X11/xorg.conf.

Press CTRL+ALT+F1 so as to get to the command line and type:
sudo /etc/init.d/gdm stop (or "kdm stop" if you use Kubuntu)

Then type:
sudo startx -- -logverbose 5

let the Xserver fail and type:
cp /var/log/Xorg.0.log /home/your_user_name/
cp /var/log/Xorg.0.log.old /home/your_user_name/

NOTE: replace your_user_name with your user name

Reconfigure the Xserver by either setting the driver to "nv" in your xorg.conf or by letting Failsafe mode reconfigure X for you.

Then attach the Xorg.0.log and Xorg.0.log.old files which you will find in your home folder.

[Lynn Schock (schocklynn)]

I tried following your instructions but: after typing sudo startx -- -logverbose 5, the server didn't fail. Instead the desktop switched to a new user with the default desktop background and a new panel, and I no longer had the command line.

Also, just so I understand, the first thing I did was use gedit to change the /etc/X11/xorg.conf. I changed the device identifier from "configured device" to" nvidia" in the Device Section was that correct? Next, from the command line I typed sudo /etc/init.d/gdm stop, and then got confirmation that gnome was stopped. Then as I stated above after typing sudo startx -- -logverbose 5, Xserver did not fail, but instead the user was switched. What am I doing wrong?

[Alberto Milone (albertomilone)]

You should have changed the "driver" instead of the "identifier". If no driver was set in the Device section, as in the following example:

Section "Device"
 Identifier "Configured Video Device"
EndSection

you will have to add it manually as follows:

Section "Device"
 Identifier "Configured Video Device"
 Driver "nvidia"
EndSection

The rest of what you did is ok. Please repeat the operation and attach the new Xorg.0.log and Xorg.0.log.old files.

[Lynn Schock (schocklynn)]

I have attached the Xorg.0.log. No Xorg.0.log.old was created. I followed your instructions twice and each time only one log was created.

[Alberto Milone (albertomilone)]

I can't see the error in the log. Can you attach the output of this command?
sudo updatedb
locate nvidia.ko

[Lynn Schock (schocklynn)]

This is the output that I got:
lynn@lynn-desktop:~$ sudo updatedb
lynn@lynn-desktop:~$ locate nvidia.ko
/lib/modules/2.6.27-4-generic/updates/dkms/nvidia.ko
/lib/modules/2.6.27-5-generic/updates/dkms/nvidia.ko
/lib/modules/last-good-boot/updates/dkms/nvidia.ko
/var/lib/dkms/nvidia/173.14.12/2.6.27-4-generic/x86_64/module/nvidia.ko
/var/lib/dkms/nvidia/173.14.12/2.6.27-5-generic/x86_64/module/nvidia.ko
/var/lib/dkms/nvidia/173.14.12/build/.nvidia.ko.cmd
/var/lib/dkms/nvidia/173.14.12/build/nvidia.ko
lynn@lynn-desktop:~$

[Thomas Pifer (zero456)]

I'm also experiencing the same problems as Lynn with NVIDIA driver 173 on a GeForce FX 5500. It seems that the driver is also choking on Load "type1" in the Module section.

[Thomas Pifer (zero456)]

My last comment was rather vague so let me explain the whole situation:

I downloaded and installed a clean copy of Intrepid yesterday, after having what I perceived as problems with software after trying to upgrade from Hardy. Note that while I was having problems with some programs, I did not have any problems with the NVIDIA drivers, and they seemed to work as they did before the upgrade.

The clean install went smooth until I had to reboot after updating the system and installing the NVIDIA driver. It came to a black screen saying that there was an error with loading the NVIDIA driver. I then created a new configuration using the non-proprietary drivers in order to get back up and running. Thinking that it might have been a problem with the xorg.conf file, I opened a terminal and ran nvidia-xconfig (without sudo privileges by chance) and happened upon this error:

PARSE ERROR: Parse error on line 34 of section Module in file /etc/X11/xorg.conf.
             "Disable" is not a valid keyword in this section.

Clearly, something was wrong. I then opened up the xorg.conf file to see exactly what was going on. The file was sparse, and incomplete, withholding a lot of the information it normally contains. Seeing the problem, I then went through with the nvidia-xconfig and it seemed to write it proper.

I rebooted the machine only to see it error out again. This time, however, the error was different, complaining about the RgbPath line. I reconfigured the X server again, edited out the line and restarted. It came to balck screen once again this time (as my comment states above) complaining about the Load "type1" line in the Modules section. I removed this line as well, and rebooted once again. Another error came up stating that it could not find the nvidia module.

At this point, my guess would be that both the packages as well as the xorg.conf generated by dexconf are broken. I'm going to attempt to try this all one more time and, if unsuccessful, seeing if the driver from NVIDIA's website will have any better of an outcome. I'm attaching the broken NVIDIA configuration, the configuration generated by nvidia-xconfig, and the non-proprietary, xorg.conf.

[Alberto Milone (albertomilone)]

Lynn: the output of that command looks good. At this point I have no way to see what happens when the driver fails. Try asking here:
http://www.nvnews.net/vbulletin/forumdisplay.php?f=14

Thomas:
you experienced 2 well-known bugs in nvidia-xconfig:
1) It doesn't accept the fact that modules can be disabled (with "Disable")
2) It still insists on setting the RgbPath option which is no longer supported and makes the Xorg crash.

Try to reproduce the problem by setting the driver to "nvidia" again (in the "Device" section) without using nvidia-xconfig.

then attach your /var/log/Xorg.0.log and your /var/log/Xorg.0.log.old

[Thomas Pifer (zero456)]

Upon my last comment, I was actually able to get the driver working again by completely removing (including files from the apt cache) and using Hardware Drivers in the Administration menu to reinstall it. The instructions are as follows:

1. Open Synaptic in the System -> Administration menu.
2. Once in Synaptic, click the Search button (or press ctrl + f) and search for nvidia.
3. Next, right-click each of the following and select Completely Remove:
       nvidia-173-kernel-source
       nvidia-glx-173
       nvidia-settings
4. Click Apply to remove the packages.
5. Next open a Terminal from Applications -> Accessories and type:
       sudo apt-get clean
6. Press <Enter> and enter your password.
7. Finally, open Hardware Drivers in the System -> Administration menu
8. Select the driver you want to use and press the Activate button.
9. Once it's finished installing, reboot the machine and the driver should take effect.

For my own sake, I then used nvidia-xconfig to write a new xorg.conf file and edited out the lines that caused the driver to choke. This was unneeded, but made me feel better as the newer one was more thorough then the one created automatically.

Hopefully, this will work for you as well Lynn.

[Alberto Milone (albertomilone)]

Thomas: I'm glad to read that you solved your problem with Jockey (i.e. Hardware Drivers). Using nvidia-xconfig adds a lot of unneeded lines to your xorg.conf.

[Lynn Schock (schocklynn)]

Thomas:
Thanks for your suggestion, but that didn't work either. I am about ready to give up, especially since I know everything (acceleration, dual monitors, etc.) will work, because they all do on the Windows XP partition, and I have not updated the driver there since 2005. If I get ambitious, maybe I will try http://www.nvnews.net/vbulletin/forumdisplay.php?f=14, as Alberto suggested. Thanks to both of you for trying to help me, but it looks like I will be running with the generic driver for the time being.

[JinYoung (classpath)]

I have resolved this situation. Belows are the step. It's just all things that I did. To tell the truth, I don't know which step is necessary or unnecessary and what is right or wrong. However, I hope my experiences can help other users.

0. My laptop is Lenovo T61 with nvidia Quadro NVS 140 M
0. I updated from hardy to intrepid using "update-manager -d"
0. I encountered the error message that xorg server can't parse config file.
0. I restarted with default configuration and did some instructions that I found on the Internet, but they aren't work well.

1. Boot with Xorg server default configuration first.
2. Remove all things that are related with nvidia in the Synaptic.
3. Reboot again
4. Install nvidia-things except nvidia-xconfig package.
  nvidia-glx-177
  nvidia-*-modaliases
  nvidia-kernel
  nvidia-kernel-common
  nvidia-177-kernel-source
  nvidia-settings
5. Reboot again
6. Run sudo nvidia-xconfig.( It works well even though I didn't installed nvidia-xconfig package. I'm getting insane? :-) )
7. Restart X server. It works well now with nvidia driver 177.

[JinYoung (classpath)]

Oh.. I'll attach my current Xorg configuration file.

[JinYoung (classpath)]

Sorry. I forget comment the line "Load Type1" in xorg.conf file that I attached.

And there are one more problem. X works well when I boot my laptop with nvidia 177 driver and the xorg.conf file. However if I try logout, the screen goes to problem. After long time later that I pushed logout button, the Nvidia log was appeared 3 times and X report that it can't detect drivers. So I have to reboot my laptop.

This is driving me crazy. :-<

[JinYoung (classpath)]

I have downgraded nvidia driver to 173 from 177 via restrict driver manager(I use xfce4) . And everything works fine.

Logout, login, XDCMP, compiz, twinview(dual monitor : LCD + CRT), firefox, mplayer , etc are so good work. :-)

[Bryce Harrington (bryce)]

[This is an automated message]

Hi schocklynn,

Please attach the output of `lspci -vvnn` too.

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.