BOOTREQUEST from prom via eth0 (non-rfc1048) Remote boot failure indigo2 prom errors
Indy fans, can you help please:
After issuing the bootp() prom command:
>> boot -f bootp():/tftpboot/tftpboot.img
No server for :/tftpboot/tftpboot.img.
Your netaddr environment variable may be set incorrectly, or
the net may be too busy for a connection to be made.
Unable to load bootp():/tftpboot/tftpboot.img: could not connect to remote
ser.
>>
Who has experienced this error in "/var/log/messages" (in the redhat 7.2
server)
____________________________________________________________________________
__
Dec 11 10:27:21 rh7hda3 dhcpd: BOOTREQUEST from 08:00:69:07:be:32 via eth0
(non-rfc1048)
Dec 11 10:27:21 rh7hda3 dhcpd: BOOTREPLY for 147.10.121.98 to 147.10.121.98
.
.
this repeats about 8 times
.
____________________________________________________________________________
___
Note the " non-rfc 1048"
Note also that BOOTREQUESTs are:
OK from Kernel
but
NOT OK from prom.
Proof:
Booting from hard disk:
>>boot -f kernel-image-2.4.0-test9-ip22-r4k root=/dev/sda1
produces in "/var/log/messages" in the redat 7.2 server
Dec 11 10:39:06 rh7hda3 dhcpd: BOOTREQUEST from 08:00:69:07:be:32 via eth0
Dec 11 10:39:06 rh7hda3 dhcpd: BOOTREPLY for 147.10.121.98 to 147.10.121.98
(08:00:69:07:be:32) via eth0
This must be affecting alot of indy fans.
Does the
(non-rfc1048)
mean something is incompatible?
I have trried
echo 2048 32767 > /proc/sys/net/ipv4/ip_local_port_range
echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc
to no affect.
Yes I have installed debian OK using redhat 5.2 but the newer versions seem
to allude me.
But I want to NFSboot & net boot etc
Thanks for your help
Roger Salisbury
Reply to: