Post Reply 
 
Thread Rating:
  • 1 Vote(s) - 4 Average
  • 1
  • 2
  • 3
  • 4
  • 5
DHCP configuring error 0x40ee186
2015-06-26, 16:10
Post: #11
RE: DHCP configuring error 0x40ee186
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?
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: DHCP configuring error 0x40ee186 - yavuz - 2015-06-26 16:10



User(s) browsing this thread: 1 Guest(s)