From: Matthew Smith <matt@kbc.net.au>
To: sparclinux@vger.kernel.org
Subject: MrCoffee Problem from i386 server
Date: Thu, 15 Sep 2005 12:15:53 +0000 [thread overview]
Message-ID: <43296329.1050001@kbc.net.au> (raw)
Hi
I have been trying to get Linux - any Linux - to work with my MrCoffee
Javastation.
My server setup:
Suse Linux 9.2/x86
rarpd V1.1
isc-dhcpd V3.0.1
tftpd V0.39 Release 2.2
MrCoffee is running OpenBoot 2.30 and has 65Mb of RAM.
After a few network problems, which I cleared up with my friend Mr
Tcpdump, the Javastation can get an address and load a boot file.
The problem is that EVERY file I try to send gives the "The file just
loaded does not appear to be executable\nok" error.
My research regarding this messages suggests that the files I am sending
are not in aout format. However, I question this, as the problem occurs
with the latest version of Prol (which I don't think I really need as
I've got the old firmware), the pre-compiled kernels presented in the
HOWTO and also a Slackware kernel that is supposed to work.
Would all of these have been presented in a non-aout format, or is there
something else going on here, like some sort of file corruption in the
transmission process?
On a related matter - just where does one get elf2aout for Linux/x86?
All the Google references I found were for NetBSD. I managed to find
one version of elf2aout.c but, when I tried to compile it, I found that
I was lacking a large number of dependencies.
Unfortunately, I don't have any other Sun hardware to play with at the
moment.
Cheers
M
--
Matthew Smith
South Australia
http://www.kbc.net.au
next reply other threads:[~2005-09-15 12:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 12:15 Matthew Smith [this message]
2005-09-15 12:27 ` MrCoffee Problem from i386 server Chris Newport
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=43296329.1050001@kbc.net.au \
--to=matt@kbc.net.au \
--cc=sparclinux@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.