Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 83001 (ati-mesa) - x11-drivers/ati-drivers - no HW acceleration in games
Summary: x11-drivers/ati-drivers - no HW acceleration in games
Status: RESOLVED TEST-REQUEST
Alias: ati-mesa
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Games (show other bugs)
Hardware: AMD64 Linux
: High normal
Assignee: X11 External Driver Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-22 13:38 UTC by Standa
Modified: 2007-04-01 21:05 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
what happens after: ACCEPT_KEYWORDS="~amd64" emerge ati-drivers (ati,6.82 KB, text/plain)
2005-02-22 14:35 UTC, Standa
Details
#emerge info (emerge_info,1.70 KB, text/plain)
2005-02-22 15:31 UTC, Standa
Details
LIBGL_DEBUG=verbose ./glxinfo (glxinfo.txt,8.24 KB, text/plain)
2005-03-22 16:31 UTC, Standa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Standa 2005-02-22 13:38:22 UTC
I installed ATI drivers 8.10.19. All works, fglrxinfo says i have ATI, glxgears shows 4600FPS aso., as good as in 32bit Gentoo, but, no game can use HW acceleration. All games use MESA (Unreal-Tournament, Quake3). To switch 'opengl-update ati' i used opengl-update-2.1.1-r1. It's like no games know i have installed ATI and continue using something else.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.



Expected Results:  
Instead of using MESA the games must use ATI drivers.
Comment 1 Chris Gianelloni (RETIRED) gentoo-dev 2005-02-22 13:50:50 UTC
Try "opengl-update xorg-x11 && opengl-update ati" and see if it helps.  Anyway, the problem sounds more to be from your configuration than the games themselves.  Since you provided no game names, there's not much we can do about it.

Check out http://www.gentoo.org/proj/en/desktop/games/ for more information on filing games bugs.
Comment 2 Standa 2005-02-22 14:12:50 UTC
i installed all without any error, this is what i get:

glxinfo | grep direct direct rendering: Yes

$fglrxinfo

display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9800 Pro Generic
OpenGL version string: 1.3.4893 (X4.3.0-8.10.19)

glxgears: 4600FPS

but when running Unreal-Tournament: ut i get in log:

OpenGL
GL_VENDOR     : Mesa project: www.mesa3d.org
GL_RENDERER   : Mesa GLX Indirect
GL_VERSION    : 1.2 (1.5 Mesa 6.1)

when i run Quake3 i get:

...loading libGL.so.1: Initializing OpenGL display
...setting mode 6: 1024 768
Using XFree86-VidModeExtension Version 2.2
XFree86-VidModeExtension Activated at 1024x768
Using 4/4/4 Color bits, 16 depth, 0 stencil display.
GL_RENDERER: Mesa GLX Indirect


***********************************************************
 You are using software Mesa (no hardware acceleration)!
 Driver DLL used: libGL.so.1
 If this is intentional, add
       "+set r_allowSoftwareGL 1"
 to the command line when starting the game.
***********************************************************

