similar to: ifcpu64.c32 not working properly when used in a menu include file

Hello, Long story short, example config: ### cut UI vesamenu.c32 MENU TITLE Multiboot USB MENU BACKGROUND #00000000 MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all MENU COLOR unsel 37;44 #50ffffff #a0000000 std MENU COLOR tabmsg 31;40 #30ffffff #00000000 std MENU BEGIN MENU TITLE System Rescue CD 2.4.1 INCLUDE sysrcd-2.4.1.conf MENU END MENU BEGIN MENU TITLE

On 09/05/2013 01:55 AM, Gene Cumm wrote: > On Wed, Sep 4, 2013 at 2:34 PM, Piotr Karbowski > <piotr.karbowski at gmail.com> wrote: > >> With syslinux (extlinux) it will jump to last INCLUDE'ed menu always, with >> 5.01 it will display list of elements, then allow me to choose which one I >> want to enter. >> >> Even if the include part contain a

I'm having issues with the ifcpu[64].c32 modules. I am building a menu system (as opposed to the command line only options I was previously using) to make it easier for my boss to use PXE. I discovered the modules for auto detecting the CPU and thought hey, that's great! However, I'm having an issue where when I select to boot say System Rescue CD, it drops me to the command line

Hello, ifcpu64.c has the following comment: * append boot_kernel_64 [-- boot_kernel_32pae] -- boot_kernel_32 Also in NEWS: (and optionally 32-bit kernels with or without PAE.) However, if one doesn't specify boot_kernel_32pae but only boot_kernel_64 and boot_kernel_32, and if the CPU doesn't have support for PAE, args[2] will be executed unconditionally, with no check for if

Another issue which looks like a bug. If 'ipappend' is set globally (not uncommon in network/pxelinux environment), the last entry for ifcpu64.c32 gets messed up -- to the 2nd (or 3rd) label all the chars from ipappend gets appended, without spaces, resulting in a messy label. Adding -- after the 3rd entry does not help -- the minuses too gets addedd to the command line. For now I

Hi, i have a strange problem since pxelinux 3.62 with the F10 help key. I configured this: DISPLAY pxelinux.cfg/schlunix_new.txt F1 pxelinux.cfg/helps/schlunix F2 pxelinux.cfg/helps/schlunix64 F3 pxelinux.cfg/helps/rescue F4 pxelinux.cfg/helps/rescue64 F5 pxelinux.cfg/helps/stress F6 pxelinux.cfg/helps/stress64 F7 pxelinux.cfg/helps/dosimages F8 pxelinux.cfg/helps/mailsystem F9

Hello, as said in the subject; I am having problems with ifcpu.c32 and ifcpu64.c32 detecting a Athlon II X4 CPU correctly as a 64Bit capable CPU. Ifcpu64.c32 does not detect PAE capabilities, also. Both boot the last (32Bit, non-PAE) entry. On two other Core2-based machines I have here, everything works. Can someone tell me what exactly these modules are looking for? Maybe I can compare that

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!". Over http it works like a charm. With the pxelinux.0 it works via

Hello everyone, Since I have some some adventures in UEFI PXE booting ahead I tried to go with the latest syslinux development snapshot in this case 5.10pre1. But I already fail when booting from CD with Failed to load COM32 file .c32 I am a bit perplex since no name of COM32 files is given. I am trying to trace down the issue as good as I can. COM32 files present are:

On Sun, Sep 20, 2015 at 8:33 AM, syslinux-bot for Gene Cumm <gene.cumm at gmail.com> wrote: > Commit-ID: e0ac1d2fdf7d7c58457f3796a12561cce95ca29f > Gitweb: http://www.syslinux.org/commit/e0ac1d2fdf7d7c58457f3796a12561cce95ca29f > Author: Gene Cumm <gene.cumm at gmail.com> > AuthorDate: Sun, 20 Sep 2015 08:30:55 -0400 > Committer: Gene Cumm <gene.cumm at

Given an isohybrid image, I'd like default to a different label when booted from usb vs. when booted from cd. Is there a way to do accomplish this, something similar to ifcpu64.c32 perhaps? Thanks. Joe

Mattias Schlenker <ms at mattiasschlenker.de> wrote: > Is ifcpu.c32 or ifcpu64.c32 sufficient for your task? No. I need to detect a given machine by something unique. E.g. the MAC-address of the Ethernet Interface CPU-id or such, because I have custom kernels for all the machines. Sven -- If you can spend five minutes on the Internet and do not run Linux, you're a genius. (Dirk

ifgpxe.c32 is a com32 module that will run one command if gPXE extensions are available, and a different command if not. At VMware, we use this module to chain-load gpxelinux.0 from pxelinux.0. Both of those binaries use exactly the same configuration file, and this module allows us to differentiate between the two cases and break the infinite chain-loading loop that might result. Typical usage:

Op 2013-07-12 om 14:06 schreef syslinux-owner at zytor.com: > Reason: Message body is too big: 1780404 bytes with a limit of 512 KB So previous not on the mailinglist. > Date: Fri, 12 Jul 2013 23:05:05 +0200 (CEST) > From: Michael Szerencsits <szerencsits.michael at gmx.at> > To: syslinux at zytor.com > Subject: efi64 boot fail during download from kernel and initrd

> > On 09/20/2013 02:34 AM, Ady wrote: > >> There might be an alternative (and possibly others too): let the user > >> select the appropriate firmware from within pxelinux.cfg/default. > >> > >> So, keep using the same method you used in previous versions, instead > >> of selecting the Syslinux cfg / firmware from the DHCP snippet that >

Hi everyone, for UEFI bootable media I currently use preloader+gummiboot while on BIOS media I use isolinux/extlinux. Since maintaining two configurations is some kind of extra work, I plan switching to syslinux in the next weeks or months. Creating an UEFI boot partition or El-Torito image seems easy: Use preloader, hashtool and the syslinux efi file, copy them to the FAT image and be

I stumbled across the following patch and wondered if it wouldn't be a good idea to have it included. http://foldingcd.svn.sourceforge.net/viewvc/*checkout*/foldingcd/trunk/folding_cd/patches/syslinux-3.51-64bit.patch?revision=5 It adds a default64 keyword and detection of a 64bit processor. It could be useful for mixed environments. The patch is against 3.51, but looks like it would port

Let's try to get this thing released. Dag: will you do your RPM buildathon on this drop? Changes in 3.74: * New UI directive, which allows a more natural way to specify a menu system (or not.) With the UI directive specifying the menu system, the DEFAULT directive can be used to select the default entry inside the menus. * kbdmap.c32: new module

Even though Doug's out of the office, I'm submitting a patch to the ifcpu[|64].c32 COMBOOT32 modules for testing. Also available for perusal with a web browser at: http://git.zytor.com/?p=users/sha0/syslinux.git;a=commitdiff;h=cc70d0fa5 5e35fabf250f4dccbaed2fa44f56da7 - Shao Miller --- >From cc70d0fa55e35fabf250f4dccbaed2fa44f56da7 Mon Sep 17 00:00:00 2001 From: Shao

On Wed, Oct 30, 2013 at 09:52:57AM +0200, Ady wrote: > > > The wiki (http://www.syslinux.org/wiki/index.php/PXELINUX) still says: > > > > "copy pxelinux.0 (from the SYSLINUX distribution) and any > > kernel or initrd images that you want to boot" > > > > like I've been doing forever, but how do I know what else I need, and > >