IRC log for ##pxe on 20101010

02:18.23extorI have a pulse H1012 Pro 100 NIC. How do I know if it has a ROM and supports PXE? It's an OEM clone of the intel pro 100 NIC.
02:34.54extorlspci shows this
02:34.54extor03:06.0 Ethernet controller: Intel Corporation 82559 InBusiness 10/100 (rev 08)
04:22.53*** join/##pxe extor (~extor@c-76-16-36-19.hsd1.il.comcast.net)
08:51.59Nirkusextor: if dont have the vendor specifications of you NIC, you need to boot it on $pc and see whether a nework boot agent starts up
08:52.25Nirkusextor: it depends on the actual card, not the chip.. usually
08:52.53extor$pc ?
08:52.59Nirkuspersonal computer
08:53.07Nirkus:)
08:53.16extorThe card has further identified itself as an intel "InBusiness" Network adapter
08:53.51extorIntel Corp. 82559 InBusiness 10/100
08:53.59Nirkusextor: on the card itself, is there a vendor and product information?
08:54.08extorLinuux says the eeprom is "corrupt"
08:54.10extoryes there is
08:54.19extorPulse H1012
08:54.26Nirkusextor: what you see in lspci is the vendor/product id of the pci interface of the chip sitting on that card
08:54.27extorEvidently it's an OEM deal
08:54.48extor03:06.0 Ethernet controller: Intel Corporation 82559 InBusiness 10/100 (rev 08)
08:54.57Nirkusextor: try to find specs for Pulse H1012 or just try to boot off it
08:55.11extorI tried booting off it, no luck
08:55.22Nirkusextor: what pc did you use?
08:55.31Nirkusextor: especially what mainboard?
08:56.05extorhttp://www.kugeldreieck.de/img/hardware/nic_pulse_h1012_3.jpg
08:56.10extorOh I used a gigabyte mobo
08:56.36extorhttp://www.newegg.com/Product/Product.aspx?Item=N82E16813128394
08:56.42extorthis exact one Rev 1.0
08:57.18extorI basically just gave up on the NIC
08:57.51extorResearch shows me it was designed in Russia using the intel 82559 chip by a company called "pulse" which doesn't support it any more lol
08:58.07extorI booted it up in windows XP and it shows up with a yellow exclamation point
08:58.27extorand knoppix does not enable it either...just shows in lspci but no driver attaches to it
08:59.02extorKinda sad because I have two of those NICs lying around here...and 2 more hidden in garbage somewhere lol
08:59.22extorI was hoping they were esxi compatible too
09:00.26Nirkusextor: on knoppi do a 'dmesg | grep eth' and look for any information regarding you NIC
09:00.59Nirkuss/knoppi/knoppix/
09:01.43extorroot@Microknoppix:~# dmesg | grep -i rtl
09:01.43extor[    6.915198] eth0: RTL8168c/8111c at 0xf8b2a000, 00:24:1d:d1:91:28, XID 3c4000c0 IRQ 26
09:01.43extorroot@Microknoppix:~#
09:02.07extorlawl irq 26 ?
09:02.37extormaybe run the DOS diags on it? From intel?
09:05.10Nirkusextor: i think thats your onboard card
09:05.33extorooops
09:05.34extordoh!
09:05.50Nirkusextor: interrupt 26 is pretty normal nowadays
09:06.26Nirkusextor: interrupts are usuassy handled using (IO-)APIC/MSI by modern hardware
09:07.39extorok rebooting into knoppix again
09:07.57Nirkusextor: what OS are you running know?
09:08.06Nirkusknow
09:08.06Nirkusgrr
09:08.06Nirkusnow
09:08.41extorNirkus, I was in XP...
09:08.52extordoing some tasks on that same box
09:08.59extorNow I am rebooting it in knoppix remotely
09:09.08extorover PXE of course. Terminal server mode :)
09:12.33Nirkusextor: you booting that box over PXE to find out whether it supports PXE? oO
09:12.49extorlawl
09:12.58extorIm booting it via the realtek which does support PXE
09:13.02Nirkusextor: try setting "First Boot Device" in your BIOS menu to "Legacy LAN"
09:13.09Nirkusah
09:13.20extorAlready tried that legacy lan deal..no luck and no display
09:13.26Nirkusk
09:13.41extorBut it appears to have a nice big fat eeprom chip
09:14.05Nirkushave you tried disabling that realtek card while testing your pulse NIC?
09:14.15extor7.011307] Intel(R) Gigabit Ethernet Network Driver - version 1.3.16-k2
09:14.19extorno I have not
09:14.20extorshould I?
09:14.49Nirkusextor: maybe your BIOS vendor doesnt allow booting off addon cards while the onboard NIC is used.. it's PC .. everything possible :)
09:15.01Nirkusextor: i would..
09:15.12extorhttp://pastebin.com/jjWa1HSV
09:15.17extorThat is my entire dmesg
09:15.25extorlet me disable the realtek now
09:15.31Nirkusextor: your message means that the intel driver was loaded, not that it has detected any hardware
09:16.31extorhttp://pastebin.com/UFp50502 <-- lspci
09:17.06Nirkuse100: 0000:03:06.0: e100_eeprom_load: EEPROM corrupted
09:17.15Nirkuse100 0000:03:06.0: PCI INT A disabled
09:17.21extorcorrupted eh?
09:17.22Nirkuse100: probe of 0000:03:06.0 failed with error -11
09:17.32extorlet me reboot and try and run the dos diags first
09:18.04extorSo you think the eeprom is fried? Or is it just an unusual OEM card which is confusing the hardware?
09:18.24Nirkusextor: maybe both
09:18.50Nirkusbut if XP doesnt laod drivers for it, it pretty much seems to be fried
09:19.11Nirkusas far as i have googled your card, XP should bring drivers for it
09:19.28extorfcc id number is "EJMNPDALBANY"
09:19.48extorhttp://forums.driverguide.com/showthread.php?t=35550
09:19.51Nirkusextor: what is it with you and DOS? :P
09:19.58extorBut it says pulse H1012 on it!
09:20.06extorNirkus, the intel diag is only in dos
09:21.27extordos util said eeprom was bad too!
09:21.39extorhrmm...I have a 2nd pulse card...let me try diags on that
09:21.54Nirkusextor: i see.. never had to use those
09:23.12extorthe 2nd NIC wasnt even detected
09:23.13extorwow
09:23.15extorthis is bad
09:23.16extorlawl
09:23.27extorthey should both act the exact same
09:23.41extorhrmm maybe that guy on ebay ripped me off years ago when I grabbed these for $5 each
09:23.43extorgrrrrrrrr
09:24.50extorsighs
09:26.51extordmesg | grep -i corrupt yields nothing here
09:27.07extorgrep eth nothing but the realtek
09:31.35Nirkusextor: seems you have been ripped off then ;)
09:37.03extorI have some other NICs
09:37.10extorbut they have empty EEPROM sockets
09:37.31extorcan those EEPROMs be salvaged from other equipment...like old telecom equipment...switches etc?
09:54.57*** join/##pxe sohibaki (~Q@94.182.173.145)
10:00.08*** part/##pxe sohibaki (~Q@94.182.173.145)
10:17.54extorhmmm when I removed my PCI-X riser card...the NIC suddenly tries to boot from EEPROM!
10:17.56extor\o/
10:39.25extorroot@Microknoppix:~# dmesg | grep eth0
10:39.26extor[    6.910385] e100: eth0: e100_probe: addr 0xfdcff000, irq 20, MAC addr 00:03:47:05:9a:fc
10:39.26extor[   67.050283] e100: eth0: e100_request_firmware: Failed to load firmware "e100/d101m_ucode.bin": -2
10:39.26extorroot@Microknoppix:~#
10:39.30extorI got it!!!
10:39.40extorBut why does it say it failed to load firmware?
10:39.45extorNirkus
12:39.12Nirkusextor: id guess because the intel driver expects the card to be intel and accept the intel firmware
12:39.36extorI got it to boot
12:39.43extorand it tries to pxe boot
12:39.48extorit gets the DHCP address
12:39.49extorbut
12:39.50extorthen
12:39.58extorit fails to talk to the tftp server
12:40.02extoryet the realtek succeeds!
12:40.09extorwonders what's wrong!
12:43.22extorMaybe I need to update the firmware in the intel NIC?
13:02.49Nirkusextor: see the log files of your tftp server, maybe theres a hint
13:07.15extorNirkus it cannot connect to it
13:07.29extorI'm thinking maybe I should use gPXE
13:07.40extorhmm
15:18.14Nirkusextor: gPXE is that thingy to flash on your NIC directly?
21:04.37extoryes and no
21:04.46extoryou can flash the nic directly which is dangerous
21:04.47extorOR
21:05.00extoryou can acutally launch it from like a floppy
21:05.14extorhttp://rom-o-matic.net
21:05.37extorbut from what I gather, there's an updated intel PXE romcode out there too?
22:50.40Nirkusextor: or you could just buy some supported NIC with PXE and linux support :P
22:51.08extorisnt my pro 100 "supported" ?
22:51.16extorIt might be supported by intel
22:51.30extorthere might be a pxe rom update for it
22:53.04Nirkusextor: its a pulse something not an intep pro 100, isnt it? :)
22:53.51extorthat pulse rumor might be false
22:54.03Nirkus:P
22:54.05extorIt shows up as an intel "management pro 100 adapter"
22:54.22Nirkusextor: yeah, because PCI ID says, its an intel chip
22:55.32extorit works in linux too now
22:57.41Nirkushehe
22:57.53Nirkusyou upgraded tha formware?
23:02.04extorno
23:02.10extorI merely removed the riser card
23:02.36extorevidently I had inserted the NIC the opposite way in the riser card(which had been created by sawing a PCI-X riser card in half)
23:08.22extorhttp://oi56.tinypic.com/28l502d.jpg  <---- See?
23:13.26Nirkusextor: the vendor and name displayed for a windows device are provided by the driver (AFAIK)
23:13.54Nirkusextor: the drover gets loaded because of the matching PCI ID of that intel chip on your NIC
23:14.09extorok what are you saying?
23:14.17Nirkusso intel chip => intel driver => intel vendor and product string in windows
23:14.23extormy NIC seems to work...it's just that the PXE code is probably very very old
23:14.34Nirkusextor: a similar thing happens on linux
23:14.51extorAlso if you recall...the FCC id of this nic belongs to intel in albany NY right?
23:15.33Nirkusextor: linux distros use a local copy of a PCI ID to vendor and product name database to resolve PCI ID to a name
23:16.03extorNirkus but if my NIC functions just as the device it is identified as...what's the problem?
23:16.11Nirkusextor: if the FCC ID belongs to intel, than its probably a real intel oem card just branded otherwise
23:16.42Nirkusextor: just saying that you computer calling it an intel card does only mean, it has a chip on it supported by the intel driver :)
23:17.05Nirkusextor: but if your NIC works fine, it doesnt matter :)
23:17.19Nirkusextor: if youre going to flash that ROM, it might matter :P
23:18.45extorI need to flash the rom yes
23:18.52extorfirst with the intel util
23:19.36Nirkusextor: good luck
23:19.41Nirkusneeds to sleep
23:20.53extorMarty Conner from etherboot said that many cards can just be flashed with gpxe
23:26.06extorhttp://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Network+Connectivity&ProductLine=Boot+Agent+Software&ProductProduct=Intel%C2%AE+Boot+Agent

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.