boot option GRUB_CMDLINE_LINUX_DEFAULT "nomodeset" leads to crash

Bug #539939 reported by Peter M. Clausen
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I am unsure if "boot option" is the correct wording, but to reproduce:

1. Edit /etc/default/grub
2. Change
old>GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
new>GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
3. run
$ sudo update-grub
4. Restart

During restart the splash screen looks strange, flickers which then leads to a crash where the computer hangs with a blank screen and totally unresponsive. Only solution hard boot, boot to terminal, revert above setting, reboot.

Bug #489447 looks similar but is regarding ATI

In redhat https://bugzilla.redhat.com/show_bug.cgi?id=500752 they seem to have reported a simlilar problem.

Please help me collecting the correct info about this problem (I am new to bug-reporting in ubuntu) and comment wether this is the correct place to report this problem.

FYI: I was trying to work around Bug #49521 which is a major problem for me. I read somewhere that "nomodeset" could help this problem - well, it did not...

ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: clausen 1329 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with STAC9750,51 at irq 5'
   Mixer name : 'SigmaTel STAC9750,51'
   Components : 'AC97a:83847650'
   Controls : 36
   Simple ctrls : 23
CurrentDmesg:
 [ 21.932654] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
 [ 22.777968] lib80211_crypt: registered algorithm 'TKIP'
 [ 32.452031] eth1: no IPv6 routers present
Date: Tue Mar 16 23:41:23 2010
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=1cad0f0e-2d36-4748-9ad7-8905a67cf6f8
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100308)
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 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: Dell Inc. Latitude D505
Package: linux-image-2.6.32-16-generic 2.6.32-16.25
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic root=UUID=8dd489d8-9973-49d4-be6f-57371ca22702 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
Regression: No
RelatedPackageVersions: linux-firmware 1.32
Reproducible: Yes
RfKill:

SourcePackage: linux
TestedUpstream: Yes
Uname: Linux 2.6.32-16-generic i686
dmi.bios.date: 01/28/2005
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0H2049
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/28/2005:svnDellInc.:pnLatitudeD505:pvr:rvnDellInc.:rn0H2049:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D505
dmi.sys.vendor: Dell Inc.

Revision history for this message
Peter M. Clausen (pclausen) wrote :
Revision history for this message
Scott Testerman (scott-testerman) wrote :

Exactly the same symptoms here. Using nomodeset is a suggest workaround for several current Intel video bugs, but it's impossible to boot using nomodeset.

Revision history for this message
Scott Testerman (scott-testerman) wrote :

"nomodeset" also fails after removing "quiet splash".

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Peter,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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