[Hardy] NVIDIA cards using vesa driver and low screen resolutions on livecd

Same error also here.

Geforce 7600 gs

In gutsy the resolution of the live-cd worked. In hardy I must use the xorg-tool to adjust the resolution to 1280x1024

I have the same problem with a 6xxx series card. Loading the restricted drivers manager fails (never appears) as does the crash report tool. I'll attach the X session errors file and Xorg.log.

The xsession errors contains a bunch of failures at the bottom seemingly related to me running the restricted driver manager. To clarify, I'm just running the live CD, not trying to install.

Booting the Live-CD my system works with Hardy Alpha 6 and generic driver this means no Nvidia proprietary.

After updating my Ubuntu 7.10 which worked with Nvidia drivers (not as well as it should but at least drivers have been recognized) to Hardy Alpha 6 on HDD; my configuration Monitor (Sony Multiscan G200) and my graphic adapter (Nvidia GeForce FX 5200) are not recognized. Only low resolution available.

When using the Nvidia GeForce FX 5200 without proprietary drivers it runs burning hot so you cannot touch it longer then 1 second. Is this normal? Or is my card damaged?

I just tried Hardy Alpha 6. I still get 800x600 by default but now the "Screens and Graphics" app. works and I can select the 'nv' driver and click Test and the test screen is correctly displayed and I can select my monitor manually as 1280x1024 and click Test and that also works. Looks like it's just the defaults that are not being correctly detected at startup.

Adding Driver "nv" to the device section of xorg.conf and Ctrl-Alt-Bksp did the trick and I'm now logged in to the live CD at 1280x1024 so it's definitely the autodetection.

That would mean that the driver does not list all pci-id's it supports. Could you run 'lscpi -nn |grep VGA' and post the results.

I'm in gutsy at the moment, waiting for big download to finish (will retry from the live CD itself in a little while). lspci -nn reports:
01:00.0 VGA compatible controller [0300]: nVidia Corporation G73 [GeForce 7600 GS] [10de:02e1] (rev a2)

Is it correct that the vesa driver doesn't support higher resolutions than 800x600 on this hardware (just wondering why gutsy live CDs work fine).

(Looks like I have a 7xxx series card after all.)

In Hardy it's the same (as expected):
01:00.0 VGA compatible controller [0300]: nVidia Corporation G73 [GeForce 7600 GS] [10de:02e1] (rev a2)

Same problem over here both in clean install and after upgrade from feisty.
Graphics card is Geforce FX5200 using hardy beta. I used the nvidia-glx-new driver on feisty all was working perfectly.
Going to try to add Driver "nv" to xorg.conf as mentioned by Shaun Crampton

I have the same problem. Also, after each boot, before my desktop appears, I get a message saying that GNOME could not start in high resolution, and the options to Configure, Continue, or Cancel. If I Configure, I am given a menu of what video card to choose, etc, but none works. The Plug 'N' Play is th default. I have tried to add Driver "nv" to the "Device" section in xorg.conf and restart X, but with no luck. In Feisty I was using nvidia-glx-new but now it seems I can't set my system to use it again. I use nVidia GeForce FX Go5650. Also, note that I upgraded from Feisty.

Thanks you.

* thank you

I am sorry, I meant I upgraded from Gutsy.

Same problem here.

On boot the Screens and Graphics screen does not show nvidia as an option (even after reselecting the nVidia proprietary driver and rebooting -- or after installing the nVidia driver via EnvyNG).

The nv driver can be selected off the Screens and Graphics menu, however, clicking on Test always fails.

When I boot, X fails and I get the low resolution error dialog. When I click on the Continue button, I end up in the GNOME desktop at 800x600. The Hardware Drivers screen shows the nVidia driver has the Enabled box checked and the Status shows a green light and says "In use".

When I run the NVIDIA Settings application, it says "You do not appear to be using the NVIDIA X driver..."

The Xorg.0.log file shows loading the nVidia driver successfully:
(II) NVIDIA GLX Module 169.12 Thu Feb 14 18:34:02 PST 2008
(II) Loading extension GLX

The only error message in the log file is the following:
(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)

I hope this helps.

Same problem using Hardy beta. X fails and displays the low resolution error dialog. Gnome starts in 800 x 600. I enable the Nvidia drive in hardware drivers and restart. X fails and displays the low resolution error dialog...

I have the Nvidia Quatro NVS 140m in a thinkpad R61. The Quatro NVS 140m is based on the GeForce 8400M G/GS. I used the update manager to upgrade from Gutsy to Hardy.

Please will you all post the output of the command "lspci -nn | grep VGA" as Timo requested of me. Perhaps your cards are missing from the supported list as well.

$ lspci -nn | grep VGA
01:00.0 VGA compatible controller [0300]: nVidia Corporation Quadro NVS 140M [10de:0429] (rev a1)

Shaun, your pci-id is missing from the driver, so that's easily fixed.

ehnar, could you check the Hardy beta livecd if it works for you now. If not, please show what 'lspci -nn |grep VGA' gives.

The Quadro issue is something else, and Tom, this bug certainly doesn't concern the proprietary driver.

Shaun, please attach the Xorg.0.log when you have specified the driver in the conf.

I have 01:00.0 VGA compatible controller [0300]: nVidia Corporation NV34 [GeForce FX 5200] [10de:0322] (rev a1).

Hardy beta1 boots up, flashes three times (beetween black screen and virtual terminal) and then starts X with the 'nv' driver.

My properly working gutsy upgraded to hardy does the same flashing, but only starts X with nv when I set the driver to it.

(On Hardy beta1 i mean the live cd.)

Please try the package from my ppa:

deb http://ppa.launchpad.net/tjaalton/ubuntu hardy main

..and don't specify nv in the conf.

Timo: it did the same for me as the original restricted driver (3 flashes).

Sorry, I have misunderstood you; my problem is solved. (I had booted the old kernel because I had two menu.lst files.)

Timo,

I'm afraid your new nv driver doesn't seem to have worked. I added your repo to sources.list and updated apt. Then I used "Force version" in Synaptic to force the xserver-xorg-video-nv package to use the one from your repo and applied the change. I hit Ctrl-Alt-Bksp to restart X but I still got a low resolution screen. I forgot to grab the X log while I ran on the live CD, but I did grep it for "nv" with no results.

Cheers,

-Shaun

I have the same problem. When I reboot, x server tries 3 times to start and then it switches to safe graphics mode (vesa, 800x600). When I hit "test" and manually select "nv" driver, it really works in test. However, when I continue, it somehow switches back to vesa.

If I configure xorg.conf to use "nv" and reboot, it works. But of course hardware acceleration don't work. So I suppose this problem to be related to nvidia driver.

