Update Package: nVidia 180.11

Thanks !

Patch for "freaks" running 2.6.28-RC4 ;)

http://www.nvnews.net/vbulletin/showpost.php?p=1843626&postcount=44

With Kernel 2.6.28 the GPU core temperature is about 10 degrees lower then
with 2.6.27.

Running a 7600GS card slightly overclocked with coolbits.

Will this update be available for Intrepid users (even if it's in proposed)?

180.06 is out

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

Release Highlights

    * Added support for CUDA 2.1.
    * Added initial support for PureVideo-like features on Linux via the new VDPAU API (see the vdpau.h header file installed withthe driver).
    * Added new workstation performance optimizations.
    * Enabled the X Render "GlyphCache" by default.
    * Disabled shared memory X pixmaps by default; see the“AllowSHMPixmaps" option.
    * Fixed a regression that could result in window decorationcorruption when running Compiz using Geforce 6 and 7 series GPUs.
    * Improved X pixmap placement on GeForce 8 series and later GPUs.
    * Improved compatibility with recent Linux kernels.
    * Improved stability on some GeForce 8 series and newer GPUs.

"bug" changed

180.06 will be a NEW driver. 177.82 is the stable release in the 177 series.

I just installed it and it just great....Jaunty and 2.6.28-RC4 running.

AWN and Compiz artefacts are fixed as I sees it. Hooray... ;)

KDE4/Plasma ?

I cannot see any reason for 177.82 and this driver can easily be tested with Jaunty.

I will provide 177.82 in Intrepid (SRU) and maybe 180.06 in Jaunty.

Ok.... the Murrine challenge is also fixed with RGBA trashing.

My logic says that the 180 driver must be a better choice also for a SRU.

Thanks, Alberto.

Diffing the .manifest files between 177.82 and 180.06, please be sure to include the following new files in the updated package:
/usr/lib/libvdpau.so.180.06
/usr/lib/libvdpau_trace.so.180.06
/usr/lib/libvdpau_nvidia.so.180.06
(plus various VDPAU library symlinks)
/usr/include/vdpau/vdpau.h
/usr/include/vdpau/vdpau_x11.h

For the -dev package, you might want to consider building the VDPAU Doxygen documentation and installing it as HTML.

Thanks for the information, Aaron.

I'll make sure that the new files and symlinks are included.

Same for me :)
All the bugs using kde4 are gone.

I'm going to test a .deb package of 180.06 as soon as it is available for Intrepid.

To put it in a clear way: user experience of kwin is very poor with 177.82 because it buggy.
I hope that there is a plan to propose this new driver (180 and the upcoming stable branch derived from 180) in intrepid.

177.82 is better but not sufficient to restore a good user experience of kwin (at least on my box (geforce 8 series))

fixes https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/298253

ver 180.08 is also out

Release Highlights:

* Added support for the following new GPUs:
o Quadro NVS 450
o Quadro FX 370 LP
o Quadro FX 5800
o Quadro FX 4800
o Quadro FX 470
o Quadro CX
* Added preliminary support for OpenGL 3.0.
* Improved VDPAU error recovery on some GPUs.

http://www.nvnews.net/vbulletin/show....php?p=1847941

Seems to be minor changes for VDPAU functionality, comments in a thread:

""The VDPAU changes in 180.08 were aimed at more graceful handling of problems that occur interacting with the GPU when decoding fails for some reason.""

Please release version 180 also for Intrepid - not only does it fix the KDE problem but supposedly also the issue with corrupted window decorations as described in https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/186382.

YES please do. =]

yes yes yes :)

Another vote for 180.x as an Intrepid backport or at least a PPA, and available in Jaunty.

Although 177.x is working here fine, it would really be nice if there would be possibility to upgrade to 180.x, because it has some major features. I guess 180.x shouldn't be default, but it could be proposed or PPA in Intrepid.

Noel J. Bergman wrote:
> Another vote for 180.x as an Intrepid backport or at least a PPA, and
> available in Jaunty.
>

Please post at least your configuration (you nvidia card)

Xavier

I'd like the 180.06 in Intrepid too. I'm on an 8600M GT card

Xavier wrote:
> Noel J. Bergman wrote:
> > Another vote for 180.x as an Intrepid backport or at least a PPA,
> > and available in Jaunty.
> Please post at least your configuration (you nvidia card)

Thinkpad T61p 6457-7WU, ergo nvidia FX-570M. Or if you prefer the verbose form, see attached.

180.x will be available as a backport ASAP

But will it be considered as a supported update or only as a backport ? Actually this could be put in intrepid-updates once it has been tested enough in intrepid-backports, just as KE 4.1.3 is.

Thanks anyway for your support.

I don't think they'll have a need to put this as an update while it's
labelled as a 'beta' by nVidia (who use the term 'beta' properly).

> I don't think they'll have a need to put this as an update while it's
> labelled as a 'beta' by nVidia (who use the term 'beta' properly).
>

