Messages in this thread | | | Date | Tue, 13 Jan 2004 16:59:51 -0800 | From | "Randy.Dunlap" <> | Subject | Re: modprobe failed: digest_null |
| |
On Tue, 13 Jan 2004 16:01:31 -0800 "Randy.Dunlap" <rddunlap@osdl.org> wrote:
| On Tue, 13 Jan 2004 15:38:45 -0800 (PST) "David Rees" <drees@greenhydrant.com> wrote: | | | On Tue, January 13, 2004 at 3:03 pm, Randy.Dunlap wrote: | | > | | > 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. | | | | I'm getting similar messages from dmesg after upgrading to 2.6.1, too: | | | | request_module: failed /sbin/modprobe -- n. error = 256 | | | | [drees@summit drees]$ /sbin/modprobe -V | | module-init-tools version 3.0-pre5 | | [drees@summit drees]$ | | | | Running on Fedora Core 1 compiled with gcc 3.3.2. Didn't see these with | | 2.6.0. | | Yes, I see a couple of similar messages: | | request_module: failed /sbin/modprobe -- parport_lowlevel. error = -16 | request_module: failed /sbin/modprobe -- fb0. error = 256 | | ...?
I don't think that it's related to IPsec since I'm not using that.
I'm looking at the changes in kernel/kmod.c for 2.6.1 to see if they could cause it.
-- ~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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |