© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
May I tell you about my own issue? It's not the Tecra 8000. The Tecra 8000 issue is a pleasant problem-solving exercise compared to this:
X.Org wrongly detects the screen resolutions available on my monitor. I have an ATI Radeon X1900 XT connected to a ViewSonic VG2230wm monitor. It's a widescreen flat panel; the native resolution is 1680x1050. Ubuntu has to use the vesa driver. When I install Ubuntu or start the LiveCD environment (or do sudo dpkg-reconfigure -phigh xserver-xorg), it puts this stuff in /etc/X11/xorg.conf:
Section "Screen"
Identifier "Default Screen"
Device "Generic Video Card"
Monitor "VG2230wm"
SubSection "Display"
EndSection
Now wait, did I just say the native resolution was 1680x1050? I sure did. So why are there mode lines like "1680x1680", "1600x1200", and "1440x1440" in here? I have no clue! But the graphical environment refuses to start up, even in "safe graphics" mode. I have to manually edit xorg.conf so that it looks like this:
Section "Screen"
Identifier "Default Screen"
Device "Generic Video Card"
Monitor "VG2230wm"
SubSection "Display"
EndSection
Then it works. It's a good thing I knew how to use Ctrl-Alt-F1 to reach a command console, use "sudo vim" to edit xorg.conf, and find the correct place in the file. A non-technical user might figure that out...if he was really, really, really desperate.
There is no bullet-proof X on Kubuntu. When I tried regular Ubuntu or Xubuntu, bullet-proof X didn't help at all. I could select a screen mode in a dialog box, but my settings seemed to have no effect.
I believe the problem is that the vesa driver goofs up parsing the monitor's EDID data. Right now, I use the radeonhd driver, built from the latest Git tree. It works perfectly fine for me. It's awesome. The attached Xorg.0.log contains all the monitor information detected by the radeonhd driver.
Unfortunately, this problem still exists in Gutsy Gibbon. I have to edit xorg.conf, even if I start the LiveCD in "safe graphics mode". Since the release of Feisty Fawn last year, I've reported this issue a few times in different places, including the Ubuntu Forums, the Ubuntu mailing lists, and the X.Org mailing list. I must say, it's like talking to a brick wall. I literally get no responses.
Doesn't anyone want to investigate? Or at least help me investigate? If you write a message telling me to shut up, I'll be happy. It means someone read my message.