From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Steve Youngs <sryoungs@bigpond.net.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: modprobe failed: digest_null
Date: Tue, 13 Jan 2004 17:31:13 -0800 [thread overview]
Message-ID: <20040113173113.0bed1edc.rddunlap@osdl.org> (raw)
In-Reply-To: <microsoft-free.87isjffhhz.fsf@eicq.dnsalias.org>
On Wed, 14 Jan 2004 11:26:00 +1000 Steve Youngs <sryoungs@bigpond.net.au> wrote:
| * Randy Dunlap <Randy.Dunlap> writes:
|
| > 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.
|
| Your correct about where this message _doesn't_ come from, but not
| about where it _does_ come from...
|
| ,----[ ./kernel/kmod.c -- lines 113 - 115 ]
| | printk(KERN_DEBUG
| | "request_module: failed %s -- %s. error = %d\n",
| | modprobe_path, module_name, ret);
| `----
Yes, I found that and am digging into it, but I'm close to end-of-day,
so someone else can pick it up soon...
--
~Randy
MOTD: Always include version info.
next prev parent reply other threads:[~2004-01-14 1:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 21:53 martin f krafft
2004-01-13 22:30 ` Randy.Dunlap
2004-01-13 22:37 ` martin f krafft
2004-01-13 22:41 ` Randy.Dunlap
2004-01-13 22:50 ` martin f krafft
2004-01-13 23:03 ` Randy.Dunlap
2004-01-13 23:38 ` David Rees
2004-01-14 0:01 ` Randy.Dunlap
2004-01-14 0:59 ` Randy.Dunlap
2004-01-14 0:08 ` martin f krafft
2004-01-14 1:05 ` David Rees
2004-01-14 23:48 ` Randy.Dunlap
2004-01-15 0:46 ` Stian Jordet
2004-01-15 8:50 ` martin f krafft
2004-01-14 1:26 ` Steve Youngs
2004-01-14 1:31 ` Randy.Dunlap [this message]
2004-01-14 8:45 ` martin f krafft
2004-01-16 15:55 ` Martin Schlemmer
2004-01-14 23:22 ` Rusty Russell
2004-01-15 8:08 ` martin f krafft
2004-01-15 16:30 ` Randy.Dunlap
2004-01-15 20:51 ` Andreas Schrell
2004-01-19 4:53 ` Rusty Russell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040113173113.0bed1edc.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sryoungs@bigpond.net.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome