edidfail for widescreen lcd (viewsonic vg2030wm) causes incorrect resolution and refresh rates

[lexual]

Binary package hint: xorg

Hi,

feisty isn't setting my Viewsonic vg2030wm 22" wide-screen LCD monitor to it's native resolution (1680x1050).

http://www.viewsonic.com.au/products/productspecs.php?id=273&s=specs

video-card is NVIDIA 6600gt (Leadtek).

I have attached my Xorg.0.log and xorg.conf

From what I can see, the horizontal sync range isn't set correctly:
HorizSync 28-51

from Xorg.0.log:
(**) NV(0): Default mode "1680x1050": 147.1 MHz, 65.2 kHz, 60.0 Hz

so line should be:
HorizSync 24-92 (or at least above 65)

If I patch xorg.conf with:
<snip>
--- xorg.conf-feisty 2007-03-23 17:13:52.000000000 +1100
+++ /etc/X11/xorg.conf 2007-03-23 17:32:54.000000000 +1100
@@ -97,7 +97,7 @@ EndSection
 Section "Monitor"
        Identifier "Generic Monitor"
        Option "DPMS"
- HorizSync 28-51
+ HorizSync 24-92
        VertRefresh 43-60
 EndSection

@@ -128,7 +128,7 @@ Section "Screen"
        EndSubSection
        SubSection "Display"
                Depth 24
- Modes "1024x768" "800x600" "640x480"
+ Modes "1680x1050" "1024x768" "800x600" "640x480"
        EndSubSection
 EndSection
</snip>

Everything is working again.
Please let me know what additional is needed so that ubuntu can rock on this hardware.

[Timo Aaltonen (tjaalton)]

please attach the output of 'sudo ddcprobe' and 'sudo xresprobe nv'.

[lexual (lexhider)]

$ sudo ddcprobe
vbe: VESA 3.0 detected.
oem: NVIDIA
vendor: NVIDIA Corporation
product: nv43 Board - p216h0 Chip Rev
memory: 131072kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x16
mode: 800x600x256
mode: 1024x768x16
mode: 1024x768x256
mode: 1280x1024x16
mode: 1280x1024x256
mode: 320x200x64k
mode: 320x200x16m
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x64k
mode: 1280x1024x16m
edid:
edidfail

$ sudo xresprobe nv
id:
res:
freq:
disptype:

[Timo Aaltonen (tjaalton)]

so, it doesn't get the EDID from the monitor. Try moving the xorg.conf aside to see if the server can use correct values.

[lexual (lexhider)]

Do you mean run X without an xorg.conf in /etc/X11 ?

[By the way, fedora 6 correctly sets up 1680x1050 for this monitor].

[lexual (lexhider)]

Starting X without an /etc/X11/xorg.conf, does run in the correct resolution: 1680x1050 on this monitor!

[Timo Aaltonen (tjaalton)]

Just as I thought :)

I'll see what can be done about the xresprobe failing to read EDID. Please attach the Xorg.0.log when you started it without config.

[Sander D (sanderd)]

Is this the same bug as "X.org doesn't detect widescreen resolution"?
https://bugs.launchpad.net/ubuntu/+source/xresprobe/+bug/63551

[Bryce Harrington (bryce)]

Can those seeing this bug please install the read-edid package (sudo apt-get install read-edid) and then post the results of running:

  get-edid | read-edid

I've read that ddcprobe only handles edid 1.0 data, and returns edidfail in other cases. get-edid is used by other distros, and supposedly handles versions of edid above 1.0. Your data could help confirm or disprove this.

[Daniel Hahler (blueyed)]

The correct command would be:
$ sudo get-edid | parse-edid

Here's my output (as provided before at https://bugs.edge.launchpad.net/ubuntu/+source/xorg/+bug/49827/comments/25):
$ sudo get-edid | parse-edid
parse-edid: parse-edid version 1.4.1
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
parse-edid: IO error reading EDID

[SugarD-x (sugajack2004)]

I've got ddc2 working but not ddc1. One monitor is 19" WideScreen LCD (DVI), second is 16" Standard LCD (VGA). Ubuntu Linux 7.10 Gutsy Gibbon Official Release. Main GPX: ATI Radeon X1300 PCI Dual-DVI/VGA Graphics Card. Secondary (Not being used): Dell/Intel 865 Onboard Video VGA Chipset.

My EDID data from the readout:

parse-edid: parse-edid version 1.4.1
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 0xc0248 "ATI ATOMBIOS"

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 successful

parse-edid: EDID checksum passed.

        # EDID version 1 revision 3
Section "Monitor"
        # Block type: 2:0 3:fd
        # Block type: 2:0 3:fc
        Identifier "HW191D"
        VendorName "HSD"
        ModelName "HW191D"
        # Block type: 2:0 3:fd
        HorizSync 30-80
        VertRefresh 49-75
        # Max dot clock (video bandwidth) 140 MHz
        # Block type: 2:0 3:fc
        # Block type: 2:0 3:ff
        # DPMS capabilities: Active off:yes Suspend:no Standby:no

        Mode "1440x900" # vfreq 59.887Hz, hfreq 55.935kHz
                DotClock 106.500000
                HTimings 1440 1520 1672 1904
                VTimings 900 903 909 934
                Flags "+HSync" "-VSync"
        EndMode
        # Block type: 2:0 3:fd
        # Block type: 2:0 3:fc
        # Block type: 2:0 3:ff
EndSection

[wuddiwupp (stefan-wuttke)]

I have the same problem with my Vaio vgn-fs115b, ddc1 not works, only ddc2.

parse-edid version 1.4.1
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 "Intel(r)915GM/910ML/915MS Graphics Chip Accelerated VGA BIOS"

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
parse-edid: EDID checksum passed.

        # EDID version 0 revision 0
Section "Monitor"
        # Block type: 2:0 3:0
        # Block type: 2:0 3:0
        # Block type: 2:0 3:0
        # Block type: 2:0 3:0
        Identifier "@@@:0000"
        VendorName "@@@"
        ModelName "@@@:0000"
        # Block type: 2:0 3:0
        # Block type: 2:0 3:0
        # Block type: 2:0 3:0
        # Block type: 2:0 3:0
        # DPMS capabilities: Active off:no Suspend:no Standby:no

        # Block type: 2:0 3:0
        # Block type: 2:0 3:0
        # Block type: 2:0 3:0
        # Block type: 2:0 3:0
EndSection

[Michael Olson (rosciol+launchpad)]

Same general idea, another datapoint? I have a GeForce 7300 LE PCI Express card and a 24" BenQ FP241VW monitor. I've had all sorts of difficulties with Xorg and with Gnome not wanting to run my monitor above a 50Hz refresh rate. Most of the time I can get Xorg to figure things out if none of the modelines in Xorg.conf are correct.

molson@daedalus:/etc/powersave$ sudo xresprobe nvidia
id:
res:
freq:
disptype:
molson@daedalus:/etc/powersave$ sudo ddcprobe
vbe: VESA 3.0 detected.
oem: NVIDIA
vendor: NVIDIA Corporation
product: G72 Board - p280h18 Chip Rev
memory: 131072kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x16
mode: 800x600x256
mode: 1024x768x16
mode: 1024x768x256
mode: 1280x1024x16
mode: 1280x1024x256
mode: 320x200x64k
mode: 320x200x16m
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x64k
mode: 1280x1024x16m
edid:
edidfail
molson@daedalus:/etc/powersave$ sudo get-edid | parse-edid
parse-edid: parse-edid version 1.4.1
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
parse-edid: IO error reading EDID

[pinkfloydhomer (david-rasmussen)]

Same deal here, freshly installed gutsy, GeForce 6600GT, Samsung 226BW. I won't post details, as they look exactly like everybody elses here.

This issue is new in Gutsy, was not a problem in Feisty.

What is the source of this issue and will it be solved?

[Fred (eldmannen+launchpad)]

I have GeForce 8600GT and Samsung SyncMaster 900SL+ (19" CRT).
I get 'edidfail' too. :(

[ccmmss (martin-salgueiro)]

So?... is there any news?. I've the same problem with my Viewsonic!. It happens after a fresh install of gutsy. My previous installation was a Feisty (AMD64) upgraded to Gutsy and works without any problem.

Now, I've installed Gutsy (X86) and cannot use my nvidia driver at 1680x1050. Do you need any information?

Thanks.

[Timo Aaltonen (tjaalton)]

xresprobe is being deprecated, and as in this case the xserver manages to get the EDID-data we'll be relying on xserver to get the right mode.

[ccmmss (martin-salgueiro)]

thanks Timo... but... is there any workaround?... something that i could do?. Should I back to Feisty?... connect my LCD using the VGA adapter?

[ccmmss (martin-salgueiro)]

Maybe... another option is not use the nvidia restricted drivers. With the "nv" driver I get a 1280x1024 resolution, works, but without acceleration.

[ccmmss (martin-salgueiro)]

Using the VGA adapter works. Is there anyone working with this bug?. Can I help?

[H_Plow (brtdth)]

Same here

Monitor: Samsung Syncmaster 206BW
Ubuntu Gutsy (AMD64)
Video Card: ATI RADEON X850XT 256MB (R480)
Connection in use: DVI - DVI
Driver in use: "vesa"--> note: I've tried latest fglrx from ATI (8.443.1) installing with Envy....but NOWAY: whenever I write "fglrx" as a driver in xorg.conf...everything get messed up...monitor signal disconnected and unrecoverable system hanging).

After very long time loss with fglrx I forsake it and had a lot to work to let "vesa" native driver to work at an higher (and proper aspect) resolution than 1024x768.....

My last "best" result is having my video-card working on DVI connector at 1400x1050@60Hz....

Of course in my xorg.conf it's correctly written "1680x1050@60" (suggested freq and refresh for my LCD display...) and "1400x1050@60" IS NEITHER WRITTEN IN xorg.conf NOR RESULTING BY "sudo ddcprobe" !!!!!!!!!

Something looks wrong with DDC and EDID.....

Any suggestion?
Cheers

P.S. Maybe a DVI/VGA adapter can "workaround" this problem, but I can't use it because the VGA connector of my display has actually plugged another PC....

[SugarD-x (sugajack2004)]

My ViewSonic at the time was and still is hooked up via a VGA connection. It is my smaller of the 2 monitors with a maximum resolution of 1024x768, and is set as the secondary monitor. My primary monitor I cannot think of the name/model of at this time as I'm not at home, but it's maximum resolution on a DVI connection is 1400x900 WideScreen. The secondary monitor is a standard, non-widescreen model.

[Fred (eldmannen+launchpad)]

$ sudo ddcprobe
vbe: VESA 3.0 detected.
oem: NVIDIA
vendor: NVIDIA Corporation
product: GW-P/N@PM898486GTQ14P:0 GW-CLK@�
�
 �
memory: 14336kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x16
mode: 800x600x256
mode: 1024x768x16
mode: 1024x768x256
mode: 1280x1024x16
mode: 1280x1024x256
mode: 320x200x64k
mode: 320x200x16m
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x64k
mode: 1280x1024x16m
edid:
edidfail

$ sudo xresprobe nv
id:
res:
freq:
disptype:

Please, can someone fix this so it works! This EDID bug is really important!
And it really really needs to get fixed!

[Timo Aaltonen (tjaalton)]

xresprobe is not used anymore. If you have issues with Hardy alpha2, the bug is likely in the nv driver.

[Timo Aaltonen (tjaalton)]

Hi, xresprobe is no longer used in Hardy Heron, the development version which will become Ubuntu 8.04. Because of that I'm closing this bug. Please test Hardy (alpha3 or later), and if your hardware still fails to get a correct resolution (or if it drops to failsafe mode), file a bug against the driver package (xserver-xorg-video-$driver). Thanks!

[Brian Murray (brian-murray)]

The xorg.conf at http://launchpadlibrarian.net/6900888/xorg.conf-PATCH and attached to this bug is problematic for the following reason:
SubSections can be closed only after being previously opened.