LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 02-13-2005, 12:12 AM   #1
t3gah
Member
 
Registered: Dec 2004
Distribution: SuSE, RedHat, ubuntu, Debian
Posts: 734

Rep: Reputation: 30
Arrow ATI 3D Acceleration


The quest for 3D acceleration for ATI video cards under Linux....

System Configuration
DFI NFII Ultra AL Motherboard (ACPI disabled)
Athlon XP3000+ *Barton Core* 333FSB CPU
Ultra 512MB DDR 400FSB RAM
ATI Radeon 9200 128MB 8x AGP (TV output = off)

Fedora Core 3 (kernel 2.6.9-1.667)
With a "workstation" install I could only get frame rates in the hundreds.

I checked multiple forum sites including this one and all document sites on the ATI driver subject including ati.com, stanford.edu/~fenn, DAG, livna, rpmfind.net, gtx.org, gnu.org, etc. I followed the instructions from each site and used the correct rpm's or source files and always got frame rates in the hundreds. Tux Racer and Hexen II crawled.

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

=[snip]=

# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************

# **********************************************************************
# 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/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/"

# 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 "Keyboard"
# 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" "microsoft"
Option "XkbLayout" "us"

EndSection


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

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/mouse"

# 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 - 60.0
VertRefresh 50 - 70
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 "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 ===

Section "Device"
Identifier "ATI Graphics Adapter"
Driver "fglrx"
# ### 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" "0x00000000"
Option "MonitorLayout" "AUTO, AUTO"
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" "1"
Option "BlockSignalsOnLock" "on"
Option "UseInternalAGPGART" "yes"
Option "ForceGenericCPU" "no"
BusID "PCI:2:0:0" # vendor=1002, device=5961
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 "1024x768" "800x600"
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 ###


[root@localhost ~]# lspci
00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1)
00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1)
00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1)
00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1)
00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1)
00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1)
00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1)00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3)
00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
01:08.0 SCSI storage controller: Adaptec AHA-2940U/UW/D / AIC-7881U
02:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200] (rev 01)
02:00.1 Display controller: ATI Technologies Inc RV280 [Radeon 9200] (Secondary) (rev 01)


[root@localhost ~]# glxgears
1280 frames in 5.0 seconds = 256.000 FPS
1449 frames in 5.0 seconds = 289.800 FPS
1476 frames in 5.0 seconds = 295.200 FPS
1394 frames in 5.0 seconds = 278.800 FPS
1584 frames in 5.0 seconds = 316.800 FPS
1584 frames in 5.0 seconds = 316.800 FPS
1716 frames in 5.0 seconds = 343.200 FPS
1584 frames in 5.0 seconds = 316.800 FPS
1452 frames in 5.0 seconds = 290.400 FPS
1716 frames in 5.0 seconds = 343.200 FPS
1716 frames in 5.0 seconds = 343.200 FPS
 
Old 02-13-2005, 12:13 AM   #2
t3gah
Member
 
Registered: Dec 2004
Distribution: SuSE, RedHat, ubuntu, Debian
Posts: 734

Original Poster
Rep: Reputation: 30
Arrow SuSE 9.1 Personal

The quest for 3D acceleration for ATI video cards under Linux (part 2)....

System Configuration
DFI NFII Ultra AL Motherboard (ACPI disabled)
Athlon XP3000+ *Barton Core* 333FSB CPU
Ultra 512MB DDR 400FSB RAM
ATI Radeon 9200 128MB 8x AGP (TV output = off)

SuSE 9.1 Personal (kernel 2.6.4-default)
I installed SuSE 9.1 Personal and enabled the beta 3D acceleration option in YaST. There was a warning that the driver was in the experimental stage, etc. My ATI 9200 AGP worked like a champ with frame rates in the thousands. Tux Racer and Hexen II rocked!

linux:~ # lspci
0000:00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1)
0000:00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1)
0000:00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1)
0000:00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1)
0000:00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1)
0000:00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1)
0000:00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
0000:00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
0000:00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1)
0000:00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3)
0000:00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
0000:00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
0000:01:08.0 SCSI storage controller: Adaptec AHA-2940U/UW/D / AIC-7881U
0000:02:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV280 [Radeon 9200] (rev 01)
0000:02:00.1 Display controller: ATI Technologies Inc: Unknown device 5941 (rev 01)


linux:~ # glxgears
9511 frames in 5.0 seconds = 1902.200 FPS
10670 frames in 5.0 seconds = 2134.000 FPS
10654 frames in 5.0 seconds = 2130.800 FPS
10696 frames in 5.0 seconds = 2139.200 FPS
10687 frames in 5.0 seconds = 2137.400 FPS
10741 frames in 5.0 seconds = 2148.200 FPS
10680 frames in 5.0 seconds = 2136.000 FPS
10674 frames in 5.0 seconds = 2134.800 FPS
10726 frames in 5.0 seconds = 2145.200 FPS
10664 frames in 5.0 seconds = 2132.800 FPS
10586 frames in 5.0 seconds = 2117.200 FPS
10628 frames in 5.0 seconds = 2125.600 FPS
10621 frames in 5.0 seconds = 2124.200 FPS
10635 frames in 5.0 seconds = 2127.000 FPS
10660 frames in 5.0 seconds = 2132.000 FPS
10641 frames in 5.0 seconds = 2128.200 FPS
10693 frames in 5.0 seconds = 2138.600 FPS


# /.../
# SaX generated XFree86 config file
# Created on: 2005-02-12T03:04:45-0500.
#
# Version: 4.8
# Contact: Marcus Schaefer <sax@suse.de>, 2002
#
# Automatically generated by [ISaX] (4.8)
# PLEASE DO NOT EDIT THIS FILE!
#

Section "Files"
FontPath "/usr/X11R6/lib/X11/fonts/misc:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/local"
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/URW"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo"
FontPath "/usr/X11R6/lib/X11/fonts/PEX"
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic"
FontPath "/usr/X11R6/lib/X11/fonts/latin2/misc:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/latin2/75dpi:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/latin2/100dpi:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/latin2/Type1"
FontPath "/usr/X11R6/lib/X11/fonts/latin7/75dpi:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/baekmuk:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/japanese:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/kwintv"
FontPath "/usr/X11R6/lib/X11/fonts/truetype"
FontPath "/usr/X11R6/lib/X11/fonts/uni:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/CID"
FontPath "/usr/X11R6/lib/X11/fonts/ucs/misc:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/ucs/75dpi:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/ucs/100dpi:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/hellas/misc:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/hellas/75dpi:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/hellas/100dpi:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/hellas/Type1"
FontPath "/usr/X11R6/lib/X11/fonts/misc/sgi:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/xtest"
FontPath "/opt/kde3/share/fonts"
InputDevices "/dev/ttyS0"
InputDevices "/dev/ttyS1"
InputDevices "/dev/ttyS2"
InputDevices "/dev/ttyS3"
InputDevices "/dev/ttyS4"
InputDevices "/dev/ttyS5"
InputDevices "/dev/ttyS6"
InputDevices "/dev/ttyS7"
InputDevices "/dev/ttyS8"
InputDevices "/dev/psaux"
InputDevices "/dev/logibm"
InputDevices "/dev/sunmouse"
InputDevices "/dev/atibm"
InputDevices "/dev/amigamouse"
InputDevices "/dev/atarimouse"
InputDevices "/dev/inportbm"
InputDevices "/dev/gpmdata"
InputDevices "/dev/mouse"
InputDevices "/dev/usbmouse"
InputDevices "/dev/adbmouse"
InputDevices "/dev/input/mice"
InputDevices "/dev/input/event0"
InputDevices "/dev/pointer0"
InputDevices "/dev/pointer1"
InputDevices "/dev/pointer2"
InputDevices "/dev/pointer3"
EndSection

Section "ServerFlags"
Option "AllowMouseOpenFail"
Option "RandR" "on"
EndSection

Section "Module"
Load "v4l"
Load "extmod"
Load "type1"
Load "freetype"
Load "dbe"
Load "dri"
Load "speedo"
Load "glx"
EndSection

Section "InputDevice"
Driver "Keyboard"
Identifier "Keyboard[0]"
Option "Protocol" "Standard"
Option "XkbLayout" "us"
Option "XkbModel" "microsoft"
Option "XkbRules" "xfree86"
Option "XkbVariant" "pc104"
EndSection


Section "InputDevice"
Driver "mouse"
Identifier "Mouse[1]"
Option "ButtonNumber" "7"
Option "Buttons" "7"
Option "Device" "/dev/mouse"
Option "InputFashion" "Mouse"
Option "Name" "PS/2-Mouse;NetScrollPS/2"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
EndSection


Section "Monitor"
DisplaySize 260 200
HorizSync 31-57
Identifier "Monitor[0]"
ModelName "151FS"
Option "DPMS"
VendorName "COMPAQ"
VertRefresh 50-90
UseModes "Modes[0]"
EndSection


Section "Modes"
Identifier "Modes[0]"
Modeline "1024x768" 61.89 1024 1080 1184 1344 768 769 772 794
Modeline "1024x768" 73.89 1024 1080 1192 1360 768 769 772 799
EndSection


Section "Screen"
DefaultDepth 16
SubSection "Display"
Depth 15
Modes "1024x768"
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768"
EndSubSection
SubSection "Display"
Depth 24
Modes "1024x768"
EndSubSection
SubSection "Display"
Depth 32
Modes "1024x768"
EndSubSection
SubSection "Display"
Depth 8
Modes "1024x768"
EndSubSection
Device "Device[0]"
Identifier "Screen[0]"
Monitor "Monitor[0]"
EndSection


Section "Device"
BoardName "RV280 5961"
BusID "2:0:0"
Driver "radeon"
Identifier "Device[0]"
Screen 0
Option "Rotate" "off"
VendorName "ATI"
EndSection


Section "ServerLayout"
Identifier "Layout[all]"
InputDevice "Keyboard[0]" "CoreKeyboard"
InputDevice "Mouse[1]" "CorePointer"
Option "Clone" "off"
Option "Xinerama" "off"
Screen "Screen[0]"
EndSection

