Problem with Intel Pro/VE

[dlb99]

Hello,

I have been trying to get iPXE working for our training class. It works on some machines, but several of the machines are somewhat 'old' and the NIC does not seem to be detected.

I enabled a number of debugs including pci and undi and got these results>
(some omitted, but more PCI materials preceded)
PCI 04:08.0 (8086:1094) has driver "undipci"
PCI 04:08.0 has mem 90000000 io 1000 irq 11
PCI 04:08.0 probe failed: no such device (http://ipxe.org/2c80603b)

Followed the link and it shows a failure at a line of net/undi.c

Does anyone hav any idea how I can get this working ?

Thanks in advance for any help.
(unfortunately we have over a dozen of these boxes)

[dlb99]

I am working through rom-o-matic due to issues building on linux 14.10

I have attempted to build versions with just eepro, undi, prove and a few others all giving similar results.
Is there a command to list the drivers that have been linked ??

(I am not certain rom-o-matic is doing this part)

[NiKiZe]

How are you starting this, do you chain from internal PXE or are you burning to rom, or just booting over usb?

If you are booting from existing PXE then undionly.kpxe works almost all the time.

[dlb99]

Hello NiKiZe,

I have an ISO on CDs with an embedded script that gets a DHCP address and then chains a second wimboot based script via http. Will try your suggestion at some point too, but for the moment I got it working to a degree by adding my cards PCI ID to the eepro100 driver. Apparently Intel has a large number of PCI IDs floating around for these NICs because they were OEM products sold to many.

The addition of the PCI ID and recompile works to a degree, but occasionally ipxe just locks up. I still had not worked out the scripts for our use of wimboot and the other parts. I figured thos out today under a VM and will try them on the old clunkers soon.. They seem to execute a few commands and then lock up if you leave them at the shell prompt for a while. I am hoping that if I have all the scripts and files in operational state it will get as far as Wimboot and then work.. Hoping anyway !

[robinsmidsrod]

dlb99: You should test the machines showing issues using http://ipxe.org/dev/driver. I would also recommend you use http://boot.ipxe.org/ipxe.iso (or ipxe.usb) when doing the testing, to ensure you're using a known working binary.