if I remember correctly it was when I executed fglxconfig... it asked me towards the end of the configuration if I wanted to use ATI's aperture or the kernels.

If you'd like when I get home tonight I'll post my XF86config.

i would appreciate that too, when i run it, I only get one AGPGART option, not the choice between the kernel's or ATI's

I have to drive the GF into pittsburgh tonight... I probably won't be home till around 11 pm / midnight... so I'll post it but it'll be posted late. I'll also post any other type of information I can find about it... (just in case the option to not use kernel agpgart is not in XFconfig).


P.S. Martinman... have you gotten any further with setting yours up?

Awsome, I will check back around midnight or so. Maybe I will be able to get things working, whoohoo!

erm...nope. Details in an IRC sometime, just i'm goin out all friday and i have a party on saturday/sunday and a memorial day parade im in (band nerds REJOICE!) on monday...

ok, here's my XF86Config-4 file... check out the ATI device section as that is probably where most are running into problems.

I hope its commented well enough... but if not please ask any questions you'd like. Good night, and I hope this helps.

Sincerely,
jpbarto

# File: XF86Config-4
# File generated by fglrxconfig (C) ATI Research, a substitute for xf86config.

# begin /etc/X11/XF86Config-4
# created by fglrxconfig; commented heavily by Jason Barto
#
# this section sets the permissions for DRM...
# this setup (mode 0666) allows all users to use DRM
# **********************************************************************
# DRI Section
# **********************************************************************
Section "dri"
# Access to OpenGL ICD is allowed for all users:
Mode 0666
EndSection

# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

Load "dbe" # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection

# This loads the Type1 and FreeType font modules
Load "type1"
Load "freetype"

# This loads the GLX module
Load "glx" # libglx.a
Load "dri" # libdri.a

EndSection

# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
# this section is nothing special to ATI... it just tells XFree86 where
# to find things like fonts.
Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"

FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
EndSection
# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"
# not passing any serverflags

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

Identifier "Keyboard1"
Driver "Keyboard"

Option "AutoRepeat" "500 30"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver
# this defines a three button mouse with scroll wheel
# specifically in my case a Logitech Trackball (or marble man)
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ImPS/2"
Option "Buttons" "5"
Option "ZAxisMapping" "4 5"
# the resolution option causes acceleration of the pointer
Option "Resolution" "256"
Option "Device" "/dev/mouse"

EndSection
# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"
Identifier "Monitor0"
HorizSync 31.5 - 80.5
VertRefresh 60 - 85
Option "DPMS"

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"

# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.

# Chipset "generic"

# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# installed.

# BusID "PCI:0:10:0"

# VideoRam 256

# Clocks 25.2 28.3

EndSection

# === ATI device section ===
# ok... here's the part you've all been waiting for

Section "Device"
Identifier "ATI Graphics Adapter"
# use our ATI fancy newly built fglrx drivers
Driver "fglrx"
# === disable/enable XAA/DRI ===
# these two options are probably a little redundant... but hey
# it couldn't hurt right?
Option "no_accel" "no"
Option "no_dri" "no"
# === FireGL DDX driver module specific settings ===
# === Screen Management ===
Option "DesktopSetup" "0x00000000"
Option "MonitorLayout" "AUTO, AUTO"
Option "IgnoreEDID" "off"
Option "HSync2" "unspecified"
Option "VRefresh2" "unspecified"
Option "ScreenOverlap" "0"
Option "GammaCorrectionI" "0x00000000"
Option "GammaCorrectionII" "0x00000000"
# === OpenGL specific profiles/settings ===
Option "Capabilities" "0x00000000"
# === Video Overlay for the Xv extension ===
Option "VideoOverlay" "on"
# === OpenGL Overlay ===
# Note: When OpenGL Overlay is enabled, Video Overlay
# will be disabled automatically
Option "OpenGLOverlay" "off"
# === Misc Options ===
Option "UseFastTLS" "0"
Option "BlockSignalsOnLock" "on"
# this next option tells the driver to use ATI's AGPGART
# you will want to use ATIs agpgart module _IF_ you have
# something like say a KT400 or P4X400 chipset that
# provides an 8x AGP port. 8x AGP is not currently
# supported in the 2.4.x series kernel agpgart module.
# thus you need to use ATIs.
Option "UseInternalAGPGART" "yes"
Option "ForceGenericCPU" "no"
# this busID can get messed up sometimes by the fglrxconfig
# script. To give you an idea... this reads as
# PCI:1:0:0 because when I type 'cat /proc/pci'
# it tells me
# Bus 1, device 0, function 0:
# VGA compatible controller: PCI device 1002:4e44 (ATI Technologies Inc) (rev 0).
# IRQ 10.
# Master Capable. Latency=255. Min Gnt=8.
# Prefetchable 32 bit memory at 0xd8000000 [0xdfffffff].
# I/O at 0x9000 [0x90ff].
# Non-prefetchable 32 bit memory at 0xe9000000 [0xe900ffff].
# Bus 1, device 0, function 1:
# Display controller: PCI device 1002:4e64 (ATI Technologies Inc) (rev 0).
# Master Capable. Latency=32. Min Gnt=8.
# Prefetchable 32 bit memory at 0xe0000000 [0xe7ffffff].
# Non-prefetchable 32 bit memory at 0xe9010000 [0xe901ffff].
#
# take note of the first device on Bus 1, device 0, function 0
# ie PCI:1:0:0... if you get errors during startup check to make sure
# that your config points to the right device...
# I think (but I'm not sure) that the second device is the digital vid out
BusID "PCI:1:0:0" # vendor=1002, device=4e44
Screen 0
EndSection
# **********************************************************************
# Screen sections
# **********************************************************************

Section "Screen"
Identifier "Screen0"
Device "ATI Graphics Adapter"
Monitor "Monitor0"
DefaultDepth 24
#Option "backingstore"

Subsection "Display"
Depth 24
Modes "1280x1024" "1280x960" "1024x768" "800x600"
ViewPort 0 0 # initial origin if mode is smaller than desktop
EndSubsection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
Identifier "Server Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.

Screen "Screen0"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"

EndSection

# end /etc/X11/XF86Config-4

Sorry to butt in here but this discussion has just become all about my own problem as well. I hope no one minds. It's completely on topic.

I have a mobo with an AGP8x chipset (SiS655) and a Radeon 9700 Pro. I'm running Slackware 9.0 and using the default kernel. I have successfully built and installed the latest ATI drivers for XF86 4.3.0 (finally). The external agpgart is compiled as a module but I'm not using it and it's not loaded. As suggested I have told fglrx that I want to use the internal agpgart module. This should put me on equal footing with everyone else here I hope. I've made a thread about it here:

http://www.linuxquestions.org/questi...threadid=60119

To summarise, cat proc/pci shows me the following:

==============================================
Bus 1, device 0, function 0:
___ VGA compatible controller: PCI device 1002:4e44 (ATI Technologies Inc) (rev 0).
____ IRQ 10.
____ Master Capable. Latency=255. Min Gnt=8.
____ Prefetchable 32 bit memory at 0xe0000000 [0xe7ffffff].
____ I/O at 0xc000 [0xc0ff].
____ Non-prefetchable 32 bit memory at 0xf5000000 [0xf500ffff].
Bus 1, device 0, function 1:
___ Display controller: PCI device 1002:4e64 (ATI Technologies Inc) (rev 0).
____ Master Capable. Latency=32. Min Gnt=8.
____ Prefetchable 32 bit memory at 0xe8000000 [0xefffffff].
____ Non-prefetchable 32 bit memory at 0xf5010000 [0xf501ffff].
==============================================

The ATI device section of my XF86Config-4 file is as follows:

# === ATI device section ===

Section "Device"
____ Identifier "ATI Graphics Adapter"
____ Driver "fglrx"
# === disable PnP Monitor ===
#Option "NoDDC"
# === disable/enable XAA/DRI ===
____ Option "no_accel" "no"
____ Option "no_dri" "no"
# === FireGL DDX driver module specific settings ===
# === Screen Management ===
____ Option "DesktopSetup" "0x00000000"
____ Option "MonitorLayout" "AUTO, AUTO"
____ Option "IgnoreEDID" "off"
____ Option "HSync2" "unspecified"
____ Option "VRefresh2" "unspecified"
____ Option "ScreenOverlap" "0"
____ Option "GammaCorrectionI" "0x00000000"
____ Option "GammaCorrectionII" "0x00000000"
# === OpenGL specific profiles/settings ===
____ Option "Capabilities" "0x00000800"
# === Video Overlay for the Xv extension ===
____ Option "VideoOverlay" "on"
# === OpenGL Overlay ===
# Note: When OpenGL Overlay is enabled, Video Overlay
# will be disabled automatically
____ Option "OpenGLOverlay" "off"
# === Misc Options ===
____ Option "UseFastTLS" "0"
____ Option "BlockSignalsOnLock" "on"
____ Option "UseInternalAGPGART" "yes"
____ Option "ForceGenericCPU" "no"
____ BusID "PCI:1:0:0" # vendor=1002, device=4e44
____ Screen 0
EndSection

When I startx I still get this:

(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:0) found
(EE) No devices detected.

Fatal server error:
no screens found

For some completely bizarre reason I can't post my Xfree86.0.log (well I can, but the bizarre part is that it isn't the same). What I mean is this. When I use the configuration above which gives me the message above, what I find in XFree86.0.log doesn't match. What the contents of XFree86.0.log DOES match in that particular circumstance is an error message I see when I use to same configuration above but have my AGP bus set to 4x in my BIOS instead of AUTO (which runs it at 8x). Xfree86.0.log does get updated however, because if I mess around with XF86Config-4 enough to produce a different error, that's what I'll see in there. I would have liked to have not had to explain that mindbending scenario but I don't want to leave it out in case it is somehow relevant :/

Anyway, here's what XFree86.0.log DOES contain. But remember, the message above is what I actually see in the console.

http://members.iinet.net.au/~cainn/XFree86.0.log (The same output I see when setting my AGP bus to 4x which in that case DOES agree with what I see on the console)

If you feel it's ok to ignore all that bullshit, then please do

what does your kernel log say? there should be some output in there about fglrx detecting your agp and so forth. I'll post what is output in my /var/log/messages when I get home.

when I modprobe the fglrx module here is what appears in /var/log/messages

May 23 12:48:06 metatron kernel: [fglrx] Maximum main memory to use for locked dma buffers: 926 MBytes.
May 23 12:48:06 metatron kernel: [fglrx] module loaded - fglrx 2.9.8 [Apr 15 2003] on minor 0

after xwindows starts and the ATI agpgart module is engaged this is also added to my /var/log/messages...
May 23 12:50:13 metatron kernel: [fglrx] AGP detected, AgpState = 0x1f000a0b (hardware caps of chipset)
May 23 12:50:13 metatron kernel: [fglrx] AGP enabled, AgpCommand = 0x1f000302 (selected caps)
May 23 12:50:13 metatron kernel: [fglrx] free AGP = 121909248
May 23 12:50:13 metatron kernel: [fglrx] max AGP = 121909248
May 23 12:50:13 metatron kernel: [fglrx] free LFB = 116391936
May 23 12:50:13 metatron kernel: [fglrx] max LFB = 116391936
May 23 12:50:13 metatron kernel: [fglrx] free Inv = 0
May 23 12:50:13 metatron kernel: [fglrx] max Inv = 0
May 23 12:50:13 metatron kernel: [fglrx] total Inv = 0
May 23 12:50:13 metatron kernel: [fglrx] total TIM = 0

Before I do anything else I may have to shoot myself.

Do I still have to have the external agpgart module loaded even though I have specified the use of the internal agpgart module that comes with the drivers? I disabled it thinking that it wasn't a good idea to have both running at the same time.

The only reason I ask is that I tried loading the external agpgart module with agp_try_unsupported=1 and then tried to start x. It worked.

I know the external module gives me no joy by itself but I was under the impression that it was a matter of one or another. I'll post some more info soon because although I'm in X now courtesy of the ATI drivers things aren't as good as they should be.

