From: Keith Owens <kaos@ocs.com.au>
To: root@chaos.analogic.com
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: linux-2.4.0-test9
Date: Sat, 04 Nov 2000 21:55:27 +1100 [thread overview]
Message-ID: <6695.973335327@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Fri, 03 Nov 2000 17:54:51 CDT." <Pine.LNX.3.95.1001103175055.612A-100000@chaos.analogic.com>
On Fri, 3 Nov 2000 17:54:51 -0500 (EST),
"Richard B. Johnson" <root@chaos.analogic.com> wrote:
>(1) I have SCSI modules that have to be installed upon boot
>from initrd. Insmod failed with "Can't find the kernel version that
>this module was compiled with..."
"Can't find the kernel version that this module was compiled with..."
means that the module object does not contain symbol __module_kernel_version.
What does 'nm' on the module report?
>modutils, downloaded and installed today. Also `insmod -f` doesn't
>work (not a kernel problem, yes, I know).
Does not work how? Details please.
>The only fix I could come up with was to remove EXTRAVERSION=test9 in
>the top-level Makefile (actually set it to nothing), then recompile
>the whole kernel. This problem will get others, I am sure.
I suspect user error, probably old modules lying around somewhere. A
compile out of the box for 2.4.0-test9 worked fine for me and AFAICT
for everybody else.
-
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 prev parent reply other threads:[~2000-11-04 10:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-03 22:54 linux-2.4.0-test9 Richard B. Johnson
2000-11-04 1:05 ` linux-2.4.0-test9 Jeff Garzik
2000-11-04 2:49 ` linux-2.4.0-test9 Richard B. Johnson
2000-11-04 3:12 ` linux-2.4.0-test9 Jeff Garzik
2000-11-04 8:20 ` linux-2.4.0-test9 Ingo Oeser
2000-11-04 8:26 ` linux-2.4.0-test9 Jeff Garzik
2000-11-04 10:55 ` Keith Owens [this message]
2000-11-06 14:45 ` linux-2.4.0-test9 Richard B. Johnson
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=6695.973335327@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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