From: Keith Owens <kaos@ocs.com.au>
To: "Jahn Veach - Veachian64" <V64@Galaxy42.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Unresolved symbols in 2.4.6
Date: Mon, 09 Jul 2001 10:37:27 +1000 [thread overview]
Message-ID: <25863.994639047@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Sun, 08 Jul 2001 18:52:28 EST." <004c01c10809$0dc310a0$5d910404@molybdenum>
On Sun, 8 Jul 2001 18:52:28 -0500,
"Jahn Veach - Veachian64" <V64@Galaxy42.com> wrote:
>nm vmlinux | grep printk
>
>c024f44e ? __kstrtab_printk
>c0254870 ? __ksymtab_printk
>c0113494 T printk
>c017c6ec t printk_pnp_dev_id
That looks OK. Just to confirm, when you did depmod -ae, did you
include -F pointing at the 2.4.6 System.map? If you omitted -F then it
used /proc/ksyms on your current kernel, I suspect that this is your
problem. The command should be depmod -ae -F 2.4.6/System.map 2.4.6.
You should not need to issue that command by hand, make modules_install
does it automatically.
As for why you panic when you try to mount the root file system, you
have your SCSI driver and ide-disk as modules, not built into the
kernel. If the code to find and mount your root file system is in
modules then you must use initrd, see the kernel howto. Unless you
have a *very* good reason to use initrd - don't. Build the root
drivers into the kenrel instead.
next prev parent reply other threads:[~2001-07-09 0:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-08 7:46 Unresolved symbols in 2.4.6 Jahn Veach - Veachian64
2001-07-08 8:23 ` Keith Owens
2001-07-08 14:20 ` Jahn Veach - Veachian64
2001-07-08 22:51 ` Keith Owens
2001-07-08 23:52 ` Jahn Veach - Veachian64
2001-07-09 0:37 ` Keith Owens [this message]
2001-07-09 1:46 ` Jahn Veach - Veachian64
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=25863.994639047@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=V64@Galaxy42.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.