Quantcast
Viewing all 1484 articles
Browse latest View live
↧

System Information

August 13, 2014, 5:15 am
$
0
0
I want to know if I exists in iPXE anything that I see system information of my pc in ipxe script (like ${netX/mac}) with informations about memory and cpu.
Asking a little more if I can retrieve informations about HD (capacity and serial) and some pci cards like wmi in windows environment.
↧
Search

HP Service Pack for Proliant (Firmware)

August 21, 2014, 10:19 am
$
0
0
I've been trying to get HP Service Pack for Proliant (SPP)[/quote][/code][/php] running and have been having an issue. I have it booting up and the issue is possible trying to mount the drive from within the boot image.

The SPP is PXE bootable. There is a PXE section that I tried to setup to use with iPXE. http://ftp.hp.com/pub/softlib2/software1...eNotes.pdf

I created a boot.ipxe that is in the same folder as the extracted /system dir from the SPP ISO.

From the main menu, I'm just doing a chain to this boot.ipxe.

Boot.ipxe
Code:
#!ipxe
kernel http://${server}/hp_spp_2014_06/system/vmlinuz raid=nodetect
initrd http://${server}/hp_spp_2014_06/system/initrd.img

imgargs vmlinuz raid=nodetect media=net rw root=/dev/ram0 ramdisk_size= init=/bin/init loglevel=3 ide=nodma showopts ide=noraid nopat pnpbios=off vga=791 splash=verbose hp_fibre showopts noexec32=off numa=off nox2apic TYPE=MANUAL AUTOPOWEROFFONSUCCESS=no AUTOREBOOTONSUCCESS=yes iso1=smbfs://${server}/shared/hp_spp_2014_06/HP_Service_Pack_for_Proliant_2014.06.0_784915_001_spp_2014.06.0-SPP2014060.2014_0618.4.iso iso1mnt=/mnt/bootdevice

boot

Now it does boot into the HP image but it dies right after getting a DHCP address then trying to mount the filesystem.
Quote:Warning!!! Unable to mount the file system. Dropping to a shell

I'm not too sure but I'm guess it might be the iso1=smbfs:// line. The ISO is on that share and have verified outside of this that it is accessible.

Any have any experience with attempting to iPXE this HP SPP ISO?
↧
↧

PHP causing wimboot to fail with: Bad CPIO magic, FATAL: could not extract inited fil

August 24, 2014, 5:46 am
$
0
0
Hi everyone,

I'm having some more PHP woes with IPXE.

It seems if i get iPXE to boot a php file and then tell that php file to load some software with wimboot, i get the following error:

Quote:Bad CPIO magic, FATAL: could not extract inited file

I've tried multiple wim files and they work fine when in iPXE menu, but once php code boots it doesn't want to chain load wimboot properly.

My php code is:

Code:
    print "kernel wimboot"."\n";
    print "initrd http://192.168.0.1/iso/paragon/BOOTMGR"."\n";
    print "initrd http://192.168.0.1/iso/paragon/ibm/BOOT/BOOT.SDI"."\n";
    print "initrd http://192.168.0.1/iso/paragon/BOOT/BCD"."\n";
    print "initrd http://192.168.0.1/iso/paragon/BOOT/MEMTEST.EXE"."\n";
    print "initrd http://192.168.0.1/iso/paragon/BOOT/FONTS/CHS_BOOT.TTF"."\n";
    print "initrd http://192.168.0.1/iso/paragon/BOOT/FONTS/CHT_BOOT.TTF"."\n";
    print "initrd http://192.168.0.1/iso/paragon/BOOT/FONTS/JPN_BOOT.TTF"."\n";
    print "initrd http://192.168.0.1/iso/paragon/BOOT/FONTS/KOR_BOOT.TTF"."\n";
    print "initrd http://192.168.0.1/iso/paragon/BOOT/FONTS/WGL4_BOOT.TTF"."\n";
    print "initrd http://192.168.0.1/iso/paragon/SOURCES/BOOT.WIM"."\n";
    print "boot"."\n";

I've tried using:

Code:
--autofree

for kernel and inited lines, but it doesn't work either :/
I've tried using wimboot 1.0.4 and 1.0.6, both produce the same error.
Hahhaha for some reason before i post a message on here i can't find the answer.
And as soon as I do i find it ...

http://forum.ipxe.org/showthread.php?tid=6844
↧

chain with "$macros" does not work anymore

