Re: modprobe failed: digest_null

[Martin Schlemmer]

On Wed, 2004-01-14 at 01:03, Randy.Dunlap wrote:
> 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.
> 

Its from the kernel afaik.  It calls modprobe, fails, and then prints
its own custom message.  He basically just have something that tries
to load a module with alias 'digest_null', but there is no such module,
so fails.

I have the same thing when I open gnome-mixer:

--
request_module: failed /sbin/modprobe -- sound-slot-1. error = 256
--

as I only have one sound card ...


Cheers,

-- 
Martin Schlemmer

Attachment: signature.asc
Description: This is a digitally signed message part