Forwarding this bug from Ubuntu reporter Anna S.: http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/473114 [Problem] Iiyama monitor's native resolution does not display properly. [Original Description] After upgrading to Karmic Koala (9.10), my iiyama ProLite E2407HDS monitor does not display properly at its native resolution of 1920x1080 (16:9). It is auto-detected correctly, but at native res, the screen is black besides the toolbars, and some apps display when run, but others do not - for instance Firefox is entirely blank. The display is only usable at the lower 16:9 resolution of 1280x720. (Background and apps all display properly in this lower res.) When scrolling through all possible resolutions, the majority of the resolutions tested did not display properly. I also checked this page: https://wiki.ubuntu.com/X/Troubleshooting/Resolution and was unable to solve the problem. In particular, adding kernel parameter modeset=0 did not do anything, so I cannot say whether Karmic is missing a quirk for this monitor or not. The display worked fine at its native res (1920x1080) in Jaunty Jackalope. Architecture: amd64 CheckboxSubmission: 3f1404c1e7a16070779964e4cd978722 CheckboxSystem: edda5d4f616ca792bf437989cb597002 Date: Tue Nov 3 19:16:38 2009 DistroRelease: Ubuntu 9.10 Lsusb: Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 0bda:0151 Realtek Semiconductor Corp. Mass Stroage Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTek Computer Inc. K8N-E Package: xorg 1:7.4+3ubuntu7 ProcCmdLine: root=UUID=0f3ca1ef-146b-4fee-ac00-15d710e99dd4 ro quiet splash modeset=0 ProcEnviron: LANG=en_US.UTF-8ProcVersionSignature: Ubuntu 2.6.31-14.48-generic RelatedPackageVersions: xserver-xorg 1:7.4+3ubuntu7 libgl1-mesa-glx 7.6.0-1ubuntu4 libdrm2 2.4.14-1ubuntu1 xserver-xorg-video-intel 2:2.9.0-1ubuntu2 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1 SourcePackage: xorg Uname: Linux 2.6.31-14-generic x86_64 dmi.bios.date: 06/27/2005 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1001.013 dmi.board.name: K8N-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1001.013:bd06/27/2005:svnASUSTekComputerInc.:pnK8N-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnK8N-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: K8N-E dmi.product.version: System Version dmi.sys.vendor: ASUSTek Computer Inc. system: architecture: x86_64kernel: 2.6.31-14-generic
Created attachment 30948 [details] BootDmesg.txt
Created attachment 30949 [details] CurrentDmesg.txt
Created attachment 30950 [details] XorgLog.txt
Created attachment 30951 [details] Xrandr.txt
If your driver has 66b194a78c470cb3978f310828dd96c3f3e96944, make sure to pull in 2a6eeec72d6bb04a32225883f431c1d2e8cff123 as well. If not, can you attach a working log from the older driver?
(In reply to comment #5) > If your driver has 66b194a78c470cb3978f310828dd96c3f3e96944, make sure to pull > in 2a6eeec72d6bb04a32225883f431c1d2e8cff123 as well. Nevermind this is only relevant for atom cards and this one is not atom-based.
Does: Option "DisplayPriority" "HIGH" in the device section of your config file help?
It reminds me on bug #24074 and bug #24406 which I'm seeing also on r200 hardware. I think it's worth to try turning off the 3d desktop effects (compiz) to check whether it's the same problem or not.
Well I checked the ubuntu bug and sure enough, in the comments: "- Changed Visual Effects to "None." My background and icons appeared!" Which means it's a duplicate of one of those two bugs.
The reporter in the ubuntu bug agreed that this is likely a duplicate, marking the bug as duplicate. *** This bug has been marked as a duplicate of bug 24406 ***
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.