Before today, I could overcome the unfortunate situation with switching to console (Ctrl+Alt+F1), turning GDM of (sudo /etc/init.d/gdm stop) and then running nvidia binary installer (sudo sh NVIDIA-Linux-x86-169.12-pkg1.run) and clicking "yes" to everything. After that, starting gdm did the trick (sudo gdm start), and hardware acceleration worked well. BUT, not anymore :(

I have tried to install every restricted/backport etc. package I can found for the kernel image, but no luck this far. (By doing this, I got my SB Audigy working)

(I have too upgraded from Gutsy.)

lspci -nn |grep VGA

02:00.0 VGA compatible controller [0300]: nVidia Corporation G70 [GeForce 7300 GT] [10de:0393] (rev a1)

Risto, you just seem to be missing the modules for the running kernel. Install linux-generic, which should pull in linux-restricted-modules etc for the current kernel.

I am having the same problems. I can enable the nvidia driver and set up my native resolution, but after a restart i get the black screen flashed 3 times and then the 600x800 resolution in the gdm and the vesa driver is selected. any help would be great. heres the output of lspci:

05:00.0 VGA compatible controller [0300]: nVidia Corporation NV43 [GeForce 6200] [10de:014f] (rev a2)

Timo, I think I had every single one of those installed and linux-generic as well.

But for me, latest updates have done the trick and *everything just works*!

Kernel is now 2.6.24-15

No, sorry. Everything seemed to work, nvidia-driver was loaded and nvidia-settings was fine. However, 3d-acceleration was not enabled so this bug is still not gone. Also, trying to start X again flickers 3 times and then switches to vesa&low resolution. So it was just a (partially) lucky boot.

At least stopping gdm and running nvidia binary installer works every now and then.

brian@brian-laptop:~$ lspci -nn | grep VGA
01:00.0 VGA compatible controller [0300]: nVidia Corporation NV31M [GeForce FX Go5600] [10de:031a] (rev a1)
brian@brian-laptop:~$

What works for me is the following:

sudo cp a 'working' xorg.conf (see example that worked for me attached)
then DO NOT REBOOT OR RESTART

instead

sudo dpkg-reconfigure -phigh xserver-xorg

This will backup your xorg and install a 'fresh' version like here:

# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc102"
 Option "XkbLayout" "us"
EndSection

Section "InputDevice"
 Identifier "Configured Mouse"
 Driver "mouse"
 Option "CorePointer"
 Option "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
 Identifier "Synaptics Touchpad"
 Driver "synaptics"
 Option "SendCoreEvents" "true"
 Option "Device" "/dev/psaux"
 Option "Protocol" "auto-dev"
 Option "HorizEdgeScroll" "0"
EndSection

Section "Device"
 Identifier "Configured Video Device"
EndSection

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
EndSection

Section "ServerLayout"
 Identifier "Default Layout"
 Screen "Default Screen"
 InputDevice "Synaptics Touchpad"
EndSection

Seems though that somehow the previous xorg content is saved somewhere because when I reboot it loads up fine.

Logically thinking, maybe just adding a single section into the 'fresh' xorg.conf, and running sudo dpkg-reconfigure -phigh xserver-xorg might also work, but haven't tried yet.

Won't solve the compiz problems though.. still can't activate effects here.

The original issue should be fixed, the nv driver package now lists all pci-id's it supports. Risto, your problem is with the nvidia binary blob. See linux-restricted-modules-2.6.24 bugs for a match or file a new one.

Loaded up live cd (Hardy release candidate) and encountered same or similar bug. screen resolution was 800x600 restricted drivers manager gave no option to use nvidia driver.

In a gutsy install my graphics hardware is detected as GeForce 6100 nForce 405, the gpu is integrated into the mainboard btw.

Gutsy did not have any problems dealing with this device and restricted drivers manager offered to install the nvidia driver.

Cheers,

Forgot to add the output from from lspci -nn | grep VGA (run from gutsy)

00:0d.0 VGA compatible controller [0300]: nVidia Corporation GeForce 6100 nForce 405 [10de:03d1] (rev a2)

Cheers,

This bug have gone for me after latest Hardy upgrades. Whether it was related to nvidia binary driver or proper detection fo my GF 7300gt, it is now completely gone and fixed.

Thanks.

upgraded from Gutsy to Hardy

01:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 8400M GS [10de:0427] (rev a1)

removed nvidia-glx-new
installed nvidia-glx
it works

Same problem here, I upgraded to hardy today.
Tried that last suggestion, did not work for me.
The nivdia driver does not load, I'm searching for 3 hours now.

Timo,

was the updated nv driver package included in the first official release on Thursday, or do we still need to update it ourselves? I ask because this bug persists on the official release I downloaded yesterday. Alternatively might the problem be something other than the unsupported pci-id's I'm a relative newbie so that might be a naive thing to say, if so I apologise in advance.

Seth,

Is your graphics hardware integrated on your motherboard or is it a seperate card? Again, I wouldn't really know if it makes any difference, just looking for similarities.

Hope it all gets sorted soon :-)

Cheers,

Oops, meant to direct that last question to Seth and Jean.

Sorry!

Not sure how relevant this might be to most of you but I also had the same problem. Installing the nvidia-glx-new driver or nvidia-glx driver and restarting crashed xorg and I had to either type "sudo dpkg-reconfigure -phigh xserver-xorg" in a virtual terminal or use bulletproof X to reconfigure the display for a different driver. By the way I have a nvidia 7100 graphics card.

I also had an issue with the hardy heron kernel 2.6.24.16 not detecting my wireless card (Aironet/Cisco 340) after a long delay of about 2 minutes in the booting process before finally starting the X session. A bug report and fix for this issue is filed under https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/173418 . The workaround there fixed my wireless connection issue perfectly well. I then installed nvidia-glx-new again, restarted my computer and managed to login as normal. I also managed to get compiz-fusion with full 3d effects working as well :).

As stated in the workaround, "I went in the /lib/modules/2.6.24-xxx/modules.alias and I commented out the first two occurrences of AES that link to padlock and geode hardware".

Now the issue seems to be the occurrences of AES that link to padlock and geode in the modules.alias file that stop the kernel from loading some device drivers.

 This worked for me, hope it works for everyone else.

oops, sorry, gave the wrong link to the other bug with the possible workaround I mentioned above. The link is given below.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/189398

Same problem. using Nvidia 7600 gt and Hardy

