Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Problems with OpenGl
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
Tummy
n00b
n00b


Joined: 09 Jun 2004
Posts: 11
Location: Germany, K-Town

PostPosted: Wed Jun 09, 2004 4:15 pm    Post subject: Problems with OpenGl Reply with quote

Hi sorry to bother you people
Got problems getting OpenGL to run under xorg

got a Radeon 9700 card with an nForce2 ASUS A7N8X Deluxe Board
running kernel-2.4.25
fxgrl is loaded as a module, so is agpgart

im using external AGPART
emerged ati-drivers and did run opengl-udate ati

but fxgrlinfo says im still running mesa3d

Xorg.0.log gives me:
(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_ENOMEM"
(EE) fglrx(0): cannot init AGP

i dont know what i still can do :(

hope somebody can help me

greetz tummy
Back to top
View user's profile Send private message
really
Guru
Guru


Joined: 27 Aug 2002
Posts: 430
Location: nowhere

PostPosted: Wed Jun 09, 2004 6:01 pm    Post subject: Re: Problems with OpenGl Reply with quote

Tummy wrote:
Hi sorry to bother you people
Got problems getting OpenGL to run under xorg

got a Radeon 9700 card with an nForce2 ASUS A7N8X Deluxe Board
running kernel-2.4.25
fxgrl is loaded as a module, so is agpgart

im using external AGPART
emerged ati-drivers and did run opengl-udate ati

but fxgrlinfo says im still running mesa3d

Xorg.0.log gives me:
(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_ENOMEM"
(EE) fglrx(0): cannot init AGP

i dont know what i still can do :(

hope somebody can help me

greetz tummy
hm.. first upgrade to 2.4.26 ;)
then try opengl-update
_________________
NoManNoProblem

Get lost before you get shot.
Back to top
View user's profile Send private message
Wedge_
Advocate
Advocate


Joined: 08 Aug 2002
Posts: 3614
Location: Scotland

PostPosted: Wed Jun 09, 2004 6:18 pm    Post subject: Reply with quote

Try increasing your AGP aperture size (in the BIOS) to 128MB.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ
Back to top
View user's profile Send private message
really
Guru
Guru


Joined: 27 Aug 2002
Posts: 430
Location: nowhere

PostPosted: Wed Jun 09, 2004 6:27 pm    Post subject: Reply with quote

Oh yea, dont forget to compile in support for agp, agpgart in your kernel.
_________________
NoManNoProblem

Get lost before you get shot.
Back to top
View user's profile Send private message
Tummy
n00b
n00b


Joined: 09 Jun 2004
Posts: 11
Location: Germany, K-Town

PostPosted: Wed Jun 09, 2004 8:42 pm    Post subject: Reply with quote

Icreased it already to maximum

still not working :(

mfG Tummy
Back to top
View user's profile Send private message
really
Guru
Guru


Joined: 27 Aug 2002
Posts: 430
Location: nowhere

PostPosted: Wed Jun 09, 2004 9:14 pm    Post subject: Reply with quote

try having agpgart in kernel, not as module?
_________________
NoManNoProblem

Get lost before you get shot.
Back to top
View user's profile Send private message
Tummy
n00b
n00b


Joined: 09 Jun 2004
Posts: 11
Location: Germany, K-Town

PostPosted: Fri Jun 11, 2004 12:01 pm    Post subject: Reply with quote

Still not working im thinking about going tokernel 2.6 does it look better there??

mfg Tummy
Back to top
View user's profile Send private message
Tummy
n00b
n00b


Joined: 09 Jun 2004
Posts: 11
Location: Germany, K-Town

PostPosted: Sat Jun 12, 2004 1:13 pm    Post subject: Reply with quote

no more ideas left.
What about the drivers from ati.com are there neweer versions than in the portage tree??
anyone got experience with installing them?

mfg Tummy
Back to top
View user's profile Send private message
really
Guru
Guru


Joined: 27 Aug 2002
Posts: 430
Location: nowhere

PostPosted: Sat Jun 12, 2004 6:20 pm    Post subject: Reply with quote

Tummy wrote:
no more ideas left.
What about the drivers from ati.com are there neweer versions than in the portage tree??
anyone got experience with installing them?

mfg Tummy
how does your XF86Config file look?
_________________
NoManNoProblem

Get lost before you get shot.
Back to top
View user's profile Send private message
Tummy
n00b
n00b


Joined: 09 Jun 2004
Posts: 11
Location: Germany, K-Town

PostPosted: Sun Jun 13, 2004 9:27 pm    Post subject: Reply with quote

# **********************************************************************
# 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" "xorg"
Option "XkbModel" "pc101"
Option "XkbLayout" "de"

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-91
VertRefresh 60-150
Option "DPMS"
# **********************************************************************
# 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" "no"
Option "TVStandard" "PAL-B"
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" "yes"
Option "FSAAScale" "6"
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" "yes"
Option "ForceGenericCPU" "no"
BusID "PCI:2:0:0" # vendor=1002, device=4e44
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 ###
Back to top
View user's profile Send private message
Toris
n00b
n00b


Joined: 22 Mar 2004
Posts: 58

PostPosted: Sun Jun 13, 2004 9:41 pm    Post subject: Reply with quote

Hmm, I'm not sure, but under XOrg, glxinfo always shows me using a Mesa renderer, even when I seem to get reasonably good performance with glxgears (1400fps on a 9200). And games work fine. So, either it just doesn't display the renderer properly, or mine isn't setup properly either :)
I'm using the inbuilt graphics kernel module however, not fglx (had problems with crashing when scrolling with the official ati drivers).
Back to top
View user's profile Send private message
Tummy
n00b
n00b


Joined: 09 Jun 2004
Posts: 11
Location: Germany, K-Town

PostPosted: Sun Jun 13, 2004 9:49 pm    Post subject: Reply with quote

Nope not in my case got only 100fps with glxgears and games dont work
(NWN breaks with "failed to initialize graphics")

mfG Tummy
Back to top
View user's profile Send private message
drutten
Tux's lil' helper
Tux's lil' helper


Joined: 31 Dec 2003
Posts: 103
Location: Sweden

PostPosted: Sun Jun 13, 2004 10:09 pm    Post subject: Reply with quote

I had a problem getting my gfx card to run in xfree for a long time.
But when I switched to 2.6 i got it to work.
Later on I found out that agp 8x probably was the problem, 2.4 kernels don't support 8x agp very well. I think you should either lower it to 4x in BIOS or upgrade to 2.6
Hope it will work out for you.
Back to top
View user's profile Send private message
Tummy
n00b
n00b


Joined: 09 Jun 2004
Posts: 11
Location: Germany, K-Town

PostPosted: Sun Jun 13, 2004 10:25 pm    Post subject: Reply with quote

diabled AGP 8X but nothing changed :(
mfg Tummy
Back to top
View user's profile Send private message
drutten
Tux's lil' helper
Tux's lil' helper


Joined: 31 Dec 2003
Posts: 103
Location: Sweden

PostPosted: Sun Jun 13, 2004 10:29 pm    Post subject: Reply with quote

Would it be much trouble to upgrade to 2.6?
I don't see why you should not do it, but maybe you have a reason.
Back to top
View user's profile Send private message
Tummy
n00b
n00b


Joined: 09 Jun 2004
Posts: 11
Location: Germany, K-Town

PostPosted: Sun Jun 13, 2004 10:35 pm    Post subject: Reply with quote

Main Reason for the moment is, that i dont exactly know how to do it ;)
but im trying to learn. will try to attack that tomorrow.

mfG tummy
Back to top
View user's profile Send private message
Tummy
n00b
n00b


Joined: 09 Jun 2004
Posts: 11
Location: Germany, K-Town

PostPosted: Mon Jun 14, 2004 7:27 pm    Post subject: Reply with quote

Can anyone see at the xorg.conf what could be wrong??

mfG Tummy
Back to top
View user's profile Send private message
Tummy
n00b
n00b


Joined: 09 Jun 2004
Posts: 11
Location: Germany, K-Town

PostPosted: Mon Jun 14, 2004 8:36 pm    Post subject: Reply with quote

Gr8 running Kernel 2.6.6 now.
But still the same Problem, same Error Message in xorg.0.log.
Any Ideas left?
Back to top
View user's profile Send private message
guitou
Guru
Guru


Joined: 02 Oct 2003
Posts: 534
Location: France

PostPosted: Mon Jun 14, 2004 11:33 pm    Post subject: Reply with quote

Might be a silly question, but did you enable MTRR in your kernel config ?
Back to top
View user's profile Send private message
Tummy
n00b
n00b


Joined: 09 Jun 2004
Posts: 11
Location: Germany, K-Town

PostPosted: Mon Jun 14, 2004 11:42 pm    Post subject: Reply with quote

yep its enabled (not as module)
mfg tummy
Back to top
View user's profile Send private message
madmango
Guru
Guru


Joined: 15 Jul 2003
Posts: 507
Location: PA, USA

PostPosted: Sat Jun 19, 2004 8:47 pm    Post subject: Reply with quote

I'm having the same problem using a 2.6 kernel.

I had it working really easy. Then it stopped. For no reason. I didn't even change a config file.
_________________
word.
Back to top
View user's profile Send private message
Wedge_
Advocate
Advocate


Joined: 08 Aug 2002
Posts: 3614
Location: Scotland

PostPosted: Sat Jun 19, 2004 9:00 pm    Post subject: Reply with quote

Try changing the "UseInternalAGPGART" setting to "no". This means the driver should use the (generally more reliable) kernel AGP support rather than it's own. The ENOMEM error often appears when you try to use the drivers AGP support.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum