All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gabriel C <nix.or.die@googlemail.com>
To: Dave Airlie <airlied@linux.ie>
Cc: Ma Ling <ling.ma@intel.com>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] drm fixes + intel display port
Date: Wed, 24 Jun 2009 16:31:46 +0200	[thread overview]
Message-ID: <4A4238D2.2060501@googlemail.com> (raw)
In-Reply-To: <1820d69d0906240715v6c3591c4x30ee87e9ec8774f7@mail.gmail.com>

[ forgot to CC LKML , sorry ]

Gabriel C wrote:

> 2009/6/24 Dave Airlie <airlied@linux.ie>:
>> Hi Linus,
>>
>> Please pull the 'drm-fixes' branch from
>> ssh://master.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git drm-fixes
>>
> 
> Hi Dave ,
> 
> I own an DQ45CB Intel motherboard. When enabling KMS with kernels from
> 2.6.29* to current git / linux-next on that board
> I don't get any console. My Monitor is saying 'No signal' , however
> once X starts up I can login in KDE/gnome etc.
> 
> The monitor is connected with an DVI-I -> VGA connector.
> 
> I found on the gfx mailing list the following patch from Ma Ling :
> 
> http://lists.freedesktop.org/archives/intel-gfx/2009-May/002504.html
> 
> which seems to fix my problem. With that patch applied I get a console
> and everything works fine.
> 
> However I still have such :
> 
> [   21.205449] i2c-adapter i2c-1: unable to read EDID block.
> [   21.205452] i915 0000:00:02.0: VGA-1: no EDID data
> 
> 
> messages in my dmesg but it works.
> 
> 
> Is there any reason why this patch never got merged ?
> 
> Best Regards,
> 
> Gabriel C



  parent reply	other threads:[~2009-06-24 14:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24  6:42 [git pull] drm fixes + intel display port Dave Airlie
     [not found] ` <1820d69d0906240715v6c3591c4x30ee87e9ec8774f7@mail.gmail.com>
2009-06-24 14:31   ` Gabriel C [this message]
2009-06-25 23:31     ` Dave Airlie
2009-06-26 13:25       ` Ma, Ling
2009-06-27 13:39         ` Gabriel C

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=4A4238D2.2060501@googlemail.com \
    --to=nix.or.die@googlemail.com \
    --cc=airlied@linux.ie \
    --cc=ling.ma@intel.com \
    --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.