reopen 397384 !
thanks
On Tue, 7 Nov 2006 00:37:36 +0100
[EMAIL PROTECTED] (Marco d'Itri) wrote:
> On Nov 07, "A. Costa" <[EMAIL PROTECTED]> wrote:
>
> > tvbox:~# modprobe -v /lib/modules/2.4.27/misc/lirc_dev.o
> > modprobe: Can't locate
> > module /lib/modules/2.4.27/misc/lirc_dev.o
> modprobe does not work this way, please RTFM.
Thanks for the tips. As per your advice I just read some of the 174
line 'modprobe' manual, in particular the SYNOPSIS, for instance:
modprobe [ -r ] [ -v ] [ -n ] [ -i ] [ modulename ... ]
If I understood that syntax correctly, modprobe takes just the module
name, not the file name. So typing in a full path name certainly should
produce an error message...
In which case the current error message is misleading for bad input
that happens to be a file name. If directory slashes are garbage
characters in such a module name, then the error message should warn
not that it "can't find" a nonsensical module name, rather the error
should warn that it can't PARSE it. There's a world of difference
between parsing and finding.
> Especially the part explaining that module-init-tools only deals with
> 2.6 kernels and that 2.4 kernels...
This part:
% man modprobe | grep -n -A 4 BACKWARDS
186:BACKWARDS COMPATIBILITY
187- This version of modprobe is for kernels 2.5.48 and
above. If it
188- detects a kernel with support for old-style modules (for
which much of
189- the work was done in userspace), it will attempt to run
modprobe.modu-
190- tils in its place, so it is completely transparent to the
user.
So, less than 2.5.48, a 'modutils' bug. 2.5.48 or greater, it's a
'module-init-tools' bug.
> ... are managed by modutils, which is
> generating these error messages.
In the end note of my first message, you may have noticed I ran the
same test on my main Debian 'unstable' system and got this error:
% cp /lib/modules/2.6.16-2-686/kernel/drivers/scsi/sata_sx4.ko /tmp/
% modprobe /tmp/sata_sx4.ko
FATAL: Module /tmp/sata_sx4.ko not found.
I regret not including a kernel version for that system then, which was:
% cat /proc/version
Linux version 2.6.16-2-686 (Debian 2.6.16-18) ([EMAIL PROTECTED]) (gcc
version 4.0.4 20060730 (prerelease) (Debian 4.0.3-6)) #1 Fri Aug 18 19:01:49
UTC 2006
So it seems this bug is in BOTH 'modutils' and 'module-init-tools'.
HTH...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
