[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: 8e9800 Fast Data Access MMU Miss

Network boot is the only way I ever install anything on sparc.

Yeah but given all these fancy firmware restrictions (not to mention
that "network booting" inherently means two machines), one can get
really creative.


Like... how do you boot an ISO file? (E.g. Solaris DVD rescue prompt.)

I do that all the time.  Essentially ensure you have the mac address of
the physical network interface that will do the initial ARP/RARP call
out.  Get that with forth .properties like so :

ok cd /pci@1f,0/pci@1,1/
ok ls
f009b2d0 usb@5,3
f009337c network@5,1
f008f780 ide@d
f008981c usb@c,3
f00818f0 network@c,1
f007d18c isa@7
f007cf84 lomp@3
f00793b8 pmu@3
f0075bcc ebus@c
ok cd network@5,1
ok .properties
local-mac-address        00 03 ba 0a 1b 03
assigned-addresses       82012910 00000000 e0440000 00000000 00020000
                         82012930 00000000 e4000000 00000000 00400000
shared-pins              mii
model                    SUNW,pci-eri
version                  1.7
compatible               pci108e,1101
device_type              network
.  etc etc

So that "00:03:ba:0a:1b:03" goes into /etc/ethers on the remote system
that is going to listen for the tftp traffic.  Setup bootparams in /etc
and also throw in an ip address into /etc/hosts.  The call out "boot
devname" where devname is the full path to the nic interface or a
firmware alias.  Running wireshark somewhere will show all the traffic
back and forth and then the sparc unit will call for a file name which
is just capital hex of the ip address it was issued after the ARP/RARP

To make a long story short all one needs is a symlink in the tftp boot
directory from the capital hex address to some netboot image. The rest
happens after that arrives and runs.  However I think we are limited to
the 10MB size of the file fetched.


Reply to: