MASTER: Request for new-legacy nvidia drivers (9631)

[Joseph Price]

http://us.download.nvidia.com/XFree86/Linux-x86/1.0-9755/README/appendix-a.html

The above link shows the large list of cards which were dropped after 96**

I believe it is extremely important that users are able to install 9755, 9631 or 7184 depending on their card. 96** will still allow a large amount of users to use 3D acceleration including desktop-effects without having to resort to 7184 with inferior performance & features.

[BjornarBerg (ssamik)]

I second that! I have had good performance with 9631, but now i'm back to using 7184 witch really suck. Wont even let me have a working tv-out connection. Tried installing 9631 from nvidia.com, but it failed.

[mikkael (mikkael)]

same here, it seems it is not possible to install 9631 manually from nvidia.com running the latest kernel 2.6.20-13.

[Joseph Price (pricechild)]

I'm marking this confirmed as people are having this issue.

[Kaarel (kaarelk1989-deactivatedaccount)]

+1

[PurpleSkunk (purple-skunk)]

Same here with a GeForce4 420 Go 32MB (rev a3) (NV17 Chipset) on a Toshiba Satellite S2450-S203 laptop.

[clooch (clooch3)]

After using an old xorg.conf (renamed). I was ablo to re-install the 9631 driver from NVIDIA.
I am not sure if the xorg.conf had anything to do with the failure to begin with, but I am up and running. well at least for the moment.

[clooch (clooch3)]

I need to apologize I just rebooted and lost it all.
I reinstalled tnd started x without reboot and it works fine.

I will fall into the background now. and follow the progress.

cheers

[cement_head (andorjkiss)]

This is a SERIOUS bug and renders my machine useless with Ubuntu as I cannot used twinview to do powerpoint presentations.

PLEASE FIX IMMEDIATELY such that the old (9631) drivers can be used with the new kernel.

[Lambros Lambrou (lambros)]

I'm afraid I've also been bitten by this "upgrade". I have a 3-year-old GeForce4 Ti 4200 card, and I've just found out nVidia have dropped support for this card in their latest drivers. After installing the latest feisty updates, the X server would not start.

In the Xorg log file, there was a message hinting that I needed to install the legacy drivers. So I did "sudo apt-get install nvidia-glx-legacy" and rebooted. That gave me a working X server. But I then found that 3D-accelerated apps would not run (some problem with finding GLX visuals). After looking through the logs and doing some online research, I found a solution: I added this line to the "Device" section of my /etc/X11/xorg.conf :

Option "AllowGLXWithComposite" "true"

Hope this information is helpful to somebody.

[adipl (diplaros)]

I also have and a GeForce4 420 Go 32MB and it is a pitty not to be able to use the correct driver for it.

[Adam Michael Roach (adammichaelroach)]

The Restricted Drivers Manager needs to correctly identify the GeForce MX420/440 cards and earlier and download the new-legacy 9631 drivers and not the new beta 9755 drivers. This is especially important as a huge number of laptops run these cards.

[Thomas Hotz (thotz-deactivatedaccount)]

I can completely agree with you. This is a _critical_ problem now.

From the nvidia discussion forums I see that even the nvidia developers say the people need the new-legacy driver http://www.nvnews.net/vbulletin/showthread.php?s=831d494234fe422b64802d71220170ab&t=88724

Here is the announcement: http://www.nvnews.net/vbulletin/showthread.php?t=81668

I still do not understand why we can't upload a new-legacy driver. This would solve many problems and our users can get the hardware support they need (or with other words they had until after Ubuntu Beta).

[Kai Springer (kai-nuknetz)]

The update this morning installed the 9755 nvidia driver for my graphics adapter (01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev a1). X-server crashed, telling me that my GPU wasn't supported and it tried probing on without any GPU, which of course didn't work. After disabling the driver I logged into the gdm and compiz had all window borders and panels flashing and I had to disable it manually via metacity --replace.

Sorry, for a complete noob this would have meant to replace ubuntu with windows. Why can't you simply go back to kernel -12 with the 9631 driver? By the way the 9755 driver doesn't work with kernel -12 either.

[jtlb (jt-lb)]

I have the same problem and when I tried to use the old one instead it crashed xorg!
I have a TNT 2 Riva 64, i know it's old but usefull.
I DO NOT want to compile it myself: The last time it crashed X.

[Suzan (suzan72)]

Go back to 9631 is a bad idea, because the new nVidia cards (8000) only work with the new 9755 driver. So updating was the right decision.

The problem is, that now 3 trees of nvidia-drivers are available:

97xx - for newer cards (at the moment in nvidia-glx)
96xx - for cards in the "middleage" (no driver available in ubuntu)
71xx - for "historic" cards (at the moment in nvidia-legacy-glx). This driver provides 3d but no support for compiz/beryl.

So the developers have to maintain 3 versions of nvidia-drivers. More work to do. Nevertheless I hope, that all 3 versions will be provided with Ubuntu.

[Soul-Sing (soulzing)]

Suzan wrote:
> Go back to 9631 is a bad idea, because the new nVidia cards (8000) only
> work with the new 9755 driver. So updating was the right decision.
>
> The problem is, that now 3 trees of nvidia-drivers are available:
>
> 97xx - for newer cards (at the moment in nvidia-glx)
> 96xx - for cards in the "middleage" (no driver available in ubuntu)
> 71xx - for "historic" cards (at the moment in nvidia-legacy-glx). This driver provides 3d but no support for compiz/beryl.
>
> So the developers have to maintain 3 versions of nvidia-drivers. More
> work to do. Nevertheless I hope, that all 3 versions will be provided
> with Ubuntu.
>
>
i agree, there were so many complaints on the dutch forum.

[Soul-Sing (soulzing)]

this is no longer a medium problem. critical i would suggest!

[greenhunter (tierfreunde-hagenburg)]

It is CRITICAL.

This bug makes my system nearly useless. Can't work with my external monitor and no gaming.

The extrem fan activity comming with very slow Xorg 7.2 is getting on my nerves. With the external monitor I was at least able to put the annoying notebook under the tabel. Now I have to put the computer in front of me.

Please drop all efforts with those "desktops effects". Give us *please* a *fast* , *quiet* and *working* system back.

[Kai Springer (kai-nuknetz)]

Yes I fully agree to the degree that a solution to the "3 drivers problem" makes the thing critical. My system now is useless and needs to be reinstalled because I even can't log into terminal anymore. I do not agree that those desktop effects might be useless. They worked for me great and I'd appreciate to have them back.

[Johan Kiviniemi (ion)]

As the PCI ID lists in the nVidia READMEs tend to be incomplete, attached is a complete list of PCI IDs supported by the three drivers.

The hex number after the 'v' matches the vendor ID and the number after the 'd' matches the device ID. In the list, the module name 'nvidia' stands for the 97xx driver, 'nvidia_96' stands for the 96xx driver and 'nvidia_71' stands for the 71xx driver (the current 'legacy').

