Iiyama monitor's native 1920x1080 does not work properly (Karmic Koala)

[Anna S.]

Binary package hint: x11-xserver-utils

After upgrading to Karmic Koala (9.10), my iiyama ProLite E2407HDS monitor does not display properly at its native resolution of 1920x1080 (16:9). No background is displayed - the screen is black besides the toolbars, even when trying to change background image/color. 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.)

When running a system test that scrolled through all possible resolutions, the majority of the resolutions tested did not display properly.

The display worked fine at its native res (1920x1080) in Jaunty Jackalope.

ProblemType: Bug
Architecture: amd64
CheckboxCommand: xrandr_cycle
CheckboxDescription:
 Click Test to cycle through the detected video modes for your system.

 Did the screen appear to be working for each mode?
CheckboxTest: xrandr_cycle
Date: Sat Oct 31 13:28: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: x11-xserver-utils 7.4+2ubuntu3
ProcCmdLine: root=UUID=0f3ca1ef-146b-4fee-ac00-15d710e99dd4 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: 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: x11-xserver-utils
Tags: checkbox-bug
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.
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: x86_64kernel: 2.6.31-14-generic

[Bryce Harrington (bryce)]

Thank you for seeking to improve Ubuntu. It seems you have filed a bug
against X using the new System Testing utility. Unfortunately, this tool
is filing bugs without collecting sufficient information to properly
diagnose the issues. I wish we could reply to every report to guide you
to gather the correct information, but it happens that so many people
are using this testing feature to file bug reports that we simply cannot
keep up with the influx. I'm replying in bulk so I can get everyone
pointed into a direction most likely to result in getting you a useful
workaround and us a complete bug report that can be solved.

Most of these problems describe issues that have documented
troubleshooting procedures, so perhaps the most helpful thing I can
do is point you to them:

  http://wiki.ubuntu.com/X/Troubleshooting

These guides explain why things break the way they do, and in some cases
provide workarounds.

I would ask that you first go through the appropriate guide for your
problem, particularly if you are having problems with resolution,
crashes, fonts, or blank screen issues, and then file a bug report using
the following command:

   ubuntu-bug xorg

This collects more detailed information than the System Testing tool
does. Please also write a detailed explanation, indicating when you
first discovered the problem, analysis steps you've done, workarounds
that work, and so on.

Or, if you suspect the problem has something to do with the way the test
script itself is working (such as if Ubuntu worked fine until you ran
the script), then file the bug against the test suite:

   ubuntu-bug checkbox

Thanks again, and good luck!