| Summary: | [Radeon 9250] Blank screen when GDM starts unless NoDRI option used. | ||
|---|---|---|---|
| Product: | xorg | Reporter: | Bryce Harrington <bryce> |
| Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> |
| Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> |
| Severity: | normal | ||
| Priority: | high | CC: | sanfton-0801 |
| Version: | 7.3 (2007.09) | Keywords: | NEEDINFO |
| Hardware: | Other | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | |||
Created attachment 22395 [details]
radeontool output (failure)
Created attachment 22396 [details]
radeontool output (success)
Created attachment 22397 [details]
xorg.conf from failure case
Created attachment 22398 [details]
xorg.conf from working case
This is forwarded from the following Ubuntu report, btw: https://bugs.launchpad.net/bugs/293698 Please also attach the full Xorg.0.log for both cases (or at the very least a diff between them) and set the MIME type to text/plain. Also, whenever the log file appears truncated, the X server's stderr output needs to be examined for possible more information. With a display manager it should be captured in the display manager's log file. Does setting the AGPMode option help? Add the following to the device section of your config: Option "AGPMode" "x" where x = 1 or 2 or 4 or 8. Try and find what AGP mode works. If none of the AGP modes help, try: Option "BusType" "PCI" (In reply to comment #7) > Does setting the AGPMode option help? Add the following to the device section > of your config: > > Option "AGPMode" "x" > where x = 1 or 2 or 4 or 8. > > Try and find what AGP mode works. If none of the AGP modes help, try: > Option "BusType" "PCI" > I have almost exact same bug. the interesting thing about AGPmode is that the driver sets this to AGP8x by default. I think earlier drivers set AGP1x for safety. If I set AGP2x, the driver responds (in xorg.0.log) something like: "illegal mode. AGP8x and 4x only allowed". Using AGP4x crashes the same as 8x. setting Option "BusType" "PCI" works fine, including the KDE4.1 compositing effects. But, in this mode the PC seems a lot slower, notably the "bouncing K" of the KDE hourglass, window repaints etc. But hours of uptime show no crashes. I will run the radeontool when I am back at my kubuntu PC later and post logs. (In reply to comment #6) > Please also attach the full Xorg.0.log for both cases (or at the very least a > diff between them) and set the MIME type to text/plain. > > Also, whenever the log file appears truncated, the X server's stderr output > needs to be examined for possible more information. With a display manager it > should be captured in the display manager's log file. > (In reply to comment #6) > Please also attach the full Xorg.0.log for both cases (or at the very least a > diff between them) and set the MIME type to text/plain. > > Also, whenever the log file appears truncated, the X server's stderr output > needs to be examined for possible more information. With a display manager it > should be captured in the display manager's log file. > Created attachment 22468 [details]
Xorg.og for failure case (AGP)
Created attachment 22469 [details]
Xorg.log for Working case (BusType PCI)
Created attachment 22470 [details]
xorg.conf for working case (uncomment AGPMode line for Failure case)
Created attachment 22471 [details]
lspci -vnn output from PC under test
struggling with jaunty radeontool in Kubuntu Intrepid. binary seems not to work, no success with source yet (only 4 weeks into Linux experience!) tipps for compiling from git appreciated.
I don't see anything but two copies of comment #6 in comment #9, did you mean to add anything there? The log file from the failure case does look truncated, please check the X server stderr output. Created attachment 22476 [details]
stdout, stderr from startx (recovery root prompt)
output from staring recovery mode, root prompt, startx > /data/all 2>&1
I wanted to say in the previous posts, that my Xorg.0.log always stops at the same place (just after textured video is set up). It does not matter which AGPMode is selected, or if AGPFastWrite is yes or no.
with BusType PCI, no problems except slightly slow PC, and occasional scrambled windows when first opened (previews or K menus)
(In reply to comment #15) > output from staring recovery mode, root prompt, startx > /data/all 2>&1 > > I wanted to say in the previous posts, that my Xorg.0.log always stops at the > same place (just after textured video is set up). It does not matter which > AGPMode is selected, or if AGPFastWrite is yes or no. There's no additional information in there... when the problem occurs, can you still ping the machine? Log in remotely? (In reply to comment #16) > (In reply to comment #15) > > output from staring recovery mode, root prompt, startx > /data/all 2>&1 > > > > I wanted to say in the previous posts, that my Xorg.0.log always stops at the > > same place (just after textured video is set up). It does not matter which > > AGPMode is selected, or if AGPFastWrite is yes or no. > > There's no additional information in there... when the problem occurs, can you > still ping the machine? Log in remotely? > The power button turns OFF the PC, but nothing else (key presses or CTRL-SH-BACKSP) seems to cause any action at all from the HDD-light. in fact, when X starts the screen gives 'no signal' and no more HDD light after that. I have another PC with Kubuntu Intrepid here. will that do for remote login? I have not done remote access before though. Created attachment 22491 [details]
X errors from var/log/kdm.log See end of the file.
Found something in this one. I imagine this is the KDE log - and it reports some X errors right at the end of the file. This file was copied during a root prompt session, right after starting X in the faulty condition, and entering the login password blindly. Then, I gave it CTRL-Sh-BACKSP...
Is this still an issue with xf86-video-ati from git master? (In reply to comment #19) > Is this still an issue with xf86-video-ati from git master? > With Kubuntu Karmic, this one appears to be fixed. My hardware is exactly unchanged, as described below. The Live CD works without having to choose VESA graphics mode, and the system works reliably with a fresh install. Actually I upgraded from Intrepid, which worked fine for a couple of days, them blew up spectacularly! The occasional scrambled video output (eg when a menu first pops up) which was present in Intrepid, is also fixed. Only thing is, the compositing refuses to engage. I think I am happier with 9.10 overall though! Unless the compositing is a related issue, I would call this one resolved. |
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.
[Problem] Blank screen during X boot on Ati Radeon 9250. Goes away if option NoDRI used. [Original Report] I've a problem using Ati Radeon 9250 on Ubuntu 8.04 with open source driver: very often, after splash screen monitor shows me "no signal" message and it goes to standby mode. I checked Xorg.0.log when xserver starts correctly and when it doesn't and I've seen two differences: 1) Some memory area (Ring, GART, Vertex buffers,etc...) are mapped to different addresses 2) When "no signal" message is shown log ends with (II) RADEON(0): no multimedia table present, disabling Rage Theatre. while when X starts without problems the log continues. I attach Xorg.0.log in both cases: working and bugged, and my xorg.conf. I found a way to use my system simply putting option NoDRI in xorg.conf: no signal message doesn't appear anymore but system is slower and desktop effects don't work. Best Regards, Simone Navari. [lspci] 00:00.0 Host bridge [0600]: VIA Technologies, Inc. K8T800Pro Host Bridge [1106:0282] Subsystem: ASUSTeK Computer Inc. A8V Deluxe [1043:80a3] 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV280 [Radeon 9200 PRO] [1002:5960] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Unknown device [1458:4054]