Bug 17956 - black screen at logon screen on 1st boot after install [RV610 / HD 2400 PRO]
Summary: black screen at logon screen on 1st boot after install [RV610 / HD 2400 PRO]
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.4 (2008.09)
Hardware: All Linux (All)
: high major
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL: https://bugs.edge.launchpad.net/ubunt...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-07 13:49 UTC by Bryce Harrington
Modified: 2011-05-18 06:15 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
logfile (36.75 KB, patch)
2008-10-07 13:49 UTC, Bryce Harrington
no flags Details | Splinter Review
xorg log file (44.59 KB, patch)
2008-11-09 06:29 UTC, Nick Griffiths
no flags Details | Splinter Review
Output from radeontool on Jaunty (broken) (17.79 KB, text/plain)
2009-04-29 12:25 UTC, Gerald Preissler
no flags Details
On Jaunty (broken) using radeon driver (17.79 KB, text/plain)
2009-04-29 12:26 UTC, Gerald Preissler
no flags Details
Output from radeontool on Hardy (working) (17.86 KB, text/plain)
2009-04-29 12:26 UTC, Gerald Preissler
no flags Details
Output of lspci -vvnn (19.92 KB, text/plain)
2009-04-29 12:27 UTC, Gerald Preissler
no flags Details
output from avivotool on 8.10 (working) (182.32 KB, text/plain)
2009-05-02 01:13 UTC, Gerald Preissler
no flags Details
output from avivotool on 9.04 (broken) (181.93 KB, text/plain)
2009-05-02 01:23 UTC, Gerald Preissler
no flags Details

Description Bryce Harrington 2008-10-07 13:49:56 UTC
Created attachment 19457 [details] [review]
logfile

Forwarding this bug from a ubuntu user:
https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/273510

Problem:
On boot in Ubuntu, after usplash X goes to a black screen.  The login sounds can be heard, and login info is accepted, so X hasn't locked up.  Disabling compiz made no difference.

I can't tell for sure from the log file, but it sounds like it's maybe mapping the outputs incorrectly?

lspci:
04:00.0 VGA compatible controller: ATI Technologies Inc RV610 video device [Radeon HD 2400 PRO]
Comment 1 Nick Griffiths 2008-11-09 06:29:25 UTC
Created attachment 20165 [details] [review]
xorg log file

Here's my xorg log file - getting the same result of two black screens, with gdm still working in the background.
Comment 2 Nick Griffiths 2008-11-09 06:32:36 UTC
my lspci:
01:00.0 VGA compatible controller: ATI Technologies Inc RV610 video device [Radeon HD 2400 PRO]
Comment 3 Bryce Harrington 2009-02-18 13:32:52 UTC
Another reporter with this same graphics hardware and identical symptoms has provided avivotool dumps for the good and bad states:

http://launchpadlibrarian.net/21879965/avivotool_bad.txt
http://launchpadlibrarian.net/21880006/avivotool_good.txt
Comment 4 Alex Deucher 2009-02-18 14:35:05 UTC
Does this still happen with 6.11.0 or git master?
Comment 5 Gerald Preissler 2009-04-29 12:23:44 UTC
This happens to me with Kubuntu 9.04 - here is a cut & paste from my original error report at https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/273510 . I will add the related as well.
---original report---
I'm having this problem with a fresh install of Kubuntu Jaunty, using either the radeon or the fglrx driver.
 Hardware:
- Asus M2A-VM motherboard
 - Sapphire Radeon HD 4670 graphics card installed
 - DELL E248 WFP LCD display (24'', 1920 x 1200 native)
Hardy works fine on the machine, when I install Jaunty into a separate partition I'm running into problems.
The symptoms are the same as describe above:
- When trying to start from the standard CD, the screen turns to black after the boot screen disappears. The display goes into powersafe eventually
 - Installing from the alternate CD works fine. When trying to boot the installed system, the screen turns black again when the KDM screen ought to appear. I can switch to the console via ctrl-alt-F1 when using the radeon driver, but not when using fglrx. Looking through Xorg.0.log I can't find anything that points to a problem.
I've run radeontool both on the Jaunty install and on the working Hardy install (using the radeontool version from the Jaunty install in both cases). I'll upload the resulting reports, Xorg.0.log and the result of lspci as run on the Hardy install.
If I can provide any additional information, please tell me what you need. This problem is a blocker for me, and I appreciate any help I can get.
Comment 6 Gerald Preissler 2009-04-29 12:25:36 UTC
Created attachment 25263 [details]
Output from radeontool on Jaunty (broken)
Comment 7 Gerald Preissler 2009-04-29 12:26:16 UTC
Created attachment 25264 [details]
On Jaunty (broken) using radeon driver
Comment 8 Gerald Preissler 2009-04-29 12:26:50 UTC
Created attachment 25265 [details]
Output from radeontool on Hardy (working)
Comment 9 Gerald Preissler 2009-04-29 12:27:22 UTC
Created attachment 25266 [details]
Output of lspci -vvnn
Comment 10 Alex Deucher 2009-04-29 12:28:09 UTC
Please make sure the fglrx kernel module has not been previously loaded when you start the open source driver.  Also, you'll need avivotool rather than radeontool for your card as the display hardware is different.
Comment 11 Gerald Preissler 2009-05-02 01:10:58 UTC
Thanks for looking into that. I ran avivotool on kubuntu 8.10 (working) and 9.04 (broken), using the version from 9.04 both times. 9.04 was a fresh install, fglrx was not installed, no related modules showed up in lsmod.
Comment 12 Gerald Preissler 2009-05-02 01:13:35 UTC
Created attachment 25363 [details]
output from avivotool on 8.10 (working)
Comment 13 Gerald Preissler 2009-05-02 01:23:01 UTC
Created attachment 25364 [details]
output from avivotool on 9.04 (broken)
Comment 14 Gerald Preissler 2009-05-07 13:39:40 UTC
I've worked around the problem by installing the fglrx driver. If I can be of any help with tracking down the problem with the radeon driver on my particular hardware please contact me.
Comment 15 Alex Deucher 2009-10-21 13:43:22 UTC
Is this still an issue with ati from git master?
Comment 16 Alex Deucher 2010-10-19 16:44:57 UTC
closing due to lack of feedback.
Comment 17 Timo Aaltonen 2011-05-18 06:15:41 UTC
closing harder :)


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.