On 03/06/2012 12:15 PM, Tom H wrote:
I'd*completely* misunderstood what you are doing so my earlier
question wasn't really relevant. Sorry.
No worries here.
IIUC, you're copying the pxe vmlinuz and initrd.img to your remote
server's "/boot" and creating a new grub.conf entry to point to these
two files and appending "ks=...", "ksdevice=...", "vnc", and
"vncpassword=..." to the kernel line.
Does helping the network setup with "ip=dhcp" or "ip=<ip-address>
netmask=<netmask> gateway=<gateway> dns=<dns>" make the install go
past the NIC selection?
Haven't tried that, but I'm kind of skeptical since it still won't know
which NIC to apply those settings to. I'll give it a try probably
tomorrow morning.
Someone's already asked you but I have to ask again. Are you*sure*
that you aren't using an earlier vmlinuz/initrd.img because there'd
been a problem previously with the same symptom that you're
experiencing.
Yes, I'm sure they are 6.2 versions. Even pulled a fresh copy and
compared. File size is identical and diff saw no diff.
I've tested this setup on a few different systems. Three of them have
dual NIC's and two of those have failed, one has worked without a
hitch. I started this thread after the second system failed, but this
morning I tested on a dual NIC system that is completely different
hardware and got the success. So this could be something specific to
the hardware setup on those two systems, they are almost identical. I'm
gonna play with them a bit more to see what I can figure out.
I do know that it works great on a system with a single NIC, I did 3
installs this way today. On one MicroWay box (Tyan S2915 motherboard)
that has dual on board NICs it took the ksdevice parameter and went
through the install no problem.
--
Stephen Berg
Systems Administrator
NRL Code: 7320
Office: 228-688-5738
[email protected]
