Eugen Paiuc wrote :
What's your inetd.conf line about tftp ?tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd /srv/tftp -l
If r4.img is well placed in /srv/tftp with appropriate read permissions, as the dhcp server seems to be talking well, I'd try putting in the dhcpd.conf block concerning your O2 the line :
filename "/srv/tftp/r4.img"; and then try to boot with bootp()r4.img I think it should work without even specifying the filename...You could (might ?) see something in /var/log/messages. Else you might try to see who says what to who with a tcpdump -i eth0... desperate means :/
Sometimes the PROM environment variables can mess the netboot up... but the "Unable to execute bootp()192.168.1.22:/r4.img" doesn't seem to match this situation...
Guillaume