MASTER: EDID fail

Bug #194760 reported by Fred
124
This bug affects 10 people
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Invalid
Wishlist
Unassigned

Bug Description

Current xorg in Hardy usually autodetects your monitor, it's resolution, dpi, etc. and everything just magically works. This happens because modern monitors can be queried for 'EDID' data, that returns all the necessary info to configure things properly.

However, there are cases where the monitor fails to report EDID. These exhibit themselves as a variety of symptoms, often including incorrect resolution selection, strange font dpi settings, inability to select resolutions other than 640x480, 800x600, 1024x768, and sometimes other odd issues. To determine if you have this issue, simply run `sudo ddcprobe` or `sudo get-edid | parse-edid`, and you will see 'EDID fail' in the output.

There are several causes for EDID fail reads. One is if you're using a truly ancient monitor from the days before EDID. A second is if you're using a video extension cable, KVM, or other piece of equipment connected between the monitor and the video card that lacks the EDID wire. In both these cases, you have a hardware issue, and there's nothing that can be done in software to get around it - you'll need to either get different hardware, or familiarize yourself with xorg.conf syntax and do your configuration yourself.

But there are also some unexplained EDID failures beyond these, and that's what this bug report is for. If you're experiencing this issue, feel free to add details of your problem here, but make sure to include the following:

1. The exact manufacturer and model id for your monitor (it is usually written on the back of the monitor)

2. Your Xorg.0.log (or Xorg.0.log.old) from after a failed boot

3. Install the 'read-edid' package, run `sudo get-edid > edid.dat` and then attach that file (it's binary, so don't copy/paste).

4. The correct HorizSync and VertRefresh ranges for your monitor. This is typically written in your monitor's documentation; if you don't have it handy, it's often available online from your monitor manufacturer's website. Laptop users (esp. macbooks) may not have this info available, but get what you can.

If your monitor is misreporting EDID (as opposed to not reporting it at all), then sometimes the issue can be solved by adding quirks for your monitor, if we have the above 4 pieces of data. Sometimes, if it's an established quirk, we can fairly easily backport those to prior versions of Ubuntu.

There are several different versions of EDID, and it sometimes happens that a newer version of EDID will be used by a monitor, that Xorg may not yet comprehend. In these cases, we simply need to examine the new EDID structure and adapt Xorg to accept it.

If your monitor is not reporting EDID at all, or if your video card is somehow invalidating it before it can be read, then this is a bigger problem. Try your monitor with a different computer and/or different video card, to identify if the issue is particular to the video card; if so, please report this and attach your lspci -vvnn. If the monitor fails the same way regardless of what video card it's attached to, then it's probably just a bad monitor. There may be nothing that can be done in this case, but report all the info about the monitor anyway, just in case new ideas come to light later. For example, bug #288807 involves this situation with a particular old laptop model, so we could possibly trigger a quirk from the hostbridge and chip.

[Original Report]
There seems to be a problem retrieving EDID data. (Extended display identification data)
* http://en.wikipedia.org/wiki/Extended_display_identification_data

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"

$ uname -a
Linux ubuntu 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686 GNU/Linux

xorg 1:7.3+10ubuntu5
xserver-xorg 1:7.3+10ubuntu5
xserver-xorg-core 2:1.4.1~git20080131-1ubuntu4
xresprobe 0.4.24ubuntu8
nvidia-glx-new 169.09+2.6.24.9-8.25
nvidia-kernel-common 20051028+1ubuntu8

Samsung SyncMaster 900SL Plus (19", CRT)
* http://downloadcenter.samsung.com/content/UM/200301/20030125151045333_900SLPLUS_EN.pdf (manual)

Gainward GeForce 8600GT (256MB GDDR3, PCI-Express) - connected to monitor via VGA (DVI->VGA adapter).
* http://www.nvidia.com/object/geforce_8600.html
* http://www.gainward.com/product/product_detail.php?products_id=105

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

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

$ 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

[ 30.234827] nvidia: module license 'NVIDIA' taints kernel.
[ 30.499265] NVRM: loading NVIDIA UNIX x86 Kernel Module 169.09 Fri Jan 11 14:38:28 PST 2008

01:00.0 VGA compatible controller: nVidia Corporation GeForce 8600 GT (rev a1)

01:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 8600 GT [10de:0402] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: CardExpert Technology Unknown device [10b0:0401]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 0
 Interrupt: pin A routed to IRQ 16
 Region 0: Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
 Region 1: Memory at d0000000 (64-bit, prefetchable) [size=256M]
 Region 3: Memory at fa000000 (64-bit, non-prefetchable) [size=32M]
 Region 5: I/O ports at dc00 [size=128]
 [virtual] Expansion ROM at feae0000 [disabled] [size=128K]
 Capabilities: [60] Power Management version 2
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
  Address: 0000000000000000 Data: 0000
 Capabilities: [78] Express Endpoint IRQ 0
  Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+
  Device: Latency L0s <512ns, L1 <4us
  Device: AtnBtn- AtnInd- PwrInd-
  Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
  Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
  Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
  Link: Supported Speed 2.5Gb/s, Width x16, ASPM L0s L1, Port 0
  Link: Latency L0s <512ns, L1 <4us
  Link: ASPM Disabled RCB 128 bytes CommClk+ ExtSynch-
  Link: Speed 2.5Gb/s, Width x16

description: updated
Revision history for this message
Fred (eldmannen+launchpad) wrote :

$ cat /proc/version_signature
Ubuntu 2.6.24-8.14-generic

$ cat /proc/driver/nvidia/version
NVRM version: NVIDIA UNIX x86 Kernel Module 169.09 Fri Jan 11 14:38:28 PST 2008
GCC version: gcc version 4.2.3 (Ubuntu 4.2.3-1ubuntu2)

$ cat /proc/driver/nvidia/registry
EnableVia4x: 0
EnableALiAGP: 0
NvAGP: 3
ReqAGPRate: 15
EnableAGPSBA: 0
EnableAGPFW: 0
Mobile: 4294967295
ResmanDebugLevel: 4294967295
RmLogonRC: 1
ModifyDeviceFiles: 1
DeviceFileUID: 0
DeviceFileGID: 0
DeviceFileMode: 438
RemapLimit: 0
UseCPA: 4294967295
UseVBios: 1
RMEdgeIntrCheck: 1

$ cat /proc/driver/nvidia/cards/0
Model: GeForce 8600 GT
IRQ: 16
Video BIOS: 60.84.35.00.00
Card Type: PCI-E
DMA Size: 40 bits
DMA Mask: 0xffffffffff
Bus Location: 01.00.0

$cat /proc/devices | grep nvidia
195 nvidia

$cat /proc/iomem | grep Video
000a0000-000bffff : Video RAM area
000c0000-000ccbff : Video ROM

$ dpkg -l read-edid | cat
read-edid 1.4.1-2.1

$ 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

Revision history for this message
Fred (eldmannen+launchpad) wrote :

Attachment with very much information.

Revision history for this message
Bryce Harrington (bryce) wrote :

The edidfail is not due to xresprobe but rather due to something incorrect with how your monitor reports its EDID information to the X server. Refiling against xorg-server.

Please attach your /var/log/Xorg.0.log, /etc/X11/xorg.conf, and the output of lspci -vvnn

Changed in xresprobe:
status: New → Incomplete
Revision history for this message
Fred (eldmannen+launchpad) wrote :

So there is a bug in the firmare in the Samsung SyncMaster 900SL Plus or something?

Output from 'lspci -vvnn' attached.

Revision history for this message
Fred (eldmannen+launchpad) wrote :

My xorg.conf configuration file attached.

Revision history for this message
Fred (eldmannen+launchpad) wrote :

My /var/log/Xorg.0.log file is attached, as requested.

Revision history for this message
Fred (eldmannen+launchpad) wrote :

I provided all information requested.

Changed in xorg-server:
status: Incomplete → New
Bryce Harrington (bryce)
Changed in xorg-server:
importance: Undecided → High
status: New → Triaged
Bryce Harrington (bryce)
description: updated
Revision history for this message
Fred (eldmannen+launchpad) wrote :

Okay, I read your edit of post.

It may be because I use a VGA (DVI->VGA adapter). Because my monitor only have VGA, and graphics card only have DVI.

H: 30 - 110 kHz
V: 50 - 160Hz

Revision history for this message
M Pietila (pietila-meghan) wrote :

I started up a separate bug for my particular monitor/video card combo, and attached all the information to it. Seemed cleaner than merging it into this bug--however, if anyone is still monitoring this bug, here's a link to the one I created:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/211098

Revision history for this message
unixnewbie (darfsten) wrote :

I am still using Feisty Fawn so I don't have any issues running sudo dpkg-reconfigure xserver-xorg or using nvidia-settings to setup my dual head setup running 2 seperate screens (it's a Nvidia 6200 with agp and dvi). Now that I see this is happening, I am scared to upgrade. Please fix this issue. I also use a kvm, my ubuntu box vga out goes into the kvm and the dvi out goes to a lcd tv as my seperate screen. My windows box agp out goes into the other agp on the kvm. I own a 17" Princeton Synergy 714 and the other 17" LCD TV per xorg.conf is Philips PHL 17PF8946.

