| View previous topic :: View next topic |
| Author |
Message |
mstreit
n00b
Joined: 10 May 2004
Posts: 7
|
 Posted: Mon May 10, 2004 9:01 pm Post subject: GLX / Grafikkarte / DRM Problem |
 |
|
Hallo!
Habe einige Probleme mit meiner Grafikkarte / 3d Beschleunigung.
Habe auch schon sämtliche Postings zu dem Thema durchgeforstet und vieles ausprobiert -> aber ohne wirklichen Erfolg.
Zu meinem System: Kernel 2.6.3
Hardware: Notebook Acer Travelmate 613TXV
1. Im X-Window bekomme ich graue Streifen in den Fensterrahmen (vorallem, wenn mehrere Programme geöffnet sind).
2. Start von Tuxracer liefert:
| Code: | Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
*** tuxracer error: Couldn't initialize video: Couldn't find matching GLX visual (Success) |
mein glxinfo output:
| Code: | Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual
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
----------------------------------------------------------------------
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
0x21 24 tc 1 0 0 c . . 0 0 0 0 0 0 0 0 0 0 0 0 0 None
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
0x22 24 dc 1 0 0 c . . 0 0 0 0 0 0 0 0 0 0 0 0 0 None |
der glxgears output:
| Code: | Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't get an RGB, Double-buffered visual |
Zum debuggen für euch meine /etc/X11/XF86Config:
| Code: | 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 "speedo"
# Load "freetype"
# Load "xtt"
# This loads the GLX module
# Load "glx"
# This loads the DRI module
# Load "dri"
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/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
# FontPath "/usr/X11R6/lib/X11/fonts/TrueType/"
# FontPath "/usr/X11R6/lib/X11/fonts/freefont/"
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><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# 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" "pc101"
Option "XkbLayout" "de"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ExplorerPS/2"
Option "Device" "/dev/mouse"
Option "ZAxisMapping" "4 5"
Option "Buttons" "5"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# 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 "My Monitor"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
HorizSync 31 - 65
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
VertRefresh 58-78
Option "NoDDC" "true"
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
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# Device configured by xf86config:
Section "Device"
Identifier "My Video Card"
Driver "i810"
# unsupported card
VideoRam 32768
# Insert Clocks lines here if appropriate
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 "Screen 1"
Device "My Video Card"
Monitor "My Monitor"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
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 "Simple 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. In this example, screen 2 is located to the
# right of screen 1.
Screen "Screen 1"
# 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
# Section "DRI"
# Mode 0666
# EndSection
|
Fallen jemanden grobe Schnitzer darin auf?
Hätte auch noch ein paar allgemeine Fragen.
Bei Grafikkarten, die den Nvidia Treiber verwenden ist ja OpenGL usw kein wirkliches Problem, was ich mitbekommen habe.
Aber was verwende ich mit meiner? Die im Kernel mitgelieferten Treiber?
Weiters wollte ich noch fragen, wie es jetzt mit dem DRM Support für den 2.6.* Kernel aussieht und wie man das Problem umgehen/lösen kann. Momentan habe ich DRM im Kernel reingetan.
Meine Grafikkarte laut lspci:
| Code: | | 00:02.0 VGA compatible controller: Intel Corp. 82815 CGC [Chipset Graphics Controller] (rev 11) |
Wäre für alle Hinweise bzw. Lösungsversuche sehr dankbar.
mfg
Marc |
|
| Back to top |
|
 |
Beforegod
Bodhisattva
Joined: 10 Apr 2002
Posts: 1495
Location: Würzburg
|
| Posted: Tue May 11, 2004 6:20 am Post subject: |
|
|
DRM im Kernel ist schonmal ein Guter Anfang.
Der Rest hätte Google oder ein kleines bisschen gesunder Menschenverstand lösen können.
| Quote: |
# This loads the GLX module
# Load "glx"
# This loads the DRI module
# Load "dri"
|
Nun rate mal wo hier der Fehler liegt???
Genau, so muss es aussehen :
| Quote: |
# This loads the GLX module
Load "glx"
# This loads the DRI module
Load "dri"
|
Zu Deiner Grafikkarte kann Dir das Forum (SUCHEN) oder Google bestimmt helfen. |
|
| Back to top |
|
|
mstreit
n00b
Joined: 10 May 2004
Posts: 7
|
| Posted: Tue May 11, 2004 8:54 am Post subject: |
|
|
Hallo,
erstmal danke für die Antwort.
Sowas blödes - wie konnt ich das nur übersehen.
Entschuldige...
Achja und die Grafikkarten Fehler hab ich auch lösen können.
Nachdem der Fehler GLX jetzt gefixed ist, gibt es neue.
Glxgears funktioniert nun auch, jedoch mit Error.
Output:
| Code: | Xlib: extension "XFree86-DRI" missing on display ":0.0".
|
Habe dazu auch ein paar Postings gefunden.
Aber die Lösungen darin beziehen sich alle auf Nvidia Karten/Treiber.
Wenigstens Tuxracer funktioniert.
Allerdings auch mit der gleichen Fehlerausgabe.
Ideen?
mfg Marc |
|
| Back to top |
|
|
mo-ca
Guru
Joined: 17 Feb 2003
Posts: 313
Location: Near Dresden, Germany
|
|
| Back to top |
|
|
mstreit
n00b
Joined: 10 May 2004
Posts: 7
|
| Posted: Tue May 11, 2004 9:29 am Post subject: |
|
|
xfree-drm emergen funktioniert nicht, weil ich den 2.6er Kernel verwende.
| Code: | !!! ERROR: x11-base/xfree-drm-4.3.0-r7 failed.
!!! Function pkg_setup, Line 71, Exitcode 0
!!! Please link /usr/src/linux to 2.4 kernel sources. xfree-drm does not yet work with 2.6 kernels, use the DRM in the kernel. |
Aber wie gesagt ist DRM im Kernel aktiviert. |
|
| Back to top |
|
|
Beforegod
Bodhisattva
Joined: 10 Apr 2002
Posts: 1495
Location: Würzburg
|
| Posted: Tue May 11, 2004 10:35 am Post subject: |
|
|
| Quote: |
# Section "DRI"
# Mode 0666
# EndSection
|
Hab ich gepennt 
| Quote: |
Section "DRI"
Mode 0666
EndSection
|
|
|
| Back to top |
|
|
mstreit
n00b
Joined: 10 May 2004
Posts: 7
|
| Posted: Tue May 11, 2004 10:48 am Post subject: |
|
|
Das ist mir mittlerweile auch schon aufgefallen  Habs also auskommentiert.
Aber hat nichts am Problem geändert.
Glxgears liefert mir auch ein sehr mieses FPS Ergebnis:
| Code: | bash-2.05b$ glxgears
Xlib: extension "XFree86-DRI" missing on display ":0.0".
581 frames in 5.0 seconds = 116.200 FPS
567 frames in 5.0 seconds = 113.400 FPS
567 frames in 5.0 seconds = 113.400 FPS
|
Folglich läuft Tuxracer auch in very slow motion  |
|
| Back to top |
|
|
Beforegod
Bodhisattva
Joined: 10 Apr 2002
Posts: 1495
Location: Würzburg
|
| Posted: Tue May 11, 2004 11:01 am Post subject: |
|
|
Mal ne saublöde frage aber das Load "Dri" steht ja drinnne gelle
Hast Du auch das Passende Kernel Modul für Deine GraKa eingestellt?
Mach mal ein lsmod und poste die Ausgabe hier (falls Du das DRM Teil als Modul geladen hast). |
|
| Back to top |
|
|
mstreit
n00b
Joined: 10 May 2004
Posts: 7
|
| Posted: Tue May 11, 2004 11:25 am Post subject: |
|
|
| Quote: | | Mal ne saublöde frage aber das Load "Dri" steht ja drinnne gelle |
Jap, is drin
| Quote: | | Hast Du auch das Passende Kernel Modul für Deine GraKa eingestellt? |
Also im Kernel unter Character devices hab ich folgendes aktiviert:
| Code: |
<*> /dev/agpgart (AGP Support)
<*> Intel 440LX/BX/GX, I8xx and E7x05 chipset support
[*] Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
<*> Intel I810
<*> Intel 830M, 845G, 852GM, 855GM, 865
|
Danke, für deine Hilfe! |
|
| Back to top |
|
|
mstreit
n00b
Joined: 10 May 2004
Posts: 7
|
| Posted: Tue May 11, 2004 11:40 am Post subject: |
|
|
AHA, ich hab vorher mal die Farben auf 24 bit gesetzt.
Jetzt mit 16 bit funktionierts - der Fehler ist weg.
glxgears ist auch besser geworden:
| Code: | 1053 frames in 5.0 seconds = 210.600 FPS
1053 frames in 5.0 seconds = 210.600 FPS
972 frames in 5.0 seconds = 194.400 FPS
1053 frames in 5.0 seconds = 210.600 FPS
1053 frames in 5.0 seconds = 210.600 FPS
|
Aber zB Tuxracer ist noch immer unspielbar, weil einfach vieeel zu langsam.
Ist das etwa schon das Maximum, das ich von meiner i810 Karte erwarten kann? |
|
| Back to top |
|
|
Beforegod
Bodhisattva
Joined: 10 Apr 2002
Posts: 1495
Location: Würzburg
|
| Posted: Tue May 11, 2004 1:48 pm Post subject: |
|
|
nicht wirklich gut, aber schonmal ein Fortschritt.
Hätte gesagt das Du die DRM Module eben als Module einbindest und nich fest in den Kernel reinsteckst. Evt hilft auch ein Update auf xorg-x11 (was eigene DRM Treiber mitbringt). Versuch auch mal einen neuen Kernel und poste danach nochmal Dein Ergebnis hier. |
|
| Back to top |
|
|
|
Deutsches Forum (German)
