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-prev] [day] [month] [year] [list]
Message-ID: <50866A9C.5060507@cfl.rr.com>
Date:	Tue, 23 Oct 2012 05:59:56 -0400
From:	Mark Hounschell <dmarkh@....rr.com>
To:	Bruno Prémont <bonbons@...ux-vserver.org>
CC:	markh@...pro.net, linux-kernel@...r.kernel.org,
	Intel Graphics Development <intel-gfx@...ts.freedesktop.org>
Subject: Re: [Intel-gfx] drm_kms_helper problems

On 10/23/2012 02:36 AM, Bruno Prémont wrote:
> On Mon, 22 Oct 2012 17:54:26 Mark Hounschell wrote:
>> Another interesting thing. I changed the boot file to only
>> "video=HDMI-A-1:e" and the monitor on the DVI port complains about the
>> resolution being to high. I then put the hdmi cable onto my dvi/hdmi
>> adapter and plug it into the DVI port and wala, a 1920 x 1080 desktop. So I
>> reboot with it in that configuration  and again comes up good connected to
>> the DVI connector.
>
> So at least the EDID firmware now gets recognized and considered :)
>
>> # xrandr
>> Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
>> VGA1 disconnected (normal left inverted right x axis y axis)
>> HDMI1 connected 1920x1080+0+0 (normal left inverted right x axis y axis)
>> 708mm x 398mm
>>      1920x1080      60.0*+   50.0     25.0     30.0     30.0     24.0
>>      1680x1050      59.9
>>      1680x945       60.0
>>      1400x1050      59.9
>>      1600x900       60.0
>>      1280x1024      75.0     60.0
>>      1440x900       59.9
>>      1280x960       60.0
>>      1366x768       60.0
>>      1360x768       60.0
>>      1280x800       74.9     59.9
>>      1152x864       75.0
>>      1280x768       74.9     60.0
>>      1280x720       50.0     60.0
>>      1024x768       75.1     70.1     60.0
>>      1024x576       60.0
>>      800x600        72.2     75.0     60.3     56.2
>>      720x576        50.0
>>      848x480        60.0
>>      720x480        59.9
>>      640x480        72.8     75.0     60.0     59.9     59.9
>>      720x400        70.1
>> DP1 disconnected (normal left inverted right x axis y axis)
>> HDMI2 disconnected (normal left inverted right x axis y axis)
>> HDMI3 disconnected (normal left inverted right x axis y axis)
>> DP2 disconnected (normal left inverted right x axis y axis)
>> DP3 disconnected (normal left inverted right x axis y axis)
>>
>> I'm still getting the same messages spewed into the kernel log file. So
>> this looks to me like the kernel is confused. Again, I ask, why do I have 3
>> HDMIs and 3 DPs but just one VGA.
>
> Maybe Daniel or Chris can comment on that high quantity of DP/HDMI
> connectors seen by driver. Those are probably also the cause of the
> persistent EDID complaints in kernel log.
>

What I see is that HDMI-1 is the DVI port, HDMI-3 is the HDMI port, so I 
assume HDMI-2 is that "other" video port.

If I set video=HDMI-A-1:d nothing comes out the DVI port and if I set 
HDMI-A-3:d nothing comes out the HDMI port. This is rather confusing. Is it 
correct?

>
> You could maybe try to disable those outputs in xorg.conf in order to not
> get your log filled with bad EDID complaints for "unused" connectors.
> But as specifying the EDID as firmware it's just a work-around to the
> issue.
>

These messages get spewed even if X is not running. The machine is 
unresponsive for 2-3 seconds when this happens.

Sure, specifying the EDID as firmware is a work around, but it's a work 
around that isn't working as intended on this hardware, for whatever 
reason. Seems like someone would be interested in fixing it? I've got a 
machine I could provide some access to?

Mark



--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