my xorg is 6.8.0 and xorg.conf is same as i see reporting on forums, made by ATI binary /opt/ati/bin/.... All works well, just i need to tell the games i have ATI. I tried your: opengl-update xorg-x11 && opengl-update ati, it changed to xorg then to ati, but nothing happend to games. Even reboot dont make it to work :(. I reinstalled whole ATI-DRIVERS, still the same problem, here is my xorg.conf:

# **********************************************************************
# 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	"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"   "ImPS/2"
    Option "ZAxisMapping"   "4 5"
    Option "Device"     "/dev/input/mice"

# 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 - 85
    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"                 "0"
    Option "BlockSignalsOnLock"         "on"
    Option "UseInternalAGPGART"         "no"
    Option "ForceGenericCPU"            "no"
    BusID "PCI:1:0:0"    # vendor=1002, device=4e48
    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       "1280x1024"
        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 ###
Comment 3 Chris Gianelloni (RETIRED) gentoo-dev 2005-02-22 14:22:54 UTC
Post your emerge info and don't post huge things like your xorg.conf, since it is pretty much useless to us and makes for a large email... ;]

If you need to attach something like xorg.conf, make it an attachment, don't post it inline...

What version of xorg-x11 ebuild are you running?

There is certain information that *must* be in a bug, or we can't do anything.
Comment 4 Standa 2005-02-22 14:35:07 UTC
Created attachment 51905 [details]
what happens after: ACCEPT_KEYWORDS="~amd64" emerge ati-drivers
Comment 5 Standa 2005-02-22 15:00:32 UTC
sorry for my long xorg.conf, now i know how to attach files, so i attached log of emerge ati-drivers. My xorg-x11 is 6.8.0-r4.
Comment 6 Chris Gianelloni (RETIRED) gentoo-dev 2005-02-22 15:02:12 UTC
Post emerge info (no need to attach that) please
Comment 7 Standa 2005-02-22 15:08:50 UTC
I hope you want to see this, in not, please tell me where or how to get info you need to help me. Btw: many thanks for trying me to help and i'm sorry about my faults and english.

1109111487: Started emerge on: Feb 22, 2005 23:31:27
1109111487:  *** emerge  ati-drivers
1109111487:  >>> emerge (1 of 1) media-video/ati-drivers-8.10.19 to /
1109111487:  === (1 of 1) Cleaning (media-video/ati-drivers-8.10.19::/usr/portage/media-video/ati-drivers/ati-drivers-8.10.19.ebuild)
1109111488:  === (1 of 1) Compiling/Merging (media-video/ati-drivers-8.10.19::/usr/portage/media-video/ati-drivers/ati-drivers-8.10.19.ebuild)
1109111540:  === (1 of 1) Post-Build Cleaning (media-video/ati-drivers-8.10.19::/usr/portage/media-video/ati-drivers/ati-drivers-8.10.19.ebuild)
1109111544:  >>> AUTOCLEAN: media-video/ati-drivers
1109111544:  --- AUTOCLEAN: Nothing unmerged.
1109111544:  ::: completed emerge (1 of 1) media-video/ati-drivers-8.10.19 to /
1109111544:  *** Finished. Cleaning up...
1109111547:  *** exiting successfully.
1109111547:  *** terminating.
Comment 8 Chris Gianelloni (RETIRED) gentoo-dev 2005-02-22 15:23:57 UTC
type "emerge info"
Comment 9 Standa 2005-02-22 15:31:18 UTC
Created attachment 51908 [details]
#emerge info
Comment 10 SpanKY gentoo-dev 2005-02-22 21:44:59 UTC
does this only happen with 32bit games ?  sounds like multilib bug ...
Comment 11 Standa 2005-02-23 00:31:38 UTC
Sorry, i'm not so experienced user to tell if i have only 32bit games, but i emerged this:

emerge unreal-tournament
emerge quake3
emerge tuxracer
emerge chromium

all emerged correctly, without any error (ut and quake3 needed original CD) but all games has same problem: runs like without acceleration. If you tell me, which game is 64bit or how to try, i will try to install and report. But remember, i'm not too experienced, so please be specific what to do.
Comment 12 the.max 2005-03-08 10:04:12 UTC
I have exactly the same problem, ATI works, but there is no working acceleration in games and programs.

Don't work any OpenGL screen savers

tested in enemy territory and tuxracer
Comment 13 SpanKY gentoo-dev 2005-03-12 10:53:24 UTC
maybe a permissions bug ... do games work correctly when run as root ?
Comment 14 Donnie Berkholz (RETIRED) gentoo-dev 2005-03-12 13:06:37 UTC
Attach the output of `LIBGL_DEBUG=verbose glxinfo` and reopen, please
Comment 15 the.max 2005-03-21 01:36:44 UTC
name of display: :0.0
libGL error: XF86DRIQueryDirectRenderingCapable returned false
libGL error: XF86DRIQueryDirectRenderingCapable returned false
display: :0  screen: 0
direct rendering: No
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
    GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating,
    GLX_EXT_import_context, GLX_OML_swap_method, GLX_SGI_make_current_read,
    GLX_SGIS_multisample, GLX_SGIX_fbconfig
client glx vendor string: ATI
client glx version string: 1.3
client glx extensions:
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context,
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_ATI_pixel_format_float,
    GLX_ATI_render_texture
GLX extensions:
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context,
    GLX_ARB_multisample
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)
OpenGL extensions:
    GL_ARB_imaging, GL_ARB_multitexture, GL_ARB_texture_border_clamp,
    GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
    GL_ARB_texture_env_combine, GL_ARB_texture_env_dot3,
    GL_ARB_transpose_matrix, GL_EXT_abgr, GL_EXT_blend_color,
    GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_texture_env_add,
    GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3,
    GL_EXT_texture_lod_bias
glu version: 1.3
glu extensions:
    GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess

   visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
 id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------
0x23 24 tc  0 24  0 r  y  .  8  8  8  0  0 16  0  0  0  0  0  1 0 None
0x24 24 tc  0 24  0 r  y  .  8  8  8  0  0 16  8 16 16 16  0  1 0 None
0x25 24 tc  0 32  0 r  y  .  8  8  8  8  0 16  8 16 16 16 16  1 0 None
0x26 24 tc  0 32  0 r  .  .  8  8  8  8  0 16  8 16 16 16 16  1 0 None
0x27 24 dc  0 24  0 r  y  .  8  8  8  0  0 16  0  0  0  0  0  1 0 None
0x28 24 dc  0 24  0 r  y  .  8  8  8  0  0 16  8 16 16 16  0  1 0 None
0x29 24 dc  0 32  0 r  y  .  8  8  8  8  0 16  8 16 16 16 16  1 0 None
0x2a 24 dc  0 32  0 r  .  .  8  8  8  8  0 16  8 16 16 16 16  1 0 None
Comment 16 Donnie Berkholz (RETIRED) gentoo-dev 2005-03-21 02:36:47 UTC
the.max, you have a different problem. Note how your glxinfo returns no on direct rendering, although the reporter's returned yes. You probably have misconfigured something -- grep your X log for EE and WW to debug it.
Comment 17 Bryan Stine (RETIRED) gentoo-dev 2005-03-21 04:45:04 UTC
Donnie - I believe this is what that pair of patches to DRI and DRM posted to the dri-devel ML a few months ago was supposed to help fix. Currently, 32-bit client programs cannot use direct rendering on a 64-bit X server. The patch I'm referring to was incomplete, though, and very unstable on my amd64 box.