[greenhunter (tierfreunde-hagenburg)]

I didn't mean that the desktop effects are useless and should be dropped at all. Just deffered till 7.10. But there are only 4 weeks left untill the final comes out and they effects are truly non essential, compered to this problem here and the sluggy xorg.

Of course I'd like effects on my screen back, too.

[rasz (citizenr)]

I posted first in
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/96941

so again :
LARGE ( http://steampowered.com/status/survey.html just look at Steam statistics, there are ton of GF3-GF4 users, ~5-10%, and those are ppl playing games =have huge incentive to upgrade, and here we got ppl who often chose linux NOT to upgrade the computer) percentage of nvidia users have NO WAY to pick the correct (9631) driver , there are only two, legacy 7xxx (for TNT and first Geforce) and 97xx (for FX and never cards).

I propose something like nvidia-glx-lesslegacy , because 9631 is somewhere in between 7xxx and 97xx

anyway I downgraded to -12 kernel and nvidia-glx_1.0.9631

for all the ppl out there , just do

rasz@capek:~$ ls -l /var/cache/apt/archives/ |grep 963
-rw-r--r-- 1 root root 4491620 2007-03-15 23:03 nvidia-glx_1.0.9631+2.6.20.3-11.10_i386.deb
-rw-r--r-- 1 root root 4491624 2007-03-18 20:03 nvidia-glx_1.0.9631+2.6.20.3-12.11_i386.deb

if you have the correct kernel-old driver pair just install them with sudo dpkg -i and wait for Ubuntu to make the middle range driver available.

[rasz (citizenr)]

WOW, I just realized we are not talking GF2-GF3 here, we are talking GF2-FX, that is like 30-40% of ALL Ubuntu Nvidia users
+1 for CRITICAL

[Wolfgang Silbermayr (silwol)]

Renders system completely usable for me too... Lucky that I know how to get things running again. For a newbie this is a catastrophy if video cards that are not too old (like my three-year-old GeForce4 Ti) suddenly can't be run without 3d acceleration.
+1 for CRITICAL from me too.

[PurpleSkunk (purple-skunk)]

Yes, +1 for CRITICAL since this issue affects many users. It should be solved ASAP in my opinion.

[Ben Collins (ben-collins)]

We are investigating if we want to include these modules. The fact that nvidia is no longer planning to maintain the 9631 driver doesn't help the case. We have to contend with possible bugs, mainly security related issues.

Not only that we have to contend with making the driver work with our kernel. If nVidia isn't keeping the driver up-to-date, we are having to modify the build ourselves to make it compile. We already had to do this with 9631. It will only mean more problems in the future as the kernel API changes. Additional work for maintenance.

For those that suggest this is a critical bug, it is not. A critical bug makes the system completely unusable (read the definition of severity levels on the Ubuntu wiki). Ubuntu's stock nv driver supports all of these chiosets. It boots and works as expected. The nvidia driver is supplied for those wanting the vendor supported drivers to get acceleration with their hw. We provide these as a courtesy, to make using Ubuntu easier for you, since we assume most people will want the drivers whether we provide them or not. We do no provide it because we have to, and if the the vendor drops support, we are at their mercy. If your card suddenly stops working, you can blame nVidia, not us.

That being said, we are looking at this from a completely technical aspect. How much work is it for us to include the 9631 driver blob compared to how much it helps users. Note that this isn't just a matter of putting it in. Once we commit to supporting it in feisty, we commit to supporting it over the life of feisty (1.5 years) and probably, much like the native driver, supporting it in later releases of Ubuntu.

The primary loss here is composite features for desktop effects and possibly some performance with GL applications (games). This is hardly a critical loss, but we realize that current trends warrant the use of such features. It is very likely we will include the 9631 for feisty, but the scope of it's inclusion and the existence of it past feisty is still up for debate.

[will_in_wi (will-in-wi)]

The nv driver will not allow any resolution over 640x480 on my GeForce4 MX Integrated with either my 19" or my 17" CRT. I might be able to fix this by looking up the specs for the monitor and manually setting it in the xorg.conf, but this is beyond the abilities of a normal user. I have always just installed the nvidia driver and it has worked perfectly. My point is that the nv driver has problems that are not easy to work around. This makes the nvidia driver critical for normal operation. Unless you are a geek who started with linux in RH6 and has used suse, gentoo, slackware and now ubuntu, and can compile your own kernel.

[Adam Michael Roach (adammichaelroach)]

The only problem I see with this is the restricted drivers manager. If indeed the 9631 driver will be included, the manager needs to detect it properly for the correct cards. On the other hand, in the case of say, my laptop with an mx440, the restricted drivers manager will give me an option to install the nvidia driver, which right now would be a false positive since the exclusion of the proper driver, essentially breaking X. If the proper driver is excluded, the restricted drivers manager needs to make the distinction and not provide the option to install the nvidia driver and stick with nv. I think the matter is more or less, how to deal with correct detection and installation than whether or not to include the driver officially.

[Ben Collins (ben-collins)]

will_in_wi: Your comment makes no sense. The nvidia-legacy driver supports your card just fine, minus some extended features. You'll get proper resolution and acceleration.

What most people don't understand is that the nvidia-legacy driver we have supports your cards. It just doesn't support use of desktop-effects (needs compositing found in 9631).

adammichaelroach: Your issue is already taken into account.

[Joseph Price (pricechild)]

In reply to Ben Colins:
"We are investigating if we want to include these modules. The fact that nvidia is no longer planning to maintain the 9631 driver doesn't help the case. We have to contend with possible bugs, mainly security related issues."

The following is a quote from http://us.download.nvidia.com/XFree86/Linux-x86/1.0-9755/README/appendix-a.html
"Below are the legacy GPUs that are no longer supported in the unified driver. These GPUs will continue to be maintained through the special legacy NVIDIA GPU driver releases."

This implies that the 9631 driver _will_ be maintained in the same fashion as the 7184 legacy driver.

That said, thankyou for the explanation on the other problems with maintaining this set. You've been a lot more verbose than other people I've spoken to and have explained and backed up with reasons :)

With the email on -devel mentioning it might be able to fix the broken upgrades issue I'm happier.

Pricey

[K.Mandla (k.mandla)]

I have a Geforce4 440 Go and even the 96xx drivers don't work for me, regardless of what Nvidia says. There's a patch that allows the 8776 driver to be built against the 2.6.19 & 2.6.20 kernels, which is the route I plan to go for as long as it lasts me. I would heartily recommend it for 420/440/460 owners (and perhaps Geforce4 owners on the whole), particularly if they want to make the jump to Feisty. I know, it's not ideal, but it's better than the nv driver.

[Ben Collins (ben-collins)]

> The following is a quote from http://us.download.nvidia.com/XFree86/Linux-x86/1.0-9755/README/appendix-a.html
"Below are the legacy GPUs that are no longer supported in the unified driver. These GPUs will continue to be maintained through the special legacy NVIDIA GPU driver releases."
> This implies that the 9631 driver _will_ be maintained in the same fashion as the 7184 legacy driver.

No it doesn't. It means the 7xxx (currently 7184) driver that we already include (the nvidia-legacy-glx packages) support it. 9631 is done. Updates to it come in the form of updates to the latest driver, currently 9755. The only driver that nvidia currently supports for these cards is 7184, since they dropped support in 9755.

So if you just want support, we already have it. If you want composite, you'll need to wait for the implementation in lrm to include 9631 support.

[David Thulson (davidthulson)]

This thread makes it appear that they are releasing 96xx series drivers as "legacy" drivers:
http://www.nvnews.net/vbulletin/showthread.php?s=74a34b9834fb4572543ff4897cbec4b4&t=81668

Ben Collins, have you (or anyone else) actually talked to nvidia about what they are planning or are we all just taking shots in the dark?

[birdflesh (birdflesh)]

Ben Collins: Many other linux distributions already offer solutions to this matter.

[cement_head (andorjkiss)]

Hi All,

The 9631 driver provides far greater flexibility for twinview setup, such as needed for OO Impress (Powerpoint) presentations - a major application of a laptop in a professional environment...and the reason I use GNU/Linux. It is posssible to do this by manually editing the xorg.conf file, but given the great interface that nvidia designed for choosing screens and resolutions, even I have to admit it's inconvenient to go back to the old method.

I agree with BenCollins that the OpenGL issue for games is a secondary one, as well as the compiz/beryl effects. However, if Ubuntu wishes to claim "It Just Works", then these issues clearly need to be addressed. I sympathise that this is probably THE worst possible time for this to occur (4 weeks prior to launch) but it shouldn't be too hard to put this explanation into the Restricted Drivers Manager.

As to the post by anti_pop about not being able to run the 9631 drivers with the new 2.6.20-13-generic kernel; I'm running it right now. tselliot has many very good guides on installing the nvidia drivers manually. All that is required is to compile the driver and build the nvidia kernel modules. Please see this post on the ubuntu forums:

http://ubuntuforums.org/showthread.php?t=393875

Again, this is a solution for a Feisty Fawn tester, or an experienced user, but not the type of experience we want a newbie, or first time linux user to encounter. Will there be a policy decision on this? It seems very unfortunate that this might slip through the cracks.

- cement_head

[Joel Oliver (joelol75)]

I was bitten by this bug and have been beating my head against the wall over possibly another bug. I downgraded my 2.6.20-13 kernel to 2.6.20-12-lowlatency (With the kernel headers to match). apt-get remove --purge nvidia-glx cleared the restricted modules.

Well to make a long story short I reinstalled the older 9631 nvidia-glx package and older restricted-modules. Then attempted to reistall the drivers from nvidias website. No go... Why not?

Tried deleting everything nvidia wise and reinstall to no avail. Finally I tried the 2.6.20-12-generic and reinstalled again and everything works. So the 2.6.20-12-lowlatency kernel or kernel headers must be borked somehow.

[Ralf Hildebrandt (ralf-hildebrandt)]

Same here, todays upgrade installed an nvidia driver & kernel module that don't support my
nVidia Corporation NV17 [GeForce4 420 Go 32M]
So I went back to use the nvidia-legacy package. Unfortunately the driver included with this doesn't support my card properly, I get a garbled screen.
So I fell back to using the "nv" driver. Which seems to work ok, except for the fact that X sometime will hog the CPU and needs to be killed with SIGKILL.
Extremely annoying.
We need multiple nvidia-olegacy packages!

[giuseppe (bepp88)]

My gf4 mx440 card has the same problem...It doesn't work with neither 97** drivers nor with the legacy one. It's no long time I use linux and I'm not able at all to solve the problem, now i stay with the nv drivers without 3d and composite. Hoping in something better...

[Timo Aaltonen (tjaalton)]

David: I fail to see how that "thread" (release announcement from December) makes it look like that version will be supported in the future..

Birdflesh: what distributions are you referring to?

[birdflesh (birdflesh)]

Timo Aaltonen:
Arch Linux for example:
http://archlinux.org/packages/search/?repo=all&category=x11&q=nvidia

[Miłosz Kosobucki (mikom)]

Nvidia is probably going to support 96xx line same way ax 71xx. If they weren't going to support it they would probably write 9631, not 96xx. It wouldn't be wise to support people with very old cards and left the ones with much newer hardware.
I think that indeed we need three packages for nvidia drivers.

[Arthur Peters (amp)]

Sorry to add more traffic on this bug, but I think I have something to add that no one has said.

Perhaps a Multiverse package could contain the 96xx drivers until it has been established whether they will be supported by NVidia?

That way Ubuntu does not have to worry about supporting the drivers and they would be available without much hassle to those of us who need it (enabling multiverse is easy). If there could be a plug in restricted-manager that would allow it to enable the 96xx driver once they were installed from Multiverse that would be nice. But regardless, "aptitude install ...; nvidia-glx-config enable" is a lot easier than the NVidia installer.

Also, once it becomes clear whether NVidia will be supporting the drivers it will be easy to either move them Restricted or not depending.

Just a thought for a compromise.
-Arthur

[David Thulson (davidthulson)]

Timo Aaltonen (and Ben Collins I suppose), if nothing else the 9631 drivers are 4 months newer than the 7184 series. Here's another good post by an nvidia employee where he mentions the 71xx "legacy branch" and a 96xx "legacy branch":
http://www.nvnews.net/vbulletin/showpost.php?p=1208356&postcount=2

I read that as saying it'll be at least as well supported as the 71xx series. I'll ask this again though: have you actually confirmed anything with nvidia or are we all (still) just making guesses?

If you don't think nvidia will support the 96xx series like they have the 71xx series, I guess I can't do anything about it. However, I agree with cement_head. You can't claim that this "just works" or that it makes life easy for non-power users.

[Olivier (olidel)]

Hello,

     I guess what you are looking for is here :
http://www.nvnews.net/vbulletin/showthread.php?t=81668. I think this link
give a good overview with all the stickies post
http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14.

Hope this help.

Thanks.

O.D.

2007/3/28, Timo Aaltonen <email address hidden>:
>
> David: I fail to see how that "thread" (release announcement from
> December) makes it look like that version will be supported in the
> future..
>
> Birdflesh: what distributions are you referring to?
>
> --
> MASTER: Request for new-legacy nvidia drivers (9631)
> https://launchpad.net/bugs/96430
>

[David Thulson (davidthulson)]

I went ahead and asked nvidia:
http://www.nvnews.net/vbulletin/showthread.php?t=88867

They are supporting the 96xx series just like the 71xx series.

[Lucas Goss (lgoss007-gmail)]

Confirmed?

http://www.nvnews.net/vbulletin/showthread.php?t=88867

Never assume, get the facts. These are critical for my use of Ubuntu!

[rasz (citizenr)]

netllama - NVIDIA Corporation:
"I'm not aware of anyone representing Ubuntu contacting NVIDIA to get an official statement on driver support, so I'm not sure why they think that anything is unsupported. Please have them email <email address hidden>.

