search for: syslinx

All, To me, 6.03 is looking good. Really good!! I'm doing a presentation for a local Linux Fest, about building a lab PXE server. One topic is the new native support in pxelinux for UEFI-based PXE. As you know, previously you had to use the hybrid approach of using pxelinux.0 for BIOS boot and grub2 for UEFI boot. So you had to maintain two different boot menus with slightly different

...work for both UEFI resp. BIOS PXE ? > > BIOS PXE always enters execution at the first byte. UEFI uses a PE32+ > image format. The PE32 header starts with the string "MZ" which > doesn't bode well for this idea. > Yes, that seems a bit difficult. What about booting syslinx from GRUB2 UEFI ? that is instead of PXE boot from BIOS I want grub to start some syslinux binary that continues behaves like PXE boot. I want to automatise the PXE boot so I can initiate one by rebooting into GRUB go from there Jocke

Hey Guys, Below is a patch for the com32/rosh/rosh.c from tonights syslinx git. The patch does the following: 1) changes the rosh_issp to use an if instead of a case for this simple test. 2) changes the rosh_dir_arg function to move the readdir() to inside the while test. This will let me go through my APUE book. Let me know if you have any questions. Keith --- ro...

Hey, i'm using latest Syslinx 6.01 and try to get the linux kernel booted via tftp in EFI mode. My menu entry: LABEL rescue64 MENU LABEL ^1. 64-Bit Rescue-System - wheezy - 3.10.2 LINUX /rescue/dev-64/vmlinuz INITRD /rescue/dev-64/initramfs.cpio.gz APPEND ... If i select the entry i get: "Bad file number!"....

...ous other possibilities). I'm also doing a bit of editing as I go with the goals of being correct, complete, clear and concise, including new and deprecated behavior with version numbers noted as there is quite the wide variation in versions used (although I've never heard of someone using Syslinx older than 3.00). My thought here is that if someone is accustomed to older behavior, this would facilitate them updating to the new behavior. Looking at doc/syslinux.txt, there are numerous basic sections. My main question is: Should any of these be regrouped into different documents? Aspects...

> What about booting syslinx from GRUB2 UEFI ? > that is instead of PXE boot from BIOS I want grub to start some syslinux binary that > continues behaves like PXE boot. > I want to automatise the PXE boot so I can initiate one by rebooting into GRUB go from there > > Jocke @Jocke, I could be wrong but... Yo...

...for normal startup! For help press the <F2> key. ...the LSS16 image is also supposed to display, but doesn't. So far so good, but now comes the UEFI part... This is where I become a bit confused. In the first partition, I created /EFI/BOOT directories, and copied these from /usr/share/syslinx/efi64: ldlinux.e64 linux.c32 syslinux.c32 syslinux.efi I then copied syslinux.efi to BOOTX64.EFI However, I read that syslinux.efi expects to find syslinux.cfg in the same directory, so I copied *everything* from the / root directory into /EFI/BOOT, even vmlinuz. Lots of redundancy here! Any adv...

...t, attempted to use the UseDefaultAddress flag, failed to > configure, and fell back to attempting to manually configure the > entire UDP datagram. At this point, it should have just worked. Have you figured out why it failed yet? I never saw any printouts for netmask/gateway, are you sure syslinx got those? Not on the same network so gateway must work for me. > > The aliases/names aren't entirely standardized and it's just a > friendly name for the GUID (which is standardized). The aliases could > easily be localized though I believe there's only 2 common groups,...

...> Could you please confirm? It did show the boot menu, I can use the arrow keys to navigate the menu, I can select the installer and it runs If I select "Help" and enter, or tab and enter, it hangs. help, tab, enter hang: http://imgr.sytes.net/a/qemu_b3.png And.. in trying to verify syslinx version, I have found another hang: efi boot, see menu, hit ^c, hung. legacy boot, ^c gets me a boot: prompt. > > > Regarding the "prompt.cfg" you are now trying to investigate (which is > not the one in boot.img), the following is (potentially) the first in a > series of...

...UseDefaultAddress flag, failed to >> configure, and fell back to attempting to manually configure the >> entire UDP datagram. At this point, it should have just worked. > > Have you figured out why it failed yet? > I never saw any printouts for netmask/gateway, are you sure syslinx got those? > Not on the same network so gateway must work for me. > >> >> The aliases/names aren't entirely standardized and it's just a >> friendly name for the GUID (which is standardized). The aliases could >> easily be localized though I believe there...

