Yeah, the goal is that X can do this by itself, and I guess other
distros are using "get-edid|parse-edid" or something similar to make
this happen. Since your get-edid output is similar to the one I get on
my samsung syncmaster 900NF monitor, I guess that X discards your
monitors edid information too. Are you sure you don't have the monitor
section filled with data about the monitor when using the "nv" driver?
I guess that nvidia binary driver could have separate edid code, but I
doubt that "nv" has one.

I hope we'll have some code in Xorg server soon, so you'll be able to
test the fix.

On 6/9/07, Jerone Young <[EMAIL PROTECTED]> wrote:
> Nvidia driver & NV driver seem to read the edid just fine. Also on other
> distros things are fine...but when I run get-edid under Feisty I get
> this:
>
> [EMAIL PROTECTED]:~# 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 supports 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
> EDID claims 255 more blocks left
> EDID blocks left is wrong.
> Your EDID is probably invalid.
> ��������������������������������������������������������������������������������
>
> --
> Problems with xresprobe & Samsung 243T LCD
> https://bugs.launchpad.net/bugs/27667
> You received this bug notification because you are a direct subscriber
> of the bug.
>

-- 
Problems with xresprobe & Samsung 243T LCD
https://bugs.launchpad.net/bugs/27667
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to