Neither the 1.0-71xx nor the 1.0-96xx legacy driver branches have been abandoned, nor are they unsupported. They are both legacy driver branches which will receive critical bug fixes and Linux kernel & Xorg compatibility updates as needed. This has been the policy for 1.0-71xx legacy for quite some time, and no one from Ubuntu voiced any concerns to NVIDIA."

yep, sure sounds like they are abandoning 96xx driver ...
/sarcasm
PS: Good work on contacting Nvidia Ben Collins ...

[Ben Collins (ben-collins)]

I had a nice long rant for here, but I'll skip it.

A) We already said we'd include the drivers for feisty. There's no further need for complaining. No one else needs to comment to this bug report. You will get 9631 drivers before feisty releases.

B) This is proprietary software. We have no control over what the vendor does. We do our best, but these are the breaks. If you don't like this sort of thing happening, complain to nVidia, not us. We didn't decide to drop support for the chipsets in question. We just provided the latest two drivers that nVidia had available on their web site (7184 and 9755). If they had posted links to three drivers, we'd have provided that from the beginning.

There really is nothing more to say.

[PurpleSkunk (purple-skunk)]

Thanks for clarification from both parts.

Ben Collins wrote:
We just provided the latest two drivers that nVidia had available on their web site (7184 and 9755). If they had posted links to three drivers, we'd have provided that from the beginning.

If that is true (and I trust you), I am going to complain to nVidia for sure.Ubuntu deserves its reputation.

[Adam Michael Roach (adammichaelroach)]

Ben:

: A) We already said we'd include the drivers for feisty.

Actually it was only stated that it was "very likely."

: B) This is proprietary software. We have no control over what the vendor does. We do our best, but these are the breaks. If you don't like this sort of thing happening, complain to nVidia, not us. We didn't decide to drop support for the chipsets in question.

I don't think anyone is complaining here, just concerned. I think when the decision is made to include a solution to have desktop effects, etc, in conjunction with proprietary drivers, there will be many concerns, especially when there are a lot of users of the proprietary product involved. I think it would be easier to explain exactly what is happening with this situation instead of being defensive; no one blames Ubuntu here. I would like to add that it is very nice to hear that the 96xx drivers are going to be included.

: We just provided the latest two drivers that nVidia had available on their web site (7184 and 9755). If they had posted links to three drivers, we'd have provided that from the beginning.

http://www.nvidia.com/object/linux_display_archive.html

: There really is nothing more to say.

[Ben Collins (ben-collins)]

> : We just provided the latest two drivers that nVidia had available on
> their web site (7184 and 9755). If they had posted links to three
> drivers, we'd have provided that from the beginning.
>
> http://www.nvidia.com/object/linux_display_archive.html

So we should distribute all 38 driver versions from that page? Or just
the two from the direct download page at:

http://www.nvidia.com/object/unix.html

Which is what you get when you go to "Download Drivers" and select
"Linux, FreeBSD, and Solaris Drivers".

What this is akin to is me uploading a 2.6.20-14 kernel which no longer
supports VIA Epia CPU's (wont happen, this is hypothetical). You
complain, and I tell you 2.6.20-13 supports your CPU. I can give you a
link to it (launchpad will retain it in archive), and you can still
download it, but would that really be what you want?

Now, edgy works for you, and feisty doesn't. I can argue that edgy will
be maintained for 1.5 years, and we'll guarantee security updates for
it. Our website confirms this, and you can easily see that in fact we
support "edgy" for your cpu, and not "feisty".

In this example, feisty latest would be considered the 9755 driver, the
2.6.20-13 kernel+feisty would be considered the 9631 driver (if you want
feisty on your Epia, you need that kernel and not the latest kernel),
and edgy would be considered the 7134 driver (works, but doesn't have
all the bling).

Can you understand my issue with this now?

[adas (adziura)]

I have the same problem (GF2). I wanted a 96xx because one program (run in wine) required this drivers...

[Joseph Price (pricechild)]

I fired off an email to nvidia to clear up a few things and here's the good news:

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

Joseph,
Thanks for writing. I believe that its my nvnews post that you've
referenced below.

Both the 1.0-71xx and 1.0-96xx legacy branches will continue to be
supported for critical bug fixes, and future Linux kernel & Xorg
compatibility updates.

We're aware that 1.0-96xx is not clearly labeled as a legacy branch here
and are taking steps to correct that:
http://www.nvidia.com/object/unix.html

However, 1.0-9631 remains available via the Archive links on that same
webpage.

Please let me know if you have further questions or concerns.

thanks,
Lonni J Friedman
NVIDIA Corporation

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

Thanks to Ben for the news that 9631 will be in Feisty! :)

[rasz (citizenr)]

>Thanks to Ben for the news that 9631 will be in Feisty! :)

are you sure? his latest post
https://launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/96430/comments/51
 still argues with the 3 drivers in repos idea ..

[Felix Rabe (public-felixrabe)]

rasz wrote:
>> Thanks to Ben for the news that 9631 will be in Feisty! :)
>
> are you sure? his latest post
> https://launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/96430/comments/51
> still argues with the 3 drivers in repos idea ..
>

That's actually not his latest comment on the issue - I erased my inbox
though :/

[eppy 1 (choppy121212)]

I'm sorry, but Nouveau can't come soon enough.

Please Ubuntu, package Nouveau as soon as it's even halfway usable. Hopefully by the end of this year...it'll be a long wait I know, but I'm sick of Nvidia's games.

http://nouveau.freedesktop.org/

[Adam Wood (adamwood)]

I just marked bug 97332 as a duplicate of this one.

For anyone interested, I was able to make my GeForce4 card work by booting with the 2.6.20-12-generic kernel and related restricted-modules. I then manually installed (dpkg -i nvidia.*9631.deb) and now I'm back to a working desktop with good speed. I found the driver cached in /var/cache/apt/archive (i think).

You can still download the nvidia drivers from here.
http://www.nvidia.com/object/linux_display_ia32_1.0-9631.html

I understand Feisty is still in Beta and maybe that's why this problem happened, but it might show a problem with the package approval process before it is pushed into the repos. Nvidia didn't hide which chips were not going to be supported and I'd like to know (without placing any blame) who was responsible for checking the driver before committing it?

Lastly, has anyone from Ubuntu tried asking Nvidia to speed up release of the newer legacy package?

[Adam Wood (adamwood)]

In response to this post by Ben Collins:
https://launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/96430/comments/51

==quote==
Can you understand my issue with this now?
========

No, not really. I don't understand the issue.

I'm confused as to where the number for 38 driver versions comes from?

http://us.download.nvidia.com/XFree86/Linux-x86/1.0-9755/README/appendix-a.html
The web page linked above shows that Nvidia considers there to be 3 distinct groups of cards. Those currently being directly supported, those supported by the 96xx series and those supported by the 71xx series. In order for Ubuntu to support the full range of Nvidia cards there must be 3 nvidia drivers. Not 38.

