On 10/19/2016 23:46, Waldemar Brodkorb wrote:
Hi Joshua, Joshua Kinard wrote,
Have you tried 64K PAGE_SIZE by chance? I use that setting on all of my SGI systems except for the IP27, which has a peculiar Oops crop up under 64K, so that machine boots 16K PAGE_SIZE at the moment. You actually get a nice performance bump on 16K or 64K versus the standard 4K. The testing netboot image I ran on my IP27 w/ 16K showed no ill effects, but I still need to do 64K on the O2 and Octane.
I have not tested 64k, but I hope it will work fine. I will check as soon as I get my O2 netbooting.
It seems I am too stupid to get the machine netbooted. I tried dnsmasq (dhcp,tftp included) and dhcpd/atftpd combination. No success so far. I have running a small Linux on my Solidrun cubox-i as bootserver for my other machines, which normally just works fine.
Could you share your bootserver details and the command you are using to boot a system?
For better experience I just want to boot OpenBSD bsd.rd.IP32 file to see that my bootserver works. Afterwards I want to try my cross-compiled kernel.
I have netbooted so many machines, even old classic unix hardware, (with mopd, rarpd, bootparamd, ...) feeling stupid right now.
Any hints?
My netbooting setup is standard dhcpd with old-school netkit-tftpd (too lazy to set up the more maintained tftp servers). The bit probably hanging you up is a simple /proc tuning directive needed for most SGI systems, so try executing this line on the netboot server:
echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc
That's needed for almost all of the SGI systems to netboot properly. IP22 (Indy/Indigo2) systems need this additional /proc tuning to limit the ephemeral port range:
echo "2048 32767" > /proc/sys/net/ipv4/ip_local_port_range
To actually do the netboot, make sure "netaddr" is unset in the ARCS environment:
unsetenv netaddr
Then try:
bootp(): <kernel args>
E.g., for my Octane, I typically use: bootp(): console=tty0 root=/dev/md0 consoleblank=0
And my IP27: bootp(): console=ttyS0,9600 root=/dev/md0
If you have no kernel args to pass, then just use "bootp():"
Just make sure your dhcpd is set up to do BOOTP requests properly and that you can tftp get the kernel image from the server using a tftp client, and it should JustWork(). If you have issues with the kernel itself booting, let me know and I can roll a kernel for you. I haven't tested O2's in a while, so I don't know if there's any surprises waiting in the 4.7 or 4.8 code.