Ubuntu
nvidia-graphics-drivers package

x wont start after latest update nvidia altarnate error

Bug #615925 reported by las
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

After updates X didnt start.So tried to fail safe(recov mode) but that didn't work either.after removing all nvidia (current,173,96) fail safe worked.then ran synaptic to get nvidia-current.It gave me this.

Setting up nvidia-current (256.35-0ubuntu2) ...
update-alternatives: using /usr/lib/nvidia-current/ld.so.conf to provide /etc/ld.so.conf.d/GL.conf (gl_conf) in auto mode.
update-alternatives: warning: skip creation of /usr/lib32/vdpau/libvdpau_nvidia.so.1 because associated file /usr/lib32/nvidia-current/vdpau/libvdpau_nvidia.so.1 (of link group gl_conf) doesn't exist.
update-alternatives: warning: skip creation of /usr/lib32/libvdpau_nvidia.so because associated file /usr/lib32/nvidia-current/vdpau/libvdpau_nvidia.so (of link group gl_conf) doesn't exist.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: nvidia-current 256.35-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-14.20-generic 2.6.35
Uname: Linux 2.6.35-14-generic i686
Architecture: i386
DRM.card0.VGA.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1280x1024 1024x768 1024x768 1024x768 800x600 800x600 800x600 640x480 640x480 640x480 720x400 720x350
 edid-base64: AP///////wAQrBkzU0YwMBYJAQEIHBWA6A2SoFdHmCYQSE+lSgBhWUVZgYAxWQEBAQEBAQEBEAvQtCBeYxASbGIIC8gQAAAaAAAA/wAyMjg3OEMwMEZTNjkKAAAA/ABERUxMIDgyOEZJCiAgAAAA/QAyeB5G/wAKICAgICAgAGc=
Date: Tue Aug 10 21:11:20 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100215)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Kobian KN6100M
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-14-generic root=UUID=32eb576a-bffd-44df-90ce-526c0652eb1c ro spUser Nameh quiet spUser Nameh
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: nvidia-graphics-drivers
dmi.bios.date: 06/01/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: KN6100M
dmi.board.vendor: Kobian
dmi.chassis.type: 3
dmi.chassis.vendor: Kobian
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/01/2007:svnKobian:pnKN6100M:pvr:rvnKobian:rnKN6100M:rvr:cvnKobian:ct3:cvr:
dmi.product.name: KN6100M
dmi.sys.vendor: Kobian
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-14-generic

Revision history for this message
las (bandara-ls) wrote :
Revision history for this message
Joshua Moravec (joshua-nofacade-moravec) wrote :

I have this problem in amd64.

tags: added: amd64
Revision history for this message
las (bandara-ls) wrote :

could this be the reason...

https://lists.ubuntu.com/archives/ubuntu-x/2010-August/000931.html

Summary for the impatient:
********************************************************************
A new X server is soon to be uploaded which requires all the
drivers to be rebuilt. Be careful when upgrading in the next few
days.
********************************************************************

As promised earlier in the cycle, we've got the second X server
transition coming up. This will take us to X server 1.9, which features
improvements to startup time, some memory usage improvements, and many
DRI2 fixes.

The 1.9 server has a new input and video ABI which means existing driver
packages will break.

The server needs to be uploaded first so the new drivers build against
the correct ABI, which means that there will be a period where safe
upgrades will have held-back packages. The dependencies should ensure
that you won't accidentally get a non-working combination of X server
and drivers, but be careful if an upgrade wants to remove X packages.

Happy testing!

Revision history for this message
las (bandara-ls) wrote :

After removing all nvidia packages and installing nvidia-185-libvdpau(Transitional package for nvidia-185-libvdpau) and running jocky (harsware drivers) to create new xorg.conf fixed it for me..

Revision history for this message
las (bandara-ls) wrote :

I think of it as a work around

Revision history for this message
bugbot (bugbot) wrote :

Hey las,

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

Changed in nvidia-graphics-drivers (Ubuntu):
status: New → Incomplete
las (bandara-ls)
Changed in nvidia-graphics-drivers (Ubuntu):
status: Incomplete → Fix Released
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.