[avivo] Error reading EDID

[Jerome Glisse]

On 7/17/07, Nicolas Trangez <eikke at eikke.com> wrote:
> On Tue, 2007-07-17 at 03:32 +0200, Jerome Glisse wrote:
> > Ok, it seems your lvds does not have edid (likely to save one extra bucks).
> It wasn't such a cheap laptop ;-) Strange get-edid | parse-edid does
> work/detect correct resolution.
>
> > Please give output of avivotool romtables mmap (you need to be root). And
> > xorg log of fglrx driver. Also you might want to try using avivotool i2c-monitor
> > (try this by changing value at line 309 & 310 to 0x7e4., 0x7e5. or 0x7e6. to
> > test on each 3 i2c line).
> Xorg log using fglrx is attached. Do note this is running my system
> server, xserver 1.2.0, unlike my previous mail using -git.
>
> Here's the output of avivotool romtables mmap (while running the fglrx
> server):
> sky avivotool # whoami
> root
> sky avivotool # ./avivotool romtables mmap
> can't mmap bios: Success
>
> As discussed on IRC:
>
> sky avivotool # echo 1 > /sys/bus/pci/devices/0000\:01\:00.0/rom
> sky avivotool # cat /sys/bus/pci/devices/0000\:01\:00.0/rom > myrom
> #echo won't do ;-)
> sky avivotool # file myrom
> myrom: BIOS (ia32) ROM Ext. IBM comp. Video (126*512)
> sky avivotool # ./avivotool romtables myrom
>
> BIOS Tables:
> ------------
>
> Header at 20a, type: 36 [ATOM]
> OEM ID: 01 01
> ATOM BIOS detected !
>
> Clock info block:
>   SCLK    : 450.000000
>   MCLK    : 450.000000
>   RefClk  : 27.000000
>   PPLL Min: 0.000000
>   PPLL Max: 1100.000000
> Connector table:
> 0:    00009011 , Id: 0, Type: VGA, DDC: AVIVO connector #1?, DAC: CRT
> 1:    00001570 , Id: 5, Type: LVDS, DDC: None, DAC: None
> 2:    00000052 , Id: 0, Type: STV, DDC: AVIVO connector #1?, DAC: TV
> TMDS PLLs:
> Maximum frequency: 165000Hz
>     0: 165000Hz a0116
>     1: 720Hz 1005
>     2: 0Hz 9410
>     3: 23200Hz 10a3
> LVDS timings:
>   x: 1280, y: 768, dotclock: 71000
>   hblank: 160, hoverplus: 48, hsyncwidth: 32
>   vblank: 55, voverplus: 3, vsyncwidth: 6
>   power-on delay: 15464
>
>
> The myrom file is attached, too.
>
> Finally, the i2c-monitor thing. I patched avivotool so I could provide
> the GPIO_IN and GPIO_OUT addresses on the command line, I'll send a diff
> in a new mail. Here's the output:
>
> sky avivotool # for i in `seq 4 6`; do sudo ./avivotool i2c-monitor 0x7e
> ${i}c 0x7e${i}8; done
> GPIO_IN = 0x7e4c, GPIO_OUT = 0x7e48
> I2C bus "DDC" initialized.
> I2C device "DDC:ddc2" registered at address 0xA0.
> 00FFFFFFFFFFFF004C2DD701
> GPIO_IN = 0x7e5c, GPIO_OUT = 0x7e58
> I2C bus "DDC" initialized.
> I2C device "DDC:ddc2" registered at address 0xA0.
> 0100000000000000D429FAB7
> GPIO_IN = 0x7e6c, GPIO_OUT = 0x7e68
> I2C bus "DDC" initialized.
> I2C device "DDC:ddc2" registered at address 0xA0.
> 0100000000000000D4A9F2B7
>
> (I have no clue what this is about)
>
> Thanks,
>
> Nicolas
>
>

Can you try with 0x7e3c & 0x7e38 and hack avivotool line 338,339 change
64 to 128 and line 375,376 change 12 to 128 a send new output thanx.

best,
Jerome Glisse