search for: af7e95c3

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

...w): _ target/EFI/BOOT/SYSLINUX.CFG _ target/EFI/BOOT/SYSLINUX/EFI64/ldlinux.e64 Before performing the test (the same as I requested in my prior email), please double check that all the syslinux-related files are originated from the following binary packages: _ syslinux-common_6.04~git20171011.af7e95c3+dfsg1-5 _ syslinux-efi_6.04~git20171011.af7e95c3+dfsg1-5 Since you have been mixing binaries from several different sources / builds / versions in your prior attempts / scripts, it is very important that you triple check that the binary files you are using now (in your "target" devi...

...se 2 files that were added by syslinux -i boot.img (right?) > Before performing the test (the same as I requested in my prior email), > please double check that all the syslinux-related files are originated > from the following binary packages: > > _ syslinux-common_6.04~git20171011.af7e95c3+dfsg1-5 > > _ syslinux-efi_6.04~git20171011.af7e95c3+dfsg1-5 > > > Since you have been mixing binaries from several different sources / > builds / versions in your prior attempts / scripts, it is very > important that you triple check that the binary files you are using now &gt...

On Wed, 2018-12-12 at 16:00 -0600, Carl Karsten via Syslinux wrote: > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > > On Tue, Dec 11, 2018 at 9:19 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > > You should be able to

Hi, I am trying to get a UEFI bootable USB. And I am unable to make it working. I have two x86_64 systems and both of them 'hangs' when I choose to boot UEFI from USB. I've created fat32 formated partition with ef00 type. I placed EFI/BOOT there with content of efi64/ distribution, I've created syslinux.cfg and renamed syslinux.efi to BOOTX64.EFI. However, it does just

...get syslinux on UEFI working? > I guess you are in Gentoo. Even if you are not using Debian, you could: 1_ Download the syslinux-related binary packages from the Debian "experimental" (_not_ to be confused with "unstable") repository (currently, "6.04~git20171011.af7e95c3+dfsg1-3") and take: * from the "syslinux-efi" package: usr\lib\SYSLINUX.EFI\efi64\syslinux.efi * from the "syslinux-common" package: usr\lib\syslinux\modules\efi64\ldlinux.e64 2.1_ Copy the new syslinux.efi to the "ESP" of your USB device, under its "E...

...y as far as I can tell. > > We know things are different with efi, but that alone isn't a blocker. > > Have you tried to updating to a newer gnu-efi ? The one included in syslinux is very old. I am using the binaries from https://sources.debian.org/src/syslinux/3:6.04%7Egit20171011.af7e95c3+dfsg1-6/debian/changelog/ > I have one here: https://github.com/joakim-tjernlund/syslinux quick look makes me wonder why it would have newer code: Syslinux GIT repo; master is identical to upstream master http://www.syslinux.org/wiki/index.ph? -- Carl K

...rote: > I guess you are in Gentoo. > > Even if you are not using Debian, you could: > > 1_ Download the syslinux-related binary packages from the Debian > "experimental" (_not_ to be confused with "unstable") repository > (currently, "6.04~git20171011.af7e95c3+dfsg1-3") and take: > > * from the "syslinux-efi" package: > usr\lib\SYSLINUX.EFI\efi64\syslinux.efi > > * from the "syslinux-common" package: > usr\lib\syslinux\modules\efi64\ldlinux.e64 > > > 2.1_ Copy the new syslinux.efi to the "ESP&q...

...nd feedback. And no, I'm not going to just write the ending/working result, in particular when I don't know/understand the new goal. If we don't know what is wrong/failing, then we need "basic" step by step testing (iterations) for troubleshooting. Using 6.04~git20171011.af7e95c3+dfsg1-6 packages from Debian Unstable for all syslinux-related files. target ??? EFI ??? BOOT ??? BOOTX64.EFI ??? LDLINUX.E64 ??? libcom32.c32 ??? libutil.c32 ??? vesamenu.c32 ??? pwd.c32 ??? ls.c32 ??? cat.c32...

...39;t a blocker. > > > > Have you tried to updating to a newer gnu-efi ? The one included in syslinux is very old. > > I am using the binaries from > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsources.debian.org%2Fsrc%2Fsyslinux%2F3%3A6.04%257Egit20171011.af7e95c3%2Bdfsg1-6%2Fdebian%2Fchangelog%2F&amp;data=02%7C01%7CJoakim.Tjernlund%40infinera.com%7C1d50b660417a4c6e2c3f08d66086688e%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C0%7C636802527742019220&amp;sdata=UYyZaxiiKgLpp%2BrdXmZ3UMVRkvTCagf2SZk%2FVtZnGdM%3D&amp;reserved=0 > I cannot tell but I...

...; when I don't know/understand the new goal. prompt.cfg is the Help option from the debian installer boot.img. > > > If we don't know what is wrong/failing, then we need "basic" step by > step testing (iterations) for troubleshooting. > > Using 6.04~git20171011.af7e95c3+dfsg1-6 packages from Debian Unstable > for all syslinux-related files. > > target > ??? EFI > ??? BOOT > ??? BOOTX64.EFI > ??? LDLINUX.E64 > ??? libcom32.c32 > ??? libutil.c32 > ??? vesamenu.c32 > ??? pwd....

On Thu, Dec 6, 2018 at 5:14 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > works with legacy, hangs with efi. > > > > where works is: > > No DEFAULT or UI configuration directive found! > > but enter and ^v make things happen > > > > hangs is: nothing happens, no response from keyboard, have to reboot. > > > > note:

...e are back on track, with updated Debian packages. 0_ Starting from an _original_ (so-called "hd-media") boot.img mounted in "target" (or "$target", or some similar notation), and the version of Syslinux-related packages in the OS should be "6.04~git20171011.af7e95c3+dfsg1-6" or newer. At the moment I'm writing this, the packages are in Debian "Unstable" (repo). Although not all the packages are essential for this procedure, the Syslinux-related packages I'm referring to are, at least: _ extlinux _ isolinux _ pxelinux _ syslinux _ sys...

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

...h updated Debian packages. > > > 0_ Starting from an _original_ (so-called "hd-media") boot.img mounted > in "target" (or "$target", or some similar notation), and the version > of Syslinux-related packages in the OS should be > "6.04~git20171011.af7e95c3+dfsg1-6" or newer. At the moment I'm writing > this, the packages are in Debian "Unstable" (repo). > > Although not all the packages are essential for this procedure, the > Syslinux-related packages I'm referring to are, at least: > > _ extlinux > _ isoli...

...failing when you started this new email thread, which is not the one from boot.img. > > > > > > If we don't know what is wrong/failing, then we need "basic" step by > > step testing (iterations) for troubleshooting. > > > > Using 6.04~git20171011.af7e95c3+dfsg1-6 packages from Debian Unstable > > for all syslinux-related files. > > > > target > > ??? EFI > > ??? BOOT > > ??? BOOTX64.EFI > > ??? LDLINUX.E64 > > ??? libcom32.c32 > > ??? libutil.c32 > &gt...

...g before syslinux code has tried to find the file. > > > > > > > > > > If we don't know what is wrong/failing, then we need "basic" step by > > > step testing (iterations) for troubleshooting. > > > > > > Using 6.04~git20171011.af7e95c3+dfsg1-6 packages from Debian Unstable > > > for all syslinux-related files. > > > > > > target > > > ??? EFI > > > ??? BOOT > > > ??? BOOTX64.EFI > > > ??? LDLINUX.E64 > > > ??? libcom32.c32 &gt...