Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
i have a problem with nvidia driver on a gentoo box (2005.1)
my Xorg.0.log
Quote:
(II) LoadModule: "glx"
(II) Loading /usr/lib64/modules/extensions/libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.6629
Module class: XFree86 Server Extension
ABI class: XFree86 Server Extension, version 0.1
(II) Loading extension GLX
(II) LoadModule: "nvidia"
(II) Loading /usr/lib64/modules/drivers/nvidia_drv.o
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.6629
Module class: XFree86 Video Driver
....
(II) NVIDIA X Driver 1.0-6629 Wed Nov 3 11:44:46 PST 2004
(II) NVIDIA Unified Driver for all NVIDIA GPUs
(II) Primary Device is: PCI 01:00:0
(--) Chipset NVIDIA GPU found
...
(II) Setting vga for screen 0.
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(--) NVIDIA(0): Linear framebuffer at 0xC0000000
(--) NVIDIA(0): MMIO registers at 0xC8000000
(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module!
(EE) NVIDIA(0): *** Aborting ***
(II) UnloadModule: "nvidia"
(EE) Screen(s) found, but none have a usable configuration.
when i try to startx with 'nv' driver and without 'Load glx' ....X works but not optimised for my graphics cards
My graphics card is a 6600 Nvidia
If you want to read my xorg.conf..
My_XORG.CONF
Quote:
# File generated by xorgconfig.
#
# Copyright 2004 The X.Org Foundation
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# 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)
#
#
# 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).
# 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"
# 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" "pc105"
# 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" "fr"
# 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" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# 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.
# 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.
# 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 "nvidia"
# 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.
# 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 "NVIDIA6600"
Monitor "VE910"
DefaultDepth 24
# 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".
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,524
Rep:
There is a log file which tells you exactly what went wrong with the nVidia driver. You are probably missing some symlinks in /usr/X11R6/lib/modules, or subdirectories thereof. Your card may not be supported yet.
Damn it, man! I have the same problem.
I used ATi before and it was hard to get it to work and let it stay that way.
I then changed to NVIDIA in hope i'll have a more stable support now. But he*l, still aint working!
I have Gentoo 2005.1. I'm 99,99% sure I've compild my kernel good, because I must have done it 50 times!
As far as I've gone, the only thing I realised is that there is no /dev/nvidia and these nodes should have been made. If anyone is able to help me, please post and I'll reply with comprehensive status about my output and current kernel config, etc.
Distribution: Gentoo 2005.1 x86_64 & Windows XP Pro
Posts: 8
Rep:
Well it looks we can add another person to this thread. I'm experiencing the same problem with a fresh install of Gentoo 2005.1 AMD64, Kernel 2.6.13r3.
I tried just about every different method of getting the nvidia drivers except for the source drivers from nvidia. I've tried but I get a conflict with existing opengl; even though I've unmerged nvidia-kernel and nvidia-glx, ran through a emerge --depclean. I still get the same errors listed below. I imagine I haven't removed something that's need to be removed but I'm not going to start deleting files if I don't know what they are.
I'm a gentoo noob but I've followed every possile nVidia install guide I could find with the same results. If I should post more information please let me know.. This is my first post to LinuxQuestions.
nvidia-installer.log <excerpt>
...
-> Installing 'NVIDIA Accelerated Graphics Driver for Linux-x86_64'
(1.0-7676):
-> The installer has encountered the following error during installation: 'Cann
ot create symlink /usr/lib/libGL.so.1 (File exists)'. Continue anyway? ("no
" will abort)? (Answer: Yes)
...
ERROR: The runtime configuration check failed for library 'libGL.so.1.0.7676'
(expected: '/usr/lib64/libGL.so.1', found: 'not'). The most likely
reason for this is that conflicting OpenGL libraries are installed in a
location not inspected by `nvidia-installer`. Please be sure you have
uninstalled any third-party OpenGL and third-party graphics driver
packages.
-> done.
-> Runtime sanity check failed.
ERROR: Installation has failed.
..
-> The installer has encountered the following error during installation: 'Cann
ot create symlink /usr/lib/libGL.so (File exists)'. Continue anyway? ("no"
will abort)? (Answer: Yes)
-> The installer has encountered the following error during installation: 'Cann
ot create symlink /usr/lib/libGLcore.so.1 (File exists)'. Continue anyway?
("no" will abort)? (Answer: Yes)
-> The installer has encountered the following error during installation: 'Cann
ot create symlink /usr/lib/libnvidia-tls.so.1 (File exists)'. Continue anyw
ay? ("no" will abort)? (Answer: Yes)
-> The installer has encountered the following error during installation: 'Cann
ot create symlink /usr/lib/tls/libnvidia-tls.so.1 (File exists)'.
Welll it looks to me that you had those symlinks before this install/emerge that means you've emerged some other ebuild and it's probably the 32 bit variant (cause i can't think of any other).
try emerge -s nvidia and see what it says is installed, what ver, what architecture. also try -s glx drm dri and see if those are installed too(they shouldn't). I don't have 64bit but I know it just another headache setting that up!
There is also a BIG kernel configuration involve here!
PS-i'm still a newb compared to others but if you're really new to linux this is gonna be HARD for you!(and maybe for the 'gurus' that would try to help you)
Distribution: Gentoo 2005.1 x86_64 & Windows XP Pro
Posts: 8
Rep:
I've tried your suggestions Worksman and nothing was installed since I "emerge --unmerge" anything nvidia related. It was clean before the install of source nVidia drivers but I still get the same errors. I've had the nVidia source drivers working on previous distros; debian, slack, mdk, mandriva (all 32bit installs mind you). I was a little vague in being a complete noob. I've been around the block with a different flavours of linux but I had a tendency of giving up when things break instead of fixing it. I'm trying to get away from that and get a nice and stable working system going, no matter what.
Is it in my best interests to post a new thread and include all my logs and confs pertaining to this problem or should I just make a continuation of this post even though it's not exactly the same topic.
In the mean time I just want to say that I've finally managed to install the nvidia drivers for my NVidia GeForce4 MX440 with AGP8X.
Believe me it took me some while! And a lot of reading but in the end you are very satisfied!
Here's what I've done and what I've found out:
Some people say that if you enable that hardware random number generator in the kernel config for the chipsets specified there that
support it, the driver will not work: false.
One thing is certain as I tried every possible combination: you need to know what to enable and what to disable(or build as a module)
in the kernel configuration.
The vesafb-tng framebuffer README should be very closelly READ!
That applies also to the nvidia driver README.
They are all in the kernel tree under 'Documentation/'.
That's what helped me and the forums too, but it is obvious that if you have patience and read all the Documentation you don't need
the forums! Just when you run into a bogo and don't know what to do! (in this case you should also read the docs first!
It might sound too much but believe me: writing to a forum and asking how do I install nvidia driver and what are the options I have
to add to xorg.conf for TwinView to work, will actually take you longer!
My current kernel config is not 100% shure but it works for me.
In the future I will experiment to get better performance if possible.
This attitude is the fault of the developers because they add new stuff like clock timing (HZ option 100/250/1000).
And it is my fault that I don't know much about my architecture, cpu and chipset(for example I don't know if my chipset supports
PCI2.3 or Message Signaled Interrupts/-X or even HPET, so I enable them because I think it does and because they didn't seem to
throw error on me or cause instabillity/security problems)
My machine is primarily a desktop machine but I don't want the preemptible kernel stuff as I'm more of a power user.
Also I chose the 'medium' stuff from where there are 3 options, excluding preemptible kernel(like HZ 250, Deadline I/O scheduler)
And it *seems* to works better, stabler, faster(or even do).
To help you I will give you my kernel .config file so you can compare mine with yours, make the difference(stuff you'r not sure about)
and merge the two.
Also I will give you my xorg.conf (it has commented out TwinView settings).
But first let me setup Apache(that won't take long).
If you can't wait then jabber me @ worksman@unstable.nl/Home or email me @ djwman@gmail.com
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.