public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ykzhao <yakui.zhao@intel.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>,
	Knut Petersen <Knut_Petersen@t-online.de>
Cc: Knut Petersen <Knut_Petersen@t-online.de>,
	"airlied@linux.ie" <airlied@linux.ie>,
	Linus Torvalds <torvalds@osdl.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] Regression DRM/i915/KMS: VGA connector unusable after 2.6.31-rc8-git1, DVI connector ok
Date: Wed, 09 Sep 2009 09:05:33 +0800	[thread overview]
Message-ID: <1252458334.3609.146.camel@localhost.localdomain> (raw)
In-Reply-To: <20090908152636.701feffb@jbarnes-g45>

On Wed, 2009-09-09 at 06:26 +0800, Jesse Barnes wrote:
> cc'ing the intel-gfx list.
> 
> On Wed, 09 Sep 2009 00:19:04 +0200
> Knut Petersen <Knut_Petersen@t-online.de> wrote:
> 
> > Hi everybody!
> > 
> > During the release cycle of the 2.6.31-rc* kernels KMS started to work
> > on my computer.
> > 
> > Booting with a monitor attached to both the VAG and the DVI
> > connectors, kernel 2.6.31-rc8-git1
> > detects both monitors correctly and sets the native video mode.
> > 
> > Booting the same configuration with kernel 2.6.31-rc8-git2 ...
> > -rc9-git1 gives a different result:
> > the DVI-attached monitor is still working perfectly, the VGA-attached
> > monitor does not detect a
> > valid video signal and switches off.
> > 
> > Hardware: AOpen i915GMm-hfs,  Pentium-M 1.86 MHz,  2GB RAM
> > The Aopen i915GMm-hfs is a  desktop board with a mobile Chipset:
> > 
> > 00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML
> > Express Processor to DRAM Controller (rev 04)
> > 00:02.0 VGA compatible controller: Intel Corporation Mobile
> > 915GM/GMS/910GML Express Graphics Controller (rev 04)
> > 00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML
> > Express Graphics Controller (rev 04)
> > 
> > Config: AGP/DRM/I915 all compiled into kernel, KMS enabled.
> > 
> > Log_Broken contains the result of "cat boot.msg | grep -i drm" of a
> > boot with 2.6.31-rc8-git2,
> > Log_OK contains the result of "cat boot.msg | grep -i drm" of a boot
> > with 2.6.31-rc8-git1
> > 
> > As a black monitor is not a nice gift I think this should be fixed
> > before the final release of 2.6.31.
Will you please try the latest git tree and see whether the issue can
still be reproduced?
Thanks.
> > 
> > cu,
> >  Knut
> 
> 


  reply	other threads:[~2009-09-09  1:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-08 22:19 Regression DRM/i915/KMS: VGA connector unusable after 2.6.31-rc8-git1, DVI connector ok Knut Petersen
2009-09-08 22:26 ` Jesse Barnes
2009-09-09  1:05   ` ykzhao [this message]
2009-09-08 22:28 ` Carlos R. Mafra
2009-09-08 23:00   ` Knut Petersen
2009-09-08 23:11 ` Linus Torvalds
2009-09-09  7:09   ` Knut Petersen
2009-09-09 14:28     ` Linus Torvalds
2009-09-09 21:35       ` Knut Petersen
2009-09-09 16:04     ` Jesse Barnes

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=1252458334.3609.146.camel@localhost.localdomain \
    --to=yakui.zhao@intel.com \
    --cc=Knut_Petersen@t-online.de \
    --cc=airlied@linux.ie \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox