Dell iPXE issues
-
the kernel won’t have anything to do with this, you need to update your ipxe files instead.
-
Still having the same issues with updated ipxe files.
Booting from ipxe usb with debug gives me
[CODE]iPXE initialising devices…Adding 3c509 root bus
Adding EISA root bus
Adding Hyper-V root bus
Failed to add Hyper-V root bus: No such device (http://ipxe.org/2c83403b)
Adding ISA root bus
Adding ISAPnP root bus
Adding MCA root bus
Adding PCI root bus
PCI 00:00.0 (8086:0044 CLASS 060000) has no driver
PCI 00:02.0 (8086:0046 CLASS 030000) has no driver
PCI 00:16.0 (8086:3b64 CLASS 078000) has no driver
PCI 00:1a.0 (8086:3b3c CLASS 0c0320) has no driver
PCI 00:1b.0 (8086:3b56 CLASS 040300) has no driver
PCI 00:1c.0 (8086:3b42 CLASS 060400) has no driver
PCI 00:1c.1 (8086:3b44 CLASS 060400) has no driver
PCI 00:1d.0 (8086:3b34 CLASS 0c0320) has no driver
PCI 00:1e.0 (8086:2448 CLASS 060401) has no driver
PCI 00:1f.0 (8086:3b0b CLASS 060100) has no driver
PCI 00:1f.2 (8086:3b2f CLASS 010601) has no driver
PCI 00:1f.3 (8086:3b30 CLASS 0c0500) has no driver
PCI 00:1f.6 (8086:3b32 CLASS 118000) has no driver
PCI 01:00.0 (1969:1062) has driver “undipci”
PCI 01:00.0 has mem 90500000 io 1000 irq 7
UNDI 0xdbb04 loading UNDI ROM 0xdbb84 to CS 964b DS 9165 for PCI 01:00.0
UNDI 0xdbb04 loaded PXENV+ 964b:00d0 !PXE 964b:0070 entry 964b:0106
UNDI 0xdbb04 using [581,614) kB of base memory
UNDINIC 0xdbb04 using UNDI 0xdbb04
UNDINIC 0xdbb04 has MAC address d4:b3:d9:05:f4:49 and IRQ 7
UNDINIC 0xdbb04 has type DIX+802.3, speed 1000000, flags 0000dc1b
UNDINIC 0xdbb04 using interrupt mode
UNDINIC 0xdbb04 added
PCI 02:00.0 (8086:0087) has driver “undipci”
PCI 02:00.0 has mem 90400000 io 0 irq 10
PCI 02:00.0 probe failed: No such device (http://ipxe.org/2c80603b)[/CODE]I think this is going to end up being an iPXE issue, so I went ahead and posted the issue on the iPXE forums. I will let y’all know if a fix is found.
Thanks everybody for the help.
-
You seem to have more than one network adapter… This is the one you propably want to make work (the second one is a wireless adapter):
[CODE]PCI 01:00.0 (1969:1062) has driver “undipci”
PCI 01:00.0 has mem 90500000 io 1000 irq 7
UNDI 0xdbb04 loading UNDI ROM 0xdbb84 to CS 964b DS 9165 for PCI 01:00.0[/CODE]
Trying to find other people having used iPXE with 1969:1062 network card didn’t show up a lot of results when searching on the web. There is just an old post from 2011: [url]http://lists.ipxe.org/pipermail/ipxe-devel/2011-November/001024.html[/url] (see the ID there and read up a couple of post before that)…iPXE mailinglist is definitely the better place to find out about this! Would be great if you’d report back on how things turned out…
-
Hey all figure I’d give an update.
Never heard anything back from the iPXE community but pressed on and almost got it solved.
I added [COLOR=#ff0000]PCI_ROM(0x1969, 0x1062, “atl1e_62”, “Attansic L1E 0x1062”, 0),[/COLOR] drivers/net/atl1e.c and rebuilt iPXE and the laptop now fully loads iPXE! <I ran around the library when this happened>
Unfortunately I get /default.ipxe…Connection times out after a few minutes.
From the iPXE shell running dhcp<fails>, ifconf<passes> i can then chain the file.
If i leave out dhcp ifconf fails, if I run ifconf first it fails but then if I run dhcp it passes which doesn’t make any since to me.
So in a confusing summary:
dhcp(fail)>ifconf>chain - works
ifconf(fail)>dhcp>chain - works
dhcp(fail)>dhcp>chain - works
ifconf(fail)>ifconf>chain - worksSet ipxescript to the following:
[CODE]#!ipxe
ifclose
ifopen && goto bootme || goto netstart
:netstart
dhcp
ifopen || reboot
isset ${next-server} && goto netboot || goto setserv
:setserv
echo -n Please enter tftp server: && read next-server && goto bootme
:bootme
isset ${next-server} && goto netboot ||
set next-server ${proxydhcp/next-server}
isset ${next-server} && goto netboot || goto netstart
:netboot
ifopen
dhcp || ifconf
chain tftp://${next-server}/default.ipxe || shell
[/CODE]Which then gives:
Configuring (net0 d4:be:d9:05:f4:49)…Error 0x040ee19 ([url]http://ipxe.org/040ee119[/url])
Configuring (net0 d4:be:d9:05:f4:49)…Error 0x040ee19 ([url]http://ipxe.org/040ee119[/url])And the boot process restarts. Any suggestions?
-
Do you have STP enabled on your network (if so can you disable it temporarily or enable Rapid STP/Portfast?)
-
Same thing, the process only hangs on this particular model of laptop. I can get everything to load manually, but anything done through ipxescript fails.
-
More updates!
Enabled DEBUG=dhcp,tftp,http in the current ipxe build and this is the error that is thrown when running the dhcp command.
[CODE]DHCP 0x27f64 entering discovery state
DHCP 0x27f64 DHCPDISCOVER
DHCP 0x27f64 could not transmit UDP packet: Error 0x7f86216b (http://ipxe.org/7f86216b)
DHCP 0x27f64 DHCPDISCOVER
DHCP 0x27f64 could not transmit UDP packet: Error 0x7f86216b (http://ipxe.org/7f86216b)
DHCP 0x27f64 DHCPDISCOVER
DHCP 0x27f64 could not transmit UDP packet: Error 0x7f86216b (http://ipxe.org/7f86216b)
DHCP 0x27f64 DHCPDISCOVER
DHCP 0x27f64 could not transmit UDP packet: Error 0x7f86216b (http://ipxe.org/7f86216b)
Error 0x040ee19 (http://ipxe.org/040ee19)[/CODE]Running dhcp again gives this.
[CODE]DHCP 0x27f64 entering discovery state
DHCP 0x27f64 DHCPDISCOVER
DHCP 0x27f64 DHCPOFFER from 10.1.1.1:67 (10.1.1.10) for 10.1.1.104
.DHCP 0x27f64 DHCPDISCOVER
DHCP 0x27f64 DHCPOFFER from 10.1.1.1:67 (10.1.1.10) for 10.1.1.104
.DHCP 0x27f64 entering request state
.DHCP 0x27f64 DHCPREQUEST to 10.1.1.10:67 for 10.1.1.104
DHCP 0x27f64 DHCPACK from 10.1.1.1:67 (10.1.1.10) for 10.1.1.104[/CODE]10.1.1.1 - Gateway
10.1.1.10 - DHCP
10.1.1.104 - ClientI will solve this, I must.
-
This post is deleted! -
[quote=“Tom Elliott, post: 43307, member: 7271”]Do you have STP enabled on your network (if so can you disable it temporarily or enable Rapid STP/Portfast?)[/quote]
HELLO Tom has a valid point here. If STP is enabled and you don’t have Portfast enabled it will cause iPXE not to work or work sporadically.
[url]http://fogproject.org/wiki/index.php/IPXE#What_do_I_enable_and_disable.3F[/url] -
RSTP is enabled and here is the config for the interface on the switch:
[CODE]interface GigabitEthernet0/6
switchport access vlan 100
switchport mode access
switchport nonegotiate
switchport voice vlan 200
spanning-tree portfast
[/CODE] -
More modifications to the ipxescript and it works!!!
I know this is a very specific use case and probably a horrible way to go about it, but if it helps here are the modifications I made.
[CODE]#!ipxe
ifclose
ifopen && goto bootme || goto netstart
:netstart
dhcp && goto netboot || goto netstart
:setserv
echo -n Please enter tftp server: && read next-server && goto bootme
:bootme
isset ${next-server} && goto netboot ||
set next-server ${proxydhcp/next-server}
isset ${next-server} && goto netboot || goto netstart
:netboot
ping -c 1 FOG IP || goto netstart
chain tftp://${next-server}/default.ipxe || shell
[/CODE]Thank you guys for all of your help and thanks to all the devs for everything. Fog is a truly amazing imaging system.
-
Awsome that you got it running now!
Have you talked to iPXE devs too?? Or do you mean FOG devs? I am just wondering because maybe iPXE devs would be able to help out fixing the driver itself. But if this is working for you, you might just leave it like that. Unfortunately I neither have the time nor the hardware to help with this any further although I’d love to help to get this properly fixed.
