Bob, You can try a test version of the new e1000e driver here:
http://etherboot.org/share/mdc/e1000e-only.dsk or here: http://etherboot.org/share/mdc/e1000e-only.iso Please let us know how things go. / Marty / On 1/26/10 6:42 PM, Robert Boerner wrote: > Thanks for the update. I guess I'll just wait since I have no ability > to write code :-) I just finished watching the videos of Marty Connor > giving talks that are on the gPXE website. Very helpful and > informative. > > Thanks again everyone for your help, > > Bob > > On Tue, Jan 26, 2010 at 2:27 PM, Joshua Oreman <[email protected]> wrote: >> On Tue, Jan 26, 2010 at 6:23 PM, Robert Boerner >> <[email protected]> wrote: >>> Hi Neil, >>> >>> That was fast :-) >>> >>> I am not receiving any error. It just seems as if no NIC is detected. >>> Am I correct in assuming that when booting it should identify the NIC >>> in the boot messages, and that when accessing the gPXE command line >>> issuing an iftstat command should list all found interfaces? During >>> the boot it simply states No more network devices. I tried ifstat and >>> nothing was returned, and then tried an ifstat net0 (I believe the >>> syntax was correct) and I get net0: no such interface. >> >> I believe that PCI ID corresponds to a NIC implemented by the Intel >> e1000e driver, which has not yet been ported to gPXE. Our project >> leader, Marty Connor, is working on it. >> >> -- Josh >> > _______________________________________________ > gPXE mailing list > [email protected] > http://etherboot.org/mailman/listinfo/gpxe _______________________________________________ gPXE mailing list [email protected] http://etherboot.org/mailman/listinfo/gpxe
