linux-kernel - Re: [git pull] drm fixes + intel display port

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <4A4238D2.2060501@googlemail.com>
Date:	Wed, 24 Jun 2009 16:31:46 +0200
From:	Gabriel C <nix.or.die@...glemail.com>
To:	Dave Airlie <airlied@...ux.ie>
CC:	Ma Ling <ling.ma@...el.com>,
	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] drm fixes + intel display port

[ forgot to CC LKML , sorry ]

Gabriel C wrote:

> 2009/6/24 Dave Airlie <airlied@...ux.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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/