...helping me point to a problem, http://www.syslinux.org/archives/2013-April/019817.html which turned out to be a bug, http://www.syslinux.org/archives/2013-April/019822.html So you cannot blame me for expecting the same patience, expertise and help in troubleshooting this new problem first with Syslinx and, if need be, later with ArchLinux. _As an example_, we might discover ArchLinux do not have the latest UEFI files/docummentation from you. So please bear with me for the time being. 2. >> In BIOS, select ArchLinux entry > Just a minor detail (but it helps for understanding each other...

...And we already expected this issue, as per recent emails in this Syslinux Mailing List. > > So far so good, but now comes the UEFI part... > > This is where I become a bit confused. In the first partition, I > created /EFI/BOOT directories, and copied these from > /usr/share/syslinx/efi64: > ldlinux.e64 linux.c32 syslinux.c32 syslinux.efi You don't seem to be needing syslinux.c32. Strictly speaking, you also don't seem to need linux.c32 (from efi64). > > I then copied syslinux.efi to BOOTX64.EFI > > However, I read that syslinux.efi expects to fin...

On Wed, 2018-12-12 at 17:10 -0600, Carl Karsten 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 Wed, Dec 12, 2018 at 4:54 PM Joakim Tjernlund > <Joakim.Tjernlund at infinera.com> wrote: > > > While I am here, I want to ask: >

...how the boot menu, > I can use the arrow keys to navigate the menu, > I can select the installer and it runs > If I select "Help" and enter, or tab and enter, it hangs. > > help, tab, enter hang: > http://imgr.sytes.net/a/qemu_b3.png > > And.. in trying to verify syslinx version, I have found another hang: > efi boot, see menu, hit ^c, hung. > legacy boot, ^c gets me a boot: prompt. > If you want to test whether the "help" files work, you select the relevant row and press enter. I don't know why you would press tab, ^c and then enter f...

...issue, as per recent emails in this > Syslinux Mailing List. > >> >> So far so good, but now comes the UEFI part... >> >> This is where I become a bit confused. In the first partition, I >> created /EFI/BOOT directories, and copied these from >> /usr/share/syslinx/efi64: >> ldlinux.e64 linux.c32 syslinux.c32 syslinux.efi > > You don't seem to be needing syslinux.c32. Strictly speaking, you > also don't seem to need linux.c32 (from efi64). Thanks for that info. >> >> I then copied syslinux.efi to BOOTX64.EFI >> >&...

...the arrow keys to navigate the menu, > > I can select the installer and it runs > > If I select "Help" and enter, or tab and enter, it hangs. > > > > help, tab, enter hang: > > http://imgr.sytes.net/a/qemu_b3.png > > > > And.. in trying to verify syslinx version, I have found another hang: > > efi boot, see menu, hit ^c, hung. > > legacy boot, ^c gets me a boot: prompt. > > > > > If you want to test whether the "help" files work, you select the > relevant row and press enter. I don't know why you would pr...

On Mon, 2017-11-27 at 18:03 -0500, Gene Cumm 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 Mon, Nov 27, 2017 at 2:14 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > > On Mon, Nov 27, 2017 at 12:07 PM, Joakim Tjernlund > >

Trying to set up UEFI Syslinux boot on an ArchLinux USB 4GB stick. - Host system: 64-bit Ubuntu 14.10 on 56 GB hard drive - Hardware: ASUS P8H77-I, Bios v1101, i7-3770 at 3.40 GHz, 16 GB DDR3 - ArchLinux Instructions followed: https://wiki.archlinux.org/index.php/Syslinux#UEFI_Systems > ? ? 2. UEFI Systems > 2.2 Installation - Arch syslinux v.6.03 196352 Oct 13 22:25 /usr/sbin/syslinux

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:

...oot process using the boot order specfied in the BIOS settings. I was unable to get this to work after a 'restore'. Presumably something got corrupted. For my purposes, booting from a specified device meets my needs. Finally, I would like for you to consider including this in the standard syslinx distribution. Q: What other design information would you like? Q: What additional testing do you want done? Q: Should I send you patches to syslinux-3.11? Or is there a later development version? Or do you prefer another mechanism? Q: Anything else? Thank you very much for all of your contri...