LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   nvidia 2.6.24.5 (https://www.linuxquestions.org/questions/slackware-14/nvidia-2-6-24-5-a-658022/)

eddygrinder 07-24-2008 01:16 PM

nvidia 2.6.24.5
 
Hello once again!

This wasn't the first time that i have this error when installing the nvidia drivers - NVIDIA-Linux-x86-96.43.07-pkg1.run:

**********************************************************************

ERROR: Unable to load the kernel module 'nvidia.ko'. This happens most
frequently when this kernel module was built against the wrong or
improperly configured kernel sources, with a version of gcc that differs
from the one used to build the target kernel, or if a driver such as
rivafb/nvidiafb is present and prevents the NVIDIA kernel module from
obtaining ownership of the NVIDIA graphics device(s).

**********************************************************************

packages:
gcc-4.2.3
gcc-g++-4.2.3
kernel-generic-2.6.24.5-i486-2
kernel-headers-2.6.24.5-x86-2
kernel-modules-2.6.24.5-i486-2
kernel-source-2.6.24.5_smp-noarch-2

What's the problem?
Thx
EddY

samac 07-24-2008 01:37 PM

What graphics card do you have?

The nvidia version you are using is for legacy cards, the latest version is http://www.nvidia.com/object/linux_d...173.14.09.html

samac

eddygrinder 07-24-2008 02:06 PM

Quote:

Originally Posted by samac (Post 3225238)
What graphics card do you have?

The nvidia version you are using is for legacy cards, the latest version is http://www.nvidia.com/object/linux_d...173.14.09.html

samac

An old one: Geforce4 TI 4200

mostlyharmless 07-24-2008 03:07 PM

Are you using the generic kernel? I have a GeForce TI 4600. The installer (same one you used) built a module for me which worked without incident with a new install of Slackware 12.1.

T3slider 07-24-2008 06:58 PM

You should make sure that rivafb and nvidiafb are absent from `lsmod` output. I would guess your problem is caused by the lack of SMP kernels -- it looks like you only have the generic and huge kernels (and not the generic-smp and huge-smp kernels) installed. From CHANGES_AND_HINTS.TXT on your install CD/DVD or available from your favourite mirror:
Quote:

Originally Posted by CHANGES_AND_HINTS.TXT
Use one of the provided generic kernels for daily use. Do not report
bugs until/unless you have reproduced them using one of the stock
generic kernels. You will need to create an initrd in order to boot
the generic kernels - see /boot/README.initrd for instructions.

Quote:

Originally Posted by CHANGES_AND_HINTS.TXT
As stated earlier, it is recommended that you use one of the generic kernels
rather than the huge kernels; the huge kernels are primarily intended as
"installer" and "emergency" kernels in case you forget to make an initrd.
For most systems, you should use the generic SMP kernel if it will run,
even if your system is not SMP-capable. Some newer hardware needs the
local APIC enabled in the SMP kernel, and theoretically there should not be
a performance penalty with using the SMP-capable kernel on a uniprocessor
machine, as the SMP kernel tests for this and makes necessary adjustments.
Furthermore, the kernel sources shipped with Slackware are configured for
SMP usage, so you won't have to modify those to build external modules
(such as NVidia or ATI proprietary drivers) if you use the SMP kernel.

If you decide to use one of the non-SMP kernels, you will need to follow the
instructions in /extra/linux-2.6.24.5-nosmp-sdk/README.TXT to modify your
kernel sources for non-SMP usage. Note that this only applies if you are
using the Slackware-provided non-SMP kernel - if you build a custom kernel,
the symlinks at /lib/modules/$(uname -r)/{build,source} will point to the
correct kernel source so long as you don't (re)move it.

If you decide to use one of the huge kernels anyway, you will encounter
errors like this:
kobject_add failed for uhci_hcd with -EEXIST, don't try to register
These occur because the respective drivers are compiled statically into the
huge kernels but udev tries to load them anyway. These errors should be safe
to ignore, but if you really don't want them to appear, you can blacklist the
modules that try to load in /etc/modprobe.d/blacklist. However, make sure you
remove them from the blacklist if you ever decide to use the (recommended)
generic kernels.

I would HIGHLY recommend using the huge-smp or generic-smp kernel over the non-SMP kernels (and I would further recommend the generic-smp kernel over the huge-smp kernel). Note that the generic-smp kernel requires the use of an initial ramdisk (initrd) -- see /boot/README.initrd for more information. Search the forum for information on how to switch to the generic-smp kernel (it has been explained many times). Note that you will have to install the huge-smp and generic-smp kernels (at least one of them, anyway) since they're not currently installed on your system. They are both located in the a/ series on your install CD/DVD (CD 1) or at your favourite mirror.

eddygrinder 07-25-2008 12:35 PM

Hello!

I'm using non-smp kernel!

I'm gonna install the smp kernel...

Cheers!

EddY

eddygrinder 07-30-2008 01:29 PM

nvidia 2.6.24.5 [SOLVED]
 
Hello!

The answer right before my eyes.... what a dumb ssa i am!
Just installed all smp packages:

kernel-generic-smp-2.6.24.3_smp-i686-2
kernel-headers-2.6.24.3_smp-x86-2
kernel-modules-smp-2.6.24.3_smp-i686-2
kernel-source-2.6.24.3_smp-noarch-2

thx for your help!
EddY

BTW i'm gonna open a new thread because i'm gonna on a vacations and i want to know if is possible to turn on/off the pc by software. Like:

01:00 - pc turn on
09:00 - pc turn off (hibernate)

Is this possible?

Thx


All times are GMT -5. The time now is 03:30 PM.