search for: usbinst

...The used syslinux version is 3.11 for windows. I only have access to an old redhat machine where I got the same error using syslinux 1.52 (yeah, quite old) Any ideas on how to quote the append string or workarounds? kind regards, Bernhard Patsch -------- syslinux.cfg working -------- default usbinst prompt 1 timeout 0 display boot.msg F1 boot.msg F2 general.msg F3 param.msg F4 rescue.msg F7 dogcat.msg label phion kernel bzImage append ks=floppy initrd=initrd.img lang= devfs=nomount ramdisk_size=16384 vmal loc=128M label usbinst kernel bzImage append initrd=initrd.img lang= text devfs=n...

...t; > > > > I'm trying to follow the guids > > > > https://www.syslinux.org/wiki/index.php?title=Install#UEFI > > > > and a ml post - here is what I have so far: > > > > > > > > https://salsa.debian.org/carlfk-guest/ansible/blob/uefiusb/usbinst/uefi/fix_hdmedia.sh > > > > (likely quite a bit of unneeded copies) > > > > > > > > it boots, (good) > > > > Initial menu has no LABEL enries! > > > > > > > > > I have to say that your cfg file(s) are not very clear to me (a...

...s/libutil.c32 ::libutil.c32 ; \ > > > > > > I'm trying to follow the guids > > https://www.syslinux.org/wiki/index.php?title=Install#UEFI > > and a ml post - here is what I have so far: > > > > https://salsa.debian.org/carlfk-guest/ansible/blob/uefiusb/usbinst/uefi/fix_hdmedia.sh > > (likely quite a bit of unneeded copies) > > > > it boots, (good) > > Initial menu has no LABEL enries! > > > I have to say that your cfg file(s) are not very clear to me (at the > time I was reading your script, which by now has been chang...

...e resulting usb stick for my use, and also fix it in a way that can be used to fix the upstream bug. I'm trying to follow the guids https://www.syslinux.org/wiki/index.php?title=Install#UEFI and a ml post - here is what I have so far: https://salsa.debian.org/carlfk-guest/ansible/blob/uefiusb/usbinst/uefi/fix_hdmedia.sh (likely quite a bit of unneeded copies) it boots, (good) Initial menu has no LABEL enries! boot: linux boot linux, but no initrd, but i'm sure once I get the .cfg files worked out that will fall into place. -- Carl K

...; to you in this context? Debian? D-I? The Syslinux Project? Other? > > I'm trying to follow the guids > https://www.syslinux.org/wiki/index.php?title=Install#UEFI > and a ml post - here is what I have so far: > > https://salsa.debian.org/carlfk-guest/ansible/blob/uefiusb/usbinst/uefi/fix_hdmedia.sh > (likely quite a bit of unneeded copies) > > it boots, (good) > Initial menu has no LABEL enries! I have to say that your cfg file(s) are not very clear to me (at the time I was reading your script, which by now has been changed). Could you please post here t...

...ur next report, we might need to perform some minor adjustments. > IOW, if your next test fails, don't worry and report the results as > accurately as possible. > report: using this code: https://salsa.debian.org/debconf-video-team/ansible/blob/05480062710486be6b5f5501f560ce3552e87c99/usbinst/uefi/build_uefi.sh Undef symbol FAIL: memset everything else is the same as before: http://imgr.sytes.net/a/qemu4.png target ??? EFI ? ??? BOOT ? ??? BOOTX64.EFI ? ??? LDLINUX.E64 ? ??? SYSLINUX ? ? ??? EFI64 ? ? ??? cat.c32 ? ? ??? chain.c32 ?...

...ime to keep > these attempts. > > If developers for Syslinux and Debian were to show any minimal (real, > concrete) interest, I would gladly perform the tests and report the > results myself. My goal is uefi support for https://salsa.debian.org/debconf-video-team/ansible/blob/master/usbinst/syslinux.cfg I have achieved it with the recent fix and this script: https://salsa.debian.org/carlfk-guest/ansible/blob/uefiusb/usbinst/uefi/fix_hdmedia.sh Now everything I need works, but I would prefer to push my changes upstream. Which maybe I can do, and we just live with some new bugs exist...

...id=thumb -device > ide-hd,drive=thumb,bootindex=1 > > http://imgr.sytes.net/a/qemu5.png Are we actually dealing with ipxe too in all these tests? > report: > using this code: > https://salsa.debian.org/debconf-video-team/ansible/blob/05480062710486be6b5f5501f560ce3552e87c99/usbinst/uefi/build_uefi.sh > > Undef symbol FAIL: memset Our "third test" was about adding the PATH directive. For some reason, the binary files you are using seem to have some building problem or some kind of corruption. I wonder whether your other device in your qemu line "-d...

...CWD is / not /EFI/BOOT good news: linux boots. bad news: selecting the Help option locks it up - menu is still there and keys don't move highlight or anything. cpu here is the relevant bits of https://salsa.debian.org/debconf-video-team/ansible/blob/61b833ad1a010c4f046ea9d1d8c81679e97671e9/usbinst/uefi/build_uefi.sh + cp /usr/lib/SYSLINUX.EFI/efi64/syslinux.efi target/EFI/BOOT/BOOTX64.EFI + cp /usr/lib/syslinux/modules/efi64/ldlinux.e64 target/EFI/BOOT/LDLINUX.E64 + cp \ /usr/lib/syslinux/modules/efi64/vesamenu.c32 \ /usr/lib/syslinux/modules/efi64/libcom32.c32 \ /usr/lib/syslinux/modules/e...

On Thu, Dec 6, 2018 at 10:00 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > First, I'm confused. In the prior "whole" setup (the one you generated > after my 15 steps, plus one workaround), was/is the basic boot menu at > least "working" when you used the workaround for the buggy PATH > directive when booting in UEFI mode? I mean: > >

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 > ? ???

...t; > > > > > > > > I'm trying to follow the guids > > > https://www.syslinux.org/wiki/index.php?title=Install#UEFI > > > and a ml post - here is what I have so far: > > > > > > https://salsa.debian.org/carlfk-guest/ansible/blob/uefiusb/usbinst/uefi/fix_hdmedia.sh > > > (likely quite a bit of unneeded copies) > > > > > > it boots, (good) > > > Initial menu has no LABEL enries! > > > > > > I have to say that your cfg file(s) are not very clear to me (at the > > time I was reading...

...; > > Are we actually dealing with ipxe too in all these tests? > Hmm? we are dealing with whatever QEMU uses for a boot manager. > > > report: > > using this code: > > https://salsa.debian.org/debconf-video-team/ansible/blob/05480062710486be6b5f5501f560ce3552e87c99/usbinst/uefi/build_uefi.sh > > > > Undef symbol FAIL: memset > > > Our "third test" was about adding the PATH directive. For some reason, > the binary files you are using seem to have some building problem or > some kind of corruption. > > I wonder whether your ot...

On Mon, Dec 3, 2018 at 10:02 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > Now it is just dd, mkfs and copy in the files we need. > > One less thing to worry about keeping versions consistent. > > > > > > I just noticed those 2 files that were added by > > > > syslinux -i boot.img > > > > (right?) > > > >

...gz # Please note it is not "INITRD initrd.gz", # we use absolute paths here too. ### EFI/BOOT/SYSLINUX.CFG end ### the version of my code is here for anyone that wants to get a clean copy: https://salsa.debian.org/debconf-video-team/ansible/blob/e6e02369fad365cbed90f10b8df888fcda87783d/usbinst/uefi/build_uefi.sh > > I know, I know... We don't have a boot menu yet. Patience :). > > For a boot menu, and only when the above configuration actually boots > your kernel+initrd in UEFIx64 mode, we will add some additional > Syslinux files from the 'efi64' subdirec...