Section "DRI"
Group "video"
Mode 0660
EndSection
 
Old 02-13-2005, 12:14 AM   #3
t3gah
Member
 
Registered: Dec 2004
Distribution: SuSE, RedHat, ubuntu, Debian
Posts: 734

Original Poster
Rep: Reputation: 30
Question Beta ATI driver works better than released????

The quest for 3D acceleration for ATI video cards under Linux (part 3)....

System Configuration
DFI NFII Ultra AL Motherboard (ACPI disabled)
Athlon XP3000+ *Barton Core* 333FSB CPU
Ultra 512MB DDR 400FSB RAM
ATI Radeon 9200 128MB 8x AGP (TV output = off)

Tools, Patches and Drivers
check.sh

ati-driver-8.8.25-1.1.src.rpm
ati-glx-8.8.25-1.1.i386.rpm

fglrx_4_2_0-8.8.25-1.i386.rpm
fglrx_4_3_0-8.8.25-1.i386.rpm
fglrx_6_8_0-8.8.25-1.i386.rpm

fglrx-kernel2.6.10.patch

kernel-module-ati-2.6.10-1.737_FC3-3.14.6-1.i386.rpm
kernel-module-ati-2.6.10-1.741_FC3-3.14.6-1.i386.rpm

Questions

What's the deal between SuSE, Fedora and ATI?

Why did the default driver from SuSE 9.1 Personal do better than both Fedora Core 3's & ATI drivers, patches and dependencies?
 
Old 02-14-2005, 02:58 AM   #4
t3gah
Member
 
Registered: Dec 2004
Distribution: SuSE, RedHat, ubuntu, Debian
Posts: 734

Original Poster
Rep: Reputation: 30
Question new custom fedora install frame rates exceed new ati driver

native FC3 ATI driver versus replacement?

I have since blown away the entire FC3 install for a new 'custom' install. No other files except the files from the FC3 CD's. Same hardware.

With the base Fedora Core 3 ATI driver and 3D support files, glxgears had this performance:

[root@localhost torcs-1.2.3]# glxgears
6100 frames in 5.0 seconds = 1220.000 FPS
6193 frames in 5.0 seconds = 1238.600 FPS
6194 frames in 5.0 seconds = 1238.800 FPS
6193 frames in 5.0 seconds = 1238.600 FPS
6194 frames in 5.0 seconds = 1238.800 FPS
6190 frames in 5.0 seconds = 1238.000 FPS
21734 frames in 5.0 seconds = 4346.800 FPS
41765 frames in 5.0 seconds = 8353.000 FPS
41788 frames in 5.0 seconds = 8357.600 FPS
41778 frames in 5.0 seconds = 8355.600 FPS
41758 frames in 5.0 seconds = 8351.600 FPS
41622 frames in 5.0 seconds = 8324.400 FPS
41624 frames in 5.0 seconds = 8324.800 FPS
41663 frames in 5.0 seconds = 8332.600 FPS
41743 frames in 5.0 seconds = 8348.600 FPS



The jump in frame per second is when I placed my xterm window completely over the glxgears animation.

Why do I want the livna radeon driver again?????
 
Old 02-14-2005, 07:06 AM   #5
bobbens
Member
 
Registered: Sep 2004
Location: Barcelona
Distribution: Debian, FreeBSD, Gentoo
Posts: 586

Rep: Reputation: 30
i wouldn't really trust the glxgears, it jumps alot with different cards and systems. With my debian and a radeon 9600 i'm only getting 1300 fps with glxgears, yet i play half-life 2 at a resolution of 1024x768 just fine (except big maps with lotsa monsters), i even beat the game :P. I can also play ut2004 just fine except onslaught where it lags a bit (on really high settings) and warcraft III with settings on max. I'm getting slightly worse then i did on windows, but i blame the drivers, ati is teh sux. Since you have a 9200 you can use the dri drivers, which i heard are alot better and won't taint your kernel.
Well i'm getting off subject here, conclusively, try benchmarking with some game or some "real" 2d program, not just glxgears to be able to really tell what's happening. Of course i could be wrong and the glxgears might be giving you the difference, but i wouldn't trust them. Some nvidia people get 8k or so i've seen, yet they do barely better in ut2004, just a question of how the kernel modules and stuff process the data.
Hope i helped some.
Oh and use fglrxinfo to see what drivers you truly are using, would help more the lspci.
 
Old 02-14-2005, 01:04 PM   #6
t3gah
Member
 
Registered: Dec 2004
Distribution: SuSE, RedHat, ubuntu, Debian
Posts: 734

Original Poster
Rep: Reputation: 30
Exclamation screenshots......

Quote:
Originally posted by bobbens
i wouldn't really trust the glxgears, it jumps alot with different cards and systems. With my debian and a radeon 9600 i'm only getting 1300 fps with glxgears, yet i play half-life 2 at a resolution of 1024x768 just fine (except big maps with lotsa monsters), i even beat the game :P. I can also play ut2004 just fine except onslaught where it lags a bit (on really high settings) and warcraft III with settings on max. I'm getting slightly worse then i did on windows, but i blame the drivers, ati is teh sux. Since you have a 9200 you can use the dri drivers, which i heard are alot better and won't taint your kernel.

Well i'm getting off subject here, conclusively, try benchmarking with some game or some "real" 2d program, not just glxgears to be able to really tell what's happening. Of course i could be wrong and the glxgears might be giving you the difference, but i wouldn't trust them. Some nvidia people get 8k or so i've seen, yet they do barely better in ut2004, just a question of how the kernel modules and stuff process the data.

Hope i helped some.

Oh and use fglrxinfo to see what drivers you truly are using, would help more the lspci.
I tried to update the driver again using the livna rpm's and I ran fglrxconfig which created the XF86Config-4 file. The menu also got a new addition.....

]Applications > System Settings > More System Settings > ATI-fglrx Display Settings

The mesa3d OpenGL info still showed up in the ATI-fglrx Display Settings control applet which I've read elsewhere as a signal that the update didn't work. Sure enough the frame rates and all of my games are crawling and glxgears, the 3D telltale has frame rates no more than 300FPS. All the games played great until I updated again. My resolution is 1024x768. Games full screen or windowed slug along at the same rate,

Snapshots of my desktop and control panel.....

http://www.geocities.com/t3gah/image...screenshot.jpg

http://www.geocities.com/t3gah/images/Screenshot.png


.. Next tiime I'll do the fglrxinfo output. Forgot about that. Thanks for the tip.


I wish someone would write up a real how-to complete with screenshots, etc. for the extreme newbie to walk through

Last edited by t3gah; 02-14-2005 at 01:59 PM.
 
Old 02-14-2005, 01:21 PM   #7
bobbens
Member
 
Registered: Sep 2004
Location: Barcelona
Distribution: Debian, FreeBSD, Gentoo
Posts: 586

Rep: Reputation: 30
Have you tried the DRI drivers, i think up to radeon 9200 is supported and that they're pretty good, otherswise i'd get the drivers off the website, i tried to get them for my debian already prepackaged and stuff, it never worked, just screwed it all up, but when i went and got the official ones and followed all the steps (most of it is intuition, i can guide you through it) i got them working great, with version 8.8.25 (latest one right now). Otherwise use the old ones.

Last edited by bobbens; 02-14-2005 at 01:24 PM.
 
Old 02-14-2005, 02:04 PM   #8
t3gah
Member
 
Registered: Dec 2004
Distribution: SuSE, RedHat, ubuntu, Debian
Posts: 734

Original Poster
Rep: Reputation: 30
Quote:
Originally posted by bobbens
Have you tried the DRI drivers, i think up to radeon 9200 is supported and that they're pretty good, otherswise i'd get the drivers off the website, i tried to get them for my debian already prepackaged and stuff, it never worked, just screwed it all up, but when i went and got the official ones and followed all the steps (most of it is intuition, i can guide you through it) i got them working great, with version 8.8.25 (latest one right now). Otherwise use the old ones.
I couldn't find the DRI drivers. Also the driver update messed up big time because now Fedora Core 3 thinks my 8x AGP card, which was listed in 4x mode for the native install, is listed as a PCI card!!!

Website? Which one? I've been to so many I left footprints!!
 
Old 02-14-2005, 03:09 PM   #9
bobbens
Member
 
Registered: Sep 2004
Location: Barcelona
Distribution: Debian, FreeBSD, Gentoo
Posts: 586

Rep: Reputation: 30
Here you can get the official ati drivers and here you can get the DRI drivers.
I'd recommend the DRI drivers if you can get them working, otherwise go with the ati drivers. The ati drivers are in rpm format, i don't remember what gentoo uses, but i can convert it to deb and get it working fine for my debian, though you have to build the module, but it's really easy. Hope you can get it working!
 
Old 02-16-2005, 12:15 AM   #10
t3gah
Member
 
Registered: Dec 2004
Distribution: SuSE, RedHat, ubuntu, Debian
Posts: 734

Original Poster
Rep: Reputation: 30
Arrow Why oh why am I having so many problems with my ATI driver install?

============================================================================
My research : WHAT FOR's for ATI 3D Acceleration

System requirement must haves before attempting to install the ATI driver:
* glibc (version 2.2 or 2.3)
--- Link: ftp.gnu.org/gnu/glibc/

* GCC installed (which is a compiler / current version 3.4.3)
--- Link: ftp.gnu.org/gnu/gcc/

* Make utility (rcurrent version 3.8.0)
--- Link: ftp.gnu.org/gnu/make/

In my opinion they should be installed by default or there should be a warning/notice that there are no compilers or make utils installed with the "style" of install you've chosen from the distro install gui.

For me I installed all of the compilers that came with Fedora Core 3 for whatever I might install in the future. (In the case of Fedora Core 3 I used the RPM's located on the (4) Fedora Core 3 CD's from X)

* X-Window System installed (XFree86 version 4.1, 4.2, 4.3 or X.Org version 6.8)
--- Links: http://www.xfree86.org or http://www.x.org (Fedora Core 3 uses X.org)

* Kernel source code
* Kernel header files (includes)

Kernel source code should match what you have, but in the case of your particular system, the new kernel may fix other things that may look like the video driver is the problem.

