Messages in this thread | | | Date | Sun, 4 Feb 2007 22:17:08 +0100 | From | "Giuseppe Bilotta" <> | Subject | Re: [Linux-fbdev-devel] [PATCH] nvidiafb: allow ignoring EDID info |
| |
On 2/4/07, Luca Tettamanti <kronos@people.it> wrote: > Giuseppe, can you send me the EDID block of your monitor?
I'd gladly do it, if I knew how to retrieve it ... because apparently, get-edid doesn't work, even though both the nv driver for X and nvidiafb manage to retrieve it.
This is the output from get-edid
""" get-edid: get-edid version 1.4.1
Performing real mode VBE call Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0 Function supported Call successful
VBE version 300 VBE string at 0x11110 "NVidia"
VBE/DDC service about to be called Report DDC capabilities
Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0 Function supported Call successful
Monitor and video card combination does not support DDC1 transfers Monitor and video card combination does not support DDC2 transfers 0 seconds per 128 byte EDID block transfer Screen is not blanked during DDC transfer
Reading next EDID block
VBE/DDC service about to be called Read EDID
Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0 Function supported Call failed
The EDID data should not be trusted as the VBE call failed Error: output block unchanged """
Anything else I can try?
-- Giuseppe "Oblomov" Bilotta - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |