Kernel refuse to boot with new monitor

[Fabbe]

Binary package hint: upstart

I've bought a new monitor, HP Compaq LA2205wg, that have maximum resolution at 1680 × 1050 (16:10). (My old monitor is a LG L2013P with 1600x1200 (4:3)).

If I plugin the new monitor and boot, it pass GRUB normal, writing "Starting up", and then the machine seems to *DIE*. ABSOLUTLY NO LOG is created, and the hard disk seems silent.

If I boot with my old monitor and switch, the "Display preferenses" recognize the new monitor, but will not allow any "new" resolutions, only 1600x1200 and some lower 16:10 resolutions.

If I boot in recovery mode on the same kernel in GRUB, and start X manually, it works fine! I get the 1680x1050. If I boot on a live CD, I also get the 1680x1050.

I have tried to reinstalled every package that seems to have with the kernel and different graphical infrastructure packages like xorg etc, but with no effect. I have tried to change to the properitary drivers, but no effect.

I'm running Ubuntu 9.10 with up-to-dates packages and 2.6.31-20-generic kernel.

The graphical card:
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Mobility Radeon HD 3600 Series [1002:9598]
        Subsystem: ASUSTeK Computer Inc. Device [1043:01da]
        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, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at d0000000 (64-bit, prefetchable) [size=256M]
        Region 2: Memory at e0300000 (64-bit, non-prefetchable) [size=64K]
        Region 4: I/O ports at 3000 [size=256]
        Expansion ROM at e0320000 [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel modules: radeon

ProblemType: Bug
Architecture: i386
Date: Tue Apr 13 02:01:58 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /sbin/init
Package: upstart 0.6.3-11
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
SourcePackage: upstart
Uname: Linux 2.6.31-20-generic i686

[Fabbe (ubuntu-fabbe)]

I have discovered that if I removed the "splash" in grub and booted, it worked. Then I did:

$ sudo nano /etc/usplash.conf
(and changed the screen resolution from 1600x1200 to 1680x1050) and then:
$ sudo update-initramfs -u

everything works again.

But I STILL consider this as a bug: The boot process should not hang just because the splash screen cannot be viewed.

[Scott James Remnant (Canonical) (canonical-scott)]

I'm not sure why you've filed this on Upstart, since you seem sure it's a Kernel issue and your description to me does sound like it's a kernel driver bug hanging the machine if the resolution is wrong

Reassigning over to the kernel

[Fabbe (ubuntu-fabbe)]

Scott: I used the bug report tool, and was forced to assign a PID, and I used "1". It was the closest I could find, the first process started by the kernel.

[Jeremy Foshee (jeremyfoshee)]

Hi Fabbe,

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.]

[Jeremy Foshee (jeremyfoshee)]

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.]