© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Thanks for those files. They seem to confirm that the kernel change in comment #16 is the cause of the regression.
So the kernel is basically doing the right thing in trying to support all screen types. Only your screen contains inadequate firmware to be able to tell the kernel what it really is. So the solution is probably to detect your particular screen model and apply a workaround just for that model (equivalent to ASUS providing a custom display driver in Windows).
It is unfortunate (for you) that hardly anyone else will experience this bug. Even on other 6-bit panels, many people won't have a problem (and I have tried on a few systems). So you're just a bit unlucky with this particular LCD panel. But it sounds like a fix is now coming :)