Geert, Here is the output of 'lspci -n -s 02:07'
02:07.0 0200: 8086:1209 (rev 10) Thanks! -Chris On Wed, Apr 14, 2010 at 2:37 PM, Geert Stappers <[email protected]>wrote: > Op 20100414 om 10:29 schreef Christopher Armenio: > > Andrew, > > Thanks for the quick reply. I tried the gPXE 0.9.7 image as you > suggested, > > but it didn't detected the NIC at all. Here are the results of some > playing > > around: > > > > gPXE 1.0.0: > > e1000 - not detected > > eepro - not detected > > eepro100 - detected, but incorrect link-state > > > > gPXE 0.9.7: > > e1000 - not detected > > eepro - not detected > > eepro100 - not detected > > > > > > Here is a dump from lspci: > > 02:07.0 Ethernet controller: Intel Corporation 8255xER/82551IT Fast > Ethernet > > Controller (rev 10) > > Flags: bus master, medium devsel, latency 32, IRQ 16 > > Memory at 81020000 (32-bit, non-prefetchable) [size=4K] > > I/O ports at 4000 [size=64] > > Memory at 81000000 (32-bit, non-prefetchable) [size=128K] > > Expansion ROM at a0000000 [disabled] [size=64K] > > Capabilities: [dc] Power Management version 2 > > Kernel driver in use: e100 > > Kernel modules: e100 > > > > > > Any thoughts/suggestions? > > > > Show us the output of > lspci -n -s 02:07 > > The '-n' is for numeric, so we can check that PCI ID with supported PCI > IDs in gPXE. The '-s 02:07' show only the device on slot 7 on bus 2. > > > Groeten > Geert Stappers > > _______________________________________________ > gPXE mailing list > [email protected] > http://etherboot.org/mailman/listinfo/gpxe >
_______________________________________________ gPXE mailing list [email protected] http://etherboot.org/mailman/listinfo/gpxe
