Natty Alpha 1, i915 has blank screen after boot

Bug #683780 reported by John Johansen
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Has never successfully brought up the display, on multiple reboots.

It makes no difference if splash, quiet, i915modeset=0 are used.

Kernel for attached bug was booted with drm.debug=0x4

This is likely the same as Bug#683775 but on different hardware.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.37-7-generic 2.6.37-7.19
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.37-7.19-generic 2.6.37-rc3
Uname: Linux 2.6.37-7-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices: aplay: device_list:235: no soundcards found...
Architecture: amd64
ArecordDevices: arecord: device_list:235: no soundcards found...
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
Date: Wed Dec 1 09:58:30 2010
HibernationDevice: RESUME=UUID=7b649748-05d3-4787-b8f5-e6d70d259bb4
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: System manufacturer ASUS NOVA (P20/P22)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.37-7-generic root=UUID=42a122a3-e749-4b29-96e6-7d97d0c73e0b ro drm.debug=0x4
RelatedPackageVersions: linux-firmware 1.40
SourcePackage: linux
dmi.bios.date: 04/14/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0501
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P2P5B1-DHS
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd04/14/2008:svnSystemmanufacturer:pnASUSNOVA(P20/P22):pvrSystemVersion:rvnASUSTeKComputerINC.:rnP2P5B1-DHS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: ASUS NOVA (P20/P22)
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
John Johansen (jjohansen) wrote :
Revision history for this message
John Johansen (jjohansen) wrote :

Tried the previous linux-image-2.6.37-6-generic kernel from the archive and it exhibits the same problems. With the 2.6.37 kernels tried the machine boots but there is no graphics, or console to the attached display. Using ssh to access the machine works fine.

The machine will boot with graphics enabled using maverick's 2.6.35-23-generic kernel.

tags: added: kernel-series-unknown
Revision history for this message
Christophe Dumez (hydr0g3n) wrote :

Same here from a USB key (Ubuntu Natty Alpha 1 amd64).

00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0410]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 41
 Region 0: Memory at f0000000 (64-bit, non-prefetchable) [size=4M]
 Region 2: Memory at e0000000 (64-bit, prefetchable) [size=256M]
 Region 4: I/O ports at 60b0 [size=8]
 Expansion ROM at <unassigned> [disabled]
 Capabilities: <access denied>
 Kernel driver in use: i915
 Kernel modules: i915

Revision history for this message
Christophe Dumez (hydr0g3n) wrote :

I confirm that the fix in Bug#683775 does not work for me either. I have just tried a daily build of Natty.

tags: added: regression-release
removed: regression-update
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Christophe Dumez (hydr0g3n) wrote :

I would like to report that I'm no longer experiencing this problem. I'm running up-to-date Natty without problem.

Revision history for this message
Alejandro Zunino (azunino) wrote :

I have an ACER ASPIRE 4736Z and Ubuntu Natty boots to a blank screen. I did not have problems with Ubuntu Maverick. I have tried lots of boot parameters with no success. Sometimes (5%) Natty boots ok... it seems totally random.

Revision history for this message
Carlos Lerzundy (arepaking) wrote :

Does not work for me either.

Revision history for this message
penalvch (penalvch) wrote :

John Johansen, thank you for reporting this and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please report the results following https://wiki.ubuntu.com/DebuggingKernelBoot ? As well, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could 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.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

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.