August 28, 2014, 6:19 am
$
0
0
Hello,

I'm currently using gpxe 0.9.7+ and tried today the git repository.

After enabling COMBOOT again I found out that the following script
does not work anymore:

Code:
#!gpxe
login
chain http://${username:uristring}:${password:uristring}@server.com/menu.c32 menu.php

This works in gpxe 0.9.7+, but not in git from 22.08.

Code:
tcpdump -A -s 1024

shows that no authorisation is transmitted to "server.com".
I suppose there is an "uri_parse" missing somewhere for the imageexec
command.
But I cannot figure out where.

regards,

Martin
↧

Installing Win7 to an iSCSI target

August 28, 2014, 1:02 pm
$
0
0
Hello,

I am trying to install Windows 7 to an iSCSI target but iSCSI disk does not appear as a install location though it is registered successfully. It looks like when windows takes over, connection is lost. I confirmed it by trying Shift-F10 and then "route print".

iPXE> dhcp net0
iPXE> set keep-san 1
iPXE> sanhook iscsi:192.168.0.1:::1:iqn.2014-08.com.axisy.stealth:lvtarget
iPXE> exit
// proceed to boot Windows 7 from CD/DVD

I'm using private subnet. I also tried setting "set netX/gateway 0.0.0.0" before sanhook but it does not help. I am not sure if I'm missing anything. I would appreciate any help.

Thanks,
Che
↧
↧

iPXE & MBP

August 29, 2014, 7:18 am
$
0
0
Hi!

