From: Chris Wilson <chris@chris-wilson.co.uk>
To: Knut Petersen <Knut_Petersen@t-online.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
airlied@linux.ie, eric@anholt.net, jesse.barnes@intel.com,
linux-kernel@vger.kernel.org,
intel-gfx <intel-gfx@lists.freedesktop.org>,
gregkh@suse.de, Jean Delvare <khali@linux-fr.org>,
David Brownell <david-b@pacbell.net>
Subject: Re: [PATCH] Fix i915 drm regression on AOpen i915GMm-HFS motherboard
Date: Mon, 03 Jan 2011 23:22:38 +0000 [thread overview]
Message-ID: <0d30dc$kl33rh@orsmga001.jf.intel.com> (raw)
In-Reply-To: <4D22571F.9060706@t-online.de>
On Tue, 04 Jan 2011 00:09:19 +0100, Knut Petersen <Knut_Petersen@t-online.de> wrote:
> Kernel 2.6.37-rc8-git2
> =================
>
> text mode console: ok, resolution 1280x1024, fully used by framebuffer
> output
> X: first device detected is LVDS with resolution 1024x768. VGA and DVI
> connector work in X,
> but X switches to 1024x768 for both of them. xrandr reports the four
> physical connectors but
> also LVDS, VGA2 and TV3 connectors.
A false detection of the LVDS would appear to be a minor issue compared to
all the trouble you have. Can you add drm.debug=0xe to your boot
commandline and attach the resulting dmesg?
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-01-03 23:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 14:25 [PATCH] Fix i915 drm regression on AOpen i915GMm-HFS motherboard Knut Petersen
2011-01-03 14:54 ` Chris Wilson
2011-01-03 14:54 ` Chris Wilson
2011-01-03 18:12 ` Knut Petersen
2011-01-03 19:45 ` Linus Torvalds
2011-01-03 19:59 ` Chris Wilson
2011-01-03 20:26 ` Linus Torvalds
2012-04-04 16:23 ` Jean Delvare
2011-01-03 23:09 ` Knut Petersen
2011-01-03 23:22 ` Chris Wilson [this message]
2011-01-04 0:35 ` Knut Petersen
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='0d30dc$kl33rh@orsmga001.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=Knut_Petersen@t-online.de \
--cc=airlied@linux.ie \
--cc=david-b@pacbell.net \
--cc=eric@anholt.net \
--cc=gregkh@suse.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jesse.barnes@intel.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.