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

iPXE EFI crash on Dell R630 + ConnectX-4

March 19, 2019, 3:45 am
$
0
0
Hi,

iPXE EFI is crashing while booting CentOS 7.6 installation kernel/initrd on a Dell R630 with a Mellanox ConnectX-4 card.

Here's a screenshot of the crash: https://i.imgur.com/kfR4fkD.png
Here's the dump the box produces: http://dpaste.com/3T4MW0G.txt

Using snponly.efi seems to make it work.

iPXE version is b6ffe.

The box is running the latest BIOS and NIC firmware.

Is this an iPXE driver bug?

Let me know if you need more information.

Thank you.
↧
Search

IPXE sanboot to NVME disk

March 20, 2019, 9:05 am
$
0
0
Hi,

I am using legacy boot which is being deployed using IPXE.
I can currently boot perfectly into devices with sda disks from IPXE using
sanboot --no-describe 0x80
However, this same command does not work for booting nvme disks form IPXE.
Looking up on IPXE documentations did not give any information on this.

Any help or suggestions will be appreciated.

Thank you.
↧
↧

TLS received oversize handshake

March 24, 2019, 3:33 pm
$
0
0
Hi All,
Our Red Hat OpenShift/Kubernetes servers appear to have been upgraded over the last few days and iPXE started giving me the following error. I've pulled the latest sources and compiled with DEBUG=tls:1 and disabled OCSP.

Here's a screen dump of the error with tls debug enabled:

https://pasteboard.co/I6XJBPp.png

Any thoughts hugely appreciated. I can provide packet traces if that helps too.

Cheers,

Doug
↧

How to boot ISO-image via SMB/CIFS

March 28, 2019, 10:41 am
$
0
0
Hi there!

Guys, could you give me please a simple example that shows how to boot 4GB ISO-image via SMB/CIFS protocol because I use local windows network? My ISO contains "EFI" folder and bootmgr file.

Thank you!


P.S. If it is not possible to use SMB/CIFS for some reasons could you please give an example of booting ISO via HTTP then?
↧

Streamlining this whole use of iPXE

April 1, 2019, 3:50 pm
$
0
0
Hi!

I just found out about iPXE when I was working on a project relating to AWS.

Basically I was able to boot from the test chain from the iPXE page. I looked around youtube and I see this have been around a while.

Is there a list of available repos I can play with? I'm partial to Linux-Lite.

Or do you recommend I go through the whole documentation, write my own script.

The thing is, I'm not interested in actually storing any of this in a web service. The idea is I want something quick to boot into (like the test) in my virtualbox or vmware image inside GNS3.

Thanks!

Matt
↧
↧

what's the difference between ata_open and scsi_open

April 4, 2019, 12:47 am
$
0
0
Hi,
the aoe.c use ata_open to attach disk,but iscsi.c use scsi_open , so what\s the difference?

If I want to implement a new protocol , which one should I use?

And is there any documents about how to implement a new protocol ?

many thanks!
↧

Noob Question: Burn rom in onboad LAN ?

April 7, 2019, 12:59 pm
$
0
0
Hi,

i have an "Fujitsu Futro S550-2" and i dont if its possible or not to burn a compiled "10ec8168.rom" into the PXE flash part of the onboard device: "Realtek 10ec:8168" because i think the part of PXE for this device resist into the bios or ?Huh

Thanks
↧

Load with wimboot different ei.cfgs

April 8, 2019, 5:28 am
$
0
0
Hello,
can i load with wimboot different ei.cfgs for example:
one ei.cfg has OEM the other Retail or Eval?

Thanks in advance

Jame
↧
Search

ipxe menu with menubar possible ?

April 9, 2019, 4:56 am
$
0
0
Hi,

is there a way to get inside the ipxe menu a menubar like whats on the screen ?
If yes, how can i add them, i used the ipxe menu example from github.

[Image: m9dBiek.png]

Thanks
↧
↧

iPXE boot 3Com PCMCIA card

April 11, 2019, 1:19 pm
$
0
0
Hello again, dear forum! : )

