<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Split screen/display corruption issue on HP EliteOne 800 G2 23-in Touch AIO" href="https://bugs.freedesktop.org/show_bug.cgi?id=97822#c33">Comment # 33</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Split screen/display corruption issue on HP EliteOne 800 G2 23-in Touch AIO" href="https://bugs.freedesktop.org/show_bug.cgi?id=97822">bug 97822</a> from <a class="email" href="mailto:r.r.arends@hr.nl" title="r.r.arends@hr.nl">r.r.arends@hr.nl</a> <pre>(In reply to Ville Syrjala from <a href="show_bug.cgi?id=97822#c31">comment #31</a>) > Hmm. I guess one weird possibility would be that the EDID would be at some > alternate address. I can't recall if that's allowed by the spec, but IIRC in > the distant past there were a few addresses that could house the EDID. > > Please run something like this as root so we can probe the entire i2c > address range: > modprobe i2c-dev ; i2cdetect `grep DPDDC-A /sys/class/i2c-dev/*/name | cut > -d '/' -f 5 | cut -d '-' -f 2` root@fuckeduphp:~# modprobe i2c-dev ; i2cdetect `grep DPDDC-A /sys/class/i2c-dev/*/name | cut -d '/' -f 5 | cut -d '-' -f 2` WARNING! This program can confuse your I2C bus, cause data loss and worse! I will probe file /dev/i2c-3. I will probe address range 0x03-0x77. Continue? [Y/n] Y 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10: 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20: 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30: 30 -- -- -- -- 35 -- -- 38 39 3a 3b 3c 3d 3e 3f 40: 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50: -- -- -- -- -- -- -- 57 -- -- -- -- -- -- -- -- 60: 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70: 70 71 72 73 74 75 76 77</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>