[ipxe-devel] Chainload WDS/SCCM2012 server, with hp8570w and undionly.kpxe, WinPE freezing...

Torgeir.Wulfsberg at kongsberg.com Torgeir.Wulfsberg at kongsberg.com
Tue Nov 24 13:37:16 UTC 2015


These two commits solved my "10Mbps" problem, when using our ".pxe" image on my HP 8570w.

[intel] Correct definition of receive overrun bit

[intel] Forcibly skip PHY reset on some models

This 8570w has an Intel 82579LM card (8086:1502), together with our Zbook15, and 8470p (which also had the same problem).

But our other Zbook15 (don't know which one is G1 or G2) has another NIC Intel I217-LM (8086:153a). Same problem. Drops to 10Mbps (9 min for 240MB boot.wim file).

Adding "INTEL_NO_PHY_RST" for this network interface as well does the trick (downloads in 90sec or so as expected):
--- oldsrc/drivers/net/intel.c	2015-11-24 13:52:53.452799000 +0100
+++ src/drivers/net/intel.c	2015-11-24 11:57:55.848463000 +0100
@@ -1058,7 +1058,7 @@ static struct pci_device_id intel_nics[]
 	PCI_ROM ( 0x8086, 0x1527, "82580-f2", "82580 Fiber", 0 ),
 	PCI_ROM ( 0x8086, 0x1533, "i210", "I210", 0 ),
 	PCI_ROM ( 0x8086, 0x1539, "i211", "I211", 0 ),
-	PCI_ROM ( 0x8086, 0x153a, "i217lm", "I217-LM", 0 ),
+	PCI_ROM ( 0x8086, 0x153a, "i217lm", "I217-LM", INTEL_NO_PHY_RST ),
 	PCI_ROM ( 0x8086, 0x153b, "i217v", "I217-V", 0 ),
 	PCI_ROM ( 0x8086, 0x1559, "i218v", "I218-V", 0),
 	PCI_ROM ( 0x8086, 0x155a, "i218lm", "I218-LM", 0),


-----Original Message-----
From: ipxe-devel-bounces at lists.ipxe.org [mailto:ipxe-devel-bounces at lists.ipxe.org] On Behalf Of ipxe-devel-request at lists.ipxe.org
Sent: 20. november 2015 13:00
To: ipxe-devel at lists.ipxe.org
Subject: ipxe-devel Digest, Vol 66, Issue 16

Send ipxe-devel mailing list submissions to
	ipxe-devel at lists.ipxe.org

To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to
	ipxe-devel-request at lists.ipxe.org

You can reach the person managing the list at
	ipxe-devel-owner at lists.ipxe.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of ipxe-devel digest..."

Today's Topics:

   1.   - Chainload WDS/SCCM2012 server, with hp8570w and
      undionly.kpxe, WinPE freezing... (Torgeir.Wulfsberg at kongsberg.com)


Message: 1
Date: Thu, 19 Nov 2015 12:08:41 +0000
From: <Torgeir.Wulfsberg at kongsberg.com>
To: <ipxe-devel at lists.ipxe.org>
Subject: [ipxe-devel]   - Chainload WDS/SCCM2012 server, with hp8570w
	and undionly.kpxe, WinPE freezing...
	<1D06107EC7935647BBBF9CC48D509F6FE9DE4BA6 at UKGAW-EXM-P04.kda.kongsberg.com>
Content-Type: text/plain; charset="utf-8"


>From iPXE we have been doing chainloading to a SCCM2012 server, with this (simple example script):

# start file
set net0.dhcp/filename SMSBoot\\x86\\wdsnbp.com

# sccm2012 server ip
set net0.dhcp/next-server

# boot that

It has been working fine until we recently got trouble on some machines (we have a lot of different hardware).
Because of this we alternate between a "ipxe.pxe" and a "undionly.kpxe" image based on nic vendor device id VVVVDDDD.
I have updated iPXE to the latest version available to this date.

This specific machine an HP 8570w (updated to the latest bios from hp).
Booting this 8570w with our "undionly.kpxe" image, and running this script above manually results in a strange behavior.

We see the well known, WDS takeover (Press F12 for network service boot).
Downloads fine (boot.wim takes about 2 minutes), just before WinPE starts graphical, it just freeze (forever, days, screen is just black).

Booting this 8570w again in "ipxe.pxe" image works fine (has a slower tftp fetch of boot.wim, actually 9 minutes), but it works.

I know we could use "wimboot", but then we have to find a good solution, whenever they update boot.wim with new drivers etc.
Perhaps a IIS http service on the SCCM server, but with different types/profiles to these pe images it may get messy, and very unpractical when doing testing.

Since this works fine with "ipxe.pxe" image, and "undionly.kpxe" is freezing, I wonder if "undi-something" could have some bug??

If I can assist in debugging this, just tell me what to do.



This e-mail and any attachment contain KONGSBERG information which may be proprietary, confidential or subject to export regulations, and is only meant for the intended recipient(s). Any disclosure, copying, distribution or use is prohibited, if not otherwise explicitly agreed with KONGSBERG. If received in error, please delete it immediately from your system and notify the sender properly.


ipxe-devel mailing list
ipxe-devel at lists.ipxe.org

End of ipxe-devel Digest, Vol 66, Issue 16

More information about the ipxe-devel mailing list