xorg fails to start i Hardy with ATI X1400

Bug #192107 reported by Trond Thorbjørnsen
4
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: xorg

I've tried both upgrade and the install cd.

I have to manually install xorg-driver-fglrx to get X to work, and then
I have to use the old xorg.conf from my gutsy with an extra line:
Option "MetaModes" "1280x800"

Neighter
$ sudo aticonfig --initial -f
or the originial xorg.conf works.

ProblemType: Bug
Architecture: i386
Date: Fri Feb 15 13:16:55 2008
DistroRelease: Ubuntu 8.04
NonfreeKernelModules: fglrx
Package: xserver-xorg 1:7.3+10ubuntu4
PackageArchitecture: all
SourcePackage: xorg
Uname: Linux huey 2.6.24-5-generic #1 SMP Thu Jan 24 19:45:21 UTC 2008 i686 GNU/Linux

Tags: apport-bug
Revision history for this message
Trond Thorbjørnsen (tthorb) wrote :
Revision history for this message
A. Meschede (ameschede-freenet) wrote :

i can confirm this bug for 3 different notebooks using an ATI x1xx graphics adapter.

in gutsy, i could run the live cd without problems. it used the vesa driver in a 1024x768 resolution. after installation i could then switch to the properitary fglrx driver with 3D and 12800x800.

now in all of the hardy alphas, ubuntu shows the bootup sequence, and when it tries to start the x server, the display goes black and nothing happens. when i switch to another terminal and type "startx" to start the server manually, it gives me this error:

"(EE) VESA(0): No valid modes
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found.
giving up."

This, i think, is a major issue, since it seems to affect most of the standard Centrino (Duo)-Notebooks with an ATI X1300, X1400 and X1600 adapter. many users won't be able to use the live cd and install ubuntu because of this.

Since i would love to tryout and test the hardy alpha, is there anything i can do for a workaround on notebooks with an ATI adapter?

Thanks for your help

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

This bug is a duplicate of bug 174434, so you should check that bug for more information..

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.