Well ok maybe...but without this driver kde4 is not usable.
plasmoid just freeze if you have a geforce 8600.
The end user does not care if it is a beta or not.
The end user says "ho look kde4.1 is crap. I cannot use it on my box. It
is so unstable :(".

I'm not such an end user but I can understand this.
I have never see a bug in this new beta driver.
It does the job. The previous one does not.

Xavier

I'm not in a position to talk about KDE... only thing I know is that
end-users aren't supposed to be using it until version 4.2.

>> I don't think they'll have a need to put this as an update while it's
>> labelled as a 'beta' by nVidia (who use the term 'beta' properly).
>>

> I'm not such an end user but I can understand this.
> I have never see a bug in this new beta driver.
> It does the job. The previous one does not.

There are already 2 Nvidia drivers--177 and 173 (I think). 177 should remain labeled "recommended", and 180 could be labeled "Beta". The description could say something like use this only if you are having problems with 177, and that no official support will be provided for it.

> There are already 2 Nvidia drivers--177 and 173 (I think).
> 177 should remain labeled "recommended",
> and 180 could be labeled "Beta"

What do you think that 173 and 177 were labeled when 177 came out? :-)

Summing up, 173 and 177 don't work with Compiz, so there's no official way to enable the desktop effects on Intrepid if you own an Nvidia card. Now they have released a new driver which happens to be labeled as beta, but it fixes all major bugs that we're complaining about. Just add 180 to the driver list and leave 177 the recommended one. Once 180 goes final, recommend this release in the list. If possible, this should be done ASAP for the reasons mentioned above. Just my 2 cents.

> Summing up, 173 and 177 don't work with Compiz
What?

2008/11/26 ma2412ma <email address hidden>

> Summing up, 173 and 177 don't work with Compiz, so there's no official
> way to enable the desktop effects on Intrepid if you own an Nvidia card.
> Now they have released a new driver which happens to be labeled as beta,
> but it fixes all major bugs that we're complaining about. Just add 180
> to the driver list and leave 177 the recommended one. Once 180 goes
> final, recommend this release in the list. If possible, this should be
> done ASAP for the reasons mentioned above. Just my 2 cents.
>
> --
> Update Package: nVidia 180.06
> https://bugs.launchpad.net/bugs/297543
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

Have you read this bug report? There are severe issues with Compiz (corrupt window decorations) and KDE4 with drivers 173/177 and 180 fixes all of them.

I know about this bug, I had it at my previous job (integrated GF 6100), and
I don't think it can be called "Compiz doesn't work".

2008/11/26 ma2412ma <email address hidden>

> Have you read this bug report? There are severe issues with Compiz
> (corrupt window decorations) and KDE4 with drivers 173/177 and 180 fixes
> all of them.
>
> --
> Update Package: nVidia 180.06
> https://bugs.launchpad.net/bugs/297543
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

OK, it should be "the Window decorations are not rendered properly when using Compiz with Nvidia drivers 173 and 177". Anyway, any news about when 180 will be in Intrepid?

I have to agree that providing 180.06 to Intrepid is crucial. If it was indeed the case that only KDE 4.2 is to be used Kubuntu should have sticked with KDE 3.5. As it is the case, my desktop is unusable as well because of the 173/177 window corruptions.

From http://forum.kde.org/showthread.php?tid=16805&pid=21177 :

"Symptons include: not being able to browse with Firefox 3.0.4 for more than 2 minutes without a (silent) crash, garbled icons in kwin, kwin itself completely freaking out with garbage all over the place, garbage in the back-drop of menu-items right before they appear, garbage in the ALT-F2 execute window, a screen full of garbage when you want to shut down or suspend your machine (except for a small readable window), VMWare player losing the border when the image keeps running, etc"

The only advice to fix it so far has been an update of the nvidia driver to 180.06. I would really like to avoid doing a manual install.

lspci | grep -i nvidia
01:00.0 VGA compatible controller: nVidia Corporation G72GL [Quadro FX 350M] (rev a1)

Just to let you know, "tips" that the 180.08 driver fixes a bunch of stuff
are leaking out and people are installing them over the Ubuntu driver...
which'll cause things to turn quite ugly when Ubuntu upgrades its driver and
you start getting all sorts of "module not found" errors and low
resolutions.

Alberto, could you update us about the current status of this bug? I think this is extremely important and 180 should be provided officially ASAP.

SRU request:

TESTCASE:

increased hardware support, bugfixes and compatibility with the new driver 180:

