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

sanboot -d switch

January 2, 2015, 6:04 am
$
0
0
Happy new year, community!

Before I fall into a trap, I'll present the actual problem instead of the question I hope to get answered.

I have a floppy disk image which cannot boot with memdisk in any permutations I have tried. It originally came on a multi-boot disc, and used some rather proprietary methods to boot the OS. It would fail if the disc were removed from system, and would not be able to run. This reads to me that a sanboot is more the way to go. I have:
Code:
sanboot -d 0x00 http://my.server/path/diskimage.ima ||

Which works ... sometimes. I have a total of two computers out of a dozen which successfully boot this. If I remove the -d switch no systems can launch the image successfully.

I'll define a failure of boot however, as it is a bit peculiar. I CAN get into the OS itself, but sometimes it will give me the following error. BTW, this is a program that runs off of a DOS clone.
Code:
Int 13h/Fun 4b01h intercept enabled. (Not emulated)

At this point, the OS looks in A: and B: for its .exe files, but cannot find them, and prompts user for a reboot.

I'm wondering if changing the -d argument gives different results depending on the motherboard. What other arguments can be passed to the -d switch? I'd Google this problem away, but I don't know what to search for. I know this has something to do with which disk it tries to boot, but what is this relative to? Is it geometry in the image, or related to the BIOS? If it's geometry, why do I get radically different results? If it is variations in board manufacturers, what other arguments should I be trying? I want a large range of compatibility for this utility.


Thanks.
↧
Search

Wimboot WinPE

January 8, 2015, 8:00 am
$
0
0
Hi All,

In our network currently we have gPXE on a dhcp serve. We have been looking at moving our tftp server and upgrading to iPXE.

I have been testing this on virtualbox by chainloading from gPXE to iPXE and it has all been going fine.

I finally went to test this on a physical machine and it halts after "Entering bootmgr.exe with parapeters at 0x2a520".

I have now tried 3 physical machines and they all show the same. The linux distros we have are fully working however. I did try booting iPXE off a USB and this worked with both Windows and Linux.

This is the .ipxe script I am using for the PE.

#!ipxe

kernel wimboot gui
initrd boot/BCD BCD
initrd boot/boot.sdi boot.sdi
initrd sources/boot.wim boot.wim
boot

I am hoping that this is just a gPXE issue and if we tell our DHCP servers to use iPXE straight it should work OK. Just wanted to see if anyone had any other suggestions.
↧
↧

Netboot Macbooks und (U)EFI with LINUX

January 10, 2015, 5:43 am
$
0
0
Hello @ll,

I have been reading A LOT in this and other forums and tried to solve this for weeks now but am stuck right now. Here is the problem I'm trying to solve:

I need to boot Laptops via LAN with a Linux System. Its an custom image which allows to connect to an exam environment on our university.
Right now we do only PXE and everything works fine. As more and more Macbooks and WIN8 Laptops appear I need a solution for this EFI Based machines. I don't need to cover Secureboot because this can be easily deactivated. Switching to CSM is not an option because students usually forget to switch back.

So we have Laptops in BIOS mode, (U)EFI mode and Macbooks which should preferyble boot the same image.

Using IPXE on an USB stick I can boot also EFI Laptops and Macbooks but this is also not a preferable option.

I CANT install ANY software on the students laptops so everything MUST work without modification (except boot order).

I know that I address two problems in one question.
1. netbooting Macbooks with a Linux image (Knoppix at the moment)
2. PXE booting UEFI laptops with a Linux image
3. PXE booting BIOS laptops with a Linux Image (this already works)

Does anyone have experiences with Task 1 and 2 here in this forum? I already managed to netboot OSX images from a LINUX Server so this works but I also have an Apple Server available. But I cant figure out how to netboot a Linux Image. So I was thinking I netboot IPXE and then continue to the usual PXE task #3 which already works.
I can also make an individual boot config in the DHCP.conf based on the MAC Addresses if necessary.

So maybe someone can help me out with this mission!

thank you very much!

gerald
↧

