[lucid] [M92 LP] blank screen on Mobility Radeon HD 4300 with KMS enabled

[Mathieu Trudel-Lapierre]

On boot with a daily image (tested with ubuntu-server), the screen remains blank at all times. Disabling KMS with "radeon.modeset=0" is a workaround that will let the text on a console be displayed correctly.

Sorry there is little information, but as this was tested on ubuntu-server, xserver-xorg is not installed and I can not immediately provide X logs.

Attaching dmesg with and without modesetting enabled, as well as the ouput of 'lspci -vnvn', /proc/version_signature and 'uname -a'.

[Mathieu Trudel-Lapierre (cyphermox)]

This is the output of dmesg when the display remains blank. It was retrieved using a remote ssh connection.

[Mathieu Trudel-Lapierre (cyphermox)]

The output of dmesg with KMS disabled.

[Ronald McCollam (fader)]

We need to verify that this happens with the desktop image and not just the server image, as this is a laptop system. Marking incomplete until we have more data.

[Mathieu Trudel-Lapierre (cyphermox)]

Tested again with yesterday's daily image: 20100406

The behavior is reproducible: with modesetting enabled, the screen remains blank throughout plymouth and X. With modesetting disabled, the display works.

Note: I've also tested with "modeset=1 dynclks=0", "modeset=1 new_pll=0", in addition to "modeset=0".

Attached is a tarball containing the logs with modesetting enabled.

[Mathieu Trudel-Lapierre (cyphermox)]

This is the logs with modesetting disabled.

[Mathieu Trudel-Lapierre (cyphermox)]

Tried again with latest desktop image (daily 20100419). The attached tar contains the logs when tested without change, so with modesetting enabled.

[Mathieu Trudel-Lapierre (cyphermox)]

Attached logs with modesetting disabled.

[Manoj Iyer (manjo)]

Is this still an issue with the latest Lucid kernel? If so can you please try the mainline ppa and report if the issue is solved upstream? http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/

[Mathieu Trudel-Lapierre (cyphermox)]

Works with the latest maverick image (20100713). Will test on Lucid with the mainline kernel and report today.

[Mathieu Trudel-Lapierre (cyphermox)]

Actually, let me clarify that: it tends to work (it's no longer a blank screen), but there is a lot of distortion, to the point the desktop is unusable -- only the mouse pointer moves (again, this is maverick 20100713).

[jerrylamos (jerrylamos)]

I don't know if this is related at all, however bug #598322 is blank screen on ati radeon mobility 7500 with an external monitor. This does occur with today's ppa.

Maverick Meerkat Alpha 1 linux version 2.6.34-5-generic does boot O.K. in KMS mode with the same xorg so it would appear to be a kernel bug.

Alpha 2, updates since, and today's ppa requires radeon.modeset=0 in the linux boot line to boot successfully.

Jerry

[Hankyone (hankyone)]

Issue can still be reproduced on Lucid 10.04.1

[jerrylamos (jerrylamos)]

ati radeon mobility 7500 blank screen just after KMS starts with today's kernel update:
Linux version 2.6.35-12-generic (buildd@rothera) (gcc version 4.4.5 20100723 (prerelease) (Ubuntu/Linaro 4.4.4-7ubuntu3) ) #17-Ubuntu SMP Mon Jul 26 18:09:52 UTC 2010
I was able to ssh in and get
dmesg
.xsession-errors
Xorg.0.log
which are attached

Let me know if this is a similar bug to 555943 or whether I should report a new one.

Thanks

[Mathieu Trudel-Lapierre (cyphermox)]

In today's maverick image (xubuntu, daily-live, 20100819), the installer is visible but graphics are distorted. Will report back with the status of the screen while booting / in X once the install is complete.

[Mathieu Trudel-Lapierre (cyphermox)]

Graphics are badly distorted when the desktop appears (again, xubuntu daily-live 20100819). Text in text mode looks fine however. See the attached image.

[JC Hulce (soaringsky)]

This bug affects Ubuntu 10.10, Maverick Meerkat. Maverick has reached end-of-life and is no longer supported, so I am closing the bug task for Maverick. Please upgrade to a newer version of Ubuntu.
More information here: https://lists.ubuntu.com/archives/ubuntu-announce/2012-April/000158.html

[penalvch (penalvch)]

Mathieu Trudel-Lapierre, 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 images are available from http://cdimage.ubuntu.com/daily-live/current/ .

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 daily kernel 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. 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. For example:
kernel-fixed-upstream-v3.11.1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Rolf Leggewie (r0lf)]

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".

[Po-Hsu Lin (cypressyew)]

Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!