My ks.cfg has the installer using a static IP address to do an NFS install for RH 6.2. The hardware for the new host is a Asus P2XBL dual-processor board with one PII present, a 3Com 905B card (which the installer correctly identifies and configures), and generic video card, IDE hard drive, floppy drive, and CD drive. There are no messages on console 4 indicating errors, and the last messages on console 3 are about insmod'ing the sunrpc, lockd, and nfs modules. The installer then dies on a signal 11 and shuts down (prompts me to reboot, etc). The ks.cfg also disables DNS on the interface.
I also downloaded the updated boot images as specified in the updates/errata section of the support pages. No luck there, either.
I tried to use the new boot.img with a local CD, and then (post-install) mount an NFS share. The server logs claim it received a valid and authenticated mount request for the appropriate NFS partition, but an directory listing on the client doesn't find the partition to be mounted. The insmod'ing of the appropriate kernel modules silently fails. Sorry for the constant updates, BTW.
Sent to test lab to attempt to reproduce.
For whatever reason, the install will bomb in the described manner if the '--dir' specifier does not preceed the NFS directory you want to mount. No idea why the insmod fails if this is left out, though.
hmmmm ... we haven't seen that behavior here in our test lab ... could you attach the kickstart file (ks.cfg) you are having the problem with ...?
Please reopen this bug if you continue to have problems.