For those of you having problems with the nvidia restricted driver either crashing X or displaying a black screen with Ubuntu 8.04 use the latest nvidia beta driver found on the nvidia website it is version NVIDIA-Linux-x86-173.08-pkg1.run. I am running the Quadro NVS 140M on a Dell D830 and this fixed my problem. The driver can be found here http://www.nvidia.com/object/unix.html and then click on archive and find the 173.08 driver.

Here are the steps:
1. Purge the nvidia restricted package if installed by doing a "dpkg --purge nvidia-glx-new"
2. Kill the gdm server, "/etc/init.d/gdm stop"
3. Install the driver mentioned above.
4. start gdm server "/etc/init.d/gdm start"
When X starts you should now see the nvidia logo with the the words beta in red. If you don't edit you xorg.conf file and replace nv with nvidia and restart X.

Hope this helps someone!!

i had the same problem with 8800gts. I have kubuntu hardy heron and the only way to install driver is with envyng tool. The strange is that jocker-tool not recognize my card and that i need driver.

Avery Day! Thank you!
These steps:
Here are the steps:
1. Purge the nvidia restricted package if installed by doing a "dpkg --purge nvidia-glx-new"
2. Kill the gdm server, "/etc/init.d/gdm stop"
3. Install the driver mentioned above.
4. start gdm server "/etc/init.d/gdm start"
When X starts you should now see the nvidia logo with the the words beta in red. If you don't edit you xorg.conf file and replace nv with nvidia and restart X.
Helped me to fix the problem. I appreciate our help, hopefully everyone will try these steps to resolve the problem.

[Resolved]

Hi,

The problem I had (live CD not giving the option to use restricted nvidia driver) goes away after installation. This may help pin down what the problem is.

Cheers,

I would also like to add something else to my fix. After rebooting X will fail with the beta driver. I have no idea why but the only way I was able to fix this was to uninstall the nvidia-kernel-common package in addition to the nvidia-glx-new. So here is revision 2 of the work around.

1. Download the 173.08 nvidia beta driver here http://www.nvidia.com/object/unix.html click on archive and find the 173.08 driver.
2. Purge the nvidia restricted package and the nvidia-kernel-package if installed by doing a "dpkg --purge nvidia-glx-new nvidia-kernel-common"
3. Kill the gdm server, "/etc/init.d/gdm stop"
4. Install the driver downloaded in step 1, unless you are brave you need to let the nvidia installer modify the xorg.conf file.
5. start gdm server "/etc/init.d/gdm start"

Just to confirm the 173.08 fix seems pretty robust and seems to solve the issue that is made worse by twin monitors

Synaptic etc just pull the (buggy) released version)

Solution works with both twinview and separate x screeens

http://www.nvidia.com/object/linux_display_ia32_173.08.html

GX5500, LCD 1440 x 900 + 1024x768

Gary

http://www.theclearboxstore.co.uk

The 173.08 drivers change log says: Fixed a regression that caused invalid EDIDs to be detected for the internal display device on some notebooks. This confirms what the problem is for me. The 173.08 driver also has some other very important fixes and support for new video cards. I wonder how Ubuntu is going to address this one, its not that I am blaming Ubuntu but I am starting to see a lot of people reporting this problem and similar problems. Its a serous enough show stopper for some of us that it should be made official in some way with the Ubuntu developers. It would be nice if there was a nvidia-glx-new-beta driver in the repositories for situations like this. It just makes sense. Or at the very least an official how to on the Ubuntu website explaining how to properly install the nvidia's beta drivers. One of the advantages of having a nvidia-glx-new-beta package is the fact that when using the nvidia driver installer it hacks up the xorg.conf file and stomps on all of the hard work the Ubuntu installer did to correctly configure everything else. For example my synaptics touchpad configuration its now hosed since the nvidia driver installer updated the xorg.conf file for me.

> Could you run 'lscpi -nn |grep VGA' and post the results.

For nVidia GeForce 7100:

00:10.0 VGA compatible controller [0300]: nVidia Corporation Unknown device [10de:07e1] (rev a2)

I, too, was able to use Avery's workaround, but I would be happier to have a solution which didn't leave me with a video configuration outside the control of the package manager. In addition to that drawback, I now have a Ununtu login screen which doesn't know what the machine's resolution is, and as a result the username/password box is pushed way down to the lower right portion of the screen instead of the center where it's supposed to be, and the session configuration widgets aren't visible at all. Anyone know a fix for that side effect?

