Created attachment 33285 [details] Xorg.0.log Originally reported at: https://bugs.launchpad.net/bugs/520925 [Problem] Monitor supports 1152x864, but this resolution is not available through xrandr. Not sure if this is due to bad EDID (so it would need an EDID quirk) or if the driver is interpreting it wrong. [Original report] My monitor samtron 56v supports 1152*864 but I cant set that resolution In display preferences ... ( system -> preferences -? Display preference ) It shows as unknown monitor I can get 1024*768 resolution In windows XP I can have 1152*864 i have intel 810 motherboard and intel 82810E display Ubuntu 9.10 (now I have updated to pre release of 10.04) Xorg.0.log shows: (II) intel(0): Not using driver mode "1152x864" (mode clock too high) --- Architecture: i386 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: xserver-xorg-video-intel 2:2.10.0+git20100120.93cd943d-0ubuntu0sarvatt PackageArchitecture: i386 ProcEnviron: LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: xserver-xorg 1:7.5+1ubuntu1 libgl1-mesa-glx 7.8.0~git20100121.4736e1cb-0ubuntu0sarvatt libdrm2 2.4.17+git20100120.9de34e2d-0ubuntu0sarvatt2 xserver-xorg-video-intel 2:2.10.0+git20100120.93cd943d-0ubuntu0sarvatt xserver-xorg-video-ati 1:6.12.99+git20100120.30a19b75-0ubuntu0sarvatt Tags: lucid Uname: Linux 2.6.33-020633rc5-generic i686 UnreportableReason: This is not a genuine Ubuntu package UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare system: distro: Ubuntu architecture: i686kernel: 2.6.33-020633rc5-generic
Created attachment 33286 [details] dmesg output
Created attachment 33287 [details] xrandr --verbose
Created attachment 33288 [details] lspci -vvnn
Can you manually create a working modeline using xrandr for the 1152x864 mode? Yakui, can you take a look? Maybe we just need another hsync quirk or something for this mode.
(In reply to comment #4) > Can you manually create a working modeline using xrandr for the 1152x864 mode? > > Yakui, can you take a look? Maybe we just need another hsync quirk or > something for this mode. This is actually an xserver bug. KMS rounds up the pixel clock limit based on all modes found in EDID; X only does so for detailed timings.
Is this still an issue?
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please file a new report if you continue to experience issues with a current server.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.