My personal opinion is that:
1) nvidia-glx-legacy needs to be renamed nvidia-glx-legacy-71xx.
2) The 9631 driver packaged as nvidia-glx-legacy-96xx.
3) the nvidia-glx package continues to follow progress on the development series driver.
4) nvidia-glx-legacy-* needs to follow and update as and when nvidia update their legacy drivers.

When the argument arises "What do we do when Nvidia release another series of drivers?" Which is possibly what Ben was worried about. The, "Is this ever going to end?" problem. The only real answer is, no probably not, but that's life. We are at the mercy of proprietary drivers. I'm just grateful there isn't a different driver for every single card!

Perhaps, by the time nvidia downgrade another series of cards to legacy status there will be so few cards supported by the 71xx drivers that Feisty+6 can drop them and still only have 3 packages to maintain.

To say that Feisty will support the 71xx and most recent drivers whilst excluding some in the middle is a very strange choice. Numbers of users affected by dropping the 71xx over the 96xx must surely be lower. Although, I don't see any reason to drop either.

[Joseph Price (pricechild)]

Adam Wood:
> Lastly, has anyone from Ubuntu tried asking Nvidia to speed up release of the newer legacy package?

Please see my latest comment:
https://beta.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/96430/comments/53

They're going to sort it out :)

Adam I think its best we drop it now despite what "was" said... BenC has now promised that all three will be in Feisty which we can't thank him enough for.

[belze (belzebu87)]

Mine GeForce MX 440 is not working correctly with nvidia driver, I must use "nv" parameter in xorg.conf
I hope troubles with 9631 driver will be soon solved, as is written above. Thank you all for your work!

[zeddock (zeddock)]

I am a linux newb but I want out of MS for myself and all of my users. We have a fleet af Dell Latitude D800 laptops that use nvidia nv28, GeForce4 Ti 4200 with AGP8X, cards.

Currently, feisty beta with updates is not handling this well. What is the best course of action for me to take?

I will need to get 3d accell and desktop effects working.

Thanx!

[belze (belzebu87)]

Hi, I'm the user who lesft the message in launchpad Nvidia's bug just
before you. I suggest you to wait the final release of feisty, I think
for that time our problems will be solved, and we don't have to wait
so long.
Davide.

[jdriessen (j-driessen)]

add me to the users affected list...

I also need 96xx drivers for my Geforce4 420 Go 32MB...

[monstrous (monstrous-deactivatedaccount)]

My graphics card: NVIDIA GeForce 4 Ti 4200 with AGP8x

I solved the problem the same way as Lambros Lambrou did: Install nvidia-glx-legacy and add >>Option "AllowGLXWithComposite" "true"<< to the device-section in /etc/X11/xorg.conf.

[R Morrison (rmorrisonva)]

i say its critical... i mean c'mon the nv driver is junk... it looks awful versus the "digital vibrance" and other features in the nvidia driver... and this affects so many nvidia users... why ship a product with crippled support for many mobile users.. non-sense.
- Richard

[R Morrison (rmorrisonva)]

nevermind... sorry for outdated comment

[James (james-ellis-gmail)]

Hi

I've read through all the comments on this bug so won't add anything more other than to say it did effect my laptop running a Geforce4 4200 Go negatively when i went along and installed the latest nvidia-glx in Feisty Beta