kernel boot failure with ipxe on uefi mode

January 14, 2015, 12:11 am
$
0
0
Hello, I've been trying to load linux kernel and initrd directly with ipxe on uefi mode. The kernel and initrd I have tried are from hp scripting toolkit linux 10.02-1. The ipxe command I've tried as follows:

iPXE>kernel http://10.4.16.100/vmlinuz initrd=initrd.img
http://10.4.16.100/vmlinuz...ok
iPXE>initrd http://10.4.16.100/initrd.img
http://10.4.16.100/initrd.img...ok
iPXE>boot

then it output:
VFS: Cannot open root device "(null)" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
kernel pannic - not syncing:VFS: Unable to mount root fs on unknown-block(0,0)

While I used the same kernel and another initrd from fedora, it worked fine.
I also tried to boot the kernel with pxe directly using bootx64.efi and elilo.conf, it worked fine too. And If I chain bootx64.efi in ipxe command line, it would boot into grub2 command line and then I don't know what to do.
Since I need use the tools in the hp scripting toolkits linux, i have to load the kernel and initrd.img from hp scripting toolkits linux directly.

Is there anyone can help me with this problem?
↧

Can't PXE Boot WDS/SCCM from iPXE?

January 14, 2015, 7:50 pm
$
0
0
For this example, I am loading iPXE from an ISO in a VM. No scripts or anything, just trying to PXE Boot. The results have been the same if I chainload on real hardware or boot iPXE from USB.

WDS 2012 is setup in proxyDHCP mode. I can boot to it fine from normal PXE and old versions of gPXE from 2010. This also worked with iPXE in the past, although I have not needed it recently so I do not know when it broke. The WDS server has remained unchanged except for windows updates.

The the current version of iPXE (from this link: http://boot.ipxe.org/ipxe.iso) gives me this:
[Image: R0wlKUP.png]

[Image: Q6Ypj0B.png]

[Image: CgiVwab.png]

The first thing I noticed is that WDS thinks it was launched in DHCP Referral mode. This is NOT the case. The DHCP server on this subnet does not provide a filename or next-server. WDS is on a different server then DHCP and runs in proxyDHCP mode. The config page in iPXE makes it appear that everything is setup correctly. Booting from this server in the same VM without iPXE does not show a DHCP Referral.

Any ideas? Thank you.
↧
↧

Wimboot and windows8.1

January 20, 2015, 2:24 pm
$
0
0
Hi, i followed the guide for wimboot but i cant successfully start windows 8.1 installation on a VM under Vmware workstation, loading process of wimboot and stuffs it's ok, i can see screen installation, after select language installation start right but at the time to choice disk i can't see any disks and installation program claim no device driver were , it seems that wimboot cant serve install.img in rigth way.
For your information compiling ipxe.efi in room-o-matic website i can boot machine in uefi mode, but the problem still persist.

Installation-error
↧

(solved)Made an ISO,but can't use it.

January 20, 2015, 10:51 pm
$
0
0
Dear all:
I built an ISO in CentOS 6.5_x86_64,and IPXE version is "commit d38bac05e7d0eb67fc19f3532a6b4fa00804106e".
steps:
1,git clone git://git.ipxe.org/ipxe.git
2,enable IMAGE_COMBOOT in src/config/general.h
3,created a basic.ipxe
4,execute "make bin/ipxe.iso EMBED=basic.ipxe"
i got the results:
genisoimage: Uh oh, I cant find the boot image 'isolinux.bin' !
rm bin/ipxe.lkrn.zbin bin/version.ipxe.lkrn.o bin/ipxe.lkrn.bin bin/ipxe.lkrn.zinfo

execute:
file bin/ipxe.iso
bin/ipxe.iso: ISO 9660 CD-ROM filesystem data 'iPXE '

ls -al bin/ipxe.iso
-rw-r--r-- 1 root root 34816 1月 21 14:45 bin/ipxe.iso

mount -o loop bin/ipxe.iso /mnt

mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

i can't use this ISO,pls help me,Big Grin
↧

How to build an ISO with undionly?

January 25, 2015, 7:57 pm
$
0
0
Dear all:
i want to build an iso with undionly,because some server use the Broadcom NIC.i couldn't find any information for it.
↧
Search

limitations of snponly.efi

January 29, 2015, 7:55 pm
$
0
0
I have WinPE network booting nicely from IBM UEFI only servers via snponly.efi Smile

Progress at last, I want more....

Is it possible to boot anything else ?
PXE format Linux or iso files would be nice.

I have had little success so far, and posts seem to indicate that only an efi binary file can be booted this way.
I can chain grubx64.efi loader, but it doesn't seem to offer anything better.
↧
↧

Check RAM size

January 30, 2015, 1:59 pm
$
0
0
How to check RAM memory size in ipxe?

I could use it for different configuration in workstations with more or less ram memory.

Thanks
↧

A problem of DHCP in iPXE

January 30, 2015, 8:29 pm
$
0
0
Hello,

I have configure a DHCP server in machine called Server, and I have about eight machines booting by using iPXE called Client1 ...-> Client8. I tried to reboot Server and eight clients at the same time. In total of about 20 times reboot, there are sometimes I see that iPXE in some clients gets the same IP address. For ex,

Assumption that Client1 -> Client8 receives IP1 -> IP8 from DHCP

In successful case, after rebooting all machines, Clien1 to Client8 can receive IP1-IP8 correspondingly and iPXE can get boot correct dump for every client by boot file name option in DHCP server configuration.

In fail case, after rebooting all machine, from the DHCP server log, I see that when Client1 sends DHCPDISCOVER to Server, Server sends DHCPOFFER with IP1 for Client1. Meanwhile Client5 also sends DHCPDISCOVER, server sends DHCPOFFER with IP5 for Client5. In the next step in the dhcp log, I see that Client1 surprisingly sends DHCPREQUEST for IP5 (not IP1), so Server sends DHCPNAK to Client1 as IP5 is reserved for Client5. Client5 also sends DHCPREQUEST to Server and Server returns DHCPACK for successful lease. At this time, tftp starts to download dump and amazingly Client1 and Client5 tries to download dump of Client5. Client1 should download the dump for it but maybe it receives the wrong DHCPOFFER and tries to download dump of Client 5 through the boot file name option in DHCPOFFER package.

My question is why iPXE on Client1 is replying to wrong DHCPOFFER?.The second question is that why Client1 is (probably) ignoring he DHCPNAK received from the Server and start tftp to download dump?. Is it a really problem in DHCP implement of iPXE.

I make sure that DHCP server configuration is correct. This problem I see is about five times in 20 times rebooting.

I am using undionly.kkpxe to boot.

Thanks alot
↧

Problems building under Ubuntu 14.10

February 2, 2015, 4:22 am
$
0
0
Hello all,

First off I'm an IPXE newbie so forgive me if this turns out to be a stupid question. I looked around in the forum and did not see any mentio of it (not that I could locate searching). Huh

I am trying to rebuild ipxe to embed a simple wmiboot script. First I used the GIT version and ran into errors, then I tried the 'release version from the Ubunto catalogs and had different problems. I can succesfully build the version from the catalogs, which is older, but it does not work (I get errors 'failed load ldlinux.c32' from iso and 'Boot Error' from the liso version). I am trying to boot them in a Hyper-V VM to test them before going to a remote site to setup a classroom with stations using ipxe. The version I can build from the ubuntu catalogs is 1.0.0+git-20131111.c3d1e78 (builds but will not boot). The prebuilt iso downloaded from your site boots fine on the same VM.

When I try to build the GIT version I get what appear to be errors from the bash scripts geniso and gendsk (also tried a floppy image). I get these errors from the GIT version whether I EMBED the script or not.

The errors I get from the GIT version are:
after issuing make bin/ipxe.iso Sad

[GENISO] bin/ipxe.iso
util/geniso: line 4: $'\r' command not found
util/geniso: line 5: syntax error near unexpected element ´$'\r''
'til/geniso: line 5: ´function help() {
arch/i386/Makefile.pcbios:59: recipe for target 'bin/ipxe.iso
' failed
make: ***[bin/ipxe.iso] Error 2

NOTE: I am working on a spanish language system and 'translating' the messages so they may not be precise. on third line the element starts with a backtick, but my international keyboard may not have generated it correctly.

Any ideas ?
↧

Does iPXE accept any DHCPOFFER message?

February 6, 2015, 12:47 am
$
0
0
Suppose that DHCP server broadcast its DHCPDOFFER message to its network, for one particular iPXE client. But at the same time, there's another iPXE client also waiting for DHCP server's reply. Will both client receive the same message and as a result, one recieves incorrect message?
↧
↧

iSCSI boot is failing

February 6, 2015, 3:53 pm
$
0
0
I have a new linux machine based on a Supermicro X10DRW-i motherboard. It has two onboard Intel i350 gigE NICs.

I have configured DHCP thusly:

Code:
host blah-iscsi {
                hardware ethernet 00:25:90:fc:3a:af;
                fixed-address 192.168.20.23;
                option iscsi-initiator-iqn "iqn.2015-02.blah.blah:1234";
                option root-path "iscsi:192.168.20.11:::00:iqn.1992-08.com.netapp:sn.123456:vs.1";
}

the NICs are configured to use DHCP to boot, and they appear to be retrieving the settings from teh DHCP server, but they do not continue to boot.

If I press ctrl-B to exit to the iPXE command line I can issue a dhcp command and try to sanboot, but it gets stuck.

[Image: iPXE_boot_hang2.jpg]

It just gets stuck at the "Booting from SAN device 0x80"

Any advice would be greatly appreciated.
↧

iPXE on USB stuck on initialisation (Dell d400 / tg3)

February 8, 2015, 10:25 am
$
0
0
Hello,

I finally decided to update my USB stick that I use to boot my computers via iPXE.

The version of the ipxe.usb I currently have (from ~2012) works ok on a Dell D400 laptop, but the latest one built from git doesn't, it gets stuck at the initial message "iPXE initialising devices...".

By going back in git commit history (and compiling on a VM running Ubuntu 12.04, to avoid issues with newer gcc versions) it seems that the problems started with commit f6840ba83e60631e6561a957f11867b206edd7d9 that introduced the new tg3 drivers, which indeed the laptop uses.

Is that a known issue? If not, how can I find out where the system gets stuck?
I'm no expert at iPXE code, so I did enable debug for the tg3, tg3_hw, tg3_phy and I could see that it gets there, but I don't know what else is suppose to happen, or which other module should I add to the debug.

Thanks.
↧
Search

How to change display resolution with (u)EFI BIOS

February 9, 2015, 1:26 am
$
0
0
Hi,

I use SYSLINUX 6.03 to boot PXE in LEGACY BIOS mode. With EFI BIOS i need to use chainload that is not yet supported.
I saw that i can do this with iPXE. It work fine. I use menu with a lot of entry and i need to have a higher resolution.
How can i do this with (u)EFI BIOS ?
I try to change it with a background png image. It work in LEBACY BIOS MODE but not in EFI mode.
I think that it may be possible because it works with SYSLINUX with vesamenu.c32

Thanks for all
↧

initiator-iqn not getting set

February 9, 2015, 2:36 pm
$
0
0
Hello,

I'm having some troubles getting a newly purchased machine to boot from an iSCSI LUN served from a NetApp filer.

I can do a network install of CentOS6 or CentOS7 to a fresh LUN. The CentOS installer is able to find the iSCSI target and install the OS. Now my problems begin, as I cannot get the new machine to boot off the remote LUN.

Here is the relevant portion of my dhcpd.conf file:

Code:
host blah-iscsi {
     hardware ethernet 00:25:90:fc:3a:af;
     fixed-address 192.168.20.23;
     option root-path "iscsi:192.168.20.11:::1:iqn.1992-08.com.netapp:sn.1234:vs.4";
     option iscsi-initiator-iqn "iqn.2015-02.blah:1234";
}

During boot I see the following in my dhcp log files:


Code:
Feb  9 14:01:39 dhcpd: DHCPDISCOVER from 00:25:90:fc:3a:af via 192.168.20.1
Feb  9 14:01:39 dhcpd: DHCPOFFER on 192.168.20.23 to 00:25:90:fc:3a:af via 192.168.20.1
Feb  9 14:01:39 dhcrelay: packet to bogus giaddr 192.168.20.1.
Feb  9 14:01:41 dhcpd: DHCPREQUEST for 192.168.20.23 (192.168.1.5) from 00:25:90:fc:3a:af via 192.168.20.1
Feb  9 14:01:41 dhcpd: DHCPACK on 192.168.20.23 to 00:25:90:fc:3a:af via 192.168.20.1
Feb  9 14:01:41 dhcrelay: packet to bogus giaddr 192.168.20.1.
Feb  9 14:01:41 in.tftpd[27549]: tftp: client does not accept options

and if I interrupt the boot process and enter the iPXE command line ping does not work until I type "dhcp" on the command line.

[Image: pre-dhcp_ipxe_ping.jpg]


if I inspect the config settings prior to manually issing a dhcp command it appears that most values are set except for the iqn-iniiator value.

[Image: pre-dhcp_ipxe_config1.jpg]
page2.
[Image: pre-dhcp_ipxe_config2.jpg]

it looks like the iqn-initiator value is not properly set. So clearly dhcp is partially working

if I manually issue the dhcp command from iPXE, then inspect the config settings the iqn-initiator value IS getting properly set:

[Image: post-dhcp_ipxe_config1.jpg]
page2.
[Image: post-dhcp_ipxe_config2.jpg]

But back on the iPXE command line, issuing an autoboot still fails.

I'm at a bit of a loss. What to try next?
↧
↧

Problem with Intel Pro/VE

February 12, 2015, 9:51 am
$
0
0
Hello,

I have been trying to get iPXE working for our training class. It works on some machines, but several of the machines are somewhat 'old' and the NIC does not seem to be detected.

I enabled a number of debugs including pci and undi and got these results>
(some omitted, but more PCI materials preceded)
PCI 04:08.0 (8086:1094) has driver "undipci"
PCI 04:08.0 has mem 90000000 io 1000 irq 11
PCI 04:08.0 probe failed: no such device (http://ipxe.org/2c80603b)

Followed the link and it shows a failure at a line of net/undi.c

Does anyone hav any idea how I can get this working ?

Thanks in advance for any help.
(unfortunately we have over a dozen of these boxes)
↧

iPXE script calls another iPXE script recursively

February 9, 2015, 5:31 pm
$
0
0
Hello,

I am writing a system which benchmarks http transfers in iPXE for different file sizes.

I have written the following(recursive) script:

(script.ipxe on somserver)
#!ipxe
chain http://someserver/script.ipxe
prompt

I get the following error after some recursions

http://someserver/script.ipxe.... Error 0x0001f714 (http://ipxe.org/0001f714)
Not in a script: Error 0x3d028001 (http://ipxe.org/3d028001)
Could not boot: Error 0x3d028001 (http://ipxe.org/3d028001)


I suspect iPXE may be running out of stack space. Is there another reason for this occurring? Is there a solution for this?

thanks
Siddharth
↧

Newbie problem with iPXE Quickstart Demo

February 16, 2015, 3:45 pm
$
0
0
Hi

I followed all the instructions to try the Quickstart Demo using the bootable iPXE image burned to a DVD.

Everything works fine. I get the "Congratulations! You have successfully booted the iPXE demonstration image....." message and then the root:/# prompt appears.

But now my system is completely hung. I can't even use CTRL-ALT-DEL.

I tried several times and get the same thing.

What could be the problem?

I would very much appreciate any help or suggestions.

Thank you
↧
Viewing all 1484 articles
Browse latest View live
Search