>I issued "boot -protocols bootp eia0" on 164LX console.
>(SRM v5.8-1 on 164LX recognize 82559 NIC)
>Kernel is loaded with tftp session and
>some code size information is displayed.
>But as soon as the system switches to OSF PAL,
>"CPU halted" message appeared and system
>returned to console mode.

I was wrong. Kernel failed, not after switch to OSF PAL,
but before switch to OSF PAL.

Below is my netboot process.
Release 1.5 generic kernel is used.
Stopped PC (ff ff fc 00 00 65 57 d8)
was among the

   $ nm /netbsd | sort
   ...
   8867 fffffc00006552e8 R vga_accessops
   8868 fffffc0000657d98 R copyright
   ...

--------- netboot message -----

>>>boot -protocols bootp eia0
Trying BOOTP boot.

Broadcasting BOOTP Request...
Received BOOTP Packet File Name is: /tftpboot/NetBSD-alpha/netbsd
local inet address: 191.168.0.2
remote inet address: 192.168.0.1
TFTP Read File Name: /tftpboot/NetBSD-alpha/netbsd
netmask = 255.255.255.0
Server is on same subnet as client.
...............................................................
...............
bootstrap code read in
base = 200000, image_start = 0, image_bytes = 4e548b
initializing HWRPB at 2000
initializing page table at 3ffec000
initializing machine state
Setting affinity to the primary CPU
jumping to bootstrap code

halted CPU 0

halt code = 2
kernel stack not valid halt
PC = fffffc00006557d8

>>>


_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.