iPXE discussion forum

Just started to use iPXE with WIMBOOT and I am having a bit of difficulty and was wondering if someone could point me in the right direction. Currently the PXE service boots with syslinux 6 on Ubuntu 12.10.
When I use the following:
LABEL wimbootpe
menu label ^2 Wimboot
com32 linux.c32
append wimboot initrd=bootmgr,Boot/boot.wim

I get the following
BAD CPIO magic,
FAtalL Could not extract initrd files
Press a key to reboot.

I have been able to use ipxe.lkrn to successfylly boot a WIM file with with the following:
LABEL iPXE
menu label iPXE
#kernel ipxe.lkrn
kernel ipxe.lkrn dhcp && chain http://192.168.1.2/boot.ipxe

However this speed result are not what I was expecting, it takes about 1 minute to download the wim file and boot. From what I read I though this was have accord in lest the 5 sec.

Also. I have placed all the files nessarry in the root directory of the web server like so
#!ipxe

kernel http://192.168.1.2:80/wimboot
initrd http://192.168.1.2:80/bootmgr bootmgr
initrd http://192.168.1.2:80/bootmgr.exe bootmgr.exe
initrd http://192.168.1.2:80/boot/bcd BCD
initrd http://192.168.1.2:80/boot/boot.sdi boot.sdi
initrd http://192.168.1.2:80/sources/boot.wim boot.wim
boot

however bootmgr did not extract bootmgr.exe, I had to manually place it in the directory. Otherwise the system would hang.

Please let me know what I a doing wrong. Thank you

(2013-10-27 23:52)ylafont Wrote: [ -> ]However this speed result are not what I was expecting, it takes about 1 minute to download the wim file and boot. From what I read I though this was have accord in lest the 5 sec.

Which iPXE driver are you using? If you type "ifstat" from the iPXE command line, it should show you which driver is in use for your NIC.

Michael

(2013-10-29 17:30)mcb30 Wrote: [ -> ]

(2013-10-27 23:52)ylafont Wrote: [ -> ]However this speed result are not what I was expecting, it takes about 1 minute to download the wim file and boot. From what I read I though this was have accord in lest the 5 sec.

Which iPXE driver are you using? If you type "ifstat" from the iPXE command line, it should show you which driver is in use for your NIC.

Michael

results from ifstat.

NET0: using 82557lm on PCI00:19.0
RXE 3 x "Operations not supported" (http://ipxe.org/3c086003)
RXE 57 x "the sockect is not connected" (http://ipxe.org/380f6001)
RXE 1 x "invalid argument" (http://ipxe.org/1c056002)

I am not sure, if i have something incorrectly configured or of i have missed a step, although i think i have viewed all the documentation.

when type show hostname or show filename as the example demostrate i get

"could not find ' hostname or filename' " no such file or directory. http://ipxe.org.2d0c203b.

please let me know. thank you.,

(2013-10-29 18:32)ylafont Wrote: [ -> ]results from ifstat.

NET0: using 82557lm on PCI00:19.0

The string "82557lm" does not appear anywhere within the iPXE codebase. Are you using a modified version of iPXE?

Michael

(2013-10-29 23:47)mcb30 Wrote: [ -> ]

(2013-10-29 18:32)ylafont Wrote: [ -> ]results from ifstat.

NET0: using 82557lm on PCI00:19.0

The string "82557lm" does not appear anywhere within the iPXE codebase. Are you using a modified version of iPXE?

Michael

don't think so, unless running make under VMWARE gives me those results. I download again and ran make on a new vmware image. I got the same results but different numbers.

syslinux menu
LABEL iPXE
menu label iPXE
kernel ipxe.lkrn dhcp && chain http://192.168.1.2/boot.ipxe

net0 using 82577lm
RXE 10 x "Operation not supported"
RXE 141 x "The socket is not connected"
RXE 1 x "invalid argument"


Here is a picture
https://dl.dropboxusercontent.com/u/5885...235929.jpg

It was indeed a typo. This seems to be the supported card we're talking about: pci,8086,10ea,"Intel Corporation","82577LM Gigabit Network Connection",intel,82577lm,82577LM,src/drivers/net/intel.c,no

I think this might be the pxelinux 6.x / ipxe issue we've seen before. Does things work if you downgrade to pxelinux 5.x, 4.x or 3.86?