A point I would like to make that is not covered here is why was I allowed to install a driver that did not support my card?
Would it not be better to maybe have the nvidia-glx installation procedure test whether or not the GPU installed is actually supported before people head down the path of a non functioning X server? Nvidia provides a Device PCI ID that could be t ested against : 0x0286 in my case (http://us.download.nvidia.com/XFree86/Linux-x86/1.0-9755/README/appendix-a.html)

I'm thinking something along the lines of "Incompatible driver found. This driver does not support your graphics card". Or maybe automatically attempt to load nv instead if nvidia fails? at least I could then boot to my desktop.

That would save a lot of:
* rebooting after upgrade
* x bleating about screens not being found (after a nice long view of the kubuntu logo and some finger tapping).
* Switching to another run level to find what the hell happened
* downgrading to nvidia-glx-legacy
* rebooting
* finding twinview no longer works
* reading the nvidia docs
* not being able to find the nvidia-glx 96xx package in the repos (is there an easy way to downgrade using just the apt repos?)
* dkpg -i /var/cache/apt/...nvidia-glx...-96xx to downgrade (luckily it was still in the cache) along with restricted modules etc
* booting into the previous kernel version
-- to get a working desktop 3 hours later

Is this really what we want *buntu to be doing in 2007 ?

- can a non tech savvy user do the above? no
- does windows do this better? yes

[Loïc Martin (loic-martin3)]

James,

However upset you might be, remember you're using a *DEVELOPMENT* version.

I don't think your last 2 questions are worth being posted to this site, so the answers might not. However, for reference:

- can a non tech savvy user do the above?
If they can't they shouldn't be using a development version - whether they are tech savvy or not is irrelevant here.

- does windows do this better?
You must be better informed than me then. I have never installed any development version of any Windows OS yet. However I *do* remember some painful Windows installations that (pick the following):
- erased the booting sequence (grub)
- refused to start and even access any command line to try to fix it
- booted in 640x480 16 color mode
- showed a garbled screen after updating nvidia drivers...
and I save you other headaches (the worse always happen after *it*'s properly installed.

Bottom line, please pay attention to the *development* *alpha* *beta* warnings if you can't cope with some *development* *alpha* *beta* problems.

[David Thulson (davidthulson)]

We are using a development version to test it and provide feedback to the Ubuntu team. While some of these comments may not be constructive, isn't the whole point of releasing public betas to have this discussion now with a few testers rather than later when it causes problems for many more people? I think James has a good idea to have a single nvidia-glx package that includes all 3 driver versions and uses the correct version automatically. Perhaps it is not feasible for Feisty at this point (or maybe even at all, I don't know), but I'd say it's worth considering.

Feisty is scheduled to be released in 15 days, and I still don't see any sign of the 96xx driver in the repos. I'm sure we would all like to make sure it gets tested before Feisty is released. When can we expect to see it in the repos?

[monstrous (monstrous-deactivatedaccount)]

@David Thulson
Maybe we have a chance to test it in the release candidate. It's scheduled to 05/12/07.

[zeddock (zeddock)]

If too much time passes before we get the 96xx legacy driver into the repos, there will not be a reasonable amount of time to beta it. I do not know how the repositories work exactly but I am wondering if someone can create a repository which could be added to a user's list of repos so the we could test it right away. Can this be done?

zeddock

[fimbulvetr (fimbulvetr)]

I'd like to see this in Feisty too, are there any processes we can use to heighten awareness to higher ups so they know what's going on?

[zeddock (zeddock)]

Well, this is the process Dan V. I think since the problem has been assigned to the Ubuntu Kernel Team that it will get resolved. I just would like some more transparency into how it is going, which is why I ask for a repository to beta test the 96xx drivers.

zeddock

[Sam Cater (wraund-deactivatedaccount)]

I have been asked to inform everyone that this bug IS being worked on as we speak, and people can expect a fix soon.
There is no need to add more and more comments.

Thank you

[Soul-Sing (soulzing)]

sam, +1

[Jan (jan23)]

This related discussion has an instruction how to install the older driver manually. http://ubuntuforums.org/showthread.php?t=393748&page=4

[Ben Collins (ben-collins)]

The new lrm has 9631 back as the defauly nvidia-glx package set. There is now a new nvidia-glx-new package set for 9755. This was chosen because it offered the least surprise for upgrades. People who need (or want) the new 9755 driver should install nvidia-glx-new.

[zeddock (zeddock)]

Going to look right now! Thanx!

zeddock

[cement_head (andorjkiss)]

Thankyou to Mr. BenCollins and the entire Ubuntu Kernel Team

- CH

[zeddock (zeddock)]

I want to add "Thanx!" first...

I am still in limbo even after the fix. This may be a consequence of my being too new to know if *I* have hosed up something or the fix is missing the mark.

Please, tell me what to do to test this appropriately?

I have tried several ways but every time I install the nvidia-glx package the reboot leaves X unable to start. I then must go into xorg.conf and change from nvidia to nv to get back up in gui.

I am running a GeForce4 4200 Ti AGP8, also known as nv28. This is in my Dell Laptop.

I have looked under restricted manager and am unsure whether enabling the nvidia restricted drivers (for Desktop Effects,) installs the nvidia-glx-new or just the nvidia-glx. (I think it is the nvidia-glx.)

Of course when X won't start, and I change to "nv", the restricted manager, and Desktop Effects, complains that I must install the restricted drivers again!

I have also, tried to go back to square-one via the command-line in the top of the xorg.conf file, but that does not help either.

Suggestions?

Thanx!!

zeddock

[Tom Haddon (mthaddon)]

Zeddock, I had a similar problem because my kernel modules were the wrong version. Just do "sudo aptitude search nvidia". Anything that's marked as installed (with an "i" as the first column), uninstall it - sudo aptitude remove ... - this will prompt you to also uninstall restricted-modules (or at least it did for me) - just accept the defaults and uninstall it.

Once it's all uninstalled, reinstall nvidia-glx and you should be good to go.

[Albert Abril (abrilc)]

I have the same problem that Zaddock and Tom Haddon.

When I exec 'Restricted Drivers Managers' it tell me to install linux-restricted-modules-2.6.20-14-generic . This package seems not to be updated at the repositories yet.
For now I have linux-restricted-modules-2.6.20-12-generic, and I'm running a 2.6.20-14-generic kernel. Then the kernel versions are not the same.

I suposse that we had been awaiting for the new package. (Or maybe make a manual installation).

Thanks a lot for BenCollins and the entire Ubuntu Kernel Team for fix this bug.

[zeddock (zeddock)]

It seems to get the right driver, but when it is enabled, meaning "nvidia" replaces "nv" in the xorg.conf file, X bombs!

Code:

Error: API mismatch: the NVIDIA kernel module has the version 1.0-7184, but this X module has the version 1.0-9631

I have tried to go back to .13, and .12, but X will still not start.
I eventually must go into xorg.conf and change nvidia to nv.

zeddock

[Arthur Peters (amp)]

I had similar problems to the ones that other people are having. For me they were related to having installed the NVidia driver using the NVidia installer. I solved them by uninstalling using the Nvidia installer and then reinstalling the ubuntu packages (nvidia-glx, linux-restricted-modules-2.6.20-14-generic) and then unloading the nvidia driver (the wrong one had been loaded somehow. And a reboot would have worked too). So overall it looks like the below on console. It must be done from outside X or the module unload will fail.

$ sudo invoke-rc.d gdm stop
$ sudo bash NVIDIA-Linux-x86-1.0-9631-pkg1.run --uninstall
$ sudo aptitude reinstall linux-restricted-modules-2.6.20-14-generic nvidia-glx
$ sudo rmmod nvidia
$ sudo invoke-rc.d gdm start

I hope this helps someone.

-Arthur

[zeddock (zeddock)]

So, if I do a completely new installation it should work correctly?

zeddock

[Ori Avtalion (salty-horse)]

The nvidia-glx and nvidia-glx-new packages have too-similar descriptions:

glx: "supports (<--grammar error) the newer GeForce, nForce and Quadro families of NVIDIA chipsets."
glx-new: "support the newer GeForce, nForce and Quadro families of NVIDIA chipsets."

These should be updated a bit with more specifics.
The drivers that are in the newly-"legacied" group include the Geforce3 and some of the Geforce2 series card.
The description should be as informative as space allows - I'd rather not guess which driver is correct for me.

glx-new also has "If you have a GeForce4, you may need the nvidia-glx package."
each the three packages should suggest to look at the other two.

[zeddock (zeddock)]

I agree. But I have other problems too.

zeddock

[Albert Abril (abrilc)]

Hi Arthur. You said that had installed
linux-restricted-modules-2.6.20-14-generic.
This package isn't in my repositories, (and not in others that I tested).

Could you post here your sources.list please? I need this package with it's
dependencies. Thanks.

On 4/10/07, Arthur Peters <email address hidden> wrote:
>
> I had similar problems to the ones that other people are having. For me
> they were related to having installed the NVidia driver using the NVidia
> installer. I solved them by uninstalling using the Nvidia installer and
> then reinstalling the ubuntu packages (nvidia-glx, linux-restricted-
> modules-2.6.20-14-generic) and then unloading the nvidia driver (the
> wrong one had been loaded somehow. And a reboot would have worked too).
> So overall it looks like the below on console. It must be done from
> outside X or the module unload will fail.
>
> $ sudo invoke-rc.d gdm stop
> $ sudo bash NVIDIA-Linux-x86-1.0-9631-pkg1.run --uninstall
> $ sudo aptitude reinstall linux-restricted-modules-2.6.20-14-genericnvidia-glx
> $ sudo rmmod nvidia
> $ sudo invoke-rc.d gdm start
>
> I hope this helps someone.
>
> -Arthur
>
> --
> MASTER: Request for new-legacy nvidia drivers (9631)
> https://bugs.launchpad.net/bugs/96430
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Albert Abril (abrilc)]

Ok. Fixed. I had an error with my restricted repositories. Thanks anyway.

[Lambros Lambrou (lambros)]

All works fine for me now. Many thanks to Ben Collins and the rest of the Kernel team - you've done a great job in somewhat difficult circumstances! :-)

Lambros

[cement_head (andorjkiss)]

How do I get nvidia-glx to install the NVIDIA XServer Settings menu item under 'Applications>System Tools'?

[Jeff Balderson (jbalders)]

Confirmed working for me -- my bug was marked as one of the dupes of this one.

[mikkael (mikkael)]

cement_head:

you can do this easily in your menu-editor.
the command line is: nvidia-settings