Why update the o/s kernel?
==========================
Support for 3D acceleration was not present in certain operating systems awhile back so the o/s needed a service pack before you could load the ATI 3D driver. The reference is the ATI 3D Rage Pro and Microsoft Windows products. There are also other references to every operating system out there. Latest hardware often denotes updated support required for the o/s and many times the driver as well.

Service Packs or Support Packs updated the operating system and the support files. The size of the service update showed just how much needed to be updated and the update is usually compressed data files. Your Linux O/S may need an update too depending upon the current kernel it has. In many driver update cases there is no one site that shows all this information and that is true for Microsoft, NetWare, FreeBSD and Linux or as far as I know. The hardware device manufacturer just refers you to the distro web site.

Then you have to check the Changelog many people say. What's a Changelog? What changes have been made since the previous released version. Unfortunately it is written by developers and programmers in terms that only they and a few other people understand. In my opinion it should be written in plain terms as well and not just "physician speak". What's that? Ever go to the doctor and here the medical jargon explanation and have to say, "Doc, please repeat that in terms "I" can understand, ok?". So anyway, the Changelog should just say this for all who read to understand:

"Added or Removed support for: <laymans terms>
* Developer/Programmer terms: <info for the technically inclined>"

Until this happens everyone will have to search around each site for their device driver info and driver downloads or search the Changelog if you know what keyword they, the developers use or what pertains to your issue or device. Currenly devices you buy for PC's don't come with Linux driver update/install CD's. Why? Ask them because I have no idea why they wouldn't have one. During my research I found webcams and video camera's and all sorts of other devices cause video lock ups or terrible performance due to chipset of the motherboard or the device drivers for those devices themselves. The kernel I have now in FC3 is 2.6.9-1.667 which apparently has a problem with nVidia nForce2 chipsets.


The Kernel
==========
What version do I have now?
* X-Windows session: Open a terminal window.
* Console session: From X-Windows you can logout or do a key combo, CTRL-ALT-F1.

- Type the following at the command prompt:

uname -r

(Write down the information.)

What version is the latest?
* http://www.linux.org (why's of updating the kernel, if you can find the information)
There's a link to the current (released) kernel listed which takes you here to Linuxhq.com. From there you have to look at the "drivers" link since the obvious term "video" is not on the main list. Why do I even mention that? Because "sound" is on the main list. Following the tree I found this link: http://www.linuxhq.com/kernel/v2.6/1...deo/index.html

Where do I get the kernel?
* http://www.kernel.org (kernels and/or patches to update your kernel to the latest version)
- The signed files are for using YUM.

Kernel files:
=============
* B2zipped:
- File: linux-2.6.10.tar.bz2
Link: http://ftp.linux.org/pub/linux/kerne...2.6.10.tar.bz2
-- Size (bytes): 36533484
-- Date: Dec 24 22:38

- File: linux-2.6.10.tar.bz2.sign
Link: http://ftp.linux.org/pub/linux/kerne...bz2.sign<br />
-- Size (bytes): 248
-- Date: Dec 24 22:38

* GZipped:
- File: linux-2.6.10.tar.gz
Link: http://ftp.linux.org/pub/linux/kerne...-2.6.10.tar.gz
-- Size (bytes): 45799369
-- Date: Dec 24 22:38

- File: linux-2.6.10.tar.gz.sign
Link: http://ftp.linux.org/pub/linux/kerne...10.tar.gz.sign
-- Size (bytes): 248
-- Date: Dec 24 22:38

* Uncompressed:
- File: linux-2.6.10.tar.sign
Link: http://ftp.linux.org/pub/linux/kerne....6.10.tar.sign
-- Size (bytes): 248
-- Date: Dec 24 22:38

Patches
=======
* B2zipped:
- File: patch-2.6.10.bz2
Link: http://ftp.linux.org/pub/linux/kerne...tch-2.6.10.bz2
-- Size (bytes): 4851041
-- Date: Dec 24 22:38

- File: patch-2.6.10.bz2.sign
Link: http://ftp.linux.org/pub/linux/kerne....6.10.bz2.sign
-- Size (bytes): 248
-- Date: Dec 24 22:38

* Gunzipped:
- File: patch-2.6.10.gz
Link: http://ftp.linux.org/pub/linux/kerne...atch-2.6.10.gz
-- Size (bytes): 5961609
-- Date: Dec 24 22:38

- File: patch-2.6.10.gz.sign
Link: http://ftp.linux.org/pub/linux/kerne...2.6.10.gz.sign
-- Size (bytes): 248
-- Date: Dec 24 22:38

* Uncompressed:
- File: patch-2.6.10.sign
Link: http://ftp.linux.org/pub/linux/kerne...ch-2.6.10.sign
-- Size (bytes): 248
-- Date: Dec 24 22:38

=============================================
Changelog
Link: http://ftp.kernel.org/pub/linux/kernel/v2.6/

File: ChangeLog-2.6.10
Size (bytes): 1552868
Date: Dec 24 22:30

/1.55 megabytes for a text file!!! Big? 1 kilobyte equals 1 page!/

