Re: [gPXE] Intel NIC Link-state problem

Op 20100417 om 07:08 schreef Marty Connor: Christopher Armenio wrote on 4/16/10 11:49 AM: Thomas, Looks like your patch works! Thanks to everyone for all of the help with this! -Chris Nice work folks! I look forward to a patch to apply. / Marty /

Re: [gPXE] Intel NIC Link-state problem

Geert Stappers wrote on 4/18/10 8:56 AM: Op 20100417 om 07:08 schreef Marty Connor: Christopher Armenio wrote on 4/16/10 11:49 AM: Thomas, Looks like your patch works! Thanks to everyone for all of the help with this! -Chris Nice work folks! I look forward to a patch to apply. / Marty

Re: [gPXE] Intel NIC Link-state problem

Marty, I forgot to post this yesterday... I fumbled around with some of the link checking code on my own and wound up removing the link state check. I compiled it and everything worked like a charm...here is my simple change: --- eepro100.c2010-04-16 09:56:56.753307333 -0400 +++

Re: [gPXE] Intel NIC Link-state problem

Hello Christopher, thanks for testing. I have pushed a patch that removes the link state checking code from eepro100 to staging[1]. Please let us know if this patch works for you. I will give it a shot on my cards too, as soon as I can. You can find prebuilt binaries at [2]. Thanks Thomas [1]

Re: [gPXE] Intel NIC Link-state problem

Thomas, Looks like your patch works! Thanks to everyone for all of the help with this! -Chris On Fri, Apr 16, 2010 at 12:47 PM, Thomas Miletich thomas.milet...@gmail.com wrote: Hello Christopher, thanks for testing. I have pushed a patch that removes the link state checking code from

Re: [gPXE] Intel NIC Link-state problem

Geert, Thomas, Shao, Results of add the printf: eepro100 - mdio_register: 0x Results of 'lspci -vn -s 02:07': 02:07.0 0200: 8086:1209 (rev 10) Flags: bus master, medium devsel, latency 32, IRQ 16 Memory at 8102 (32-bit, non-prefetchable) [size=4K] I/O ports at 4000 [size=64]

Re: [gPXE] Intel NIC Link-state problem

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 -

[gPXE] Intel NIC Link-state problem

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 stapp...@stappers.nlwrote: Op 20100414 om 10:29 schreef Christopher Armenio: Andrew, Thanks for the quick reply. I tried the gPXE 0.9.7 image

Re: [gPXE] Intel NIC Link-state problem

Christopher, the gPXE source code suggests that 8086:1209 is indeed handled by EEPRO100, as you originally claimed. It still might be good to try gPXE 1.0.0+ anyway. - Shao ___ gPXE mailing list gPXE@etherboot.org

[gPXE] Intel NIC Link-state problem

Hi there, I seem to be having a problem getting gPXE to correctly interact with my intel NIC (integrated intel eepro100). I believe gPXE is incorrectly reporting the link as being down. There are both link and activity lights on the physical interface, and I can see the RX counter incrementing

Re: [gPXE] Intel NIC Link-state problem

Hello Chris, While I can't really help troubleshoot your issue, there was just another thread on the list today about a fellow who was unable to pull DHCP with gPXE on an eepro100 but the vendor PXE was working just fine. You can get more info here: