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

Trim whitespaces from a string?

March 4, 2016, 4:42 pm
$
0
0
For some reason, Acer did store the manufacturer and product in my Acer Aspire One as:

Code:
"Acer      "
"Aspire one      "

And when outputting this to the screen, the added spaces look weird:

Code:
"Acer      Aspire one      boot menu"

I found several settings types which convert the data, e.g. uristring, hex, etc. ... but I didn't find a way to just trim the excessive spaces.

I found this discussion on the mailing list, but the mentioned trick doesn't work anymore and there's no other solution to the problem in that thread. There was also a proposal for a new "trim" command, but that's where the thread ended.

Is there a way to trim whitespaces?
↧
Search

Problem installing Windows to a iSCSI drive via iPXE

February 25, 2016, 11:27 pm
$
0
0
I setup a DHCP/TFTP and iscsi target server box (win2012r2) to boot client, pxe boot chained to undionly.kpxe.
When client booted up, I saw ipxe showed "Preserving SAN device 0x80"
Since the iscsi drive had no OS installed, it turned to boot from the 2nd boot device - an installation DVD for windows 2008 r2 standard server.
After entering the setup interface to select destination disk, the iscsi drive was in "offline" status, putting the iscsi drive online and I cannot go the next step, receiving error message:
"Windows cannot be installed to this disk. This computer’s hardware may not support booting to this disk. Ensure that the disk’s controller is enabled in the computer’s BIOS menu."
Whatever I treated the iscsi drive, creating partition, formatting, converting to mbr..., all not work.
And I noticed one thing that during the installation prebooting, the iscsi target was found to turn to "disconected" before entering "select language" stage. So I doubt that something caused the installation program disconnected from iscsi drive that make the setup failed.

Any help will be greatly grateful!
↧
↧

VMware VM stops working

February 29, 2016, 12:07 pm
$
0
0
I created a iPXE iso using the rom-o-matic site to allow me to manually configure the network interface so that the server can contact the cobbler server where tftp is running. It works on my local network but when I do it from the VM it shows the VMWare logo in the middle of the screen and then nothing happens.

When I look at the web server's log files I can it the requests:
[29/Feb/2016:14:16:51 -0500] "GET /tftp/pxelinux.0 HTTP/1.1" 200 17056 "-" "iPXE/1.0.0+"
[29/Feb/2016:14:16:51 -0500] "GET /tftp/pxelinux.cfg/default HTTP/1.1" 200 2441 "-" "iPXE/1.0.0+"
[29/Feb/2016:14:16:51 -0500] "GET /tftp/menu HTTP/1.1" 404 497 "-" "iPXE/1.0.0+"
[29/Feb/2016:14:16:51 -0500] "GET /tftp/menu.cbt HTTP/1.1" 404 501 "-" "iPXE/1.0.0+"
[29/Feb/2016:14:16:51 -0500] "GET /tftp/menu.0 HTTP/1.1" 404 499 "-" "iPXE/1.0.0+"
[29/Feb/2016:14:16:51 -0500] "GET /tftp/menu.com HTTP/1.1" 404 501 "-" "iPXE/1.0.0+"
[29/Feb/2016:14:16:51 -0500] "GET /tftp/menu.c32 HTTP/1.1" 200 55273 "-" "iPXE/1.0.0+"
[29/Feb/2016:14:18:18 -0500] "GET /tftp/pxelinux.0 HTTP/1.1" 200 17056 "-" "iPXE/1.0.0+"
[29/Feb/2016:14:18:19 -0500] "GET /tftp/pxelinux.cfg/default HTTP/1.1" 200 2441 "-" "iPXE/1.0.0+"
[29/Feb/2016:14:18:19 -0500] "GET /tftp/menu HTTP/1.1" 404 497 "-" "iPXE/1.0.0+"
[29/Feb/2016:14:18:19 -0500] "GET /tftp/menu.cbt HTTP/1.1" 404 501 "-" "iPXE/1.0.0+"
[29/Feb/2016:14:18:19 -0500] "GET /tftp/menu.0 HTTP/1.1" 404 499 "-" "iPXE/1.0.0+"
[29/Feb/2016:14:18:19 -0500] "GET /tftp/menu.com HTTP/1.1" 404 501 "-" "iPXE/1.0.0+"
[29/Feb/2016:14:18:19 -0500] "GET /tftp/menu.c32 HTTP/1.1" 200 55273 "-" "iPXE/1.0.0+"

It gets the pxelinux.0 file and then the default but something probably happens around after it receives the menu.c32 file. I have also noticed that if I don't provide the 209:string and there is matching MAC address it works. The 209:string value actually causes Virtualbox to die also.

could someone shed some light on this for me?

#!ipxe

:start
set version 0.22
echo <STUFF STUFF> loader v${version}
# goto dhcp || shell