Are there any known issues, that MacBooks (7,1 / 5,5 / 5,4 / 8,1) are not able to work with iPXE? I was able to set up an dhcpd to boot an ipxe64.efi file. Long way ;-) Thats works, but iPXE freezes direct after CTRL+B. Grub 2.02-beta2 works, but is not able to connect to the network.... At least apple crap, but it should work in any way :-(
↧

Use MS DHCP for both UEFI and BIOS

August 31, 2014, 9:49 am
$
0
0
I was wondering if it is possible to use the Windows Server DHCP role to hand out different boot file names for both BIOS and UEFI machines using either vendor or user classes similar to the way it is done for iPXE chainloading?

Is there a guide somewhere? Or is this just not possible and ISC DHCP should be used because of the logic support in dhcpd.conf?
↧

xenserver unattended install with iPXE

September 1, 2014, 3:14 am
$
0
0
Hi,

I'm trying to install xenserver 6.2.0 on my server, and I want to use iPXE. My server doesn't have cd-rom and integrated network controller is busted, but iPXE works with my wireless card. I had no luck with creating reliable USB boot stick, and on top of that it is a headless server with no video output, therefore my options are pretty much limited to iPXE unattended install through wireless connection.

In xenserver documentation there is a guide on how to perform install using PXE, but if I understand correctly it won't directly apply to how to perform iPXE installation. What I'd need to do to make it work? I understand that it might just be possible, but is it feasible for me to do it, if my experience with PXE/iPXE/xenserver is limited? Please point me in the right direction.

Let me know,
xezzy
↧
Search

Installing Win 8.1 64 Bit via iPXE

September 1, 2014, 3:42 am
$
0
0
Hello,

I'm trying for days now to get my pxe boot environment working.

I have a dnsmasq server which pxe boots to a syslinux menu where you can select different images (working fine).

The menu calls the following:
KERNEL IPXE.KRN
APPEND dhcp && set image win81 && chain http://install.local/default.ipxe

To say it first the images / extracted files work fine if used on CD...

In the default.ipxe I tryed different configs:

set boot-url http://install.local/

:win81
sanboot --drive 0x81 --keep --no-describe ${boot-url}os/Win81.iso
--> Error /Boot/BCD is missing

:win81
sanboot --no-describe ${boot-url}os/Win81.iso
--> I/O error

:win81_org1
set dir ${osdir}Win81/
kernel ${boot-url}_boot/wimboot
initrd ${dir}bootmgr bootmgr
initrd ${dir}boot/bcd BCD

initrd ${boot-url}_boot/fonts/chs_boot.ttf fonts/chs_boot.ttf
initrd ${boot-url}_boot/fonts/cht_boot.ttf fonts/cht_boot.ttf
initrd ${boot-url}_boot/fonts/jpn_boot.ttf fonts/jpn_boot.ttf
initrd ${boot-url}_boot/fonts/kor_boot.ttf fonts/kor_boot.ttf
initrd ${boot-url}_boot/fonts/segmono_boot.ttf fonts/segmono_boot.ttf
initrd ${boot-url}_boot/fonts/segoe_slboot.ttf fonts/segoe_slboot.ttf
initrd ${boot-url}_boot/fonts/segoen_slboot.ttf fonts/segoen_slboot.ttf
initrd ${boot-url}_boot/fonts/wgl4_boot.ttf fonts/wgl4_boot.ttf

initrd ${boot-url}_boot/fonts/malgunn_boot.ttf fonts/malgunn_boot.ttf
initrd ${boot-url}_boot/fonts/meiryo_boot.ttf fonts/meiryo_boot.ttf
initrd ${boot-url}_boot/fonts/meiryon_boot.ttf fonts/meiryon_boot.ttf
initrd ${boot-url}_boot/fonts/msjh_boot.ttf fonts/msjh_boot.ttf
initrd ${boot-url}_boot/fonts/msjhn_boot.ttf fonts/msjhn_boot.ttf
initrd ${boot-url}_boot/fonts/msyh_boot.ttf fonts/msyh_boot.ttf
initrd ${boot-url}_boot/fonts/msyhn_boot.ttf fonts/msyhn_boot.ttf
initrd ${dir}boot/boot.sdi boot.sdi
initrd ${dir}sources/boot.wim boot.wim
imgstat
boot

--> This config works for the 32Bit version fine but for 64 Bit the Bootloader starts (Loading Files) and then stops with a black screen.

I have a bit of technical experience but I'm pretty new to the whole pxe booting topic.
I tried to get some kind of debug output but totaly failed as I'm not even sure where the setup failed.
What I already tried is to change the bootmgr and afterwards the whole boot folder from the working 32 Bit install -> no success...

I also managed to get the install.wim instead of the install.esd - I changed the files but no change / same behaviour.

I would be happy if somebody could point me in the right direction.

BTW I know that I can boot a Winpe image and start the install from there but that's not what I would like to have - I would like to directly boot to the setup as if the cd would be in the machine.

Thanks in advance for any help
↧
↧

wimboot 2.1+ from pxelinux

September 2, 2014, 9:19 pm
$
0
0
I have been using wimboot with pxelinux (6.02) for a few months with great success. Never had an issue with v1.0.6 or more recently v2.0.

However, if I update to 2.1 or 2.2.2, I can no longer boot wim files. The bootloader and wim load fine, but then I get a 'Unrecognized argument error' (see screenshot).

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

My menu entry looks like this:

Code:
LABEL winpe
    MENU LABEL WinPE
    COM32 linux.c32
    APPEND wimboot initrdfile=winpe/bootmgr.exe,winpe/bcd,winpe/boot.sdi,winpe/boot.wim

If I downgrade to wimboot v2.0, I can immediately boot to WinPE again.

Did the required arguments or order of them recently change, or I am doing something wrong?

Thanks.
↧

Install really necessary?

September 8, 2014, 12:37 am
$
0
0
Hi There,

As with the newest version of Windows 8.1 there was a feature added to dism (i think) were you can boot windows from a wim file located on your harddrive. I know with winpe it is already possible to boot windows over http but can it work with a persistent installation or windows to go as well?

mounting somehow a http path as harddisk and booting windows from the web? Making sure changes get uploaded via http(s) as well?

Please leave your ideas Image may be NSFW.
Clik here to view. Smile

Regards,
J
↧

Boot image over http using only NETBOOT?

September 7, 2014, 5:52 am
$
0
0
I need to achieve to boot ISO over http:\\ with NETBOOT from the BIOS. Without using any other boot device ie. USB,HD,CD.

So i cannot store the DHCP settings on any boot device.

Can this be done?

I have a standard wireless netgear router with DHCP but i understand not enough to pass to TFTP. I understand there is DD-WRT extended firmware for certain routers to be able to store PXE settings to pass to TFTP over the net but it doesn't support my router.

I was thinking if iPXE is in the Network ROM i can boot DHCP from there.

What are my possible options?

Regards.
Mark
↧

Boot ISO over http with NETBOOT only?

September 7, 2014, 6:16 am
$
0
0
I need to achieve to boot ISO over http:\\ with NETBOOT from the BIOS. Without using any other boot device ie. USB,HD,CD.

So i cannot store the DHCP settings on any boot device.

Can this be done?


I have a standard wireless netgear router with DHCP but i understand not enough to pass to TFTP. I understand there is DD-WRT extended firmware for certain routers to be able to store PXE settings to pass to TFTP over the net but it doesn't support my router.

I was thinking if iPXE is in the Network ROM i can boot DHCP from there.

What are my possible options?

Regards.
Mark
↧
↧

CentOS 6.5 KVM gPXE to iPXE emulation failed (mmio) rip 3d6 f2 af 83 c7

September 8, 2014, 5:38 pm
$
0
0
Long story short, I setup KVM on a CentOS 6.5 hypervisor. Using virt-install to start the VM, it never gets past iPXE and just gets stuck.

I even rebult an undionly.kpxe file to boot into shell, but it still gets stuck. Does anybody have an insight on what I'm doing wrong?

Quote:gPXE 0.9.7 -- Open Source Boot Firmware -- http://etherboot.org
Features: HTTP DNS TFTP AoE iSCSI bzImage COMBOOT ELF Multiboot PXE PXEXT

net0: AB:CD:EF:12:34:56 on PCI00:03.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
Waiting for link-up on net0... ok
DHCP (net0 AB:CD:EF:12:34:56).... ok
net0: 1.1.1.33/255.255.255.0 gw 1.1.1.1
Next server: 1.1.1.23
Filename: undionly.ikpxe
tftp://1.1.1.23/undionly.kpxe.. ok
PXE->EB: !PXE at 9C37:0710, entry point at 9C37:0397
UNDI code segment 9C37:07A6, data segment 9CB2:2CD8 (624-638kB)
UNDI device is PCI 00:03.0, type gPXE
624kB free base memory after PXE unload
iPXE initialising devices...ok



iPXE 1.0.0+ (d97c) -- Open Source Network Boot Fi

On the hypervisor, I see the following:

Quote:kernel: emulation failed (mmio) rip 3d6 f2 af 83 c7

Or...

Quote:KVM internal error. Suberror: 1
rax 0000000000001e20 rbx 000000000000ffff rcx 000000000000fcff rdx 0000000000001e20
rsi 0000000000000063 rdi 000000000009fffe rsp 0000000000002e8c rbp 0000000000002e90
r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11 0000000000000000
r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000
rip 00000000000003d6 rflags 00010403
cs c000 (000c0000/0000ffff p 1 dpl 0 db 0 s 1 type b l 0 g 0 avl 0)
ds 0040 (00000400/0000ffff p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0)
es 9f80 (0009f800/0000ffff p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0)
ss 9915 (00099150/0000ffff p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0)
fs 9915 (00099150/0000ffff p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0)
gs 9915 (00099150/0000ffff p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0)
tr 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
ldt 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0)
gdt 0/0
idt 0/3ff
cr0 10 cr2 0 cr3 0 cr4 0 cr8 0 efer 0
emulation failure, check dmesg for details
↧

Problems loading WinPE using WIMBOOT

September 9, 2014, 4:45 am
$
0
0
I try loading custom [with drv + add pack] WinPE30 (Win7) and WinPE51(Win8.1) using WIMBOOT.
boot.wim (PE30) - 111 mb original
boot.wim (PE30) - 176 mb custom
boot.wim (PE51) - 264 mb custom
Depending on the hardware platforms the obtain different reslts:

Chipset H77, RAM Size-4Gb
Loading original WinPE30 - OK
Loading custom WinPE30 - ERROR bootmgr.exe: STATUS: 0xc000000D An Unexpected error has occurred
Loading custom WinPE51 - OK

Chipset H77, RAM Size-2Gb
Loading original WinPE30 -OK
Loading custom WinPE30 -OK
Loading custom WinPE51 -OK

Chipset H81, RAM Size -4Gb
Loading original WinPE30 -OK
Loading custom WinPE30- ERROR bootmgr.exe STATUS: 0xc000000D An Unexpected error has occurred
Loading custom WinPE51 - hang on the starting Windows logo.

By the above configurations loading WinPE 30\51 is OK using command -chain.
part of my menu:

*************************
#Chain Boot
:PE3_Chain
set DIR BootingOS\WinPe30\x86
chain pxeboot.n12 # Boot loader WinPE30

# Loading from WimBoot
:PE3_Wimboot
set DIR BootingOS\WinPe30\x86
cpuid --ext 29 && set arch amd64 || set arch x86 kernel wimboot
initrd /BootingOS/WinPe30/x86/bootmgr.exe bootmgr.exe
initrd ${DIR}/boot/bcd BCD
initrd ${DIR}/boot/boot.sdi boot.sdi
initrd ${DIR}/sources/boot.wim boot.wim
boot

:PE5
set DIR BootingOS\WinPe51\x86
kernel wimboot
initrd /BootingOS/WinPe51/x86/bootmgr.exe bootmgr.exe
initrd ${DIR}/boot/bcd BCD
initrd ${DIR}/boot/fonts/segmono_boot.ttf segmono_boot.ttf
initrd ${DIR}/boot/fonts/segoe_slboot.ttf segoe_slboot.ttf
initrd ${DIR}/boot/fonts/segoen_slboot.ttf segoen_slboot.ttf
initrd ${DIR}/boot/fonts/wgl4_boot.ttf wgl4_boot.ttf
initrd ${DIR}/boot/boot.sdi boot.sdi
initrd ${DIR}/sources/boot.wim boot.wim
boot

*************************
What is the problem ?

P.S.
iPXE -last build
Wimboot ver: - try 1.04 \1.05 \ 2.00 \ 2.23
↧
Search

wimboot filename length restricted to 7 ?

September 10, 2014, 7:32 pm
$
0
0
hello all

good to know that latest wimboot (2.2.4) support UEFI booting.

but it seems that boot.wim filename max length is restricted to 7 ?

e.g.
if loaded with filename initrd 1234567.wim it's OK
if loaded with filename initrd 12345678.wim then boot failed


P.S. are these all same effect:
initrd boot/bcd bcd
initrd boot/bcd
initrd --name bcd boot/bcd
initrd -n bcd boot/bcd
↧

UEFI + Ubuntu netinstall crashing

September 11, 2014, 9:09 am
$
0
0
Hi there,

It seems there is a problem with loading a kernel/initrd for ubuntu's netinstall while using UEFI on VMWare Workstation 10/Lenovo T440s (current build from GIT). Using a regular BIOS everything works fine with the following iPXE part:

:ubuntu-trusty-amd64
initrd http://de.archive.ubuntu.com/ubuntu/dist.../initrd.gz
chain http://de.archive.ubuntu.com/ubuntu/dist...md64/linux fb=false
boot || goto failed
goto start

iPXE loads the initrd and the kernel and then it crashes at:
VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Someone else hit that problem as well?
↧
↧

UEFI & Ubuntu netinstall crashing

September 12, 2014, 2:45 am
$
0
0
Hi there,

I've tried launching Ubuntu's netinstall (precise/amd64) through iPXE and UEFI.
Sadly it crashes saying it cannot find the root block device.
Disabling UEFI and using BIOS it launches just fine.
The same happens with Fedora's netinstall.

Code:
VFS: cannot open root device "(null)" or unknown-block(0,0): error -6

I used these settings:
Code:
:ubuntu-trusty-amd64
initrd http://de.archive.ubuntu.com/ubuntu/dists/trusty/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/initrd.gz
chain http://de.archive.ubuntu.com/ubuntu/dists/trusty/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/linux fb=false
boot || goto failed
goto start

:install_fedora
initrd http://ftp.uni-kl.de/pub/linux/fedora/linux/releases/20/Fedora/x86_64/os/images/pxeboot/initrd.img
chain http://ftp.uni-kl.de/pub/linux/fedora/linux/releases/20/Fedora/x86_64/os/images/pxeboot/vmlinuz inst.repo=http://ftp.uni-kl.de/pub/linux/fedora/linux/releases/20/Fedora/x86_64/os/
boot || goto failed
goto start
↧

etherboot (gpxe) site is down

September 15, 2014, 10:52 am
$
0
0
Sorry to post this here but I suspect there are people here who might know what is going on with the legacy gpxe/etherboot project.

Does anyone know how to contact the maintainer of the gPXE project, particularly the rom-o-matic.net site? I would like to volunteer to host a mirror site of it. Please contact me directly at jinzishuai@gmail.com

Thanks a lot,
Shi
↧

iPXE boot from a Hyper-V PV NIC?

September 16, 2014, 3:57 pm
$
0
0
Hi there,

Is there any way to iPXE boot from a Hyper-V VM running with their PV NIC?
I can only get the legacy NIC to work with Hyper-V.
Thanks a lot.

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