oh i want to leave a big "thanks" here to all the people who made 9631 available again!

[cement_head (andorjkiss)]

Yep, that's what I did, but...

It's a small bug that this is not installed as part of nvidia-glx

- CH

[Olivier (olidel)]

Hello,

      I don't know if you noticed it but there is a new package in the
ubuntu repository, it is called nvidia-glx-new and it it the nvidia driver
version 1.0.9755. The old nvidia-glx package is back to nvidia driver
version 1.0.9631. So that should fix this issue.

     Thank you very much to the ubuntu team and community for the good work.

Thanks.

O.D.

2007/4/11, cement_head <email address hidden>:
>
> Yep, that's what I did, but...
>
> It's a small bug that this is not installed as part of nvidia-glx
>
>
> - CH
>
> --
> MASTER: Request for new-legacy nvidia drivers (9631)
> https://bugs.launchpad.net/bugs/96430
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

[cement_head (andorjkiss)]

Hi Oliver,

I don't think so...going to the 9755 driver will bugger the whole X server (again), at least on my card (nVIDIA GeForceGo 2).

Manual install of the 1.0-9631 driver from nvidia's website installed the XServer Setting control menu item. Using Ubuntu's nvidia-glx package does not.

This appears to be a bug.

It is small, but annoying.

Hello,

      I don't know if you noticed it but there is a new package in the
ubuntu repository, it is called nvidia-glx-new and it it the nvidia driver
version 1.0.9755. The old nvidia-glx package is back to nvidia driver
version 1.0.9631. So that should fix this issue.

     Thank you very much to the ubuntu team and community for the good work.

Thanks.

O.D.

2007/4/11, cement_head <email address hidden>:
>
> Yep, that's what I did, but...
>
> It's a small bug that this is not installed as part of nvidia-glx
>
>
> - CH
>
> --
> MASTER: Request for new-legacy nvidia drivers (9631)
> https://bugs.launchpad.net/bugs/96430
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

[Steveire (steveire)]

