I currently have SuSE 9.1 Pro PXE/TFTP booting/autoinstalling working great with our 32-bit machines. My problem is that I can't seem to get this to also work with our x86_64 machines.
I don't know if there is a graceful way to separate 32 and 64-bit stuff in the /tftpboot directory, so what I initially tried to do was make an isolinux.cfg menu option which specified an alternate (64-bit) linux and initrd, but when it loads the 64-bit kernel and initrd, the machine immediately reboots.
I tried to boot it off the 32-bit kernel/initrd just to do the install, but as soon as it loads the data into ramdisk, it goes to a blue yast screen with the message "An error occurred during installation!" (very helpful) Switching to other consoles at this point reveals only a little more info, such as the messages: lockd:failed to open /var/lib/nfs/state: err=2 request_module: runaway loop modprobe binfmt-464x (5 of these)
Lastly, I backed up the /tftpboot directory and blew it away, making a brand new one with only stuff from the 64-bit distribution in there, and it behaved exactly like it did when I tried specifying the alternate linux and initrd (rebooted). Now this situation suggests that setting up 64bit network booting the same way as with the 32-bit stuff doesn't work with my 64-bit systems, and that there is something special I need to be doing for them.
Is there some documentation specific to 64-bit network booting / autoinstalling? Does it in fact differ from the 32-bit procedure (aside from having an x86_64 kernel/initrd/distro/control-files)? I know Anas is still working on the 9.1 docs, but has anyone successfully PXE/DHCP/TFTP/autoinstalled an AMD64 machine? Perhaps it is just a compatibility problem with my hardware?
The 64bit systems I'm installing are AMD Opteron 146's on Asus SK8N motherboards (nForce chipset). I've tried floppy booting, but it doesn't talk to the NIC correctly (not sure my problem would be avoided anyway). Otherwise I may go ask the suse-amd64 list as well.
Thanks in advance, -Charles Smith