Hello Gents!
Today I just got my first refurbished T1000 :)))) After updating fw to
latest version 6.7.12, I am trying to boot ofwboot.net and bsd.rd from a
tftp server without the usual rarp procedure as OBP of this machine allows
through setenv to do such a setup. For instance, there are people loading
linux this way: https://help.ubuntu.com/community/Installation/Sparc
My config is:
setenv network-boot-arguments
host-ip=10.9.9.100,router-ip=10.9.9.1,subnet-mask=255.255.255.0,hostname=T1000,file=tftp://
10.9.9.1/ofwboot.net
Where on 10.9.9.1 is a cross cable attached laptop with a tftp server
running (also dhcp if should be needed, but not in this case). Within the
tftpboot home on laptop I have copied "ofwboot.net", "bsd.rd" and a copy of
bsd.rd renamed as "bsd".
This is what happens:
-------------------
{0} ok boot net0
[...]
Boot device: /pci@7c0/pci@0/network@4 File and args:
1000 Mbps full duplex Link up
>> OpenBSD BOOT 1.4
Trying bsd...
1000 Mbps full duplex Link up
No response for RARP request
open /pci@7c0/pci@0/network@4/bsd: No such file or directory
Boot: bsd.rd
1000 Mbps full duplex Link up
No response for RARP request
open /pci@7c0/pci@0/network@4/bsd.rd: No such file or directory
Boot: tftp://10.9.9.1/bsd.rd
1000 Mbps full duplex Link up
No response for RARP request
open /pci@7c0/pci@0/network@4/tftp://10.9.9.1/bsd.rd: No such file or
directory
Boot:
---------------------
It looks like that I can load ofwboot.net, which then helplessly tries to
look for bsd kernel, which is present in the tftp home; also trying other
files like "bsd.rd" or "tftp://10.9.9.1/bsd.rd"; does not lead to any result.
Anyway, the fact that after failure to load I still get the "Boot:" prompt
suggests me that the problem could lie within ofwboot.net itself which,
without the rarp technique, is not maybe able to find where on the network
to load the kernel.
Is my analysis correct?
Should this apply, considering that nowadays it is starting to be more and
more common to have class T machines available, wouldn't it be great to
give ofwboot.net the ability to work with dhcp or, at least, to pass it
manually network parameters? After all, not everybody who needs to netboot
does it to run run diskless, it is very likely that a good share of them
(including me) just netboots to netinstall. Not to mention the bonus
flexibility that would be available in disaster recovery scenarios...
Thank you for your answers.
Paolo
