Quantcast
Channel: iPXE discussion forum - All Forums
Viewing all 1484 articles
Browse latest View live
↧

How can I use ipxe without Tiny PXE Server

April 14, 2016, 11:35 pm
$
0
0
Hi devs,
First i'm sorry for my bad English.
I just want to use only ipxe without needed 3rd tool.
I booted VM from network then press Ctrl B to type command.
Follow demo guide, i type dhcp then chain to out demo.php (ipxe script). It work fine.
Since it work fine with our demo ipxe script, i try with my ipxe script on real machine.
I try to create a small menu.ipxe and put at root directory.
Run WM, boot from network then type command (see my screenshot)
It say that connection timed out.
I do not which step i did wrong. If i try 3rd tool (Tiny PXE server then menu.ipxe was configured by ipxe).
Please give me some hints. Tks
↧
Search

iPXE EFI build fails with PXE_STACK defined

April 19, 2016, 8:21 pm
$
0
0
I am trying to build an EFI version of iPXE for distribution to Apple laptops, so I may chainload PXE.

The command I am using is
Code:
make bin-x86_64-efi/ipxe.efi
. The build, after some time, halts with an error:

Code:
[AR] bin-x86_64-efi/blib.a
ar: creating bin-x86_64-efi/blib.a
  [HOSTCC] util/elf2efi64
  [VERSION] bin-x86_64-efi/version.ipxe.efi.o
  [LD] bin-x86_64-efi/ipxe.efi.tmp
bin-x86_64-efi/blib.a(librm.o): In function `pm_esp':
(.data.pm_esp+0x0): relocation truncated to fit: R_X86_64_32 against symbol `_estack' defined in .stack section in bin-x86_64-efi/blib.a(stack.o)
bin-x86_64-efi/blib.a(librm.o): In function `real_to_prot':
(.text16.real_to_prot+0x1): relocation truncated to fit: R_X86_64_PC16 against symbol `enable_a20' defined in .text16.early section in bin-x86_64-efi/blib.a(liba20.o)
bin-x86_64-efi/blib.a(librm.o): In function `real_to_prot':
(.text16.real_to_prot+0x8): relocation truncated to fit: R_X86_64_16 against symbol `rm_ds' defined in .text16.data.rm_ds section in bin-x86_64-efi/blib.a(librm.o)
bin-x86_64-efi/blib.a(librm.o): In function `real_to_prot':
(.text16.real_to_prot+0x25): relocation truncated to fit: R_X86_64_16 against `.bss16.rm_virt_addrs'
bin-x86_64-efi/blib.a(librm.o): In function `real_to_prot':
(.text16.real_to_prot+0x2b): relocation truncated to fit: R_X86_64_16 against `.data16.gdt'
bin-x86_64-efi/blib.a(librm.o): In function `real_to_prot':
(.text16.real_to_prot+0x4a): relocation truncated to fit: R_X86_64_32 against `.text.real_to_prot'
bin-x86_64-efi/blib.a(librm.o): In function `r2p_pmode':
(.text.real_to_prot+0x10): relocation truncated to fit: R_X86_64_32 against `.data.pm_esp'
bin-x86_64-efi/blib.a(librm.o): In function `r2p_pmode':
(.text.real_to_prot+0x17): relocation truncated to fit: R_X86_64_32 against symbol `idtr32' defined in .data.idtr32 section in bin-x86_64-efi/blib.a(librm_mgmt.o)
bin-x86_64-efi/blib.a(librm.o): In function `r2p_pmode':
(.text.real_to_prot+0x1e): relocation truncated to fit: R_X86_64_32 against symbol `rm_ss' defined in .bss.rm_ss section in bin-x86_64-efi/blib.a(librm.o)
bin-x86_64-efi/blib.a(librm.o): In function `r2p_pmode':
(.text.real_to_prot+0x27): relocation truncated to fit: R_X86_64_32 against symbol `rm_sp' defined in .bss.rm_sp section in bin-x86_64-efi/blib.a(librm.o)
bin-x86_64-efi/blib.a(librm.o): In function `prot_to_real':
(.text.prot_to_real+0x2): additional relocation overflows omitted from the output
bin-x86_64-efi/blib.a(pxe_entry.o): In function `pxe_segments':
(.text16.data+0x26): undefined reference to `_data16_memsz'
bin-x86_64-efi/blib.a(pxe_entry.o): In function `pxe_segments':
(.text16.data+0x2e): undefined reference to `_data16_memsz'
bin-x86_64-efi/blib.a(pxe_entry.o): In function `pxe_segments':
(.text16.data+0x36): undefined reference to `_text16_memsz'
bin-x86_64-efi/blib.a(pxe_entry.o): In function `pxe_segments':
(.text16.data+0x3e): undefined reference to `_text16_memsz'
bin-x86_64-efi/blib.a(pxe_entry.o): In function `pxenv':
(.text16.data+0x76): undefined reference to `_data16_memsz'
bin-x86_64-efi/blib.a(pxe_entry.o): In function `pxenv':
(.text16.data+0x82): undefined reference to `_data16_memsz'
bin-x86_64-efi/blib.a(pxe_entry.o): In function `pxenv':
(.text16.data+0x86): undefined reference to `_text16_memsz'
Makefile.housekeeping:1104: recipe for target 'bin-x86_64-efi/ipxe.efi.tmp' failed
make: *** [bin-x86_64-efi/ipxe.efi.tmp] Error 1
rm bin-x86_64-efi/version.ipxe.efi.o

The curious thing about this is that I can compile iPXE as an ISO completely fine, however the exact same code will not build as an EFI. The only change being that I have defined PXE_STACK in config/general.h

Code:
/*
* PXE support
*
*/
#define    PXE_STACK        /* PXE stack in iPXE - you want this! */
//#undef    PXE_MENU        /* PXE menu booting */

I am compiling the code against the current git master branch. Using gcc:
Code:
gcc (Ubuntu 5.2.1-22ubuntu2) 5.2.1 20151010
And on Ubuntu 15.10.
↧
↧

iPXE on Mac - No more network devices

April 22, 2016, 6:39 am
$
0
0
Hello,
First sorry for my english.
I'm trying run iPXE on iMac6,1 (EFI x86), but without success. I got a message:
No more network devices.

So, I decided recompile ipxe efi executable image with DEBUG flags. After that, generally I see two error codes: 0x7f10e18f and 0x7f37e08e.

I've copied screen output by hand:

-> only DEBUG=efi_pci

Quote:000 has driver "m88e8053"
EFIPCI 02010c00d041030a000000001010600001c010106000000 has driver "m88e8053"
EFIPCI 02010c00d041030a000000001010600001c010106000000 has driver "m88e8053"
EFIPCI 02010c00d041030a000000001010600001c010106000000 could not open PCI device: Error 0x7f10e18f (http://ipxe.org/7f10e18f)
HANDLE 02010c00d041030a000000001010600001c010106000000 PciIo opened 21x (H) by DxeCore(?) for <NULL>
HANDLE 02010c00d041030a000000001010600001c010106000000 PciIo opened 1x (D) by Marvell® Yukon™ UNDI
HANDLE 02010c00d041030a000000001010600001c010106000000 PciIo opened 1x (G) by Simple Network Protocol Driver for UNKNOWN<0xbeeb9610,78ee99fb-6a5e-4186-97de-cd0aba345a74>
HANDLE 02010c00d041030a000000001010600001c010106000000 PciIo opened 1x © by Marvell® Yukon™ UNDI for UNKNOWN<0xbeeb9610,78ee99fb-6a5e-4186-97de-cd0aba345a74>
ok

-> only DEBUG=efi_driver

Quote:iPXE initalising devices...EFIDRV connecting our drivers
EFIDRV 02010c00d041030a000000001010600001c010106000000 has driver "PCI"
EFIDRV 02010c00d041030a000000001010600001c010106000000 disconnecting existing drivers
EFIDRV 02010c00d041030a000000001010600001c010106000000 could not disconnect existing drivers: Error 0x7f37e08e (http://ipxe.org/7f37e0e)
EFIDRV 02010c00d041030a000000001010600001c010106000000 connecting new drivers
EFIDRV 02010c00d041030a000000001010600001c010106000000 has driver "PCI"
EFIDRV 02010c00d041030a000000001010600001c010106000000 DRIVER_START
EFIDRV 02010c00d041030a000000001010600001c010106000000 could not start driver "PCI" Error 0x7f10e18f (http://ipxe.org/7f10e18f)
EFIDRV 02010c00d041030a000000001010600001c010106000000 could not connect new drivers: Error 0x7f37e08e (http://ipxe.org/7f37e0e)
ok

-> both DEBUG=efi_pci,efi_driver

Quote:e: Error 0x7f10e18f (http://ipxe.org/7f10e18f)
HANDLE 02010c00d041030a000000001010600001c010106000000 PciIo opened 21x (H) by DxeCore(?) for <NULL>
HANDLE 02010c00d041030a000000001010600001c010106000000 PciIo opened 1x (D) by Marvell® Yukon™ UNDI
HANDLE 02010c00d041030a000000001010600001c010106000000 PciIo opened 1x (G) by Simple Network Protocol Driver for UNKNOWN<0xbeeb9610,78ee99fb-6a5e-4186-97de-cd0aba345a74>
HANDLE 02010c00d041030a000000001010600001c010106000000 PciIo opened 1x © by Marvell® Yukon™ UNDI for UNKNOWN<0xbeeb9610,78ee99fb-6a5e-4186-97de-cd0aba345a74>
EFIDRV 02010c00d041030a000000001010600001c010106000000 could not start driver "PCI" Error 0x7f10e18f (http://ipxe.org/7f10e18f)
EFIDRV 02010c00d041030a000000001010600001c010106000000 could not connect new drivers: Error 0x7f37e08e (http://ipxe.org/7f37e0e)
ok

-> DEBUG=device,pci,efi_pci,efi_driver

Quote:DxeCore(?) for <NULL>
HANDLE 02010c00d041030a000000001010600001c010106000000 PciIo opened 1x (D) by Marvell® Yukon™ UNDI
HANDLE 02010c00d041030a000000001010600001c010106000000 PciIo opened 1x (G) by Simple Network Protocol Driver for UNKNOWN<0xbeeb9610,78ee99fb-6a5e-4186-97de-cd0aba345a74>
HANDLE 02010c00d041030a000000001010600001c010106000000 PciIo opened 1x © by Marvell® Yukon™ UNDI for UNKNOWN<0xbeeb9610,78ee99fb-6a5e-4186-97de-cd0aba345a74>
EFIDRV 02010c00d041030a000000001010600001c010106000000 could not start driver "PCI" Error 0x7f10e18f (http://ipxe.org/7f10e18f)
EFIDRV 02010c00d041030a000000001010600001c010106000000 could not connect new drivers: Error 0x7f37e08e (http://ipxe.org/7f37e0e)
Failed to add EFI root bus: Error 0x7f37e08e (http://ipxe.org/7f37e08e)
Adding PCI root bus
ok

My network card is Marvell Yukon II 88E8053 (11ab:4362, driver sky2). This card is supported by iPXE so I don't understand my problems. Please help and thank you in advance.

Best Regards,
Piotr
↧

Problem chainloading syslinux.efi from iPXE

April 28, 2016, 1:57 am
$
0
0
I have compiled iPXE from the Github repository and I'm trying to use it on a UEFI system to chainload into our SysLinux-based PXE system.

As it is, iPXE does not like the syslinux.efi it is grabbing:

[Image: IPXE_EFI2.png]
[Image: IPXE_EFI3.png]

I've blanked out our public IP address. The above is a VM, on a physical box it reboots before I can grab the output. The ultimate purpose of this is to have a UEFI bootable memory stick that can bypass DHCP and boot to a specific PXE server using a static IP number. For now it gets an IP from DHCP and then overrides the values.

Here is the embedded script content:

Code:
#!ipxe
echo Built by MGR on 28 April, 2016
set syslog xxx.xxx.xxx.12

# Default student PXE server
set next-server xxx.xxx.xxx.12

# Offer manual IP configuration
prompt --timeout 3000 Press a key to configure network manually, or wait for DHCP. || goto godhcp

# Manual IP configuration
echo In the configurator go into the 'net0' or 'net1' sub-menu and configure these
echo three fields for the VLAN this PC is connected to:
echo gateway
echo ip
echo netmask
prompt Press a key when ready to begin.
config
ifopen
echo The default route is configured as follows:
route
prompt --timeout 3000 Press a key to enter shell, or wait for PXE boot. || goto gopxe
shell
goto gopxe

# Get a DHCP address
echo Obtaining an IP number from DHCP...
:godhcp
dhcp || goto godhcp
echo DHCP has given IP number ${netX/ip} for MAC ${netX/mac}
echo Gateway IP: ${netX/gateway}
prompt --timeout 3000 Press a key to enter shell, or wait for PXE boot. || goto gopxe
shell

:gopxe
# Offer a Staff network option
prompt --timeout 3000 Press a key for Staff network PXE, or wait for Student network PXE. || goto gogopxe
set next-server xxx.xxx.xxx.13

:gogopxe
set netX/next-server ${next-server}

# EFI or BIOS?
iseq ${platform} efi && goto efi || goto bios

:bios
set filename pxelinux.0
goto gogogopxe

:efi
set filename syslinux.efi

:gogogopxe
set netX/filename ${filename}
echo PXE server is ${netX/next-server}
echo PXE boot file is ${netX/filename}

# Set SYSLINUX configfile
set 210 http://${next-server}/
set 209 pxelinux.cfg/default

# PXE boot
chain http://${next-server}/${filename}

I have tried various 64-bit versions of syslinux.efi, including 6.03 binaries provided on the website and compiling my own from the source. None of them work, so I suspect my iPXE build is not configured correctly.

In config/general.h I have set:

#define IMAGE_EFI

Are there any other configuration changes I need to make to get this working? Or additional debugging I can add to 'DEBUG=dhcp:2,tftp:2,http:2,image:7,efi_init:7,efi_image:7' that would provide useful output?

Thanks.
↧

Recently iPXE don't chainboot.

April 26, 2016, 10:49 pm
$
0
0
About one years ago, I sucessed iPXE chainbooting.
I use iPXE 1.0.0+ (acc27) build.

But I tried chainboot by recently iPXE build.
I failed iPXE chainboot.
I use iPXE 1.0.0+(55e4).

Environment is same.
same server, same client.

Why?

Code:
Intel UNDI. PXE-2.1 (build 002)
Copyright (C) 1997-2000 Intel Corporation

For RealTek RTL8111B/8111C Gigabyte Ethernet Controller v2.14(000225)

CLIENT MAC ADDR: 00 25 11 CB 41 1B GUID 00020003-0004-0005-0006-00700080009
CLIENT IP: 172.20.10.83 MASK 255.255.0.0
DHCP IP: 172.20.0.70 PROXY IP:172.20.0.225
GATEWAY IP: 172.20.0.254

Auto-Select:
     splash

BOOT SERVER IP : 172.20.0.225

PXE-EB: !PXE at 9C3E:0070,entry point at 9C3E:0109
             UNDI code segment 9C3E:1A7A, data segment 923D:A010 (584-632kB)
             UNID device is PCI 02:00.0, type DIX+802.3
             584kB free base memory after PXE unload
iPXE initialising devices...ok

iPXE 1.0.0+ (55e4) -- Open Source Network Boot Firmware -- http://ipxe.org
Features: DNS HTTP iSCSI TFTP AoE ELF MBOOT PXE bzImage Menu PXEXT

net0: 00:25:11:cb:41:1b using undionly on UNDI-PCI02:00,0 (open)
  [Link:up, TX:0 TXER:0 RX:0 RXE:0]
Configuring (net0 00:25:11:cb:41:1b)....ok
net0: 172.20.10.83/255.255.0.0 gw 172.20.0.254
Nothing to boot: No such file or directory
No more network devices

Press Ctrl+B for the iPXE command line...


I found out old build chainboot fine.
I searched chainbooting recently iPXE build.

It is chainbooting underline.
https://git.ipxe.org/ipxe.git/commit/ba3...59c339bfa6
Code:
[settings] Re-add "uristring" setting type
author    Michael Brown <mcb30@ipxe.org>    
Tue, 25 Aug 2015 20:33:40 +0900 (12:33 +0100)
committer    Michael Brown <mcb30@ipxe.org>    
Tue, 25 Aug 2015 21:31:46 +0900 (13:31 +0100)
commit    ba3695353add020b686547699ba5e259c339bfa6
tree    d400084f87152adbbbc7dbca3140c1c2789c03b0    tree | snapshot (tar.gz tar.bz2 zip)
parent    4e03af8ec2d497e725566a91fd5c19dd604c18a6

After commit source, It cannot chainboot.

Enviroment
Server
- Debian Wheezy (Linux pxeserver 3.2.0-4-amd64 #1 SMP Debian 3.2.78-1 x86_64 GNU/Linux)
- ECS 945GCT-M
- Intel® Pentium® Dual CPU E2160 @ 1.80GHz
- Dnsmasq 2.62-3+deb7u3
- iPXE (undionly.kpxe)
Client
- Desktop PC
- ECS G43T-M5
- Realtec PCIe GBE Family Controller
- Intel UNDI,PXE-2.0 (bulid 082)
- Realtek RTL8139(A/B/C)/RTL8130 PCI Fast Ethernet Controller v2.11

dnsmasq conf
Code:
root@pxeserver:~# cat /etc/dnsmasq.conf | grep -v -e ^# -e ^$
dhcp-range=172.20.0.0,proxy
dhcp-boot=tag:!ipxe,undionly.kpxe,172.20.0.225
dhcp-match=set:ipxe,175 # gPXE/iPXE sends a 175 option.
dhcp-boot=tag:!ipxe,undionly.kpxe
dhcp-boot=tag:ipxe,http://172.20.0.225/a.ipxe
pxe-service=tag:!ipxe,x86PC,"splash",undionly.kpxe
enable-tftp
tftp-root=/var/ftpd
log-queries
conf-dir=/etc/dnsmasq.d

Is dnsmasq.conf settings wrong?
Old build can chainbooting.
I don't think it wrong.

I get two packet caputure chainbooting and not chainbooting by tcpdump.
I share it for you by cloudshark.

Chainboot sucess!
iPXE 1.0.0+(ba36) Tue, 25 Aug 2015

Chainboot failed!
iPXE 1.0.0+(55e4)
↧
↧

shim.efi.signed and iPXE

April 27, 2016, 2:46 pm
$
0
0
Hello everyone,

I need to load iPXE on computers that have secureboot enabled. Obviously this is an issue because iPXE does not have a purchased cert so it therefor won't authenticate.

What I am trying to do is use shim.efi.signed to boot into iPXE. Shim does have the proper cert and allows me to boot grubx64.efi which can read a standard grub.cfg I can modify.

Right now, I can boot my computer to a grub menu but when I select my programmed menu option I just receive a black screen.

Code:
if loadfont /grub/font.pf2 ; then
    set gfxmode=auto
    insmod efi_gop
    insmod efi_uga
    insmod gfxterm
    terminal_output gfxterm
fi

set menu_color_normal=white/black
set menu_color_highlight=black/light-gray

menuentry "Load iPXE" {
    set gfxpayload=keep
    linux /boot/IPXE.KRN
}


I found similar configs but they all use pxelinux.0 so functions like, KERNEL and APPEND don't apply. My setup is sort of special I guess.

Thanks for reading.
↧

problem with boot.ipxe

April 28, 2016, 4:00 pm
$
0
0
Hi,
I try to use the iPXE, with the ISO.
I prepared my IIS folder with all the necessary.
When I try to boot with the file boot.ipxe, the process will hang...
Trying to rename with .php extension...

Script :

#!ipxe

kernel http://gss/win7/wimboot
initrd http://gss/win7/boot/bcd BCD
initrd http://gss/win7/boot/boot.sdi boot.sdi
initrd http://gss/win7/sources/boot.wim boot.wim
boot

But if I type each line in the prompt, the wim boots properly...

If you can help me.

Thanks a lot.
See Attachment below

Greg

Ipxe
↧

Newb: PXE booting W2K12R2

April 29, 2016, 7:31 am
$
0
0
Good morning,

I have an (old) HP Z400 workstation which recently suffered a HDD failure. It was a bit of a bit deal, so I'd like to offload this to our iSCSI SAN. Unfortunately, the integrated NIC doesn't support this.

Is there any links, or anything more simplified?

I walked through the chainloading and got confused.

Thanks!
↧
Search

initrd vs kernel initrd=

May 3, 2016, 5:28 am
$
0
0
Hi

Some time I can load kernel the initrd like that
kernel /some/kernel
initrd /some/initrd.img

Other time doesn't works. I have to pass initrd as kernel parameter like
kernel /some/kernel initrd=/some/initrd.img

What is the difference between initrd command and passing initrd parameter to kernel command?

thanks.
↧
↧

--timeout feature for read command?

May 4, 2016, 6:00 am
$
0
0
Hi,

I was wondering if it's possible to add --timeout to the read command - similar to how the prompt command works?

I have an ipxe script that starts with read. It will goto the corresponding section when the user types the proper text, else it goes back to start. I would like it to timeout to a certain section after a period of time with no input.

Thanks
↧

win 2012R2 & 2008R2 not see disk

May 5, 2016, 3:36 am
$
0
0
2012R2 & 2008R2 install not see iscsi disk.
↧

nslookup: command not found

May 5, 2016, 8:43 am
$
0
0
Hi,

When trying to PXE boot a (Windows 7) guest on an oVirt host, I get:

'nslookup: command not found
Could not boot image: Exec format error (http://ipxe.org/2e022001)'

The Windows entry works fine when using a Xen or VMWare hypervisor, so I suspect it is something wrong with how oVirt does it, but I'm not quite sure what could cause this. I can PXE boot Linux VMs via the same method on the oVirt host without issue, however, they do not require the nslookup or chain functions in iPXE.

In my 'default' file on my kickstart host, the entry that is failing for Windows is:

nslookup wds <?php echo $wdroot."\n"; ?>
set net0/next-server ${wds}
chain tftp://${wds}/boot\\x86\\wdsnbp.com || goto failed
goto start


An example Linux host that boots fine from the same menu:

:sl6.7-lvm
set kernel ${boot-root}/sysimages/sl6/6.7/vmlinuz
set initrd ${boot-root}/sysimages/sl6/6.7/initrd.img
set ksname /boot/kickstarts/sl6.7-lvm.ks
set imgargs ${sl6-imgargs}
goto execboot

Thanks for any pointers.

-Cam
↧

set net0.dhcp/hostname not working as expected

May 8, 2016, 7:53 am
$
0
0
Perhaps my expectations are off but, if I have the following script:

iPXE> dhcp
iPXE> show net0.dhcp/hostname
iPXE> net0.dhcp/hostname:string = host-192-168-100-3
iPXE> set net0/next-server 192.168.100.39
iPXE> set net0.dhcp/hostname abc.123
iPXE> show net0.dhcp/hostname:string = abc.123
iPXE> chain tftp://192.168.100.39/pxelinux.0

This works, however my Linux kickstart installation still sees host-192-168-100-3

Any ideas on what I'm doing wrong?
↧
↧

Display Goes Blank

May 8, 2016, 11:07 pm
$
0
0
Hi team,
We are using Pxelinux, wimboot and TFTPd32 to network boot our Litouch (winPE), and the issue is with HP prodesk 600G1 desktop with nvidia G card, where display goes blank.however with internal G card, display works well and I can see the winPE screen.

Checked wDS, and display works well with external G card as well. Please find attached screen shot after which I don't see any display. NOR the display I think excution also stop, because I enabled monitoring on my MDT console but nothing comes up as excution on the system. Update the system with latest BIOS and ME firmware but still issue is there.
↧

Input/Output Error loading wim file

May 9, 2016, 6:26 am
$
0
0
Hello, I'm getting "Input/Output error" when trying to load a customized wim file.

Steps to create wim file:
Code:
Installed Windows 2012 R2 onto physical server
Installed drivers and an application
booted server to winpe and captured partition with DSIM

The .wim file is just under 6Gb in size.

Here is the code in the .ipxe menu:
Code:
:VSS
imgfree
kernel ${boot-url}/iPXE/tools/winpe_64_VSS/wimboot gui
initrd ${boot-url}/iPXE/tools/winpe_64_VSS/media/Boot/BCD BCD
initrd ${boot-url}/iPXE/tools/winpe_64_VSS/media/Boot/Fonts/segmono_boot.ttf segmono_boot.ttf
initrd ${boot-url}/iPXE/tools/winpe_64_VSS/media/Boot/Fonts/segoe_slboot.ttf segoe_slboot.ttf
initrd ${boot-url}/iPXE/tools/winpe_64_VSS/media/Boot/Fonts/wgl4_boot.ttf    wgl4_boot.ttf
initrd ${boot-url}/iPXE/tools/winpe_64_VSS/media/Boot/boot.sdi boot.sdi
initrd ${boot-url}/iPXE/tools/winpe_64_VSS/media/sources/boot.wim boot.wim
boot || goto failed

I have tried booting to this with several different servers. They all have over 100Gb of RAM and a mix of Qlogic, Intel, and BCOM NIC cards.

[Image: inputoutputerror.jpg]

Has anyone tried this or have any suggestions?
Thanks...Corey
↧
Search

How to set the DHCPv6 in win2012r2 to boot ipxe.efi

May 13, 2016, 1:36 am
$
0
0
As title, I would like to use the IPv6 iPXE.

Environment----
1. 2012R2 , WDS, DHCPv4 + V6
2. Boot to ipxe.efi with DHCPv4 UEFI is successful.(set DHCP option 67 = boot\x64\ipxe.efi)

My question is ----
How can I use the DHCP IPv6 service under 2012r2 to "set the boot file" as same as IPv4?
↧

iPXE Lenovo Thincentre stick 300

May 20, 2016, 7:53 am
$
0
0
http://www.windowscentral.com/lenovo-ide...300-review

I build ipxe.efi (and rename to BootIA32.efi)

make bin-i386-efi/ipxe.efi EMBED=~/my_script_sccm.ipxe

as per http://doc.rogerwhittaker.org.uk/ipxe-in...n-and-EFI/

using

https://git.ipxe.org/ipxe.git/snapshot/2...703.tar.gz

It all works, till I actually try to boot, and get error EFI USB device Boot Failed

It does not even start booting...

I am trying to use it with (via hub)

ASIX AX88178 USB to Ethernet - like http://forum.ipxe.org/showthread.php?tid=6151&page=3

VID_0B95&PID_1790

Any ideas what could be?

sebus

edit:
I even re-created the image with https://rom-o-matic.eu/ (using same 276d, as master did fail with error:

"make" unexpectedly returned exit value 2 at /var/www/ipxe-buildweb/build.fcgi line 630 )

Same problem with booting
↧
↧

How to get the login information to authenticate in IIS basic windows authentication.

May 22, 2016, 2:36 pm
$
0
0
Hello,

I am new to iPXE, and I having some issues in getting the login information to to authenticate against windows basic authentication in IIS 8. I followed this example "chain http://${username:uristring}:${p.../boot.ipxe", but I am still getting a 401.1 error message " Denied by Invalid User Credentials".

Do I need to create my own server side process to handle the authentication?

I will appreciate any help in this matter.

Thanks
↧

Need some help NFS booting a mounted Ubuntu 16.04 mini.iso (both UEFI and BIOS)

May 23, 2016, 1:43 pm
$
0
0
Hey there,

I'm completely new to network booting/iPXE, etc., and I'm having some problems getting a network boot setup working. I'm hoping somebody here can help.

Here's a quick overview of my setup:

1. I have configured a DHCP server to instruct chainloading of either ipxe.efi or undionly.kpxe depending on whether or not the boot client is UEFI or BIOS

2. The DHCP server sends the client to a TFTP server running on a QNAP TurboNAS to serve up the correct file

3. The same QNAP TurboNAS has the mini.iso for Ubuntu 16.04 mounted with read-only guest permissions and available via NFS

4. I have built iPXE w/ DOWNLOAD_PROTO_NFS enabled

Up to here is where things seem to fall apart; I Ctrl+B in to the command line to start playing with stuff but I can't seem to get the kernel to load.

I know that NFS is working, because I can get to files such as the initrd without issue:

Code:
dhcp
initrd nfs://guest@<server ip>/Ubuntu1604Mini/initrd.gz

Works just fine. But when I try to get the kernel to load, I get Exec format error. From cursory Googling I'm going to assume that the kernel image doesn't have the EFI stub compiled properly but I'm not totally sure. I have tried several different commands:

Code:
kernel nfs://guest@<server ip>/Ubuntu1604Mini/linux #doesn't work
kernel nfs://guest@<server ip>/Ubuntu1604Mini/linux initrd=initrd.gz #doesn't work
kernel nfs://guest@<server ip>/Ubuntu1604Mini/linux root=/dev/nfs nfsroot=guest@<server ip>:/Ubuntu1604Mini initrd=initrd.gz #doesn't work
kernel nfs://guest@<server ip>/Ubuntu1604Mini/linux root=/dev/nfs netboot=nfs nfsroot=guest@<server ip>:/Ubuntu1604Mini initrd=initrd.gz #doesn't work

Is this an EFI issue, or am I just missing something monumentally obvious? Any help on this would be incredibly appreciated.
↧

Error building ISO

May 25, 2016, 10:43 am
$
0
0
I was trying to build an ISO image using
Code:
make bin/ipxe.iso

But I got an error as follows:
Code:
[BUILD] bin/hvm.ids.o
  [BUILD] bin/undi.ids.o
  [AR] bin/blib.a
ar: creating bin/blib.a
  [HOSTCC] util/zbin
  [VERSION] bin/version.ipxe.lkrn.o
  [LD] bin/ipxe.lkrn.tmp
  [BIN] bin/ipxe.lkrn.bin
  [ZINFO] bin/ipxe.lkrn.zinfo
  [ZBIN] bin/ipxe.lkrn.zbin
  [FINISH] bin/ipxe.lkrn
  [GENISO] bin/ipxe.iso
cp: missing destination file operand after ‘bin/iso.dir.CtH7Ki’
Try 'cp --help' for more information.
genisoimage: Uh oh, I cant find the boot image 'isolinux.bin' !
rm bin/ipxe.lkrn.zinfo bin/ipxe.lkrn.zbin bin/version.ipxe.lkrn.o bin/ipxe.lkrn.bin

Any idea what I'm doing wrong?
↧
Viewing all 1484 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>