--ufMBWnG1WFkAvCRz
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Apr 30, 2006 at 12:43:42PM -0400, George Georgalis wrote:
>=20
> I've got a pair of custom kernels for my host, roxy.
> One is i386 the other is amd64, roxy is an amd64 host.
>=20
> When I boot my x86 kernel, all is fine, but with the
> amd64 kernel I get "Inappropriate file type or format"
> at bootstrap. Their types are:
>=20
> ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), statically linke=
d, not stripped
> ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically link=
ed, not stripped
>=20
> I presume the bootstrap code is blocking since it's
> a different arch?
>=20
> How do I fix this so I can boot up the amd64 kernel?

Use bootblocks from NetBSD/amd64.  NetBSD/i386's bootblocks can't boot
64-bits kernel.

Note that booting an amd64 on an i386 userland is STRONGLY discouraged at
the moment.  Except for a very specific configuration, it won't reach
multi-users.

--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"When I find the controls, I'll go where I like, I'll know where I want
to be, but maybe for now I'll stay right here on a silent sea."
KT Tunstall, Silent Sea, Eye to the Telescope, 2004.

--ufMBWnG1WFkAvCRz
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)

iQEVAwUBRFTt1NgoQloHrPnoAQK3fQgAmIChRNtBU/3Kmk3Gwg59I8E/uY5R4hV0
MKcdme7FaehLm2gWQsxqnJs3Gy7flgl8LvGHsjxDCR+erd/KfUoZZLuHyDoVFJ6t
QAMNSim2ItAFcu0REOoWE7yX5UT3sm7lNA4v/PPwIbXTmrU8SVFgnkj3Jxuoj86r
x5Lvb6xR9HjaF9EnSGv7iQplaHk2sd787wz45rZ41cB00Jk/uI+DOrMGn9Tt4R/T
VvpPj2QBiwN6VdFEaooaens2j5sMMFnxIuHIwx2OFRFZHf6JRIHxNAxVoy/zA3Rv
JmciNaEv+UUrTtKfSN9MiMPcf5OOgR3mONrbKsL6t9OK1cCMa2yxsg==
=YThs
-----END PGP SIGNATURE-----

--ufMBWnG1WFkAvCRz--