Reading DisplayPort DDC/CI under linux using libdrm -


i'm trying read ddc information monitor attached displayport link of laptop.

thus i'm looking i2cdetect , i2cdump couldn't find attached /dev/i2c bus.

my next step access through libdrm, , had set drmmodeconnector comes next?

according dekkard's answer tried

sudo i2cdetect -l i2c-0   i2c         i915 gmbus ssc                      i2c adapter i2c-1   i2c         i915 gmbus vga                      i2c adapter i2c-2   i2c         i915 gmbus panel                    i2c adapter i2c-3   i2c         i915 gmbus dpc                      i2c adapter i2c-4   i2c         i915 gmbus dpb                      i2c adapter i2c-5   i2c         i915 gmbus dpd                      i2c adapter i2c-6   i2c         dpddc-b                             i2c adapter i2c-7   smbus       smbus i801 adapter @ efa0          smbus adapter 

which shows panel attached i2c-2 , displayport i2c-6. when run $ sudo get-edid -b 6 leads to:

$ sudo get-edid -b 6 2 potential busses found: 2 6 trying 6 per request. bus 6 doesn't have edid... couldn't find accessible edid on computer. attempting use classical vbe interface      performing real mode vbe call     interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0     function supported     call successful      vbe version 300     vbe string @ 0x11100 "intel(r) sandybridge/ivybridge graphics chipset accelerated vga bios"  vbe/ddc service called     report ddc capabilities      performing real mode vbe call     interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0     function supported     call successful      monitor , video card combination not support ddc1 transfers     monitor , video card combination supports ddc2 transfers     0 seconds per 128 byte edid block transfer     screen not blanked during ddc transfer  reading next edid block  vbe/ddc service called     read edid      performing real mode vbe call     interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0     function supported     call failed  edid data should not trusted vbe call failed looks vbe successful. have day. 

although help! @dekkard

could give me hint or post tutorials?

thanks lot , best regards,

befedo

try

sudo get-edid 

get-edid, parse-edid - read-edid tools retrieve , interpret monitor specifications using vesa vbe ddc protocol

for more info see here: http://manpages.ubuntu.com/manpages/lucid/man1/get-edid.1.html

update:

try ddccontrol:

also, might lead solution:

https://unix.stackexchange.com/questions/114359/how-to-get-edid-for-a-single-monitor


Comments

Popular posts from this blog

asp.net mvc - SSO between MVCForum and Umbraco7 -

Python Tkinter keyboard using bind -

ubuntu - Selenium Node Not Connecting to Hub, Not Opening Port -