On Tue, 2009-08-25 at 15:07 -0700, Linus Torvalds wrote:
> 
> On Tue, 25 Aug 2009, mailing54 wrote:
> 
> > Linus Torvalds schrieb:
> > > Are you using the same config? It sounds very much like your -rc7 problems
> > > are due to the Intel KMS (kernel mode setting) driver, which I know has 
> > > had
> > > problems on at least Mac Mini's. And I wonder if the -rc6 kernel deb used
> > > different config options and didn't enable KMS, for example. Because I 
> > > don't
> > > think anything actually changed in the KMS code itself between rc6 and 
> > > rc7.
> >   
> > Not sure what settings to look for, but this looks like you are completely
> > correct:
> > 
> > tob...@tbox:~$ cat /boot/config-2.6.31-020631rc6-generic | grep KMS
> > # CONFIG_DRM_I915_KMS is not set
> > # CONFIG_DRM_RADEON_KMS is not set
> > tob...@tbox:~$ cat /boot/config-2.6.31-020631rc7-generic | grep KMS
> > CONFIG_DRM_I915_KMS=y
> > CONFIG_DRM_RADEON_KMS=y
> 
> Yeah, so it's i915 kms.
> 
> You can disable it dynamically at boot time with the 
> 
>       i915.modeset=0
> 
> kernel command line (or I guess with "nomodeset" too, for that matter, 
> which should disable both i915 and radeom kms).
> 
> However, the problem remains that KMS gets the output wrong, in ways that 
> clearly X does not. Eric - it's clearly not just Mac Mini and my 
> experimental machine that have problems, but also a Macbook 2.1.
> 
> I wonder why the Intel KMS logic doesn't look at which output was driven 
> before it got invoked. Instead, it seems to want to try to detect 
> everything from scratch, even though we should be able to assume that if 
> you boot from BIOS (or EFI, for that matter), the current state of the 
> graphics pipeline is likely meaningful.

In my experience, the BIOS setup doesn't reflect what outputs should be
used at runtime, and certainly not the correct configuration of the
enabled outputs.  For example, if we went to this, the giant monitor
attached to my laptop that I actually look at would go unused.

> And clearly distros are trying to enable this. Which means that this is 
> getting way more important to solve.

Yes, please open a bug on bugs.freedesktop.org and set severity=critical
-- the people working on modesetting should pick it up and take a look
at it.

For some of the DDC bugs, David Müller has an interesting-looking patch
to parse the BIOS's tables describing what DDC pin is used for VGA on
852, though it looks like it should be usable on much more.  I was
hoping the modesetting guys would review it and ack, but no response so
far.

-- 
Eric Anholt
e...@anholt.net                         eric.anh...@intel.com


Attachment: signature.asc
Description: This is a digitally signed message part

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to