From: Peter Kaczuba <pepe@pool.informatik.rwth-aachen.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.0ac12
Date: Sat, 27 Jan 2001 12:06:57 +0100 [thread overview]
Message-ID: <20010127120657.A975@orbiter.ath.cx> (raw)
On 2001-01-27 1:46:12 "Sergey Kubushin" <ksi@cyberbills.com> wrote:
> Modules still don't load:
>
>=== Cut ===
>ide-mod.o: Can't handle sections of type 32131
>ide-probe-mod.o: Can't handle sections of type 256950710
>ide-disk.o: Can't handle sections of type 688840897
>ext2.o: Can't handle sections of type 69429248
>=== Cut ===
>
>Section types are exactly the same in ac9,10,11,12.
>
>Is it supposed to be this way? Does anybody care? Or may be I'm the only
>one who uses modules?
You are not alone out there! :-)
I have the same problems using a modular kernel, it is the same
configuration as yours (kernel 2.4.0-ac12, modutils 2.4.2,
binutils-2.10.1.0.4, gcc-2.95.2). 2.4.0-ac4 works, up from 2.4.0-ac8 do
not (others not tested).
I get these errors at boot time:
VFS: Mounted root (romfs filesystem) read only.
kmod: runaway modprobe loop assumed and stopped
kmod: runaway modprobe loop assumed and stopped
insmod: /lib/modules/2.4.0-ac12/kernel/net/unix/unix.o: can't handle
sections of type 255 /lib/modules/2.4.0-ac12/kernel/net/unix/unix.o
kmod: runaway modprobe loop assumed and stopped
insmod: /lib/modules/2.4.0-ac12/kernel/net/unix/unix.o: insmod net-pf-1
failed
Hope this helps.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-27 11:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-27 11:06 Peter Kaczuba [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-27 11:25 Linux 2.4.0ac12 Keith Owens
2001-01-26 23:53 Alan Cox
2001-01-27 1:46 ` Sergey Kubushin
2001-01-27 6:52 ` Keith Owens
2001-01-30 2:45 ` john slee
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=20010127120657.A975@orbiter.ath.cx \
--to=pepe@pool.informatik.rwth-aachen.de \
--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