Thanks for taking a look.
Regarding PRAM and Modelines:
You were right. I did not reset PRAM, but confirmed that changing geometry settings in OSX changed my display in Linux. Since I'm dual booting OSX 10.4, I will adjust there first and then "tweak" modelines until I get there. Sidenote: stumbled on "apt-get install videogen" and find it a lot more useful than cvt for this purpose.
Regarding AGP vs. PCIMode:
A major cocern for me is the ability to use system RAM, and I may have confirmed AGPSize gets ignored when ForcePCIMode is used. My thinking that RAM is relatively cheap and easy for these machines. VideoRAM - not gonna happen. Could be really useful on the ones with 4 or 6 MB of VRAM.
If I add Option "AGPSize" "32" to the xorg.conf in the first post, this is the major difference I was hoping to fix more so than just FPS.
This is from 3.2.0-23 (Lubuntu) but is the same as 3.2.0-26
Code:
PCIMode
[ 930.139] (II) R128(0): Using 8 MB AGP aperture
[ 930.140] (II) R128(0): Using 1 MB for the ring buffer
[ 930.140] (II) R128(0): Using 2 MB for vertex/indirect buffers
[ 930.140] (II) R128(0): Using 1 MB for AGP textures
Code:
AGP Mode (and unusable due to CCEtimeouts)
[ 34.422] (II) R128(0): Using 32 MB AGP aperture
[ 34.422] (II) R128(0): Using 1 MB for the ring buffer
[ 34.422] (II) R128(0): Using 2 MB for vertex/indirect buffers
[ 34.422] (II) R128(0): Using 29 MB for AGP textures
Putting uninorth_agp in modules didn't change things. drm.debug didn't yield anything obvious to me.
I still think the significant error is
Code:
aty128fb 0000:00:10.0: putting AGP V2 device into 0x mode
Agreed, and I don't understand this either:
Code:
dmesg | grep -i vga
[ 0.047384] vgaarb: loaded
[ 32.545041] vgaarb: this pci device is not a vga device
[ 33.354151] vgaarb: this pci device is not a vga device
[ 33.964274] agpgart: Couldn't find an AGP VGA controller.
I still will try the kernel compile to see if it yields more performance. But, if it does force PCI mode, then we still lose use of system RAM. (I think.)
I realize DRI for R128 is no longer officially supported, but would a bug report be warranted? Even if a user isn't downgrading mesa, the initial install appears as "hung" system since DRI is enabled by default.
The attached has detailed logs with and without PCIMode in 3.2.0-23 if anyone wants to take a closer look.
Thanks
Bookmarks