Finally, what's the process for getting a card into the database for PCI IDs? The 7100 has been around for a while.

> ... what's the process for getting a card into the database for PCI IDs?

I see that it's already in the upstream database, and I found the update-pciids command.

I also did some research and found that gdm decides what the screen resolution is be reading the first mode in the Display section of xorg.conf, and was able to fix the problem with the login screen by adjusting the order of the modes in that section so that gdm uses the correct resolution for the login screen.

So now if I could just find a way to get out of low resolution land without jumping outside the package manager's realm, life with Ubuntu would be perfect. :-)

I have an older NVIDIA card the GeForce4 MX 4000 and have exactly the same bug. However, when I get the NVIDIA driver (NVIDIA-Linux-x86_64-173.08-pkg2.run) it will not install as the card is too old and I can only use older (legacy) drivers.
Does anybody know how to solve this. Of course I find in my X11org.0.log file:
"Failed to initialize GLX extension (Compatible NVIDIA X driver not found)". But That is not the solution.
Is it possible not to load the glx-extensions or or are they necessary?
I hope somebody can help me out as I have just got a wide-screen 19" monitor and that's not nice with 800x600!.
Joep

Joep,

Read the second post down http://www.nvnews.net/vbulletin/showthread.php?s=49027174bcdd86c18631aaade1057d49&t=111460

Avery

