[Maverick] [PATCH 0/4] KMS Disablement for i8xx

[Brian Rogers]

  On 09/05/2010 02:05 PM, Steven wrote:
> On Sun, Sep 5, 2010 at 2:09 PM, Matthew Garrett <mjg59 at srcf.ucam.org 
> <mailto:mjg59 at srcf.ucam.org>> wrote:
>
>     On Thu, Sep 02, 2010 at 05:10:11PM -0700, Leann Ogasawara wrote:
>     > On Fri, 2010-09-03 at 09:52 +1000, Christopher James Halse
>     Rogers wrote:
>     > > Disabling KMS on these cards in Maverick will result in them
>     using the
>     > > VESA X driver, which has been reported to work on the various
>     i8xx bugs.
>
>     It's probably worth noting that a large number of 855 machines have
>     native panel resolutions that aren't present in the vesa tables,
>     and so
>     won't be able to run in native resolution with the vesa driver.
>
>
> This has been my experience. When running the vesa driver on Lucid on 
> my i855, I get:
> (EE) VESA: No valid modes.
> (EE) Screen(s) found, but none have a usable configuration.
> Then the graphics never load.

Wouldn't the fbdev X driver be a better option? I don't believe it 
suffers from the same stability issues, and it should always be able to 
use the native panel resolution. I'd also trust it more with 
suspend/resume and VT or user switching. Does vesa have any advantages 
over fbdev?

To support fbdev fallback for problem cards, the 
xserver-xorg-video-intel driver would have to be patched to blacklist 
i8xx cards (with support for overriding in xorg.conf), and we'd have to 
make sure fbdev is tried as a fallback before vesa.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/kernel-team/attachments/20100908/7242d1f4/attachment.html>