https://bugs.freedesktop.org/show_bug.cgi?id=943
Comment 18 Donnie Berkholz (RETIRED) gentoo-dev 2005-03-21 10:41:08 UTC
Bryan -- hmm not likely, this is ati-drivers, and it should work with them if things are set up properly. If reporter were using X's ati driver, that would make sense.
Comment 19 Joshua Baergen (RETIRED) gentoo-dev 2005-03-21 21:23:59 UTC
I've seen similar behaviour on my friend's x86 laptop w/ ATI 9700 and ATI's latest drivers.  He's currently looking for a solution and come up dry...I'll see if he gets anywhere, it may be related.
Comment 20 Standa 2005-03-22 16:31:08 UTC
Created attachment 54194 [details]
LIBGL_DEBUG=verbose ./glxinfo 

Here is what i've been asked. I hope it will help to solve something. I still
haven't found something helping me.

Thanks for help, Standa
Comment 21 Standa 2005-03-22 16:32:37 UTC
I reopen this BUG, because i sended attachment as i was asked. Standa
Comment 22 Standa 2005-03-30 14:16:59 UTC
This is what i get full xterm while i'm running TUXRACER:

__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!
FGLTexMgr: open of shared memory object failed (Function not implemented)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!
FGLTexMgr: open of shared memory object failed (Function not implemented)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!

Does it helps? Standa
Comment 23 Donnie Berkholz (RETIRED) gentoo-dev 2005-03-31 11:52:39 UTC
Yeah, it tells me that you didn't read the release notes.

http://www2.ati.com/drivers/linux/linux_8.10.19.html

Read this section:  3D Applications Produce Open of Shared Memory Object Failed Error Message
Comment 24 Standa 2005-04-09 00:46:10 UTC
Hello, i repaired TMPFS, i put it in kernel and all games i can compile are running great, they are accelerated, i mean games like: tuxracer, chromium.

But games, NOT compiled, like Unreal, Quake3 has still the same error, they are still telling me i haven't acceleration a i need to use software acceler., but it's about 2FPS :(.

Standa
Comment 25 Luca Barbato gentoo-dev 2005-04-26 01:25:38 UTC
silly question, do you have the multilib support on, and the required 32bit files in place? (in lib32 I think)
Comment 26 Standa 2005-06-28 13:11:18 UTC
I don't know how to check if multilib is working, but i reinstalled whole Gentoo and i 
got the same problem :(. It's pretty annoying, Quake3 is still not running, while 
whole compiled system uses acceleration great.

Please help me, or i will need to switch to other disto. Standa
Comment 27 SpanKY gentoo-dev 2005-06-28 17:11:50 UTC
the threat that we 'better fix this bug right now or a user is going to switch
distros' is pretty ridiculous
Comment 28 Standa 2005-06-29 08:26:41 UTC
I tried this:
emerge -pv gcc and i got:
These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild   R   ] sys-devel/gcc-3.4.3-r1  (-altivec) -bootstrap -boundschecking -
build +fortran* -gcj +gtk* -hardened -ip28 (-multilib) -multislot (-n32) (-n64) 
+nls -nocxx -nopie -nossp -objc -static 27,754 kB

Total size of downloads: 27,754 kB

I find in many discusions that i need multilib for playing, but some say, i 
don't. What is correct? And how will i enable multilib, USE="multilib" is not 
working.

Can somebody help? Thanks, Standa

p.s. i love Gentoo, it's the best i found, but if there is no way how to enable 
other family members to play games, what can i do? Use Windows as Daniel 
Robbins? No thanks...
Comment 29 giovanni.bobbio 2005-12-21 03:50:10 UTC
(In reply to comment #23)
> Yeah, it tells me that you didn't read the release notes.
> 
> http://www2.ati.com/drivers/linux/linux_8.10.19.html
> 
> Read this section:  3D Applications Produce Open of Shared Memory Object Failed Error Message

I just found that I am affected by this misconfiguration and read the release notes. They say I should create this fstab entry:
tmpfs /dev/shm tmpfs defaults 0 0

Problem is I already have in my /etc/fstab:
shm   /dev/shm tmpfs nodev,nosuid,noexec 0 0

Am I really supposed to mount two different devices on the same mount point?
Comment 30 Jakub Moc (RETIRED) gentoo-dev 2007-04-01 21:05:41 UTC
Nothing to write home about for 15 months; reopen if current x11-drivers/ati-drivers versions have this problem.