--- Location: http://ftp.kernel.org/pub/linux/kern...angeLog-2.6.10



What do I look for? See what I looked for below:
=============================================
Summary of changes from v2.6.9 to v2.6.10


---- Searched Changelog for "ATI"

"[PATCH] USB: usb_unlink_urb removal from input/ati_remote.c"


---- Searched Changelog for "3D & mach64"

"[PATCH] fbdev: Various mach64 changes

Alexander Kern <alex.kern@gmx.de>
[PATCH] port Daniel Mantione 2.4 driver to 2.6
[PATCH] add more pci_id number
[PATCH] add accelerated imgblit
[PATCH] revert SDRAM_MAGIC_PLL to old behaviour
[PATCH] do a "from BIOS" initialisation only by __i386__

Arnaud FONTAINE <arnaud.fontaine@free.fr>
[PATCH atyfb] correction for 3D Rage Mobility L

Geert Uytterhoeven <geert@linux-m68k.org>
[PATCH atyfb] Atari Atyfb fixes
[PATCH atyfb] Atyfb on Mach64 GX or Atari
[PATCH 468] m68k sparse floating point

James Simmons <jsimmons@infradead.org>
[PATCH add] port to framebuffer_alloc api

Nicolas Souchu <nsouch@free.fr>
[PATCH] I do not found a copy, but it was incorporated too

Ville Syrjälä <syrjala@sci.fi>
[PATCH] fix pan with doublescan
[PATCH] another double scan fix
[PATCH] disable linear aperture register access
[PATCH] Memory type correction
[PATCH] atyfb (2.6): Fix mmio_start
[PATCH] atyfb (2.6): Fix mem_refresh_rate for Mobility
[PATCH] atyfb (2.6): Add RGB565 support
[PATCH] atyfb: Blank LCD by turning off backlight voltage
[PATCH] atyfb: Rage LT LCD register access
[PATCH] atyfb: vblank irq support
[PATCH] atyfb: MTRR support

Antonino Daplas <adaplas@pol.net>
remove/modify all references to info->cursor"


---- Searched Changelog for "acceleration"

"[PATCH] ns83820: add vlan tag hardware acceleration support"

"[ARM PATCH] 2167/1: OMAP update 6/8: Add graphics acceleration support to DMA"


---- Searched Changelog for "9200"
* Results: (none)


---- Searched Changelog for "AGP"

"[PATCH] fbdev: Remove i810fb explicit agp initialization hack."

"[PATCH] janitor: char/sis-agp: replace schedule_timeout() with msleep()"

"PCI: fix up pci_save/restore_state in via-agp due to api change."


"[CPUFREQ] NVidia nForce2 FSB cpufreq driver.

Adds cpufreq support for FSB changing on nForce2 platforms. On this
plattforms the PCI/AGP clock is independent from the FSB and it also
doesn't depend on the used CPU."

(this is my motherboards chipset, nVidia nForce2 / DFI NFII Ultra AL)


"[PATCH] FB_INTEL Kconfig breakage

FB_INTEL selects AGP_INTEL (i.e. intel-agp.c), which is i386-only.

AGP_INTEL itself depends on X86 && !X86_64 and for a good reason - it doesn't
build elsewhere."


---- Searched Changelog for "radeon" & "video"

"[PATCH] janitor: list_for_each: drivers-char-drm-radeon_mem.c

s/for/list_for_each/"

"[PATCH] janitor: video/radeon_base: replace MS_TO_HZ() with msecs_to_jiffies()

Replace MS_TO_HZ() with msecs_to_jiffies()."

"[PATCH] janitor: video/radeonfb: remove MS_TO_HZ()

Removes definition of MS_TO_HZ() in favor of msecs_to_jiffies()."

"[ACPI] ACPI_VIDEO is EXPERIMENTAL"

"[ACPI] fix video module unload oops"

"[PATCH] tmpfs truncate latency

High latency observed when deleting a large video file from tmpfs.