I`ve got two Panasonic Toughbooks CF-M34 mark 1, as out company would have thrown them away elsewise.

Since they are in perfect state still, I decided to dispose them myself in person. ; )
The Toughbooks unfortunately allow only to boot from A: or C:. Also ths thing has no ethernet port, same goes for the docking station, that I aso have.

Okay, so far so good.. I can boot from floppy, which means I could iPXE boot some boot media, so I thought, but since this hardware has no ethernet port, I need to use the PCMCIA port. Now I have three PCMCIA LAN cards.. a Highscreen one, a Xircom one and a 3Com. According to the [iPXE device list] the 3Com and Xircom cards are the most promising ones.
Unfortunately none of the cards does work with the latest iPXE boot image. :/

Question is, is there a way to enable PCMCIA support and make a 3Com 3C589D Combo card work with iPXE?

I`d like to boot CloneZilla first, to image the current HDD status, and then, after this, I`d install either [ArcaOS] or OS/2 Warp. - Maybe even Windows 2000.

Thanks in advance for reading : ))
↧

UEFI iscsi boot windows 7 slowly

April 12, 2019, 9:17 am
$
0
0
forgive my poor english first.Sad

Test environment:
ServerPC: windows server 2012 iscsi target + tftp32 + latest ipxe.efi / snponly.efi
ClientPC : 1000M PCI-E NIC with UEFI network boot enabled ,local harddisk has removed.

After ClientPC boot into ipxe shell , I type
dhcp --> set keep-san 1 -> sanboot iscsi:10.10.10.253::::iqn.2019.com.test:gpt in shell , then the clientPC begin load OS image, but very very slowly, it takes about 3 - 5 minutes before the windows boot animation logo appeared.

and at this time, I found the wintarget service in server side has crashed, and once I restart the wintarget servive, it crashed immediately , after crash -> restart for 10 - 20 times , the clientPC can successfully boot into windows desktop.

I tried snponly.efi , and tried another PC with diffrent NIC, the resule always same. So I guess this is not a network or NIC problem, it maybe the ipxe send a wrong scsi command to iscsi target, and caused the target crash.

So I fetched the lates IPXE source ,and compiled with DEBUG=iscsi,scsi,efi_block:2, and enable syslog, then I replace ipxe.efi in server side, and reboot the clientPC.

the syslog is:

...................
<6>ipxe: EFIBLK 0x80 read LBA 0x0027cd38 to 0xbf4000+0x00000200 10.10.10.1 13/04 00:05:37.264
<6>ipxe: EFIBLK 0x80 write LBA 0x0027cd38 from 0xbf4000+0x00000200 10.10.10.1 13/04 00:05:37.275
<6>ipxe: iSCSI 0xe9a3008 start data out DataSN 0x0 len 0x200 10.10.10.1 13/04 00:05:37.283
<6>ipxe: EFIBLK 0x80 read LBA 0x00072800 to 0xb80000+0x00002000 10.10.10.1 13/04 00:05:37.354
<6>ipxe: EFIBLK 0x80 read LBA 0x00072800 to 0xbea000+0x00004000 10.10.10.1 13/04 00:05:37.363
<6>ipxe: EFIBLK 0x80 read LBA 0x00672800 to 0xb80000+0x00000400 10.10.10.1 13/04 00:05:37.373
<6>ipxe: EFIBLK 0x80 read LBA 0x0067280a to 0xb80000+0x00000400 10.10.10.1 13/04 00:05:37.383
<6>ipxe: EFIBLK 0x80 read LBA 0x00072960 to 0xbee000+0x00004000 10.10.10.1 13/04 00:05:37.393
<6>ipxe: EFIBLK 0x80 read LBA 0x00672d54 to 0xb80000+0x00000400 10.10.10.1 13/04 00:05:37.402
<6>ipxe: EFIBLK 0x80 read LBA 0x00075240 to 0xc00000+0x00004000 10.10.10.1 13/04 00:05:37.419
<6>ipxe: EFIBLK 0x80 read LBA 0x0067aad0 to 0xb80000+0x00000400 10.10.10.1 13/04 00:05:37.429
<6>ipxe: EFIBLK 0x80 read LBA 0x0027cd38 to 0xbf4000+0x00000200 10.10.10.1 13/04 00:05:37.439
<6>ipxe: EFIBLK 0x80 write LBA 0x0027cd38 from 0xbf4000+0x00000200 10.10.10.1 13/04 00:05:37.449
<6>ipxe: iSCSI 0xe9a3008 start data out DataSN 0x0 len 0x200 10.10.10.1 13/04 00:05:37.459
<6>ipxe: EFIBLK 0x80 read LBA 0x00072800 to 0xb80000+0x00002000 10.10.10.1 13/04 00:05:37.522
<6>ipxe: EFIBLK 0x80 read LBA 0x00000000 to 0xb80000+0x00000200 10.10.10.1 13/04 00:05:37.532
<6>ipxe: EFIBLK 0x80 read LBA 0x00000001 to 0xb80000+0x00000200 10.10.10.1 13/04 00:05:37.541
<6>ipxe: EFIBLK 0x80 read LBA 0x00000001 to 0xb80000+0x00000200 10.10.10.1 13/04 00:05:37.550
<6>ipxe: EFIBLK 0x80 read LBA 0x00000000 to 0xb80000+0x00000200 10.10.10.1 13/04 00:05:37.560
<6>ipxe: EFIBLK 0x80 read LBA 0x00000001 to 0xbf4000+0x00000200 10.10.10.1 13/04 00:05:37.569
<6>ipxe: EFIBLK 0x80 read LBA 0x00000002 to 0xbf5000+0x00004000 10.10.10.1 13/04 00:05:37.579
<6>ipxe: EFIBLK 0x80 read LBA 0x00000002 to 0xbf5000+0x00004000 10.10.10.1 13/04 00:05:37.589
<6>ipxe: EFIBLK 0x80 read LBA 0x00000800 to 0xbf5000+0x00002000 10.10.10.1 13/04 00:05:37.598
<6>ipxe: EFIBLK 0x80 read LBA 0x00032800 to 0xbf5000+0x00002000 10.10.10.1 13/04 00:05:37.608
<6>ipxe: EFIBLK 0x80 read LBA 0x00072800 to 0xc04000+0x00004000 10.10.10.1 13/04 00:05:37.618
<6>ipxe: EFIBLK 0x80 read LBA 0x00672800 to 0xbf5000+0x00000400 10.10.10.1 13/04 00:05:37.627
<6>ipxe: EFIBLK 0x80 read LBA 0x0067280a to 0xbf5000+0x00000400 10.10.10.1 13/04 00:05:37.636
<6>ipxe: EFIBLK 0x80 read LBA 0x00072960 to 0xc08000+0x00004000 10.10.10.1 13/04 00:05:37.652
<6>ipxe: EFIBLK 0x80 read LBA 0x0067ab08 to 0xbf5000+0x00000400 10.10.10.1 13/04 00:05:37.664
<6>ipxe: EFIBLK 0x80 read LBA 0x0101c830 to 0xbf5000+0x00002000 10.10.10.1 13/04 00:05:37.673
<6>ipxe: EFIBLK 0x80 read LBA 0x004a5988 to 0x24c5000+0x014c2600 10.10.10.1 13/04 00:05:37.685
<6>ipxe: iSCSI 0xe9a3008 closed: Connection reset (http://ipxe.org/0f0a6095) 10.10.10.1 13/04 00:05:37.811
<6>ipxe: SCSI 0xe9a36e8 tag 18ae01e6 closed: Connection reset (http://ipxe.org/0f0a6095) 10.10.10.1 13/04 00:05:37.819
<6>ipxe: iSCSI 0xe99fb08 initiator iqn.2010-04.org.ipxe:2dfe4d56-efb6-00a3-efcf-7a4242c83c9f 10.10.10.1 13/04 00:05:37.830
<6>ipxe: iSCSI 0xe99fb08 target 10.10.10.253 iqn.2019.com.test:gpt 10.10.10.1 13/04 00:05:37.834
<6>ipxe: iSCSI 0xe99fb08 entering security negotiation 10.10.10.1 13/04 00:05:37.841
<6>ipxe: SCSI 0xe9a12e8 created for LUN 0000-0000-0000-0000 10.10.10.1 13/04 00:05:37.850
<6>ipxe: iSCSI 0xe99fb08 closed: Connection reset (http://ipxe.org/0f0a6095) 10.10.10.1 13/04 00:05:37.858
<6>ipxe: iSCSI 0xe99f908 initiator iqn.2010-04.org.ipxe:2dfe4d56-efb6-00a3-efcf-7a4242c83c9f 10.10.10.1 13/04 00:05:42.853
<6>ipxe: iSCSI 0xe99f908 target 10.10.10.253 iqn.2019.com.test:gpt 10.10.10.1 13/04 00:05:42.860
<6>ipxe: iSCSI 0xe99f908 entering security negotiation 10.10.10.1 13/04 00:05:42.868
<6>ipxe: SCSI 0xe99fb28 created for LUN 0000-0000-0000-0000 10.10.10.1 13/04 00:05:42.876
<6>ipxe: iSCSI 0xe99f908 closed: Connection reset (http://ipxe.org/0f0a6095) 10.10.10.1 13/04 00:05:42.886
......................................

once the log line " <6>ipxe: EFIBLK 0x80 read LBA 0x004a5988 to 0x24c5000+0x014c2600 10.10.10.1 13/04 00:05:37.685 " appeared , the wintarget crashed .
from the source , the 0x014c2600 in the log line means read size, I don't understand why the system try to read 0x014c2600 bytes (21M) data in one scsi IO.
It seems there is a bug in ipxe efi block io?

(This boot slow problem and large size scsi read request won't appear in bios mode iscsi boot, only uefi)

any one can help? thanks very much.
I simply add code :

if (len >= 0x1000000)
{
return EFI_BAD_BUFFER_SIZE;
}

in the function efi_block_io_read (efi_block.c) , the client can successfully boot in 30 - 40 seconds, and the target has not crash.

But this is not a good solution, we need to found the reason why the len argument is so big.
↧

Can ipxe support the ECDHE for TLS?

April 12, 2019, 6:48 pm
↧

can't open '/conf/arch.conf'

February 25, 2019, 4:00 am
$
0
0
try to load debian 9.5 from headless and it gave me this error:
vmlinuz and initrd.img (renamed from initrd) was copied from debian 9.5 netboot.

```
Select an option and press ENTER to boot/install, or F1 for Help
ready.
▒Loading, please wait...live/INITRD_N10.3.2.GZ....
/init: .: line 37: can't open '/conf/arch.conf'
[ 2.296345] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200
[ 2.296345]
[ 2.305438] CPU: 1 PID: 1 Comm: init Not tainted 4.9.0-7-686 #1 Debian 4.9.110-1
[ 2.312791] Hardware name: To be filled by O.E.M. To be filled by O.E.M./SHARKBAY, BIOS 4.6.5 12/11/2013
[ 2.322215] f2d21f18 c32e3132 f2ccb600 f2cfe040 c3158ac1 f2cfe040 f2ccb680 f2cfe040
[ 2.330081] f2cfe040 f2d21f64 c305c5e0 c368d010 00000200 be0509d1 00000002 f2eaade0
[ 2.337947] f2cfe040 01000154 f2ccba40 c37634c0 f51e05c0 00000000 f2d21f4c f2d21f4c
[ 2.345807] Call Trace:
[ 2.348256] [<c32e3132>] ? dump_stack+0x55/0x73
[ 2.352854] [<c3158ac1>] ? panic+0x94/0x1d8
[ 2.357107] [<c305c5e0>] ? do_exit+0xa00/0xa00
[ 2.361618] [<c305c657>] ? do_group_exit+0x37/0x90
[ 2.366478] [<c305c6c6>] ? SyS_exit_group+0x16/0x20
[ 2.371420] [<c3001a88>] ? do_fast_syscall_32+0x98/0x160
[ 2.376796] [<c359743a>] ? sysenter_past_esp+0x47/0x75
[ 2.382027] Kernel Offset: 0x2000000 from 0xc1000000 (relocation range: 0xc0000000-0xf7ffdfff)
[ 2.390594] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200
[ 2.390594]

