List Info

Thread: booting amd64 kernel




booting amd64 kernel
user name
2006-04-30 16:43:42
I've got a pair of custom kernels for my host, roxy.
One is i386 the other is amd64, roxy is an amd64 host.

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:

ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV),
statically linked, not stripped
ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
statically linked, not stripped

I presume the bootstrap code is blocking since it's
a different arch?

How do I fix this so I can boot up the amd64 kernel?

// George


-- 
George Georgalis, systems architect, administrator
<IXOYE><
http://galis.org/
cell:646-331-2027 mailto:georgegalis.org
booting amd64 kernel
user name
2006-04-30 17:03:17
On Sun, Apr 30, 2006 at 12:43:42PM -0400, George Georgalis
wrote:
> 
> I've got a pair of custom kernels for my host, roxy.
> One is i386 the other is amd64, roxy is an amd64 host.
> 
> 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:
> 
> ELF 64-bit LSB executable, AMD x86-64, version 1
(SYSV), statically linked, not stripped
> ELF 32-bit LSB executable, Intel 80386, version 1
(SYSV), statically linked, not stripped
> 
> I presume the bootstrap code is blocking since it's
> a different arch?
> 
> 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.

-- 
Quentin Garnier - cubecubidou.net - cubeNetBSD.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.
booting amd64 kernel
user name
2006-04-30 17:22:54
On Sun, Apr 30, 2006 at 07:03:17PM +0200, Quentin Garnier
wrote:
>On Sun, Apr 30, 2006 at 12:43:42PM -0400, George
Georgalis wrote:
>> 
>> I've got a pair of custom kernels for my host,
roxy.
>> One is i386 the other is amd64, roxy is an amd64
host.
>> 
>> 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:
>> 
>> ELF 64-bit LSB executable, AMD x86-64, version 1
(SYSV), statically linked, not stripped
>> ELF 32-bit LSB executable, Intel 80386, version 1
(SYSV), statically linked, not stripped
>> 
>> I presume the bootstrap code is blocking since
it's
>> a different arch?
>> 
>> 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.

That sounds a bit tricky to switch.

>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.

So, for this kick around host, I should probably reinstall
with an
amd64 cd/pxe and move on from there. okay.

Thanks,
// George


-- 
George Georgalis, systems architect, administrator
<IXOYE><
http://galis.org/
cell:646-331-2027 mailto:georgegalis.org
no wm0 Re: booting amd64 kernel
user name
2006-04-30 19:38:41
On Sun, Apr 30, 2006 at 01:22:54PM -0400, George Georgalis
wrote:
>On Sun, Apr 30, 2006 at 07:03:17PM +0200, Quentin
Garnier wrote:
>
>>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.
>
>So, for this kick around host, I should probably
reinstall with an
>amd64 cd/pxe and move on from there. okay.

*sigh* my wm0 interface doesn't work in amd64 3.0 cd
install.

wm0 is configured in dmesg
accepts an ip with ifconfig
1000baseT full-duplex media is auto selected
switch lights blink when I ping the LAN hosts, no pings
return

PR time?

Might I have better luck with a current kernel?
(this device has been without problem in i386)

(FWIW, there is an nVidia on-board interface, which doesn't
show
up in dmesg and was not expected to work, when set to auto
or
disabled in BIOS)

// George


-- 
George Georgalis, systems architect, administrator
<IXOYE><
http://galis.org/
cell:646-331-2027 mailto:georgegalis.org
[1-4]

about | contact  Other archives ( Real Estate discussion Medical topics )