Re: [ipxe-devel] UEFI's TPL is not restored caused EXSi 6.5U3 boot failed with iPXE

On 12/06/2020 07:15, JamesWang [王家明] wrote: We encountered a CPU exception problem while booting EXSi 6.5U3 with iPXE.  It is caused by system is running on TPL_CALLBACK level. Fixed in http://github.com/ipxe/ipxe/commit/1832f8a9b Sorry for the delay in moderating the mailing list! Thanks,

Re: [ipxe-devel] iPXE boot failing with the below error

On 23/06/2020 05:59, Sadhana wrote: we are seeing the below error while doing iPXE. Is there any way to clear the memory from pxe mode. PXE> boot t_ftp: _ . Not enough space (http://ipxe.org/310f2089) What size is the

Re: [ipxe-devel] Network driver issues

On 04/06/2020 23:32, Shawn Ward wrote: I am attempting to pxeboot a Proliant m710x Server cartridge in our HP Moonshot 1500 chassis. However, when it runs dhcp I get a ‘waiting for link up on net0 and net1 timeout with an unknown (http://ipxe.org/err/1a086194).’ Then when I try to manually

Re: [ipxe-devel] Enabling pfSense commands...

On 29/04/2020 13:38, Emmit Truth wrote: How can ping become included among the available commands? As per https://ipxe.org/cmd/ping#build_options : "This command is available only when the build option PING_CMD is enabled." Hope that helps, Michael

Re: [ipxe-devel] hardware support

On 07/05/2020 03:21, Feng Guo wrote: so I google the error->https://forum.ipxe.org/showthread.php?tid=17335->https://ipxe.org/appnote/buildtargets->https://ipxe.org/appnote/hardware_drivers 15b3:1018, which is ConnectX-5 VF, is not there, while 15b3:1017(ConnectX-5) is there. I assume the

Re: [ipxe-devel] [sfc] Add PCI ID for Solarflare SFC9120 and Solarflare SFC9140

On 14/07/2020 16:59, LaDerrick H wrote: This patch adds support for 2 Solarflare NICs. Applied, thank you. http://github.com/ipxe/ipxe/commit/78ca890c3 Michael ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org

Re: [ipxe-devel] [ipxe/ipxe] [efi] Restore the TPL to the original one (#113)

@jjohnson42 Thanks for the hints about reproduction via ESXi 7's bootx64.efi. I will try to assemble a test case in qemu that demonstrates the problem. If you have a minimal test case ready to use, that would be really helpful. @huanghe4 What you are describing is not a **root** cause. If

Re: [ipxe-devel] [ipxe/ipxe] [efi] Restore the TPL to the original one (#113)

Neither the code change nor the commit message make any sense to me, sorry. Instead of the commit, could you please provide a way to reproduce your observed problem? Thanks. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub:

Re: [ipxe-devel] [PATCH] [build] Be explicit about -fcommon compiler directive

On 06/05/2020 22:03, Bruce Rogers wrote: gcc10 switched default behavior from -fcommon to -fno-common. Since "__shared" relies on the legacy behavior, explicitly specify it. Signed-off-by: Bruce Rogers Applied, with modification to just specify -fcommon unconditionally (since even older gcc

Re: [ipxe-devel] [ipxe/ipxe] fix EMBED: don't eagerly assign over non-empty value (#115)

What problem is this actually solving? Any variables specified in the `make` command line will override assignments within the Makefile. Building with `make EMBED=...` works with no problems already. -- You are receiving this because you are subscribed to this thread. Reply to this email

Re: [ipxe-devel] https booting

On 22/07/2020 15:13, Daniel P. Berrangé wrote: We could easily define etc/ipxe/https/{ciphers,cacerts} paths in a different format if better suited for iPXE. Libvirt can set the right path depending on whether its booting a VM with EDK2 vs legacy BIOS The most useful for iPXE would probably be

Re: [ipxe-devel] [ipxe/ipxe] Change __divmoddi4 from int64 [unknown] to int64_t (#59)

Merged in http://github.com/ipxe/ipxe/commit/cede0c5ba; thank you! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/ipxe/ipxe/pull/59#issuecomment-661866855___

Re: [ipxe-devel] [ipxe/ipxe] Change __divmoddi4 from int64 [unknown] to int64_t (#59)

Closed #59. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/ipxe/ipxe/pull/59#event-3571314819___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org

Re: [ipxe-devel] [ipxe/ipxe] gensdsk: fix default target (#76)

Closed #76. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/ipxe/ipxe/pull/76#event-3571280770___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org

Re: [ipxe-devel] [ipxe/ipxe] gensdsk: fix default target (#76)

Merged as http://github.com/ipxe/ipxe/commit/4277942ac; thank you. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/ipxe/ipxe/pull/76#issuecomment-661862764___

Re: [ipxe-devel] [ipxe/ipxe] successful wpa handshake (memcmp polarity) (#103)

Closed #103. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/ipxe/ipxe/pull/103#event-3571626809___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org

Re: [ipxe-devel] [ipxe/ipxe] successful wpa handshake (memcmp polarity) (#103)

Good catch; thanks. Pushed the memcmp fix as http://github.com/ipxe/ipxe/commit/0de5e6014 and pushed a simpler fix for the wpa_derive_ptk debug message as http://github.com/ipxe/ipxe/commit/ee2dc525b -- You are receiving this because you are subscribed to this thread. Reply to this email

Re: [ipxe-devel] [ipxe/ipxe] Fix pcbios memory accounting bug (#105)

Closed #105. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/ipxe/ipxe/pull/105#event-3571477118___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org

Re: [ipxe-devel] [ipxe/ipxe] Fix pcbios memory accounting bug (#105)

Looks good; thank you. Merged as http://github.com/ipxe/ipxe/commit/45a0ca6de http://github.com/ipxe/ipxe/commit/6ec33b8d6 Thank you for debugging! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [ipxe-devel] [ipxe/ipxe] Fix typo in comment describing length codes (#121)

Merged as http://github.com/ipxe/ipxe/commit/8bc85ec6f; thanks -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/ipxe/ipxe/pull/121#issuecomment-661914693___

Re: [ipxe-devel] [ipxe/ipxe] IPXE fails to boot CentOS 8 (#122)

Try instead: ``` :centos8m kernel CentOS8.2x64/vmlinuz initrd=initrd.img ks=http://10.1.13.195/Centos8/kickstart-manual initrd CentOS8.2x64/initrd.img boot ``` (i.e. move the kernel command line arguments to the `kernel` line, and remove `ksdevice=bootif`) -- You are receiving this because you

Re: [ipxe-devel] [ipxe/ipxe] Fix a GNUism that FreeBSD's sed(1) cannot deal with (#85)

Closed #85. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/ipxe/ipxe/pull/85#event-3571696996___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org

Re: [ipxe-devel] [ipxe/ipxe] Fix a GNUism that FreeBSD's sed(1) cannot deal with (#85)

Merged as http://github.com/ipxe/ipxe/commit/8d243e65c - thank you! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/ipxe/ipxe/pull/85#issuecomment-661911930___

Re: [ipxe-devel] [ipxe/ipxe] Fix typo in comment describing length codes (#121)

Closed #121. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/ipxe/ipxe/pull/121#event-3571721743___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org

[ipxe-devel] [ipxe/ipxe] file:/ URIs for USB key after loading native USB drivers (#123)

### Description As a user, I want to be able to use the `file:/` URI syntax to refer to local files on a USB key from which iPXE was loaded even if iPXE includes native USB host controller drivers, since I expect this to work regardless of which drivers are included in the build. Using the

Re: [ipxe-devel] [ipxe/ipxe] [efi] Restore the TPL to the original one (#113)

@JamesWangAmiTw The timer callback function is `efi_tick()`, not `efi_currticks()`. The timer event controlled by `efi_tick_startup()`/`efi_tick_shutdown()` does not execute the code in `efi_currticks()`. There should not be any code path that leads to `efi_currticks()` while at

Re: [ipxe-devel] ipxe issue with http server permission denied

On 14/12/2020 13:25, Yi Yi3 Liang wrote: I have encountered a problem and need to ask you in the process of setting up the ipxe environment,and this problem is described as follows: The permission denied during ipxe boot due to my http server(Nginx for ubuntu) comes with username and password

Re: [ipxe-devel] EFI TPL for efi_currticks()

On 08/12/2020 16:22, Petr Borsodi wrote: why efi_currticks function restores the TPL to an "external" TPL (especially TPL_APPLICATION) and raises it back to TPL_CALLBACK? This would not be necessary if the timer used TPL_NOTIFY for its event. There are other system timers that may be

Re: [ipxe-devel] Custom syslog port

On 18/11/2020 11:46, Michael Schaller wrote: Michael, a syslog URI sounds like a good idea to me. I'm not aware of any RFC other than https://tools.ietf.org/html/draft-lear-ietf-syslog-uri-00, which proposes a rather odd URI syntax IMHO. Others seem to use URIs like `[tcp/udp]://host:port` or

Re: [ipxe-devel] Custom syslog port

On 12/11/2020 12:56, Michael Schaller wrote: We do automated installation testing for a whole array of different hardware models (similar to https://autotest.github.io/). Each machine logs to a dedicated syslog endpoint so that we have one dedicated log per installation attempt per machine. We

Re: [ipxe-devel] Custom syslog port

On 17/11/2020 20:44, Geert Stappers wrote: On Tue, Nov 17, 2020 at 08:17:35PM +0100, Michael Schaller wrote: On Tue, Nov 17, 2020 at 6:08 PM "Please elaborate" wrote: On Tue, Nov 17, 2020 at 05:54:04PM +0100, Michael Schaller wrote: So are there any comments or opinions on this feature

Re: [ipxe-devel] Custom syslog port

On 12/11/2020 11:46, Michael Schaller wrote: We use a central syslog service that provides syslog endpoints on a per-host basis with a random port per endpoint. How hard would it be to add an iPXE setting that allows to configure the syslog port? Something like `set syslog-port PORT` or `set

Re: [ipxe-devel] chain http and "slow" network interfaces

On 24/11/2020 20:13, Etienne Champetier wrote: To work around situations where we can't run DHCP or ProxyDHCP, we build a simple iPXE iso that loop on all interfaces and try to chain to a predefined local link IPv6. It works well until on some server the interface takes ~40s to transmit anything

Re: [ipxe-devel] Install Windows 10 via http

On 03/02/2021 12:02, pat...@chojecki.it wrote: Sorry for the poor english, but I have a problem with the ipxe configuration via http, on disk less client https://ipxe.org/howto/winpe I can install Windows 10 Enterprise LTSC 2019, but I can't install other Windows. Im check Windows 10

Re: [ipxe-devel] [ipxe/ipxe] enable bin/ipxe.iso target to build on FreeBSD (#42)

@mcb30 commented on this pull request. > @@ -95,6 +95,8 @@ SYSLINUX_DIR_LIST := \ /usr/share/syslinux/modules/bios \ /usr/local/share/syslinux \ /usr/local/share/syslinux/bios \ + /usr/local/share/syslinux/bios/core \ +

Re: [ipxe-devel] [ipxe/ipxe] enable bin/ipxe.iso target to build on FreeBSD (#42)

@mcb30 commented on this pull request. > @@ -58,19 +58,19 @@ NON_AUTO_MEDIA+= iso %iso: %lkrn util/geniso $(QM)$(ECHO) " [GENISO] $@" $(Q)ISOLINUX_BIN=$(ISOLINUX_BIN) LDLINUX_C32=$(LDLINUX_C32) \ - VERSION="$(VERSION)" bash util/geniso -o $@ $< +

Re: [ipxe-devel] [ipxe/ipxe] enable bin/ipxe.iso target to build on FreeBSD (#42)

@mcb30 commented on this pull request. > @@ -120,7 +120,7 @@ case "${LEGACY}" in ;; 0) # copy isolinux bootloader - cp ${ISOLINUX_BIN} ${dir} + install -m 644 ${ISOLINUX_BIN} ${dir} Merged (in the replacement `util/genfsimg`)

Re: [ipxe-devel] [ipxe/ipxe] enable bin/ipxe.iso target to build on FreeBSD (#42)

This has been forward-ported and merged as https://github.com/ipxe/ipxe/commit/9557497e7 and https://github.com/ipxe/ipxe/commit/25b675c3d Thank you! -- You are receiving this because you commented. Reply to this email directly or view it on GitHub:

Re: [ipxe-devel] [ipxe/ipxe] enable bin/ipxe.iso target to build on FreeBSD (#42)

Closed #42. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/ipxe/ipxe/pull/42#event-4268487577___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org

Re: [ipxe-devel] A couple of compile issues

On 17/06/2021 11:36, Dean Westhead wrote: Is it still necessary to make these mods or is the ability to build a single ISO that will boot EFI and non EFI machines now part of the master branch ? This is now present in the master branch. You can build an EFI .iso in what is hopefully the most

Re: [ipxe-devel] A couple of compile issues

On 17/06/2021 13:50, Michael Brown wrote: Even with a clean download ( before any of my messing about with it ! ), i am getting compile errors with a basic make : ar: creating bin/blib.a objcopy: invalid option -- 'D' This is a known issue introduced just a few days ago by commit https

Re: [ipxe-devel] 486 with a Realtek 8139

On 05/05/2021 20:13, Michael Brown wrote: For unlzma.S, just changing to ".arch i486" is fine, since there are no 586-class instructions in that file. For undinet.c, the "rdtsc" instructions are used only for profiling. It's probably not worth the marginally increased

Re: [ipxe-devel] 486 with a Realtek 8139

On 07/05/2021 00:20, Nikolai Zhubr wrote: I appologise for bugging you with ancient etherboot, please ignore if it is too much off topic. I'm just not sure how to proceed yet. I'm pleased that you managed to get something working, but just to be clear: there is zero chance of any changes

Re: [ipxe-devel] 486 with a Realtek 8139

On 05/05/2021 19:53, Nikolai Zhubr wrote: Thanks for mentioning Bochs, I've copied your 486 config commandline and was able to build and start testing. Its way more handy than with real iron. It is even possible to disable e820 function by hand. Now as long as 586+ requirement is not really

Re: [ipxe-devel] 486 with a Realtek 8139

On 16/05/2021 21:04, Michael Brown wrote: On 16/05/2021 21:04, Nikolai Zhubr wrote: Ok, no need for a floppy actually. Apparently the "boot partition" method is still usable as long as disk partitioning was performed carefully (I ran Msdos' fdisk utility on this same board to add a

Re: [ipxe-devel] 486 with a Realtek 8139

On 15/05/2021 22:56, Nikolai Zhubr wrote: One note is that I had to compile using the default ancient system gcc compiler with: "make -j1 bin/10ec8139.kpxe EMBED=chain.ipxe" where gcc says: gcc (SUSE Linux) 4.8.3 An attempt to cross-compile using my preferred 486 toolchain with gcc 7.5 fails

Re: [ipxe-devel] 486 with a Realtek 8139

On 16/05/2021 10:00, Nikolai Zhubr wrote: I have to correct myself. The documentation does exist (online), however for me as a user it is arranged in a very unexpected manner, and it confuses to a surprisingly high degree. First, the material goes all upside-down: command line goes before

Re: [ipxe-devel] 486 with a Realtek 8139

On 16/05/2021 21:04, Nikolai Zhubr wrote: Ok, no need for a floppy actually. Apparently the "boot partition" method is still usable as long as disk partitioning was performed carefully (I ran Msdos' fdisk utility on this same board to add a partition so as to avoid possible conflicts with

[ipxe-devel] IRC channel migration

Along with most of the rest of the world, the #ipxe IRC channel has migrated from Freenode to Libera.Chat. I'll maintain a presence in both for the next few weeks, but would encourage people to gradually migrate across whenever convenient. There is also now a Matrix room #ipxe:matrix.org

Re: [ipxe-devel] 486 with a Realtek 8139

On 05/05/2021 07:54, Martin Habets wrote: Long ago Etherboot used to be i386 code. Nowadays I think iPXE only runs on i586 or later, e.g. arch/x86/prefix/unlzma.S has: .arch i586 From memory there are a couple of places in the code where iPXE uses assembler opcodes that don't exist in

Re: [ipxe-devel] Install Windows 10 via http

On 05/02/2021 12:54, pat...@chojecki.it wrote: Hi, I have next problem. I can't install upgrade 1809+ What I do wrong? How I can upgrade OS? Congratulations; it looks as though you have solved all of your iPXE-related issues. Your system is successfully booting via iPXE from an iSCSI

Re: [ipxe-devel] autoexec.ipxe and UEFI secure boot ?

On 04/04/2021 16:42, Etienne Champetier wrote: Since https://github.com/ipxe/ipxe/commit/a3f1e8fb6707811e6eb90e339d7ebe813fd89a63, iPXE load autoexec.ipxe from filesystem allowing pretty much the same use case as embedding configuration without the need to recompile iPXE binary. Now I'm

Re: [ipxe-devel] Diskless Cilent Centos via iSCSI

On 12/02/2021 07:04, pat...@chojecki.it wrote: I have another problem with install CentOS 7 I try install CentOS on iSCSI target,I Can't install partition /boot on iSCSI target. The problem arises from: i instaled centos from cd You need to perform an installation via the network, with

Re: [ipxe-devel] Diskless Cilent Centos via iSCSI

On 15/02/2021 19:16, brent s. wrote: On 2/12/21 11:43, Oliver Rath wrote: Ist there something appropriate for Debian/Ubuntu? For e.g. Focal release of Ubuntu, you would use this URL base (make sure the initramfs and kernel filenames are the same, I didn't check):

Re: [ipxe-devel] [PATCH] [ath5k] Add missing AR5K_EEPROM_READ in ath5k_eeprom_read_turbo_modes

On 16/02/2021 18:29, Bruce Rogers wrote: The GCC11 compiler pointed out something that apparently no previous compiler noticed: in ath5k_eeprom_pread_turbo_modes, local variable val is used uninitialized. From what I can see, the code is just missing an initial AR5K_EEPROM_READ. Add it right

Re: [ipxe-devel] Diskless Cilent Centos via iSCSI

On 12/02/2021 16:43, Oliver Rath wrote:   https://ipxe.org/howto/rh_san Maybe it is interesting to know, that the path for RH Centos  *8* (instead of 7) changed to http://mirror.centos.org/centos/8/BaseOS/x86_64/os/images/pxeboot/ Thanks. I've updated the documentation to use this

Re: [ipxe-devel] [edk2-devel] EfiRom vs. iPXE usability note

On 19/02/2021 17:33, Laszlo Ersek wrote: The PCI Firmware Spec does not seem to specify a particular "checksum byte" in the option ROM format, it only seems to state that the bytes in the option ROM must sum to zero. This (apparently) allows option ROM providers to implement different schemes

Re: [ipxe-devel] [SPAM] Connection is not working

On 19/02/2021 17:22, Klaus Falke wrote: Hi, why this is not working: image *What I can do to fix it?* First: please update your version of iPXE. The version you are using is from 2013(!) or earlier since it predates commit https://github.com/ipxe/ipxe/commit/26b87b221 Once you have

Re: [ipxe-devel] Allow user to edit a kernel command line before booting with a read timeout

On 23/04/2021 11:46, Matteo Guglielmi wrote: Would it be possible to ask for a read --timeout option in order to automate the following script (unattended boot)? set cmdline selinux=0 console=ttyS0,115200n8 console=tty0 echo -n Kernel command line: ${} read --timeout 5 cmdline chain

Re: [ipxe-devel] read function issue (string: 256 char limit?)

On 09/09/2021 08:48, Matteo Guglielmi wrote: Would it be possible to extend the size limit of 256 characters of the read function? Should be increased to 1024 in https://github.com/ipxe/ipxe/commit/2265a6519 Thanks, Michael ___ ipxe-devel

Re: [ipxe-devel] Generating a BIOS/UEFI hybrid ISO image

On 07/10/2021 09:43, Dean Westhead wrote: I have checked the files in the two ISO's ( one generated from the old geniso and one from teh new genfsimg ), and the files in them are very different. Merely saying that they "are very different" does not really give me any useful information with

Re: [ipxe-devel] Generating a BIOS/UEFI hybrid ISO image

On 07/10/2021 14:52, Dean Westhead wrote: Sorry ... I didnt want to take lots of your time if it is only me having this issue and everyone else is working fine. In the old "working" ISO, there is the following files : boot.cat efiboot.img ipxe.krn isolinux.bin isolinux.cfg The new one that

Re: [ipxe-devel] Generating a BIOS/UEFI hybrid ISO image

On 05/10/2021 09:38, Dean Westhead wrote: I may be missing something, but since the commit changed the file src/util/geniso to src/util/genfsimg, I have not been able to generate an ISO file that can be used to boot both BIOS and UEFI ... it always only boots BIOS. I admit that the changes

Re: [ipxe-devel] Generating a BIOS/UEFI hybrid ISO image

On 05/10/2021 15:18, Dean Westhead wrote: Yes ... that is what i have been trying and failing ! hehe ! it all "makes" without any errors and after installing the xorriso package the genfsimg runs without any errors too. The only problem is that the outputted combined.iso will not boot a

Re: [ipxe-devel] Does imgextract keep writing to same named location by design?

On 11/03/2022 16:44, John Hanks wrote: I am using imgextract to download several images, like so imgextract --name one http://master/one.img imgextract --name two http://master/two.img imgextract --name three http://master/three.img

Re: [ipxe-devel] iPXE working on 486(386?) hardware, hanging on init_librm

On 30/01/2022 22:03, Nikolai Zhubr wrote: For iPXE this fix is unnecessary but still last time I tried iPXE would hang on 486 for some reason. At least one part of this problem should now be fixed: https://github.com/ipxe/ipxe/commit/bc35b24e3 This was a fun problem to debug! Michael

Re: [ipxe-devel] iPXE working on 486(386?) hardware, hanging on init_librm

On 02/02/2022 15:52, Nikolai Zhubr wrote: https://github.com/ipxe/ipxe/commit/bc35b24e3 This was a fun problem to debug! Oh, nice. The commit log was an entertaining reading! I'll try to re-test it on some 486 as time permits later. Now as the effect appeared to be still clearly algorythmic

Re: [ipxe-devel] [ipxe/ipxe] Fixed bug in intel 10M/100M/1G NIC driver. (#52)

Closed #52. -- Reply to this email directly or view it on GitHub: https://github.com/ipxe/ipxe/pull/52#event-6052904769 You are receiving this because you commented. Message ID: ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org

Re: [ipxe-devel] [ipxe/ipxe] Fixed bug in intel 10M/100M/1G NIC driver. (#52)

This was cleaned up into commit https://github.com/ipxe/ipxe/commit/2d79b20f2 -- Reply to this email directly or view it on GitHub: https://github.com/ipxe/ipxe/pull/52#issuecomment-1036448623 You are receiving this because you commented. Message ID:

Re: [ipxe-devel] [ipxe/ipxe] QRcode (#102)

> @NiKiZe Thanks! I tried a few things but it seems that im unable to get the > UCS-2 or 2byte char working for the ISO10646 charset. iPXE is currently ASCII-only. I am currently working on adding Unicode support in stages. The first part (allowing the use of UTF-8 in iPXE scripts, allowing

Re: [ipxe-devel] ipxe.org OSCP server check

On 03/09/2023 11:11, Geert Stappers via ipxe-devel wrote: When I do wget http://ca.ipxe.org/cross-ca.crt && \ wget https://ca.ipxe.org/ca.crt && \ openssl x509 -in cross-ca.crt -ocsp_uri -noout && \ openssl ocsp -issuer ca.crt -cert cross-ca.crt -text -url

Re: [ipxe-devel] ipxe.org OSCP server issues?

On 21/08/2023 18:57, Geert Stappers via ipxe-devel wrote: On Mon, Nov 26, 2018 at 03:26:20PM +, Michael Brown wrote: On 15/11/2018 21:21, Stephen Soltesz wrote: Are there any known issues with the ipxe.org <http://ipxe.org> OSCP servers? Yesterday I was able to boot a test

Re: [ipxe-devel] Issues with Broadcom NICs in Dell R7625

On 19/01/2023 16:48, Thomas Walker via ipxe-devel wrote: First off, I want to say thank you, the work done 2 years ago (https://github.com/ipxe/ipxe/commit/988d2c13cdf0f0b4140685af35ced70ac5b3283c) to fix walking through multiple instances of EFI_PCI_ROOT_BRIDGE_IO_PROTOCOL worked like a

Re: [ipxe-devel] Issues with Broadcom NICs in Dell R7625

On 20/01/2023 13:54, Thomas Walker wrote: Anyway, I can move forward here. I have no intention of ever needing to PXE off of bnxt, so I can leave it out. And the "legacy NIC wrapper" warning appears to be cosmetic. But I'm willing to debug further if that is helpful since I know you don't

Re: [ipxe-devel] REG: Query on 9K MTU Testing flow

On 13/03/2023 21:31, Michael Brown via ipxe-devel wrote: There is what looks like a bug when using DHCP to change MTU: the change of MTU requires the interface to be closed and reopened, but closing the interface will cause the initiating DHCP transaction itself to be aborted. This probably

Re: [ipxe-devel] REG: Query on 9K MTU Testing flow

On 13/03/2023 03:16, MohamedShah R via ipxe-devel wrote: 1. If our device configures netdev->mtu as 1500  and netdev->max_pkt_len is 9128(above 9k). 2. If the DHCP server sends MTU size as 9K.    As per the code walk-through, I understand that this api "staticintapply_netdev_settings”

Re: [ipxe-devel] REG: Query on 9K MTU Testing flow

On 13/03/2023 17:48, MohamedShah R wrote: Hi Michael,  Thanks for your response. Below is the flow- I have seen in the execution- it hits the intf_close as part of netdev_close called from apply_netdev_settings,.

Re: [ipxe-devel] linux16 /ipxe.lkrn output

On 19/02/2023 21:29, Geert Stappers via ipxe-devel wrote: What output to expect from ipxe.lkrn ( downloaded from https://boot.ipxe.org ) when started from grub? You should see the same output as when ipxe.lkrn is started from any other method, e.g.: iPXE initialising devices...ok iPXE

Re: [ipxe-devel] IPv6 DHCP Behavior

On 03/04/2023 09:54, Andreas Fink wrote: so which fileame or url is being used if both answers? the one which answers first (which would be unpredictable order) If your network boot servers provide conflicting responses for the boot URL, then the behaviour is undefined. Michael

Re: [ipxe-devel] IPv6 DHCP Behavior

On 03/04/2023 08:39, Ramesh Soni -X (ramsoni - Altran ACT S.A.S at Cisco) via ipxe-devel wrote: We have both DHCPv4 and DHCPv6 running on same iPXE server. Our box is running iPXE code for downloading the image from ipv6, we have made entry in ipxe server dhcpd6.conf file for this box. First

Re: [ipxe-devel] REG: Query on 9K MTU Testing flow

On 14/03/2023 16:45, MohamedShah R wrote: Thanks for the quick response. I am new to the PXE source code and tried out the below changes  for the experimental testing in the netdev_close api and it works fine. Why can't we have a new api netdev_reopen() which does the same logic of

Re: [ipxe-devel] IPv6 DHCP Behavior

On 05/04/2023 08:14, Ramesh Soni -X (ramsoni - Altran ACT S.A.S at Cisco) wrote: Thanks, Michael, for your response. We have not provided the boot filename in DHCPv4 so it is picking the file from DHCPv6. Although we are seeing some inconsistent behaviour here. We are seeing sometime DHCP

[ipxe-devel] iPXE and Secure Boot

Dear all, I'm in the process of trying to get a UEFI shim signed so that we are able to provide iPXE binaries that can be booted on a system with UEFI Secure Boot enabled. As part of the shim submission process, I need to create a PGP key (having never previously found a need for one), and

Re: [ipxe-devel] iPXE and Secure Boot

On 13/02/2023 21:05, Alex Chernyakhovsky wrote: Where are you located geographically? Debian Developers are by-design well connected within the PGP web of trust, and there are likely folks that would be happy to meet you and sign your keys. The WoT is somewhat fickle in terms of the bars

Re: [ipxe-devel] commit 3ef4f7e2ef4a22ea1e2eccc72957d7bf3fe2f945 breaks "prompt --key" command

umentation, I was able to bisect it to the following commit: commit 3ef4f7e2ef4a22ea1e2eccc72957d7bf3fe2f945 Author: Michael Brown Date:   Tue Jul 4 14:31:07 2023 +0100 I build iPXE on Debian Bullseye amd64. The resulting binary (.iso) was booted on a Qemu VM, also amd64 architecture. J

Re: [ipxe-devel] commit 3ef4f7e2ef4a22ea1e2eccc72957d7bf3fe2f945 breaks "prompt --key" command

On 07/07/2023 14:10, Michael Brown via ipxe-devel wrote: On 07/07/2023 09:32, Sven Dreyer via ipxe-devel wrote: I just noticed that my iPXE script containing a line "prompt --key 0x197e [..]" stopped working. Pressing F12 acted like I was pressing a different key. This worked in my

<    7   8   9   10   11   12