menu --name repo Boot Options to reach Repo
item --menu repo --gap STUFF STUFF STUFF PXE Service
item --menu repo --gap
item --menu repo Static Static Configuration
item --menu repo Dhcp DHCP Configuration
item --menu repo start Return
choose --menu repo --default static --keep target
goto ${target}

:Static
echo Please enter the server's networking information:
imgfree
ifclose net0
echo -n IP : && read net0/ip
echo -n Subnet mask : && read net0/netmask
echo -n Gateway : && read net0/gateway
echo -n DNS : && read dns
ifopen net0
echo Attempting chainload of pxelinux.0 from Repo ...
goto pxelinux || goto start
↧

Convert USB Boot to iPXE

March 1, 2016, 9:03 am
$
0
0
Hello iPXE,

Since we're using 7 methods to boot to different scenario's, i am asked to investigate iPXE as an option.

I see that iPXE is able to boot machines from the network using either Legacy or (U)EFI which is perfect; because we are going to have to support all the variants, so the i386 & x64 UEFI and Legacy systems.

As of now, i'm using WDS to distribute iPXE that distributes pxelinux that displays a menu that either is able to boot to an ISO or WDS.

What I'm trying to do is to remove WDS from my enviroment and use iPXE to boot the ISO's and WIM's, so that I can have a single menu and other options attached to that.

However, I've already figured out that booting to ISO is impossible on UEFI. So then I have the following question:

The company that provides us with the ISO, also provides us with the ability to create a bootable USB-stick; on this stick there are multiple efi files (all the needed files).

I'm wondering if it is possible to use the files on the USB Stick to make iPXE able to boot to the ISO via HTTP.

Sadly our company does not have SAN-disks, so that is not a valid option.

I'd love to hear,

Alex
↧

SANBoot ISO Image - Not Available For Install

March 2, 2016, 3:25 pm
$
0
0
So, this is something I've seen a few threads about, but never found a satisfactory solution to.

Suppose I SANBoot, let's say, debian-8.3.0-amd64-netboot.iso. It starts well enough, but after the GRUB prompt the installer complains that there's no "Common CD-ROM Drive," i.e., it can't see the ISO any longer. This happens in its own way when SANBoot'ing a Windows 7 iso too.

Is there any way to somehow load the entire iso into RAM, or otherwise make the machine aware of its contents?

I have successfully gotten Debian going by untar'ing its netinstall tarball on the remote host and using iPXE's kernel and initrd directives to point to the linux and initrd.gz, but an ISO would be much more convenient.
↧
↧

Few questions about sanhook'ing and BIOS

March 5, 2016, 7:20 pm
$
0
0
I'll start by thanking you all for iPXE. I've only recently discovered it, and it seems pretty awesome. So thanks for that.

Apologies if I've missed something obvious, this is all new territory for me. Basically, I'm learning about with iSCSI by tinkering with it, and my weapons of choice are the latest iPXE ISO, a simple iSCSI server from here, and Microsoft's iSCSI bootable initiator in XP setup, booted from an ISO on a USB stick using Firadisk.

As you might expect with such a convoluted setup, I have a weird problem. Smile (I'm not looking for help for the XP bit here - I'm just telling you for context.)

Basically, the install seems to work, it formats, but tries to add the MBR to my USB stick rather than the iSCSI target, and when looking at the resulting VHD I end up with a full directory tree, but not a single file. All a bit weird. So, troubleshooting 101, I took a step back.

I wanted to see if the device was working in anything else. So I tried a partedmagic boot ISO, and was able to mount the iSCSI target fine, and dump files on it, etc. no problems. So, step back.

I boot XP setup from GRUB4DOS, which has a command line. So I fired that up, and had a look at what GRUB could see via the BIOS. At this point, I get an error from GRUB4DOS that it's "tuning" the geometry of the iSCSI sanhook'ed disk, and then showing it as a CHS drive, not LBA. I suspect this may be incorrect hooks into int13 by iPXE? (btw, the target is a 10GB VHD on my other machine.)

I'm going to try using a smaller VHD (< 8GB to avoid the CHS limit) to see if that helps, but thought I may as well ask here if this is a known limitation or if I'm doing something obviously silly here to someone who is a bit more experienced.
↧

iPXE, iSCSI and int13

