From: Michael Reinelt <reinelt@eunet.at>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: modules load, but do not initialize
Date: Tue, 06 Nov 2001 23:51:50 +0100 [thread overview]
Message-ID: <3BE86986.F975DEB9@eunet.at> (raw)
Hello,
I found a strange behaviour today: I'm experimenting with a boot floppy
with its own little linux on it, based on kernel 2.4.14.
I get the same effects when I really boot the disk, or if I chroot()
into the directory which will later get imaged to disk: I can load and
unload modules (with insmod, lsmod, rmmod, modprobe), but it looks like
they never get initialised. I know for shure that some modules should
write something to syslog or the console, delay a bit (esp
ide-probe-mod), and, last but not least, provide a device or something.
Nothing of this happens.
Well, something happens after a few tries: it ooopses...
What's happening here?
I can provide any info you like or need.
bye, Michael
--
netWorks Vox: +43 316 698260
Michael Reinelt Fax: +43 316 692343
Geisslergasse 4 GSM: +43 676 3079941
A-8045 Graz, Austria e-mail: reinelt@eunet.at
reply other threads:[~2001-11-06 22:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3BE86986.F975DEB9@eunet.at \
--to=reinelt@eunet.at \
--cc=linux-kernel@vger.kernel.org \
/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