| View previous topic :: View next topic |
| Author |
Message |
atrain
Tux's lil' helper
Joined: 05 Oct 2004
Posts: 86
|
 Posted: Sun Oct 31, 2004 12:56 am Post subject: NVIDIA kernel support wont start!!! |
 |
|
im running gentoo-dev-sourses, kernel 2.6.9, and when i tried emerging nvidia-kernel, after i tried modprobing:
| Code: | bash-2.05b# modprobe nvidia
FATAL: Error inserting nvidia (/lib/modules/2.6.9-gentoo-r1/video/nvidia.ko): Unknown symbol in module, or unknown parameter (see dmesg) |
i have nvidia-glx, xorg, kde and gmone emerged.... |
|
| Back to top |
|
 |
einstein1981
Guru
Joined: 10 Mar 2004
Posts: 395
Location: Venezuela , Caracas
|
| Posted: Sun Oct 31, 2004 1:27 am Post subject: might be of some help |
|
|
It had been some time since i'd used my gentoo, becaus of university, so when I got some tie and did the emerge sync and world, after 3 months of not doing it , my x server gto seriously screwed.. so I REDID MI WHOLE ISNTALL just to find out that xf86 wasn't the default grafical server for gentoo.. this long story is to tell you that, when i installed xorg i ran into some problems, with nvidia-kernel...
the way I solved it was by doing this
| Code: | ACCECPT_KEYWORD="~x86" emerge nvidia-kernel
ACCECPT_KEYWORD="~x86" emerge nvidia-glx |
might be worth a try
good luck@
_________________
thesis. |
|
| Back to top |
|
|
atrain
Tux's lil' helper
Joined: 05 Oct 2004
Posts: 86
|
| Posted: Sun Oct 31, 2004 2:53 am Post subject: |
|
|
| i tried ACCECPT_KEYWORD="~x86" emerge nvidia-kernel, and all i got when i satarted xorg is a blank screen an i couldnt do anything exept restart... |
|
| Back to top |
|
|
rj686
Apprentice
Joined: 12 Oct 2004
Posts: 199
Location: In my room playing my guitar or Sitting at my damn computer trying to get my fuckin gentoo to work:)
|
| Posted: Sun Oct 31, 2004 2:57 am Post subject: |
|
|
ive got the same error and ive been trying to solve it for DAYS
(sorry that i cant be of help) 
_________________
Athalon XP 3000+ (e-machines)
OS's:
Windows due to my idiot brother, I'll go full linux once i get my laptop  |
|
| Back to top |
|
|
atrain
Tux's lil' helper
Joined: 05 Oct 2004
Posts: 86
|
| Posted: Sun Oct 31, 2004 3:00 am Post subject: |
|
|
well i hear with the 2.6.9 kernel u will need the 6111 driver; to get it: emerge sync, the accept_keywords="~x86" emerge nvidia-kernel
im trying to do the same with the nvidia-glx right now... |
|
| Back to top |
|
|
atrain
Tux's lil' helper
Joined: 05 Oct 2004
Posts: 86
|
| Posted: Sun Oct 31, 2004 3:06 am Post subject: |
|
|
yup it works!!!!
remember - in ur xorg.conf, NO DRI, no DBE, YES GLX
[
and at end:
| Code: | Section "DRI"
Mode 0666
EndSection
|
|
|
| Back to top |
|
|
rj686
Apprentice
Joined: 12 Oct 2004
Posts: 199
Location: In my room playing my guitar or Sitting at my damn computer trying to get my fuckin gentoo to work:)
|
| Posted: Sun Oct 31, 2004 3:07 am Post subject: |
|
|
i still get teh same error
_________________
Athalon XP 3000+ (e-machines)
OS's:
Windows due to my idiot brother, I'll go full linux once i get my laptop |
|
| Back to top |
|
|
rj686
Apprentice
Joined: 12 Oct 2004
Posts: 199
Location: In my room playing my guitar or Sitting at my damn computer trying to get my fuckin gentoo to work:)
|
| Posted: Sun Oct 31, 2004 3:10 am Post subject: |
|
|
i dont see that section.......(DRI)
mine took the command
| Code: | | ACCECPT_KEYWORD="~x86" emerge nvidia-kernel |
but it didnt seem to do anything cuz i still get that error
i did the same with glx but im still havin trouble
_________________
Athalon XP 3000+ (e-machines)
OS's:
Windows due to my idiot brother, I'll go full linux once i get my laptop
Last edited by rj686 on Sun Oct 31, 2004 3:26 am; edited 2 times in total |
|
| Back to top |
|
|
rj686
Apprentice
Joined: 12 Oct 2004
Posts: 199
Location: In my room playing my guitar or Sitting at my damn computer trying to get my fuckin gentoo to work:)
|
| Posted: Sun Oct 31, 2004 3:22 am Post subject: |
|
|
same error after i finished the commands.......what the hell am i doing wrong 
_________________
Athalon XP 3000+ (e-machines)
OS's:
Windows due to my idiot brother, I'll go full linux once i get my laptop |
|
| Back to top |
|
|
einstein1981
Guru
Joined: 10 Mar 2004
Posts: 395
Location: Venezuela , Caracas
|
| Posted: Sun Oct 31, 2004 4:32 am Post subject: |
|
|
Well I'll post my xorg.conf file,because, you need to get this properly configured in order for it to work...
| Code: |
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
#
# **********************************************************************
# Refer to the xorg.conf(5x) man page for details about the format of
# this file.
# **********************************************************************
# **********************************************************************
# 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
# **********************************************************************
# 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)
#
#
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/Type1/"
# FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/local/"
# FontPath "/usr/share/fonts/Speedo/"
# FontPath "/usr/share/fonts/TrueType/"
# FontPath "/usr/share/fonts/freefont/"
# 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 "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 Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xorg"
Option "XkbModel" "dell101"
Option "XkbLayout" "us"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "PS/2"
Option "Device" "/dev/mouse"
# 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 xorg.conf 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 "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 43-85
# 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 40-60
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 xorgconfig:
Section "Device"
Identifier "geforce5200"
Driver "nvidia"
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 "geforce5200"
Monitor "monitor"
DefaultDepth 16
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 "1400x1050" "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
|
at first don't get greedy with the depth and resolution, get a working config, then work your way up...
remember that you have to recompile nvidia-kernel and glx, after compiling a new kernel...
To try out your config type if this gives you a horrible grafics set, just cnrtl alt backspace to close it...
also you say in one of the previous posts that the screen goes blank and nothing else to do but restart.. this is unprobable, did you know that you have multiple consoles, you can switch between them by pressing cntrl alt and the F keys
for instance... you boot up to the F1 console... from 1 to 6 its consoles... when a graphical server such as xfree or xorg starts up in F7 so, if the screen goes blank just control alt f1 to go back to the caller console...
It would seem to me that the blank screen is an indication that the server IS in fact RUNNING, only it's not properly configurer, usualy when it crashes, you just get the reason on the caller console..
well hope this helps...
check the vsync and hsync for your screen, mine are for a dell inspiron 5150 laptop. so don't use then unless you are sure they work.. you could een fry your monitor...
well bye
charz
_________________
thesis. |
|
| Back to top |
|
|
rj686
Apprentice
Joined: 12 Oct 2004
Posts: 199
Location: In my room playing my guitar or Sitting at my damn computer trying to get my fuckin gentoo to work:)
|
| Posted: Sun Oct 31, 2004 5:10 am Post subject: |
|
|
i've got a tatung lcd monitor but i have nothing in teh way of information about it
_________________
Athalon XP 3000+ (e-machines)
OS's:
Windows due to my idiot brother, I'll go full linux once i get my laptop |
|
| Back to top |
|
|
atrain
Tux's lil' helper
Joined: 05 Oct 2004
Posts: 86
|
| Posted: Sun Oct 31, 2004 5:22 am Post subject: |
|
|
| try reemergeing xorg, and grabing a new version... |
|
| Back to top |
|
|
einstein1981
Guru
Joined: 10 Mar 2004
Posts: 395
Location: Venezuela , Caracas
|
| Posted: Sun Oct 31, 2004 5:31 am Post subject: |
|
|
ok, the monitor settings should be documented in your user manual, or just google for it... I assure you they are there...
also I forgot to ask if you had tried the automatic config script?
well keep trying...
_________________
thesis. |
|
| Back to top |
|
|
|
Desktop Environments
