lling to sign
each other's keys, but I have met plenty of folks that consider "in person
meeting and show government ID" to be the bar. Take a look at
https://wiki.debian.org/Keysigning/Coordination and
https://wiki.debian.org/DebianLocations.
Sincerely,
-Alex
On Fri, Feb 10, 202
The script was the culprit indeed, it returned as PXE-NBP. It loads up fine
now
Thanks!
On Sat, 2 Jul 2022 at 15:27, Alex Leo wrote:
> I'll check the apache logs later today.
> Regarding ipxe.lkrn I know it works since the example
> http://boot.ipxe.org/demo/boot.php loads f
ead the pined topics in the forum it explains the state.
Didn't notice that discussion was moved to GitHub. I was checking by last
reply and saw forum was somewhat active.
On Sat, Jul 2, 2022, 10:54 AM Christian Iwata Nilsson,
wrote:
>
>
> On Sat, 2 Jul 2022, 04:39 Alex Leo
PEND dhcp && chain http://192.168.10.123/windows/win2019/boot.ipxe
Anyone have ideas why it won't boot? I have wimboot in same directory as
boot.ipxe
Alex
___
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo/ipxe-devel
Hi, I was wanting to try out this tool, but the quickstart seems to carry some
implied knowledge, or be missing some steps:
1 Download sdcard.img and write it onto any blank micro SD card using a tool
such as dd or Etcher.
2 Insert the micro SD card into your Raspberry Pi.
3 Power on your Raspbe
e solution?
Thank you.
Alex Vaserfirer
Principal Engineer
office: 1 (972) 633-3409
alex.vaserfi...@unicomengineering.com<mailto:alex.vaserfi...@unicomengineering.com>
<http://www.unicomengineering.com/> [cid:6edc8b4ebdfb48a0af35af483839ea02]
<http://
Hello.
I couldn't create a subject at your forum therefore I send the message to you
on email:
"Im create HDD image from physical hdd 3,5 GB.
On this hdd one boot partition 3.5GB, FAT32 and installing DOS(from win98).
On this partition there is a lot of different files, the total size of all
fil
t the switch
reports the LACP links as being inactive (not down which is what happens
when nothing's plugged in).
Any suggestions? In particular what can I do to further diagnose this issue
(can I watch packets that iPXE is sending/receiving)? I'm using the i
Hi Michael,
Can you suggest anything that would make you consider taking this patch?
Thanks,
Alex
On Mon, 2015-02-09 at 12:52 -0700, Alex Williamson wrote:
> iPXE uses DHCP timeouts loosely based on values recommended by the
> specification, but often abbreviated to reduce timeouts for re
#undef PXEBS_MAX_TIMEOUT_SEC
#define PXEBS_MAX_TIMEOUT_SEC 7
Signed-off-by: Alex Williamson
---
Michael, does this look reasonable or can you suggest a better
mechanism for downstreams to tune DHCP timeouts for customers on
topologies that require something more spec compliant without
#undef PXEBS_MAX_TIMEOUT_SEC
#define PXEBS_MAX_TIMEOUT_SEC 7
Signed-off-by: Alex Williamson
---
src/config/general.h| 61 +++
src/include/ipxe/dhcp.h | 11 +---
src/net/udp/dhcp.c | 31 ++--
3 files
request phase.
Signed-off-by: Alex Williamson
---
This continues to be a problem that customer complain about. The
xNBA version of ipxe has already included this commit [1][2]. Others
have also expressed support for this patch in the past [3]. Previous
postings of this patch can be found here
This is more or less an issue with Apple choosing to create their own EFI
system rather than adhere to standards. gPXE and early iPXE builds work great
with Apple EFI due the the fact that gPXE/iPXE would forcibly reset the network
drivers rather than allow EFI to control this. This was fixed in
operation? Obviously, we can just comment
that line out, but if the only downside is a slightly higher CPU usage
during menu versus keys not working it seems that erring on the
always-works option by default might be sensible.
Either way, thank you for your help!
-Alex
On Thu, Apr 17, 2014 at 3:24 PM
enu and got to the ipxe command line what do you get when
> you press the arrow keys?
>
>
> On 9 April 2014 03:41, Alex Davies wrote:
>
>> Hi All,
>>
>> We had the same problem using SOL on Dell hardware.
>>
>> I tried both your patch Michael and the divi
A, B, C and D. Here I pressed the key after each word (e.g. "u", "p", up A down B right C left D
up: command not found
-Alex
From: Alex Davies [mailto:a...@davz.net]
Sent: 11 April 2014 23:18
To: Alex Davies
Subject: Fwd: [ipxe-devel] serial arrow keys broken
something. What debug
flag should I enable to see what it is getting?
The menu is working nicely with color and if I connect to the 'full
console' via the DRAC, and move the arrow key, the SOL menu refreshes
correctly.
Thanks!
-Alex
On Thu, Mar 27, 2014 at 2:46 PM, Michael Brown wrote:
t where we try to boot from the NIC. This
change allows downstream distributions to modify or disable either
timeout for their particular needs.
Signed-off-by: Alex Williamson
---
v2: Allow independent configuration of each banner timeout.
Michael, if I haven't captured your suggestion
ation.
Signed-off-by: Alex Williamson
---
src/arch/i386/prefix/romprefix.S | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/src/arch/i386/prefix/romprefix.S b/src/arch/i386/prefix/romprefix.S
index 091673d..3a80a20 100644
--- a/src/arch/i386/prefix/romprefix.S
+++
Add an i386 specifical initialization hook and BSS data to allow
prefix code to store autoboot device information.
Signed-off-by: Alex Williamson
---
src/arch/i386/core/pci_autoboot_device.c | 52 ++
1 file changed, 52 insertions(+)
create mode 100644 src/arch
device
in another device ROM, ex. wifi iPXE loaded from wired NIC ROM space.
Thanks,
Alex
---
Alex Williamson (3):
[autoboot] Enable infrastructure to specify an autoboot device location
[i386/core] Add support for setting autoboot_device from BSS
[romprefix] Store boot bus:dev.fn
means that all netdevs matching the autoboot device location will
be given priority. The previous behavior of attempting boot from any
netdev is preserved in the case where no matching netdevs are found,
which includes the case of an autoboot device being unspecified.
Signed-off-by: Alex
> This means that PCI version is PCI2.1 right? How iPXE check this?
It's in reference to the PCI BIOS version, not to the PCI hardware
specification of the device. Thanks,
Alex
___
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
https://li
request phase.
Signed-off-by: Alex Williamson
---
I posted this previously[1] and prior to that also sent a question to
the list asking why iPXE uses the non-spec compliant DHCP timeouts
that it does[2]. There was some support for this patch[3], but it was
never commited. My ping a couple
pt to autoboot remaining devices. The
remaining devices are still available for interactive or scripted
boot.
Signed-off-by: Alex Williamson
---
Changes since RFC:
- Found how to properly store and retrieve data across real/protected
- Switch to "preferred" flag on device_descr
t where we try to boot from the NIC. This
change allows downstream distributions to optionally disable the ROM
init-time banner while retaining the boot-time banner to create a
single binary supporting both use cases.
Signed-off-by: Alex Williamson
---
src/arch/i386/prefix/romprefix.S |2 ++
are better ways to
handle the assembly and pass the data between real and protected modes
(I don't claim to know x86 assembly).
[1] http://lists.ipxe.org/pipermail/ipxe-devel/2013-November/002944.html
Signed-off-by: Alex Williamson
---
src/arch/i386/prefix/romprefix.S | 21 +++
Hi, Guys.
We are planning to start working on adding BCV support based on ipxe code.
Any reason why the iSCSI support and sun_hook are implemented above the BEV not
the BCV as the PnP spec suggests?
Any major issues that we may encounter in this effort?
Thanks
Alex
we can get this working like it's supposed to? Thanks,
Alex
___
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
Hi, Milan.
The ConnectX3 cards have Mellanox modified version of ipxe ,
FlexBoot(http://www.mellanox.com/page/products_dyn?product_family=34&mtag=flexboot).
The issue you are describing may be connected to autosensing , when the nic
doesn't recognize the link layer correctly.
Please try burning
Perfect, It may take some time to see if this fixes the issue we have been
seeing.
I will get back to this mailing list with feedback when I have one.
Thanks for the effort Michael.
Alex
-Original Message-
From: Michael Brown [mailto:mbr...@fensystems.co.uk]
Sent: Saturday, July 13
Thanks for the info.
Unfortunately the configuration from net0 will persist within the undi
interface - the OS driver will use the wrong configuration.
-Original Message-
From: Michael Brown [mailto:mbr...@fensystems.co.uk]
Sent: Saturday, July 13, 2013 4:31 PM
To: Alex Markuze
Cc: ipxe
On Mon, 2013-06-24 at 17:07 +0100, Michael Brown wrote:
> On 21/06/13 22:15, Alex Williamson wrote:
> > Ping. Comments?
>
> One issue: fetch_settings_origin() will return NULL if the setting is
> not found, but passing in NULL to the subsequent fetch_ipv4_setting()
> will
Ping. Comments? There was one +1 for some fix in this space. Thanks,
Alex
On Fri, 2013-06-07 at 14:22 -0600, Alex Williamson wrote:
> For discovery, both the DHCP and PXE specs suggest timeouts of 4, 8,
> 16, and 32 seconds. This gives us a maximum timeout of 60 seconds,
> versus th
Ping. Comments? Thanks,
Alex
On Fri, 2013-06-07 at 09:38 -0600, Alex Williamson wrote:
> In cases where we have both a DHCP and ProxyDHCP response we retrieve
> the next-server and filename independently. This means they can
> actually come from different settings blocks. For insta
request phase.
Signed-off-by: Alex Williamson
---
src/include/ipxe/dhcp.h |4
src/net/udp/dhcp.c | 22 +-
2 files changed, 13 insertions(+), 13 deletions(-)
diff --git a/src/include/ipxe/dhcp.h b/src/include/ipxe/dhcp.h
index b97dfe3..f3f7185 100644
--- a/src
-server from net0.dhcp. It's sensible that
filename+next-server should be treated as a pair and retrieved from
the same settings block. Re-order fetch_next_server_and_filename to
get filename first, find the origin settings block, and get
next_server from the same.
Signed-off-by: Alex Willi
On Fri, 2013-06-07 at 13:28 +0100, Michael Brown wrote:
> On 06/06/13 23:37, Alex Williamson wrote:
> > When iPXE tries to boot in the above environment, it tries to load
> > tftp://10.0.0.1/pxelinux.0 as the boot file. The next-server comes from
> > server1's DHCP pack
an't add an artificial priority to get
them in the correct order. Registering the settings from the ProxyDHCP
packet before the DHCP packet does work, but it's ugly and prone to
being broken by changes to the list manipulation code in settings.
Suggestions? Thanks,
Alex
__
t
includes the PXEClient tag. iPXE waits for 2 seconds total to have
elapsed. Why? Are we just trying to reduce that 12 second delay in a
non-PXE environment?
If there's agreement that at least the discovery phase should be
something closer to the spec defined intervals, I can post a patch
mailto:mbr...@fensystems.co.uk]
Sent: Friday, May 24, 2013 3:16 PM
To: Alex Markuze
Cc: ipxe-devel@lists.ipxe.org
Subject: Re: [ipxe-devel] 64 bit bARS support.
On 24/05/13 10:54, Alex Markuze wrote:
> I've noticed that the iPXE code has macros and comments regarding the
> support of 64 bit BAR ad
Hi,
On Mellanox NICs both ports share the same PCI bus function, the iPXE supports
this by allowing several net devices.
Unfortunately when both ports are connected to a subnet with a DHCP/BOOT
server. If the first port finishes the DHCP process and downloads the menu ,
but the uses chooses to a
Hello,
I've noticed that the iPXE code has macros and comments regarding the support
of 64 bit BAR addresses.
Has this code been ever validated? Does it work or does it still need patching?
Thanks
___
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
h
hanks,
Alex
On Wed, May 30, 2012 at 12:13 PM, Oliver Rath wrote:
> Hi Alex
>
> Am 30.05.2012 12:59, schrieb Oliver Rath:
>> [..]
>>
>> Am 30.05.2012 12:42, schrieb Alex Davies:
>>> Hi All,
>>>
>>> If I enter iPXE shell and enter "chain
e slashing and adding quotes to no avail (these escape
characters are simply converted too).
Is there another way?
Thanks,
Alex
--
Alex Davies
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. I
This works - thanks!
Is net0 always the 'correct' one (say if the server booted from NIC2)?
Thanks,
Alex
On Tue, May 15, 2012 at 11:34 AM, Michael Brown wrote:
> On Tuesday 15 May 2012 11:08:15 Alex Davies wrote:
> > If I point iPXE directly to tftp://ip.of.wds/pxelinux.n12
ve thought that I should be able to
override this in iPXE with a set command. Does anyone know if this is
possible and if so what to 'set'?
Thanks,
Alex
--
Alex Davies
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or e
oduce this error.
>
> Ignore that. I managed to reproduce the error on an older version of gcc
> (4.4.1). Should now be fixed:
>
> http://git.ipxe.org/ipxe.git/commitdiff/6a4b128
>
> Michael
--
Alex Davies
This email and any files transmitted with it are confidentia
’ does break
strict-aliasing rules
tests/list_test.c:437: note: initialized from here
make: *** [bin/list_test.o] Error 1
I get no such error building 838a76a042684.
Thanks,
Alex
--
Alex Davies
This email and any files transmitted with it are confidential and
intended solely for the use
that just runs wget to pull
down a large image, which should not be too complicated, but i'm loath to
reinvent a wheel.
Thanks,
Alex
On Sat, Mar 31, 2012 at 2:00 PM, Jarrod Johnson
wrote:
> xCAT stateless
--
Alex Davies
This email and any files transmitted with it are confidential
64 bit version of
unidonly.kpxe that can address all the system memory?
Failing that, is anybody else booting large initrd images successfully with
iPXE?
Thanks,
Alex
___
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
https://lists.ipxe.org/mailman
Just to follow this up in case anybody else finds this thread, after some
internal work to allow us to remove the legacy system, we have done exactly
as you suggest and had iPXE working well in testing for several weeks now.
Thanks!
-Alex
On Wed, Feb 29, 2012 at 5:03 PM, Gabriel Barazer wrote
That replicates my problem exactly, but I can't remove the first step :(
Thanks for confirming, does anyone have an idea of a fix?
Is it possible to configure iPXE to show a menu, one option of which is to
load pxelinux from iPXE?
Thanks,
Alex
Sent from a mobile device
On Feb 29, 2012 3:
on how best to fix / get around this?
Thanks,
Alex
--
From: John Julien [mailto:john at julienfamily.com]
Sent: Thursday, July 28, 2011 5:43 PM
To: ipxe-devel at lists.ipxe.org
Subject: UNDI Memory Error
Hi,
I've come across an issue using the UNDI driver of the Broadcom 5709C card.
On Tue, 2011-03-15 at 02:13 +, Michael Brown wrote:
> On Tuesday 15 Mar 2011 01:25:51 Michael Brown wrote:
> > On Monday 14 Mar 2011 19:57:35 Alex Williamson wrote:
> > > Ok, sorry for the distraction, I think I can explain it now. Last week
> > > I was testing larg
On Tue, 2011-03-15 at 01:25 +, Michael Brown wrote:
> On Monday 14 Mar 2011 19:57:35 Alex Williamson wrote:
> > Ok, sorry for the distraction, I think I can explain it now. Last week
> > I was testing large (8G) guests. Today I was trying to figure out how
> > the pcne
On Mon, 2011-03-14 at 13:18 -0600, Alex Williamson wrote:
> On Mon, 2011-03-14 at 12:22 -0600, Alex Williamson wrote:
> > On Sat, 2011-03-12 at 12:57 +, Michael Brown wrote:
> > > On Saturday 12 Mar 2011 12:05:53 Michael Brown wrote:
> > > > On Friday 11 Mar 2011
On Mon, 2011-03-14 at 12:22 -0600, Alex Williamson wrote:
> On Sat, 2011-03-12 at 12:57 +, Michael Brown wrote:
> > On Saturday 12 Mar 2011 12:05:53 Michael Brown wrote:
> > > On Friday 11 Mar 2011 18:27:28 Alex Williamson wrote:
> > > > I'm looking to refres
On Sat, 2011-03-12 at 12:57 +, Michael Brown wrote:
> On Saturday 12 Mar 2011 12:05:53 Michael Brown wrote:
> > On Friday 11 Mar 2011 18:27:28 Alex Williamson wrote:
> > > I'm looking to refresh qemu's PXE ROMs with iPXE, but it looks like the
> > > eepr
s for tagging a
release soon? Thanks,
Alex
___
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo/ipxe-devel
On Thu, 2010-12-16 at 04:06 +, Michael Brown wrote:
> On Thursday 16 Dec 2010 03:46:56 Alex Williamson wrote:
> > > igbvf_vf.c does not build:
> > >
> > > drivers/net/igbvf/igbvf_vf.c: In function ‘igbvf_update_mc_addr_list_vf’:
> > > drivers/net/igbvf
On Wed, 2010-12-15 at 16:51 +, Michael Brown wrote:
> On Friday 10 Dec 2010 20:57:21 Alex Williamson wrote:
> > Driver for Intel 82576 based virtual functions, based on Intel source
> > code available at:
> >
> > http://sourceforge.net/projects/e1000 (igb
62 matches
Mail list logo
