Black screen / No display on boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-video-intel (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: xorg
Hi, I'm running an up to date Natty Alpha build on an Asus eeepc 901 with an atom processor. While not constant (i.e., sometimes it works, sometimes it doesn't), I'm finding the computer boots with a black screen. I can still hear the sounds of the operating system, can still press the keys and get a response (usually a sound cue), however I can't see anything. Seems to happen four out of 7 times when I boot, and I have to do a hard reset.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: xorg 1:7.5+6ubuntu3b1
ProcVersionSign
Uname: Linux 2.6.37-7-generic i686
Architecture: i386
DRM.card0.LVDS.1:
status: connected
enabled: enabled
dpms: On
modes: 1024x600
edid-base64: AP/////
DRM.card0.VGA.1:
status: disconnected
enabled: disabled
dpms: Off
modes:
edid-base64:
Date: Fri Dec 3 20:52:30 2010
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20101202)
MachineType: ASUSTeK Computer INC. 901
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
dmi.bios.date: 06/11/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2103
dmi.board.
dmi.board.name: 901
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: 901
dmi.product.
dmi.sys.vendor: ASUSTeK Computer INC.
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: natty
architecture: i686
kernel: 2.6.37-7-generic
summary: |
- No display on bootup + Black screen / No display on boot |
affects: | xorg (Ubuntu) → xserver-xorg-video-intel (Ubuntu) |
tags: | added: black-screen |
Almost certainly more likely to be a kernel issue, perhaps dupe of bug #683775. Try the fix Andy posted to that bug and see if it resolves it for you. If it does, this bug report should be duped to that one.