nvidia-graphics-drivers-177:
  * Add driver 177.82 (LP: #297543):
    * Added support for the following new GPUs:
       o Quadro NVS 450
       o Quadro FX 370 LP
       o Quadro FX 5800
       o Quadro FX 4800
       o Quadro FX 470
       o Quadro CX
    * Fixed a problem on recent mobile GPUs that caused a power management resume from S3 to take 30+ seconds.
    * Fixed a problem with hotkey switching on some recent mobile GPUs.
    * Fixed an image corruption issue seen in FireFox 3.
  * Make it conflict with driver 180
  * Make it easier to add the support for new flavours in nvidia-glx-VER.preinst
  * Switch to DKMS patching system (in debian/rules) so as to have different
    patches for different kernel versions

nvidia-graphics-drivers-173, 96
  * Make it conflict with driver 180
  * Make it easier to add the support for new flavours in nvidia-glx-VER.preinst
  * Switch to DKMS patching system (in debian/rules) so as to have different
    patches for different kernel versions

Driver 180 will be uploaded to Jaunty (it's ready for the upload) and backported to Intrepid since 180.08 is not stable.

What about 177.82 ?? Becuase in driver 177.80 .png images in Firefox come up as black until you refresh the page .. I think its vital that 177.82 be included as a normal update in Intrepid because of that Firefox image issue.

Also to enable backports I just go System > Admin > Software Sources > Updates yeah ?? or is it a PPA that I have to enable ??

Thanks Alberto.

lunch: 177.82 will be uploaded to intrepid-proposed for testing and then to intrepid-updates.

Driver 180.08 (nvidia-glx-180) has been uploaded to Jaunty. The same package works if you install it in Intrepid.

This bug was fixed in the package nvidia-graphics-drivers-177 - 177.82-0ubuntu1

---------------
nvidia-graphics-drivers-177 (177.82-0ubuntu1) jaunty; urgency=low

  * Add driver 177.82 (LP: #297543):
    * Added support for the following new GPUs:
       o Quadro NVS 450
       o Quadro FX 370 LP
       o Quadro FX 5800
       o Quadro FX 4800
       o Quadro FX 470
       o Quadro CX
    * Fixed a problem on recent mobile GPUs that caused a power management resume from S3 to take 30+ seconds.
    * Fixed a problem with hotkey switching on some recent mobile GPUs.
    * Fixed an image corruption issue seen in FireFox 3.
  * Make it conflict with driver 180
  * Make it easier to add the support for new flavours in nvidia-glx-VER.preinst
  * Switch to DKMS patching system (in debian/rules) so as to have different
    patches for different kernel versions

 -- Alberto Milone (tseliot) <email address hidden> Sun, 30 Nov 2008 18:23:09 +0100

What about intrepid-proposed though?

Vadim: I need someone from the SRU team to approve this FFE. Then driver 180 will have to be copied to the backports repository.

173 driver update is fine for intrepid-proposed. Alberto, thanks for preparing this, please find someone in #ubuntu-devel to upload this (I'm a bit busy ATM, sprint).

180 is fine for intrepid-backports, of course. Since it's a new package, I'm also willing to consider putting it into intrepid-updates, unless the binary packages which it builds overlap with the ones from 173 (which I don't think).

For the impatient:

I downloaded
* nvidia-180-kernel-source NVIDIA binary kernel module source
* nvidia-180-modaliases Modaliases for the NVIDIA binary X.Org driver
* nvidia-glx-180 NVIDIA binary Xorg driver

from https://edge.launchpad.net/~anders-kaseorg/+archive and installed them (had to deactivate the previously installed driver using Jockey before I could install). After installation I rebooted, enabled the 180 driver in Jockey and rebooted again.

The packages are for Jaunty but I installed them on Intrepid which seems to work OK for me. The OOo issues and the logout screen garbage are fixed for me, the systray icon background issue is still there (I'm using KDE4).
The only weird thing I've notices so far is a slight font problem in that sometimes it looks like some pixels from the caracters aren't drawn. I prefer this to the other issues with the older drivers.

-----
This info is provided AS IS and I make absolutely NO WARRANTIES whether express or implied. If you decide to use the info you do so at your own risk!

Shock: the impatient can install my packages for Jaunty (which contain all the purevideo goodness).

> the impatient can install my packages for Jaunty

From where? I've made sure to keep up-to-date, and I still don't see them via apt-get. I've assumed that I just need to be a bit more patient, but you seem to imply that even the impatient should be able to see them by now.

Alberto: Where are the packages available from? I wasn't able to find them.
They show up in the Jaunty queue https://launchpad.net/ubuntu/jaunty/+queue but I don't think they've been built yet. Launchpad search returns no matches: https://launchpad.net/ubuntu/jaunty/+search?text=nvidia-glx-180

I completely understand that the packages are in universe, but in the grand scheme of things Canonical is doing a very poor job especially in light of bug #1. Weeks have passed since the driver has been released by Nvidia and it's still not available in Ubuntu. I consider good hardware support the bare _minimum_ for us to stand a chance of resolving bug #1.

Please let me assure you, Alberto, that in no way I consider you responsible for any of this -- In fact I have nothing but praise for your work so far. Instead I think Canonical needs to find better ways than relying on the community for basic hardware support such as video. For example, Nvidia provides OpenSuse packages for their video drivers, I would assume the same would be possible for Ubuntu.

Erm, I don't consider a -beta- software to be available right away on
everybody's computer.

Why not? If the beta happens to be way better than the previous stable release where's the problem?

nvidia release cycle is such as we get fully usable "beta" drivers.
Should we remove all the softwares with a version number < 1.0 from the
repositories? ;)
"beta" or "release" is not a problem: It works! Other drivers do not work.

Xavier

On Wed, Dec 3, 2008 at 8:17 AM, ma2412ma <email address hidden> wrote:

> Why not? If the beta happens to be way better than the previous stable
> release where's the problem?
>
> --
> Update Package: nVidia 180.06
> https://bugs.launchpad.net/bugs/297543
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Intrepid Ibex Backports: New
> Status in "nvidia-graphics-drivers-177" source package in Ubuntu: Fix
> Released
> Status in "nvidia-graphics-drivers-180" source package in Ubuntu: Fix
> Released
> Status in nvidia-graphics-drivers-177 in Ubuntu Intrepid: In Progress
> Status in nvidia-graphics-drivers-180 in Ubuntu Intrepid: In Progress
> Status in nvidia-graphics-drivers-177 in Ubuntu Jaunty: Fix Released
> Status in nvidia-graphics-drivers-180 in Ubuntu Jaunty: Fix Released
>
> Bug description:
> Release Highlights, 180.06
>
> http://www.nvnews.net/vbulletin/showthread.php?t=123072
>
> * Added support for CUDA 2.1.
> * Added initial support for PureVideo-like features on Linux via the new
> VDPAU API (see the vdpau.h header file installed withthe driver).
> * Added new workstation performance optimizations.
> * Enabled the X Render "GlyphCache" by default.
> * Disabled shared memory X pixmaps by default; see the"AllowSHMPixmaps"
> option.
> * Fixed a regression that could result in window decorationcorruption
> when running Compiz using Geforce 6 and 7 series GPUs.
> * Improved X pixmap placement on GeForce 8 series and later GPUs.
> * Improved compatibility with recent Linux kernels.
> * Improved stability on some GeForce 8 series and newer GPUs.
>
>
> Release Highlights, 177.82:
>
> * Added support for the following new GPUs:
> o Quadro NVS 450
> o Quadro FX 370 LP
> o Quadro FX 5800
> o Quadro FX 4800
> o Quadro FX 470
> o Quadro CX
> * Fixed a problem on recent mobile GPUs that caused a power management
> resume from S3 to take 30+ seconds.
> * Fixed a problem with hotkey switching on some recent mobile GPUs.
> * Fixed an image corruption issue seen in FireFox 3.
>
> http://www.nvnews.net/vbulletin/showthread.php?p=1842773
>
> Tested without any notable issues. Test with Jaunty ?
>

tis 2008-12-02 klockan 17:27 +0000 skrev Shock:
> Alberto: Where are the packages available from? I wasn't able to find them.

They will be here:

http://archive.ubuntu.com/ubuntu/pool/restricted/n/nvidia-graphics-drivers-180/

For now, the binaries are here:

https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/180.08-0ubuntu1/+build/802788

/Mikael

--
<email address hidden>

Plus ça change, plus c'est la même chose

Per this thread http://www.nvnews.net/vbulletin/showthread.php?t=124059 nvidia driver version 180.11 (beta) was released.

Release Highlights:

    * Added support for the following new GPUs:
          o GeForce 9400M
    * Fixed font corruption on GeForce 6 and 7 series GPUs when the GlyphCache setting is enabled.
    * Fixed a memory leak problem when the GlyphCache setting is enabled.
    * Added support for GVO full-range color.
    * Fixed a problem parsing the monitor sync range X config file options.
    * Improved VDPAU error detection and reporting.
    * Improved VDPAU support for some video bitstreams.

The 180.11 NVIDIA Accelerated Linux Graphics Driver Set for Linux/x86 is available for download via FTP.
The 180.11 NVIDIA Accelerated Linux Graphics Driver Set for Linux/x86-64 is available for download via FTP.

Please see the README (x86, x86-64) for more information about this release.

It seems to fix the font corruption issue I was mentioning earlier. Until we get the 180.11 driver in the repos (if we get it) there a couple of alternative fixes for the font corruption issue:
 1) set GlyphCache to 0: nvidia-settings -a GlyphCache=0
Some reports indicate that in some cases the InitialPixmapPlacement needs to be also set to 0 to get rid of the text corruption. YMMV
 2) disable sub-pixel hinting in the anti-aliasing settings.

-----
This info is provided AS IS and I make absolutely NO WARRANTIES whether express or implied. If you decide to use the info you do so at your own risk!

For what it is worth, I agree with the caution of the packagers in this case.
The driver is tagged beta for a reason. Yes, it's true that most of my Kubuntu Intrepid issues went away with the upgrade to nvidia driver version 180.06. No, that was not the end of it.
As documented on the Nvidia forum, I'm still required to run this after every restart of X, including after every suspend/hibernate/reboot:

nvidia-settings -a GlyphCache=0 -a InitialPixmapPlacement=0

I also agree with Xavier and all since we can at least see "something" on our screens in stead of being dumped to a command line prompt without network support since that's apparently another stupid change in Intrepid.

here is what i did:

$ dget http://archive.ubuntu.com/ubuntu/pool/restricted/n/nvidia-graphics-drivers-180/nvidia-graphics-drivers-180_180.08-0ubuntu1.dsc
$ pbuilder-intrepid build nvidia-graphics-drivers-180_180.08-0ubuntu1.dsc

mattcasters, the requirement to run this command after every restart of X might have been resolved with 180.11 as Shock pointed out.

Anyway, when will 180 (now 180.11) be added to the backports repository of Intrepid?

mattcasters: glyphcache is enabled by default now. See the changelog of 180.06 ("Enabled the X Render "GlyphCache" by default.")

Shock: I have packaged the new release (I was affected by the font corruption bug too) and I have just asked a core developer to upload it to Jaunty.

ma2412ma: it depends on how busy core developers are. I'll let you know when the new packages are available in the backports.

Alberto,

Thanks again for all your work. I am most appreciative of it, I'm sure others are too -- they're prolly just a bit more shy in voicing that :)

I was merely commenting on the fact that you can always make a decision either way: get 180 out there immediately or after a bit of testing. As 180.11 proves you can make a case for both. In this case I think the best thing to do was give the nv packagers a bit more time to fix a few annoying (not critical) bugs.

mattcasters: "get 180 out there immediately or after a bit of testing."

Who does the testing?
What is the downside of making it available immediately without pushing it as default/recommended?

Shock, these are good questions and I don't know the answers. But that just proves that you and I are not in a position to evaluate the situation.
It's not about being right or wrong: you either trust the team and compliment Alberto & the rest with their good work or you don't. (I do) Have a little faith :-)