May 24 07:48:45 darkstar kernel: [fglrx] Maximum main memory to use for locked dma buffers: 803 MBytes.
May 24 07:48:45 darkstar kernel: [fglrx] module loaded - fglrx 2.9.12 [May 9 2003] on minor 0
May 24 07:48:45 darkstar kernel: Fire GL built-in AGP-support
May 24 07:48:45 darkstar kernel: Based on agpgart interface v0.99 (c) Jeff Hartmann
May 24 07:48:45 darkstar kernel: agpgart: Maximum main memory to use for agp memory: 816M
May 24 07:48:45 darkstar kernel: [fglrx] AGP detected, AgpState = 0x1f004e1b (hardware caps of chipset)
May 24 07:48:45 darkstar kernel: [fglrx] AGP enabled, AgpCommand = 0x1f004312 (selected caps)
May 24 07:48:45 darkstar kernel: [fglrx] free AGP = 54800384
May 24 07:48:45 darkstar kernel: [fglrx] max AGP = 54800384
May 24 07:48:45 darkstar kernel: [fglrx] free LFB = 116391936
May 24 07:48:45 darkstar kernel: [fglrx] max LFB = 116391936
May 24 07:48:45 darkstar kernel: [fglrx] free Inv = 0
May 24 07:48:45 darkstar kernel: [fglrx] max Inv = 0
May 24 07:48:45 darkstar kernel: [fglrx] total Inv = 0
May 24 07:48:45 darkstar kernel: [fglrx] total TIM = 0

Everything looks good then huh? If you could shed some light on this it would be great because I'd like to understand what happened and whether or not I am ok now. I'm getting just under 100fps (1024x768, everything maxed) in Quake3 (atleast I know hardware acceleration is actually working) but it should be atleast double that if I'm comparing it to Windows.

no if you use ATI's agpgart you don't use the kernel's agpgart. I remember seeing some posts somewhere about using ATI and getting the error message you're getting when trying to start x. I'll take a look and see what I can find. In the mean time just to give you something to compare to... using schneider's drivers and a 9700 pro at 8x glxgears runs between 1800 and 2800 fps.

maybe try setting the bios to 8x (so it doesn't have a choice as it sounds like you're running at 4x at the moment).

My AGP is set to 8x atm. It's been that way since yesterday when I was last poking around in the mobos BIOS.

1800-2800 fps? Something is definitely wrong then because I don't get over 85 fps. That's a drastic difference. I'm not 100 percent sure what part of my syslog you want to see so I'll post the last part of the most recent section (seems the most relevant since it contains all the messages associated with AGP or fglrx).

=====================================================
May 24 07:47:58 darkstar kernel: agpgart: Trying generic SiS routines for device id: 0655
May 24 07:48:41 darkstar modprobe: modprobe: Can't locate module char-major-10-134
May 24 07:48:45 darkstar modprobe: modprobe: Can't locate module char-major-226
May 24 07:48:45 darkstar last message repeated 3 times
May 24 07:48:45 darkstar kernel: agpgart: Unsupported SiS chipset (device id: 0655), you might want to try agp_try_unsupported=1.
May 24 07:49:02 darkstar modprobe: modprobe: Can't locate module sound-slot-1
May 24 07:49:02 darkstar modprobe: modprobe: Can't locate module sound-service-1-0
May 24 07:49:02 darkstar modprobe: modprobe: Can't locate module sound-slot-1
May 24 07:49:02 darkstar modprobe: modprobe: Can't locate module sound-service-1-0
May 24 07:49:38 darkstar modprobe: modprobe: Can't locate module sound-slot-0
May 24 07:49:38 darkstar modprobe: modprobe: Can't locate module sound-service-0-1
May 24 07:50:38 darkstar kernel: [fglrx:firegl_agp_lock_pages] *ERROR* agp_allocate_memory_phys_list failed
May 24 07:50:38 darkstar kernel: [fglrx:firegl_agp_lock_pages] *ERROR* agp_allocate_memory_phys_list failed
May 24 07:51:27 darkstar last message repeated 2 times
=====================================================

That doesn't look nice.

Why do you think enabling the external agpgart module again made a difference?

what was loaded the first time (that accelleration worked?)?

and what was loaded the second time ( that accelleration failed?)?

If you're talking about how I can get 100fps in Quake3 but only 85fps with fgl_glxgears nothing is actually different. When I try it again now the situation is the same.