All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tino Keitel <tino.keitel@tikei.de>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: DVI/EDID broken with Intel i945 graphics and 2.6.37-rc2
Date: Tue, 23 Nov 2010 22:47:04 +0100	[thread overview]
Message-ID: <20101123214704.GA26884@mac.home> (raw)
In-Reply-To: <5b55a1$indcgc@fmsmga002.fm.intel.com>

[-- Attachment #1: Type: text/plain, Size: 610 bytes --]

On Fri, Nov 19, 2010 at 21:42:10 +0000, Chris Wilson wrote:
> On Fri, 19 Nov 2010 08:54:27 +0100, Tino Keitel <tino.keitel@tikei.de> wrote:
> > On Wed, Nov 17, 2010 at 10:20:09 +0000, Chris Wilson wrote:
> > 
> > [...]
> > 
> > > An alternative is to force detection, ie change the detect(analog, false)
> > > to true.
> > 
> > Hi,
> > 
> > this didn't help either.
> 
> If we didn't even hit the additional printks, then I am no longer even
> sure what is going on here... Can you add drm.debug=0xe to your boot line
> and attach the dmesg from boot?

Hi, dmesg with drm.debug=0xe is attached.

Regards,
Tino

[-- Attachment #2: dmesg.xz --]
[-- Type: application/octet-stream, Size: 11328 bytes --]

  reply	other threads:[~2010-11-23 21:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-16 18:49 DVI/EDID broken with Intel i945 graphics and 2.6.37-rc2 Tino Keitel
2010-11-17 10:20 ` Chris Wilson
2010-11-17 12:02   ` Tino Keitel
2010-11-17 20:01   ` Tino Keitel
2010-11-19  7:54   ` Tino Keitel
2010-11-19 21:42     ` Chris Wilson
2010-11-23 21:47       ` Tino Keitel [this message]
2010-11-23 22:42         ` [PATCH] drm/i915/sdvo: Always fallback to querying the shared DDC line Chris Wilson
2010-11-23 23:02           ` Tino Keitel
2010-11-21 16:33 ` DVI/EDID broken with Intel i945 graphics and 2.6.37-rc2 Maciej Rutecki
  -- strict thread matches above, loose matches on Subject: below --
2010-11-17  6:29 Tino Keitel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101123214704.GA26884@mac.home \
    --to=tino.keitel@tikei.de \
    --cc=chris@chris-wilson.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.