DRI not working due to problem with AGP

Hi there.

I have a strange issue with my Radeon 9600 - direct rendering doesn't
work anymore (ok, perhaps not that strange ...)
If someone could help me I'd be grateful forever.

I had it up and running (with direct rendering) a few days ago, after
tampering with ati-drivers unsuccessfully for months I gave DRI a shot
and it worked immediately after I rewrote my xorg.conf. Yet yesterday I
noticed that direct rendering was off again.

rohanda tomboy # uname -a
Linux rohanda 2.6.17-gentoo-r8 #11 PREEMPT Wed Nov 22 05:37:20 UTC 2006
x86_64 AMD Athlon(tm) 64 Processor 2800+ AuthenticAMD GNU/Linux

===
it's the very same with kernel 2.6.18-r2
x11-drm is from 2006-06-08
and i use a ati radeon 9600 AQ, RV350-chip
===

rohanda tomboy # dmesg | grep agp
agpgart: Detected AGP bridge 0
agpgart: Aperture conflicts with PCI mapping.
agpgart: Aperture from AGP @ fc000000 size 4096 MB
agpgart: Aperture too small (0 MB)
agpgart: No usable aperture found.
agpgart: Consider rebooting with iommu=memaper=2 to get a good aperture.
Linux agpgart interface v0.101 (c) Dave Jones

===
iommu=memaper=2 I added in my grub.conf and reinstalled - doesn't change
anything.
additionally i have the possibility of altering the agp-aperture-size in
my bios between 32MB and 512 - none of these values changes anything.
===

rohanda tomboy # grep /var/log/Xorg.0.log -e WW -e EE
Current Operating System: Linux rohanda 2.6.17-gentoo-r8 #11 PREEMPT Wed
Nov 22 05:37:20 UTC 2006 x86_64
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) Loading extension MIT-SCREEN-SAVER
(WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found
(WW) RADEON(0): Failed to detect secondary monitor, MergedFB/Clone mode
disabled
(WW) RADEON(0): config file hsync range 28-96kHz not within DDC hsync
ranges.
(WW) (1280x960,Monitor0) mode clock 148.5MHz exceeds DDC maximum 140MHz
(WW) (1280x1024,Monitor0) mode clock 157.5MHz exceeds DDC maximum 140MHz
(WW) (1600x1200,Monitor0) mode clock 162MHz exceeds DDC maximum 140MHz
(WW) (1600x1200,Monitor0) mode clock 175.5MHz exceeds DDC maximum 140MHz
(WW) (1600x1200,Monitor0) mode clock 189MHz exceeds DDC maximum 140MHz
(WW) (1600x1200,Monitor0) mode clock 202.5MHz exceeds DDC maximum 140MHz
(WW) (1600x1200,Monitor0) mode clock 229.5MHz exceeds DDC maximum 140MHz
(WW) (1792x1344,Monitor0) mode clock 204.8MHz exceeds DDC maximum 140MHz
(WW) (1792x1344,Monitor0) mode clock 261MHz exceeds DDC maximum 140MHz
(WW) (1856x1392,Monitor0) mode clock 218.3MHz exceeds DDC maximum 140MHz
(WW) (1856x1392,Monitor0) mode clock 288MHz exceeds DDC maximum 140MHz
(WW) (1920x1440,Monitor0) mode clock 234MHz exceeds DDC maximum 140MHz
(WW) (1920x1440,Monitor0) mode clock 297MHz exceeds DDC maximum 140MHz
(WW) (1400x1050,Monitor0) mode clock 155.8MHz exceeds DDC maximum 140MHz
(WW) (1920x1440,Monitor0) mode clock 341.35MHz exceeds DDC maximum 140MHz
(WW) (2048x1536,Monitor0) mode clock 266.95MHz exceeds DDC maximum 140MHz
(WW) (2048x1536,Monitor0) mode clock 340.48MHz exceeds DDC maximum 140MHz
(WW) (2048x1536,Monitor0) mode clock 388.04MHz exceeds DDC maximum 140MHz
(WW) RADEON(0): [agp] AGP not available
(EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI.
(WW) RADEON(0): Direct rendering disabled
(EE) AIGLX: Screen 0 is not DRI capable
(WW) Couldn't load XKB keymap, falling back to pre-XKB keymap

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--