ABI change in xorg 1.9 breaks legacy nvidia-96 drivers in Maverick
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Release Notes for Ubuntu |
Fix Released
|
Undecided
|
Unassigned | ||
X.Org X server |
Invalid
|
Undecided
|
Unassigned | ||
jockey (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Maverick |
Fix Released
|
Undecided
|
Alberto Milone | ||
nvidia-graphics-drivers-96 (Ubuntu) |
Fix Released
|
Medium
|
Alberto Milone | ||
Maverick |
Fix Released
|
Medium
|
Alberto Milone |
Bug Description
Per bug 616394, xorg-1.9 is incompatible with the nvidia-96 and nvidia-173 driver packages that are currently in Maverick. These are the proprietary drivers in Ubuntu for Nvidia hardware prior to the GeForce 6000 series.
Perhaps a "Breaks: nvidia-96, nvidia-173" or some such line could be added to the xserver-common control file to keep the X.org 1.7 installation from Lucid intact during an upgrade to Maverick.
Changed in xorg-server (Ubuntu): | |
status: | New → Confirmed |
tags: | added: maverick |
NoOp (glgxg) wrote : | #1 |
luk1don (luk1don) wrote : | #2 |
I confirm too. Last working version with the nvidia-96 is: xserver-xorg-core 2:1.8.1.
The solution is downgrade to that package but it breaks some dependencies...
Charlie Jolly (charlie-jolly) wrote : | #3 |
Breaking 3D acceleration needs a big fat warning for anyone upgrading...
As a note: 260.xx beta drivers on Nvidia site incorrectly stated as being compatible with GeForce 5 series, at least with AGP cards....
Wish there was an easy menu so I could choose my driver... e.g. NV, Nvidia, Nouveau, Vesa etc
Going to try and downgrade xorg trick..
Charlie Jolly (charlie-jolly) wrote : | #4 |
>[ 562.979] (II) LoadModule: "nvidia"
>[ 562.980] (II) Loading /usr/lib/
>[ 563.018] dlopen: /usr/lib/
>[ 563.018] (EE) Failed to load /usr/lib/
>[ 563.018] (II) UnloadModule: "nvidia"
>[ 563.018] (EE) Failed to load module "nvidia" (loader failed, 7)
>[ 563.018] (EE) No drivers available.
Christian (kurisu666) wrote : | #5 |
THe Same Problem would be IF I Upgrade to Maverick... I Hope it doesnt take so long to fix it, because there alot people with such Cards... Just Like me and my Geforce 4 Ti 4200 AGP :D
SV (sv22342) wrote : | #6 |
If I only knew about that problem before upgrade I have just made few hours ago :( (10.04.1->10.10) Now I'm stuck with nv driver, as nouveau is so slow on my machine, that even moving mouse pointer over menus makes lag. That's really bad, I hope nvidia-96 binary drivers will work with Ubuntu 10.10 as soon as possible.
Here is what Xorg.0.log says:
[ 241.130] (II) LoadModule: "nvidia"
[ 241.130] (II) Loading /usr/lib/
[ 241.131] dlopen: /usr/lib/
[ 241.131] (EE) Failed to load /usr/lib/
[ 241.131] (II) UnloadModule: "nvidia"
[ 241.131] (EE) Failed to load module "nvidia" (loader failed, 7)
[ 241.131] (EE) No drivers available.
[ 241.131]
Fatal server error:
[ 241.131] no screens found
Darik Horn (dajhorn) wrote : | #7 |
An NVIDIA staffer said that the nvidia-173 drivers are being updated for X.org 1.9 here:
http://
NoOp (glgxg) wrote : Re: [Bug 626974] Re: ABI change in xorg 1.9 breaks legacy nvidia-96 and nvidia-173 drivers in Maverick | #8 |
On 09/30/2010 01:35 PM, Darik Horn wrote:
> An NVIDIA staffer said that the nvidia-173 drivers are being updated for
> X.org 1.9 here:
>
> http://
>
Unfortunately it's very quiet on the 96 front:
<http://
Mytonn (mytonn) wrote : Re: ABI change in xorg 1.9 breaks legacy nvidia-96 and nvidia-173 drivers in Maverick | #9 |
And nvidia-173 drivers are updated..
* Added support for X.Org xserver 1.9.
* Updated nvidia-installer to detect the nouveau kernel module and fail with an appropriate error message.
luk1don (luk1don) wrote : Re: [Bug 626974] Re: ABI change in xorg 1.9 breaks legacy nvidia-96 and nvidia-173 drivers in Maverick | #10 |
Fortunately not "very" quiet:)
http://
Ryu Ito (kumaryu-watchtower) wrote : Re: ABI change in xorg 1.9 breaks legacy nvidia-96 and nvidia-173 drivers in Maverick | #11 |
I now have 173.14.28 running in Maverick, Xserver 1.9 with Geforce FX5700 Ultra.
As noted in a post from Mytonn, the drivers are from http://
Darik Horn (dajhorn) wrote : | #12 |
Kudos to Aaron at Nvidia for providing excellent ongoing Linux support.
Darik Horn (dajhorn) wrote : | #13 |
I don't see the new 173.14.28 driver in the Ubuntu x-swat queue, so I updated the nvidia-173 package and put it here:
https:/
This updated Nvidia driver is compatible with my 32-bit Ubuntu 10.10 Maverick RC computer where I have older hardware. The 64-bit build installs cleanly, but I haven't tested it.
An updated nvidia-96 driver isn't yet availabe on the upstream FTP server.
Ryu Ito (kumaryu-watchtower) wrote : | #14 |
As reported in:
Ubuntu “nvidia-
"Nvidia 173 driver does not work with xserver 1.9 "
nvidia-
has now been released. I can confirm that it is now included in the most recent set of updates for maverick.
auxbuss (launchpad-auxbuss) wrote : | #15 |
A regular aptitude upgrade installed the updated nvida-173-
Maverick/GeForce GT 330M/Sony Vaio f-series
Julien Aubin (gojulgarbmail) wrote : | #16 |
auxbuss > You should use package nvidia-current, not NVidia-173. I'm not even sure your card is supported by driver nvidia-173...
auxbuss (launchpad-auxbuss) wrote : | #17 |
To be honest, looking at the nvidia package installed, I'm not clear what I should or should not have. I've not had problems here before, so I've never looked. For background, this machine was upgraded from Lucid. I have the following installed:
nvidia-
nvidia-
nvidia-common
nvidia-current
nvidia-
nvidia-settings
It looks like 173, 96, and common can go, so I'll try that and leave this bug alone. Apologies.
Omega-xis (nieknooijens) wrote : | #18 |
got an older model with geforce 4-mx which is affected.
however, my quadcore with the nvidia 9600GTX isn't affected, it works fine on that machine.
Changed in ubuntu-release-notes: | |
status: | New → In Progress |
Felix (apoapo) wrote : | #19 |
I experience non-working drivers with a "geforce 4200 ti"
Hardeep Singh (hardeep1singh-s60) wrote : | #20 |
I have a newer Nvidia GTS250, Ubuntu 10.10 final boot CD just gives me screen with big green squares after 20-30 seconds of choosing an option from the grub. Have been facing this issue since the beta and sadly the issue exists even in the final version.
Here's a video of what I see. http://
Brian Rogers (brian-rogers) wrote : | #21 |
Hardeep, you should file a new bug report for that. It's not related to this bug.
Philip Muškovac (yofel) wrote : | #22 |
@Hardeep: Please file a bug against xserver-
Xebozone (markdavidoff) wrote : | #23 |
Confirmed still not working with my
HP GFX PCA GeForce4 MX440-8X 64MB DDR w/comp TV (part no. 5187-3706)
even with nvidia-current drivers installed
belovedmonster (jd-hartland) wrote : | #24 |
Xebozone, your card will use nvidia-96, which hasn't been fixed by the Nvidia guys yet (unless something has changed I'm not aware of). Until they issue a fix this bug can't be fixed. We are waiting on them to supply the fix.
mutineer612 (mutineer612) wrote : | #25 |
I recently upgraded from 10.4 to 10.10 x64 and found out the hard way that 10.10 has issues with nVidia GeForce8400 due to newer version of Xorg 1.9. I had the nVidia driver 'current' working with my nVidia GeForce 8400 when I performed the upgrade from 10.4, and after rebooting found that the system booted to a purple background image with no login prompt. I tried booting into recovery mode by holding shift while booting and disabling the nVidia driver and rebooting.
Now with the driver removed the system boots to purple background screen with the ubuntu status indicators (dots) and makes the drum sound normally followed by the login prompt, but I'm unable to see it and none of the function keys work to drop to a console. However if I perform the reboot again with the drivers removed I'm able to hold down the shift key while booting and enter recovery mode again and then select safe graphics mode to access the system, and this seems to work ok, but I cannot get the system to boot without performing these manual steps.
Adam Reeve (adreeve) wrote : | #26 |
Mutineer612, this bug has nothing to do with your problem, it is for older cards using the nvidia-96 drivers. If you think you've found a bug and can't find it reported in Launchpad then please create a new bug report.
Martina Neumayer (martina.neumayer) wrote : | #27 |
Confirmed. Affect me too :( after upgrade from 10.04.
GF5200 AGP, Ubu 10.10, Xorg 1.9
calinflorin (calinflorin2000) wrote : | #28 |
Same here with nvidia gt240. When trying to install I get pixel-ed screen in 10.10 and cut-off window screen in 10.04 LTS.
Antoine Jouve (aj94tj) wrote : | #29 |
This bug affects my Geforce MX440. But I fear that this bug won't be fix one day because the nvidia's guys don't care about our old graphics cards :(
Laurent (laurent-q) wrote : | #30 |
Same problem for me with my GeForce 8500 GT and the nvidia-173(current) after a fresh install of 10.10
G M Slater (precipitous-media) wrote : | #31 |
For what it's worth - I have a GeForce 7300 and am running the Current driver (UbuntoStudio). I can boot into the generic kernel fine, but trying to boot into either 2.6.35-20-Low Latency, or 2.6.33-29-Realtime gives me only a command prompt. Unfortunately, I must have one of these kernels working for music production...
LostOverThere (lostoverthere) wrote : | #32 |
Yeah, this is a huge problem for people with legacy cards (which is a great deal of people running Linux). I had huge problems even setting the correct resolution (which wasn't detected correctly).
Running a Geforce MX 440 (AGP 8X) here.
Rob Bruce (r-bruce) wrote : | #33 |
Affects my PCI Express 2 Quadro FX 580. I didn't even think this was all that old of a card (it's still available).
Algo (algo-lkma) wrote : | #34 |
Too bad, affect my Geforce2 MX400 too.
As a temporary solution, I edit xorg.conf, and change:
From
Driver "nv"
To
Driver "vesa"
At least, we can run xWindows ^_^
ludwigmace (mason-schoolfield) wrote : | #35 |
If you're not sure if your card uses a legacy Nvidia driver or not, please see this list:
http://
It looks like this bug report is specifically for nvidia-96 and nvidia-173 drivers. So if your card (or its PCI ID) isn't on the above list underneath the 173.14.xx or 96.43.xx sections then unfortunately you won't find much help in this bug report; somebody out there please correct me if I'm wrong :)
And since 173.14.xx has already been fixed it looks like we're basically waiting on 96.43.xx drivers, which I'm guessing will be out in about a week or so.
Martina Neumayer (martina.neumayer) wrote : | #36 |
Maybe this helps someone.
Its from OMG website.
Thnx to "saurabhneo23"
http://
--
"If you can't fix it then downgrade it " :D
Well those who couldn't get their Nvidia drivers working with Ubuntu 10.10 due to newer version of Xorg-Xserver try to do the following : (it worked for me ;))
1) Remove any form of Nvidia drivers , configuration files and anything related to it. I dropped to vesa drivers but that is not necessary.
1) Backup /etc/apt/
2) In Synaptic, remove xserver-xorg
3) Reload/update the sources and install xorg
4) Install the Nvidia driver which you know worked with Lucid. In my case it is 195.36.24
5) change the sources.lst back to maverick
6) Reconfigure the xserver: sudo dpkg-reconfigure xserver-xorg
7 ) Now run these commands one after the another :
-- sudo update-alternatives --config gl_conf
-- sudo ldconfig
-- sudo update-initramfs -u
-- sudo nvidia-xconfig
8) Now using synaptic lock the version of these downgraded packages (xorg, nvidia-current, etc ) so that they don't get upgraded automatically
9) Restart.
Rob Bruce (r-bruce) wrote : | #37 |
@ludwigmace
Thanks for that link. Looks like I have a different problem (albeit having the same net effect) thus a different bug.
Anyway, for anyone wondering what the PCI ID of their Nvidia card is but not knowing where to look, try
lspci -d 10de: -nn
(to filter out everything by Nvidia)
or just:
lspci -nn
(if you want to see all your PCI hardware by every manufacturer.)
The PCI ID is the XXXX in the [10de:XXXX] that follows the manufacturer and product names
Infocenter has the info too, but you've got to dig through a few layers and didn't immediately pop out at me.
roddi (ruotger-skupin) wrote : | #38 |
Oh Man!
instead of warning you or downgrading the driver to something without acceleration that works, they let you run into that known trap! I'm really disappointed. Luckily Linux is only a hobby for me.
R
Firass Shehadeh (firass-shehadeh) wrote : | #39 |
I ran into this issue while upgrading from 10.4 to 10.10 on my 6 years old Dell Inspiron 8600.
According to lspci, my card is:
01:00.0 VGA compatible controller: nVidia Corporation NV28 [GeForce4 Ti 4200 Go AGP 8x] (rev a1)
If I try to use the nvidia driver in my Xorg configuration file, then X windows fails to start. If I comment out the driver line, then I think I was getting a generic driver, but the resolution was awkward, and I didn't the proper aspect ratio (the screen was compressed) and I couldn't get nice resolution).
So I removed the proprietary driver, and now X Windows is able to start, and the resolution is as usual. I think this is due to the "NOUVEAU" driver that comes by default (I saw that in /var/logs/
The main drawback: all the animated icons and windows decorations look very awful. It is like the bitmaps are off or something like it. I still prefer this option over the bad aspect/resolution, or downgrading Xorg.
Hopefully the Nvidia 96 driver will be updated to fix the issue with Xorg, or the nouveau driver will be updated to remove the annoying bitmap effects (I don't know how else to describe this).
To be fair, the issue touches several software components, and it is not easy to convince all of them to march towards the same release schedule.
Martina Neumayer (martina.neumayer) wrote : | #40 |
Update:
--
1) Remove any form of Nvidia drivers , configuration files and anything related to it. I dropped to vesa drivers but that is not necessary.
1) Backup /etc/apt/
2) In Synaptic, remove xserver-xorg and jockey-gtk
3) Reload/update the sources: sudo apt-get update and install xorg and jockey
There may be needed reboot.
4) Install the Nvidia driver which you know worked with Lucid. In my case it is 195.36.24
5) change the sources.lst back to maverick
6) Reconfigure the xserver: sudo dpkg-reconfigure xserver-xorg
7 ) Now run these commands one after the another :
-- sudo update-alternatives --config gl_conf
-- sudo ldconfig
-- sudo update-initramfs -u
-- sudo nvidia-xconfig
8) Now using synaptic lock the version of these downgraded packages (xorg, nvidia-current, etc ) so that they don't get upgraded automatically
9) Restart.
Martina Neumayer (martina.neumayer) wrote : | #41 |
Third update to the fix:
http://
luk1don (luk1don) wrote : | #42 |
nvidia-173 drivers
This bug was fixed in the package nvidia-
nvidia-96 drivers
This bug wasn't fixed yet, see duplicated bug:
https:/
Martina Neumayer (martina.neumayer) wrote : | #43 |
Fixed? So why this ***$#^#^$%$^&&*** don't work?
:/
Riku Eskelinen (kingi89) wrote : | #44 |
And why, oh why, my bug got marked as duplicate :( (see https:/
Algo (algo-lkma) wrote : | #45 |
As a quick temporary solution, use VESA driver la!
Just need to edit 1 line in xorg.conf.
I am using VESA driver now, don't feel much different (though cannot run 3D games).
Nelson Richter (nelson-richter) wrote : | #46 |
I have a Nvidia MX-400/440 video card running on a Athlon XP2100 with 512 ram. After upgrading to 10.10 I've experienced a really annoying wrong resolution (1024x768 instead of 1440x900) but is now working properly. I don't know what I did exactly. I really tried a lot of suggestions I've found on the web, like uninstalling e installing again some packs. If someone is interested on the current configuration of any file, please let me know.
paercebal (paercebal) wrote : | #47 |
Same problem for me.
I wonder if "normal" people could have found the "dlopen: /usr/lib/
A warning prior upgrade would have been nice...
-- Written from my brand new 10.10 Ubuntu on a 800*600 über-ugly resolution
paercebal (paercebal) wrote : | #48 |
Thanks to eMcE's hack, I succeeded in getting my screen back.
Still, there one glitch : Upon restarting, it went on the console, because it could not find the nvidia driver. I guess it was because I installed nvidia-current alongside nvidia-96. The solution was to choose nvidia-96 driver instead of nvidia-current (for my video card, I use the "96" driver).
Please note that before eMcE's last step (Restart), I did edit my xorg.conf file to put it back the configuration that worked for me on Ubuntu 10.04.
The steps were:
1. Start Ubuntu on recovery mode
2. On the ugly menu, choose "failsafe mode for one session only"
3. When logged in, go to Menu -> System -> Administration ->Hardware Drivers
4. You should see two drivers, the "NVIDIA accelerated graphic drivers (version current)" (which is "green", i.e., "in use", and the "NVIDIA accelerated graphic drivers (version 96) [Recommended]" which is not used.
5. Select "NVIDIA accelerated graphic drivers (version 96) [Recommended]" and Activate it (the button on the down right of the window)
6. Restart
7. Enjoy the purple screen
-- Written from my brand new 10.10 Ubuntu on a 1900*1200 über-cool resolution
P.S.: BTW, I hate those left-handed "à la MacOS" buttons, but the new font is really cool !!!
Martina Neumayer (martina.neumayer) wrote : | #49 |
@paercebal..
Im not the autor of this, I just repost solution here, and add some updates.
If this works for You than I'm glad :)
Daëavelwyn (daeavelwyn) wrote : | #50 |
I'm also affected by this bug and have exactly the same error message (found in Xorg log) :
14.301] (II) LoadModule: "nvidia"
[ 14.301] (II) Loading /usr/lib/
[ 14.302] dlopen: /usr/lib/
[ 14.302] (EE) Failed to load /usr/lib/
[ 14.302] (II) UnloadModule: "nvidia"
[ 14.302] (EE) Failed to load module "nvidia" (loader failed, 7)
[ 14.302] (EE) No drivers available.
[ 14.303]
Fatal server error:
[ 14.303] no screens found
[ 14.303]
I hope a patch will be published quickly :-/
SEWilco (scot-wilcoxon) wrote : | #51 |
I'm waiting for this to be fixed so I can upgrade my HP laptop, which is using nvidia-173.
Although I'm willing to fix it another way if someone makes a laptop with upgradable graphics cards.
macstevejb (macstevejb) wrote : | #52 |
Same problem here with my Geforce2 MX400 card which uses the v96.xx driver. Had to revert to Ubuntu 10.04 to get the driver installed correctly.
Hoping for a fix soon so I can upgrade to Meerkat.
Larry Woodring (larry-w) wrote : | #53 |
I'm having the problem, too. One of the reasons I installed Ubuntu on this old PC was that Linux is supposed to run better on older equipment. I had several major problems with my update from 10.04 to 10.10: first, my grub config got messed up and I had to restore it, losing my multi-boot in the process. Second, I had to do the "quick and dirty" fix to load the vesa driver, since my nvidia-96 driver is not supported. Overall, the upgrade to 10.10 has been a disaster. I'm afraid I was lulled into thinking that Ubuntu was more sophisticated than it is. In the future, I'll be sure to wait a couple of months before upgrading versions to make sure that bugs like this are ironed out first.
Ubuntu wants to appeal to the masses, but that won't fly until upgrades become reliable.
Paul Pechey (paul-pechey-deactivatedaccount) wrote : | #54 |
My PC also uses the GeForce2 MX/MX 400 (rev b2) card, so it looks like I'm stuck until they release a fix for the v96 driver. I'm afraid I agree with Larry's comment on Oct 16: upgrades need to be smoother. I've no idea how easy it is to revert back to 10.04.
Troy R. (dsm-iv-tr) wrote : | #55 |
Larry,
While upgrades have their share of issues, this is also not the forum to complain about the Ubuntu upgrade process.
Had you read the release notes, you would have done better to avoid upgrading until a better solution arose.
Troy
TM (napolas) wrote : | #56 |
With proprietary drivers 173.14.28 from mesa can´t enable desktop effects but glx is functioning.
Larry Woodring (larry-w) wrote : | #57 |
Troy,
You're right this is not the forum to complain about the upgrade process. And you're correct that if I had read the release notes, I might have discovered that it would be better to wait. On the other hand, if a release has significant bugs, it might be better to delay the release, or change the upgrade process to deal with the missing components in a more graceful manner.
For the most part, the point I'm making is that many of us have fallen into the trap of thinking that Ubuntu has become a mainstream operating system vs. a hobbyist OS. Clearly, it's not ready to be a mainstream OS and is still better suited to hobbyists than a general audience. This is more of an observation than a complaint.
Sam Azer (samazer) wrote : | #58 |
Hi Guys,
It's always good to help improve communication, understanding and cooperation - anytime and anywhere...
FWIW, I see many people dropping Windows (even though it's a very solid OS these days,) and moving to MACs and PCs running Ubuntu. In fact Ubuntu is now a mainstream operating system and, after years of major re-writing, Kubuntu is rapidly getting there too! You may have noticed news article after article from corporations and governments, going back as far as 10 years, announcing that they are supporting Ubuntu and, more recently, installing it by default on new PCs.
It's a good idea to review, though, why some people are having trouble and others, like me, are tickled pink:
There's an obvious scheduling problem with so many distros and projects being so disconnected from the manufacturers. The manufacturers would surely like to be able to provide the proper support and the distros would like to be able to work more closely with the manufacturers and the programmers involved in the various projects - but the business process is evolving with many problems remaining to be solved.
Canonical is making progress in this area and I think you'll find that all interested project leaders are paying attention - so we are marching forward on the learning curve and things are getting better in general. Also the cost of entry for new projects is going up - which will reduce the number of new projects and improve the quality of the successful projects as time goes on.
For now, though, people with production servers and workstations need to be more patient about major upgrades.
In my case I upgraded a few systems on the basis of the excellent work that I was seeing in the previous beta releases - but then I found that there are some serious instabilities in 10.10 (mysterious crashes that bring down everything including the kernel.) This is normal for a new release and I knew it - so I will try next time to wait a bit before upgrading my production environments. On the other hand it's hard for me to be patient because I want so much to make use of all the excellent product that is in the upgrades!
(My thanks and congratulations again to the many wonderful people who make all this good stuff possible!)
I hope that more people will take the time to review and discuss (and hopefully explain) what's going on in more detail as time permits. More discussion will Improve the level of knowledge and understanding which will help more people to properly benefit and enjoy all this great work that's being done.
Have a great day,
Take care,
Sam.
summary: |
- ABI change in xorg 1.9 breaks legacy nvidia-96 and nvidia-173 drivers in - Maverick + ABI change in xorg 1.9 breaks legacy nvidia-96 drivers in Maverick |
angandrob (angandrob) wrote : | #59 |
I have same trouble with nvidia-96 on 10.10 fresh install.
I can see both viewpoints. I know people that upgraded to Windows 7 and found older peripherals no longer worked and had to be replaced, so it does happen with “mainstream” OS. However there is a definite perception that Linux generally is more usable on older hardware, so incompatibilities (especially for something that worked in last few releases only a few months ago) are a little unexpected.
There is also the frequency of updates, whilst Windows only has a new release every 3 years or so and thus people expect larger changes, Ubuntu is effectively re-released every 6 months so people expect things that worked 6 months ago to still work. (I know there are LTS releases that are the most stable, but still people like to get the latest if its available).
Despite all this what is the expected solution. The issue was first raised nearly 2 months ago on 2010-08-30 and still hasn't been resolved (and may have been known about months before that), so is it likely to be resolved soon or should we be looking at other options. Is there a possibility that it will never be resolved (ie. hardware deemed too old so won’t bother trying to get drivers to work)? Will Nouveau ever get to the same capability and if so when. Would be good to know the expectations and timing so people can decide what to do, like roll-back to pseudo 10.04 or buy a new card.
Tim Riker (timriker) wrote : | #60 |
I've pulled the xserver-xorg packages from Lucid, and used the Maverick nvidia-96 package. Pinned xorg, xserver-xorg on the Lucid release using "aptitude hold xserver-xorg". Working nvidia drivers again for the old system.
I'm not on that machine at present, sorry to not post specific versions. Can someone at least post a nvidia-96 and perhaps nvidia-glx-96 update that require the old xserver-xorg? This should stop people from installing the new xorg and breaking things again.
Current Requires lists: x11-common (>= 1:7.0.0) which perhaps should also state < 1:9.0.0 ?
luk1don (luk1don) wrote : | #61 |
Temporarily solution
Before NVIDIA drivers installation do:
sudo apt-get purge xserver-xorg-core
sudo sed -i 's/maverick/
sudo apt-get update
sudo apt-get install xserver-xorg-core
echo "xserver-xorg-core hold" | sudo dpkg --set-selections
sudo sed -i 's/lucid/
sudo apt-get update
Riku Eskelinen (kingi89) wrote : | #62 |
@angandrob: As far as I know this bug cannot be fixed until NVidia releases xorg 1.9 compatible binary driver. And NVidia has told via its forum that they will release nvidia-96 driver for xorg 1.9, but it is low priority issue for them. So all we can do now is sit back, relax and enjoy our nv/vesa/nouveau drivers.
Karel Marik (kaja-marik) wrote : | #63 |
Same issue here on fresh maverick install. All GPU demanding applications are unusable.
Now running ...
$ lspci -v
01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev b2) (prog-if 00 [VGA controller])
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16
Memory at ee000000 (32-bit, non-prefetchable) [size=16M]
Memory at f0000000 (32-bit, prefetchable) [size=128M]
Expansion ROM at efff0000 [disabled] [size=64K]
Capabilities: <access denied>
Kernel driver in use: nouveau
Kernel modules: nouveau, nvidiafb, rivafb
John Harrington (j-fharrington) wrote : | #64 |
The nouveau hardware accelerated 3-d driver works fairly well in Maverick on my GeForce 4 MX 4000 card. Googleearth works pretty much as it did with the proprietary driver, including 3-d buildings, except that when the view moves close to horizontal and the horizon comes into view, the photographic view of the earth sometimes suddenly disappears. Otherwise, the 3-d effect works fine. Stellarium works at the same speed as with the proprietary driver, but the sunlight illumination doesn't appear on the planets (i.e., they appear in shadow from all sides). Foobillard billiards simulation game works fine except that there's an annoying moving shadow pattern on the table top. I haven't had any crashes.
I can't turn on desktop effects--I get the message that I need the proprietary driver.
According to the nouveau website, if you've got an nvidia card with a nv30 or later chip and want to try the 3-d hardware accelerated driver, you need nouveau_dri.so driver, which is in the libgl1-
In order to determine whether you need the nouveau_dri or the nouveau_vieux_dri driver, consult the table at: http://
John Harrington (j-fharrington) wrote : | #65 |
In my prior email running down how various 3-d programs work with the nouveau dri driver, I meant to say that celestia (not stellarium) works but without showing sunlight on planets. Stellarium crashes with error message: nv10_render.c:104: get_hw_format: Assertion `0' failed.
Aborted
SEWilco (scot-wilcoxon) wrote : | #66 |
Robert Hooker on 2010-10-19
summary: - ABI change in xorg 1.9 breaks legacy nvidia-96 and nvidia-173 drivers in
- Maverick
+ ABI change in xorg 1.9 breaks legacy nvidia-96 drivers in Maverick
I don't understand the meaning of the above change on 10-19. Does it mean that the original Ubuntu release does work with nvidia-173, that there is a modified version which works with nvidia-173, or that there is a different bug for the nvidia-173 problems?
Craig Kelley (ink) wrote : | #67 |
SEWilco: NVidia updated their 173 drivers already. The 96 code is still outstanding.
Alan (veloceraptor) wrote : | #68 |
It becomes apparent that NVidia couldn't care less about us people who bought their products when they were a fairly new company, so I guess when it become time to replace my graphics card I'm going to be spending my money elsewhere.
The bug was first reported on 2010-08-30 and it's now 2010-10-27 with still no fix in sight. Thanks a lot NVidia!
ludwigmace (mason-schoolfield) wrote : | #69 |
Seems that the 96 drivers have been updated every few months, with the longest delays being 5 and 8 months. This is an older legacy chipset so I'm OK with the fact that they don't update their drivers immediately whenever a Linux distribution updates its graphics packages. Last update was 7/15 to hopefully we'll see something fairly soon.
You can keep an eye on the drivers here:
ftp://download.
Andrea Mazzilli (andrea-mazzilli) wrote : | #70 |
They're working on it !
http://
Aaron Plattner (aplattner) wrote : | #71 |
Please give 96.43.19 a try. It was just released, so it might be a while before somebody packages it for Ubuntu.
luk1don (luk1don) wrote : | #72 |
Good job!
Thank you NVIDIA team!
Somebody can asign this to Alberto Milone...
Alex - Microsmeta (microsmeta) wrote : | #73 |
[SOLVED] Installing nvidia 96.43.19 drivers
as you see here: http://
as explained here: ftp://download.
James Kittsmiller (jkittsmiller2) wrote : | #74 |
Look here for the 64bit version:
ftp://download.
Antoine Jouve (aj94tj) wrote : | #75 |
Good job guys !
Thank you
Craig Kelley (ink) wrote : | #76 |
Any chance for a deb?
macstevejb (macstevejb) wrote : | #77 |
Really would like the opportunity to install Ubuntu 10.10 on my old box with a GeForce MX-400/440 card...hope that this new driver can be packaged soon :)
João Cruz (jalrnc) wrote : | #78 |
Yay. Reverting xorg back to lucid has been working pretty well for me so far, but I do appreciate the fix. Thanks nvidia!
paercebal (paercebal) wrote : | #79 |
Thanks, Aaron !
Alan (veloceraptor) wrote : | #80 |
Installed the new driver, unpinned x-server, upgraded and all is working well.
Many thanks NVIDIA team and many thanks to ludwigmace for posting the ftp link. That README is so very helpful :-)
Option "UseEvents" "True"
Option "TripleBuffer" "boolean"
in xorg.conf solved a couple of long-standing annoyances.
angandrob (angandrob) wrote : | #81 |
I installed the new driver and all seems to be working well now. Thanks guys for pushing this through.
James Kittsmiller (jkittsmiller2) wrote : | #82 |
Tried to install the new drivers can get 2d but I can't get compiz to work, any instructions on installing under Ubuntu?
Claudio Mignanti (claudyus) wrote : | #83 |
Hi,
I add the related branch, I guess that this is the correct way to inform Alberto Milone... or at least to I believe so :)
imlegend (story3661936) wrote : | #84 |
I had the same problem as James Kittsmiller. I successfully installed the driver,but still the compiz didn't work. Besides, I can't play video any more.
Ravishankar (ravi-buz) wrote : | #85 |
I still unable to install the driver..any help
luk1don (luk1don) wrote : | #86 |
No, this is the correct way:)
affects: | xorg-server (Ubuntu Maverick) → nvidia-graphics-drivers-96 (Ubuntu Maverick) |
luk1don (luk1don) wrote : | #87 |
nvidia-96 drivers are updated:
http://
Paul Anderson (deviljelly) wrote : | #88 |
Hi... Iǘe tried installing the 96.43.19 drivers from the .RUN package but something is conflicting.... can someone create a .deb?
owise1 (o-wise-1) wrote : | #89 |
the nvidia-96 drivers need to be packaged otherwise every time there is kernel chnage you will have to re-run the nvidia .RUN script. A PITA
imlegend (story3661936) wrote : | #90 |
I have solved my problems. Maybe there would be some help for James Kittsmiller.
1. Can't play video. It's the mplayer issue.
The cause was the mplayer couldn't find libvdpau.so.1. Just re-install libvdpau in synaptic and it goes well.
2. The compiz issue.
Just check the version of the compiz. It may be too high(like 0.9.0). Downgrade it and everything will be fine.
The packages are as below:
compiz
compiz-core
compiz-plugins
compiz-gnome
compizconfig-
compiz-
compiz-
compiz-fusion-bcop
Totally remove them, and re-install them,then reboot and enjoy your 3D effects.
Giuseppe Calaprice (giuseppe-calaprice) wrote : | #91 |
Nvidia 8600M GT on 10.10 MM, same problem!
baracus2k (baracus2k) wrote : | #92 |
They work fine over here. I have a Geforce 2 MX 32MB and I can enable effects through compiz and the extra effects from the appearance menu.
I followed the instructions by luk1don (post 45) on this page. It asked me something about some preinstall script but I just said continue.
http://
Then to enable effects I just followed the instructions from the Italian website posted earlier here. First run sudo gedit /etc/X11/xorg.conf and save a backup somewhere. Then just add the two lines below to xorg.conf anywhere under the Screen section.
Option "AddARGBGLXVisuals" "True"
Option "DisableGLXRoot
NoOp (glgxg) wrote : Re: [Bug 626974] Re: ABI change in xorg 1.9 breaks legacy nvidia-96 drivers in Maverick | #93 |
On 11/07/2010 04:46 PM, baracus2k wrote:
> They work fine over here. I have a Geforce 2 MX 32MB and I can
> enable effects through compiz and the extra effects from the
> appearance menu.
>
> I followed the instructions by luk1don (post 45) on this page. It
> asked me something about some preinstall script but I just said
> continue. http://
>
> Then to enable effects I just followed the instructions from the
> Italian website posted earlier here. First run sudo gedit
> /etc/X11/xorg.conf and save a backup somewhere. Then just add the two
> lines below to xorg.conf anywhere under the Screen section. Option
> "AddARGBGLXVisuals" "True" Option "DisableGLXRoot
>
However, several days following nVidia's fix/update
(https:/
and no action from Ubuntu.
Loading the driver manually will cause it to break with kernel updates.
The driver needs to be fixed in Ubuntu so that those of us with older
nVidia cards can upgrade/install properly.
yossarian_uk (morgancoxuk) wrote : | #94 |
@Giuseppe Calaprice - your Geforce 8600 doesn't use the nvidia-96 drivers .....
You should use nvidia-current driver - I have a geforce 8500 and it works totally fine...
Giuseppe Calaprice (giuseppe-calaprice) wrote : | #95 |
@yossarian_uk - I tried to install nvidia-current driver but I have the same trouble! Did you fix it or it works totally fine since the first installation?
Riku Eskelinen (kingi89) wrote : | #96 |
I think the new driver should be packaged and the package released asap, and this bug report should be updated. Now it seems that we're all waiting that somebody does something, but nobody does anything. That makes, IMO, Ubuntu in whole look bad.
Darik Horn (dajhorn) wrote : | #97 |
I've packaged the new nvidia-96 driver for Maverick in this PPA:
James Kittsmiller (jkittsmiller2) wrote : | #98 |
I tried your PPA installed the driver and after reboot nvidia-setting says driver not running, jockey says activated but not in use, and there is no xorg.conf file. What did I do wrong?
Riku Eskelinen (kingi89) wrote : | #99 |
Darik: Your packaging works for me, got nvidia running *thumbs up*. The only issue I ran into was X's driver autodetection, which seems to select VESA even if there are all nv, nouveau and nvidia to choose from. Setting driver to "nvidia" in xorg.conf seems to solve that, and I think it is bug somewhere in X and not in nvidia driver.
James Kittsmiller (jkittsmiller2) wrote : | #100 |
yes, but in previous releases, the Nvidia driver package would add an xorg.conf to load the driver. X has never auto detected the proprietary drivers when they are loaded.
Darik Horn (dajhorn) wrote : | #101 |
James: You must `sudo ./NVIDIA-
DKMS improperly clobbers the local nvidia.ko module and you'll get version mismatches and a mangled configuration. If you want to regenerate the xorg.conf file, then run `sudo nvidia-xconfig` at a terminal prompt. Also note that the Jockey driver manager doesn't recognize the oldest and newest Nvidia drivers but they still work properly. Ignore he warning.
This ticket is the wrong place to do technical support. The best place to ask is the PPA page, the IRC channel, or the forums.
Xebozone (markdavidoff) wrote : | #102 |
Great stuff! Hope to see in the official mirror soon!
James Kittsmiller (jkittsmiller2) wrote : | #103 |
@Darik Horn
This was a fresh install of 10.10, I never installed the binary package this time around, just used your PPA, that is why I asked here. I searched around the net till I found the xorg.conf that gets installed by default with jockeys 96.43.17 on 10.04 and copied it to my own file.
Darik Horn (dajhorn) wrote : | #104 |
I reverted the patch in jockey that ignores nvidia-96 and put it into the PPA.
If jockey still doesn't automatically update the xorg.conf file then do this:
1. Ensure that the nvidia-common package is installed. Jockey needs nvidia-common to detect nvidia-96 and nvidia-173 hardware.
2. Backup and delete the /etc/X11/xorg.conf file.
3. Toggle the driver in System -> Administration -> Additional Drivers. (eg: Deactivate, Activate)
4. Check the /var/log/jockey.log file for warnings and errors. This log file is usually empty unless something is glitched.
James Kittsmiller (jkittsmiller2) wrote : | #105 |
That's much better, worked like a charm now if we could only get a commit from a developer.
James Kittsmiller (jkittsmiller2) wrote : | #106 |
I meant to the main repositories.
macstevejb (macstevejb) wrote : | #107 |
@Darik Horn's ppa worked a treat with my Nvidia GeForce 4 MX 400 card on an old box with Lubuntu 10.10 installed.
Many thanks for packaging this new nvidia driver :)
NoOp (glgxg) wrote : | #108 |
@Darik Horn: Thanks for packaging this.
Ubuntu 10.10 (fully updated)
*-display
description: VGA compatible controller
product: NV25GL [Quadro4 900 XGL]
vendor: nVidia Corporation
Shows up in Jockey properly, cannot enable desktop effects (System|
$ sudo nvidia-xconfig
and reboot.
Afterwards I am able to set desktop effects. However none of the compiz settings (using the compiz settings manager) work.
$ cat xorg.conf
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 30.0 - 110.0
VertRefresh 50.0 - 150.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection
NoOp (glgxg) wrote : | #109 |
Got it working; had to remove the driver via jockey, reinstall compiz, re-enable the driver via jockey, reboot & re-enable 'Visual Effects - Extra', and reset the compiz settings via the compiz settings manager. I now get the expected compiz bells & whistles (rotating desktops etc., etc). Thanks Darik. Perhaps Ubuntu could assign this to you for final packaging?
Jonathan Chan (coprolites) wrote : | #110 |
@Darik Horn: Thank you dearly, I was lost without that package/ppa. So glad to have my compiz plugins back on my Ubuntu 10.10.
I have a GeForce2 MX400 and the ppa worked perfectly after following your troubleshooting instructions.
Sim (aydinshahin93) wrote : | #111 |
Thanks a lot Darik Horn, it works perfectly with a Geforce4 TI 4200!
Philip Muškovac (yofel) wrote : | #112 |
Marking Triaged. All that's left to do is to package it for natty and maverick.
Changed in nvidia-graphics-drivers-96 (Ubuntu): | |
importance: | Undecided → Medium |
status: | Confirmed → Triaged |
Changed in nvidia-graphics-drivers-96 (Ubuntu Maverick): | |
importance: | Undecided → Medium |
status: | Confirmed → Triaged |
Petr A. Sokolnikov (petr-sokolnikov) wrote : | #113 |
- Xorg.0.log.old Edit (8.0 KiB, application/x-trash)
Darik Horn, hello.
I was tried your PPA, but got error.
Felix (apoapo) wrote : | #114 |
Why isn't it in the repos? Sure, i am clearly capable of installing binary from nvidia or using someone's ppa.
But this is Ubuntu. Main staff said it's for human beings. Not scripting nerds. Ubuntu released a version without support for older gfx cards without a real warning in the update manager. That's a big fail. (!!)
Now a fix apperead, hooray. But it takes weeks to get it into the repos. Is it just that no one of the devs is interested in releasing it? Better things to do than fixing gfx for 50% of Ubuntuusers? (linux = OS for lowend machines. Of Course high end also ;) )
Sorry for that flame post, but it's too often like this. Developers stop when things work. Work means: do this sh script as root, shutdown x-server and install it by ... I guess i don't have to tell you what my girlfriend would say to that kind of step by step guide..
Maybe we should re-define "working" for Ubuntu and try to improve user experience for unexperienced users! ( the mac way.. clearly visible a successfull way)
Larry Woodring (larry-w) wrote : | #115 |
apo, you are 100% on target. I could go through all of the gyrations to patch my drivers using the posted solution, but I didn't install Ubuntu because I wanted to spend a lot of time maintaining the machine I use it on. Ubuntu has a great distribution and updating system. It seems pointless and inefficient to have to work around the system in a case like this. This should be rolled into a normal update ASAP and officially available.
NoOp (glgxg) wrote : | #116 |
On 11/19/2010 03:25 AM, apo wrote:
> Why isn't it in the repos? Sure, i am clearly capable of installing
...
And still unassigned...
https:/
shows:
Maintainer:
Ubuntu Development Team
Urgency:*
Low Urgency
Seems to me that failure to use default 3D graphics, compiz, et al
should be something other than "Low Urgency". So let's recap... these
are all the cards/users that are being left behind:
<ftp://download.
NVIDIA chip name Device PCI ID
GeForce 6800 Ultra 0x0040
GeForce 6800 0x0041
GeForce 6800 XE 0x0043
GeForce 6800 XT 0x0044
GeForce 6800 GT 0x0045
GeForce 6800 GT 0x0046
GeForce 6800 GS 0x0047
GeForce 6800 XT 0x0048
Quadro FX 4000 0x004E
GeForce 7800 GTX 0x0090
GeForce 7800 GTX 0x0091
GeForce 7800 GT 0x0092
GeForce 7800 GS 0x0093
GeForce Go 7800 0x0098
GeForce Go 7800 GTX 0x0099
Quadro FX 4500 0x009D
GeForce 6800 GS 0x00C0
GeForce 6800 0x00C1
GeForce 6800 LE 0x00C2
GeForce 6800 XT 0x00C3
GeForce Go 6800 0x00C8
GeForce Go 6800 Ultra 0x00C9
Quadro FX Go1400 0x00CC
Quadro FX 3450/4000 SDI 0x00CD
Quadro FX 1400 0x00CE
GeForce 6800/GeForce 6800 Ultra 0x00F0
GeForce 6600/GeForce 6600 GT 0x00F1
GeForce 6600 0x00F2
GeForce 6200 0x00F3
GeForce 6600 LE 0x00F4
GeForce 7800 GS 0x00F5
GeForce 6800 GS 0x00F6
Quadro FX 3400/4400 0x00F8
GeForce 6800 Ultra 0x00F9
GeForce PCX 5750 0x00FA
GeForce PCX 5900 0x00FB
Quadro FX 330/GeForce PCX 5300 0x00FC
Quadro NVS 280 PCI-E/Quadro FX 330 0x00FD
Quadro FX 1300 0x00FE
GeForce PCX 4300 0x00FF
GeForce2 MX/MX 400 0x0110
GeForce2 MX 100/200 0x0111
GeForce2 Go 0x0112
Quadro2 MXR/EX/Go 0x0113
GeForce 6600 GT 0x0140
GeForce 6600 0x0141
GeForce 6600 LE 0x0142
GeForce 6600 VE 0x0143
GeForce Go 6600 0x0144
GeForce 6610 XL 0x0145
GeForce Go 6600 TE/6200 TE 0x0146
GeForce Go 6600 0x0148
GeForce Go 6600 GT 0x0149
Quadro NVS 440 0x014A
Quadro FX 550 0x014C
Quadro FX 540 0x014E
GeForce 6200 0x014F
GeForce 6500 0x0160
GeForce 6200 TurboCache(TM) 0x0161
GeForce Go 6200 0x0164
Quadro NVS 285 0x0165
GeForce Go 6400 0x0166
GeForce Go 6200 0x0167
GeForce Go 6400 0x0168
GeForce4 MX 460 0x0170
GeForce4 MX 440 0x0171
GeForce4 MX 420 0x0172
GeForce4 MX 440-SE 0x0173
GeForce4 440 Go 0x0174
GeForce4 420 Go 0x0175
GeForce4 420 Go 32M 0x0176
GeForce4 460 Go 0x0177
Quadro4 550 XGL 0x0178
GeForce4 440 Go 64M 0x0179
Quadro NVS 0x017A
Quadro4 500 GoGL 0x017C
GeForce4 410 Go 16M 0x017D
GeForce4 MX 440 with AGP8X 0x0181
GeForce4 MX 440SE with AGP8X 0x0182
GeForce4 MX 420 with AGP8X 0x0183
GeForce4 MX 4000 0x0185
Quadro4 580 XGL 0x0188
Quadro NVS with AGP8X 0x018A
Quadro4 380 XGL 0x018B
Quadro NVS 50 PCI 0x018C
GeForce2 Integrated GPU 0x01A0
GeForce 7300 LE 0x01D1
Quadro NVS 110M 0x01D7
GeForce Go 7300 0x01D7
GeForce Go 7400 0x01D8
Quadro NVS 110M 0x01DA
Quadro NVS 120M 0x01DB
Quadro FX 350M 0x01DC
Quadro FX 350 0x01DE
GeForce 7300 GS 0x01DF
GeForce4 MX Integrated GPU 0x01F0
GeForce3 0x0200
GeForce3 Ti 200 0x0201
GeForce3 Ti 500 0x0202
Quadro DCC 0x0203
GeForce 6800 0x0211
GeForce 6800 LE 0x0212
GeForce 6800 GT 0x0215
G...
belovedmonster (jd-hartland) wrote : | #117 |
I hate to add a "+1 Me Too" comment, but it is becoming slightly embarrassing that no one has yet put this patch into Ubuntu. The fact is, for years now Ubuntu has been advertised by many people as being the OS that can bring your older hardware back to life. MILLIONS of people must run Ubuntu on old hardware. This problem needs to be fixed ASAP.
Petr A. Sokolnikov (petr-sokolnikov) wrote : | #118 |
+1 Me Too =)
I don't know why patch still not released. What ever, I hope it'll be soon, doesn't it?
Changed in nvidia-graphics-drivers-96 (Ubuntu): | |
assignee: | nobody → Alberto Milone (albertomilone) |
Changed in nvidia-graphics-drivers-96 (Ubuntu Maverick): | |
assignee: | nobody → Alberto Milone (albertomilone) |
Changed in nvidia-graphics-drivers-96 (Ubuntu): | |
status: | Triaged → In Progress |
Changed in nvidia-graphics-drivers-96 (Ubuntu Maverick): | |
status: | Triaged → In Progress |
Alberto Milone (albertomilone) wrote : | #119 |
SRU request:
The new package (which is now in maverick-proposed, pending for approval) restores compatibility with the X server ABI in Maverick. This update is warmly recommended as there are no (stable) alternatives to Nvidia's -96 3D driver that work with the current X server.
Alberto Milone (albertomilone) wrote : | #120 |
I really meant to say "pending approval"
Alberto Milone (albertomilone) wrote : | #121 |
- jockey_0.5.10-0ubuntu5.2.debdiff Edit (887 bytes, text/plain)
The attached debdiff re-enabled nvidia-96 in Jockey
Antoine Jouve (aj94tj) wrote : | #122 |
And what should we do with this patch? Excuse me, but I don't understand...
Philip Muškovac (yofel) wrote : | #123 |
@Antoine: that patch is meant for the ubuntu archive sponsors, not for you (unless you want to build your own jockey package). It'll take some time for all pieces to arrive in maverick updates.
Antoine Jouve (aj94tj) wrote : | #124 |
@Philip thanks for your answer, I'm going to wait some time...
Sebastiano (lafayette84) wrote : | #125 |
I can't find updated package in maverick-proposed. It is expected to be there?
owise1 (o-wise-1) wrote : | #126 |
Sebastiano - Philip wrote "It'll take some time for all pieces to arrive in maverick updates." yesterday so I expect that some time could be a week or two!
Sebastiano (lafayette84) wrote : | #127 |
owise1, I read also that Alberto Milone said that package is now in maverick-proposed. I subscribed to that repository in apt sources, anyway I can't find it!
I'm pretty sure because I also browsed inside main mirror (archive.ubuntu.com - pool) and no updated package for nvidia-96
Manfred Hampl (m-hampl) wrote : | #128 |
Alberto's ppa package worked well even on my vintage Geforce2 MX/MX 400 card.
How do we now get a version into the offical package repositories?
Just one remark to Alberto's package contents:
I think the 3 patches in the debian/dkms/patches directory should be removed, because as far as I can see they are already incorporated in the original nvidia package, and trying to apply them during the build process most probably will not work (but should not do any harm).
Martin Pitt (pitti) wrote : | #129 |
Thanks Alberto! Please upload the jockey change as well.
Changed in jockey (Ubuntu Maverick): | |
assignee: | nobody → Alberto Milone (albertomilone) |
status: | New → In Progress |
Changed in nvidia-graphics-drivers-96 (Ubuntu Maverick): | |
status: | In Progress → Fix Committed |
tags: | added: verification-needed |
Martin Pitt (pitti) wrote : Please test proposed package | #130 |
Accepted nvidia-
Alberto Milone (albertomilone) wrote : | #131 |
Ok, I've uploaded Jockey too.
Thanks.
yvesm (yves-moisan) wrote : | #132 |
Hi All,
I ran into issues trying to fix my display (MX 440-SE). I tried a few things : downloading a couple of nvidia packages with Synaptic, then ran nvidia-xconfig as root and now my xconf.org is broken. I tried using the backedup one, but even at that X does not start the way it should. In fact for a long while X didn't start at all. I commented out the nvidia section of it and now I get X to sort of start but I get 640X480 (at least I had 1024 X 768 before; that still wasn't good of course but I couldn't go for more).
Should I try reinstalling Ubnutu from scratch (just to make sure all those nvidia packages are gone) or just a clean xorg.conf (url please) would do ? Then should I try Martin's patch ?
I was hoping to steer my teenager from MS windows yesterday ...
TIA.
NoOp (glgxg) wrote : | #133 |
@Martin & Alberto: I'm not seeing jockey_
https:/
Should I wait for jockey to be upgraded in proposed before testing, or go ahead and use Darik's version? IMO it would be better to test with Alberto's so that we can verify both (nvidia-96 & jockey 5.2) at the same time.
Darik Horn (dajhorn) wrote : | #134 |
Notice the PPA version, where I used a dot instead of a tilde.
$ dpkg --compare-versions 0.5.10-0ubuntu5.2 gt 0.5.10-
$ echo $?
1
My computer already got Alberto's nvidia-96 from maverick-proposed, but it won't get jockey from maverick-proposed if it is published with a regular debchange increment.
Do this to disable the PPA and get the official jockey release if/when it becomes available in maverick-proposed:
$ sudo apt-add-repository --remove ppa:dajhorn/
$ sudo apt-get update
$ sudo apt-get install --reinstall jockey-common jockey-gtk
NoOp (glgxg) wrote : Re: [Bug 626974] Re: ABI change in xorg 1.9 breaks legacy nvidia-96 drivers in Maverick | #135 |
On 11/22/2010 11:50 AM, Darik Horn wrote:
> Notice the PPA version, where I used a dot instead of a tilde.
>
> $ dpkg --compare-versions 0.5.10-0ubuntu5.2 gt 0.5.10-
> $ echo $?
> 1
>
> My computer already got Alberto's nvidia-96 from maverick-proposed, but
> it won't get jockey from maverick-proposed if it is published with a
> regular debchange increment.
>
> Do this to disable the PPA and get the official jockey release if/when
> it becomes available in maverick-proposed:
>
> $ sudo apt-add-repository --remove ppa:dajhorn/
> $ sudo apt-get update
> $ sudo apt-get install --reinstall jockey-common jockey-gtk
>
Aleady did that - thanks :-) I'm just waiting for jockey to build before
I test together. Thanks again Darik for the early PPA build(s).
Almacha (almacha) wrote : | #136 |
It works. I installed nvidia-96 from maverick-proposed and ran nvidia-xconfig. I can now play OpenGL games. My card is an nVidia GeFroce 4 Ti 4200. Thanks for your work.
Martin Pitt (pitti) wrote : Please test proposed package | #137 |
Accepted jockey into maverick-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https:/
Changed in jockey (Ubuntu Maverick): | |
status: | In Progress → Fix Committed |
Martin Pitt (pitti) wrote : | #138 |
Natty jockey fix is in bzr.
Changed in jockey (Ubuntu): | |
status: | New → Fix Committed |
NoOp (glgxg) wrote : | #139 |
Works w/32-bit - partially:
VGA compatible controller: nVidia Corporation NV25GL [Quadro4 900 XGL] (rev a3)
2.6.35.23-generic
$ apt-cache policy jockey-common
jockey-common:
Installed: 0.5.10-0ubuntu5.2
Candidate: 0.5.10-0ubuntu5.2
Version table:
*** 0.5.10-0ubuntu5.2 0
500 http://
100 /var/lib/
0.
500 http://
0.
500 http://
maverick@
nvidia-96:
Installed: 96.43.19-0ubuntu1
Candidate: 96.43.19-0ubuntu1
Version table:
*** 96.43.19-0ubuntu1 0
500 http://
100 /var/lib/
96.
500 http://
Testing procedure:
1. Uninstalled Derik's repository & installs (purged nvidia* (sudo apt-get purge nvidia*) and jockey-common & jockey-gtk) and reinstalled jockey-common & jockey-gtk 0.5.10-0ubuntu5.2 proposed.
2. Rebooted w/o nvidia in low graphics mode - perhaps because I purged nvidia*?
3. System|
4. Reinstall nvidia-96 manually: sudo apt-get install nvidia-96... reboot. System|
5. System|
6. Install compiz-
The only part that bothers me is the initial failure of jockey to recognize & offer to install the nvidia-96 driver. While this may possibly be related to my purging nvidia*, jockey should (IMO) still detect the card following the clean reboot. So, until someone can explain why it does not: nvidia-96 96.43.19-0ubuntu1 works, but jockey 0.5.10-0ubuntu5.2 does not.
Alberto Milone (albertomilone) wrote : | #140 |
@NoOp
That's because you removed nvidia-common (which is what Jockey uses to do hardware detection with nvidia).
In other words I think things are ok. A one-line change in Jockey didn't cause that.
Petr A. Sokolnikov (petr-sokolnikov) wrote : | #141 |
- Xorg.3.log Edit (8.5 KiB, text/plain)
Hey guys, can you help me? I don't know why packages from maverick-proposed repository not worked in my ubuntu.
For the first i was remove dajhorn repository from my repository list by "sudo apt-add-repository --remove ppa:dajhorn/
After: apt-get update.
Then "apt-cache policy jockey-common" told:
jockey-common:
Установлен: 0.5.10-0ubuntu5.2
Кандидат: 0.5.10-0ubuntu5.2
Таблица версий:
*** 0.5.10-0ubuntu5.2 0
500 http://
100 /var/lib/
0.
500 http://
0.
500 http://
and "apt-cache policy nvidia-96" told:
nvidia-96:
Установлен: (отсутствует)
Кандидат: 96.43.19-0ubuntu1
Таблица версий:
96.
500 http://
100 /var/lib/
96.
500 http://
Then tried to install nvidia-96: "sudo apt-get install nvidia-96"
Then rebooted and recieved this:
[ 54.450] (II) NVIDIA(0): Initialized GART.
[ 54.458] (EE) NVIDIA(0): Failed to allocate/map the primary surface!
[ 54.459]
Fatal server error:
[ 54.459] AddScreen/
[ 54.459]
[ 54.459]
Please consult the The X.Org Foundation support
at http://
for help.
[ 54.461] Please also check the log file at "/var/log/
[ 54.461]
[ 54.584] ddxSigGiveUp: Closing log
Why it's not working for me ?
Darik Horn (dajhorn) wrote : | #142 |
Petr: Delete the /etc/xorg.conf file, toggle the nvidia-96 driver off/on at System -> Administration -> Additional Drivers, and restart the computer.
The "Failed to allocate/map the primary surface" error is caused by a missing AddARGBGLXVisuals option in the xorg.conf file. Jockey creates a correct xorg.conf file.
Some cards don't start if this option is missing, and others get GL artifacts like the desktop wallpaper being used in all transparencies.
NoOp (glgxg) wrote : Re: [Bug 626974] Re: ABI change in xorg 1.9 breaks legacy nvidia-96 drivers in Maverick | #143 |
> @NoOp
> That's because you removed nvidia-common (which is what Jockey uses to do hardware detection with nvidia).
>
> In other words I think things are ok. A one-line change in Jockey didn't
> cause that.
>
Ah. Got it. That makes sense. Thanks.
Petr A. Sokolnikov (petr-sokolnikov) wrote : | #144 |
- Xorg.1.log Edit (8.8 KiB, text/plain)
Darik Horn, thanks for your advise, but still not working.
petka@petka-
....
[ 49.159] (II) NVIDIA(0): Initialized GART.
[ 49.178] (EE) NVIDIA(0): Failed to allocate/map the primary surface!
[ 49.181]
Fatal server error:
[ 49.183] AddScreen/
[ 49.183]
[ 49.183]
Please consult the The X.Org Foundation support
at http://
for help.
[ 49.183] Please also check the log file at "/var/log/
[ 49.183]
[ 49.369] ddxSigGiveUp: Closing log
petka@petka-
Section "Screen"
Identifier "Default Screen"
DefaultDepth 24
Option "AddARGBGLXVisuals" "True"
EndSection
Section "Module"
Load "glx"
EndSection
Section "Device"
Identifier "Default Device"
Driver "nvidia"
Option "NoLogo" "True"
EndSection
Manfred Hampl (m-hampl) wrote : | #145 |
@Petr: Some ideas:
1. In several messages about problems with the nVidia driver it is recommended to add not only
-> Option "AddARGBGLXVisuals" "True"
but also
-> Option "DisableGLXRoot
to the xorg.conf file
Can you try that?
2. you might also try to delete your xorg.conf and re-create it with nvidia-xsettings
3. any error messages related to the video card in your boot logs?
Algo (algo-lkma) wrote : | #146 |
In case having problem, can try to remove compiz first.
At first my Ubuntu always halted with the new driver too!
luk1don (luk1don) wrote : | #147 |
Petr A. Sokolnikov@
Probably a framebuffer problem. Try options in kernel line, eg.:
vga=794, vga=791, vga=798, ... or some changes in grub configuration.
Launchpad Janitor (janitor) wrote : | #148 |
This bug was fixed in the package jockey - 0.6-0ubuntu1
---------------
jockey (0.6-0ubuntu1) natty; urgency=low
[ Alberto Milone ]
* data/handlers/
- Re-enable nvidia-96 now that it's compatible with xserver 1.9.
(LP: #626974).
[ Martin Pitt ]
* New upstream release 0.6:
- Add support and test case for reading modaliases from package headers.
- Put back "Additional Drivers" progress window title. Thanks Bilal
Akhtar! (LP: #323815)
- jockey/
cupshelpe
jockey is not normally used directly to install printer drivers.
Instead, system-
with the device ID, so jockey does not need to detect printers by
itself.
- jockey-kde: Use runtime .ui loading instead of pykdeuic4; the latter
just keeps breaking.
- gtk/jockey-gtk.ui: Drop obsolete has_separator property; Explicitly set
topmost GtkVBox fill property to True, as the default changed in GTK 3.0
(GNOME #634592)
- Various test suite fixes.
* debian/control: Drop now obsolete python-{qt4,kde}* build dependencies.
* debian/
* jockey/oslib.py, has_repositories(): Greatly speed up (5 seconds →
negligible) by calling "apt-cache policy" instead of creating an
apt.Cache() object.
* Drop data/handlers/
firmware now. Also, the wl driver is generally a lot better.
* Add support for putting modalias definitions in driver package's
debian/control, so that we can replace the /usr/share/
lists with lookups in the package database (see blueprint
hardware-
foo-modaliases packages, and shipping third-party driver packages will
just work in Jockey without any further integration.
- Add debian/
${modaliases} substvar from scanning .ko files or
debian/
- Add debian/
dh_jockey.
- Add debian/
- debian/control: Add dh-modaliases package.
- debian/
- debian/rules: Create manpage from dh_modaliases POD.
- jockey/oslib.py: Add apt implementation for package_
- tests/oslib.py: Add test case for our package_
implement
package with a "Modaliases:" field in the local apt repository.
* jockey/oslib.py: Change deprecated apt.apt_
* debian/rules: Drop simple-patchsys.mk, we don't need it (patches are
inline, maintained in bzr).
-- Martin Pitt <email address hidden> Thu, 25 Nov 2010 19:49:00 +0100
Changed in jockey (Ubuntu): | |
status: | Fix Committed → Fix Released |
Sebastiano (lafayette84) wrote : | #149 |
Still have problems even with new driver version. Reading through X log, it seems that glx module loaded is the one shipped by X.org and not by NVIDIA. is that correct?
X won't start and crashes with a segfault, even if AddARGBGLXVisuals is true in xorg.conf (created from scratch by jockey).
Any idea?
Sebastiano (lafayette84) wrote : | #150 |
Well, I did it. Browsing a bit through NVIDIA forums, I discovered that I was missing the correct ModulePath in xorg.conf to load libglx of Nvidia, not X.org's one.
Anyway, I'm a bit curious because jockey did create the X.org configuration file for me, and that line was not added.
Is jockey in fault, or on a default system Nvidia glx module will have priority over others?
For the ones who just want to know, in case, how I solved:
in xorg.conf, in section "Files", be sure that the first module path is Nvidia one
....
Section "Files"
ModulePath "/usr/lib/
ModulePath "/usr/lib/
.....
Alberto Milone (albertomilone) wrote : | #151 |
@Sebastiano: there's no need to add that line as the alternatives system + our patched xserver should take care of that.
Can you attach the output of the following command, please?
update-alternatives --display gl_conf
Sebastiano (lafayette84) wrote : | #152 |
Here it is. Strange, seems all ok. I haven't attached Xorg log before the adding of new module path, but crashed clearly because it was loading X.org libglx.so file.
---
sebastiano@
gl_conf - auto mode
link currently points to /usr/lib/
/usr/lib/
slave xorg_extra_modules: /usr/lib/
/usr/lib/
slave man_nvidiaxconf
slave nvidia-
slave nvidia-smi.1.gz: /usr/share/
slave nvidia_bug_report: /usr/lib/
slave nvidia_desktop: /usr/share/
slave nvidia_drv: /usr/lib/
slave nvidia_modconf: /lib/nvidia-
slave nvidia_smi: /usr/lib/
slave nvidia_xconfig: /usr/lib/
slave xorg_extra_modules: /usr/lib/
slave xvmcconfig: /usr/lib/
Current 'best' version is '/usr/lib/
Petr A. Sokolnikov (petr-sokolnikov) wrote : | #153 |
@luk1don,
I was tried different vga modes in /etc/default/grub, but still got error.
dmesg wrote:
[ 99.118023] agpgart-intel 0000:00:00.0: AGP 3.0 bridge
[ 99.118052] agpgart-intel 0000:00:00.0: bridge is in legacy mode, falling back to 2.x
[ 99.118065] agpgart-intel 0000:00:00.0: putting AGP V2 device into 4x mode
[ 99.118119] nvidia 0000:01:00.0: putting AGP V2 device into 4x mode
[ 100.654542] Xorg:1844 conflicting memory types e8000000-e8500000 uncached-
[ 100.654552] reserve_memtype failed 0xe8000000-
[ 100.656966] Xorg:1844 conflicting memory types e8000000-e8500000 uncached-
[ 100.656975] reserve_memtype failed 0xe8000000-
in Xorg.0.log:
[ 88.122] (EE) NVIDIA(0): Failed to allocate/map the primary surface!
[ 88.123]
Fatal server error:
[ 88.123] AddScreen/
Please, any idea, how can I fix it?
Petr A. Sokolnikov (petr-sokolnikov) wrote : | #154 |
Petr A. Sokolnikov (petr-sokolnikov) wrote : | #155 |
Manfred Hampl (m-hampl) wrote : | #156 |
@Petr:
Your problem seems to be the same as bug 605837
As a workaround adding the nopat option to your kernel boot command line should help. Please give it a try.
Petr A. Sokolnikov (petr-sokolnikov) wrote : | #157 |
@Manfred Hampl: Thanks! It work's!
Stefan Ivarsson (stefanivarsson) wrote : | #158 |
Have tested proposed as outlined in post #137. No issues at all with installation.
Driver works well and I even got my old bugs with non-working Suspend and Hibernate back ;-)
From my end ready for prime time
BRGDS
//Stefan
Newk (newk) wrote : | #159 |
i'm back to 10.04
:(
X kept breaking... i can't trust 10.10 yet
yaztromo (tromo) wrote : | #160 |
Got my X working now using the proposed drivers HOWEVER
- Sometimes X will freeze whilst starting GDM and the only solution is to pull the power
- Minimizing applications causes X to freeze for two seconds every time
Running Xubuntu 10.10
lspci:
VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev a2)
Graham Knap (graham-knap) wrote : | #161 |
If you don't want to enable the proposed-updates repository, and would prefer to install updated the packages manually, this method worked for me and my GeForce 4 Ti 4200:
1. Download and install the new jockey packages.
https:/
2. Jockey should now offer the nVidia 96 driver. Enable it. This will install version 96.43.18, which won't actually work, so don't reboot yet. However, this step is still useful because it installs dependencies, and makes the necessary configuration changes to enable the driver.
3. Download and install the new driver package.
https:/
4. Reboot.
Jukka Siitari (reed-siitari) wrote : | #162 |
Still no released fix for this bug!!!
My Ubuntu has been unusable for 3 months now! Starts only to command prompt after upgrading to Maverick. I do not want to go back to playing with command prompt/
Quote from Ubuntu pages: "Users of the official release, in contrast, expect a high degree of stability. They use their Ubuntu system for their day-to-day work, and problems they experience with it can be extremely disruptive. Many of them are less experienced with Ubuntu and with Linux, and expect a reliable system which does not require their intervention."
Alberto Milone (albertomilone) wrote : | #163 |
@Jukka
I thought the package had already been accepted into updates but this doesn't seem to be the case.
You can follow the instructions in comment #137 to enable the -proposed repository and install the new package:
https:/
Jukka Siitari (reed-siitari) wrote : | #164 |
OK Alberto!
Got Maverick "almost" working as per instructions of comment #137. Took a while, though.
There are still some issues in Maverick, however, although they mostly are not related to this bug. There is one thing, however, which might be related to the instructions in #137: The "Software Sources" line has disappeared from the desktop, ie. from System -> Administration. And because #137 instructs to edit the /etc/apt/
Thanks anyway!
tags: |
added: verification-done removed: verification-needed |
Deno (denis-havlik) wrote : | #165 |
Installing the 96.43.19 from maverick-proposed solved the issue on my Dell Latitude D800 oldie (GeForce4 4200 Go card).
FYI:
- I had to use the text install to get the 10.10 installed on this laptop in the first place;
- X worked after reboot, but the mouse cursor had a "shadow" ca. 1 cm apart from the real cursor position (with nv driver, I presume);
- installation of original 10.10 nvidia drivers resulted in text-only mode for a while; and
- the #137 method saved the day (thx).
Deno (denis-havlik) wrote : | #166 |
OK, something is broken now: kpackagekit (I'm on kubuntu) replies "unknown error"on every mouse click. On console output it complains about missing the ibus-daemon...
synaptic work fine, so it's bye-bye kpackagekit...
Tristan Schmelcher (tschmelcher) wrote : | #167 |
Installed nvidia-96, jockey-common, and jockey-gtk from maverick-proposed on my Compaq Presario R3000 and rebooted and the problem is now fixed (amd64).
Geoff (geoffch) wrote : | #168 |
I installed jocky-gtk, jockey-common, nvidia-96, nvidia-
Launchpad Janitor (janitor) wrote : | #169 |
This bug was fixed in the package jockey - 0.5.10-0ubuntu5.2
---------------
jockey (0.5.10-0ubuntu5.2) maverick-proposed; urgency=low
* data/handlers/
- Re-enable nvidia-96 now that it's compatible with xserver 1.9
(LP: #626974).
-- Alberto Milone <email address hidden> Mon, 22 Nov 2010 11:46:49 +0100
Changed in jockey (Ubuntu Maverick): | |
status: | Fix Committed → Fix Released |
Launchpad Janitor (janitor) wrote : | #170 |
This bug was fixed in the package nvidia-
---------------
nvidia-
* New upstream release:
- Switch to new xsfbs variables to get the server ABI
(LP: #616214).
- Add support for X.Org xserver 1.9 (LP: #626974).
* debian/
- Call dpkg-trigger with "--by-package".
* debian/
- Add compatibility with kernel 2.6.3{6|7}.
-- Alberto Milone <email address hidden> Sat, 20 Nov 2010 17:36:13 +0100
Changed in nvidia-graphics-drivers-96 (Ubuntu Maverick): | |
status: | Fix Committed → Fix Released |
Bryce Harrington (bryce) wrote : | #171 |
I'm assuming this task was just left open in error and that the issue also is solved in natty's package.
Changed in ubuntu-release-notes: | |
status: | In Progress → Fix Released |
Changed in nvidia-graphics-drivers-96 (Ubuntu): | |
status: | In Progress → Fix Released |
Larry Siden (lsiden) wrote : | #172 |
This problem is affecting me too. I have tried:
* installing the PPA ubuntu-
* following suggestions from #36 to downgrade back to Lucid.
* installing driver from maverick-proposed (apt-get install nvidia-
* installing proprietary driver directly from Nvidia site.
I've been at it all afternoon reading this and other threads and trying suggestions and nothing has worked. Does anybody have a fix for this?
A side-question. How do I know which driver I need for my chipset. lspci says I have NVidia NV44A [GeForce 6200]. Does that need the 96 or 170 driver or something else? I don't even know what those numbers mean. I assume that they must correspond to chipsets. I've been to the nvidia site but don't know what to look for.
I wish there was a clear set of instructions somewhere. Alternately, someone please tell me what kind of card I need to upgrade to for which there are good drivers in Maverick. I'd gladly pay a few extra bucks to have a working system again because I depend on it for my work. What a mess this has been for me and for others!
Larry Siden (lsiden) wrote : | #173 |
BTW - I tried running jockey-text (I have only a simple tty console right now) with -u, -c, -l, and it prints only "GtkWarning: could not open display" which doesn't make sense since jockey-text is supposed to be for non-graphics terminals. I know this is probably a separate issue, but I just thought I'd mention it.
Manfred Hampl (m-hampl) wrote : | #174 |
@Larry: from ftp://download.
Larry Siden (lsiden) wrote : | #175 |
Thanks. I finally got the proprietary driver from Nvidia to install and
it's working so I'll leave well enough alone and hope that they fix the
problem in the next Ubuntu release (11.4) so I can go back to the distro
package.
-Larry Siden
The United States is a nation of laws, badly written and randomly enforced.
--Frank Zappa 1940-1993
On Mon, Apr 11, 2011 at 2:10 AM, Manfred Hampl <email address hidden>wrote:
> @Larry: from
>
> ftp://download.
> it seems to me that you need the 260 (for natty 270) family of drivers,
> not the 96 one.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https:/
>
> Title:
> ABI change in xorg 1.9 breaks legacy nvidia-96 drivers in Maverick
>
> To unsubscribe from this bug, go to:
> https:/
>
clopezsandez (clopezsandez) wrote : | #176 |
I do not think so; I have been trying 11.04 and I have the same problem (a black screen in 10 seconds).
Changed in xorg-server: | |
status: | New → Invalid |
Larry Woodring (larry-w) wrote : | #177 |
So, what's the current situation? Will these drivers be supported with an update to Maverick now? What does the "invalid" status in xorg-server mean?
Manfred Hampl (m-hampl) wrote : | #178 |
As far as I know the current situation is as follows:
There is a working version of the dedicated proprietary nvidia-96 driver for Ubuntu 10.10 - not delivered with the installation or upgrade CD's, but available from the standard repositories for normal package installation.
The issue with Ubuntu 11.04 (there is no working dedicated proprietary nvidia -96 driver for xorg 1.10 available yet) is not the topic of this bug, but dealt with in bug #741930
Setting the status on X.org X server to 'invalid' mens that the changes have to be done / have been done on other packages, and X.org X server is not to be blamed.
Luigi Maselli (grigio) wrote : | #179 |
It happened again with Ubuntu 12.04 Precise Pangolin :(
Any update on nvidia-96 and maverick (10.10)? The 10.10 release date is drawing near & still no working nvidia-96 in maverick. Quite a few legacy cards will be affected by this issue:
==== www.nvidia. com/object/ linux-display- ia32-96. 43.18-driver. html
http://
GeForce 4 MX series:
MX 440, MX 440 (AGP 8X), MX 420 (AGP 8X), MX 420, MX 440-SE, MX
Integrated GPU, MX 460, MX 440SE (AGP 8X), MX 4000
Quadro NVS series:
NVS 285, NVS 55/280 PCI, NVS 210, NVS 420, NVS 450, NVS 50, NVS 295, NVS
280, NVS 440, NVS 290
Quadro 4 Go series:
500 GoGL, 550 XGL, 700 GoGL
Quadro 2 Go series:
MXR/EX/Go
GeForce 4 Ti series:
Ti 4800, Ti 4800 SE, Ti 4400, Ti 4200 (AGP 8X), Ti 4200, Ti 4600
GeForce 2 series:
Ti 200, GeForce3, Ti 500
Quadro 2 MXR series:
Quadro2 MXR/EX/Go
====
Including my machines with nVidia NV25GL [Quadro4 900 XGL] cards in them.