From: Magnus Damm <eramdam@kieray1.p.y.ki.era.ericsson.se>
To: linuxppc-dev@lists.linuxppc.org
Cc: helmut.buchsbaum@siemens.at
Subject: Re:Problems starting up system on a MPC823FADS
Date: Fri, 18 Dec 1998 13:17:10 +0100 (MET) [thread overview]
Message-ID: <199812181217.NAA21363@kieray1> (raw)
>I try to get a linux system up and running on a Motorola MPC823FADS
I'm currently running linux on MPC860ADS and the MBX.
MBX:
Works fine.
I've succeeded loading linux from my floppydrive (yea!) and via ethernet.
MPC860ADS:
I use MPC8BUG to set up some registers and load vmlinux.
today it runs linux from initrd. I've mounted nfs and it works fine.
But nfs as root doesn't.
I added some debug printouts to open() and nfs read() and compared
nfs with initrd.
initrd:
VFS: Mounted root (ext2 filesystem).
open file '/dev/console' returns 0x00000000
open file '/etc/ld.so.preload' returns 0xfffffffe
open file '/etc/ld.so.cache' returns 0xfffffffe
open file '/lib/libtermcap.so.2' returns 0x00000003
open file '/lib/libc.so.6' returns 0x00000003
open file '/etc/nsswitch.conf' returns 0xfffffffe
open file '/lib/libnss_compat.so.1' returns 0xfffffffe
open file '/usr/lib/libnss_compat.so.1' returns 0xfffffffe
open file '/lib/libnss_files.so.1' returns 0xfffffffe
open file '/usr/lib/libnss_files.so.1' returns 0xfffffffe
open file '//.bashrc' returns 0xfffffffe
open file '//.bash_history' returns 0xfffffffe
open file '/etc/termcap' returns 0xfffffffe
bash#
nfs:
VFS: Mounted root (nfs filesystem).
Freeing unused kernel memory: 36k init 28k prep
open file '/dev/console' returns 0x00000000
nfs: read(bin/sh, 128@0)
nfs: read(bin/sh, 160@52)
nfs: read(bin/sh, 13@244)
nfs: read(lib/ld.so.1, 128@0)
nfs: read(lib/ld.so.1, 96@52)
open file '/etc/ld.so.preload' returns 0xfffffffe
open file '/etc/ld.so.cache' returns 0xfffffffe
open file '/lib/libtermcap.so.2' returns 0x00000003
open file '/lib/libc.so.6' returns 0x00000003
open file '/etc/nsswitch.conf' returns 0xfffffffe
open file '/lib/libnss_compat.so.1' returns 0xfffffffe
open file '/usr/lib/libnss_compat.so.1' returns 0xfffffffe
open file '/lib/libnss_files.so.1' returns 0xfffffffe
open file '/usr/lib/libnss_files.so.1' returns 0xfffffffe
open file '' returns 0xfffffffe
open file '/usr/local/bin/' returns 0x00000003
reading 80 bytes from handle 0x00000003 - returned 4294967275
reading 1024 bytes from handle 0x00000003 - returned 4294967275
[nothing more]
>I switched from gcc-2.8.1 to egcs-1.1b as a cross compiler (x86 -->
>PPC), but without any success.
I think I've got the same problem as you have.
I use egcs-2.91.57. It generates code that works on my MBX-board.
I've read the mbx-documentation several times, and I don't think
it tells us everything about the register-setups.
My guess is that our boot-code/script doesn't initialize everything.
Or the ethernetdriver assumes more than the ethernetaddress.
>Probably one of you can give me even the slightest hint,
>how I could get any futher!
I know that Dan Malek has released his boot-code for the FADS.
Have a look in ftp://linuxppc.cs.nmt.edu/pub/linuxppc/embedded/
Let me know if you find out anything about the nfs-root problem!
Another thing:
There seem to be quit a lot of people around hacking embedded linux.
Why not create a board.h file?
board.h:
#if defined(CONFIG_MBX)
#include <mbx.h>
#elif defined(CONFIG_FADS)
#include <fads.h>
#elif defined(CONFIG_ADS)
#include <ads.h>
#else
#error "No board"
#endif
Cheers /
Magnus
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
reply other threads:[~1998-12-18 12:17 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=199812181217.NAA21363@kieray1 \
--to=eramdam@kieray1.p.y.ki.era.ericsson.se \
--cc=helmut.buchsbaum@siemens.at \
--cc=linuxppc-dev@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).