similar to: Bug#988477: xen-hypervisor-4.14-amd64: xen dmesg shows (XEN) AMD-Vi: IO_PAGE_FAULT on sata pci device

On 8 Nov 2019 at 0:42, Ady Ady via Syslinux wrote: > > As usual, builds/versions should not be mixed, at least within the same > platform (bios/ia32/x64). > I keep versions strictly separated. Both the build directories under /usr/src/syslinux-<VERSION>, and under /tftpboot/pxelinux/<VERSION>/efi64/<my data> and I flip the "filename" and

On 6/6/19 8:16 AM, Ady Ady via Syslinux wrote: > >> the PXELINUX log line is >> printed (PXELINUX 6.04 lwIP 6.04-pre3 Copyright (C) 1994-2015 H. Peter >> Anvin et al), > > (snip) > > FWIW, the official binaries from 6.04-pre2 and 6.04-pre3 are not good > for troubleshooting. > > Is the same behavior present when testing with other versions? I would

Dear gentlemen, I think I'd better start another thread for this... thanks to Ady Ady and Gregory Lee Bartholomew for their responses to my early question. Just for the record, my fresh experience with PXElinux 6.x follows: syslinux.efi version 6.03 does boot to the extent that it shows a prompt, but if I provide it with a CFG file containing several labels, no matter what label I type

On Sat, Jan 20, 2024 at 12:21:37AM +0100, marki via Syslinux wrote: > Hello, > > So I'm running syslinux.efi > Which loads menu.c32 > Which is supposed to start ESXi's bootx64.efi/mboot.efi > > But that gives > > """ > Loading mboot.efi... ok > Invalid Boot signature 0x2, bailing out > Booting kernel failed: Bad file number >

If they are useful, then one should note where they can be found and how to extract them for anyone not using a Debian-based distro. Saying just that they are in the Debian Testing repo, doesn't mean much to a non-Debian-er... On Thu, Nov 14, 2019 at 09:50:40PM +0000, Ady Ady via Syslinux wrote: > > Do note that not everyone is running a Debian based system, > > so "the

On 1/20/2024 1:29 AM, Ralph Ronnquist via Syslinux wrote: > On Sat, Jan 20, 2024 at 12:21:37AM +0100, marki via Syslinux wrote: >> Hello, >> >> So I'm running syslinux.efi >> Which loads menu.c32 >> Which is supposed to start ESXi's bootx64.efi/mboot.efi >> >> But that gives >> >> """ >> Loading mboot.efi... ok

Hello, So I'm running syslinux.efi Which loads menu.c32 Which is supposed to start ESXi's bootx64.efi/mboot.efi But that gives """ Loading mboot.efi... ok Invalid Boot signature 0x2, bailing out Booting kernel failed: Bad file number """ Secure boot is disabled. Thoughts? The reason why it would be nice using PXE and syslinux here is because we have

Hi, i'm possibly not the best source of general SYSLINUX knowledge, as my interest in it is only with my xorriso hat on. (As you can see in the SYSLINUX wiki, xorriso can do the isohybridization without the need for the isohybrid program.) Fulalas Caos wrote: > I tried this: > mkisofs -o "$ISONAME" -v -l -J -joliet-long -R -D -A "$CDLABEL" \ > -V

Hello, On Debian, I've hit a bit of an issue with the 32-bit EFI support where the ELF loader failed to load the ldlinux.e32 file. The issue occurs in com32/lib/sys/module/i386/elf_module.c in the load_segments() function, particularly when iterating through the module's program headers and loading the PT_LOAD ones. The code hits a program section which has a zero on-disk size, the

tags 988477 - moreinfo found 988477 4.17.2+76-ge1f9cb16e2-1~deb12u1 affects 988477 src:linux severity 988477 critical quit I am also observing #988477 occur. This machine has a AMD Zen 4 processor. The first observation was when motherboard/processor was swapped out, the older motherboard/processor was several generations old. The pattern which is emerging is Linux MD RAID1 plus recent AMD

found 988477 4.17.3+10-g091466ba55-1~deb12u1 severity 988477 critical quit Justification is same as original, data loss. I'm unsure about of the border between "data loss" and "serious data loss" is, but the original reportter declared it so and I don't disagree. On Sun, Aug 25, 2024 at 11:41:44PM +0200, Maximilian Engelhardt wrote: > I am changing the severity

Hi hpa, Ady, hpa at zytor.com (H. Peter Anvin) writes: > On 6/6/19 8:16 AM, Ady Ady via Syslinux wrote: >> >>> the PXELINUX log line is >>> printed (PXELINUX 6.04 lwIP 6.04-pre3 Copyright (C) 1994-2015 H. Peter >>> Anvin et al), >> >> (snip) >> >> FWIW, the official binaries from 6.04-pre2 and 6.04-pre3 are not good >> for

Hello everybody, I am looking for the efi64/syslinux.efi with IP support like the bios/lpxelinux.0 version has. I am using debian buster with: syslinux-efi 3:6.04~git20190206.bf6db5b4+dfsg1-1 all collection of bootloaders (UEFI bootloader) Thank you in advance, Kind regards, Jelle de Jong

Hello everybody, I been using lpxelinux.0 with legacy boot to load KERNEL over http instead of tftp and I want to switch to efi boot. Thank you for the great tech! However it seems the syslinux.efi does not support HTTP / IP? How can I get efi boot load syslinux with an IP stack? # dpkg -S /usr/lib/SYSLINUX.EFI/efi64/syslinux.efi syslinux-efi: /usr/lib/SYSLINUX.EFI/efi64/syslinux.efi # dpkg

On 7/18/19 10:30 AM, Michael Stapelberg via Syslinux wrote: >>> >>> Is the same behavior present when testing with other versions? I would >>> suggest trying 6.04-pre1, and/or the binaries from Debian Sid / >>> Unstable (which are more up-to-date than official upstream 6.04-pre1). >>> Please note that you need to replace _all_ binaries (e.g. *.c32),

On Sat, Dec 1, 2018 at 2:46 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > it works. (boots into the d-i installer, I don't care if the installer > > is missing stuff, booting it is all we care about here. > > > OK, so let's add complexity (but not the whole thing, not yet). > > We already have: > > target > ??? EFI > ? ???

On Fri, Mar 14, 2025 at 10:42:24PM +0100, Maximilian Engelhardt wrote: > A fix [1] for the IO_PAGE_FAULT went into xen 4.20 which is now available in > testing and unstable. > The 4.20.0-1 Debian source package can also be compiled for bookworm if you > have a bookworm system running and want to test there. Please not that qemu > also needs to be recompiled for this xen version

xen source: lintian output: 'license-problem-gfdl-invariants stubdom/grub.patches/00cvs invariant part is: with no invariant sections, with the front-cover texts being a gnu manual, and with the back-cover texts as in (a) below', automatically rejected package. xen source: If you have a good reason, you may override this lintian tag. xen-utils-4.11: lintian output:

Hi, I'm trying to create a samba4.0.1-package for ubuntu12.4. It seems as if I've succeeded to resolve the dependencies and everything is compiling and linking just fine until it switches to the source4 directory. There I always get these kerberos/heimdal-related linker-errors: default/source3/libads/kerberos_57.o: In function

Hello, I have a strange issue with Samba 4 as an AD DC regarding GPO creation. I use the following packages on Debian wheezy: dpkg -l | grep samba ii libsamba-credentials0:i386 4.0.0+dfsg1-1 i386 Samba Credentials management library ii libsamba-hostconfig0:i386 4.0.0+dfsg1-1 i386 Samba host configuration library ii