View previous topic :: View next topic |
Author |
Message |
AnonNomis n00b
Joined: 18 Apr 2002 Posts: 28
|
Posted: Thu Jul 11, 2002 5:55 am Post subject: opengl problems |
|
|
I keep getting this error when i try to run opengl games. Im using nvidia drivers. Does anyone know what this means?
SDL initialized.
Couldn't set GL mode: X11 driver not configured with OpenGL
Curiosity caused me to try running games as root. It ended up giving me a different error as root. Do opengl games require you to install directfb and to enable the frame buffer in the kernel? Thanks for the help.
Tux Racer 0.61 -- a Sunspire Studios Production (http://www.sunspirestudios.com)
(c) 1999-2000 Jasmin F. Patry <jfpatry@sunspirestudios.com>
"Tux Racer" is a trademark of Jasmin F. Patry
Tux Racer comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to redistribute it under certain conditions.
See http://www.gnu.org/copyleft/gpl.html for details.
---------------------- DirectFB v0.9.12 ---------------------
(c) 2000-2002 convergence integrated media GmbH
(c) 2002 convergence GmbH
-----------------------------------------------------------
(*) Single Application Core. (2002-07-11 02:42)
(*) DirectFB/misc/memcpy: using linux kernel memcpy()
(*) DirectFB/InputDevice: IMPS/2 Mouse 0.9 (convergence integrated media GmbH)
(*) DirectFB/InputDevice: Keyboard 0.9 (convergence integrated media GmbH)
(!) DirectFB/core/fbdev: Couldn't open neither `/dev/fb0' nor `/dev/fb/0'!
--> No such file or directory
(!) DirectFB/Core: Error during initialization: dfb_fbdev_initialize()
Segmentation fault |
|
Back to top |
|
|
Swishy Guru
Joined: 06 Jun 2002 Posts: 491 Location: NZ
|
Posted: Thu Jul 11, 2002 2:06 pm Post subject: |
|
|
What does your X86config look like??? _________________ Theres no substitute for C.I. |
|
Back to top |
|
|
AnonNomis n00b
Joined: 18 Apr 2002 Posts: 28
|
Posted: Thu Jul 11, 2002 10:45 pm Post subject: |
|
|
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"
EndSection
Section "ServerFlags"
EndSection
Section "InputDevice"
Identifier "Keyboard1"
Driver "Keyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "itouch"
Option "XkbLayout" "us"
Option "XkbVariant" "us"
EndSection
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/mouse"
Option "ZAxisMapping" "4 5"
EndSection
Section "Monitor"
Identifier "ViewSonic"
# 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 60-100
# 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 50-100
EndSection
# 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 "asus"
Driver "nvidia"
#VideoRam 256
# Insert Clocks lines here if appropriate
EndSection
Section "Screen"
Identifier "Screen 1"
Device "asus"
Monitor "ViewSonic"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
Section "ServerLayout"
Identifier "Simple Layout"
Screen "Screen 1"
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection |
|
Back to top |
|
|
tomas n00b
Joined: 05 Jul 2002 Posts: 62 Location: Sweden
|
Posted: Thu Jul 11, 2002 10:57 pm Post subject: |
|
|
Try running opengl-update nvidia. |
|
Back to top |
|
|
AnonNomis n00b
Joined: 18 Apr 2002 Posts: 28
|
Posted: Fri Jul 12, 2002 7:33 am Post subject: |
|
|
Ya i've tried that. |
|
Back to top |
|
|
ASCI Blue Tux's lil' helper
Joined: 07 May 2002 Posts: 132
|
Posted: Fri Jul 12, 2002 6:04 pm Post subject: |
|
|
I'm not familiar with nVidia cards but does one need the DRI section for them? |
|
Back to top |
|
|
Zu` l33t
Joined: 26 May 2002 Posts: 716 Location: BE
|
Posted: Fri Jul 12, 2002 10:44 pm Post subject: |
|
|
ASCI Blue wrote: | I'm not familiar with nVidia cards but does one need the DRI section for them? |
No.
If you load glx, you don't need to load dri. Even more, X will prompt an error if you do so.
So this is enough in your XF86Config:
Code: |
# This loads the GLX module
Load "glx"
|
I see your XF86Config isn't made with
So if GLX still doesn't work, you could try that to make a working XF86Config.
Good luck |
|
Back to top |
|
|
FINITE Guru
Joined: 10 May 2002 Posts: 449
|
Posted: Fri Jul 12, 2002 11:22 pm Post subject: |
|
|
I was going to reccomend what zu did. Rename you existing config file and then run XF86Config and create a new config file with it. Should work fine. |
|
Back to top |
|
|
AnonNomis n00b
Joined: 18 Apr 2002 Posts: 28
|
Posted: Sat Jul 13, 2002 12:52 am Post subject: |
|
|
Ran X -configure it gave me a file in which the only noticable changes were
Load "extmod"
Load "record"
Load "xtrap"
Load "speedo"
Load "xie"
Load "pex5"
Im not sure which one did it but one actually caused me kernel panics when switching back to runlevel 3. I still got the same error, "Couldn't initialize video: X11 driver not configured with OpenGL (Success)"
thanks again |
|
Back to top |
|
|
AnonNomis n00b
Joined: 18 Apr 2002 Posts: 28
|
Posted: Sat Jul 13, 2002 10:29 am Post subject: |
|
|
Do games like gltron, chromium, and tuxracer require you to have DirectFB installed? I'm guessing it does because when i run gltron after doing a "su -" i get....
(!) DirectFB/core/fbdev: Couldn't open neither `/dev/fb0' nor `/dev/fb/0'!
--> No such file or directory
When i run gltron after "su" my screen goes blank and X crashes. I telneted into my system and did a dmesg and found that VesaFB could not load the video.
Is this because these games change the resolution and refresh rate? I saw in the VesaFB documentation that it isn't capable of changing refresh rates. I'm guessing that VesaFB is my problem, and that I should use the NvidiaFB. The only problem I have with that is that the NvidiaFB caused a kernel panic before, and that is why I resorted to VesaFB in the first place. Is there another option here. Could xdirectfb possibly be the answer? |
|
Back to top |
|
|
|