** Description changed: + 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 your video card's PCI ID (i.e., 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. + + + [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/[EMAIL PROTECTED]:0 [EMAIL PROTECTED] � � 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
-- EDID fail https://bugs.launchpad.net/bugs/194760 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
