Ubuntu
update-manager package

[nvidia] nvidia-glx-177 -> -180 replacement does not work for cdrom only upgrades

Bug #366962 reported by keepitsimpleengr
2
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-180 (Ubuntu)
Invalid
Undecided
Unassigned
update-manager (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Binary package hint: update-manager

The upgrade has produce and unusable system using the 2.6.8-11 kernel due to garbage on one screen.
===
After the update with alternate amd64 from 8.10 to 9.04 screen 1 is blank and screen 0 has altered resolution.
---
Ran nvidia-settings and it reported nvidia drivers were not being used and to run as root nvidia-xconfig.
This produced garbage on screen 0

Booted 9.04 in recovery, ran fix xorg.conf. Then boot failed because "no screen found".

Booted 9.04 in recovery, ran fix broken packages. "no screen found" again.

Copied old xorg.conf to /etc/X11, booted 9.04. This produced garbage on screen 0, screen 1 was drawn properly but menus did not work.

Booted 8.10 kernel which worked normally, compared nvidia packages using Synaptic with a successful 9.04 upgrade on 32 bit. After comparison, removed nvidia-glx-1980-dev and added envyng-core.

Still garbage on screen 0, screen 1 was drawn properly and menus did not work when booting with 9.04 kernel.

The 32 bit 9.04 has nvidia-108-libvdpau but cannot find it for amd64 using Synaptic. However, amd64 shows it with "dpkg -l | grep nvidia". see below…

Can now run in old 8.10 kernel boot.
---
:~$ apt-cache policy update-manager
update-manager:
  Installed: 1:0.111.7
  Candidate: 1:0.111.7
  Version table:
 *** 1:0.111.7 0
        500 cdrom://Ubuntu 9.04 _Jaunty Jackalope_ - Release amd64 (20090420.1) jaunty/main Packages
        500 http://mirrors.us.kernel.org jaunty/main Packages
        100 /var/lib/dpkg/status

:~$ dpkg -l | grep nvidia
ii nvidia-173-modaliases⋯173.14.16-0ubuntu1⋯Modaliases for the NVIDIA binary X.Org drive
ii nvidia-180-kernel-source⋯180.44-0ubuntu1⋯NVIDIA binary kernel module source
ii nvidia-180-libvdpau⋯180.44-0ubuntu1⋯Video Decode and Presentation API for Unix
ii nvidia-180-modaliases⋯180.44-0ubuntu1⋯Modaliases for the NVIDIA binary X.Org drive
ii nvidia-71-modaliases⋯71.86.08-0ubuntu1⋯Modaliases for the NVIDIA binary X.Org drive
ii nvidia-96-modaliases⋯96.43.10-0ubuntu1⋯Modaliases for the NVIDIA binary X.Org drive
ii nvidia-common⋯0.2.11⋯Find obsolete NVIDIA drivers
rc nvidia-glx-177⋯177.82-0ubuntu0.1⋯NVIDIA binary Xorg driver
ii nvidia-glx-180⋯180.44-0ubuntu1⋯NVIDIA binary Xorg driver
rc nvidia-glx-180-dev⋯180.44-0ubuntu1⋯NVIDIA binary Xorg driver development files
rc nvidia-glx-new-dev-envy⋯173.14.12+2.6.24.503-503.30⋯NVIDIA binary XFree86 4.x/X.Org 'new' driver
rc nvidia-glx-new-envy⋯173.14.12+2.6.24.503-503.30⋯NVIDIA binary XFree86 4.x/X.Org 'new' driver
rc nvidia-kernel-common⋯20051028+1+nmu2ubuntu2⋯NVIDIA binary kernel module common files

:~$ dpkg -l | grep envy
ii envyng-core⋯2.0.1ubuntu1⋯install the ATI or the NVIDIA driver
rc nvidia-glx-new-dev-envy⋯173.14.12+2.6.24.503-503.30⋯NVIDIA binary XFree86 4.x/X.Org 'new' driver
rc nvidia-glx-new-envy⋯173.14.12+2.6.24.503-503.30⋯NVIDIA binary XFree86 4.x/X.Org 'new' driver

ii nvidia-settings⋯180.25-0ubuntu1⋯Tool of configuring the NVIDIA graphics driv

Tags: jaunty
Revision history for this message
keepitsimpleengr (keepitsimpleengineer) wrote :
Revision history for this message
keepitsimpleengr (keepitsimpleengineer) wrote :

Attached xorg.conf files…

Revision history for this message
keepitsimpleengr (keepitsimpleengineer) wrote :

Note about xorg.conf files.

The amd64 system has two video cards. Each video card supports only one monitor. Xinerama, twinview are not used.

Both screens are composited.

Note: After the upgrade running the 8.10 kernel, menu actions on screen 1 cause actions to occur on screen 0. ???

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

The previous nvidia-glx-177 driver is no longer supported in jaunty, this caused the system to select the nvidia-glx-180 driver instead. Now because this was a CDROM only upgrade the nvidia-glx-180 driver could not be found (its not on the CD) and it selected the "nv" driver.

Please use jockey to install the updated driver in your jaunty kernel. I will add code that warns about this.

summary: - screen 0 garbage after amd64 8.10>9.04 upgrade w/nvidia
+ [nvidia] screen 0 garbage after amd64 8.10>9.04 upgrade w/nvidia
Michael Vogt (mvo)
summary: - [nvidia] screen 0 garbage after amd64 8.10>9.04 upgrade w/nvidia
+ [nvidia] nvidia-glx-177 -> -180 replacement does not work for cdrom only
+ upgrades
Changed in update-manager (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
keepitsimpleengr (keepitsimpleengineer) wrote :

Michael...

The 180 driver was being used by 8.10, and was in use by the system after upgrade when booted from 8.10 kernel, from proposed I think.

I will test this as soon as a new mainboard arrives (next day or two) and is installed (original, marginal one failed during repeated reboots).

Thanx

Revision history for this message
Michael Vogt (mvo) wrote :

Hello keepitsimpleengr,

thanks for this added information. I re-read the report and indeed nvidia-glx-180 is installed. I open a bug task against nvidia-glx-180 if its not working properly.

There is still a problem in update-manager here (also a smaller one) that it does not warn if it has to remove the nvidia driver in case of cdrom only upgrades (so I keep the u-m task open).

Changed in update-manager (Ubuntu):
importance: Medium → Low
Revision history for this message
keepitsimpleengr (keepitsimpleengineer) wrote :

Michael...

New mainboard installed, testing revealed power supply problems directly affecting video interface cards (which may be the source of my problem). New power supply due in in two days.

Revision history for this message
keepitsimpleengr (keepitsimpleengineer) wrote :

Michael...

After motherboard replacement, GRUB fails to boot, Bug https://bugs.launchpad.net/bugs/371427

Revision history for this message
keepitsimpleengr (keepitsimpleengineer) wrote :

Michael...

GRUB "fixed".

On boot of 9.04, screen resolution substantially reduced. "Hardware Drivers" reports Nvidia Version 180 active and in use" and is apparently not true.

nvidia-settings reports nvida driver not installed.

Restarted in recovery and ran xfix from rescue menu.

"Hardware Drivers" not reports no nvidia drivers in use-selected Version 180, restarted.

used nvidia-settings to set up dual monitors, primary monitor has been changed from origiginal, cannot change wit nvidia-settings. see https://bugs.launchpad.net/bugs/372274

update manager did not properly load/update comiz-fusion, see https://bugs.launchpad.net/bugs/371973

Update-manager failed to use existing nvidia version 180 on update.

System now restored more or less to original working condition, only big problem is with gnome panel, see: https://bugs.launchpad.net/bugs/346964 and http://bugzilla.gnome.org/show_bug.cgi?id=581502

Bryce Harrington (bryce)
tags: added: jaunty
Revision history for this message
bugbot (bugbot) wrote :

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: New → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

We're closing this bug since it is has been some time with no response from the original bug reporter. However, if the issue still exists in the latest development version of Ubuntu and you are the original reporter please feel free to reopen with the requested information. If you are not the original reporter, please don't reopen this one but instead file a new bug and reference this one.

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.