cat /proc/version_signature
Ubuntu 2.6.20-16.35-generic

cat /proc/driver/nvidia/version
NVRM version: NVIDIA UNIX x86 Kernel Module 100.14.23 Thu Oct 4 10:16:34 PDT 2007
GCC version: gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)

cat /proc/driver/nvidia/registry
VideoMemoryTypeOverride: 1
EnableVia4x: 0
EnableALiAGP: 0
NvAGP: 3
ReqAGPRate: 15
EnableAGPSBA: 0
EnableAGPFW: 0
SoftEDIDs: 1
Mobile: 4294967295
ResmanDebugLevel: 4294967295
FlatPanelMode: 0
DevicesConnected: 0
RmLogonRC: 1
VbiosFromROM: 0
ModifyDeviceFiles: 1
DeviceFileUID: 0
DeviceFileGID: 0
DeviceFileMode: 438
RemapLimit: 0
UseCPA: 4294967295
DetectPrimaryVga: 1
EnableBrightnessControl: 0
PanelPWMFrequency: 1018
PanelBrightnessLimits: 65280
UseVBios: 1
RMEdgeIntrCheck: 1

 cat /proc/driver/nvidia/cards/0
Model: GeForce 6200
IRQ: 23
Video BIOS: 05.44.a2.07.00
Card Type: AGP
DMA Size: 32 bits
DMA Mask: 0xffffffff
Bus Location: 01.00.0

cat /proc/devices | grep nvidia
195 nvidia

000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM

read-edid
Version: 1.4.1-2.1

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

Revision history for this message
Cody Boisclair (codeman38) wrote :

I have a Gateway Solo 9500 laptop (from approximately 2001) which has a 1024x768 built-in display, but which is being incorrectly detected as only capable of 800x600. As it turns out, running ddcprobe does indeed turn up the "edidfail" message.

This being a laptop display panel, I'm not sure what the correct HorizSync and VertRefresh values are.

I will be attaching my Xorg.0.log and edid.dat in subsequent attachments.

Revision history for this message
Cody Boisclair (codeman38) wrote :
Revision history for this message
Cody Boisclair (codeman38) wrote :

The error displayed on stderr when get-edid is run:

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 19 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.

Revision history for this message
Defalco (scalo-54) wrote : acer fp581

my max resolution is 600x480 on acefp581, nvidia geforce 7600 gs, kubuntu 8.04 (hardy).
This is the response from edid:(sudo get-edid > edid.dat)

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

please HELP ME, i don't know what to doooooo

Revision history for this message
Fred (eldmannen+launchpad) wrote : Re: EDID fail

Defalco,
You could manually edit the /etc/X11/xorg.conf file (make a backup of it first), and add the refresh rate range for your monitor.

Revision history for this message
DickeyWang (hwang313000) wrote :