I'm also having a problem with an nvidia geforce 420go. I'm trying to make a support thread here(http://ubuntuforums.org/showthread.php?t=405959), but not getting much in the way of leads.

[mike (arizonagroovejet)]

The new nvidia-glx package works for my Nvidia GeForce 3somethingorother. Cheers for making 9631 available again.

[zeddock (zeddock)]

I want to say "Thanx!"

I am on a Dell Latitude D800 with nVidia GeForce4 Go 4200 Ti AGP8.

Upon a first try yesterday night, I could not use the 96xx driver. (I ended up with a blank screen)

This morning I have done a complete reinstall using the beta ISO.
On first boot after the install the update manager said there was a ton of updates that were needed. I updated. (Took hours!)

After the update it asked for a reboot. I did it. Checked updates again. No more...

I went to restricted manager and saw the 96xx installed but not in use. I checked it to ON.
I rebooted... hoping to not see a blank screen again...

Rebooted fine! Although I do not see an nVidia white, logo screen, it was obvious it was working and the Restricted Manager said "In Use" as well.

I rebooted just to make sure xorg.conf would not be corrupted.
Reboot went fine.

I enable desktop Effects. Almost immediately I got a requester to keep current or Previous settings, something I did not see before when it would fail...
I said Keep Current, and checked on the show desktop on cube.

I rebooted twice to verify it was solid.......

It is now solid for me.

Thanx again!!!

zeddock

[DaveAbrahams (boostpro)]

I seem to now have the right drivers installed, but that's apparently not enough to make "desktop effects" work with my GeForce 2 Go. I can get beryl to "work" but everything is so slow (like 1 frame every 20 sec) as to be unusable. It's not too surprising because glxgears doesn't run smoothly when maximized either. Have I left out an important step, or is this about what I should expect from this old card?

[Albert Abril (abrilc)]

Dave Abrahms, there had been changes with nvidia-glx packages. Now, there
are three different packages of nvidia-glx:

 · nvidia-glx
 · nvidia-glx-new
 · nvidia-glx-legacy

Maybe you have the wrong package for your card.
Check what should be your choice. Maybe it's the cause of your problem.
If you installed it with the 'Restricted Drivers Manager', it's supposed
that it would install the right .deb for your card. Otherwise, if you
installed manually (aptitude/apt-get), maybe not.

Luck!

[jdriessen (j-driessen)]

I have a Nvidia Geforce4 420 Go 32MB.

the nvidia-glx driver (9631) doesn't work on my system. (although it is the latest driver to support my card stated by Nvidia.com)
I get a blank screen after boot.

I installed the driver via restricted Drivers Manager today. on a fresh install of Feisty Beta 7.04.
I updated my system and rebooted before opening restricted drivers manager to load the driver.

I have the same problem installing the 9631 driver from Nvidia's website on Edgy. The 8771 drivers worked for my card in edgy.

I know this is not a support forum. I am merely posting this bug.

Ps. Would this be a problem not with Ubuntu but with the proprietary Nvidia Driver itself?

[jdriessen (j-driessen)]

in response to my previous post

those of you having similar problems if you have a Geforce4 420 Go 32MB.

the 9631 driver is looking for a CRT monitor and not and LCD (those of you having the problem on LCD monitors)

to fix this:

edit your xorg.conf

go to Section "Screen"

below defaultdepth, add: Option "UseDisplayDevice" "UFP-0"

this should fix the blank screen issue on LCD displays.

[K.Mandla (k.mandla)]

Hmm. No luck with my Geforce4 440 Go 64Mb. Thus far, patching the 8776 driver is the only thing that has worked for me. Thanks for the tip, though. Cheers!

[zeddock (jim-leaders)]

I had to completely reinstall the OS but afterwards, it worked. Desktop Effects and everything. Looking pretty good.

zeddock

[unggnu (unggnu)]

I can confirm this. Only nvidia glx legacy lets X start with Geforce4 440 Go 64Mb but only with a resolution of 800x600 instead of 1600x1200. Nvidia-glx seems to start X but the screen doesn't show anyhting. Is there anything planned to fix this or is the only solution nv or patching drivers/kernel? The problem with nv is the cpu usage and the disability to wake up screen after lid close.

[Justin J Stark (justinjstark)]

Works great for me with my geforce4 mx440se. Good work guys.

[missmomo0911 (missmomo0911)]

Still same problem like Enola Gay's,My video card is NVIDIA GeForce4 MX 440 64MB,and I use nvidia-glx-legacy
(nvidia-glx don't work with my card),but the screen can't show higher or lower dots per inch ,it can just show 800*600 dpi...

[eppy 1 (choppy121212)]

"
How do I get nvidia-glx to install the NVIDIA XServer Settings menu item under 'Applications>System Tools'?
"
"
cement_head:

you can do this easily in your menu-editor.
the command line is: nvidia-settings

oh i want to leave a big "thanks" here to all the people who made 9631 available again!
"

Could it be possible for nvidia-glx to automatically make a .desktop file for nvidia-settings, so that people don't wonder if it's installed or not? (as many packages in Dapper were like, thankfully now most apps automatically make menu items)

[Sitsofe Wheeler (sitsofe)]

Can people still having issues / suggestions spin them off into their own bug rather than overloading this one? Thanks.

[missmomo0911 (missmomo0911)]

NVIDIA GeForce4 MX 440 64MB...still have problems,I use command like follow:
 sudo apt-get install nvidia-glx-legacy
 sudo nvidia-glx-config enable
 sudo nano /etc/X11/xorg.conf

change "nv" to "nvidia",crtl+alt+space...just can show 800*600 dpi...
I have report this bug three times...what's going on ??> <

[Vangelis Tasoulas (cyberang3l)]

Ben Collins said on 2007-04-10:
The new lrm has 9631 back as the defauly nvidia-glx package set. There is now a new nvidia-glx-new package set for 9755. This was chosen because it offered the least surprise for upgrades. People who need (or want) the new 9755 driver should install nvidia-glx-new.

So missmomo0911 read more carefully before report this "not anymore a bug" again.

You have to install nvidia-glx package. Not the legacy one.
I had exactly the same problem as you have with the same nvidia MX440 graphics card and there is no problem now.

Hope it will work for you too as it has already worked for many of us.

[Albert Abril (abrilc)]

I have the same problem that missmomo0911: With a nvidia GeForce 440 MX
64Mb.
Sorry for those who doesn't like to see the same message again and again,
but it's the only way to confirm the bug.

[missmomo0911 (missmomo0911)]

I have remove nvidia-glx-legacy,and install nvidia-glx,it's work now.
I am sorry that I don't notice that nvidia-glx could get it work.Thank
you very much.

[Vangelis Tasoulas (cyberang3l)]

missmomo0911 said:
I have remove nvidia-glx-legacy,and install nvidia-glx,it's work now.
I am sorry that I don't notice that nvidia-glx could get it work.Thank
you very much.

You`re welcome :)
It is nice it works for you too ;)

[fishlet (fishlet-yahoo)]

+1 to the "this is a critical bug" side. I ran the distribution update tool and ended up with a boat anchor. Installed from scratch and applied the GLX drivers and ended up with a boat anchor again, could not even log in to the system :-(

I have a GForce 4 card, not new but not old by any means. If Ubuntu doesn't want to package so many drivers, why don't they leave out the oldest drivers instead of these- it doesn't make any sense. Surely there must be more middle aged GForce cards out there than TNT and Riva cards, Right? I know it makes for more work but I hope the Ubuntu maintainers realize their alienating alot of people by stripping that out.

Anyway, for those who are still struggling with getting their system running again- here's what I did:

1. Installed Feisty from scratch (I didn't have all day to fix it once it turned into a boat anchor)
2. Dowloaded NVIDIA's 96XX drivers
3. Installed LibC6 development package from Adept- needed for driver install.
4. Log out of KDE and from the KDM login screen- selected console login to get out of the X and to a console.
5. Run the NVIDIA installer, it will complain about some pgk-config thing being missing but it doesn't seem to be a critical problem, just proceed until
    it says that the driver is installed.
6. Reboot... system will come up with NVIDIA accelerated driver working like a charm.

Note, I had a bear of a time getting the resolution and refresh rates to be what I wanted after the install using Ubuntu's screen resolution control panel. Then I discovered that the NVIDIA installer puts it's own control tool in the KDE menu (under system or utils I think, I'm not in front of that computer right now). Heres what I had to do to fix that...

1. Set the resolution with NVIDIA's provided control panel.
2. Go into ubuntu's video control panel, it'll show some crazy refresh rate like 150hz or something, just ignore that and don't change anything there. I changed the power
    saver setting to make the control panel savable. If you don't do this, you may find that Ubuntu overwrites the settings changes you did in the NVIDIA control panel
    next time you reboot.

Of course, if you have a LCD you probably don't need to worry about that.

[Matthew Hughes (tute666)]

good god man.
read the bloody thread.
there are no cards left out anymore.
It's been fixed for a couple of weeks.

On 30/04/07, fishlet <email address hidden> wrote:
>
> +1 to the "this is a critical bug" side. I ran the distribution update
> tool and ended up with a boat anchor. Installed from scratch and applied
> the GLX drivers and ended up with a boat anchor again, could not even
> log in to the system :-(
>
> I have a GForce 4 card, not new but not old by any means. If Ubuntu
> doesn't want to package so many drivers, why don't they leave out the
> oldest drivers instead of these- it doesn't make any sense. Surely there
> must be more middle aged GForce cards out there than TNT and Riva cards,
> Right? I know it makes for more work but I hope the Ubuntu maintainers
> realize their alienating alot of people by stripping that out.
>
> Anyway, for those who are still struggling with getting their system
> running again- here's what I did:
>
> 1. Installed Feisty from scratch (I didn't have all day to fix it once it
> turned into a boat anchor)
> 2. Dowloaded NVIDIA's 96XX drivers
> 3. Installed LibC6 development package from Adept- needed for driver
> install.
> 4. Log out of KDE and from the KDM login screen- selected console login
> to get out of the X and to a console.
> 5. Run the NVIDIA installer, it will complain about some pgk-config thing
> being missing but it doesn't seem to be a critical problem, just proceed
> until
> it says that the driver is installed.
> 6. Reboot... system will come up with NVIDIA accelerated driver working
> like a charm.
>
> Note, I had a bear of a time getting the resolution and refresh rates to
> be what I wanted after the install using Ubuntu's screen resolution
> control panel. Then I discovered that the NVIDIA installer puts it's own
> control tool in the KDE menu (under system or utils I think, I'm not in
> front of that computer right now). Heres what I had to do to fix that...
>
> 1. Set the resolution with NVIDIA's provided control panel.
> 2. Go into ubuntu's video control panel, it'll show some crazy refresh
> rate like 150hz or something, just ignore that and don't change anything
> there. I changed the power
> saver setting to make the control panel savable. If you don't do this,
> you may find that Ubuntu overwrites the settings changes you did in the
> NVIDIA control panel
> next time you reboot.
>
> Of course, if you have a LCD you probably don't need to worry about
> that.
>
> --
> MASTER: Request for new-legacy nvidia drivers (9631)
> https://bugs.launchpad.net/bugs/96430
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[fishlet (fishlet-yahoo)]

That's all fine and good... but it didn't work for me.
Hence, the additional instructions.

[Tristan Schmelcher (tschmelcher)]

For people who are still having problems and who mistakenly installed nvidia-glx-new before switching to nvidia-glx, see here: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/106217

[botbotdingzip (botbotdingzip)]

fix released? Just installed the nvidia-legacy-glx and still no acceleration?? Worked fine in earlier versions of kubuntu. I have a GF 2 MX 200 like alot of others. Just install Feisty?? Get real. Fix what you broke before you start spraying releases please.

[cement_head (andorjkiss)]

botbotdingzip, you have to switch the xorg.conf to read "nvidia" from "nv" and reboot.