March 6, 2016, 3:55 pm
$
0
0
Just wondering...this is all very new to me, but do iPXE's int13 hooks mean that you would expect the sanhook'ed iSCSI target to show up as a browsable (hdx) device in GRUB4DOS (command line, (hd<tab to auto complete>), or indeed, any code that utilises int13?

...also, I tried starting a thread yesterday, but it still hasn't appeared? I ended up mostly answering my own questions, but as the thread is invisible, I can't edit or delete it...
↧

Does iPXE support USB Nics

March 9, 2016, 4:56 pm
$
0
0
I have approx. 30 Dell tablets with an AX88772 - USB2.0 to 10/100M nic built into the dock. Does iPXE support usb nic booting?
↧
Search

iPXE EFI booting ISOs

March 9, 2016, 5:05 pm
$
0
0
Any way I can boot ISOs in an EFI firmware. I wanted to boot dban and/or memtest.
↧
↧

ipxe uefi x64 WimBoot

March 11, 2016, 7:00 am
$
0
0
Hi iPxe,

I'm trying to boot to an x64 Windows 10 WIM image from ipxe.
The script i'm using is as follows:


Code:
:wimboot
set base-url http://10.168.51.5/bootimg/win
kernel ${base-url}/wimboot
initrd ${base-url}/\${arch}/default.bcd BCD
initrd ${base-url}/boot.sdi boot.sdi
initrd -n boot.wim \${base-url}/winpe.wim boot.wim

The iPXE menu happily starts loading all the files .. everything OK untill there

The output I receive later is:

Code:
Command line: "wimboot"
Using wimboot via 0xd13ba588 len 0x8440
Using default.bcd via 0xd13ba628 len 0x2000
using boot.sdi via 0xd13ba6c8 len 0x306000
using boot.wim via 0xd13ba768 len 0x115a90b3
...found WIM file boot.wim
...found file "Windows\boot\EFI\bootmgfw.efi"
Using BOOTX64.EFI via 0xd1274a00 len 0xee360
..extracted \Windows\Boot\EFI\bootmgwf.efi
Read BOOTX64.EFI
Could not load BOOTX64.EFI: 0x800000000003
Could not boot: Error 0x7f048281 (http://ipxe.org/7f048281)
*note: i tried my best to copy all numbers as-is..

The files I'm using come from an official Windows 10 DVD
and i'm a little illusive to why this does not work.
↧

iPXE support on PowerPC

March 10, 2016, 10:46 pm
$
0
0
Hi Folks,

Do we have PXE support for PowerPC platforms/products ? If yes,
could you please share the details ?

In iPXE source, I could find only x86/x86_64/i686 (Only Intel) architecture supported.

Thanks,
chandra
↧

help with ISC Kea dhcp and iPXE

March 13, 2016, 10:09 pm
$
0
0
Does anyone have a working Kea dhcp server for chain-loading iPXE?
↧

wimboot Can't handle unknown compression scheme

March 14, 2016, 5:59 am
$
0
0
Normally wimboot works on any .wim image.

But I have WinPE_SE 10 created wim, which does not want to boot via wimboot

[Image: 15mik3p.jpg]


Just had to redo the compression with DISM.EXE /Export-Image /Compress:max & it does work (at least the part which finds bootmgr.exe)
↧
↧

Failed to boot winpe by ipxe: Enter bootmgr.exe with parameters at 0x2a390

March 14, 2016, 6:56 am
$
0
0
I am sure that is the fault of the .wim file itself, because the same hardware boot perfectly fine from other .wim(s)

Just wonder what could be the cause of it.

This particular wim is created by WinPE SE 10

[Image: nvtkd4.jpg]

sebus
↧

Disable options in menu based on CPU

March 16, 2016, 10:30 am
$
0
0
Hello,

I'm trying to write a dynamic boot menu using php.
However, since i'll have to support different CPU types and architectures, i'd like to remove certain menu options (or do not display) based on the CPU type.

I know that I can use CPUID --ext29 to check if the machine supports x64; and I already supply the machines with different ipxe versions (undionly.kpxe, ipxe_x86.efi and ipxe_x64.efi)

However, somehow I need to provide the architecture while calling the PHP script; or I need an if statement in ipxe to not display the item.

I've tried putting the following options in my DHCP:

Code:
if exists user-class and option user-class = "iPXE" {
    ## filename "http://10.168.51.5/bmenu.php?host=${serial}";
       if option arch = 00:06 {
                 filename "http://10.168.51.5/bmenu.php?host=${serial}&arch=Uefix86";
         } elsif option arch = 00:07 {
                  filename "http://10.168.51.5/bmenu.php?host=${serial}&arch=Uefix64";
         } elsif option arch = 00:00 {
                 filename "http://10.168.51.5/bmenu.php?host=${serial}&arch=Legx86";
        }  else {
                 filename "http://10.168.51.5/bmenu.php?host=${serial}&arch=unknown";
        }

} else {
        if option arch = 00:06 {
                filename "ipxe_x86.efi";
         } elsif option arch = 00:07 {
                 filename "ipxe_x64.efi";
         } elsif option arch = 00:00 {
                 filename "undionly.kpxe";
        }
  }
}

however, the x64 machines do receive the ipxe_x64.efi file (so the first time it requests the arch it is indeed 00:07; however, when booted to my boot menu, it display 'arch=unknown', so the 'arch=Uefix64' is not relevant

A machine booted to undionly.kpxe does display 'Legx86'.

Also, if there is a better way to pass the arch variable into the php url, please let me know. I'm using an if statement because that works in the first load-out of ipxe Smile
↧
Search

Wireless MAC

March 16, 2016, 10:32 am
$
0
0
Ola,

What do I need to do to retrieve the wireless MAC address if present in the device?
I'm using Undionly.kpxe and ipxe.efi to boot to ipxe, but only the LAN-cards are recognized.
↧

Broadcom BCM5709 cards not working

March 17, 2016, 11:34 am
$
0
0
I'm having issues with some HP DL360 g7 servers with BCM5709 NICs in them.

I pulled the latest ROM from the iPXE rom-o-matic and when running on new hardware, it works great. But on the Broadcom NICs the iso doesn't see NICs at all. I found a few links in the forums but no real resolution:

http://forum.ipxe.org/showthread.php?tid=23 (Plans to support card Broadcom Net Extreme II - BCM5709 (14e4:1639)) but that one has no resolution.

There is someone who seems to have done work with this: http://ipxe.org/gsoc/bnx2 . Following their git repo I find this https://git.ipxe.org/people/dewyatt/ipxe...heads/bnx2 However, when building an iso from that tree the system hangs when I run ifopen on the NIC. By hang I mean that I run ifopen and then a few seconds later the shell seems to lock being unable to type anything in and nothing prints out.

So... Has anyone gotten these NIC's to work with iPXE? Should I use a different driver (if so how?)?

Thanks!
↧
↧

Issues with Autoboot

March 18, 2016, 12:01 pm
$
0
0
I am trying autoboot command and getting following failure.

autoboot is working fine 3-4 time (Each time I pressed Ctrl +c during copy operation , started "autoboot net1" to restart the operation) and after that, its giving following error.

How Can I debug this issue.

iPXE> autoboot net1
net1: 00:22:12Big Grinf:ff:37 using dh8900cc on PCI0f:00.2 (open)
[Link:up, TX:880268 TXE:26 RX:885485 RXE:338]
[TXE: 15 x "Operation canceled (http://ipxe.org/0b086095)"]
[TXE: 11 x "Error 0x2a654089 (http://ipxe.org/2a654089)"]
[RXE: 182 x "The socket is not connected (http://ipxe.org/380f6093)"]
[RXE: 122 x "Operation not supported (http://ipxe.org/3c086083)"]
[RXE: 1 x "The socket is not connected (http://ipxe.org/380a6093)"]
[RXE: 18 x "Error 0x440e6083 (http://ipxe.org/440e6083)"]
Configuring (net1 00:22:12Big Grinf:ff:37).................. ok
net0: fe80::222:12ff:fedf:ff36/64 (inaccessible)
net0: 2001:db8:185::/48 gw fe80::213:5fff:fe21:d74a (no address) (inaccessible)
net1: 192.168.1.123/255.255.255.0 gw 192.168.1.1
net1: fe80::222:12ff:fedf:ff37/64
net2: fe80::222:12ff:fedf:ff38/64 (inaccessible)
net3: fe80::222:12ff:fedf:ff39/64 (inaccessible)
Next server: 192.168.1.1
Filename: http://192.168.1.1/test_machine/test_image.iso
http://192.168.1.1/test_machine/test_ima............. Connection timed out (http://ipxe.org/4c0a6092)
↧

UEFI and iSCSI boot

March 29, 2016, 9:05 pm
$
0
0
Hi iPXE team, firstly I want to thank you for all your contribution to the community.

I got the latest code and made a UEFI image ipxe.efi, and I chain boot into this image and in the shell I was trying to sanhook a iSCSI disk, but I got a error says: "Could not open SAN device: Error 0x3f201483". The iSCSI target was tested OK.

In the page http://ipxe.org/efi/vision, it says "...An iPXE UEFI driver now provides a user experience which is almost as full-featured as the user experience provided by an iPXE BIOS driver." but look into the code and found "san_hook" is only implemented in "pc_bios". So my question is, if I want to sanboot a iSCSI disk in UEFI, is this feature already included in current iPXE? or what should I do to possibly make it happen?
↧

How to remove LACP support from iPXE?

March 22, 2016, 7:50 am
$
0
0
The LACP responder in src/net/eth_slow.c is causing a problem for me. I'd like to disable it.

I've found that commenting out 'REQUIRE_OBJECT ( eth_slow );' in src/net/ethernet.c seems to do the trick.

Is that the right way to do it? Are there other methods which might be more appropriate and/or flexible (perhaps a DHCP option or similar)?
↧
Viewing all 1484 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>