murankar
Game Owner
 NWN
NWN: SoU
NWN: HotU
Suscrito: 24 feb 2005 |
 Colgado: sábado, 22 octubre 2005 12:10 |
i just read the red hat 8.0 stuff. Then i remembered that i forgot my system info. i am currently on slack 10.2. So i have the most current kernel and close to currant modules. I have yet to run and driver mods at this point until i get some help on the glx issue. Slackware 10.2 does not use the XF86config file it uses the Xorg.conf file. will the rpm for RH8.0 still work?
i am going to check out any forums for slack. |
|
KristonFincher
Game Owner
 NWN
NWN: SoU
NWN: HotU
Suscrito: 28 mar 2003 |
Colgado: sábado, 22 octubre 2005 07:41 |
I have found that the nVidia run file is much easier for the first time users. If you use RPM and are comfortable with it the RH8.0 instructions should work for you just fine, but I usually just get the latest run package from nvidia.com. Since you use the slack distro, I will assume that you do not usually run RPM.
Change to init mode 3 (/sbin/init 3) and log in as root. Run NVIDIA-xxx-.run and follow the instructions (usually just hit <ENTER>). When it is finished, edit /etc/X11/xorg.conf and remove the load lines for "dir" and "GLcore" if they exist. Change the driver line from "nv" to "nvidia". Exit the editor.
Run X to make sure that it works correctly. You should see the nVidia splash screen for a second or two, the the X crosshatch. If this works correctly, press <CTRL><ALT><BACKSPACE> to exit. You may now go back to init mode 5 if you were using it, or whatever you normally used for running X. If you have any problems, read the README before continuing. I have found many solutions in there, such as the selinux bug with nVidia drivers.
Run "glxinfo". You should see "server glx vendor string: NVIDIA Corporation" near the top. glxinfo will run on the original X installation as well. If it runs, you have some form of glx installed, since glx is the extension to X that allows OpenGL rendering.
_________________
All Windows problems are hardware problems.
Don't load it on hardware, you have no problems. |
|
|
murankar
Game Owner
NWN
NWN: SoU
NWN: HotU
Suscrito: 24 feb 2005 |
Colgado: martes, 25 octubre 2005 08:22 |
her are printouts from my attemp to install the drivers.
i ran xorgconfig to get these settings. also the card i have is a pci card.
GLXGEARS
root@desktop:~# glxgears
Xlib: extension "GLX" missing on display ":0.0".
glxgears: Error: couldn't get an RGB, Double-buffered visual.
root@desktop:~#
root@desktop:~# glxinfo
name of display: :0.0
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
Segmentation fault
# 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 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
skip a few lines
#
# 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 xorgconfig:
Section "Device"
Identifier "nvidia"
Driver "nv"
#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 "nvidia"
Monitor "compaq"
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
#
# 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 |
|
|
TjaBBe
Game Owner
 NWN
NWN: SoU
NWN: HotU
NWN 2
Suscrito: 04 sep 2002
De: The Netherlands |
Colgado: viernes, 28 octubre 2005 10:07 |
Quote: Posted 10/25/05 20:22:56 (GMT) by murankar
Section "Device"
Identifier "nvidia"
Driver "nv"
#VideoRam 32768
# Insert Clocks lines here if appropriate
EndSection
# EndSection
You still have your Driver set to nv... This should say:
Driver "nvidia"
Just edit it manually 
Hope that helps.
_________________
...ehm...yeah...definately...Edited By TjaBBe on 10/28/05 10:08 |
|
|
murankar
Game Owner
NWN
NWN: SoU
NWN: HotU
Suscrito: 24 feb 2005 |
Colgado: lunes, 31 octubre 2005 12:43 |
|
i have tried that. it screws up my x server at that point. it freezes right after i startx. unless it is taking longer to start due to the active 3d drivers. |
|
|