The reason why I'm against them is because I had stability issues - screen
would sometimes flicker and whole computer just pause. However I installed
the driver via nvidia's own installer - so I'm waiting for a package to be
available in ubuntu for testing first.

It's not a reason - you always can roll back to the older driver in this
case ;)

2008/12/3 Vadim Peretokin <email address hidden>

> The reason why I'm against them is because I had stability issues - screen
> would sometimes flicker and whole computer just pause. However I installed
> the driver via nvidia's own installer - so I'm waiting for a package to be
> available in ubuntu for testing first.
>
> --
> Update Package: nVidia 180.06
> https://bugs.launchpad.net/bugs/297543
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

There are two separate issues here, albeit somewhat related. One is keeping the current, stable, driver current. That is the 177.82 update.

The other issue is making the latest driver available as soon as possible for testing, and for those who want to live on the edge. I've updated the description to match this, since it is the bulk of the comments.

When it was 173 and 177, Ubuntu did a good job of making both available in Jockey, labeling one as recommended and the other as beta. When the status changed, so did the presentation in Jockey. I see no reason not to continue in that way as new drivers come out and their status evolves.

The only difference I see between compatible (with the driver) release, e.g., Hardy, Intrepid and Jaunty, is simply whether to put the updated driver(s) in main or backport.

FWIW, I tried 180.08 with Hardy, saw a problem (menu highlighting), and installed 177.82 by hand. For Jaunty, I've been using 177.82 while waiting for a 180 package to hit the repositories, but if that doesn't happen soon, I'll un-install the package and install 180.11 (or whatever is then current) by hand.

@Vadim Peretokin: The simple fact that the drivers are available doesn't force you to install them, see my earlier comments. The point is: you have a choice of installing them or not AND if something goes wrong you can roll back cleanly. Freedom of choice. Frankly, I wouldn't have such a big problem installing them using the nvidia installer if there weren't those reports about breaking the system if you do so.

I'm running Ubuntu on a production machine so I need it to have high availability and be usable. Maybe this is making me overly cautious in installing using the nvidia installer and so I would like to have the option of installing using a package (cleaner, IMHO) especially since the Recommended driver (177) had serious issues with OpenOffice (heavy screen corruption -- Really?! On a production machine running a stable version?! I'm not running a development version, BTW). I'm already sorry I upgraded to Intrepid: upgrade broke the system so I had to do a clean install only to find out that the office suite I need to use every day has the side effect of causing screen corruption in some way.

This is why I'm saying that I think Canonical needs to do a far better job in terms of hardware support and not simply rely on the community especially because bug #1 is a target for the company. The fact that ther target seems to be to provide the same level of usability as Windows makes me run Ubuntu and not OpenSuse on my work machine.

Maybe this seems like a rant to you -- it's not meant to be. It's simply some stuff that's been on my mind lately. I think it's not just me that feels the same way and I think we need to voice our opinions if we want resolution.

My 2c.

Mikael wrote:
> They will be here:
> http://archive.ubuntu.com/ubuntu/pool/restricted/n/nvidia-graphics-drivers-180/

They *are* there, but they still show up as new in the Jaunty queue, and are not available via apt*, yet.

Alberto wrote:
> I have packaged the new release (I was affected by the font corruption bug too) and I have
> just asked a core developer to upload it to Jaunty.

You are referring to 180.11? Great! And thanks again. :-)

Noel: yes, I was referring to 180.11

After talking to Mario about using the backports for driver 180 I came to the conclusion that we can use intrepid-proposed instead. The modalias package of 180 won't be installed by default, therefore Jockey won't suggest 180 unless you install nvidia-180-modaliases. I think this is a good compromise.

Alberto,

Thanks again for the great work. I'm running with your 180.11 packages and all is well in the universe again :)

