Monitor reports no input detected and goes into sleep mode
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
Regression from 2.6.35 based Maverick kernels.
Single monitor attached to the machine via dvi (or hdmi via converter).
It will display grub, or console output, but at about the point gdm starts the display goes black, and reports that no input is detected.
This behavior exists in the 2.6.36, 2.6.37 and 2.6.38 upstream kernels as well.
I bisected this problem to
commit b599c0bca1e08a8
Author: Adam Jackson <<link:
Date: Fri Jul 16 14:46:31 2010 -0400
drm/i915/hdmi: Set sync polarity based on actual mode
Signed-off-by: Adam Jackson <<link:
Signed-off-by: Eric Anholt <<link:
However reverting this commit in later kernels does not result in the display functioning, and I have not traced it any further yet.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.38-8-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfe8f8000 irq 46'
Mixer name : 'Realtek ALC888'
Components : 'HDA:10ec0888,
Controls : 27
Simple ctrls : 14
Date: Mon Apr 11 06:25:25 2011
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: System manufacturer ASUS NOVA (P20/P22)
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.50
SourcePackage: linux
UpgradeStatus: Upgraded to natty on 2010-12-01 (131 days ago)
dmi.bios.date: 04/14/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0501
dmi.board.
dmi.board.name: P2P5B1-DHS
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: ASUS NOVA (P20/P22)
dmi.product.
dmi.sys.vendor: System manufacturer
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
John Johansen, thank you for reporting this and helping make Ubuntu better. Natty reached EOL on October 2012. /wiki.ubuntu. com/Releases
Please see this document for currently supported Ubuntu releases:
https:/
We were wondering if this is still an issue in a supported release? If so, could you please test for this 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 please run the following command in the development release from a Terminal (Applications- >Accessories- >Terminal) , as it will automatically gather and attach updated debug information to this report:
apport-collect -p linux <replace- with-bug- number>
Also, could you please test the latest upstream kernel available following https:/ /wiki.ubuntu. com/KernelMainl ineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag: testing
needs-upstream-
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 text: testing
needs-upstream-
If this bug is fixed in the mainline kernel, please add the following tags: fixed-upstream fixed-upstream- VERSION- NUMBER
kernel-
kernel-
where VERSION-NUMBER is the version number of the kernel you tested.
If the mainline kernel does not fix this bug, please add the following tags: bug-exists- upstream bug-exists- upstream- VERSION- NUMBER
kernel-
kernel-
where VERSION-NUMBER is the version number of the kernel you tested.
If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags: unable- to-test- upstream unable- to-test- upstream- VERSION- NUMBER
kernel-
kernel-
where VERSION-NUMBER is the version number of the kernel you tested.
Please let us know your results. Thank you for your understanding.
Helpful Bug Reporting Tips: /help.ubuntu. com/community/ ReportingBugs
https:/