Lucid - 'no signal' message occasionally on boot

[Orographic]

Using Lucid Lynx, i occasionally get the 'no signal' message on my monitor during boot. it had only happened a few times in six weeks but has now happened three times in the last few days. I have Lucid set to log in automatically, if that is of use to bug testers.

This problem doesn't happen (that I know of) in Windows 7 or PCLOS 2010 on the same machine, using identical internal drives, so it doesn't seem to be hardware related.

I never have a problem with Lucid once I have booted. No crashes at all. Its just during the boot process.

When this problem occurs, I can see the BIOS screen no problem, then as it goes to boot into Lucid the screen says 'no signal' then my green light on the monitor goes orange. Pressing ctrl-alt-F1 seems to shut everything down fine then it boots fine the next time.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xorg 1:7.5+5ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic-pae 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic-pae i686
Architecture: i386
Date: Fri Jun 18 18:10:30 2010
DkmsStatus: Error: [Errno 2] No such file or directory
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: Gigabyte Technology Co., Ltd. H55-USB3
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic-pae root=UUID=2a2ef3ba-5b08-4623-bdbc-13f92ac61a46 ro quiet splash
ProcEnviron:
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
dmi.bios.date: 02/12/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F4
dmi.board.name: H55-USB3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd02/12/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: H55-USB3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-22-generic-pae

[Orographic (temp850)]

Sorry, I should have posted my machine specs: Intel Core i3, gigabyte H55-USB3 motherboard, 4G of DDR3 RAM, Ben Q 2200HD monitor.

[Orographic (temp850)]

I am still getting this problem, where I get a no signal message from the monitor about once every three weeks (or possibly related to the amount of boots in that time). After pressing crl-alt-f1 the system shuts down the I can start up again fine. I then tend to have it occur again within a day or two then it disappears for weeks again. My Lucid install is full up to date. This same machine has Windows 7 on another hard drive and it doesn't occur at all on that setup.

[Bryce Harrington (bryce)]

From your description it sounds like this is occurring well before X kicks in. In any case, powering down the monitor is not done by X but rather by the kernel and/or power management software. Bumping to the kernel.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest v3.2-rcN kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the others). 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.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.2-rc1'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. If you believe this bug does not require upstream testing, please add the tag: 'kernel-upstream-testing-not-needed'.

Thanks in advance.

[penalvch (penalvch)]

Orographic, 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 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/KernelMainlineBuilds ? 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:
needs-upstream-testing

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:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

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:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

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:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

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