radeonfb broken on ATI with exotic laptop lcd

Created an attachment (id=3962)
Pictures of the laptop starting up

FWIW, radeonfb is known not to work correctly on a variety of hardware, and will
also prevent suspend/resume from working correctly. If you want usplash,
vga16fb is the only reasonable option at the moment (which is why it uses that
by default).

(In reply to comment #2)
> FWIW, radeonfb is known not to work correctly on a variety of hardware, and will
> also prevent suspend/resume from working correctly. If you want usplash,
> vga16fb is the only reasonable option at the moment (which is why it uses that
> by default).

Actually, vga16fb doesn't work either and this is what i tried to use radeonfb.
Forgot two to say two things that may help solving the bug :
* Once xorg is started, when going on a terminal (crtl + alt +FX), everything is
fine. Maybe thanks to a video ram reset or something ?
* radeonfb was ok while using hoary

Maybe this kernel bug is related: http://bugme.osdl.org/show_bug.cgi?id=4295

no, it is unrelated

If possible, please upgrade to Dapper's 2.6.15-7 kernel. If you do not want to
upgrade to Dapper, then you can also wait for the Dapper Flight 2 CD's, which
are due out within the next few days.

Let me know if this bug still exists with this kernel.

Thank you for reporting this bug and following up on it.

I am marking this bug Closed since there has been no response from you for over three months. We
would like to fix all existing issues, but need need feedback to help with debugging.

Should you still have a problem with the latest up to date Dapper kernel and packages, please reopen this bug. In this case, please answer the questions that have already been asked of you before and provide the log files and information required for debugging.

Sorry about not having answered to ben, I just forgot to do it :/

I've tried again with the 2.6.15-21-686 kernel, and the problem remains.
By the way, radeonfb seems to be very buggy and i've seen it as been blacklisted so this bug may certainly be considered harmless.

This is how my screen looks like now during startup

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

This bug report was marked as Confirmed a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, 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.]

Unassigned from Ben Collins. Marked Invalid. If this is being experienced in Karmic or Lucid, please open a new case with the relevant apport data so that we can begin fresh.

-JFo