Ubuntu
nvidia-graphics-drivers-180 package

X doesn't start automatically any more after installing restricted nvidia drivers

Bug #436578 reported by tankdriver on 2009-09-25

This bug report is a duplicate of: Bug #434361: gdm sometimes fails to switch to VT7 after new upstart merge. Edit Remove

This bug affects 6 people

Affects		Status	Importance	Assigned to	Milestone
	nvidia-graphics-drivers-180 (Ubuntu)	New	Undecided	Unassigned
	usplash (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: xorg

Ubuntu Karmic amd64 (daily-live 20090925 + updates) Gnome edition.
device: HP HDX 18-1080EG notebook (nvidia graphics)

After installing the "recommended Hardware Drivers" on my system, X does not start automatically any more.

Steps to reproduce:
- install restricted driver (v185 recomended)
- reboot:
--grub starts
--usplash starts (white ubuntu-logo appears)
--screen black (blinking cursor on topleft)
--after 5 sec screen completely black... forever!

Workaround:
- press a (any) key
- login shell tty1 appears
- press CRL+ALT+F7
- X starts, Ubuntu writing & progressbar appears
- loginscreen
- session successfully started

I recognized this problem last week.
And I found 1 other karmicuser on IRC having exactly the same bug (workaround helped).

ProblemType: Bug
Architecture: amd64
Date: Fri Sep 25 14:17:49 2009
DistroRelease: Ubuntu 9.10
MachineType: Hewlett-Packard HP HDX 18 Notebook PC
NonfreeKernelModules: nvidia
Package: xorg 1:7.4+3ubuntu5
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-10-generic root=UUID=de645ea9-c1df-4976-9bfe-991c2f80f721 ro elevator=deadline quiet splash
ProcEnviron:
PATH=(custom, no user)
LANG=de_AT.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
RelatedPackageVersions:
xserver-xorg 1:7.4+3ubuntu5
libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu5
libdrm2 2.4.13-1ubuntu1
xserver-xorg-video-intel 2:2.8.1-1ubuntu1
xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu2
SourcePackage: xorg
Uname: Linux 2.6.31-10-generic x86_64
dmi.bios.date: 04/30/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.23
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3610
dmi.board.vendor: Quanta
dmi.board.version: 15.29
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.23:bd04/30/2009:svnHewlett-Packard:pnHPHDX18NotebookPC:pvrRev1:rvnQuanta:rn3610:rvr15.29:cvnQuanta:ct10:cvrN/A:
dmi.product.name: HP HDX 18 Notebook PC
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard
fglrx: Not loaded
system:
distro: Ubuntu
architecture: x86_64kernel: 2.6.31-10-generic

Tags:

Revision history for this message

tankdriver (stoneraider-deactivatedaccount) wrote on 2009-09-25:

BootDmesg.gz Edit (14.0 KiB, application/x-gzip)
CurrentDmesg.txt Edit (1.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (5.2 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (12.1 KiB, text/plain; charset="utf-8")
GdmLogOld.txt Edit (43.5 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (38.2 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (868 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.6 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (124.3 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (239.8 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (213 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (15.0 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (48.0 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (6.1 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (21.7 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (22.0 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (52.6 KiB, text/plain; charset="utf-8")

Revision history for this message

NaNo (olivier-n) wrote on 2009-09-25:

I can confirm I have the exact same bug (same steps to reproduce and workaroud).

My configuration is the following :
- Karmic Alpha 4 with all available updated packages installed
- on Fujitsu Siemens Esprimo Mobile X9525 notebook, with nvidia graphics card
- installed restricted driver (v185)

Revision history for this message

tankdriver (stoneraider-deactivatedaccount) wrote on 2009-09-25:

@NaNo:
I found another workaround:
Can you please try to boot Karmic without the "quiet" "splash" boot options?
(Hold SHIFT at startup to get in GRUB, press E, delete the only the words "quiet" and "splash", and press CTL+X)
This worked for me.

Adding the package "usplash", because when Its turned off, it works.

Revision history for this message

Karol Pucyński (kpucynski) wrote on 2009-09-25:

I have the same situation with nvidia 190.32 driver on Karmic Alpha 6.
I don't need to login to workaround. It is enough to press atl+f7 to "resume" booting...

Bryce Harrington (bryce) on 2009-09-26

affects:

xorg (Ubuntu) → nvidia-graphics-drivers-180 (Ubuntu)

Revision history for this message

Roland Hughes (original-seasoned-geek) wrote on 2009-09-26:

I have same problem. Just this morning I applied the last 128 Meg of updates Synaptic said were waiting, machine boots to console login prompt. I actually logged in and did

sudo kdm

to get things working, but will try this other work around now.

How did you guys manage to report this bug? When I click on the "Report a Bug" link this morning, even after logging in, I'm tossed to the wiki which is completely useless for actually reporting a bug, and of even less use for a KUbuntu user.

32-bit Karmic
AMD machine

Revision history for this message

Alex Murray (alexmurray) wrote on 2009-09-27:

This occurs intermittently for me - sometimes I boot successfully and X starts automatically, sometimes I need to do CTRL-ALT-F7 to get it to come up..(and sometimes my machine rarely gets stuck and X doesn't come up at all...)

Revision history for this message

tankdriver (stoneraider-deactivatedaccount) wrote on 2009-09-28:

At the point where tty1 appears:
- login
'status gdm' gives me:
gdm start/running, process 1225

Sebastian Schmidt (baschti-schmidt) on 2009-09-28

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status:	New → Confirmed
status:	Confirmed → New

Revision history for this message

tankdriver (stoneraider-deactivatedaccount) wrote on 2009-09-28:

@ Bryce Harrington:
Please take a look at bug #436530 (possible duplicate), but on an ATI Card.
(bug Bug #436578 was originally filed under xorg)

Revision history for this message

Harry (harry33) wrote on 2009-09-28:

This bug is also a duplicate to this one:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/434361

Revision history for this message

NaNo (olivier-n) wrote on 2009-09-30:

#10

@tankdriver

Sorry, I've off the launchpad site for a while.

Anyway, yesterday's update of the following packages solved the problem:
- usplash_0.5.39_i386.deb
- libusplash0_0.5.39_i386.deb

Now, when ubuntu boots up, i have the normal sequence:
-grub starts
-usplash starts (white ubuntu-logo appears)
-uspash disappears and screen gets black shortly
-gdm screen appears, waiting for user to log in