ATI MOBILITY RADEON Xpress 200 + glxgears = good or bad?
Message
I've got a Turion with an ATI Xpress200 card, and everything works fine, except the dri. I'm using ati-drivers (w/extras) 8.20.8 and x11-drm-20051028 (the latest versions as of writing this.
Video works fine; X looks great, but i just can't get direct rendering working. Oh, and I have used eselect to specify the ATI gl.
Any ideas?
J.
Code: Select all
(II) fglrx(0): UMM Bus area: 0xd45c1000 (size=0x03a2f000)
(II) fglrx(0): UMM area: 0x1c5c1000 (size=0x03a2f000)
(II) fglrx(0): driver needs X.org 6.8.x.y with x.y >= 0.0
(II) fglrx(0): detected X.org 6.8.2.0
(II) Loading extension ATIFGLRXDRI
(II) fglrx(0): doing DRIScreenInit
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
[drm] failed to load kernel module "fglrx"
(II) fglrx(0): [drm] drmOpen failed
(EE) fglrx(0): DRIScreenInit failed!
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
(II) fglrx(0): FBADPhys: 0x1c000000 FBMappedSize: 0x03ff0000
(II) fglrx(0): FBMM initialized for area (0,0)-(1280,8191)
(II) fglrx(0): FBMM auto alloc for area (0,0)-(1280,768) (front color buffer - assumption)
(==) fglrx(0): Backing store disabled
(==) fglrx(0): Silken mouse enabled
(==) fglrx(0): Using hardware cursor (scanline 768)
(II) fglrx(0): Largest offscreen area available: 1280 x 7419
(**) Option "dpms"
(**) fglrx(0): DPMS enabled
(WW) fglrx(0): Option "IgnoreEDID" is not used
(WW) fglrx(0): Option "NoTV" is not used
(II) fglrx(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
Solid Horizontal and Vertical Lines
Offscreen Pixmaps
Setting up tile and stipple cache:
32 128x128 slots
32 256x256 slots
16 512x512 slots
(II) fglrx(0): Acceleration enabled
(II) fglrx(0): Direct rendering disabled
(II) Loading extension FGLRXEXTENSION
(II) Loading extension ATITVOUT
(==) RandR enabled
(II) Setting vga for screen 0.
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
Any ideas?
J.
"I cannot support a movement that exploded spending and borrowing and blames its successor for the debt."
-Andrew Sullivan
-Andrew Sullivan
atrus123 wrote:I've got a Turion with an ATI Xpress200 card, and everything works fine, except the dri. I'm using ati-drivers (w/extras) 8.20.8 and x11-drm-20051028 (the latest versions as of writing this.
Code: Select all
(II) fglrx(0): UMM Bus area: 0xd45c1000 (size=0x03a2f000) (II) fglrx(0): UMM area: 0x1c5c1000 (size=0x03a2f000) (II) fglrx(0): driver needs X.org 6.8.x.y with x.y >= 0.0 (II) fglrx(0): detected X.org 6.8.2.0 (II) Loading extension ATIFGLRXDRI (II) fglrx(0): doing DRIScreenInit drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed [drm] failed to load kernel module "fglrx" ( J.[/quote] Well, in your case flgrx kernel module (additional to fgltx X11 module), responsible for dri, failed to load. Do 'modprobe fglrx' and see in 'dmesg' what are the errors. I also can't make dri to work. However my module loads, DRI is initialized OK in the log, but starting X with dri enable I get black screen and hanged machine. I currently suspect it may come from the driver trying to use agp, where my card is on PCI-E and there is even no AGP bridge in the machine
Request update on workaround posted by Lelik:
Hi,
I managed to get past the "blank-screen" problem while starting up X (loading the DRI module) by disabling sideport and using UMA only in the BIOS as posted by lelik. However, I have two follow up questions:
- Is ATI planning a driver that will allow us to use sideport memory, or d we need to keep switching BIOS settings every time we plan on running Win/Linux? (I know this is not a gentoo q: this q is more in the hope that someone from ATI reads this thread and plans on being kind enough to post a response).
- By disabling sideport and enabling UMA, I got ~ 826 fps. Way better than 400 fps, however, nowhere close to the 2500 fps I get on my old radeon 8500... is this truly the max performance that can be squeezed out of this card using UMA?
Thanks
I managed to get past the "blank-screen" problem while starting up X (loading the DRI module) by disabling sideport and using UMA only in the BIOS as posted by lelik. However, I have two follow up questions:
- Is ATI planning a driver that will allow us to use sideport memory, or d we need to keep switching BIOS settings every time we plan on running Win/Linux? (I know this is not a gentoo q: this q is more in the hope that someone from ATI reads this thread and plans on being kind enough to post a response).
- By disabling sideport and enabling UMA, I got ~ 826 fps. Way better than 400 fps, however, nowhere close to the 2500 fps I get on my old radeon 8500... is this truly the max performance that can be squeezed out of this card using UMA?
Thanks
Edit: I feel a little silly. I forgot to copy the kernel over to /boot the last time I compiled it. It still doesn't load though. I'll post the output when I get home.dmpogo wrote: Well, in your case flgrx kernel module (additional to fgltx X11 module), responsible for dri, failed to load.
Do 'modprobe fglrx' and see in 'dmesg' what are the errors.
Code: Select all
[fglrx] Maximum main memory to use for locked dma buffers: 371 MBytes.
[fglrx] free PCIe = 54804480
[fglrx] max PCIe = 54804480
[fglrx] free LFB = 53145600
[fglrx] max LFB = 53145600
[fglrx] free Inv = 0
[fglrx] max Inv = 0
[fglrx] total Inv = 0
[fglrx] total TIM = 0
[fglrx] total FB = 0
[fglrx] total PCIe = 16384
Direct rendering works now, though it is only producing about 800fps. I'll play with it.
Thanks for the input. It got me looking in the right place.
Once I have fine-tuned it, I'll post my configs for posterity.
J.
"I cannot support a movement that exploded spending and borrowing and blames its successor for the debt."
-Andrew Sullivan
-Andrew Sullivan
Ok, this xorg.conf works with dri and ati-drivers.
Also, I do have agpart enabled in the kernel. It seems like others have had problems with enabling this, but mine will not work without it, even though the card is pci-e. I forget the exact errors, but without agpart, make modules_install complained about not being able to allocate some required resources for the fglx kernel module.
I also had to disable framebuffer.
J.
Code: Select all
# **********************************************************************
# DRI Section
# **********************************************************************
Section "dri"
# Access to OpenGL ICD is allowed for all users:
Mode 0666
# Access to OpenGL ICD is restricted to a specific user group:
# Group 100 # users
# Mode 0660
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
# **********************************************************************
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
RgbPath "/usr/X11R6/lib/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#
FontPath "/usr/share/fonts/artwiz"
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/"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/corefonts"
FontPath "/usr/share/fonts/sharefonts"
FontPath "/usr/share/fonts/terminus"
# FontPath "/usr/share/fonts/artwiz"
# The module search path. The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
EndSection
# **********************************************************************
# Server flags section.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
# Option "NoTrapSignals"
# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "Dont Zoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
# Option "AllowNonLocalModInDev"
EndSection
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for XFree86
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
# Option "Protocol" "GlidePointPS/2"
Option "Device" "/dev/input/mice"
Option "CorePointer"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
EndSection
# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the XF86Config man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "Monitor0"
HorizSync 31.5 - 80.5
VertRefresh 60 - 75
Option "DPMS"
# === mode lines based on GTF ===
# VGA @ 100Hz
# Modeline "640x480@100" 43.163 640 680 744 848 480 481 484 509 +hsync +vsync
# SVGA @ 100Hz
# Modeline "800x600@100" 68.179 800 848 936 1072 600 601 604 636 +hsync +vsync
# XVGA @ 100Hz
# Modeline "1024x768@100" 113.309 1024 1096 1208 1392 768 769 772 814 +hsync +vsync
# 1152x864 @ 60Hz
# Modeline "1152x864@60" 81.642 1152 1216 1336 1520 864 865 868 895 +hsync +vsync
# 1152x864 @ 85Hz
# Modeline "1152x864@85" 119.651 1152 1224 1352 1552 864 865 868 907 +hsync +vsync
# 1152x864 @ 100Hz
# Modeline "1152x864@100" 143.472 1152 1232 1360 1568 864 865 868 915 +hsync +vsync
# 1280x960 @ 75Hz
# Modeline "1280x960@75" 129.859 1280 1368 1504 1728 960 961 964 1002 +hsync +vsync
# 1280x960 @ 100Hz
# Modeline "1280x960@100" 178.992 1280 1376 1520 1760 960 961 964 1017 +hsync +vsync
# SXGA @ 100Hz
# Modeline "1280x1024@100" 190.960 1280 1376 1520 1760 1024 1025 1028 1085 +hsync +vsync
# SPEA GDM-1950 (60Hz,64kHz,110MHz,-,-): 1280x1024 @ V-freq: 60.00 Hz, H-freq: 63.73 KHz
# Modeline "GDM-1950" 109.62 1280 1336 1472 1720 1024 1024 1026 1062 -hsync -vsync
# 1600x1000 @ 60Hz
# Modeline "1600x1000" 133.142 1600 1704 1872 2144 1000 1001 1004 1035 +hsync +vsync
# 1600x1000 @ 75Hz
# Modeline "1600x1000" 169.128 1600 1704 1880 2160 1000 1001 1004 1044 +hsync +vsync
# 1600x1000 @ 85Hz
# Modeline "1600x1000" 194.202 1600 1712 1888 2176 1000 1001 1004 1050 +hsync +vsync
# 1600x1000 @ 100Hz
# Modeline "1600x1000" 232.133 1600 1720 1896 2192 1000 1001 1004 1059 +hsync +vsync
# 1600x1024 @ 60Hz
# Modeline "1600x1024" 136.385 1600 1704 1872 2144 1024 1027 1030 1060 +hsync +vsync
# 1600x1024 @ 75Hz
# Modeline "1600x1024" 174.416 1600 1712 1888 2176 1024 1025 1028 1069 +hsync +vsync
# 1600x1024 @ 76Hz
# Modeline "1600x1024" 170.450 1600 1632 1792 2096 1024 1027 1030 1070 +hsync +vsync
# 1600x1024 @ 85Hz
# Modeline "1600x1024" 198.832 1600 1712 1888 2176 1024 1027 1030 1075 +hsync +vsync
# 1920x1080 @ 60Hz
# Modeline "1920x1080" 172.798 1920 2040 2248 2576 1080 1081 1084 1118 -hsync -vsync
# 1920x1080 @ 75Hz
# Modeline "1920x1080" 211.436 1920 2056 2264 2608 1080 1081 1084 1126 +hsync +vsync
# 1920x1200 @ 60Hz
# Modeline "1920x1200" 193.156 1920 2048 2256 2592 1200 1201 1203 1242 +hsync +vsync
# 1920x1200 @ 75Hz
# Modeline "1920x1200" 246.590 1920 2064 2272 2624 1200 1201 1203 1253 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 1400x1050 @ 60Hz M9 Laptop mode
# ModeLine "1400x1050" 122.000 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync
# 1920x2400 @ 25Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@25" 124.620 1920 1928 1980 2048 2400 2401 2403 2434 +hsync +vsync
# 1920x2400 @ 30Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@30" 149.250 1920 1928 1982 2044 2400 2402 2404 2434 +hsync +vsync
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 "0x5a42"
# 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 ===
Section "Device"
Identifier "ATI Graphics Adapter"
Driver "fglrx"
# BusID "PCI:1:5:0"
# ### generic DRI settings ###
# === disable PnP Monitor ===
#Option "NoDDC"
# === disable/enable XAA/DRI ===
Option "no_accel" "no"
Option "no_dri" "no"
# === misc DRI settings ===
Option "mtrr" "off" # disable DRI mtrr mapper, driver has its own code for mtrr
# ### FireGL DDX driver module specific settings ###
# === Screen Management ===
Option "DesktopSetup" "0x00000100"
Option "MonitorLayout" "AUTO, NONE"
Option "IgnoreEDID" "off"
Option "HSync2" "unspecified"
Option "VRefresh2" "unspecified"
Option "ScreenOverlap" "0"
# === TV-out Management ===
Option "NoTV" "yes"
Option "TVStandard" "NTSC-M"
Option "TVHSizeAdj" "0"
Option "TVVSizeAdj" "0"
Option "TVHPosAdj" "0"
Option "TVVPosAdj" "0"
Option "TVHStartAdj" "0"
Option "TVColorAdj" "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"
# === Center Mode (Laptops only) ===
Option "CenterMode" "off"
# === Pseudo Color Visuals (8-bit visuals) ===
Option "PseudoColorVisuals" "off"
# === QBS Management ===
Option "Stereo" "off"
Option "StereoSyncEnable" "1"
# === FSAA Management ===
Option "FSAAEnable" "no"
Option "FSAAScale" "1"
Option "FSAADisableGamma" "no"
Option "FSAACustomizeMSPos" "no"
Option "FSAAMSPosX0" "0.000000"
Option "FSAAMSPosY0" "0.000000"
Option "FSAAMSPosX1" "0.000000"
Option "FSAAMSPosY1" "0.000000"
Option "FSAAMSPosX2" "0.000000"
Option "FSAAMSPosY2" "0.000000"
Option "FSAAMSPosX3" "0.000000"
Option "FSAAMSPosY3" "0.000000"
Option "FSAAMSPosX4" "0.000000"
Option "FSAAMSPosY4" "0.000000"
Option "FSAAMSPosX5" "0.000000"
Option "FSAAMSPosY5" "0.000000"
# === Misc Options ===
Option "UseFastTLS" "2"
Option "BlockSignalsOnLock" "on"
Option "UseInternalAGPGART" "yes"
Option "ForceGenericCPU" "no"
Option "KernelModuleParm" "agplock=0" # AGP locked user pages: disabled
# BusID "PCI:1:0:0" # no device found at config time
Screen 0
EndSection
# **********************************************************************
# Screen sections
# **********************************************************************
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen0"
Device "ATI Graphics Adapter"
Monitor "Monitor0"
DefaultDepth 24
#Option "backingstore"
Subsection "Display"
Depth 24
Modes "1280x960"
ViewPort 0 0 # initial origin if mode is smaller than desktop
# Virtual 1280 1024
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
### EOF ###I also had to disable framebuffer.
J.
"I cannot support a movement that exploded spending and borrowing and blames its successor for the debt."
-Andrew Sullivan
-Andrew Sullivan
Also, I do have agpart enabled in the kernel. It seems like others have had problems with enabling this, but mine will not work without it, even though the card is pci-e. I forget the exact errors, but without agpart, make modules_install complained about not being able to allocate some required resources for the fglx kernel module.
Same here
This is a short summary (in part - a memo for myself) about Radeon Xpress 200M PCI-E video, ati-drivers and DRI, as well as some other issues.
1) My platform: Compaq r4225, Athlon64, Radeon Xpress 200M PCI-E 128 Mb video.
Note, ATI makes a distinction between 200M, which it classifies as 'Mobility Product' and plain Radeon Xpress 200, which it classifies as 'Integrated Product'. I suspect the difference is the existence of SidePort with 128 Mb dedicated video RAM in 200M version.
2) Driver: ~amd64 ati-drivers-8.20.8
3) DRI:
a) if Sideport is enabled in BIOS either as a sole video memory or in mixed mode with UMA set to 32 or 64 Mb (segment of system memory used as a video one) then DRI is not working. DRI initializes OK, but X locks with black screen.
b) if BIOS is configured in UMA mode (abandoning dedicated memory) DRI is working. glxgears gives unspectacular 800 fps.
c) if BIOS is configured in Sideport+128M UMA, DRI works and gets the best performance for this machine, glxgears ~ 1700 fps.
d) With NoDRI 'on' option in xorg.conf, the driver uses GLX support from ATI, glxgears ~ 670 fps, for any memory configurations. As we see, DRI in pure UMA mode gives very little advantage over nonDRI ATI GLX.
e) In software emulation Mesa-glx gives 350fps for glxgears. If this is sufficient, the kernel module need not be bothered with.
4) Xvideo is NOT enabled by the driver by default (i.e with minimalistic xorg.conf). I had it enabled by
in 'Device' section. Some people seem to require
and/or
but they were not necessary for me to get XVideo
5) fglrx kernel module requires agpgart support (built in or modular) in the kernel. Module gives both compilation errors and
refuses to be inserted with agpgart disabled (some unresolved agp-related symbols).
6) MTRR:
the driver attempts to create multiple (9-12) mtrr regions, and quickly runs out of the number the kernel can support. I get error logs to that extend. However, if I enable 128M mtrr region before loading the driver
echo "base=0xc0000000 size=0x8000000 type=write-combining" >> /proc/mtrr
(Video memory sits at 0xc0000000 address and 0x8000000 is 128M), all the regions that fglrx creates are created as counts within this region and everything is fine.
Notice than when UMA is enable together with SidePort, driver creates additional uncacheble mtrr segment at 0xb0100000 . With UMA-only setup, the memory address is at 0xd8000000
Conclusions: seems ati drivers are buggy. I suspect they have not ironed out DRI support for SidePort configuration. Also, the requirement of agpgart on pure PCI-E (no AGP bridge) system seems to point to the half-bakedness of the drivers.
1) My platform: Compaq r4225, Athlon64, Radeon Xpress 200M PCI-E 128 Mb video.
Note, ATI makes a distinction between 200M, which it classifies as 'Mobility Product' and plain Radeon Xpress 200, which it classifies as 'Integrated Product'. I suspect the difference is the existence of SidePort with 128 Mb dedicated video RAM in 200M version.
2) Driver: ~amd64 ati-drivers-8.20.8
3) DRI:
a) if Sideport is enabled in BIOS either as a sole video memory or in mixed mode with UMA set to 32 or 64 Mb (segment of system memory used as a video one) then DRI is not working. DRI initializes OK, but X locks with black screen.
b) if BIOS is configured in UMA mode (abandoning dedicated memory) DRI is working. glxgears gives unspectacular 800 fps.
c) if BIOS is configured in Sideport+128M UMA, DRI works and gets the best performance for this machine, glxgears ~ 1700 fps.
d) With NoDRI 'on' option in xorg.conf, the driver uses GLX support from ATI, glxgears ~ 670 fps, for any memory configurations. As we see, DRI in pure UMA mode gives very little advantage over nonDRI ATI GLX.
e) In software emulation Mesa-glx gives 350fps for glxgears. If this is sufficient, the kernel module need not be bothered with.
4) Xvideo is NOT enabled by the driver by default (i.e with minimalistic xorg.conf). I had it enabled by
Code: Select all
Option 'VideoOverlay' 'on' Code: Select all
Option 'OpenGLOverlay' 'off' Code: Select all
Option 'PseudoColorVisuals' 'off' 5) fglrx kernel module requires agpgart support (built in or modular) in the kernel. Module gives both compilation errors and
refuses to be inserted with agpgart disabled (some unresolved agp-related symbols).
6) MTRR:
the driver attempts to create multiple (9-12) mtrr regions, and quickly runs out of the number the kernel can support. I get error logs to that extend. However, if I enable 128M mtrr region before loading the driver
echo "base=0xc0000000 size=0x8000000 type=write-combining" >> /proc/mtrr
(Video memory sits at 0xc0000000 address and 0x8000000 is 128M), all the regions that fglrx creates are created as counts within this region and everything is fine.
Notice than when UMA is enable together with SidePort, driver creates additional uncacheble mtrr segment at 0xb0100000 . With UMA-only setup, the memory address is at 0xd8000000
Conclusions: seems ati drivers are buggy. I suspect they have not ironed out DRI support for SidePort configuration. Also, the requirement of agpgart on pure PCI-E (no AGP bridge) system seems to point to the half-bakedness of the drivers.
Last edited by dmpogo on Sun Jan 29, 2006 3:41 am, edited 5 times in total.
DRI and Sideport:
dmpogo:
My experience with the 200M *almost* matches yours with one significant exception: DRI.
- Without DRI, I get 400 fps
- With DRI / sideport set in BIOS, I get the blank screen/lockup.
- With UMA only in BIOS, I get 800 fps
*** however ***
- With mixed mode (128M sideport + 128M UMA) I get 1600 - 2500 fps [Nothing spectacular, but livable]
I'm guessing that due to the agpgart dependency, DRI cannot initialize on sideport memory alone as that is inaccessible by AGP, however, once it initializes on UMA, the card itself can scale to use sideport memory, thereby improving GL perf.
Did anyone else have success using a mixed mode config? If this works for other 200M users, then this option might be the best "workaround" until ATI releases a pci-e driver.
Also: thanks for the pointer on XVideo: that was next on my to-do list
My experience with the 200M *almost* matches yours with one significant exception: DRI.
- Without DRI, I get 400 fps
- With DRI / sideport set in BIOS, I get the blank screen/lockup.
- With UMA only in BIOS, I get 800 fps
*** however ***
- With mixed mode (128M sideport + 128M UMA) I get 1600 - 2500 fps [Nothing spectacular, but livable]
I'm guessing that due to the agpgart dependency, DRI cannot initialize on sideport memory alone as that is inaccessible by AGP, however, once it initializes on UMA, the card itself can scale to use sideport memory, thereby improving GL perf.
Did anyone else have success using a mixed mode config? If this works for other 200M users, then this option might be the best "workaround" until ATI releases a pci-e driver.
Also: thanks for the pointer on XVideo: that was next on my to-do list
Re: DRI and Sideport:
Interesting, I'll double check the mixed mode and report. Hope I made an error before.acerbix wrote:dmpogo:
My experience with the 200M *almost* matches yours with one significant exception: DRI.
- Without DRI, I get 400 fps
- With DRI / sideport set in BIOS, I get the blank screen/lockup.
- With UMA only in BIOS, I get 800 fps
*** however ***
- With mixed mode (128M sideport + 128M UMA) I get 1600 - 2500 fps [Nothing spectacular, but livable]
Did you try 128M sideport + 32M UMA ?
Re: DRI and Sideport:
I have checked mixed mode again and yes for 128M Sideport + 128M UMA DRI works and gears give ~1700 fps - the best value I've seen on this machine.acerbix wrote:dmpogo:
My experience with the 200M *almost* matches yours with one significant exception: DRI.
- Without DRI, I get 400 fps
- With DRI / sideport set in BIOS, I get the blank screen/lockup.
- With UMA only in BIOS, I get 800 fps
*** however ***
- With mixed mode (128M sideport + 128M UMA) I get 1600 - 2500 fps [Nothing spectacular, but livable]
I'm guessing that due to the agpgart dependency, DRI cannot initialize on sideport memory alone as that is inaccessible by AGP, however, once it initializes on UMA, the card itself can scale to use sideport memory, thereby improving GL perf.
Did anyone else have success using a mixed mode config? If this works for other 200M users, then this option might be the best "workaround" until ATI releases a pci-e driver.
However for 128M SidePort + 32/64 UMA the driver locks in the same same way as with Sideport Only option.
I have edited my summry to this regard.
- trueshanti
- n00b
- Posts: 30
- Joined: Wed Feb 15, 2006 6:38 am
- Location: Thailand
- Contact:
Re: DRI and Sideport:
on glxgears or fgl_glxgear ??dmpogo wrote: I have checked mixed mode again and yes for 128M Sideport + 128M UMA DRI works and gears give ~1700 fps - the best value I've seen on this machine.
_ _ _