I tried 180.11 today for testing the CUDA and the VDPAU interfaces. I noticed that on my M1330 running Intrepid the login screen after resume is missing. Moreover, without the acpi_sleep=S3_bios kernel option the system hangs with a black screen after resuming from suspend, and a reboot is required.

Well, not a problem for myself but its so boring using recovery and reinstall a nVidia driver.... ;)

Something is wrong with Jaunty.... !? or someone must push correct trigger.... ;)

http://archive.ubuntu.com/ubuntu/pool/main/n/

plun@plun:~$ sudo apt-get install nvidia-180-modaliases
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package nvidia-180-modaliases

Shock wrote:
> I'm running with your 180.11 packages

Stecklum wrote:
> I tried 180.11 today for testing [on] Intrepid

Plun wrote:
> $ sudo apt-get install nvidia-180-modaliases
> ...
> E: Couldn't find package nvidia-180-modaliases

I am seeing the same as Plun:

 # lsb_release -r; date; apt-get update; apt-cache search nvidia modaliases
 Release: 9.04
 Wed Dec 3 15:09:28 EST 2008
 ...
 Fetched 9138kB in 25s
 Reading package lists... Done
 nvidia-173-modaliases - Modaliases for the NVIDIA binary X.Org driver
 nvidia-177-modaliases - Modaliases for the NVIDIA binary X.Org driver
 nvidia-71-modaliases - Modaliases for the NVIDIA binary X.Org driver
 nvidia-96-modaliases - Modaliases for the NVIDIA binary X.Org driver

Nor do I see anything different with Intrepid, even though I enabled everything, including -proposed and -backports.

plun, Noel: If you're asking where to get Alberto's 180.11 packages, I got them from the Jaunty build queue: https://launchpad.net/ubuntu/jaunty/+queue

Try the NEW and DONE queues. Hope it helps.

Later, this link might be of help https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/

Nope.... I have 2 choices, directly from nVidias site or a working hardware manager.... not from Launchpad... ;)
I have no problem to install these drivers.. works great since I install them 12 hours ago directly from nVidia.

Just a principle.... and catching bugs with the prefered way to install.

They show up in Jaunty now after doing apt-get update.

after I made NVIDIA-Linux-x86_64-177.82-pkg2.run all were the best. But as soon as I began to change HDD from they original places to the other I met the strange oobstackle to boot into X mode. I"m sure that after sudo /etc/init.d/gdm stop (start) сd /home/(name)/Desktop || sudo sh ./NVIDIA-Linux-x86_64-177.82-pkg2.run => sudo /etc/init.d/gdm start sudo startx) all was GOOD!!!

suspend stopped working completely with 180.XX
laptop dead on weak-up, hard-kill / reboot solves the problem..
oldschool solutions will nt apply anymore...
bug

http://www.nvnews.net/vbulletin/showthread.php?p=1865016#post1865016

About suspend... http://torvalds-family.blogspot.com/2008/12/debugging-hell.html
Linus challenge

Also.... a *NIX box can be killed with MagicSysRq ;)

http://fosswire.com/2007/09/08/fix-a-frozen-system-with-the-magic-sysrq-keys/

And BIOS uptodate ? Dell PCs are a complete mess... just visit support !

Thank you very much Mr Milone I installed your packages for 177.82 and it went beautifully .. the only thing is that it should tell you to restart your computer after you install the deb but I guess installing from deb is not exactly the way you should do it.

Also I have to say that 2D performance seems to be better if installing from a deb than installing from a .run file ... I think Mr Milone did a few tweaks to improve this.

Once again thanks for your hard work Mr Milone.

> Thank you very much Mr Milone

Sounds like "Mr Corleone" :)

2008/12/6 lunch <email address hidden>

> Thank you very much Mr Milone I installed your packages for 177.82 and
> it went beautifully .. the only thing is that it should tell you to
> restart your computer after you install the deb but I guess installing
> from deb is not exactly the way you should do it.
>
> Also I have to say that 2D performance seems to be better if installing
> from a deb than installing from a .run file ... I think Mr Milone did a
> few tweaks to improve this.
>
> Once again thanks for your hard work Mr Milone.
>
> --
> Update Package: nVidia 180.11
> https://bugs.launchpad.net/bugs/297543
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

Accepted nvidia-graphics-drivers-96 into intrepid-proposed, please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Accepted nvidia-graphics-drivers-173 into intrepid-proposed, please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Accepted nvidia-graphics-drivers-177 into intrepid-proposed, please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

That's weird. It's called nvidia-graphics-drivers-177 in the changelog,
however update manager shows it a nvidia-glx-177

Why did you set it to "Fix Released"? The drivers are in intrepid-proposed,
not intrepid-updates.

lunch: Please don't change the status to Fix Released when this is not the case. Reverted status changes.

I have opened Bug 306315 to track the problem reported by huiii and myself that once updated to 180.11 as enabled by the fix to this bug, resume is broken.

From looking at the nv forums, it seems that the suspend/resume issues with the current 180.xx drivers are quite widespread. Until there is a fix (from nv or a workaround from Ubuntu) it's impossible to get too excited about this!

nvidia-graphics-drivers-177 in intrepid-proposed are working out fine so far
- run compiz, and graphics-intensive games (quake wars, savage 2) without a
hitch.

I got the 180 driver installed, but I had to upgrade to Jaunty alpha since I couldn't get the package to work on 8.10 (the installer failed, but it didn't give me an error message). 180 seems to have fixed (or at least significantly improved) the Firefox scrolling issue (I think it was this bug: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/125970). It crashed once with smooth scrolling on--the display became corrupted and parts the desktop and the Firefox window were rendered in the wrong place--but I don't really have time to see if the problem is repeatable, so I'll just leave smooth scrolling off for now.

I haven't tried standby yet, so I can't comment on that.

I've tried the Nvidia 180 driver on Kubuntu 8.10. I no longer experience the video garbage bug (https://bugs.launchpad.net/ubuntu/+source/kubuntu-kde4-meta/+bug/254468) whether using Compiz or not. It's also cleared up a video artefact bug that caused severe rendering issues when Eclipse was open. So I'm very happy now. :-)

I also had random crashing problems with the Nvidia 177 driver, especially when using Compiz or any OpenGL based application, but as they are random, I will have to wait to see if they still occur.

I'm not too bothered about the suspend/resume issues, as I don't use suspend/resume on this machine. I'd rather have working graphics. :-)

I'm using a Gigabyte GA-M68SM-S2 motherboard, which has an onboard GeForce 7025

Many thanks to those who got this package out there!

180.16 seems to have been released, with many fixes and improved vdpau support.

ftp://download.nvidia.com/XFree86/Linux-x86_64/180.16/

Release announcement: http://www.nvnews.net/vbulletin/showthread.php?p=1873716

Do we want to update this bug, again, to cover the new release, or open another bug?

I just tried 180.16 and the suspend/resume problem still remains. I'm using
a D630, Ubuntu 8.10 32 bit, Nvidia NVS 135M.

Bug 307791 should be used for the 180.16 upgrade.

Updated 180.11.02: http://www.nvnews.net/vbulletin/showthread.php?t=124813

> Bug 307791 should be used for the 180.16 upgrade

Alberto is not subscribed there, and no one has touched the nvidia-glx-180 package since the original 180.11. So three code drops from nvidia (180,11,2, 180,16, 180.18) have gone without an update.

And on the suspend / resume front, that is the subject of Bug 306315. David Chen is asking for some testers.

> David Chen

Sorry ... no way to edit and correct my error ... *Daniel* Chen.

Version 180.18 is out...

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

i build packages and uploaded them to my ppa at

https://launchpad.net/~thomas-creutz/+archive

fre 2009-01-02 klockan 15:04 +0000 skrev Thomas C.:
> Version 180.18 is out...
>
> http://www.nvnews.net/vbulletin/showthread.php?t=125134
>
> i build packages and uploaded them to my ppa at
>
> https://launchpad.net/~thomas-creutz/+archive

Is there a difference between these and the ones here:

https://launchpad.net/~anders-kaseorg/+archive

?

--
<email address hidden>

Varning! E-post till och från Sverige, eller som passerar servrar i
Sverige, avlyssnas av Försvarets Radioanstalt, FRA.
WARNING! E-mail to and from Sweden, or via servers in Sweden, is
monitored by the National Defence Radio Establishment.

Mikael Nilsson schrieb:
> Is there a difference between these and the ones here:
>
> https://launchpad.net/~anders-kaseorg/+archive
>
> ?
>

Oh sorry.. i dont think so.. i have not found this package before :-/

https://launchpad.net/~thomas-creutz/+archive has the package for 8.10 while
https://launchpad.net/~anders-kaseorg/+archive has it for the in-development
9.04

Thomas Creuz's ppa workes perfectly for me with a GeForce 6600 GT. No more title bar glitches
Thanks.

I just noticed that with new 180.18 drivers the generated modaliases file is bogus. This is because there are two very short consecutive objects now (before the objects with pciids) and nvidia_supported thinks it found it right. Attached is a debdiff that fixes the issue for now (by ensuring that there are necessary zeroes, i.e. that numbers are at least int32).

Builds for jaunty and intrepid should appear in my ppa (https://launchpad.net/~snaury/+archive) soon.

Re: the original SRU bug that this was for 177.82 (Before it got hijacked for the 180 series drivers)

I've got a variety of machines that have been using 177.82 from proposed since the day 177.82 was released. One of these machines was w/ a more modern GPU and affected directly by the 30+ second suspend bug. The bug is resolved by 177.82, and i've not seen any other regressions in using it.

Lots of positive feedback about the updated 177.82, and no regression reports, so I consider this verified.

180 is new, so there is no regression potential, so this can go to -updates as well.

This bug was fixed in the package nvidia-graphics-drivers-177 - 177.82-0ubuntu0.1

---------------
nvidia-graphics-drivers-177 (177.82-0ubuntu0.1) intrepid-proposed; urgency=low

  * Add driver 177.82 (LP: #297543):
    * Added support for the following new GPUs:
       o Quadro NVS 450
       o Quadro FX 370 LP
       o Quadro FX 5800
       o Quadro FX 4800
       o Quadro FX 470
       o Quadro CX
    * Fixed a problem on recent mobile GPUs that caused a power management resume from S3 to take 30+ seconds.
    * Fixed a problem with hotkey switching on some recent mobile GPUs.
    * Fixed an image corruption issue seen in FireFox 3.
  * Make it conflict with driver 180
  * Make it easier to add the support for new flavours in nvidia-glx-VER.preinst
  * Switch to DKMS patching system (in debian/rules) so as to have different
    patches for different kernel versions
  * Add debian.binary/patches/NVIDIA-177.82_2.6.28.patch to ensure compatibility
    with 2.6.28 kernels (LP: #303107)

 -- Alberto Milone (tseliot) <email address hidden> Sun, 30 Nov 2008 18:23:09 +0100

I did a jaunty -> intrepid-updates backport of -180:
  https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/180.11-0ubuntu1~intrepid1

I'll NEW it tomorrow, when the package built.

Did anyone test the updated -96 and -173 drivers?

I NEWed -180 in intrepid-updates.

i hope there will be an official driver update after 177.82 for intrepid, there are broken tittle bars (with compiz), appeared after updating from 8.04 to 8.10; using GeForce 6200... this issue was not present in ubuntu hardy!

nvidia-glx-177 177.82-0ubuntu0.1

this update does not fix the issue, the tittle bars are still broken!

Martin, what repo do i need to give your nvidia package 180.11-0ubuntu1~intrepid1
 a try?

Hello,

evgen [2009-01-08 9:52 -0000]:
> Martin, what repo do i need to give your nvidia package 180.11-0ubuntu1~intrepid1
> a try?

It's in intrepid-updates now, which is enabled by default.

nvidia-glx-180 | 180.11-0ubuntu1~intrepid1 | intrepid-updates/restricted | amd64, i386

Thank you Martin, it works nice and fixes the issue with title bars on my box with nvidia GeForce 6200 (and enabled compiz).

180.* upgrade request superseded by Bug 315169, which is for 180.22 (the first non-beta release in the 180 series). So that needs to be handled as 180.11 (nvidia beta) was handled.

Please keep any discussion of future upgrades to new bugs as this bug is solved. That 180.22 release has already been uploaded, but it's in the NEW queue.

Mario Limonciello
Dell | Linux Engineering
<email address hidden>

-----Original Message-----
From: <email address hidden> on behalf of Noel J. Bergman
Sent: Fri 1/9/2009 7:05 PM
To: <email address hidden>
Subject: [Bug 297543] Re: Update Package: nVidia 180.11

180.* upgrade request superseded by Bug 315169, which is for 180.22 (the
first non-beta release in the 180 series). So that needs to be handled
as 180.11 (nvidia beta) was handled.

--
Update Package: nVidia 180.11
https://bugs.launchpad.net/bugs/297543
You received this bug notification because you are a member of The Dell
Team, which is a subscriber of a duplicate bug.

> Please keep any discussion of future upgrades to new bugs as this bug is solved

Oh, gee, thanks for the lesson in netiquette. :-, If you re-read my post without a knee-jerk response, you will note that it is a reference to Bug 315169 -- you know, the new report for the new version -- for people who want to keep track of the 180 series, rather than see folks continue to re-purpose this report, which happened several times previously.

> 180.22 release has already been uploaded, but it's in the NEW queue.

Yes, I know. I'd already commented on that release in the "appropriate" bug reports. Still waiting for response. One of the points I raised was that it is STILL in the new queue. Nothing has come out of the NEW queue since 180.11.

If nobody tests the updated -96 and -173 versions, I'll remove those from -proposed in a week.

Both are working fine with Savage 2 (3d game, requires min opengl 2.0, effects heavy).

Thanks, Vadim!

This bug was fixed in the package nvidia-graphics-drivers-96 - 96.43.09-0ubuntu1.1

---------------
nvidia-graphics-drivers-96 (96.43.09-0ubuntu1.1) intrepid-proposed; urgency=low

  * Make it conflict with driver 180 (LP: #297543)
  * Make it easier to add the support for new flavours in nvidia-glx-VER.preinst
  * Switch to DKMS patching system (in debian/rules) so as to have different
    patches for different kernel versions

 -- Alberto Milone (tseliot) <email address hidden> Sat, 01 Nov 2008 16:47:04 +0100

This bug was fixed in the package nvidia-graphics-drivers-173 - 173.14.12-1-0ubuntu5.1

---------------
nvidia-graphics-drivers-173 (173.14.12-1-0ubuntu5.1) intrepid-proposed; urgency=low

  * Make it conflict with driver 180 (LP: #297543)
  * Make it easier to add the support for new flavours in nvidia-glx-VER.preinst
  * Switch to DKMS patching system (in debian/rules) so as to have different
    patches for different kernel versions

 -- Alberto Milone (tseliot) <email address hidden> Sun, 30 Nov 2008 18:40:48 +0100

Hi!

GeForce 6600GT. The bug was exist in 177 version of driver, after update to 180 it's gone.