Avery,
Thanks for the quick reply. In essence you say I have to disable glx.
I did that to comment out the Load "glx" line (put a # in column 1) but
apparently that did not the trick but I have to use the line Disable
"glx" in section Module.
 However, in my other Linux configuration (FC7 with vesa drivers) glx is
enabled: I give the relevant sections of xorg.conf:
Section "Module"
 Load "extmod"
 Load "glx"
 Load "dbe"
 Load "extmod"
EndSection

Section "Monitor"
 HorizSync 31.0 - 83.0
 VertRefresh 56.0 - 75.0
 Identifier "Monitor0"
 VendorName "Belinea"
 ModelName "1925 S1W"
 Option "UseEdidFreqs" "1"
# DisplaySize 426 270
 Option "dpms"
EndSection

Section "Device"

# Option "AddARGBGLXVisuals" "True"
 Identifier "Videocard0"
 Driver "vesa"
 VendorName "Xorganisation"
 BoardName "nVidia Corporation NV18 [GeForce4 MX 4000 AGP 8x]"
 Option "AddARGBGLXVisuals" "True"
EndSection

I use 'vesa" as the nvidia drivers doesn't work. (If I give as driver
"nvidia" my system will not start in graphic mode and gives a screen
hardware message saying "signal out of range" and I assume it is either
pixel clock or refresh rate that is out of range.
The problem I have now there is that my new wide screen
monitor-resolution 1440x900 will not work.
I assume that the old hardware (see boardname in section "Device") does
not know that resolution. Can you give me clues how to get that in the
board. I don't do games but use the highest resolution to give me enough
space on my screen (a.o. for audio editing with more than 12 channels).
Hope you can help me out.
Sorry for the lot of questions but I hope you can help me out.
Joep

On Wed, 2008-04-30 at 15:30 +0000, Avery Day wrote:
> Joep,
>
> Read the second post down
> http://www.nvnews.net/vbulletin/showthread.php?s=49027174bcdd86c18631aaade1057d49&t=111460
>
> Avery
>

Avery,
Sorry for the delay but I gave up and went back to FC7. Now I try again and administered the suggestion:Disable "glx". However, no result.
Are there other suggestions. I don't like to buy a new card.
By the way: under FC7 after some initial problems the nvidia driver (I don' know the version) works. I can do all I want.
Thanks in advance
Joep

Hi All,

I just ran into this bug as well in ubuntu 8.04

lspci -nn |grep VGA
01:05.0 VGA compatible controller [0300]: nVidia Corporation NV28GL [Quadro4 980 XGL] [10de:0288] (rev a1)

no amount of wrangling with nv, nvidia-glx, nvidia-glx-new, or nvidia-glx-legacy would convince the system not to load the "vesa" driver. In the end I worked around this by downloading the linux32 driver from nvidia after removing all nvidia packages but the kernel module (trying to remove nvidia-kernel-common yields a frightening series of suggestions from apt-get).

The driver I downloaded, that worked, was:

NVIDIA-Linux-x86-96.43.05-pkg1.run

Sam,
With my (old) GeForce4 MX 4000 board the X.org nv-driver works without a
problem. I even succeeded to adapt the modeline command in the xorg.conf
file to the resolution 0f 1440x900.
I have to try the (old) 96.43.05 nvidia driver but I first have to solve
another problem with U 8.04.
Joep

On Sat, 2008-05-10 at 06:50 +0000, Sam Stern wrote:
> Hi All,
>
> I just ran into this bug as well in ubuntu 8.04
>
> lspci -nn |grep VGA
> 01:05.0 VGA compatible controller [0300]: nVidia Corporation NV28GL [Quadro4 980 XGL] [10de:0288] (rev a1)
>
> no amount of wrangling with nv, nvidia-glx, nvidia-glx-new, or nvidia-
> glx-legacy would convince the system not to load the "vesa" driver. In
> the end I worked around this by downloading the linux32 driver from
> nvidia after removing all nvidia packages but the kernel module (trying
> to remove nvidia-kernel-common yields a frightening series of
> suggestions from apt-get).
>
> The driver I downloaded, that worked, was:
>
> NVIDIA-Linux-x86-96.43.05-pkg1.run
>

Joep,

I have not a clue, sorry!!

There is a better way than to uninstall the nvidia-kernel-common package and that is to blacklist the nv driver. I originally tried to do this in the "/etc/modprobe.d/blacklist" file but that failed hence the reason why I said to uninstall the nvidia-kernel-common package (I was in a hurry). The right way is to black list the nv driver in the "/etc/default/linux-restricted-modules-common" file.

Revision 3
1. Download the 173.08 nvidia beta driver here http://www.nvidia.com/object/unix.html click on archive and find the 173.08 driver.
2. Purge the nvidia restricted package if installed by doing a "dpkg --purge nvidia-glx-new"
3. Kill the gdm server, "/etc/init.d/gdm stop"
4. Install the driver downloaded in step 1, unless you are brave you need to let the nvidia installer modify the xorg.conf file.
5. Black list the nv driver in the "/etc/default/linux-restricted-modules-common" (should look like this DISABLED_MODULES="nv")
5. start gdm server "/etc/init.d/gdm start"

@Avery Day

your last solution worked for me. Running Kubuntu 8.04 with 7600GS. Installed the beta drivers right from the word "go" on a clean install, X would fail. The crucial part for me was to blacklist the "nv" driver.
Without blacklisting nv, I would get this:
API mismatch: the client has the version 173.08, but this kernel module has the version 71.86.04. Please make sure that this kernel module and all NVIDIA driver... etc etc

I agree with being able to install beta drivers from the repos, that would be nice.

Again,
I removed the nvidia drivers and manually updated xorg.conf to use the
Xorg "nv" driver. That worked for me. It even correctly interpretated
the modeline I entered.
I will try the nvida 96.43.05 driver later. A @Avery poited out this
driver doens't work with older cards (e.g. my GeForce4 MX 4000).
Joep

On Mon, 2008-05-12 at 10:18 +0000, Fungyo wrote:
> @Avery Day
>
> your last solution worked for me. Running Kubuntu 8.04 with 7600GS. Installed the beta drivers right from the word "go" on a clean install, X would fail. The crucial part for me was to blacklist the "nv" driver.
> Without blacklisting nv, I would get this:
> API mismatch: the client has the version 173.08, but this kernel module has the version 71.86.04. Please make sure that this kernel module and all NVIDIA driver... etc etc
>
> I agree with being able to install beta drivers from the repos, that
> would be nice.
>

>>>I have the same problem. When I reboot, x server tries 3 times to start and then it switches to safe graphics
>>>mode (vesa, 800x600). When I hit "test" and manually select "nv" driver, it really works in
>>>test. However, when I continue, it somehow switches back to vesa.
Same problem.

Black list the nv driver in the "/etc/default/linux-restricted-modules-common" and reinstall nvidia driver works for me

The same problem happen to me. I tried lots of reinstallation of the official and unofficial driver.
It's all my fault :) I wanted to build my own driver module ...
Finally, bored, I've done some hard cleaning :

sudo rm -f /lib/module/[currentkernel]/volatile/nvidia.ko
sudo rm -f /lib/module/[currentkernel]/volatile/nvidia_legacy.ko

CARE ! this solution worked for me cause my ubuntu didn't load the right module (nvidia rather than nvidia_new) but it's quite messy to remove the modules as I've done.
Maybe it's not the best solution but it worked...

Thanks to all,
It works, black listing "nv" is the "trick", after so many tries... I got compizfusion working (and the noisy fan silenced...)
Thanks again,
Fernando

My friends, maybe you could advice me on this issue. I followed these steps successfully, when Hardy came out.

1. Download the 173.08 nvidia beta driver here http://www.nvidia.com/object/unix.html click on archive and find the 173.08 driver.
2. Purge the nvidia restricted package and the nvidia-kernel-package if installed by doing a "dpkg --purge nvidia-glx-new nvidia-kernel-common"
3. Kill the gdm server, "/etc/init.d/gdm stop"
4. Install the driver downloaded in step 1, unless you are brave you need to let the nvidia installer modify the xorg.conf file.
5. start gdm server "/etc/init.d/gdm start"

I was using Ubuntu happily, till this black Friday, when I run the apt-get update. Update ruined my xorg cofig I guess. So I downloaded the latest driver and followed the steps provided by you in Revision 3 again.

The driver installed successfully, but now my resolution is limited to 640 x 480... . It feels very uncomfy... .

I suspect that the resolution is limited due to the incorrect monitor setting.

I'm using Nvidia 7600 gt with Samsung SynchMaster 17 inch.

I don't know much about configuration, but can follow the instructions patiently.

Could someone help me to troubleshoot the cause of this inconvenience, please.

Thank you in advance.

@Avery Day,
I don't know if it's too late to add a comment to this bug...
I have a problem now with 2.6.24-21-rt (#1 SMP PREEMPT RT) kernel and I have lspci -nn |grep VGA
01:00.0 VGA compatible controller [0300]: nVidia Corporation NV25GL [Quadro4 900 XGL] [10de:0258] (rev a3)
and it worked with available modules in Gustsy's repo good enough for me at the max. resolution my monitor allowed (old LG monitor with max. 1024X768 res).

Now with vesa that came with installation, is only 800X600 and cannot determine screen configuration, the restricted NVDIA driver works but only at 640X480 resolution, and envy install of same driver (96.43.05) yields a X server fatal error with no screen detected and module missing and I must fall back to vesa default via recovery mode. Also I typed in nv in device line in my /etc/X11/xorg.conf file and this yeilds in same 800X600 resolution and lower glx modes than I had in Gutsy.

I want to know if your advice on loading the restricted driver,

"Revision 3
1. Download the 173.08 nvidia beta driver here http://www.nvidia.com/object/unix.html click on archive and find the 173.08 driver.
2. Purge the nvidia restricted package if installed by doing a "dpkg --purge nvidia-glx-new"
3. Kill the gdm server, "/etc/init.d/gdm stop"
4. Install the driver downloaded in step 1, unless you are brave you need to let the nvidia installer modify the xorg.conf file.
5. Black list the nv driver in the "/etc/default/linux-restricted-modules-common" (should look like this DISABLED_MODULES="nv")
5. start gdm server "/etc/init.d/gdm start"

will likely solve my issue with Nvidia driver 96.43.07 as well, which is their latest driver for my card:

Version: 96.43.07
Operating System: Linux x86
Release Date: July 16, 2008

Release Highlights

    * Fixed a problem that caused TV output on secondary TVs to be black and white on some GPUs.
    * Improved nvidia-xconfig behavior when updating X configuration files without a "Module" section.
    * Restored compatibility with recent Linux 2.6 kernels.

was the "without a Module" the issue anyways or is it possibly as chef mentions,

"As stated in the workaround, "I went in the /lib/modules/2.6.24-xxx/modules.alias and I commented out the first two occurrences of AES that link to padlock and geode hardware".

Now the issue seems to be the occurrences of AES that link to padlock and geode in the modules.alias file that stop the kernel from loading some device drivers."

lastly, how do you get "Screens and Graphics" app.? Don't know what to install via Synaptic or Aptitude!
Tnks!

dragonfly schreef:
> @Avery Day,

>
I'm honored by your request but my name is not Avery Day and I did not
gave those answers.
I have an nvidia card (GEforce 4000) using ubuntu 8.04 (hardy) and the
nvidia drivers - finally - work OK.
I have had much problems with nvidia drivers (in Fedora as well as
Ubuntu) but most problems, in my case were caused by the drivers not
recognizing the monitor.
Hope somebody else can help you.
Joep