shmem_truncate held info->lock (easily dropped) and nested atomic kmaps
(more awkward to handle, since it's structured to keep them) while scanning
the many pages of its swap vector. Now be prepared to cond_resched every
64 ops (but scan an empty page in one go).

shmem_free_pages to free a linked list of empty swap vector pages at the
end (cond_resched every 64): could still free them one by one in the main
loop, but this foreshadows scalability changes - which will want to use RCU
on them, only freeing the pages after a grace period."

"[PATCH] radeonfb: If no video memory, exit with error

Nothing good will happen if we try to ioremap and use a zero-sized frame
buffer. I observed this problem on an ia64 sx1000 box, where the BIOS
doesn't run the option ROM. If we try to continue, radeonfb just gets
hopelessly confused because the card isn't initialized correctly."

"[PATCH] fbcon: Remove spurious casts

This patch removes unnecessary casts from drivers/video/console/fbcon.c.
Assignment from a void pointer does not require a cast and char type is
promoted to int automatically."


"[PATCH] USB: remove dead code in usb video

Hi,

Patch below removes somem dead, never used code from the usbvideo driver,
including a function that uses interruptible_sleep_on_timeout() oddly."

"[PATCH] saa7111.c: fix VIDEO_MODE_SECAM

VIDEO_MODE_SECAM was incorrectly writing the contents of cached register 14
back to hardware register 8, rather than using cached register 8."

"[PATCH] atyfb: Fix power management

The new atyfb has the return value for the Power Management routine
wrong. This prevents sleep from working on PowerBooks with mach64
video chips. This fixes it."

"[ACPI] fix warnings for 64-bit video build (Luming Yu)"

"[PATCH] v4l: yet another video-buf interface update

This is one more interface fix for the video-buf.c module, the first
attempt on that wasn't that clever. Instead of passing the driver private
data through all function calls I've just made that an element of the
videobuf_queue struct which is passed around everythere _anyway_.

That removes some reduncancy, should be less error prone and gain me some
points on rusty's interface design scala

It also fixes the tvtime crashes which where caused by overviewing one
place to fixup in the first attempt."

(the list goes on and on for the word "video" with reference to "[PATCH] v41:" and there are sub-sections of chipsets other that what this post is about. Check the file yourself for your chipset)

"[PATCH] media/video/bw-qcam.c: remove an unused function

The patch below removes an unused function from media/video/bw-qcam.c"

"[PATCH] video-buf oops/crash fixes

Some places which need adaption to the last video-buf API change where
forgotten, this patches fixes them up. Hope I really caught them all now."

"[PATCH] iomem annotations and isa_-ectomy: media/video/pms.c

switched to ioremap() + normal iomem access primitives"

"[PATCH] video: semicolon bug in atyfb_base.c

Indentiation and logic suggest this was wrong."

"[PATCH] media: Update drivers/media/video/arv.c

Here is a patch to update AR camera device driver.

drivers/media/video/arv.c:

- Remove warnings; use module_param() instead of MODULE_PARM(), because
MODULE_PARM() is deprecated.

- Fix white-space damages."

"[PATCH] ppc64: Workaround PCI issue on g5

ppc64 has a global called "pci_probe_only" which, when set, prevents the
arch PCI code from calling pci_assign_unassigned_resources(). This was
cleared by pmac so far, but a bug in the definition of the variable make
that ineffective until 2.6.10, and so we never called
pci_assign_unassigned_resources().

With 2.6.10, that bug was fixed and so we now call it, which results in
some problems. Some devices who have perfectly valid assigned addresses by
firmware end up beeing moved around anyway, which is a BAD thing can can
break boot on some machines since it breaks the relationship between
addresses in Open Firmware device-tree and actual location of PCI devices.
(Some low level things like the PIC are ioremap'ed based on their OF
address, way before the PCI based ASIC hosting them has been found). This
also break the "offb" default framebuffer driver since the video card ends
up beeing moved around as well.

For now, the fix is to set pci_probe_only on pmac, thus reverting to the
old behaviour. In the long run, it would be interesting to "fix"
pci_assign_unassigned_resources() so that it does what it's name claims,
and only assigns things that have been left unassigned instead of moving
things around gratuituously..."

"http://bugme.osdl.org/show_bug.cgi?id=3286

The kernel keeps printing "Lost sync on frames" error messages as soon as a
program tries to access the webcam. No video data can be retrieved from
the webcam.

The following patch seems enough to solve the problem. (just inverting the
order at which the old and new data blocks are sent to the user)."

"[PATCH] VGA console font problems on 2.6 kernel

From: Egbert Eich <eich@suse.de>

I would like to utilize kernel ioctls to save/restore console fonts
in VGA text mode when running X. So far the Xserver takes care of this
however there more and more problems with this:
1. On some platforms (IA64) we need to POST the BIOS before
we even have a chance to access the hardware ourselves.
This POSTing will usually undo any changes to the graphics
hardware that the kernel may have done.
2. More and more drivers fully rely on BIOS support however
the BIOS functions which could be used to save/restore
register settings may be broken so the only way of mode
save/restore is getting/setting the BIOS mode ID.

I've hacked up some code for X however I ran into two problems:

1. con_font_get() in linux/drivers/char/vt.c seems to be broken as
the font parameters (height, width, charcount) are never reported
back. Therefore this function seems to be pretty useless.
The fix is simple (please see below).

2. fb consoles seem to allow to install fonts per vt so that the user
can have a different font on every console. The text console driver
doesn't support this: the font is downloaded to the video card
and will be used for all systems. Still the vga_con driver stores
the font parameters per console with the effect that setting a
font with different parameters on one console will result in the
wron values when this font information is read back from another
console.
Appearantly this broken feature has been introduced in 2.6 as
in the 2.4 kernel the vga_con font information is stored in one
single global variable.

The IA64 platform at least still heavily relies on the VGA text console.
To be able to fix some VT switching issues with X on this platform I
need these two issues resolved."

"[PATCH] fbdev: fix framebuffer memory calculation for vesafb

- use vesafb_fix.line_length * vesafb_defined.yres to calculate the minimum
memory required for a video mode. From Aurelien Jacobs <aurel@gnuage.org>.

- separately calculate the memory required for a video mode, memory to be
remapped, and total memory (for MTRR). From Gerd Knorr
<kraxel@bytesex.org>.

- the 'vram' option is for memory to be remapped, not total memory."

(I noticed a vesafb error after I updated the ATI driver the first time around)

"[PATCH] sata_sil mod15 quirk with Seagate ST3120026AS

From: <stuart@cybertherial.com>

Hardware Environment: AMD64, sil3512 controller on m/b. Harddrive: Seagate
120GB ST3120026AS

Problem Description: Drive would lock when writing large files, eg video
from firewire, audio editing. Checked dmesg, was obviously the sata drive.

Have added the drive to the blacklist in sata_sil.c and the problem seems
to have disappeared.

Is there a good test to verify that the mod15 bug is really the problem?"

---- Searched Changelog for "dri" & "drm"
* Results:
"[PATCH] mark inter_module_* deprecated

These had been officially deprecated since Rusty's module rewrite, but
never got the __deprecated marker. The only remaining users are drm and
mtd, so we'll get some warnings for common builds. But maybe that's the
only way to get the drm people to fix the mess "

"[PATCH] drm_drv.h: replace pci_find_device

As pci_find_device is going away I've replaced it with pci_get_device.
for_each_pci_dev is a macro wrapper around pci_get_device."

Last edited by t3gah; 02-16-2005 at 04:40 AM.
 
Old 02-16-2005, 12:43 AM   #11
t3gah
Member
 
Registered: Dec 2004
Distribution: SuSE, RedHat, ubuntu, Debian
Posts: 734

Original Poster
Rep: Reputation: 30
I used to write help files and documents of how-to's for some big computer companies.

I'll be posting the complete how-to for everything involved including DRI in a short while....

Last edited by t3gah; 02-16-2005 at 12:47 AM.
 
Old 02-16-2005, 01:03 AM   #12
bobbens
Member
 
Registered: Sep 2004
Location: Barcelona
Distribution: Debian, FreeBSD, Gentoo
Posts: 586

Rep: Reputation: 30
Re: I used to write help files and documents of how-to's for some big computer compan

Quote:
Originally posted by t3gah
I used to write help files and documents of how-to's for some big computer companies.
No really? Maybe you should consider posting in the tutorials section for easier access (and not to mention stickiness), but you should make it more noobish if you want to post there (noobish howtos get attention). Well looks like you got it working (sorry haven't had time to read it at all). Good luck.
 
Old 02-17-2005, 12:47 PM   #13
perry
Member
 
Registered: Sep 2003
Location: USA & Canada
Distribution: Slackware 12.0
Posts: 978

Rep: Reputation: 30
Re: I used to write help files and documents of how-to's for some big computer companies.

Quote:
Originally posted by t3gah
I'll be posting the complete how-to for everything involved including DRI in a short while....
so i got myself a new system, cutting edge amd athlon 3000 and an ati 9600xt and a motherboard to promise 400 fsb plus a bunch of other niceities that i'll have to list here. question is, what is chances of being happy

or should have i gotten a nVidea

thanks

- perry\
 
Old 07-28-2005, 04:58 AM   #14
Geoffb
LQ Newbie
 
Registered: Aug 2004
Location: Cape Town, South Africa
Distribution: Fedora Core 4 (2.16.11.1-1369)
Posts: 12

Rep: Reputation: 0
t3gah

We seem to have very similar systems:

AMD Barton 3000+
1gig ram
K7N2 Delta nForce 2
ATI 9550XT

But i need your help badly. I've just spent the last 3 weeks searching and trying and searching and reading and trying to get 3d accelration working on my Fedora Core 4 (2.6.11-1.1369) box, but i still haven't managed to do it. And thats after reading just about every ati guide (rage3d,here, etc).

Could you please please explain to me how you managed to get it right?

My drivers seem to install properly, so i'm gessing it's a problem with my agp and dri not being modules. But i'm a total linux newbie and the kernel guides i have got don't really help me much.
 
Old 07-29-2005, 01:40 PM   #15
hashbrown
LQ Newbie
 
Registered: Jul 2005
Location: Vancouver BC
Distribution: Mandriva 2006
Posts: 28

Rep: Reputation: 15
If you're using ATI's drivers from their site, then ...

If it's only 3-d acceleration that's not working (what does is say in your X logs?), then most likely it's because the fglrx module is not kosher with your kernel version. Install the kernel-sources package matching your kernel (type uname -r to determine this) and then do the following:

Build the fglrx kernel module

1. cd /lib/modules/fglrx/build_mod
2. sh make.sh

Install the fglrx kernel module
3. cd /lib/modules/fglrx
4. sh make_install.sh

Cheers.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
3D acceleration ATI on suse 10.0 fdahl_009 Linux - Hardware 10 10-30-2005 11:42 AM
3D acceleration, ati mobility U1 microsoft/linux Debian 2 10-11-2005 05:41 PM
ATI 3D acceleration Mad Mardigan Linux - Hardware 1 10-10-2004 09:35 PM
ATI Radeon 3D acceleration White R4bbit Debian 17 11-18-2003 04:06 AM
I still can't use the ATI 3D acceleration with 2.6 kernel... moly82 Linux - Software 0 10-25-2003 07:59 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 09:45 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration