07.11.2013 23:20, Olivier Langlois kirjoitti:
o Contents of /proc/asound/cardX/eld#0.0
Thanks a lot :)
monitor_present 1 eld_valid 1 monitor_name SC-09TX connection_type HDMI
[...]
Looks OK, thanks for testing. Do you happen to have an EDID handy for the receiver, just to double-check the data matches? Not sure how it is available with fglrx driver, maybe in /var/log/Xorg.0.log... No need to go to extraordinary lengths to get it, though :)
Anssi,
Here is the EDID from Xorg.0.log:
[511268.796] (II) fglrx(0): EDID (in hex): [511268.797] (II) fglrx(0): 00ffffffffffff00412f000001010101 [511268.797] (II) fglrx(0): 00110103806e3e782ad7b3ae51509423 [511268.797] (II) fglrx(0): 0c4a4721080081800101010101010101 [511268.797] (II) fglrx(0): 010101010101023a801871382d40582c [511268.797] (II) fglrx(0): 45004e6c4200001e011d8018711c1620 [511268.797] (II) fglrx(0): 582c25004e6c4200009e000000fd0017 [511268.797] (II) fglrx(0): 3d0f450f000a202020202020000000fc [511268.797] (II) fglrx(0): 0053432d303954580a202020202001c4
I'm seeing the monitor_name ok. Unfortunately, it doesn't dump the extension that byte 126 indicates to be present. (the CEA EDID Timing Extension with the SADs ?) to validate the rest of the content of /proc/asound/cardX/eld#0.0.
Is there any other way to get the EDID data?
With direct VBE BIOS calls, e.g. with this: http://gitweb.mageia.org/software/monitor-edid/
monitor-get-edid -v --try-in-console --max-vbe-port 6 > edid.bin (or --vbe-port X if multiple monitors)
or directly with the C tool (X=0..6): monitor-get-edid-using-vbe -v --try-in-console --port X > edid.bin
However, I don't know if fglrx interferes with it (I know nvidia proprietary driver doesn't/didn't).