From: Keith Owens <kaos@ocs.com.au>
To: Ed Tomlinson <tomlins@cam.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.7-pre5 missing symbols?
Date: Wed, 11 Jul 2001 13:54:18 +1000 [thread overview]
Message-ID: <5194.994823658@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Tue, 10 Jul 2001 07:53:59 -0400." <20010710115400.5ED711C495@oscar.casa.dyndns.org>
On Tue, 10 Jul 2001 07:53:59 -0400,
Ed Tomlinson <tomlins@cam.org> wrote:
>Is it just me or is there something missing?
>oscar# depmod -ae 2.4.7-pre5
>depmod: *** Unresolved symbols in /lib/modules/2.4.7-pre5/kernel/drivers/net/8139too.o
>depmod: cpu_raise_softirq
Works for me. Were you booted off the 2.4.7-pre5 kernel when you ran
depmod? If you were booted off another kernel, you must run depmod
with -F 2.4.7-pre5/System.map. If you were booted off the correct
kernel, cd to the top level 2.4.7-pre5 directory and run these
commands.
nm drivers/net/tulip/tulip.o | fgrep cpu_raise_softirq
nm vmlinux |
egrep '__k[^_]*_cpu_raise_softirq|\<cpu_raise_softirq\>' |
tee /dev/tty |
awk '/__ks..tab/{ printf "objdump -s -j %s --start-addr=0x" $1 " vmlinux | head -10\n",
$3 ~ /__ksymtab/ ? "__ksymtab" : ".kstrtab"}' | sh
prev parent reply other threads:[~2001-07-11 3:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-10 11:53 2.4.7-pre5 missing symbols? Ed Tomlinson
2001-07-10 12:18 ` Jeff Garzik
2001-07-11 3:54 ` Keith Owens [this message]
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=5194.994823658@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=tomlins@cam.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