Activity log for bug #288807

Date Who What changed Old value New value Message
2008-10-24 16:53:39 Alexander Muon bug added bug
2008-10-24 16:53:39 Alexander Muon bug added attachment 'Xorg.0.log' (Xorg.0.log)
2008-11-02 00:11:56 Geir Ove Myhr description Binary package hint: xserver-xorg-video-intel ubuntu intrepid, limited to 800x600, 640x480, should have detected 1024x768 Binary package hint: xserver-xorg-video-intel ubuntu intrepid, limited to 800x600, 640x480, should have detected 1024x768 Update: X can't read DDC info from the monitor: (II) intel(0): VESA VBE DDC read failed
2008-11-04 19:03:59 Bryce Harrington title intel 82815 screen resolution not detected [i815] screen resolution not detected
2008-11-04 19:05:27 Bryce Harrington xserver-xorg-video-intel: status New Incomplete
2008-11-04 19:05:27 Bryce Harrington xserver-xorg-video-intel: statusexplanation Thank you for including your Xorg.0.log. Please also attach the following: * Output from `lspci -vvnn` * Output from `xrandr --verbose` * Output from `get-edid | parse-edid` (you'll need the read-edid package for this)
2008-11-08 21:22:40 no2nonFree bug added attachment 'i8xx-resolution-bug-report' (i8xx-resolution-bug-report)
2008-11-10 15:58:53 Alexander Muon bug added attachment 'lspci' (lspci -vvnn)
2008-11-10 15:59:48 Alexander Muon bug added attachment 'xrandr' (xrandr --verbose)
2008-11-10 16:00:48 Alexander Muon bug added attachment 'get-edid' (get-edid | parse-edid)
2008-11-27 07:53:28 jaypmcwilliams bug added attachment 'guidance-backends_0.8.0svn20080103-0ubuntu16_i386.deb' (guidance-backends_0.8.0svn20080103-0ubuntu16_i386.deb)
2008-11-27 07:54:32 jaypmcwilliams bug added attachment 'displayconfig-gtk_0.3.10_all.deb' (displayconfig-gtk_0.3.10_all.deb)
2008-12-02 22:11:58 Bryce Harrington xserver-xorg-video-intel: status Incomplete Confirmed
2008-12-02 22:11:58 Bryce Harrington xserver-xorg-video-intel: statusexplanation Thank you for including your Xorg.0.log. Please also attach the following: * Output from `lspci -vvnn` * Output from `xrandr --verbose` * Output from `get-edid | parse-edid` (you'll need the read-edid package for this)
2009-01-07 02:44:56 Bryce Harrington description Binary package hint: xserver-xorg-video-intel ubuntu intrepid, limited to 800x600, 640x480, should have detected 1024x768 Update: X can't read DDC info from the monitor: (II) intel(0): VESA VBE DDC read failed [Problem] Resolutions are incorrect on the Vaio PCG-SRX51 because its display does not support DDC, and thus is not properly communicating its horizontal and vertical sync rate capabilities to the driver. [Discussion] Prior to Hardy, xorg.conf's required having the HorizSync and VertRefresh settings explicitly specified in the xorg.conf; Hardy's xserver gained the capability to detect these settings from the monitor itself using DDC reads, and thus the installation scripts were modified to not list these two pieces of data. However, the Vaio PCG-SRX51 does not correctly communicate these values, so users started seeing problems in Hardy. This can be seen in Xorg.0.log files from the following error: (II) intel(0): VESA VBE DDC read failed The HorizSync and VertRefresh values are employed in the calculation of valid modelines (i.e. resolutions), so a consequence of this problem is that users were not able to load all the resolutions that the hardware is capable of doing. (Bad sync rates can cause other glitches, but the resolution issue is the most noticeable problem). The Xorg.0.log shows a stream of "Not using default mode ..." and falling all the way down to an 800x600 resolution. An example set of files from experiencing this behavior are seen here: http://launchpadlibrarian.net/19497368/i8xx-resolution-bug-report Running get-edid | parse-edid indicates that the hardware doesn't support DDC at all: Monitor and video card combination does not support DDC1 transfers Monitor and video card combination does not support DDC2 transfers [Proposed Solution] Unfortunately since neither DDC nor EDID works, that poses a considerable constraint for automatic detection. However, perhaps it could be quirked based on both the hostbridge and video chip: 00:00.0 Host bridge [0600]: Intel Corporation 82815 815 Chipset Host Bridge and Memory Controller Hub [8086:1130] (rev 02) 00:02.0 VGA compatible controller [0300]: Intel Corporation 82815 Chipset Graphics Controller (CGC) [8086:1132] (rev 02) Subsystem: Compaq Computer Corporation Device [0e11:001a] Unfortunately neither -intel nor the xserver has infrastructure in place for synthetically setting DDC info this way. It may be worthwhile establishing an infrastructure if there is additional hardware that needs to be similarly quirked. One approach could be to introduce a check in i810_driver.c in I810DoDDC() of the return from vbeDoEDID; if it is NULL, then if the PCI's match the above, generate a synthetic MonInfo structure with appropriate h/v sync values and so on. This approach would also let us hardcode the vendor and twiddle other monitor details. Alternatively, a possibly simpler approach could be to modify the handling of undefined h/v sync rates inside xf86ValidateModes() in the xserver. Instead of just defaulting to 31.5-37.9 / 50-70, it could do a check of the chip and hostbridge, and if it matches a quirked one, use that for the h/v sync rates. This approach would have the advantage of being usable across all drivers. [Workaround] Make your xorg.conf look like this: Section "Device" Identifier "Configured Video Device" Driver "intel" EndSection Section "Monitor" Identifier "Configured Monitor" HorizSync 31.5-48.5 VertRefresh 40-70 Option "dpms" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" Device "Configured Video Device" DefaultDepth 16 Option "Accel" SubSection "Display" Depth 16 Modes "1024x768" EndSubSection SubSection "Display" Depth 24 Modes "1024x768" EndSubSection EndSection this is thanks denvergeek on the Ubuntu forums: http://ubuntuforums.org/showthread.php?t=972062&highlight=8.10+ibex+screen+resolution&page=2 [lspci] 00:02.0 VGA compatible controller [0300]: Intel Corporation 82815 Chipset Graphics Controller (CGC) [8086:1132] (rev 11) Subsystem: Sony Corporation Device [104d:80df] [Original Report] ubuntu intrepid, limited to 800x600, 640x480, should have detected 1024x768 Update: X can't read DDC info from the monitor: (II) intel(0): VESA VBE DDC read failed
2009-01-07 02:44:56 Bryce Harrington title [i815] screen resolution not detected [i815] Wrong resolution on Vaio PCG-SRX51 due to incorrect h/v rates
2009-01-07 02:47:46 Bryce Harrington xserver-xorg-video-intel: status Confirmed Triaged
2009-01-07 02:47:46 Bryce Harrington xserver-xorg-video-intel: importance Undecided High
2009-01-07 02:53:28 Bryce Harrington title [i815] Wrong resolution on Vaio PCG-SRX51 due to incorrect h/v rates [i815] Wrong resolution on Vaio PCG-SRX51, PCG-SRX41 and PCG-FX370 due to incorrect h/v rates
2009-01-07 02:55:33 Bryce Harrington description [Problem] Resolutions are incorrect on the Vaio PCG-SRX51 because its display does not support DDC, and thus is not properly communicating its horizontal and vertical sync rate capabilities to the driver. [Discussion] Prior to Hardy, xorg.conf's required having the HorizSync and VertRefresh settings explicitly specified in the xorg.conf; Hardy's xserver gained the capability to detect these settings from the monitor itself using DDC reads, and thus the installation scripts were modified to not list these two pieces of data. However, the Vaio PCG-SRX51 does not correctly communicate these values, so users started seeing problems in Hardy. This can be seen in Xorg.0.log files from the following error: (II) intel(0): VESA VBE DDC read failed The HorizSync and VertRefresh values are employed in the calculation of valid modelines (i.e. resolutions), so a consequence of this problem is that users were not able to load all the resolutions that the hardware is capable of doing. (Bad sync rates can cause other glitches, but the resolution issue is the most noticeable problem). The Xorg.0.log shows a stream of "Not using default mode ..." and falling all the way down to an 800x600 resolution. An example set of files from experiencing this behavior are seen here: http://launchpadlibrarian.net/19497368/i8xx-resolution-bug-report Running get-edid | parse-edid indicates that the hardware doesn't support DDC at all: Monitor and video card combination does not support DDC1 transfers Monitor and video card combination does not support DDC2 transfers [Proposed Solution] Unfortunately since neither DDC nor EDID works, that poses a considerable constraint for automatic detection. However, perhaps it could be quirked based on both the hostbridge and video chip: 00:00.0 Host bridge [0600]: Intel Corporation 82815 815 Chipset Host Bridge and Memory Controller Hub [8086:1130] (rev 02) 00:02.0 VGA compatible controller [0300]: Intel Corporation 82815 Chipset Graphics Controller (CGC) [8086:1132] (rev 02) Subsystem: Compaq Computer Corporation Device [0e11:001a] Unfortunately neither -intel nor the xserver has infrastructure in place for synthetically setting DDC info this way. It may be worthwhile establishing an infrastructure if there is additional hardware that needs to be similarly quirked. One approach could be to introduce a check in i810_driver.c in I810DoDDC() of the return from vbeDoEDID; if it is NULL, then if the PCI's match the above, generate a synthetic MonInfo structure with appropriate h/v sync values and so on. This approach would also let us hardcode the vendor and twiddle other monitor details. Alternatively, a possibly simpler approach could be to modify the handling of undefined h/v sync rates inside xf86ValidateModes() in the xserver. Instead of just defaulting to 31.5-37.9 / 50-70, it could do a check of the chip and hostbridge, and if it matches a quirked one, use that for the h/v sync rates. This approach would have the advantage of being usable across all drivers. [Workaround] Make your xorg.conf look like this: Section "Device" Identifier "Configured Video Device" Driver "intel" EndSection Section "Monitor" Identifier "Configured Monitor" HorizSync 31.5-48.5 VertRefresh 40-70 Option "dpms" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" Device "Configured Video Device" DefaultDepth 16 Option "Accel" SubSection "Display" Depth 16 Modes "1024x768" EndSubSection SubSection "Display" Depth 24 Modes "1024x768" EndSubSection EndSection this is thanks denvergeek on the Ubuntu forums: http://ubuntuforums.org/showthread.php?t=972062&highlight=8.10+ibex+screen+resolution&page=2 [lspci] 00:02.0 VGA compatible controller [0300]: Intel Corporation 82815 Chipset Graphics Controller (CGC) [8086:1132] (rev 11) Subsystem: Sony Corporation Device [104d:80df] [Original Report] ubuntu intrepid, limited to 800x600, 640x480, should have detected 1024x768 Update: X can't read DDC info from the monitor: (II) intel(0): VESA VBE DDC read failed [Problem] Resolutions are incorrect on several Sony Vaio laptops because their display panels do not support DDC, and thus is not properly communicating its horizontal and vertical sync rate capabilities to the driver. [Discussion] Prior to Hardy, xorg.conf's required having the HorizSync and VertRefresh settings explicitly specified in the xorg.conf; Hardy's xserver gained the capability to detect these settings from the monitor itself using DDC reads, and thus the installation scripts were modified to not list these two pieces of data. However, the Vaio PCG-SRX51 does not correctly communicate these values, so users started seeing problems in Hardy. This can be seen in Xorg.0.log files from the following error: (II) intel(0): VESA VBE DDC read failed The HorizSync and VertRefresh values are employed in the calculation of valid modelines (i.e. resolutions), so a consequence of this problem is that users were not able to load all the resolutions that the hardware is capable of doing. (Bad sync rates can cause other glitches, but the resolution issue is the most noticeable problem). The Xorg.0.log shows a stream of "Not using default mode ..." and falling all the way down to an 800x600 resolution. An example set of files from experiencing this behavior are seen here: http://launchpadlibrarian.net/19497368/i8xx-resolution-bug-report Running get-edid | parse-edid indicates that the hardware doesn't support DDC at all: Monitor and video card combination does not support DDC1 transfers Monitor and video card combination does not support DDC2 transfers [Proposed Solution] Unfortunately since neither DDC nor EDID works, that poses a considerable constraint for automatic detection. However, perhaps it could be quirked based on both the hostbridge and video chip: 00:00.0 Host bridge [0600]: Intel Corporation 82815 815 Chipset Host Bridge and Memory Controller Hub [8086:1130] (rev 02) 00:02.0 VGA compatible controller [0300]: Intel Corporation 82815 Chipset Graphics Controller (CGC) [8086:1132] (rev 02) Subsystem: Compaq Computer Corporation Device [0e11:001a] Unfortunately neither -intel nor the xserver has infrastructure in place for synthetically setting DDC info this way. It may be worthwhile establishing an infrastructure if there is additional hardware that needs to be similarly quirked. One approach could be to introduce a check in i810_driver.c in I810DoDDC() of the return from vbeDoEDID; if it is NULL, then if the PCI's match the above, generate a synthetic MonInfo structure with appropriate h/v sync values and so on. This approach would also let us hardcode the vendor and twiddle other monitor details. Alternatively, a possibly simpler approach could be to modify the handling of undefined h/v sync rates inside xf86ValidateModes() in the xserver. Instead of just defaulting to 31.5-37.9 / 50-70, it could do a check of the chip and hostbridge, and if it matches a quirked one, use that for the h/v sync rates. This approach would have the advantage of being usable across all drivers. [Workaround] Make your xorg.conf look like this: Section "Device" Identifier "Configured Video Device" Driver "intel" EndSection Section "Monitor" Identifier "Configured Monitor" HorizSync 31.5-48.5 VertRefresh 40-70 Option "dpms" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" Device "Configured Video Device" DefaultDepth 16 Option "Accel" SubSection "Display" Depth 16 Modes "1024x768" EndSubSection SubSection "Display" Depth 24 Modes "1024x768" EndSubSection EndSection this is thanks denvergeek on the Ubuntu forums: http://ubuntuforums.org/showthread.php?t=972062&highlight=8.10+ibex+screen+resolution&page=2 [lspci] 00:02.0 VGA compatible controller [0300]: Intel Corporation 82815 Chipset Graphics Controller (CGC) [8086:1132] (rev 11) Subsystem: Sony Corporation Device [104d:80df] [Original Report] ubuntu intrepid, limited to 800x600, 640x480, should have detected 1024x768 Update: X can't read DDC info from the monitor: (II) intel(0): VESA VBE DDC read failed
2009-03-05 02:48:58 Bryce Harrington xserver-xorg-video-intel: importance High Wishlist
2010-02-17 15:55:13 Jeremy Foshee bug task added linux (Ubuntu)
2010-02-17 15:55:26 Jeremy Foshee linux (Ubuntu): status New Incomplete
2010-02-17 15:55:34 Jeremy Foshee xserver-xorg-video-intel (Ubuntu): status Triaged Invalid
2010-02-17 15:55:42 Jeremy Foshee linux (Ubuntu): importance Undecided Wishlist
2010-02-18 15:56:34 TJ attachment added Lucid Xubuntu LiveCD (2010-02-17) desktop photo http://launchpadlibrarian.net/39367680/xubuntu-lucid-x86-livecd-srx51.png
2010-03-05 10:54:14 TJ attachment added Lucid Ubuntu LiveCD (2010-03-04) desktop photo http://launchpadlibrarian.net/40238151/ubuntu-lucid-x86-livecd-srx51.jpg
2010-03-05 11:08:49 TJ attachment added Lucid Ubuntu LiveCD (2010-03-04) Xorg/kern/xsession log files http://launchpadlibrarian.net/40239998/SRX51-lucid-bug288807.tar.gz
2010-03-05 18:31:50 Joel Goguen removed subscriber Joel Goguen
2010-06-14 22:31:24 Jeremy Foshee tags edid i815 intel resolution xorg edid i815 intel kj-expired resolution xorg
2010-06-14 22:31:33 Jeremy Foshee linux (Ubuntu): status Incomplete Expired
2011-10-05 22:09:19 Jeremy Foshee removed subscriber Jeremy Foshee