Sorry dcantrell, I don't want to be the bearer of bad news. While trying to do a kickstart install using anaconda 11.4.1.38 this morning with the ks.cfg file on a local http server, loader would hang at the "waiting for hardware to initialize ..." message. The funny thing is I can do a normal install with install.img and all the packages on that same webserver just fine (using the default dhcp settings), so this seems to be something specific to the kickstart path (where the network gets brought up earlier). I'll try to catch you on irc between 21:00 - 22:00 tonight, so thats between 9:00 - 10:00 for you, in case you need me to run any tests to pin this down.
p.s. I've been using the same ks setup with 11.4.1.32 and their it works fine, so this is a regression which happened between 11.4.1.32 and 11.4.1.38
"Waiting for hardware to initialize" is all udevsettle running. Are there any messages on tty4 indicating the kernel's waiting on something to happen? I have installs get hung up from time to time when a USB key is plugged into a certain port. They just sit there waiting, with the kernel spewing messages on tty4. Once the USB key is removed, everything proceeds. You could be seeing something similar.
Ok, I just tried this again, there are interesting messages on tty3, esp. the last one: INFO: getting kickstart file INFO: only have one network device: eth0 INFO: sending dhcp request through device eth0 ERROR: failed to start NetworkManager (6)
*** Bug 464310 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 462083 ***