Test 1, 2 & 3. With this new sparc64 netboot image, while typing 'boot net' on OBP, getting this error, on my Sun Fire V440 server.
Boot device: /pci@1c,600000/network@2 File and args: /pci@1c,600000/net work@2: 100 Mbps full duplex link up Requesting Internet Address for 0:3:ba:62:8d:61 ERROR: /packages/obp-tftp: Last Trap: Fast Data Access MMU Miss A clean reboot doesn't help. On my tftpdsrv. # cd /var/log # tail -f syslog Apr 3 10:44:58 tftpdsrv rarpd[13068]: RARP request from 00:03:ba:62:8d:61 on eth0 Apr 3 10:44:58 tftpdsrv rarpd[13068]: RARP response to 00:03:ba:62:8d:61 192.168.1.230 on eth0 # cd /var/lib/tftpboot # ls -l lrwxrwxrwx 1 30 Apr 1 15:03 C0A801E6 -> debian-sparc64-sid-netboot.img -rw-r--r-- 1 22326288 Apr 1 14:48 debian-sparc64-sid-netboot.img -rw-r--r-- 1 9348048 May 31 2016 debian-sparc-wheezy-netboot.img -rw-r--r-- 1 8659728 Apr 14 2010 gentoo-sparc64-20100413.tftpboot # file debian-sparc64-sid-netboot.img debian-sparc64-sid-netboot.img: sparc executable # file debian-sparc-wheezy-netboot.img debian-sparc-wheezy-netboot.img: sparc executable Question: Why is the sprac64 image that big? Doing the the same with the wheezy image, the server does boot, true. Thanks, Frans van Berckel
