Cannot get normal graphical session running after install
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-video-ati (Ubuntu) |
Invalid
|
High
|
Unassigned |
Bug Description
I cannot get the Hardy Beta graphical session running on an HP Compaq Presario SR1620NX (Sempron 2GHz, 512MB RAM, 160GB HDD) with ATI Radeon Xpress 200G Series integrated video.
The installation works fine, but then I cannot log on. When I enter my username and password, it attempts to switch to the desktop, but ends up putting me right back into the login screen. The same thing happens when attempting to run the live CD. This leads to the upper part of the screen showing color variations and just bleeding away the top of the login screen.
I previous reported bug #145670 on Gutsy - that was fixed by the release date. I can run the released version of Gutsy 7.10 fine on the problematical HP Compaq Presario SR1620NX.
I have installed Ubuntu 8.04 beta on several other machines without any problems - including an eMachines T4010 and a Dell Inspiron 700m.
Thanks for any help you can offer.
description: | updated |
description: | updated |
Changed in xserver-xorg-video-ati: | |
status: | Incomplete → New |
status: | New → Incomplete |
Hi Brian,
Looks like this bug was filed against Ubuntu rather than against Xorg, so I didn't notice it until today; sorry about the delay in response, I've corrected the package.
The problem you're describing is X crashing on the main X session, but works properly with the gdm-controlled X login session. This generally means that the driver basically works with your hardware, but there is a configuration issue on this particular hardware. Please attach your /etc/X11/xorg.conf and /var/log/Xorg.0.log files for me to take a look at.
It looks like the PCI ID for an ATI Radeon Xpress 200G is 1002:5954. Can you confirm this (it can be found in lspci -vvnn). Looking in the driver source there are some code paths unique to this hardware for features it does not support, which could explain why you've seeing a crash on it while other systems work properly. With the Xorg.0.log in hand hopefully there will be an error message and/or a backtrace that indicates what the issue is.