public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alex Schuster <wonko@wonkology.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: ATI X trouble, again
Date: Sat, 24 Oct 2009 08:26:03 +0200	[thread overview]
Message-ID: <200910240826.09061.wonko@wonkology.org> (raw)
In-Reply-To: <5bdc1c8b0910231512l61f3a82g27f2cc59219fbb83@mail.gmail.com>

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: 0x003f0000 is: 0xffffffc0
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  : 0x003f0000
(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  : 0xffffffc0
freq: 135000000
best_freq: 135000000
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  : 0x003f0000
(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



      reply	other threads:[~2009-10-24  6:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-23 12:15 [gentoo-user] ATI X trouble, again Alex Schuster
2009-10-23 13:46 ` Mark Knecht
2009-10-23 14:09   ` Alex Schuster
2009-10-23 14:20     ` Mark Knecht
2009-10-23 13:59 ` Jesús Guerrero
2009-10-23 15:33 ` [gentoo-user] " Nikos Chantziaras
2009-10-23 15:47   ` Alex Schuster
2009-10-23 16:12     ` Nikos Chantziaras
2009-10-23 19:45       ` Alex Schuster
2009-10-23 16:17     ` Jesús Guerrero
2009-10-23 21:05       ` Alex Schuster
2009-10-23 22:12         ` Mark Knecht
2009-10-24  6:26           ` Alex Schuster [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200910240826.09061.wonko@wonkology.org \
    --to=wonko@wonkology.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox