yadd unter Linux booten

Hi,
ich versuche gerade meine yadd direkt von Linux zu booten. Das ewige hin und her booten stinkt mir.
Dabei verwende ich folgende Konfiguration:

/etc/inetd.conf
bootps dgram udp wait root /usr/sbin/bootpd bootpd -c /home/tux/dbox2/tftpboot

/etc/dhcpd.conf
default-lease-time 600;
max-lease-time 7200;

authoritative;

ddns-updates off;
ddns-update-style none;

subnet 192.168.1.0 netmask 255.255.255.0 {
}

host nokia {
# fixed-address 192.168.1.67;
fixed-address nokia;
hardware ethernet 00:50:9c:43:12:d0;
allow bootp;
server-name "192.168.1.101";
filename "/ppcboot";
}

/etc/sysconfig/atftpd
ATFTPD_OPTIONS="--daemon "
ATFTPD_USE_INETD="no"
ATFTPD_DIRECTORY="/home/tux/dbox2/tftpboot"

/etc/exports
/home/tux/dbox2 *(rw,no_root_squash)

/etc/hosts und /etc/ethers sind angepasst, alle deamons laufen.
Ich bekomme beim Versuch 'ne yadd zu booten folgende Einträge in der /var/log/messages

Mar 15 08:29:02 tux dhcpd: BOOTREQUEST from 00:50:9c:xx:xx:xx via eth0
Mar 15 08:29:02 tux dhcpd: BOOTREPLY for 192.168.1.67 to nokia (00:50:9c:xx:xx:xx) via eth0
Mar 15 08:29:02 tux tftpd[1985]: Serving /ppcboot to 192.168.1.67:2001
Mar 15 08:29:03 tux dhcpd: ip length 328 disagrees with bytes received 392.
Mar 15 08:29:03 tux dhcpd: accepting packet with data after udp payload.
Mar 15 08:29:03 tux dhcpd: BOOTREQUEST from 00:50:9c:xx:xx:xx via eth0
Mar 15 08:29:03 tux dhcpd: BOOTREPLY for 192.168.1.67 to nokia (00:50:9c:xx:xx:xx) via eth0
Mar 15 08:29:03 tux tftpd[1986]: Serving /tftpboot/logo-lcd to 192.168.1.67:1361
Mar 15 08:29:03 tux dhcpd: ip length 328 disagrees with bytes received 392.
Mar 15 08:29:03 tux dhcpd: accepting packet with data after udp payload.
Mar 15 08:29:03 tux dhcpd: BOOTREQUEST from 00:50:9c:xx:xx:xx via eth0
Mar 15 08:29:03 tux dhcpd: BOOTREPLY for 192.168.1.67 to nokia (00:50:9c:xx:xx:xx) via eth0
Mar 15 08:29:03 tux tftpd[1987]: Serving /tftpboot/logo-fb to 192.168.1.67:1619
Mar 15 08:29:05 tux dhcpd: ip length 328 disagrees with bytes received 392.
Mar 15 08:29:05 tux dhcpd: accepting packet with data after udp payload.
Mar 15 08:29:05 tux dhcpd: BOOTREQUEST from 00:50:9c:43:12:d0 via eth0
Mar 15 08:29:05 tux dhcpd: BOOTREPLY for 192.168.1.67 to nokia (00:50:9c:xx:xx:xx) via eth0
Mar 15 08:29:05 tux tftpd[1988]: Serving /tftpboot/kernel-cdk to 192.168.1.67:3289

ip length 328 disagrees with bytes received 392 - damit weiß ich nichts anzufangen. Da scheint mir was in die Suppe zu spucken.
Hat wer 'ne Idee dazu?

CU Richie