[mythtv-users] Can't read edid all of the sudden

[Kirk Bocek]

Mike Perkins wrote:
> Kirk Bocek wrote:
>>
>>
>> On 3/12/2010 4:04 PM, Paul Kendall wrote:
>>> Yes, cut that raw EDID and extension and paste it into a hex editor
>>> to get a raw edid file which you would put in /etc/X11/edid.bin.
>>
>> I'm late to this thread but I assume you are talking about cutting the 
>> EDID data out of a verbose X log. Here's a little perl program I wrote 
>> to do just that. Replace the hex strings after the __DATA__ line and 
>> run the script. "outfile.bin" will contain the binary EDID data.
>>
>> #!/usr/bin/perl
>> #
>> # hex2bin.pl
>> # convert hex strings to binary file
>> #
>> use strict;
>>
>> open OUT, ">outfile.bin";
>> binmode OUT, ':raw';
>>
>> my $cnt = 0;
>> while (<DATA>) {
>>         my @line = split ' ';
>>         my $dat;
>>         foreach $dat (@line) {
>>                 print "Octet $dat\n";
>>                 print OUT chr(hex $dat) if $dat;
>>                 $cnt++ if $dat;
>>         }
>> }
>> close OUT;
>> print "Output $cnt octets.\n";
>>
>> #EDID block for Westinghouse SK-32H590D
>> __DATA__
>> 00 ff ff ff ff ff ff 00  5c 85 70 50 bb 00 00 00
>> 0b 11 01 03 80 47 28 8c  2a 19 91 a7 55 46 98 24
>> 10 48 49 a1 08 00 81 c0  01 01 01 01 01 01 01 01
>> 01 01 01 01 01 01 9d 1c  56 92 50 00 28 30 30 20
>> 35 00 c5 8f 21 00 00 1a  20 1c 50 a0 50 00 16 30
>> 30 20 25 00 c5 8f 21 00  00 1a 00 00 00 fd 00 31
>> 4c 0f 31 08 00 0a 20 20  20 20 20 20 00 00 00 fc
>> 00 53 4b 2d 33 32 48 35  39 30 44 0a 20 20 01 54
>> 02 03 17 71 44 84 05 03  02 23 09 07 07 83 01 00
>> 00 65 03 0c 00 10 00 01  1d 00 72 51 d0 1e 20 6e
>> 28 55 00 c5 8f 21 00 00  1e 01 1d 80 18 71 1c 16
>> 20 58 2c 25 00 c5 8f 21  00 00 9e 8c 0a d0 8a 20
>> e0 2d 10 10 3e 96 00 c5  8f 21 00 00 18 8c 0a d0
>> 8a 20 e0 2d 10 10 3e 96  00 14 8f 21 00 00 18 00
>> 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 32
>>
> OK, I'll bite. How does one edit this file to provide the information 
> which one wants the driver to see? And don't tell me 'use a hex editor', 
> what I mean is what's the format of the file?

As I said, I'm late to this thread. I assume you were talking about running X 
in verbose mode and extracting the EDID information logged by X.

This script is an alternative to using a hex editor. Delete all the lines 
after the "__DATA__" line and replace them with the EDID lines in your X log. 
They'll look like this data with some text in front of each line. You'll need 
to edit that text out.

When you run this script, it will create the file "outfile.bin" which will be 
your binary EDID data. Rename outfile.bin to something intelligible for your 
display and reference the file in your xorg.conf file as previously instructed.