Subject: RE: Port to Sun 386i
To: Zach Lowry <zach@zachlowry.net>
From: Zach Lowry <zach@zachlowry.net>
List: port-sun3
Date: 06/25/2003 22:01:18
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> -----Original Message-----
> From: Zach Lowry [mailto:zach@zachlowry.net]
> Sent: Wednesday, June 25, 2003 9:22 PM
> To: Zach Lowry
> Subject: RE: Port to Sun 386i
>
> NVRAM boot device...ie(0,0,0)
>
>
> Booting from tftp server at 192.168.0.13
>
>
> Downloaded 24372 bytes from tftp server.
>
>
>
>
>
> Boot: Device ie(0,0,0): invalid boot block
>
> Anyone know what that's all about?
>
Because I'm an idiot, that's what it's all about. I imagined that the
bootloader was shared between Sun3 and Sparc from the NetBSD Docs,
and didn't have time this afternoon to verify. I thought it might of
been some Forth magic that I didn't have the time/desire to
understand. :)
Regardless, I believe I'll try and compile the Sun3 bootloader with
an i386 target and see what happens. If not that, I'll try a
roadrunner target. (Does GCC still have that?)
- -----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.4
iQA/AwUBPvphYoHWQmQc5olOEQLBogCeOnvosx2lMquC7A62UJz6Jhdm014AoLLE
wM/IRrp2soOHBjcr3im62dd0
=/sOf
- -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.4
iQA/AwUBPvph4oHWQmQc5olOEQKMjACfZ388quhHQNTNcfC811FpdV8TXVwAoJCe
Uc5FO+uOYgVZf+Te3Lm8j6yt
=nLDR
-----END PGP SIGNATURE-----