netbooting alphastation 500 with current debian
after spending the better part of a day reading up on the various
netbsd, openbsd, and linux instructions for netbooting an alphasation
500, i have finally gotten the alpha to boot with the image from
debian.org (im sorry, offhand I dont have its URL).
i've got this entry in /etc/bootptab:
idiot:\
:ht=ether:\
:ha=0000F823B3FE:\
:sm=0xFFFF0000:\
:lg=10.1.1.1:\
:ip=10.1.4.7:\
:sa=10.1.1.200:\
:hn:\
:gw=10.1.1.1:\
:bf=alpha.img:\
:bs=4487002:\
:vm=auto:
(yes, the machine's name is idiot, long story)
the various alpha settings are:
>>>sho
auto_action BOOT
boot_dev ewa0.0.0.6.0
boot_file
boot_osflags
boot_reset ON
bootdef_dev dka0.0.0.9.0
booted_dev
booted_file
booted_osflags
bus_probe_algorithm old
char_set 0
console serial
controlp on
dump_dev
enable_audit ON
ewa0_arp_tries 9
ewa0_bootp_file alpha.img
ewa0_bootp_server envy
ewa0_bootp_tries 3
ewa0_def_ginetaddr 10.1.1.1
ewa0_def_inetaddr 10.1.4.7
ewa0_def_inetfile
ewa0_def_sinetaddr 0.0.0.0
ewa0_def_subnetmask 255.255.0.0
ewa0_ginetaddr 0.0.0.0
ewa0_inet_init bootp
ewa0_inetaddr 10.1.4.7
ewa0_inetfile /export/netboot/idiot/alpha.img
ewa0_loop_count 3e8
ewa0_loop_inc a
ewa0_loop_patt ffffffff
ewa0_loop_size 2e
ewa0_lp_msg_node 1
ewa0_mode Full Duplex, Twisted-Pair
ewa0_protocols BOOTP
ewa0_sinetaddr 10.1.1.1
ewa0_tftp_tries 9
mop_debug OFF
mop_password 00-00000000-00000000
mop_version 1
mopv3_boot OFF
os_type OpenVMS
pal OpenVMS PALcode V1.20-0, Tru64 UNIX PALcode
V1.22-0
pci_parity off
version V7.2-2 Apr 4 2000 17:17:43
Some notes if anyone cares to add them to the documentation:
First, bootpd "ignored" connections from idiot until idiot asked for
envy (the bootp server) by name rather than ip. I havent the foggiest
why this might be. Second, the gw, bs, sm, and sa variables were
*mandatory* in bootptab. They aren't for sparcs. This may confuse users
who have been netbooting other architectures. Third, the alpha *really*
wants to use the mops stuff. In order to make it look at bootp (i did
actually try to find a way to build a mops server for it, without
luck), you need to set the ewa0_inet_init and ewa0_protocols variables
(they are slightly different for the intel cards).
So, this is where I get to:
>>>boot ewa0
System will be reset prior to boot.
ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.
ef.ee.ed.ec.eb.ea.e9.f4.e8.e7.e6.e5.e4.
Digital AlphaStation 500/266
Console V7.2-2 Apr 4 2000 17:17:43
CPU 0 booting
(boot ewa0.0.0.6.0)
Trying BOOTP boot.
Broadcasting BOOTP Request for file: alpha.img
Received BOOTP Packet File Name is: /alpha.img
local inet address: 10.1.4.7
remote inet address: 10.1.1.200
TFTP Read File Name: /alpha.img
netmask = 255.0.0.0
Server is on same subnet as client.
.....................................................................
bootstrap code read in
base = 14a000, image_start = 0, image_bytes = 44775a
initializing HWRPB at 2000
initializing page table at 13c000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
Linux/AXP bootp loader for Linux 2.4.18-generic
Switching to OSF PAL-code .. Ok (rev 1000000020116)
Initrd positioned at 0xfffffc0001214000
Loading the kernel...''
(note that it also ignores both the netmask specified in srm, and the
netmask offered by bootpd -- this appears to be a bug, but not serious
for 10/8 networks).
so i first thought that maybe i had neglected to tell linux i wanted a
serial console. but the box is not responding to pings at all, and just
doesnt seem to be up. i'm not seeing any traffic from it on the network.
i'm real excited in that i've got bootp and tftp working to the degree
the alpha will load an image. anyone care to speculate on how to build
an image it will like?
thanks!
alex
Reply to: