Hi, There have been various posts, but I still don't get everything accomplished. Now I really need the initrd method to get around the (known) e1000 problem on x/t60 thinkpad, where fai-kernels based Installations don't work.
One thing that definitely doesn't work, is described in http://www.mail-archive.com/[EMAIL PROTECTED]/msg04404.html IMHO the main blocker to get rid of gthe fai-kernels. Still, when I circumvent this problem by entering the nfs root server location in the pxe config file, I have the next trouble: First, the kernel and initrd are booted correctly, and nfsroot is also booted nicely. But then, the client's resolv.conf is not set "right", and therefore my faiserver isn't found: The resolv.conf that is used on the install client is the same as the one on the faiserver (copied from NFSROOT/etc/resolv.conf-installserver). This doesn't work, because the faiserver is also the nameserver, so the client tries to resolve stuff from 127.0.0.1, which doesn't work. I can hack it to work by copying a correct resolv.conf to NFSROOT/etc/resolv.conf-installserver, but I just don't understand why and where the installserver resolv.conf is copied into /tmp/etc/resolv.conf ( where NFSROOT/etc/resolv.conf points to), instead of using the correct dhcp information. Maybe just my configuration is a bit odd, but I don't really see how this causes such a problem - in all other installations, without the initrd stuff, everything runs fine, resolv.conf's are set right and installs run nice. I am running FAI 2.10.x on a sarge server (but the initrd is made on etch, so it contains quite up to date initrd scripts). Henning
