restricted nvidia driver fails after upgrade to kubuntu 8.04

[John Cottier]

Binary package hint: xorg

I am using an Nvidia Geforce2 MX400 on Kubuntu with Ubuntu metapackage installed too. Worked fine in Feisty and Gutsy.
I upgraded from Gutsy with the restricted driver removed. After, the screen looked slightly shifted to the left (start button), and found the card was was set to vesa. I discovered the "Hardware Drivers Manager" in the "System" menu and selected the restricted driver.
After a reboot I got dumped at the console. It complained displayconfig-gtk was not installed, so I apt-get to install. After another reboot I got a VGA screen with the displayconfig dialog. The dialog shows only vesa, and driver available "open source" and greyed out.
I can select the geforce2 card, but this seems to be ignored. Monitor is shown correctly, but Resolution allows 800x600 only. After a reboot it logged in with correct maximum resolution 1024x768, card vesa, driver nv, restricted driver has been deselected by the system.

I read about installing linux-restricted-modules-2.6.24-xx-386 manually so I did this and got different behavior. Now if I select resticted driver and reboot, I get the displayconfig dialog. It correctly detects the card, but not the monitor. So I select it manually, set the resolution and get dumped in the console. Reboot and its back the displayconfig but the card is vesa again.

I know you cant use dpkg reconfigure-xserver xorg any more, so thats me stuck!

Please let me know what info is required to track this bug.

[lspci]
00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
     Subsystem: nVidia Corporation C51 Host Bridge
03:00.0 VGA compatible controller: nVidia Corporation G72 [GeForce 7300 LE] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: Dell Unknown device 0405
[ 43.642895] pci 0000:00:00.0: Enabling HT MSI Mapping

[Pierre Hamm (pierre-hamm)]

Nearly the same happened after upgrading from Ubuntu7.10 ot8.04 the system worked only on 800x600,after manual configuration i got an unreadable screen.I installed a new nvidia driver with synaptic and activated him the dialog box said it works but the resolution was still low and compiz fusion didnt work.For the time you spent with this thank you. Pierre HAmm

[Richard Seguin (sectech)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please attach your X server configuration file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.0.log) to the bug report as individual uncompressed file attachments using the "Attachment:" box below. Could you please also try to run without any /etc/X11/xorg.conf and let Xorg autodetect your display and video card? Please also attach the /var/log/Xorg.0.log from this attempt. Thanks in advance.

[Richard Seguin (sectech)]

* Marking incomplete pending enough information to triage

[John Cottier (john-cottier)]

Hello Richard,
OK, I have attached those files. Shall I just rename xorg.conf as root and reboot for the test? Regards John Cottier.

[Richard Seguin (sectech)]

I would try renaming the xorg.conf file to something else (as you suggested) and let the system detect the card and monitor again. xorg.conf isn't a required file (usually it's quite empty) as of hardy so letting the system auto-configure the card might remedy the situation. Could you please report back what you find? By the way, is the main goal to use the restricted driver or the nv driver?

Thanks,

Richard Seguin

[John Cottier (john-cottier)]

The restricted driver is my goal, and of course to improve ubuntu/Kubuntu. I have tried the live CD first:- Booted ok, checked in System Settings... Monitor and Display, it had detected the geforce2 card, nv driver, monitor as only default plug and play, which causes a shift left making the Kicker menu invisible. I went into administrator mode and then the monitor was detected correctly. Maybe there is a permission issue there. Pressed Apply exited, logged off and selected restart X. This gave some console text and then seemed to stop responding. Had to Ctrl+Alt+Del to start shutdown.

Booting from the hardrive with xorg.conf renamed:-

This was similar. Checked in System Settings... Monitor and Display, it had detected the geforce2 card, nv driver, monitor as only default plug and play. Went into administrator mode and then the monitor was then detected correctly, but ALL the buttons are greyed out! Cannot apply the settings. Logged out and restarted X, no difference. Rebooted, and now the monitor is correctly detected. However going to System..Hardware Drivers Manager now shows an empty box.

In both cases there are no KDE login graphics either. You just get a blank blue screen for a few seconds, then its jumps straight into the desktop.

[John Cottier (john-cottier)]

After restoring the .generic kernel (see Bug #232019), the behavior has changed. The System..Hardware Drivers Manager now shows the restricted driver, and selecting it gives a warning explaining what it is. After this I am prompted to reboot. After reboot, the nv driver is still in operation. Even though the restricted driver is still shown as "In use" on the System..Hardware Drivers Manager.

[John Cottier (john-cottier)]

I have now experimented with three other ways to use then restricted driver:- Manually editing xorg to change nv driver to nvidia, running sudo nvidia-xconfig in a console, and running sudo apt-get purge nvidia-glx and then reselecting the restricted driver in the "hardware Drivers Manager".

In each case, after a reboot the results are the same:- Booting stops in console mode and auto-invokes the displayconfig dialog in "low resolution mode". The dialog has the "vesa" driver used, as it says no card could be detected. I can manually select "geforce2 DDR (generic)" from the list but only the OpenSource driver is available, the button for this is greyed out. Click OK and this takes me back to console login with no message as to what to do! But I now know from experience just to Ctrl+Alt+Del to restart. The reboot then logs in as normal with all setting correctly detected, but on the open driver. Also, if you press "Continue" in the displayconfig dialog, you are sent back to console login. sudo displayconfig says there is "no X server available" to run it! startx gives some error messages which says something like the Nvidia kernel module has a mismatch with the Nvidia driver and gives some different number for each. This has always worked before from Feisty through the upgrade to Gutsy, and pre-Ubuntu Linux.

The lack of a splash KDE was due to a missing mood..something plugin. So this plugin must be missing on the live CD too.

[Richard Seguin (sectech)]

Returning status to new as time restraints and not allowing me to complete triage

[John Cottier (john-cottier)]

After the latest (major) Ubuntu update, which included the kernel and restricted driver, it behaves slightly differently, but still does not work:- The only difference is the displayconfig dialog after a reboot. This now shows the card correctly detected, but still selects the vesa driver by default!. It no longer shows an "OpenSouce" selection, this part of the dialog has gone. After another reboot, its back to normal, and back on the nv driver, "hardware Drivers Manager" shows the restricted driver as "not in use" again.

[John Cottier (john-cottier)]

Can anyone help me with this please?

[Pierre Hamm (pierre-hamm)]

Sorry i couldnt do this before, xkb was also corrupted an i was not possible to type here is a sample of the files related to bug232012 i hope they help you to correct this.I thinkthere was an error during the upgrade this one has been broken two times.So iinstalled a new system it seems to work well.Friendly Hamm Pierre.

[John Cottier (john-cottier)]

I have tested again since the xorg update. But still no change.
I have also tried removing nvidia-glx and installing nvidia-glx_legacy, then setting xorg.conf to the "nvidia" driver. This works, but sadly does not have GLX extensions enabled, so not much use :-(
On my Gutsy machine at work, which uses GeForce 7300 card, Gutsy has a bug which loaded the glx instead of glx_new (which was buggy anyway, so cant use 3D on that machine without lockups!). So I tried this as some users have said that Geforce2 MX400 cards should use the legacy driver, although ubuntu documenation says nvidia-glx is the correct module. I have no idea what else to try, but this nvidia-glx stuff is a mess and really needs sorting.

[John Cottier (john-cottier)]

another big update, now on kernel 2.6.24-19-generic. No change, still not working.

[Sebastian (blub)]

I'm using ubuntu 8.04 and I have the same issue.
I then stopped the gdm from the console and tried to manually start the server with startx and there was a error message that said that there was a api mismatch between the driver and the module.
It wasn't in the log file so I had to pipe it in another file.
I have a GeForce Go 7300 card.

[Alberto Milone (albertomilone)]

The API mismatch happens when the version of nvidia-glx- doesn't match the one of the kernel module. Please follow these steps:

Install envyng-core:
sudo apt-get install envyng-core

then type:
envyng -t

select 1 and follow the instructions.

Let me know how it goes.

[Alberto Milone (albertomilone)]

This problem might happen at random, therefore it is difficult to reproduce and impossible to fix without DKMS.

[John Cottier (john-cottier)]

Hello Alberto,

Thanks for your reply.
I am reluctant to use envy as this breaks the ubuntu update system, and I have heard of people who have had the xserver broken irretrievably after installing envy. Besides I really think ubuntu need to fix this without relying on 3rd party helper applications. What is DKMS ?

[Alberto Milone (albertomilone)]

John: I'm the new maintainer of the NVIDIA driver in Ubuntu. EnvyNG was created in order to solve the problems which affected Envy (not that it could really break the xserver irretrievably...). It is the way in which we'll keep the drivers updated in Ubuntu. In Intrepid the packages will use DKMS by default.

Here you can find a definition of DKMS:
http://linux.dell.com/projects.shtml

[John Cottier (john-cottier)]

Hello Alberto,

I have followed your instructions. I used option 1 to install the nvidia driver. It completed ok and asked to re-boot which I did. Sadly the behavior is still the same. IE It lands in the console, invokes the "low resolution mode" dialog, showing the correctly detected monitor, but just a default VESA card. Then when you select the actual card, the system then appears to detect the card correctly, but only offers open-source drivers (optio greyed out). I select OK, then reboot.

If there are any files or debugging procedures you want me to do, please let me know. I dont know if this is a regression bug, or an update issue really, but without a clean install I cannot tell as the live CD will not allow the install of the glx nvidia driver.

[John Cottier (john-cottier)]

Another update, now on the generic ..19 kernel. Behavior almost the same. When the jockey dialog appears, it correctly detects the card, but still selects vesa driver. I manually select geforce2 generic DDR. I have attached the dump from envyng console output.

[John Cottier (john-cottier)]

Hello, Has there been any progress on this problem please?

[Richard Seguin (sectech)]

Not as of yet... I have had to step away from triaging bugs for a while, but I will be looking at this issue again shortly. Just so we can catch up, have you applied all of the updates and tried testing this problem again?

Thanks,

Richard Seguin

[eylander (john-eylander)]

It appears to me that I am having the exact same problem with Ubuntu 7.10. I have a GeForce 8800 GT video card with 512 mb RAM. I've tried to install/reinstall NVIDIA-GLX-NEW several times, have downloaded the latest drivers from NVIDIA (latest try with 173.14.09), and every time I reboot the darn system it comes back up with a window stating that it is either going to start in low graphics mode or I can select the video drivers. Further, i can't seem to find the video drivers I just installed in the menu. I've tried removing (renaming) xorg.conf to something else, and that doesn't work.

Something else I've notice...If I try to select a driver during the boot up process (vs. just allowing the system to use the generic VESA driver), the driver that loads still appears to be the generic VESA driver. I say this because after the system loads and I log into X, I go up to System->administration->screen and graphics to check which video card loaded, and it always says generic VESA driver. It would seem to me that even if I loaded the Nvidia Legacy driver during the boot up process, the screen and graphics GUI should state that is the driver that is loaded.

Thanks for any help you can provide. I'd like to get my nice 22" widescreen monitor set up with a better resolution then 800X600.

John Eylander

[John Cottier (john-cottier)]

Hello Richard,

Yes, if you look at the bug history you will see I have re-tested each time the kernel, nvidia related files have been updated.
Also, Alberto Milone informs me that he has taken over as nvidia driver maintainer, so after any envyng updates I have retested also. No change so far, and no further response from Alberto.

Also I have today updated my work PC to Kubuntu 8.4.1 (3D has been broken with Gutsy update on this PC) and this now has exactly the same problem. This is on a totally different PC and nVidia card (Dell E520 and GeForce 7300) so this is by no means an isolated case. I wish dpkg-reconfigure xserver-xorg still worked for video config.

On my work PC I was also left with only VGA only resolution selection on my 22" 1680 x 1050 monitor. I selected a generic 1680 x 1050 monitor from the Monitor & display configuration in System settings to correct this, but my resolution at KDM logon is still wrong.

I have almost forgotten what 3D looks like now its been that long since I have been able to use it on either PC!

[John Cottier (john-cottier)]

Apparently this bug is due to "expire in 56 days". Well thats one way to get rid of a bug I guess, thanks a lot guys :-(

[oss_test_launchpad (oss-test-launchpad)]

I have commented on this general problem in https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/248730, with no result.

[Alberto Milone (albertomilone)]

John: please set the driver to "nvidia" in the Device section of your xorg.conf, restart the Xserver, let it crash or let it enter failsafe mode and yype:
sudo /usr/bin/nvidia-bug-report.sh

and in the same directory as the one from which you type the command you will find an nvidia-bug-report.log. Please attach it.

[eylander (john-eylander)]

The attached message contains private information from Creighton University. To protect the contents of this message it has been encrypted. To view the message follow these simple directions.
1. Open the attachment labeled securemessage.html.
2. You must register to decrypt this message and future messages from Creighton University. Choose a password to continue the registration process.
3. Follow the steps requested of you during the remainder of the registration process.
4. Once you have completed the registration process, choose the “read your message” button, enter your password, and view your message.

If you have any questions about this message, please contact <email address hidden>.

Thanks,
Creighton University Mail Administrator

----------------------------------------

[John Cottier (john-cottier)]

Hello eyelander: Why the encryption? I cannot open it anyway.

[John Cottier (john-cottier)]

Alberto: Thanks for your reply, I have attached the log here. I will do the same with my Dell when I get to work tomorrow and post that here too.

[eylander (john-eylander)]

The attached message contains private information from Creighton University. To protect the contents of this message it has been encrypted. To view the message follow these simple directions.
1. Open the attachment labeled securemessage.html.
2. You must register to decrypt this message and future messages from Creighton University. Choose a password to continue the registration process.
3. Follow the steps requested of you during the remainder of the registration process.
4. Once you have completed the registration process, choose the “read your message” button, enter your password, and view your message.

If you have any questions about this message, please contact <email address hidden>.

Thanks,
Creighton University Mail Administrator

----------------------------------------

[eylander (john-eylander)]

I don't know why the Creighton server encrypted the email. I thought is was something on your end that did that (I received a CC copy of the encrypted email too), but I guess not. I'll resend in a separate email.

John Eylander

-----Original Message-----
From: <email address hidden> on behalf of John Cottier
Sent: Wed 9/17/2008 10:38 AM
To: Eylander, BJ
Subject: [Bug 232012] Re: restricted nvidia driver fails after upgrade tokubuntu 8.04

Hello eyelander: Why the encryption? I cannot open it anyway.

--
restricted nvidia driver fails after upgrade to kubuntu 8.04
https://bugs.launchpad.net/bugs/232012
You received this bug notification because you are a direct subscriber
of the bug.

Status in "linux-restricted-modules-2.6.24" source package in Ubuntu: Incomplete

Bug description:
Binary package hint: xorg

I am using an Nvidia Geforce2 MX400 on Kubuntu with Ubuntu metapackage installed too. Worked fine in Feisty and Gutsy.
I upgraded from Gutsy with the restricted driver removed. After, the screen looked slightly shifted to the left (start button), and found the card was was set to vesa. I discovered the "Hardware Drivers Manager" in the "System" menu and selected the restricted driver.
After a reboot I got dumped at the console. It complained displayconfig-gtk was not installed, so I apt-get to install. After another reboot I got a VGA screen with the displayconfig dialog. The dialog shows only vesa, and driver available "open source" and greyed out.
I can select the geforce2 card, but this seems to be ignored. Monitor is shown correctly, but Resolution allows 800x600 only. After a reboot it logged in with correct maximum resolution 1024x768, card vesa, driver nv, restricted driver has been deselected by the system.

I read about installing linux-restricted-modules-2.6.24-xx-386 manually so I did this and got different behavior. Now if I select resticted driver and reboot, I get the displayconfig dialog. It correctly detects the card, but not the monitor. So I select it manually, set the resolution and get dumped in the console. Reboot and its back the displayconfig but the card is vesa again.

I know you cant use dpkg reconfigure-xserver xorg any more, so thats me stuck!

Please let me know what info is required to track this bug.

[John Cottier (john-cottier)]

Here is the log from my work PC which is: Dell E521, AMD64 dual core + GeForce 7300 LE Kubuntu Hardy 32 bit

[John Cottier (john-cottier)]

any progress on this? Is this likely to be fixed in Intrepid?

[Alberto Milone (albertomilone)]

John: this shouldn't be a problem in Intrepid any more.

[John Cottier (john-cottier)]

Alberto, according to the Intrepid release notes:-

"Users with the nVidia TNT, TNT2, TNT Ultra, GeForce, GeForce2, GeForce3, and GeForce4 chipsets are affected and will be transitioned on upgrade to the free nv driver instead. This driver does not support 3D acceleration. "

Does this mean I am now stuffed forever for 3D drivers on my graphic card with Ubuntu?

[Alberto Milone (albertomilone)]

John: not forever, only until NVIDIA releases new legacy drivers compatible with the new X.org.

[John Cottier (john-cottier)]

Alberto: Does that mean this will be fixed in a future Ubuntu release?, or as soon as nvidia fix it (and its tested) ?

[oss_test_launchpad (oss-test-launchpad)]

Is this fixed for Ubuntu 8.10?

[John Cottier (john-cottier)]

It would appear not. Its still on the release notes. Whether it will be fixed in 8.10 later is another issue. It seems unlikely though. On my work PC, that had an nvidia binary driver bug in Gusty, and after 3 months we where informed it would not be fixed until Hardy due to QA procedure. But then Hardy had another bug! which stopped binary drivers working, and now Intrepid has yet another issue with some binary drivers!

It is really sad and frustrating and its seems never ending, yet the 3D desktop is still a main marketing point for Ubuntu, and pictures of it shown on the Ubuntu and Kubuntu sites for the adverts. My kids are not happy either (no tux racer, flight gear etc) but what can you do?

[Alberto Milone (albertomilone)]

John: I have replied to you question in this blog post (which in turn has links to another bug report): http://albertomilone.com/wordpress/?p=292

As regards your complaint, I can only say that we have very little control over binary drivers. The same is not true for open source drivers (e.g. intel, ati, etc.).

[John Cottier (john-cottier)]

Hello Alberto,

Thanks, I noticed your comments on that bug ref later and posted your comments on bin-false.org as some are rushing to install via the nvidia script.

Can you confirm the procedure for the -proposed, presumably you have to enable "proposed updates" in adept..Manage repositories..updates. What other action is necessary? or what commands are used in the console to achieve this?

Regarding ATI, the situation to me is just not clear. At https://wiki.ubuntu.com/HardwareSupportComponentsVideoCardsAti some ATI cards seem to need binary drivers for 3D too, and there is no information beyond Feisty. So there is no clear way a user can select a card to buy that he knows is going to work/have 3D support via open source or proprietary drivers. I think more accurate information on graphic cards and drivers need to be made publicly available and maybe this might help the graphic card makers to see the benefit of open source collaboration. How about graphic card support league table!

[Alberto Milone (albertomilone)]

John:
As regards -proposed, have a look at this page: https://wiki.ubuntu.com/Testing/EnableProposed

That wiki page is slightly obsolete and definitely needs an update.

[gary (grcrosby)]

Ibid, I just did a clean install of Ubuntu 8.04 from Kubuntu 7.04 & the nvidia drivers simply lock up the screen after log in. I have found no errors in the log files, but the system is so stuck that the only option is to hit the reset button on the box. K-7.04 was good & stable on the restricted drivers. At this rate I will simply go back to the earlier release & lurk around waiting to see if someone can come up with a fix for this problem, which is not the ideal situation.

BTW, the video card is a nvidia GeForce 2 MX/MX400 agp board.

[John Cottier (john-cottier)]

I have tried to install the nvidia driver, via the NVIDIA script "The hard way" (see attached), but this too has failed.
The /etc/default/linux-restriced-modules-common, and /etc/modules file settings seem to be ignored by ubuntu. The NVIDIA script ran without errors, but after restarting KDM, I just got the same jockey "Low resolution" dialog. The xorg.conf has been reverted to the "nv" driver, but running lsmod does not show the nv or nvidia modules at all so it seems the whole video sytem is a mystery nowadays.

I guess this info is out of date too, as it seems any community information I can find is. The line about rm /lib/linux-restricted-modules/.nvidia* is clearly wrong in my case, as this folder contains subfolders for all current and older kernels.

It seems I am up against a brick wall with this.
Does anybody have any up to date information on how to get nvidia drivers to work?

[John Cottier (j-cottier)]

I tried an upgrade to 8.10, but this borked (got stuck) and so I decided to reformat the root (left the home partition as is) and do fresh install of ubuntu 8.10 and then later added the kubuntu-desktop meta package.

This was pretty flawless, after all the updates ubuntu offered the restricted driver automagically, and 3D seemed to worked fine (happy kids!). However if you select desktop effects, then the title bar vanishes from any dialog. Also in Kubuntu with its desktop effects turned on, it prevents any 3D applications from running (you just get a black screen) although I have read that the applications maybe running but verrrry slowly. Also wine dialogs / fonts are unreadable. All these appear to be Nvidia bugs related to the new driver EG https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-96/+bug/300476

Its a great shame that nothing is being done to resolve upgrade to Hardy problems though, especially as Hardy is LTS (Long Time [bug] Suffering?)

[John Cottier (j-cottier)]

This bug still an issue on my work PC which is a Dell E521, AMD64 dual core + GeForce 7300 LE Kubuntu Hardy 32

After recent updates, I can now select the NVIDIA driver in Hardware Drivers Manager (jockey-kde) but it still dumps me into the low resolution mode screen after restart. However I can now manually select the restricted driver, and set the correct resolution and widescreen mode for the monitor (Dell 22" LCD widescreen) which was not available before. But it still gets rejected and dumps me back to the low resolution screen. Only the nv driver works.

However I have managed to get the NVIDIA driver working on a live CD (although I had to edit the xorg.conf by hand), so I know the system works, its my upgrade that has broken something. Is there anything I can check, any permissions on root folders that are critical for the video system. Can I delete and get the system to restore any file or folders to re-initialize the video driver sub system? any ideas?

[John Mckenna (jfmckenna)]

John Cottier,

I was having issues with my MX400 card as well and solved them with information on this web site:

http://www.ubuntugeek.com/common-problems-and-solutions-for-nvidia-restricted-drivers-after-ubuntu-810-intrepid-ibex-upgrade.html

Good luck and hope that helps, I know how frustrating it is ;)

[John Cottier (j-cottier)]

@John Mckenna

Thanks for the info. Actually I have my MX400 working now, I reformatted the root partition and installed intrepid (on my home PC). Its just my work PC that is stuck now. That has a GeForce 7300, and it works from the live CD, so I know its the upgrade that has borked it. I am sure there must be a way to delete and re-install key video related folders to force the video system to become like a fresh install, but I lack the knowledge. But it does not seem as though this bug is getting any attention sadly, so I guess I am stuck with it.

[NoOp (glgxg)]

I am also having issues with nvidia drivers in Ubuntu 8.04.2 (Gnome) with 2.6.24-24-386. Everything works well using 2.6.24-24-generic.

*-display
                description: VGA compatible controller
                product: NV25GL [Quadro4 900 XGL]
                vendor: nVidia Corporation
                physical id: 0
                bus info: pci@0000:01:00.0
                version: a3
                width: 32 bits
                clock: 66MHz
                capabilities: pm agp agp-2.0 vga_controller bus_master cap_list
                configuration: driver=nvidia latency=248 maxlatency=1 mingnt=5 module=nvidia

I loaded the -386 yesterday in order to enable ltmodem and found myself in vesa mode. Attached are the xorg logs for both -386 and -generic, and my -generic xorg.conf. Hopefully they will help the maintainer figure out the issue as it is vital that an LTS release be able to use the card properly.

[NoOp (glgxg)]

This xorg.conf works without issue in -generic. However it does not in -386 as nvidia drivers are not being loaded. I have also (in -386) booted in recovery mode & tried xfix, moved xorg.conf out of the way - doesn't work. Additionally, jocky-gtk does not offer the option to load the nvidia driver in -386 mode.

For the nvidia maintainer: this issue is not random and is repeatable on my system. Let me know if you need any additional information.

For the issue originator (John): I realize that my system is Gnome & my card is not the same model as yours, however I'm hoping that the added information from my system will help find a solution overall.

[earthforce_1 (earthforce1)]

I just got bitten with my 8.04 system with nvidia drivers on dual side by side syncMaster 2443 displays as soon as I installed kernel 2.6.24-24-generic. Came up in low res mode, couldn't detect display. Works fine when I go back to 2.6.24-23-generic. The NVIDIA X Server Settings window shows the following:

NVidia driver: 169.12
X Server Version Number 11.0
Server Vendor String 11.0
Server Vendor String The X.Org Foundation
Server Vendor Version 1.4.0.90 (10400090)

NV-Control Version 1.14
---- Graphics card information ---------
Grpahics Processor: G92-200
VBIOS Version 62.92.52.00.90
Memory 512 MB
Bus Type: PCI Express 16x
Bus ID: 1:0:0
IRQ: 16
X Screens: Screen 0
Display Devices: Samsung SyncMaster (DFP-1)
                           Samsung SyncMaster (DFP-2)

[Bryce Harrington (bryce)]

Thank you for reporting this issue about a driver from the
linux-restricted-modules package. lrm-2.4.24 was shipped with Ubuntu
8.04 which reached end-of-life for desktop support on May 12th, 2011.

For that reason, this bug report is being closed at this time. I'm
marking it wontfix because what you describe is probably a valid issue,
but there are no plans to work on lrm 2.4.24 bugs further.

The issue may be resolved in a newer version. If not, aside from filing
a new bug report, another angle may be to file it directly with the
driver vendor.