Re: modprobe failed: digest_null

[Randy.Dunlap]

On Tue, 13 Jan 2004 23:50:47 +0100 martin f krafft <madduck@xxxxxxxxxxx> wrote:

| also sprach Randy.Dunlap <rddunlap@xxxxxxxx> [2004.01.13.2341 +0100]:
| > I would guess that you have a high-priority $PATH to old modprobe
| > than to the new modprobe...
| 
| That would surprise me, Debian handles this quite well:
| 
| diamond:~# which modprobe
| /sbin/modprobe
| diamond:~# modprobe -V
| module-init-tools version 3.0-pre5
| diamond:~# modprobe.modutils -V
| modprobe version 2.4.26
| modprobe: QM_MODULES: Function not implemented
| diamond:~# uname -r
| 2.6.1

OK, maybe someone else has an answer then.

The message:
kernel: request_module: failed /sbin/modprobe -- digest_null. error = 256
is from modutils and not from module-init-tools according to my
source files.

--
~Randy
MOTD:  Always include version info.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/