linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Stephan Ruettiger (r0337c)" <r0337c@email.sps.mot.com>
To: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: no symbol-table - /proc-fs empty
Date: Thu, 23 Mar 2000 07:57:17 +0100	[thread overview]
Message-ID: <38D9C04D.A1F6B259@email.sps.mot.com> (raw)


Hello all,

i use a MBX860 which is connectet via NFS to its root filesystem. The
kernel i use is a 2.2.13 which has /proc filesystem enabled. After the
MBX-board is booted i have no access to the symbol table.
To be shure it's not a failure in my modul, i use the easiest one i
found (hello-modul from Alessandro Rubini). Below you can see what's
happend after the insmod command.

#insmod -v hello.o
Section 1: (.text) at 0x18537b8
Section 2: (.rela.text) at 0x1854e98
Section 3: (.data) at 0x1853830
Section 5: (.modinfo) at 0x1853830
Section 6: (.sdata) at 0x1853830
Section 7: (.rodata) at 0x1853838
Section 8: (.comment) at 0x1853868
Section 9: (.shstrtab) at 0x1854ee8
Section 10: (.symtab) at 0x1854f48
Section 11: (.strtab) at 0x18550a0
textseg = 0x18537b8
bss_size = 25507984
last byte = 0x1854890
module size = 4312
jump table = 0x1853890
versioned kernel: no
versioned module: no
ELF kernel
ELF module
printk undefined
Loading failed! The module symbols (from linux-2.2.13) don't match your
linux-2.2.13
#

Also the /proc directory is empty.
I have no idea and so i would be happy if anyone can tell me what's
going wrong.


------------------------
Stephan Ruettiger
Motorola Munich
r0337c@email.sps.mot.com
------------------------

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

                 reply	other threads:[~2000-03-23  6:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=38D9C04D.A1F6B259@email.sps.mot.com \
    --to=r0337c@email.sps.mot.com \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).