Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Booting wds without wimboot
2014-12-10, 21:46
Post: #5
RE: Booting wds without wimboot
Okay, I don't belve that it is an intel networkcard problem since I saw an similar behaviour on a different machine (x64 instead of x86) with rtl8168 driver: Error 0x7f8d101 and 3c086003 with 2a07e006. Only the "socket is not connected error" is missing.

But one after another.
Let's have a look with the initial intel driver (82547ei) machine and ipxe "DEBUG=intel":
Some red lines appear:
1) after loading ipxe.krn and iPXE initialising devices:
INTEL 0xbddc4 MAC+PHY reset (ctrl003c0261)
INTEL 0xbddc4 has autoloaded MAC adress 00:xx:xx:xx:xx:xx (anonymized)
INTEL 0xbddc4 link status is 00000380

2) after Features: AoE HTTP iSCSI DNS TFTP SRP bzImage ELF MBOOT PXE PXEXT Menu
INTEL 0xbddc4 ring 03800 is at [1f64be00,1f64bf00)
INTEL 0xbddc4 ring 02800 is at [1f64bf00,1f64c000)
INTEL 0xbddc4 link status is 00000381

3) after net0: ... [Link status: Down ...] again:
INTEL 0xbddc4 link status is 00000381

(white) Waiting for link-up on net0...
(red) INTEL 0xbddc4 link status is 00000383

4) after pressing F12 and WDSNBP trying to download pxeboot.n12 no more red messages - just failing as decribed.

5) Restearting into commandline 'ifstat' has no red messages, calling 'dhcp' says:
INTEL 0xbddc4 ring 03800 is at [1f64bf00,1f64c000)
INTEL 0xbddc4 ring 02800 is at [1f64c000.1f64c100)
INTEL 0xbddc4 link status is 00000383
INTEL 0xbddc4 link status is 00000383
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
Booting wds without wimboot - chmeyer - 2014-12-01, 21:46
RE: Booting wds without wimboot - chmeyer - 2014-12-10 21:46



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