Hello Jonathan,
I suggest first trying disabling the NIC in the BIOS of the machine...
but depending on the machine, that doesn't always work.
After gPXE loads, the Autoboot process will try the NICs it finds in
the order that they're enumerated: net0, net1 .... netN. If you use
an embedded script that specifically opens, DHCPs net1 (thereby
skipping net0), and boots net1/${filename}, you should get the
behavior that you want. I'd write out the script here in the email
for you... but I can't quite remember the syntax this early in the
morning. I need more coffee :D
Cheers,
Andrew Bobulsky
On Fri, Feb 3, 2012 at 8:37 AM, Jonathan Smith
<jonathan.sm...@seamap.com> wrote:
> Hi All,
>
>
>
> I am using an ETX processor board which has a built in NIC, but am using a
> separate additional NIC to communicate with a host computer. The built in
> NIC is not being connected to anything.
>
>
>
> I am finding that when I boot the ETX processor, the built-in NIC is tries
> to communicate with the host computer for roughly 14 seconds, before the
> second one tries.
>
>
>
> Can anyone help me with reducing this retry time on the first NIC? I want to
> reduce the overall boot time.
>
>
>
> The ROM I used is from ROM-o-matic using an eepro100 NIC in an .sdsk format.
>
>
>
> Any help you can give would be much appreciated.
>
>
>
> Regards,
>
>
>
> Jonathan
>
>
> _______________________________________________
> gPXE mailing list
> gPXE@etherboot.org
> http://etherboot.org/mailman/listinfo/gpxe
>
_______________________________________________
gPXE mailing list
gPXE@etherboot.org
http://etherboot.org/mailman/listinfo/gpxe
