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 - 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/