I'm also having this problem on my 14" Lenovo Thinkpad T61p (with Nvidia Quadro FX 570M video card, LCD native resolution is 1400x1050), and since it's a laptop, I can not get informations like bandwidth/frequencies of the LCD. Although I did find something that may be interesting: when running the open source mesa driver, I can set the monitor into 1400x1050, 1024x768, 800x600, 640x480, however the resolution 1280x960 is missing, on the other hand, when I use the restricted driver (both 169.12 and 173.14.05 via EnvyNG), both 1400x1050 and 1280x960 is selectable, but the resolution of 1024x768 and 800x600 is missing, instead I see some weird resolutions like 800x512 or something.
Anyway, attached here is a bug report log file that I generated using "startx -- -logverbose 6" and "nvidia-bug-report.sh" (comes with the restricted Nvidia driver ), and part of it reads:
(--) NVIDIA(0): Raw EDID bytes:
(--) NVIDIA(0):
(--) NVIDIA(0): 00 ff ff ff ff ff ff 00 30 ae 22 40 00 00 00 00
(--) NVIDIA(0): 22 11 01 03 80 1d 15 78 ea 6f 95 9c 54 4c 87 26
(--) NVIDIA(0): 21 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01
(--) NVIDIA(0): 01 01 01 01 01 01 30 2a 78 20 51 1a 10 40 30 70
(--) NVIDIA(0): 13 00 1f d7 10 00 00 18 25 23 78 20 51 1a 10 40
(--) NVIDIA(0): 30 70 13 00 1f d7 10 00 00 18 00 00 00 0f 00 90
(--) NVIDIA(0): 43 32 90 43 28 0f 01 00 30 64 00 55 00 00 00 fe
(--) NVIDIA(0): 00 4c 54 44 31 34 31 45 4e 39 42 0a 20 20 00 f7
(--) NVIDIA(0):
(--) NVIDIA(0): --- End of EDID for LEN (DFP-0) ---
(--) NVIDIA(0):
(II) NVIDIA(0): Frequency information for LEN (DFP-0):
(II) NVIDIA(0): HorizSync : 53.299-63.981 kHz
(II) NVIDIA(0): VertRefresh : 50.000-60.000 Hz
(II) NVIDIA(0): (HorizSync from EDID)
(II) NVIDIA(0): (VertRefresh from EDID)
I suspect the HorizSync value is wrong, but I don't know much about the EDID stuff. The detailed bug log file is attached.

Revision history for this message
Anlace (gail-laforest) wrote :
Download full text (33.3 KiB)

This monitor and video card setup works perfectly in Windows XP Pro. The monitor worked perfectly with Ubuntu/KDE 6.10 and older versions. It also works perfectly in all versions of OS X. In all cases the monitor is using a DVI connection and switching to a VGA adapter did not correct the problem (there is no VGA output for this vid card). I haven't tried using the latest driver from Nvidia's web site yet.

Video Card is Nvidia GeForce 9800 GTX.

1. The exact manufacturer and model id for your monitor
     ViewSonic VX2025WM

2. Your Xorg.0.log (or Xorg.0.log.old) from after a failed boot

This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.

X.Org X Server 1.4.0.90
Release Date: 5 September 2007
X Protocol Version 11, Revision 0
Build Operating System: Linux Ubuntu (xorg-server 2:1.4.1~git20080131-1ubuntu9.2)
Current Operating System: Linux gail-kde 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686
Build Date: 13 June 2008 01:08:21AM

 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Jul 15 07:33:23 2008
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "Configured Monitor"
(**) | |-->Device "Configured Video Device"
(==) Automatically adding devices
(==) Automatically enabling devices
(==) No FontPath specified. Using compiled-in default.
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
 Entry deleted from font path.
(==) FontPath set to:
 /usr/share/fonts/X11/misc,
 /usr/share/fonts/X11/100dpi/:unscaled,
 /usr/share/fonts/X11/75dpi/:unscaled,
 /usr/share/fonts/X11/Type1,
 /usr/share/fonts/X11/100dpi,
 /usr/share/fonts/X11/75dpi,
 /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType
(==) RgbPath set to "/etc/X11/rgb"
(==) ModulePath set to "/usr/lib/xorg/modules"
(==) |-->Input Device "Configured Mouse"
(==) |-->Input Device "Generic Keyboard"
(==) The core pointer device wasn't specified explicitly in the layout.
 Using the first core pointer device.
(==) The core keyboard device wasn't specified explicitly in the layout.
 Using the first keyboard device.
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Loader magic: 0x81dc500
(II) Module ABI versions:
 X.Org ANSI C Emulation: 0.3
 X.Org Video Driver: 2.0
 X.Org XInput driver : 2.0
 X.Org Server Extension : 0.3
 X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules//libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
 compiled for 1.4.0...

Revision history for this message
Andreas Heinlein (aheinlein) wrote :

I have a problem that may or may not be related. I have seen several cases where X autoconfig does not work correctly, i.e. you only get 640x480 and have to correct it with displayconfig-gtk. Some of these cases were related to complete edid failures as described, but I found at least one case where the ouput of 'sudo ddcprobe' looks good including edid data, but 'sudo get-edid | parse edid' returns nonsense, telling "The EDID data should not be trusted as the VBE call failed" and resolutions like 3840x2560. read-edid also complains that the monitor always claims there are 32 edid blocks left; the whole get-edid thing takes about 10-12s.
Monitor is a Belinea 106055 (CRT) with a 'real' maximum resolution of 1600x1200, refresh 30-96kHz, vrefresh 50-160Hz.
This is also one of the cases where the 'old' way from Feisty and Gutsy worked, whereas the 'hardy' way does not :-(

Revision history for this message
Andreas Heinlein (aheinlein) wrote :
Revision history for this message
Caroline Ford (secretlondon) wrote :

I'm using x86_64 which doesn't have read_edid (it is i386 and powerpc only). How is it intended to set up X properly on this architecture?

Revision history for this message
Caroline Ford (secretlondon) wrote :

secret@elektronika:~$ sudo ddcprobe
[sudo] password for secret:
vbe: VESA 3.0 detected.
oem: NVIDIA
vendor: NVIDIA Corporation
product: G84 Board - p403h02 Chip Rev
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

secret@elektronika:~$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 1024 x 768
VGA1 disconnected
DVI0 disconnected
VGA2 connected 1024x768+0+0 0mm x 0mm
   1024x768 60.0*
   800x600 60.3
   640x480 59.9
   680x384 119.6 119.9
   576x432 120.1
   512x384 120.0
DVI1 disconnected

Revision history for this message
Caroline Ford (secretlondon) wrote :

Monitor is Acer W193X and should be 1440x900 @ 60 Hz.

description: updated
Revision history for this message
Fred (eldmannen+launchpad) wrote :

Tools report that EDID fail.
However the monitor works perfectly tough. Even without any Xorg config file, it gets auto-detected correctly.

Samsung SyncMaster 2493HM (connected straight via DVI to Gainward GeForce 8600GT)
Ubuntu 8.10 Intrepid Ibex (alpha)
kernel: 2.6.27-2-generic
xorg: 1:7.4~1ubuntu1
xserver-xorg-core 2:1.4.99.906-2ubuntu5

--
$ 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 get-edid > edid.dat
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
--

Revision history for this message
Thomas B Homburg (thomasbhomburg) wrote :

EDID works sometimes:

NVIDIA GPU GeForce 7600 GS (G73)
Monitor: Manufact: LG, Model ID: LG 32LC51, Description: 32" lcd tv, 16/10

sudo dccprobe says: "edidfail"
sudo get-edid > edid.data says get-edid: output block unchanged"

Valid HorizSync and VertRefresh from the manual:
640x350 31,5 70,1
720x400 31,5 70,1
640x480 31,5 59,9
848x480 31,5 60,0
852x480 31,5 60,0
800x600 37,9 60,3
1024x768 48,4 60,0
1280x768 47,8 59,9
1360x768 47,7 59,8
1366x768 47,7 59,8

Revision history for this message
Thomas B Homburg (thomasbhomburg) wrote :

Workaround for NVIDIA7600/LGTV in the last post:
http://gentoo-wiki.com/HOWTO_Xorg_HDTV

Setting
Option "ModeValidation" "NoMaxSizeCheck, NoHorizSyncCheck, NoVertRefreshCheck"

Revision history for this message
cutterjohn (moylanj) wrote :

Well, I believe that I've been experiencing the EDID parse failure as my notebook exhibits ALL of the symptons listed here, limited to one resolution(fortunately highest native LCD res), ddcprobe EDID fail, xrandr one res(highest) reported, read-edid and parsing fail as everyone else's above does.

MSI MS-1651 WSXGA+ LCD (1680 x 1050), P8600, 2 x 2GB Kingston ValueRAM CL5, WDC WD3200BEVT (320GB non-base 10 impared, c. 300GB to everyone else), 9600M GT 512MB GDDR3 (This is basically the same thing as the MSI GX620 -038 US model.) nVidia 177.80 restricted drives in use.

The nVidia driver thinks that the LCD panel is a seiko, but looking inside of the dump for edid that I get using the nVidia driver it is identified as a Samsung LTN154P4-L01. Only could turn up an LTN150 on Samsung's site, so I've no clue as to the correct sync and refresh values.

Revision history for this message
cutterjohn (moylanj) wrote :

EDID from nvidia driver dump

Revision history for this message
cutterjohn (moylanj) wrote :

get-edid > edid.out results in 0byte edid.out file, but here is the output
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

and ddcprobe:
vbe: VESA 3.0 detected.
oem: NVIDIA
vendor: NVIDIA Corporation
product: G96 Board - 06160001 Chip Rev
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

Revision history for this message
cutterjohn (moylanj) wrote :

Oh yes, the all important Ubuntu revision info
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 8.10
Release: 8.10
Codename: intrepid

uname -a:
Linux maximus 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux

I also have a failsafe Xorg log that I could upload as well, as it seems to report a bit more info than the normal X.org log. (I've been trying to find the right manual sync and refresh values to get correct modelines for other resolutions, but haven't had much luck yet only getting black screens although I can hear the normal Ubuntu startup sound so likely the timings are off.)

I'm sort of suspicious that it's either an nVidia driver bug or maybe a combo of nVidia driver bug plus new LCD panel and EDID implementation...

Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

Not nVidia-only, I have the same on an Intel-based laptop (FujitsuSiemens Lifebook S7110).

get-edid and ddcprobe fail, however everything works out of the box... I discovered this because xdpyinfo reports dpi and screen physical size incorrectly...

Bryce Harrington (bryce)
description: updated
Revision history for this message
Chris Wyatt (wyattmeister) wrote :

I recently bought a Technika Pro LCD22-408 and it isn't properly detected by Ubuntu, I ran a get-edid and got this:

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

Also there was stuff before this I think relating to my laptop's screen which is properly detected. Bad monitor? If anyone could tell me how to manually configure this monitor or it's refresh rates then I would be greatly obliged. It supports 1680 x 1050 but I can't use it which is a real shame :( .

Also, I'm using a GeForce 7200 MX and Ubuntu Intrepid. I've tried both nvidia-glx-177 and nvidia-glx-180.

Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

the version of read-edid included in ubuntu (1.4.1) is stale since 2001
a new maintainer has released 2.0.0 here: http://www.polypux.org/projects/read-edid/
and a request for packaging has been filed as bug #242043

Bryce Harrington (bryce)
Changed in xorg-server:
importance: High → Wishlist
Revision history for this message
artheon (r-j-m-jeurissen) wrote :

I had the same problem. EDID failed, so my computer could only start up in low graphics mode after telling me that there were not suitable modes. When I took out the vga switch (konig 4-port manual switch), the monitor was detected correctly. Apparently, the EDID wire is not connected in the switch. As a workaround, I now boot without the switch and connect the switch after booting. I never shut down. I only hibernate my computer. Updates that require a restart can be annoying this way, though. I hope this helps someone.

Revision history for this message
Chris Wyatt (wyattmeister) wrote :

My problem turned out to be similar, it was the cable which must've not been up to spec. I ended up buying a much higher quality cable which got rid of the noise problem and let me enjoy 1680x1050 for a while, until for some reason that resolution just decided to stop working :\ .

Definitely won't be going to any small Asian computer shops for a while, the previous Asian computer shop I went to installed a really cheap, crappy LCD screen in to my laptop, it just looked piss-poor, so I made them order an HP one :) , had to pay a bit more though.

Revision history for this message
nukedathlonman (areginato) wrote :

Another Edid failure. This is on a new Dell Vostro 1720 with nVidia 9600M GS video card with 1920x1200 Premium display and a fresh install of Kubuntu 9.04 "Jaunty" (also applies to Ubuntu). I can only access 1920x1200x24 bit video. Fine for daily use, but no good for gaming when a lower resolution is needed.

dccprobe:

vbe: VESA 3.0 detected.
oem: NVIDIA
vendor: NVIDIA Corporation
product: G96 Board - vostro21 Chip Rev
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

xrandr:

Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200
default connected 1920x1200+0+0 0mm x 0mm
   1920x1200 50.0*

xresprobe nvidia:

id:
res:
freq:
disptype: lcd/lvds

xorg.conf:

# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# Note that some configuration settings that could be done previously
# in this file, now are automatically configured by the server and settings
# here are ignored.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
 DefaultDepth 24
EndSection

Section "Module"
 Load "glx"
EndSection

Section "Device"
 Identifier "Configured Video Device"
 Driver "nvidia"
 Option "NoLogo" "True"
EndSection

Revision history for this message
nukedathlonman (areginato) wrote :

Sorry, nearly forgot the log file...

Revision history for this message
Ajay (ajay-g-m) wrote :

My machine details are as below. Any suggestions??? (Please note that I'm a novice in Linux world, so please give a little more detail in your instructions.

Thank You

**************************************************************************************************
user@desktop:~$ uname -a
Linux desktop 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:01:29 UTC 2009 i686 GNU/Linux
**************************************************************************************************
user@desktop:~$ sudo ddcprobe
[sudo] password for user:
vbe: VESA 3.0 detected.
oem: Brookdale-G Graphics Chip Accelerated VGA BIOS
vendor: Intel Corporation
product: Brookdale-G Graphics Controller Hardware Version 0.0
memory: 832kb
mode: 1280x1024x256
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x32k
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x64k
mode: 1280x1024x16m
mode: 132x25 (text)
mode: 132x43 (text)
mode: 132x50 (text)
mode: 132x60 (text)
mode: 640x480x256
mode: 800x600x256
mode: 1024x768x256
mode: 640x480x64k
edid:
edid: 1 1
id: 1058
eisa: SAM1058
serial: 44503137
manufacture: 2 2001
input: sync on green, analog signal.
screensize: 32 24
gamma: 2.260000
dpms: RGB, active off, suspend, standby
timing: 720x400@70 Hz (VGA 640x400, IBM)
timing: 720x400@88 Hz (XGA2)
timing: 640x480@60 Hz (VGA)
timing: 640x480@67 Hz (Mac II, Apple)
timing: 640x480@72 Hz (VESA)
timing: 640x480@75 Hz (VESA)
timing: 800x600@56 Hz (VESA)
timing: 800x600@60 Hz (VESA)
timing: 800x600@75 Hz (VESA)
timing: 832x624@75 Hz (Mac II)
timing: 1024x768@87 Hz Interlaced (8514A)
timing: 1024x768@60 Hz (VESA)
timing: 1024x768@70 Hz (VESA)
timing: 1024x768@75 Hz (VESA)
timing: 1280x1024@75 (VESA)
ctiming: 640x480@85
ctiming: 800x600@85
ctiming: 1024x768@85
ctiming: 1280x1024@60
dtiming: 800x600@85
dtiming: 1024x768@104
monitorrange: 30-70, 50-160
monitorserial: HMDR108008
**************************************************************************************************

Revision history for this message
Solanki (narendra-bhinmal) wrote :

My monitor is not showing resolution above than 800x600. Windows XP has correctly detected the supported resolutions. 1024x768 is the highest resolution supported by my monitor.

Manufacturer : Micron Electronics, Inc
Model no. : RM07R11

Revision history for this message
Solanki (narendra-bhinmal) wrote :
Revision history for this message
Solanki (narendra-bhinmal) wrote :

narendra@narendra-desktop:~$ sudo ddcprobe
vbe: VESA 2.0 detected.
oem: Intel810(TM) Graphics Chip Accelerated VGA BIOS
memory: 1024kb
memory: 4096kb
mode: 132x25 (text)
mode: 132x43 (text)
mode: 132x50 (text)
mode: 132x60 (text)
mode: 320x200x64k
mode: 640x400x256
mode: 640x480x256
mode: 640x480x32k
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x16
mode: 800x600x256
mode: 800x600x32k
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x256
edid:
edidfail

narendra@narendra-desktop:~$ sudo get-edid
get-edid: get-edid version 2.0.0

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
 Function supported
 Call successful

 VBE version 200
 VBE string at 0x2110 "Intel810(TM) 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 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

Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote :

Also problem with the EDID, Ubuntu believes the screen is 72" instead of 40".

Motherboard: GIGABYTE GA-H55M-UD2H H55 S-1156 M-ATX
Graphics (built-in): Intel H55
Monitor: Sony Bravia KDL-40W4000
Presumed modes:
    DisplaySize 884 495
    HorizSync 31.5 - 64.0
    VertRefresh 60.0 - 75.0

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION="Ubuntu lucid (development branch)"

$ uname -a
Linux htpc 2.6.34-020634rc3-generic #020634rc3 SMP Tue Apr 6 17:31:12 UTC 2010 x86_64 GNU/Linux

$ sudo ddcprobe
vbe: VESA 3.0 detected.
oem: Intel(R)Ironlake Desktop Graphics Chipset Accelerated VGA BIOS
vendor: Intel Corporation
product: Intel(R)Ironlake Desktop Graphics Controller Hardware Version 0.0
memory: 65472kb
mode: 1280x1024x256
mode: 1280x1024x64k
mode: 1280x1024x16m
mode: 1024x768x256
mode: 1024x768x64k
mode: 1024x768x16m
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 640x480x256
mode: 800x600x256
mode: 640x480x64k
edid:
edid: 1 3
id: 5c01
eisa: SNY5c01
serial: 01010101
manufacture: 1 2008
input: analog signal.
screensize: 160 90
gamma: 2.200000
dpms: RGB, no active off, no suspend, no standby
timing: 720x400@70 Hz (VGA 640x400, IBM)
timing: 640x480@75 Hz (VESA)
timing: 1024x768@87 Hz Interlaced (8514A)
ctiming: 1280x1024@60
dtiming: 1920x1080@67
dtiming: 1280x720@71
monitorname: SONY TV XV
monitorrange: 14-70, 48-62

$ gtf 1920 1200 60

  # 1920x1200 @ 60.00 Hz (GTF) hsync: 74.52 kHz; pclk: 193.16 MHz
  Modeline "1920x1200_60.00" 193.16 1920 2048 2256 2592 1200 1201 1204 1242 -HSync +Vsync

Revision history for this message
Tim Kornhammar (tim-kornhammar) wrote :

And the xorg log.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

If you have issues with a specific driver not getting the proper display mode, please file a bug against the driver. Some EDID fiascos can be fixed by an xserver quirk, but again please file new bugs. Closing this meta-bug.

Changed in xorg-server (Ubuntu):
status: Triaged → Invalid
Revision history for this message
Fred (eldmannen+launchpad) wrote :

I am using Nvidia proprietary device driver.
Maybe it doesn't get EDID because it doesn't support XRandR?

bugbot (bugbot)
tags: added: hardy
Revision history for this message
Mikael Nordfeldth (mmn) wrote :

lspci:
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
00:02.1 Display controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)

Using latest updates for 11.10 Oneiric Ocelot and xserver-xorg-video-intel, I get edidfail with `sudo ddcprobe` while connected via DVI.

What's curious in this case is that Intel has released an alternative driver for Windows systems which supposedly fixes the problem. I do not know if the problem is due to the same cause in Oneiric, as I don't have a Windows license to test with, but here is Intel's report on the issue:
http://www.intel.com/support/graphics/sb/CS-028366.htm

Here's my info according to the checklist:
1. AOC 416V (TK7SMUDBAWA1HN, Serial No. F1677JA000866). Picture of monitor label attached.

2. Xorg.0.log attached. In the end of it, I set 1920x1200 resolution manually with a command I copied straight off another 1920x1200 monitor:
xrandr --newmode "1920x1200" 193.16 1920 2048 2256 2592 1200 1201 1204 1242 -HSync +Vsync && xrandr --addmode DVI1 1920x1200 && xrandr -s 1920x1200

3. get-edid couldn't finish! This was the output:
get-edid: get-edid version 2.0.0

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
 Function supported
 Call successful

 VBE version 300
 VBE string at 0x11100 "Intel(r)Lakeport-G 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 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

4. Seems to be:
Horizontal 74.038 kHz
Vertical 59.95 Hz

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nvidia-graphics-drivers (Ubuntu):
status: New → Confirmed
penalvch (penalvch)
no longer affects: nvidia-graphics-drivers (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.