Re: [gentoo-user] Re: ATI X trouble, again
Mark Knecht writes: BTW - EVERY problem I was having when I dealt with this sort of thing a couple of months ago was visible in some sense in the Xorg.0.log files. I would look for errors, figure out what was causing them, mostly being config issues in my case, and then fix them and try again. It really paid to sort of dig into that file and try to look closely at every warning message along with the more obvious error (EE) messages. There are only two (EE) errors about input devices, because I have them configured manually. The warnings: (WW) RADEON(0): DRI init changed memory map, adjusting ... (WW) RADEON(0): MC_FB_LOCATION was: 0xefffe000 is: 0xefffe000 (WW) RADEON(0): MC_AGP_LOCATION was: 0x003f is: 0xffc0 No idea what this is. (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) Probably harmless, I have this on my desktop system, too. That's it. Then I have some blank/disable messages I do not understand at the bottom. On my desktop system, where I at least got some unaccelerated X output with the radeon driver, I have some of them, but fewer. Output CRT1 disable success Blank CRTC 0 success Disable CRTC 0 success Blank CRTC 1 success Disable CRTC 1 success (II) RADEON(0): RADEONRestoreMemMapRegisters() : (II) RADEON(0): MC_FB_LOCATION : 0xefffe000 0xefffe000 (II) RADEON(0): MC_AGP_LOCATION : 0x003f (II) RADEON(0): avivo_restore ! Enable CRTC 1 success Unblank CRTC 1 success Enable CRTC 0 success Unblank CRTC 0 success (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) (II) No APM support in BIOS or kernel (II) AIGLX: Resuming AIGLX clients after VT switch Output CRT1 disable success Output CRT2 disable success Blank CRTC 0 success Disable CRTC 0 success Blank CRTC 1 success Disable CRTC 1 success Output CRT1 disable success Blank CRTC 0 success Disable CRTC 0 success Mode 1280x1024 - 1688 1066 5 (II) RADEON(0): RADEONRestoreMemMapRegisters() : (II) RADEON(0): MC_FB_LOCATION : 0xefffe000 0xefffe000 (II) RADEON(0): MC_AGP_LOCATION : 0xffc0 freq: 13500 best_freq: 13500 best_feedback_div: 50 best_ref_div: 2 best_post_div: 5 (II) RADEON(0): crtc(0) Clock: mode 135000, PLL 135000 (II) RADEON(0): crtc(0) PLL : refdiv 2, fbdiv 0x32(50), pdiv 5 Set CRTC 0 PLL success Set CRTC Timing success Set CRTC 0 Overscan success Not using RMX scaler 0 setup success Set CRTC 0 Source success crtc 0 YUV disable setup success Output DAC1 setup success Output CRT1 enable success Enable CRTC 0 success Unblank CRTC 0 success Output CRT2 disable success Blank CRTC 1 success Disable CRTC 1 success (II) RADEON(0): [RESUME] Attempting to re-init Radeon hardware. (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) AIGLX: Suspending AIGLX clients for VT switch Output CRT1 disable success Blank CRTC 0 success Disable CRTC 0 success Blank CRTC 1 success Disable CRTC 1 success (II) RADEON(0): RADEONRestoreMemMapRegisters() : (II) RADEON(0): MC_FB_LOCATION : 0xefffe000 0xefffe000 (II) RADEON(0): MC_AGP_LOCATION : 0x003f (II) RADEON(0): avivo_restore ! Enable CRTC 1 success Unblank CRTC 1 success Enable CRTC 0 success Unblank CRTC 0 success (II) UnloadModule: mouse (II) UnloadModule: kbd (II) RADEON(0): [drm] removed 1 reserved context for kernel (II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0x1efff000 at 0x7fe96dacf000 (II) RADEON(0): [drm] Closed DRM master. I also got help on the same ATI list you were pointed out. Very helpful folks. Thanks, I will go there. Wonko
[gentoo-user] Re: ATI X trouble, again
On 10/23/2009 03:15 PM, Alex Schuster wrote: I did not try ati-drivers. Her card is a RV505 (Radeon X1550 Series) which is no longer supported by current ati-drivers. Older drivers might still work for a while, but only with kernels 2.6.29. And I suspect the problem is not the driver itself, because radeon does not work, too, and I also had similar problems of a blank screen with an ATI card and different drivers. For the radeon X driver (which *is* the best choice for the X1000 series) make sure you also have radeon in-kernel support enabled.
Re: [gentoo-user] Re: ATI X trouble, again
Nikos Chantziaras writes: On 10/23/2009 03:15 PM, Alex Schuster wrote: I did not try ati-drivers. Her card is a RV505 (Radeon X1550 Series) which is no longer supported by current ati-drivers. Older drivers might still work for a while, but only with kernels 2.6.29. And I suspect the problem is not the driver itself, because radeon does not work, too, and I also had similar problems of a blank screen with an ATI card and different drivers. For the radeon X driver (which *is* the best choice for the X1000 series) make sure you also have radeon in-kernel support enabled. It is enabled, and according do dmesg, it is running fine: [ 387.433698] [drm] Initialized drm 1.1.0 20060810 [ 387.535673] [drm] Initialized radeon 1.30.0 20080528 for :02:00.0 on minor 0 But that's only for GLX, right? So even if it weren't enabled, I should see something, I guess. Wonko
[gentoo-user] Re: ATI X trouble, again
On 10/23/2009 06:47 PM, Alex Schuster wrote: Nikos Chantziaras writes: On 10/23/2009 03:15 PM, Alex Schuster wrote: I did not try ati-drivers. Her card is a RV505 (Radeon X1550 Series) which is no longer supported by current ati-drivers. Older drivers might still work for a while, but only with kernels 2.6.29. And I suspect the problem is not the driver itself, because radeon does not work, too, and I also had similar problems of a blank screen with an ATI card and different drivers. For the radeon X driver (which *is* the best choice for the X1000 series) make sure you also have radeon in-kernel support enabled. It is enabled, and according do dmesg, it is running fine: [ 387.433698] [drm] Initialized drm 1.1.0 20060810 [ 387.535673] [drm] Initialized radeon 1.30.0 20080528 for :02:00.0 on minor 0 But that's only for GLX, right? So even if it weren't enabled, I should see something, I guess. Can you post /var/log/Xorg.0.log on http://pastebin.ca ?
Re: [gentoo-user] Re: ATI X trouble, again
On Fri, 23 Oct 2009 17:47:44 +0200, Alex Schuster wo...@wonkology.org wrote: Nikos Chantziaras writes: On 10/23/2009 03:15 PM, Alex Schuster wrote: I did not try ati-drivers. Her card is a RV505 (Radeon X1550 Series) which is no longer supported by current ati-drivers. Older drivers might still work for a while, but only with kernels 2.6.29. And I suspect the problem is not the driver itself, because radeon does not work, too, and I also had similar problems of a blank screen with an ATI card and different drivers. For the radeon X driver (which *is* the best choice for the X1000 series) make sure you also have radeon in-kernel support enabled. It is enabled, and according do dmesg, it is running fine: [ 387.433698] [drm] Initialized drm 1.1.0 20060810 [ 387.535673] [drm] Initialized radeon 1.30.0 20080528 for :02:00.0 on minor 0 But that's only for GLX, right? So even if it weren't enabled, I should see something, I guess. Yes. What kind of blank is it? Do you see the mouse pointer at least? Do the monitor(s) stay on or do they go into standby mode? I've had issues with radeon in the past, and after asking in the mailing list it seemed like some issue with my AGP card. Some developer suggested to try this in the xorg.conf file and it worked for me: Option BusType PCIE And yes, it's an AGP card. The logic behind this is out of my understanding. You can see the thread here: http://article.gmane.org/gmane.comp.freedesktop.xorg.drivers.ati/10628/match=i92guboj If you have problems with the radeon (not fglrx or radeonhd) driver, I suggest posting to that list. It's probably the best place to get help if the standard procedures do not work. -- Jesús Guerrero
Re: [gentoo-user] Re: ATI X trouble, again
Nikos Chantziaras writes: Can you post /var/log/Xorg.0.log on http://pastebin.ca ? Config file and logs are already here: http://wonkology.org/~wonko/tmp/tanja/ Wonko
Re: [gentoo-user] Re: ATI X trouble, again
Jesús Guerrero writes: On Fri, 23 Oct 2009 17:47:44 +0200, Alex Schuster wo...@wonkology.org wrote: What kind of blank is it? Do you see the mouse pointer at least? Do the monitor(s) stay on or do they go into standby mode? The monitors complain about bad frequencies. The TFT then enters standby mode, the CRT continues trying to show something, but I only see the frequency out of range message. I've had issues with radeon in the past, and after asking in the mailing list it seemed like some issue with my AGP card. Some developer suggested to try this in the xorg.conf file and it worked for me: Option BusType PCIE And yes, it's an AGP card. The logic behind this is out of my understanding. You can see the thread here: http://article.gmane.org/gmane.comp.freedesktop.xorg.drivers.ati/10628/ma tch=i92guboj Tried that, but it did not help. If you have problems with the radeon (not fglrx or radeonhd) driver, I suggest posting to that list. It's probably the best place to get help if the standard procedures do not work. Thanks! I will do that. Wonko
Re: [gentoo-user] Re: ATI X trouble, again
On Fri, Oct 23, 2009 at 2:05 PM, Alex Schuster wo...@wonkology.org wrote: Jesús Guerrero writes: On Fri, 23 Oct 2009 17:47:44 +0200, Alex Schuster wo...@wonkology.org wrote: What kind of blank is it? Do you see the mouse pointer at least? Do the monitor(s) stay on or do they go into standby mode? The monitors complain about bad frequencies. The TFT then enters standby mode, the CRT continues trying to show something, but I only see the frequency out of range message. I've had issues with radeon in the past, and after asking in the mailing list it seemed like some issue with my AGP card. Some developer suggested to try this in the xorg.conf file and it worked for me: Option BusType PCIE And yes, it's an AGP card. The logic behind this is out of my understanding. You can see the thread here: http://article.gmane.org/gmane.comp.freedesktop.xorg.drivers.ati/10628/ma tch=i92guboj Tried that, but it did not help. If you have problems with the radeon (not fglrx or radeonhd) driver, I suggest posting to that list. It's probably the best place to get help if the standard procedures do not work. Thanks! I will do that. Wonko BTW - EVERY problem I was having when I dealt with this sort of thing a couple of months ago was visible in some sense in the Xorg.0.log files. I would look for errors, figure out what was causing them, mostly being config issues in my case, and then fix them and try again. It really paid to sort of dig into that file and try to look closely at every warning message along with the more obvious error (EE) messages. I also got help on the same ATI list you were pointed out. Very helpful folks. Good luck, Mark
