DHCP configuring error 0x40ee186

[Richard_Compal]

Hello all,
i am a new person for iPXE, and now i meet a question when i build snponly.efi for UEFI boot, i download the source and rebuild snponly.efi, when the NB boot to ipxe, run dhcp command, it feedback bellow info,

iPXE>dhcp
configuring (net0 01:01:01:01:01:01)...... Error 0x40ee186 (http://ipxe.org/040ee186)
iPXE>ifstat
net0: 01:01:01:01:01:01 using NII on NII-PC08:00.0(closed)
Link:down, TX:0 TXE:0 RX:0 RXE:0
Link status: Unknow(http://ipxe.org/1a086194)]

1. i build the Win2012 DHCP server with VMware, it will show this error.
2. i don't use VMware build DHCP server, and use a server build DHCP, will no this issue, but initrd file by HTTP, the speed very slowly.
3. use other's guys build snponly.efi, use VMware build DHCP, also no this issue, initrd file speed normal, and i cannot use it, because i need chainload my php file.

anyone can help me? many thanks,
sorry for my english very poor.

[robinsmidsrod]

That error URL isn't valid in the latest version of the code, so you should first try to build the latest version of iPXE. After that you could also try ipxe.efi instead of snponly.efi to see if a native iPXE driver works better than using the firmware-provided SNP/NII driver to drive the networking hardware.

[Richard_Compal]

Dear Robin,
Many thanks for your great support, i have found this root cause, and rebuild ipxe.efi, it can boot to UEFI sucessfull, thanks

[robinsmidsrod]

Richard: Just for reference, what was the root cause?

[Richard_Compal]

Oh, that isn't right root cause at 29/12, at that day, i built snponly.efi and boot fail, then i reported this issue, and then i built a ipxe.efi and boot OK, so i think maybe i need to use ipxe.efi, but after these, i found it booted up OK with snponly.efi, i review my testing again, i found my testing NB have been changed, and current that boot fail NB has been shipping out, but i rember that NB is a realtek LAN, not Intel LAN card.

[Richard_Compal]

Robin, i found the LAN card, VEN_10EC&DEV_8168, it's Realtek Pcie GBE Family Controller Series v2.60,
1. use snponly.efi run DHCP will get "configuring (net0 01:01:01:01:01:01)...... Error 0x40ee186 (http://ipxe.org/040ee186)"
2. use Ipxe.efi will ok
3. i also found this LAN card boot to Legacy mode with undionly.kpxe/undionly.kkpxe, DHCP will get "configuring(net0 d0:bf:9c:63:a1:b1)........Error 0x040ee119 (http://ipxe.org/0x040ee119)"

[ribalda]

I am having the same issue with the latest git version

d38bac05e7d0eb67fc19f3532a6b4fa00804106e ([build] Include Hyper-V driver in the all-drivers build)

uefi mode (8086150e.efi)

This fixes it for me.

Code:

+++ b/src/usr/autoboot.c
@@ -360,9 +360,16 @@ int netboot ( struct net_device *netdev ) {
                goto err_ifopen;
        ifstat ( netdev );

+       if ( ( rc = ifconf ( netdev, NULL ) ) == 0 )
+               goto ok_dhcp;
+
+       netdev_close ( netdev );
+
        /* Configure device */
        if ( ( rc = ifconf ( netdev, NULL ) ) != 0 )
                goto err_dhcp;
+
+ok_dhcp:

I know it does not make much sense, but it does the trick

If you need to, I can run any tests on my board.

Regards!

[Richard_Compal]

Can you tell me how to fix it? or show me detail code.

[ribalda]

It it not a really fix, it is more a hack. If ifconf fails, I try again and then it would likely work.

The snipset I attach was written in unified format: http://en.wikipedia.org/wiki/Diff_utilit...ied_format

Take a look to that url and ask me again if it still does not make sense

[renato]

I bumped into this exact same issue
Im trying to PXE boot in UEFI mode using snponly.efi and ipxe.efi built from latest in git master branch.
commit 40de41276218ef1bca9f47fd166e83deb1c1f536
owner Michael Brown
last change Wed, 15 Apr 2015 05:20:06 -0600 (12:20 +0100)

the NIC is the same realtek 10ec:8168

I am trying to pxe boot winpe and I have successfully booted other systems with Broadcom and Intel NICs, however for this Realtek NIC I haven't had any luck.

has anybody fixed this issue?
ribalda patch did not work for me, I keep getting the same error
if I switch to ipxe.efi everything is downloaded successfully (Im using wimboot) but while wimpe is starting the systems freezes in the windows logo with no error messages.

Any Idea what may be causing the snponly error or the hanging?

Thank you

Renato

[yavuz]

I wanna hop on the me-too bandwagon.

I'm working on a Shuttle XS36V4 (just for the purpose to be able to debug via serial, I have this problem with a lot of Shuttle devices with Realtek chipsets).

I have buiilt snponly.efi with:
make bin-x86_64-efi/snponly.efi DEBUG=efi_driver,efi_pci,snp,snpnet,snponly

And I get the following output on serial:

Code:

CHAINED 0xac13c418 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2)/MAC(80EE73AA0C7B,0x0)/IPv4(0.0.0.0) found SimpleNetwork on 0xac13c418 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2)/MAC(80EE73AA0C7B,0x0)/IPv4(0.0.0.0)
CHAINED 0xac13c418 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2)/MAC(80EE73AA0C7B,0x0)/IPv4(0.0.0.0) found Nii31 on 0xac29e198 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2)/MAC(80EE73AA0C7B,0x0)
iPXE initialising devices...EFIDRV connecting our drivers
CHAINED 0xac29e198 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2)/MAC(80EE73AA0C7B,0x0) 0xac305228 is the chainloaded Nii31
EFIDRV 0xac29e198 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2)/MAC(80EE73AA0C7B,0x0) has driver "NIIONLY"
EFIDRV 0xac29e198 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2)/MAC(80EE73AA0C7B,0x0) disconnecting existing drivers
EFIDRV 0xac29e198 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2)/MAC(80EE73AA0C7B,0x0) connecting new drivers
CHAINED 0xac29e198 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2)/MAC(80EE73AA0C7B,0x0) 0xac305228 is the chainloaded Nii31
EFIDRV 0xac29e198 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2)/MAC(80EE73AA0C7B,0x0) has driver "NIIONLY"
EFIDRV 0xac29e198 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2)/MAC(80EE73AA0C7B,0x0) DRIVER_START
CHAINED 0xac29e198 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2)/MAC(80EE73AA0C7B,0x0) 0xac305228 is the chainloaded Nii31
EFIDRV 0xac29e198 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2)/MAC(80EE73AA0C7B,0x0) using driver "NIIONLY"
ok



iPXE 1.0.0+ (3681) -- Open Source Network Boot Firmware -- http://ipxe.org
Features: DNS HTTP TFTP EFI Menu

No more network devices                  

EFIDRV disconnecting our drivers        
EFIDRV 0xac29e198 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2)/MAC(80EE73AA0C7B,0x0) DRIVER_STOP child 0xac0c3e18 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2)/MAC(80EE73AA0C7B,0x0)/MAC(010101010101,0x1)
EFIDRV 0xac29e198 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2)/MAC(80EE73AA0C7B,0x0) DRIVER_STOP
EFIDRV disconnecting our drivers
EFIDRV reconnecting old drivers

Using the ipxe.efi it works correct with the rtl8168 driver:

Code:

iPXE initialising devices...EFIDRV connecting our drivers
EFIPCI 0xb5c25f18 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2) has driver "rtl8168"
EFIDRV 0xb5c25f18 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2) has driver "PCI"
EFIDRV 0xb5c25f18 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2) disconnecting existing drivers
EFIDRV 0xb5c25f18 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2) connecting new drivers
EFIPCI 0xb5c25f18 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2) has driver "rtl8168"
EFIDRV 0xb5c25f18 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2) has driver "PCI"
EFIDRV 0xb5c25f18 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2) DRIVER_START
EFIPCI 0xb5c25f18 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2) has driver "rtl8168"
EFIPCI 0xb5c25f18 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2) using driver "rtl8168"
EFIDRV 0xb5c25f18 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x2) using driver "PCI"
ok

I would like to use the snponly.efi (because it's much faster and because ipxe.efi has other problems with other chipsets), is this possible? Or can someone push me in the right direction how I can build a minimal snponly.efi like driver but with rtl8168 driver in it?