Your message dated Tue, 16 Sep 2008 20:36:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Close
has caused the Debian Bug report #269677,
regarding nvidia-kernel-2.4.26-1-686: modprobe fails with "Cannot allocate
memory"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
269677: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=269677
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: nvidia-kernel-2.4.26-1-686
Version: 1.0.6111+1
Severity: normal
When I tried to load up the nvidia kernel module with "modprobe nvidia"
I got this:
Warning: loading /lib/modules/2.4.26-1-686/nvidia/nvidia.o will taint the
kernel: non-GPL license - NVIDIA
See http://www.tux.org/lkml/#export-tainted for information about tainted
modules
/lib/modules/2.4.26-1-686/nvidia/nvidia.o: init_module: Cannot allocate memory
/lib/modules/2.4.26-1-686/nvidia/nvidia.o: insmod
/lib/modules/2.4.26-1-686/nvidia/nvidia.o failed
/lib/modules/2.4.26-1-686/nvidia/nvidia.o: insmod nvidia failed
Hint: insmod errors can be caused by incorrect module parameters, including
invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
After a quick web search I found this:
Try manually deleting the /dev/nvidia* devices via:
rm -f /dev/nvidia*
[...]
The module should load properly then. The error return code set in
nv.c on line 1109 is -ENOMEM when the devfs_mk_cdev fails on 2.4.x
kernels. This return code causes insmod to fail correctly but print
the wrong error.
[taken from http://www.nvnews.net/vbulletin/showthread.php?t=34428]
Running the rm command worked, but would it be possible to change nv.c
so that it (a) fails with a better error code and (b) doesn't call
devfs_mk_cdev if the devices exist already?
Cheers,
Mark.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-1-686
Locale: LANG=en_GB, LC_CTYPE=en_GB
Versions of packages nvidia-kernel-2.4.26-1-686 depends on:
ii nvidia-kernel-common 1.0.6111+1 NVIDIA binary kernel module common
-- no debconf information
--- End Message ---
--- Begin Message ---
Le September 16, 2008 06:48:10 pm Mark Sheppard, vous avez écrit :
> I've not seen that error in years. more. That was with an old 2.4.x
> kernel and I've long since moved to 2.6.x and am using this:
>
> nvidia-kernel-legacy-2.6.18-6-686 1.0.7184+6etch2
>
> So I guess this bug is no longer current.
Since nobody who reported experiencing this bug is still experiencing it,
let's assume the bug is out of date. If anyone can reproduce with a current
Debian suite, feel free to reopen.
--- End Message ---