```
↧
↧

waiting for link-up on netX ..howto skip unused devices

April 25, 2019, 3:00 pm
$
0
0
Hi

i have 2 NIC's in my pc, one onboard and a quad port one, i want to pxe boot from the onboad device
but the quad port card comes on initialising devices first. so i dont want to wait for all 0-3 nics (net0/net1/net2/net3) of this quad port card getting timeout and then ipxe tries to boot from the onboard lan

[Image: 9qsTEo3.png]

how can i skip the devices net0-3, before (net4...the real pxe boot device) without pressing every time ctrl+c ? i mean how can i directly boot from net4 ?
thanks
↧

error

May 1, 2019, 12:20 am
$
0
0
I am having issue with one Dell model to image, keep getting the following error.

iPXE 1.0.0+ -- Open Source Network Boot Firmware -- http://ipxe.org
Feature: DNS HTTP iSCSI TFTP SRP AoE EFI Menu
Waiting for link-up on net0...… Ok
Configuring (net0 6c:2b:59Big Grin3:63:77)……...No configuration methods succeeded (http://ipxe.org/040ee186)

any help would grateful

Macscottie
↧
Search

Net-booting an EFI image on an aarch64 server with iPXE script

May 1, 2019, 3:23 pm
$
0
0
I'm having some problems getting netboot to work on a UEFI based arm 64-bit system (Ampere Computing eMAG). Right now I'm just trying to get Ubuntu to work.

I was originally trying to use a file like:

Code:
#!ipxe
kernel http://path/to/repo/linux initrd=initrd
initrd http://path/to/repo/initrd.gz
boot

And was getting this error: http://ipxe.org/err/2e0080

My assumption is that the linux image is not EFI compatible. In the Ubuntu path I'm using there's a netbootaa64.efi file, which (and I have limited experience) looks like the right netboot binary for me to use. But I'm not quite sure how to use iPXE in this way.

Some more background:
Ubuntu netbootaa64.efi path: here
iPXE Version: 1.0.255+
Provisioning Platform: Packet
HW Platform: Ampere Computing eMAG (c2.large.arm on Packet)

I did some tests trying to chain load the efi file, something like:
Code:
#!ipxe
chain http://path/to/repo/netbootaa64.efi

The error above goes away and the efi file is downloaded, but I get dropped straight into the grub shell with no apparently filesystem*.

*ls in the grub shell gives me (hd0) with no partitions listed. ls (hd0)/ gives me a 'no filesystem found' error.

I also found some threads that reference using the
Code:
kernelefi
or
Code:
initrdefi
commands in the iPXE script, but those commands are not found and give an error when the script runs.

Anyone have some pointers to how I can get a netboot of Ubuntu working through iPXE on an aarch64 UEFI based system? Really stuck on this one.
↧

Detecting hardware and platform

May 2, 2019, 7:46 am
$
0
0
Good day,

I'm currently doing volunteer work for a school that has a limited budget. They have about 40 Raspberry Pi 3B+ units, 20 Dell PCs, and 10 HP PCs. All Dell units are the same as each other and all HP units are the same as each other (i.e. homogeneous configuration). The school doesn't have the money to replace the hard disks in all the units (all PCs and Pis were donated with no persistent storage device), and they just need to boot Ubuntu or Raspian to run a browser, educational games, etc.

Is it possible with iPXE to, on the client PCs, at boot time:
  • Detect the system architecture (i.e. arm versus Intel) so that it auto-boots a specific boot image without user intervention (i.e. Ubuntu versus Raspian).
  • Detect differences in hardware (i.e. so the Intel units can check before booting, what manufacturer/model/make of network card, HDD if present, hardware, etc. (we'd like to use a different boot image for the Dell versus HP machines, as we may be able to get a donation of HDD/SDD units for the HP units, in which case, they would still boot via iPXE, but the persistent storage could be used to hold onto kids' files, drawings, animations, etc.).

Thank you for your time and assistance.
↧
↧

same config for uefi and legacy

May 2, 2019, 10:01 am
$
0
0
Hello everyone.
I have my ipxe server that works great.
I just have a problem when I want to start my client computers on a winpe image in tftp.
I have to have 2 configurations for legacy positions and for uefi posts. For uefi, I put "kernel wimboot" then "initrd BCD"... For legacy, I have to put "kernel wimboot wimboot" then "initrd BCD BCD" ...
Is it possible to have the same config for all positions in legacy or uefi? Thank you in advance
↧

http(s) authentification : how to pass informations ?

May 5, 2019, 11:25 am
$
0
0
Hello, I failed to find documentation about that and rare traces found on the forum are like this :

Code:
https://${username:uristring}:${password:uristring}@${net0.dhcp/next-server}/pxe/menu.php

How are ${username:uristring} and ${password:uristring} populated in this case ?

Is it possible to prompt the user for these informations ?

Is there a list of all variables iPXE sets itself that could be passed to a request ?
↧

ipxe -> symantec pxe chain

May 7, 2019, 3:21 am
$
0
0
Hallo all,

Could someone help me with the following?:

We boot our clients using ipxe, users get a menu to boot from.
One of the options is Altiris(symantec).

We chainload using the following command:
chain tftp://192.168.200.28/BSTrap/x86pc/BStrap.0, this works in BIOS.

For UEFI we use:
chain tftp://192.168.200.28/BTrap/X64/BStrap.efi

This give us the error:
Proxy offer not received Failed to initialize application
PXE-E16: No offer received.

If i leave out ipxe and directly boot Symantec via pxe in UEFI, it works after setting option 60 PXEClient.

Using wireshark without ipxe i see that symantec does a ProxyDHCP, some this does not work from ipxe.

Could someone help me with this i have tried a lot of things but i am not able to resolve it?

Thank you
Wietse

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