From: David J. Bianco <bianco@jl...> - 2002-06-17 14:55:12
Hello, all. I've recently been trying to boot a Linux 2.4
kernel on a Neoware 4000 thin client (www.neoware.com). I've
run into a problem that I would like some advice with.
The machine uses an RTL8139 integrated NIC with the standard PCI
settings. Due to the fact that it uses DiskOnChip, I compiled
Etherboot with RELOCADDR=0x84000. I invoked mkbni-linux with
"--rootdir=rom --ip=rom --relocseg=0x8000 --first16".
The machine successfully loads Etherboot from the TFTP server
and transfers the kernel. When the kernel loads, I get the
Linux Net Boot Image Loader Version 0.8.1 (mknbi-linux)
Copyright (C) 1996,1997 G. Kuhlmann and M. Gutschke
GPLed by G. Kuhlmann
Invalid vendor magic ID
Boot from (N)etwork or from (L)ocal?
Then it tries to load the kernel again, but is unsuccessful for
some reason (perhaps Etherboot left the NIC in a weird state?)
In any case, I guess the real problem is the vendor ID. I've
seen references on this list to to imggen, which supposedly
solves this problem for 3COM boot agents, but that doesn't seem
to apply in this case. There is a boot agent involved, but
it's an RTL8139 agent and not a 3COM agent.
What do you guys think? Has anyone else seen this before?
David J. Bianco, GSEC <bianco@...>
Thomas Jefferson National Accelerator Facility
The views expressed herein are soley those of the author and
not those of SURA/Jefferson Lab or the US DOE.