On 2009.08.25 21:20:18 -0700, Linus Torvalds wrote:
And how about MacBook 2.1, which apparently also goes black?
Linus, sorry for reply this old thread.
I just handed on one MacBook with 945GM, and tried to find out
the reason of black screen. It is TV detection that caused it.
MacBook
On Wed, Aug 26, 2009 at 4:26 PM, Eric Anholte...@anholt.net wrote:
On Wed, 2009-08-26 at 13:47 +1000, Dave Airlie wrote:
On Wed, Aug 26, 2009 at 1:33 PM, Linus
Torvaldstorva...@linux-foundation.org wrote:
On Wed, 26 Aug 2009, Zhenyu Wang wrote:
In my experience, the BIOS setup
On Wed, 2009-08-26 at 11:58 +0800, Zhenyu Wang wrote:
Hi
From the config file it seems that the CONFIG_FRAMEBUFFER_CONSOLE is
set as m.
Will you please set it to y and see whether the black screen
happens?
Thanks.
Yakui
On 2009.08.25 20:33:32 -0700, Linus Torvalds wrote:
On Wed,
On Wed, 26 Aug 2009, Dave Airlie wrote:
3. Here's the thing, we do detect something has changed, we detect we no
longer have a monitor connected on the mac mini because the routing
for the DDC pins is insane and need special treatment in the driver.
That's the second thing - DDC in general
On Wed, 26 Aug 2009 10:12:14 -0700 (PDT)
Linus Torvalds torva...@linux-foundation.org wrote:
In all three cases the end result is no EDID, but regardless of
that, the correct action is basically _never_ to say ok, I'll just
assume that the display is on connector XYZ regardless of what the
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
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 2009.08.25 15:33:57 -0700, Eric Anholt wrote:
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
On Wed, 26 Aug 2009, Zhenyu Wang wrote:
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
On Wed, Aug 26, 2009 at 1:33 PM, Linus
Torvaldstorva...@linux-foundation.org wrote:
On Wed, 26 Aug 2009, Zhenyu Wang wrote:
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
On 2009.08.25 20:33:32 -0700, Linus Torvalds wrote:
On Wed, 26 Aug 2009, Zhenyu Wang wrote:
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
On Wed, 26 Aug 2009, Dave Airlie wrote:
If you actually detected things _right_, none of this would be an issue.
But you don't. And you seem to have a really hard time even admitting
that. You try to re-detect things, and you SCREW UP.
This isn't anything to do with redetection, and
On Wed, 26 Aug 2009, Zhenyu Wang wrote:
We can't depend on any BIOS display config as you noted before our driver.
But you do. You depend on the even _less_ reliable existence of a VBT
table.
And our driver does more flexible config than VBIOS does.
If by flexible you mean doesn't work
On Wed, Aug 26, 2009 at 2:13 PM, Linus
Torvaldstorva...@linux-foundation.org wrote:
On Wed, 26 Aug 2009, Dave Airlie wrote:
If you actually detected things _right_, none of this would be an issue.
But you don't. And you seem to have a really hard time even admitting
that. You try to
14 matches
Mail list logo
