[ipxe-devel] Issues in booting with Intel i-350

[Robin Smidsrød]

The iPXE intel driver has some issues with some chipsets. It's a known
issue, but we've been unable to nail down exactly what is the problem.
It affects (among others), HP EliteBook 8470p and 5th gen Intel NUCs. In
most situations you end up getting linkup on 10Mbit instead of gigabit,
but there are also some situations where you don't get linkup at all.
I've tested this extensively myself, as I have those two systems above
at home.

If you have experience looking at datasheets and writing C code, we
would very much appreciate troubleshooting assistance. If you can find
the root cause for the broken link detection behavior I'm fairly certain
that it will be quickly tested (and hopefully merged).

-- Robin

On 18.09.2015 19:24, varun satrawla wrote:
> Hi,
> 
> We have a Intel’s Haswell based custom hardware with i350-b (8086 1523)
>  NIC that we are trying to boot using iPXE. We are using usb device for
> now. It seems iPXE is unable to configure network interfaces. I see the
> following.
> 
> 
> Any thought on why this might be happening? [I have verified that dhcp
> server is up and running by booting some other system.]
> 
> 
> Thanks,
> Varun
> 
> 
> *iPXE 1.0.0+ (3f8d)* -- Open Source Network Boot Firmware -- http://ipxe.org
> Features: DNS HTTP iSCSI TFTP SRP AoE ELF MBOOT PXE bzImage Menu PXEXT
> iPXE> 
> iPXE> 
> iPXE> 
> iPXE> 
> iPXE> 
> iPXE> 
> iPXE> dhcp net1
> INTEL 0xd5eac ring 03800 is at [db76d100,db76d200)
> INTEL 0xd5eac ring 02800 is at [db76d200,db76d300)
> INTEL 0xd5eac link status is 80280703
> INTEL 0xd5eac link status is 80280703
> Configuring (net1 00:33:22:33:44:52).................. Error 0x040ee119
> (http://ipxe.org/040ee119)
> INTEL 0xd5eac MAC reset (ctrl 181c0261)
> iPXE> 
> 
> 
> 
> Boot up Logs (debugging enabled)
> 
> INTEL 0xd5c4c MAC reset (ctrl 00100260)
> INTEL 0xd5c4c has autoloaded MAC address 00:90:fb:4c:a3:b4
> INTEL 0xd5c4c link status is 40080683
> PCI 00:1a.0 (8086:8c2d class 0c0320) has no driver
> PCI 00:1b.0 (8086:8c20 class 040300) has no driver
> PCI 00:1c.0 (8086:8c10 class 060400) has no driver
> PCI 00:1d.0 (8086:8c26 class 0c0320) has no driver
> PCI 00:1f.0 (8086:8c4f class 060100) has no driver
> PCI 00:1f.3 (8086:8c22 class 0c0500) has no driver
> PCI 01:00.0 (10b5:8724 class 060400) has no driver
> PCI 02:01.0 (10b5:8724 class 060400) has no driver
> PCI 02:02.0 (10b5:8724 class 060400) has no driver
> PCI 02:08.0 (10b5:8724 class 060400) has no driver
> PCI 02:09.0 (10b5:8724 class 060400) has no driver
> PCI 02:0a.0 (10b5:8724 class 060400) has no driver
> PCI 03:00.0 (8086:1523) has driver "i350-b"
> PCI 03:00.0 has mem f7c60000 io e060 irq 5
> PCI 03:00.0 latency timer is unreasonably low at 0. Setting to 32.
> INTEL 0xd5eac MAC reset (ctrl 181c0261)
> INTEL 0xd5eac has autoloaded MAC address 00:33:22:33:44:52
> INTEL 0xd5eac link status is 80280703
> PCI 03:00.1 (8086:1523) has driver "i350-b"
> PCI 03:00.1 has mem f7c40000 io e040 irq 11
> PCI 03:00.1 latency timer is unreasonably low at 0. Setting to 32.
> INTEL 0xd610c MAC reset (ctrl 181c0261)
> INTEL 0xd610c has autoloaded MAC address 00:33:22:33:44:53
> INTEL 0xd610c link status is 80280707
> PCI 03:00.2 (8086:1523) has driver "i350-b"
> PCI 03:00.2 has mem f7c20000 io e020 irq 5
> PCI 03:00.2 latency timer is unreasonably low at 0. Setting to 32.
> INTEL 0xd636c MAC reset (ctrl 181c0261)
> INTEL 0xd636c has autoloaded MAC address 00:33:22:33:44:54
> INTEL 0xd636c link status is 8028070b
> PCI 03:00.3 (8086:1523) has driver "i350-b"
> PCI 03:00.3 has mem f7c00000 io e000 irq 11
> PCI 03:00.3 latency timer is unreasonably low at 0. Setting to 32.
> INTEL 0xd65cc MAC reset (ctrl 181c0261)
> INTEL 0xd65cc has autoloaded MAC address 00:33:22:33:44:55
> INTEL 0xd65cc link status is 8028070f
> ok
> 
> 
> 
> _______________________________________________
> ipxe-devel mailing list
> ipxe-devel at lists.ipxe.org
> https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
>