Quantcast
Viewing all 1484 articles
Browse latest View live
↧

Chainloading from ipxe to multiple pxeboot roms

July 28, 2016, 10:19 am
$
0
0
Hi,

I've set up a server with pxelinux.0 as bootrom that is used to boot different linux distributions via pxe. However, there a several other distributions that require a hardcoded different pxe bootrom. Is it possible that I can pxe boot into ipxe and then chainload into other pxe bootroms?

So basically, I want to create a ipxe boot menu file that is sent to a client after a dhcp request which let's me choose from different pxe roms. Like pxelinux.0, grub.pxe or even pxeboot.n12 and so on...
↧
Search

Whitespace in strings

July 29, 2016, 2:17 pm
$
0
0
How does one go about printing whitespace characters with echo? I'm attempting to center some text and since there is no option to do so with echo (possible feature enhancement?), I figured I'd try some equivalent methods. Escape sequences don't seem to work: [2J successfully clears the screen, but [12C seems to be interpreted (single blank space in output) and then ignored (no movement to the right). 'echo' with blank spaces and then the string only prints the string. 'echo' with quotes around blank spaces and string appears to print the quote, a space, and then the string, with all other leading spaces stripped. I suppose I could do 12x 'echo -n', but is there an easier/better way of doing this?
↧
↧

Linux + New notebook problem

July 30, 2016, 2:35 am
$
0
0
I have new Dell E7470 and have a problem with launch Linux via iPXE.

I try examples like this : http://boot.ipxe.org/demo/boot.php and this: http://ipxe.org/howto/rh_san

But in both examples, i see freezed coursor and nothing more, after successfull process of download kernel and initrd.

Have u any idea? Try in legacy and UEFI. (Freezed in UEFI and Rebooted in Legacy)
↧

VirtualBox compatibility ?

August 2, 2016, 2:32 pm
$
0
0
Hello,

I was using virtualbox 5.0.20 (Win 7 x64) with Extension Pack and iPXE boot worked fine with Intel Pro 1000 MT Desktop Nic (82540EM).

I upgraded to 5.1.2 (extension pack upgraded too) and now when I boot to iPXE :
Image may be NSFW.
Clik here to view. [Image: ipxe-vboxbf67.png]

iPXE stopped on "configuring......." and this error appears : "no more network devices"

I use a proxyDHCP (Tiny PXE Server 1.0.0.19).

When I try with a physical machine (laptop) everything works fine.

Any idea Image may be NSFW.
Clik here to view. Sad ?
↧

Need to support as many devices as possible!

August 4, 2016, 3:06 pm
$
0
0
Hi, I am wondering how I can configure iPXE to support as many different laptops / machines as possible. I repair Laptops & PC's so often the first thing I like to do is boot them from the network and run various tools such as anti-virus scanners, Hardware tests (Memtest, etc), or disk cloning software.

It's been a couple of years since I last played around with iPXE but I still have it all configured and working well with my custom menu and applications (like the ones mentioned above). I think the reason I stopped using it was because I found that I was unable to boot many types of laptops using iPXE so had to resort to using USB flash drives / DVD media for running the tools I needed.

Can anyone advise how I might be able to configure iPXE to support as broad a range of NIC's as possible?

I am using undionly.kpxe built using an embedded basic script which chainloads iPXE. This is the contents of the script:

Code:
#!ipxe

dhcp
chain http://192.168.1.105:8085/boot.ipxe

I use DNSMasq for my DHCP and have the following configured as an additional option:

Code:
dhcp-boot=undionly.kpxe,qnap,192.168.1.105

Many thanks in advance,
Graham
↧
↧

iPXE and Reboot Restore RX

August 8, 2016, 5:25 pm
$
0
0
Folks - I am using FOG to image our PC's. I have been experimenting with using Reboot Restore Rx
(http://www.horizondatasys.com/en/product...#Features)
as a way to roll back changes made to the PC's (we are a public library).

I cannot seem to get iPXE to chain to the hard drive. RRRx always errors out. It boots just fine when I F12 to the hard disk.

Has anyone ever used this software and made it work with iPXE?

Thanks -

Mark
↧

efi booting problem

August 10, 2016, 3:05 am
$
0
0
hi everyone..

I try to boot using ipxe.efi for efi mode.
The boot in VMWare works properly, but not working properly in real PC (DELL).

i used ipxe.efi file : make bin-x86_64-efi/ipxe.efi DEBUG=efi_driver
when I used snponly.efi :make bin-x86-64/snponly.efi ,too.

PC: Dell D7SVS02
NIC: rtl8168

message:
iPXE initialising devices..
EFIDRV connecting our drivers
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) has driver "PCI"
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) disconnecting existing drivers
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) /MAC (c81f6625e234,0x0) has driver "NII"
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) /MAC (c81f6625e234,0x0) DRIVER_START
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) /MAC (c81f6625e234,0x0) is not supported by driver "PCI": Error 0x7f10e183 (http://tpxe.org/7f10e183)
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) /MAC (c81f6625e234,0x0)/IPv4(0,0,0,0) has driver "SNP"
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) /MAC (c81f6625e234,0x0)/IPv4(0,0,0,0) DRIVER_START
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) /MAC (c81f6625e234,0x0)/IPv4(0,0,0,0) is not supported by driver "PCI": Error 0x7f10e183 (http://tpxe.org/7f10e183)
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) /MAC (c81f6625e234,0x0)/IPv4(0,0,0,0) is not supported by driver "NII": Error 0x7f10e183 (http://tpxe.org/7f10e183)
EFIDRV UNKNOEN<0xd0a0d398> could not start driver "SNP": Error 0x7f45e082 (http://tpxe.org/7f45e082)
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) /MAC (c81f6625e234,0x0)/IPv6(0000:0000:0000:0000:0000:0000:0000:0000) has driver "SNP"
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) /MAC (c81f6625e234,0x0)/IPv6(0000:0000:0000:0000:0000:0000:0000:0000) DRIVER_START
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) /MAC (c81f6625e234,0x0)/IPv6(0000:0000:0000:0000:0000:0000:0000:0000) is not supported by driver "PCI": Error 0x7f10e183 (http://tpxe.org/7f10e183)
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) /MAC (c81f6625e234,0x0)/IPv6(0000:0000:0000:0000:0000:0000:0000:0000) is not supported by driver "NII": Error 0x7f10e183 (http://tpxe.org/7f10e183)
EFIDRV UNKNOEN<0xd0a0d398> could not start driver "SNP": Error 0x7f45e082 (http://tpxe.org/7f45e082)

And those messages are repeated.
If anyone know this problem, help me.
↧

iPXE boot failed but 'boot || goto boot_menu' reback to boot menu NOT work

August 16, 2016, 12:44 am
$
0
0
Hi,

When I test iPXE boot menu, boot menu with wrong URL make boot failed.

I have added :

Code:
boot || goto boot_menu

to a boot menu entry, hoping to return back to boot menu when boot failed. But it seem that boot || goto boot_menu NOT work.

Boot failed with a message, and then exit iPXE boot to localdisk :

Code:
Could not boot: No such file or directory (http://ipxe.org/2d0c613b)
Could not boot image: No such file or directory
No more network devices

Here is the Failed screenshot :

Image may be NSFW.
Clik here to view. [Image: Bqi3MO2.png]

My iPXE script :

Code:
#!ipxe
prompt --key 0x02 --timeout 1000 Press Ctrl-B for the iPXE command line... && shell ||

:boot_menu
menu iPXE Clone Menu
item clone      KS Auto Install : centos-7-kvm
item localboot  Boot From Local Disk
item static     gPXE Static Install
item shell      iPXE Shell

choose --default localboot --timeout 30000 target && goto ${target} ||
echo __NOTE: Cancel Enter Select Menu, Exit
exit

:localboot
sanboot --no-describe --drive 0x80 || goto boot_menu

:clone
kernel http=//192.168.10.199/iso/7/images/pxeboot/vmlinuz net.ifnames=0 biosdevname=0 inst.sshd ipv6.disable=1 inst.stage2=http=//192.168.10.199/iso/7 inst.ks=http=//192.168.10.199/ks/ks-centos-7-kvm.cfg ks.device
=bootif BOOTIF=01-${net0/mac:hexhyp}
initrd http=//192.168.10.199/iso/7/images/pxeboot/initrd.img
boot || goto boot_menu
goto boot_menu

:static
set 210:string http://${next-server}/pxe/
set 209:string ${210:string}pxelinux.cfg/default
echo __INFO: chain ${210:string}gpxelinux.0
echo __INFO: ${209:string}
chain ${210:string}gpxelinux.0 ||
goto boot_menu

:shell
echo __NOTE: Type 'config' enter iPXE config setting, 'exit' return to boot menu.
shell
goto boot_menu
↧
Search

ipxe efi booting failed

August 10, 2016, 3:13 am
$
0
0
hi everyone..
i'm not speak English well.

i try ipxe booting with efi pc.
the boot in VMWare was a success, but real PC was failed.

i used ipxe.efi file : make bin-x86_64-efi/ipxe.efi DEBUG=efi_driver
when I used snponly.efi :make bin-x86-64/snponly.efi ,too.
why real pc ipxe booting is failed?
help me.

PC: Dell D7SVS02
NIC: rtl8168

message:
iPXE initialising devices..
EFIDRV connecting our drivers
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) has driver "PCI"
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) disconnecting existing drivers
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) /MAC (c81f6625e234,0x0) has driver "NII"
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) /MAC (c81f6625e234,0x0) DRIVER_START
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) /MAC (c81f6625e234,0x0) is not supported by driver "PCI": Error 0x7f10e183 (http://tpxe.org/7f10e183)
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) /MAC (c81f6625e234,0x0)/IPv4(0,0,0,0) has driver "SNP"
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) /MAC (c81f6625e234,0x0)/IPv4(0,0,0,0) DRIVER_START
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) /MAC (c81f6625e234,0x0)/IPv4(0,0,0,0) is not supported by driver "PCI": Error 0x7f10e183 (http://tpxe.org/7f10e183)
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) /MAC (c81f6625e234,0x0)/IPv4(0,0,0,0) is not supported by driver "NII": Error 0x7f10e183 (http://tpxe.org/7f10e183)
EFIDRV UNKNOEN<0xd0a0d398> could not start driver "SNP": Error 0x7f45e082 (http://tpxe.org/7f45e082)
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) /MAC (c81f6625e234,0x0)/IPv6(0000:0000:0000:0000:0000:0000:0000:0000) has driver "SNP"
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) /MAC (c81f6625e234,0x0)/IPv6(0000:0000:0000:0000:0000:0000:0000:0000) DRIVER_START
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) /MAC (c81f6625e234,0x0)/IPv6(0000:0000:0000:0000:0000:0000:0000:0000) is not supported by driver "PCI": Error 0x7f10e183 (http://tpxe.org/7f10e183)
EFIDRV PciRoot (0x0)/Pci (0x1c,0x4)/Pci(0x0,0x0) /MAC (c81f6625e234,0x0)/IPv6(0000:0000:0000:0000:0000:0000:0000:0000) is not supported by driver "NII": Error 0x7f10e183 (http://tpxe.org/7f10e183)
EFIDRV UNKNOEN<0xd0a0d398> could not start driver "SNP": Error 0x7f45e082 (http://tpxe.org/7f45e082)

And those message is repeated endless
↧
↧

Local boot menu with extended information

August 18, 2016, 8:26 am
$
0
0
Hello,

I need to create a boot menu with only local drives and additional information (bios drive number, bus type, model, serial number, capacity). And allow user to select only boot devices that pass hard-coded filter (I plan to hardcode boot menu and filter rules into "autoboot.c").

I've found some structures in "ata.c", but no code points or examples how to access (or prepare) list of local disks (IDE/SATA/USB). Maybe someone knows good starting point?

Thanks in advance
↧

Local boot menu with extended information

August 18, 2016, 8:30 am
$
0
0
Hello,

I need to create a boot menu with only local drives and additional information (bios drive number, bus type, model, serial number, capacity). And then allow user to select only boot devices that pass hard-coded filter (I plan to hardcode boot menu and filter rules into "autoboot.c").

I've found some structures in "ata.c", but no code points or examples how to access (or prepare) list of local disks (IDE/SATA/USB). Maybe someone knows good starting point?

Thanks in advance
↧

Error Code 0x0000005c during WinPE load

August 18, 2016, 11:03 am
$
0
0
Hi,

I'm using a first generation Hyper-V VM running on a Windows 2012R2 server and booting off of ipxe.iso (with ipxe.krn). I'm using wimboot v.2.5.2 to try and load WinPE. Here is the contents of the script I'm running using the chain command...

Code:
kernel http://x.x.x.x/winpe/wimboot  gui
initrd http://x.x.x.x/winpe/bcd        bcd
initrd http://x.x.x.x/winpe/boot.sdi        boot.sdi
initrd http://x.x.x.x/winpe/boot.wim       boot.wim
boot

I see each of these lines process o.k., then I see WinPE start to load with the blue windows logo in the middle of the screen. Next I get this error message...

Your PC needs to restart.
Please hold down the power button.
Error Code: 0x0000005C
Parameters:
<4 lines of parameters that I don't think will help troubleshoot so I'm not typing them>

I've tried with both WinPE 4.0 and WinPE 5.0 without luck.

If I boot from the WinPE .iso then it loads just fine.

If I don't add the gui parameter after wimboot in my script then I get this message:

Get parameters: C/H/S = 1024/255/63, drives = 1
Get disk type: sectors = 0xfff80040, type = 3
Extensions installation check
<and 2 more lines>

Any ideas why it's failing?
↧

Build iPXE binary (undionly.kpxe) to handle http basic authentication

August 19, 2016, 12:55 am
$
0
0
Hi everyone


I am currently having a troubles to send an HTTP request with basic authentication from a host running an iPXE (undionly.kpxe) binary.

The request http://<login>:<psw>@<ip> sends an http request where the header does not contain any authentication.

I think that the binary that I built does not handle http basic authentication. The command that I used to build it is:
make bin/undionly.kpxe HTTP_AUTH_BASIC=enable DOWNLOAD_PROTO_HTTPS=enable EMBED=<iPxeScript>

Could anyone tell me how to properly build my ipxe binary in order to handle http basic authentication. Or if the request that I wrote on the iPXE script is wrong.
↧
↧

iPXE ESXi 6.0u2 on UEFI -> PSOD

August 23, 2016, 2:23 am
$
0
0
I’m trying to solve a PSOD (purple screen) issue on a ProLiant DL380 Gen9 while installing ESXi via PXE in UEFI mode. The only thing that seems to be consistent is that the system PSOD always at the same point. (Kernel stack is always the same)
All DL380Gen9 which I could get my hands on crash!! The system crashes on any ESXi release!!

The PSOD indicates an hardware issue, but installing via the ISO media works just fine. I found an advisory that describes the issue really good, but it relates to running ESXi servers, not during the ESXI installation and the suggested work-arround doesn’t work.

• I’m focusing on 2 DL380Gen9 servers: 1xLLF (SATA) based, 1x SSF (SAS) based. (both panic with the same error at the same spot)
o ILO is 2.44 (latest from the web)
o System Rom is 2.22_07-18-2016 (latest from the web)
o SPP 2016.04 is loaded
• I have the PSOD with ALL ESXi Releases
o Custom HPE 5.5 update 2 / 5.5 update 3 / 6.0 / 6.0 update 1 / 6.0 update 2
o Orginal VM ware release (6.0 update 2)

• Following advisory describes the issue (only I’m having the PSOD during installation) pretty close
o http://h20564.www2.hpe.com/portal/site/h...-c04912076
o YES the ESXi Panic code is: LINT1/NMI (Motherboard nonmaskable interrupt) undiagnosed
o YES the ILM Log says: Uncorrectable PCI Express Error (Embedded device, Bus 0, Device 0, Function 0, Error status 0x00000000)
Note: the Advisory handles an Error status 0x00100000. Here we have 0x0000000

• Applied workaround of advisory ( Kernelopt in boot.cfg iovDisableIR=TRUE ) but STILL all systems panic
• It isn’t a hardware issue. Installing from ISO works just fine, removed all PCI cards, (even internal Smart Array Ctrl), … still panic.
• Issue is only UEFI mode. Bios mode works fine

o System starts BOOTX64.EFI …. It loads all the modules found in BOOT.CFG.
o The Yellow Startup screen comes up and the gray progress bar at the bottom of the screen progresses.
o Last message of ESXI is “VM Kernel loaded successfully” then system panic


Anyone care to reproduce ? … I’ve got a feeling I hit some undocumented bug.

• IPXE Script Looks like:
#!ipxe
kernel http://<ip-address>/netboot/vmware/6.0_u2/boot/bootx64.efi -c http://<ip-address>/netboot/vmware/6.0_u2/boot/boot.cfg
boot

• Boot.cfg looks like:
bootstate=0
title=Loading ESXi installer
timeout=5
prefix=http://<ip-address>/netboot/vmware/6.0_u2/depot
kernel=tboot.b00
kernelopt=runweasel iovDisableIR=true
modules=b.b00 --- jumpstrt.gz --- useropts.gz --- k.b00 --- chardevs.b00 --- a.b00 --- user.b00 --- uc_intel.b00 --- uc_amd.b00 --- sb.v00 --- s.v00 --- scsi_mpt.v00 --- net_tg3.v00 --- elxnet.v00 --- ima_be2i.v00 --- lpfc.v00 --- scsi_be2.v00 --- amsHelpe.v00 --- conrep.v00 --- hpbootcf.v00 --- hpe_buil.v00 --- hpe_esxi.v00 --- hpe_ilo.v00 --- hpe_smx_.v00 --- hponcfg.v00 --- hpssacli.v00 --- hptestev.v00 --- char_hpc.v00 --- hpnmi.v00 --- scsi_hpd.v00 --- scsi_hps.v00 --- scsi_hpv.v00 --- intelcim.v00 --- net_i40e.v00 --- net_igb.v00 --- net_ixgb.v00 --- nmlx4_co.v00 --- nmlx4_en.v00 --- misc_cni.v00 --- net_bnx2.v00 --- net_bnx2.v01 --- net_cnic.v00 --- net_nx_n.v00 --- net_qlcn.v00 --- qlnative.v00 --- scsi_bfa.v00 --- scsi_bnx.v00 --- scsi_bnx.v01 --- scsi_qla.v00 --- mtip32xx.v00 --- ata_pata.v00 --- ata_pata.v01 --- ata_pata.v02 --- ata_pata.v03 --- ata_pata.v04 --- ata_pata.v05 --- ata_pata.v06 --- ata_pata.v07 --- block_cc.v00 --- ehci_ehc.v00 --- emulex_e.v00 --- weaselin.t00 --- esx_dvfi.v00 --- esx_ui.v00 --- ima_qla4.v00 --- ipmi_ipm.v00 --- ipmi_ipm.v01 --- ipmi_ipm.v02 --- lsi_mr3.v00 --- lsi_msgp.v00 --- lsu_hp_h.v00 --- lsu_lsi_.v00 --- lsu_lsi_.v01 --- lsu_lsi_.v02 --- lsu_lsi_.v03 --- lsu_lsi_.v04 --- misc_dri.v00 --- net_e100.v00 --- net_e100.v01 --- net_enic.v00 --- net_forc.v00 --- net_mlx4.v00 --- net_mlx4.v01 --- net_vmxn.v00 --- nmlx4_rd.v00 --- nvme.v00 --- ohci_usb.v00 --- rste.v00 --- sata_ahc.v00 --- sata_ata.v00 --- sata_sat.v00 --- sata_sat.v01 --- sata_sat.v02 --- sata_sat.v03 --- sata_sat.v04 --- scsi_aac.v00 --- scsi_adp.v00 --- scsi_aic.v00 --- scsi_fni.v00 --- scsi_ips.v00 --- scsi_meg.v00 --- scsi_meg.v01 --- scsi_meg.v02 --- scsi_mpt.v01 --- scsi_mpt.v02 --- uhci_usb.v00 --- vsan.v00 --- vsanheal.v00 --- vsanmgmt.v00 --- xhci_xhc.v00 --- tools.t00 --- nmst.v00 --- xorg.v00 --- imgdb.tgz --- imgpayld.tgz
build=
updated=0
↧

build UEFI ready ipxe-ISO

August 31, 2016, 5:40 am
$
0
0
Hi there,

Anyone know if it is possible to generate a UEFI compatible ipxe ISO?
The current generated ISO does not seem to work on UEFI.

Regards,
Martien
↧
Search

Unable to load boot.ipxe - Please help!

September 1, 2016, 2:23 am
$
0
0
Hi All,

Firstly I'm very new to ipxe so please take it easy Image may be NSFW.
Clik here to view. Smile..

I've so far been completely unable to pxe a machine using it and Im now smashing my head against the desk..

Using pxelinux menu with the below commands:

#---
LABEL IPXE
MENU LABEL IPXE
KERNEL iPXE\iPXE.KRN dhcp && chain http://10.10.10.10/iPXE/boot.ipxe


Boot.ipxe content:

#!ipxe
cpuid --ext 29 && set arch amd64 || set arch x86
boot wimboot
initrd bootmgr bootmgr
initrd ${arch}/media/Boot/BCD BCD
initrd ${arch}/media/Boot/boot.sdi boot.sdi
initrd ${arch}/media/sources/boot.wim boot.wim
imgstat
boot



Now, when I PXE a machine and select the IPXE option on my pxelinux menu, it passes through and load IPXE fine. It then successfully registers dhcp, but then when it attempts to load the boot.ipxe file, it says OK but just completely hangs. Nothing follows that line, and thats it, the machine is then stuck.

The boot.ipxe and all other files are hosted in IIS (mime types etc added) and I can successfully access them in a browser.

Also, If i purely boot to command line IPXE I can successfully download each file using initrd.

I have tried absolutely everything I can think to get this working now with now joy.

Please help!
↧

WinPE Booting multiple operating systems

September 4, 2016, 12:45 am
$
0
0
Hi, there. I'm trying to build a custom Pxeboot menu with a few utilities that I use frequently, I uploaded most of them already and they are working. I would like to add Windows 7 , 8.1 and 10 installations to WinPe, I was following this guide http://ipxe.org/howto/winpe , but have a question about the startup batch file - which is, is it possible that I could write it once for each operating system, so I don't have to type the net use command every time I boot ( This is going to be used multiple times every day and it would save me a lot of time ). What I'm aiming for is to create a menu like "Windows 10 x86" , "Windows 7 x64" etc. and when an option is chosen I'd like it to boot directly as it was booting from a USB. I would eventually like to do the same for UEFI boot as well. If anyone here could point me in the right direction, post a link of a guide or something. I don't have any programming knowledge, but I think I follow steps quite good. Any help would be appreciated. Let me know if you need any information on the setup.
↧
↧

Are old cross-signed certs causing "iPXE cross-signing CA has expired" errors?

September 7, 2016, 12:30 pm
$
0
0
Are any certs still being served from http://ca.ipxe.org/auto signed by the cross-signing cert that expired in Feb 2016?

I see that http://ca.ipxe.org/cross-ca.crt is up to date. However, when running an https download from google cloud storage, ipxe reports that "iPXE cross-signing CA" has expired.

Adding a new debug log line to crypto/x509.c I see that iPXE is using a cross-signing certificate that is valid "not after" 1456479729 (2016-02-26T09:42:09).

See a screen shot here: https://storage.googleapis.com/dash-test...-error.png (I could not upload an attachment for this post)

These are the two HTTP get requests from iPXE for the cross-signed certs (I believe).
Code:
GET /auto/5df65e6d.der?subject=ME4xCzAJBgNVBAYTAlVTMRAwDgYDVQQKEwdFcXVpZmF4MS0wKwYDVQQLEyRFcXVpZmF4​IFNlY3VyZSBDZXJ0aWZpY2F0ZSBBdXRob3JpdHk= HTTP/1.1

GET /ocsp/root/MEIwQDA+MDwwOjAJBgUrDgMCGgUABBSdIkBuCekXxHtcIxfjfzqJURDvHwQUq0EwXAuzDHEHMTwzdkSY​HFHUKnICASk= HTTP/1.1

And, I see that some *.der files have older timestamps than 31-Aug-2016:
http://ca.ipxe.org/auto/ -- one in particular: 5df65e6d.der has an mtime of 01-Nov-2014.

Unfortunately, I'm not able to inspect these .der files; openssl reports:

Code:
$ openssl x509 -inform der -in ~/Downloads/5df65e6d.der -out certificate.pem
unable to load certificate
140437768582816:error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag:tasn_dec.c:1338:
140437768582816:error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error:tasn_dec.c:390:Type=X509

Is this an issue with out-of-date certs? Will it be fixed?

Is there a repository or location for the scripts used to generate the auto/*.der files for self-hosting cross-signed certificate files?

Commands used to build and test.
Code:
$ make EMBED=embed.ipxe bin/ipxe.iso  DEBUG=x509,validator
$ cat embed.ipxe
dhcp
set crosscert http://ca.ipxe.org/auto
kernel https://storage.googleapis.com/dash-test-1/tinycore/vmlinuz
↧

Booting Linux kernel under UEFI hangs immediately after download

September 8, 2016, 2:27 pm
$
0
0
I am attempting to use iPXE to load the installers for various Linux Distributions onto UEFI enabled servers. The server's are able to boot correctly in BIOS mode, but fail when UEFI is enabled. When they fail, it is immediately after successfully downloading both the kernel and initrd. Nothing is printed after the ok message for the ftp download of the initrd and it hangs forever. This happens whether attempting to boot the installer for Ubuntu 16.04, Fedora 24, or CentOS 7.2.

This same setup works correctly when attempting to booth these same installers using the UEFI mode in a KVM/Qemu virtual machine.

Also, experiments with using PXE Grub on real hardware to boot the same kernels have been successful, but it relies on TFTP which is much slower.

Here's my script for installing Ubuntu 16.04:

#!ipxe
kernel ftp://server/pxeboot/ubuntu-installer/amd64/linux initrd=initramfs
initrd --name initramfs ftp://server/pxeboot/ubuntu-installer/amd64/initrd.gz
boot
↧

iPXE EFI - no network after the DHCP sequence

September 12, 2016, 9:21 am
$
0
0
Hi,

we are experiencing multiple issues while booting with iPXE for UEFI.

We have compiled it as "snp.efi" (app) and "snp.efidrv" (driver).

While booting with iPXE included as an EFI driver in our firmware, the Intel NIC is seen, then the DHCP sequence is done and the client receives its IP parameters. However, it fails to continue (HTTP download timeout). At this step, we noticed that the client and the server cannot ping themselves (whereas the DHCPACK has been received by the client), and the client emits lots of ARP WHO-HAS to know the MAC address of the server.

Here are the corresponding traces:

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

net0: 08:00:38:b0:90:ad using NII on NII-0000:02:00.0 (open)
[Link:up, TX:0 TXE:0 RX:2993 RXE:6]
[RXE: 4 x "Network unreachable (http://ipxe.org/28056090)"]
[RXE: 2 x "Operation not supported (http://ipxe.org/3c086083)"]
DHCP 0xa7e02308 entering discovery state
Configuring (net0 08:00:38:b0:90:ad)...DHCP 0xa7e02308 DHCPDISCOVER
.DHCP 0xa7e02308 DHCPDISCOVER
DHCP 0xa7e02308 DHCPOFFER from 10.0.0.10:67 for 10.0.30.103
..DHCP 0xa7e02308 entering request state
DHCP 0xa7e02308 DHCPREQUEST to 10.0.0.10:67 for 10.0.30.103
DHCP 0xa7e02308 DHCPACK from 10.0.0.10:67 for 10.0.30.103
ok
net0: 10.0.30.103/255.255.0.0 gw 10.0.255.254
Next server: 10.0.0.10
Filename: http://10.0.0.10/tftpboot/boot.ipxe
http://10.0.0.10/tftpboot/boot.ipxe....... Operation canceled (http://ipxe.org/0b072095)

iPXE> ifstat
net0: 08:00:38:b0:90:ad using NII on NII-0000:02:00.0 (open)
[Link:up, TX:7 TXE:4 RX:4992 RXE:137]
[TXE: 4 x "Error 0x2a376089 (http://ipxe.org/2a376089)"]
[RXE: 56 x "Network unreachable (http://ipxe.org/28056090)"]
[RXE: 25 x "Operation not supported (http://ipxe.org/3c086083)"]
[RXE: 56 x "Invalid argument (http://ipxe.org/1c056082)"]
net1: 00:a0:c9:00:00:01 using NII on NII-0000:02:00.1 (closed)
[Link:down, TX:0 TXE:0 RX:0 RXE:0]
[Link status: Unknown (http://ipxe.org/1a086194)]
iPXE> ping 10.0.0.10
0 bytes from <none>: seq=1: Connection timed out (http://ipxe.org/4c1b2092)
0 bytes from <none>: seq=2: Connection timed out (http://ipxe.org/4c1b2092)
0 bytes from <none>: seq=3: Connection timed out (http://ipxe.org/4c1b2092)
Finished: Operation canceled (http://ipxe.org/0b072095)
iPXE>

As you can see, there a few network errors, but this doesn't seem to be the root cause of this issue: that works well with the snp.efi application when it is launched from an EFI shell !

Does someone has an idea about this issue (or what we are doing wrong) ?

We have a second issue which is really less important at this step, because we have a workaround. Even with the snp.efi application, we need to add a 'sleep' of 10 seconds after retrieving the kernel and the initrd to avoid a kernel crash in the first second (while enumerating the cores [smpboot]).

Many thanks for any help. Please let me know if more traces might help.


regards,
--
Christophe
↧
Viewing all 1484 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>