similar to: ifcpu[64].c32 functions drop to command line

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

The following is a pxelinux problem, specifically to do with including config files with the menu include directive and the ifcpu64.c32 com module. I have a working ifcpu64.c32 setup that jumps to the label rescue64 in the case of a 64-bit CPU. The label "rescue64" defines a 64-bit kernel and a 64-bit initrd.img. The setup jumps to a label named "rescue32" in the case of a

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

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

Conditions to trigger this bug(s): 1_ Boot with ISOLINUX (SYSLINUX seems fine). 2_ Do NOT use the UI directive. 3_ In between TEXT HELP - ENDTEXT directives, use more than one line of text. *** syslinux.cfg start *** DEFAULT vesamenu.c32 PROMPT 0 LABEL pwd1 COM32 pwd.c32 TEXT HELP one line of text two lines of text ENDTEXT *** syslinux.cfg end *** Result: the system ([vesa]menu) hangs.

On 2014?03?07? 18:24, Ady wrote: > Hi Steven, > > Perhaps this could be of some basic sample/help, being based on > Debian: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589 > > where: > _ if gpxelinux.0 is needed, it should probably be replaced by ipxe. > _ lpxelinux.0 (from official Syslinux archive) could optionally be > added. > > _ from the

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

Hello, At the boot prompt ALLOWOPTIONS 0 is only applied to implicit kernels and not to labels. For configuration which want to allow selection, but prevent customization of the kernel command line, this behaviour is bad. Also the IMPLICIT 0 is applied to both the boot prompt and configuration setting (like DEFAULT); but one could argue that only the command supplied at the prompt make sense to

Hello, I poked a little bit to extract the list of modules dependencies in Syslinux v6 (see below). I have attached a bash script that generate a nice table from the tarball. The output can either be an ASCII table, or wiki markup, typically for the page Library_modules[1]. I am not in the wiki Editor group, so I can't put that in the wiki. anyway, here's an updated dependency tree for

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

Hallo, Matt, Du meintest am 25.06.13: >> Not really... let's just document "make bios". > There's preliminary documentation in doc/building.txt. (sent to you and to the mailing list; some robot blocks the list ...) Additionally: Compiling (with "make bios") worked. Running "pxelinux": more problems than with 5.10. 5.00-pre6: all worked fine

> Hallo, Matt, > > Du meintest am 25.06.13: > > >> Not really... let's just document "make bios". > > > There's preliminary documentation in doc/building.txt. > > (sent to you and to the mailing list; some robot blocks the list ...) > > Additionally: > > Compiling (with "make bios") worked. > > Running

Am 30.10.2013 17:31, schrieb Steve Rikli: > But more generally: is copying files from the syslinux distribution > into your /tftpboot/ dir still the best recommended way to "install > pxelinux"? > That latter method seems overkill for setting up pxelinux in a tftp > server, and I'd prefer to get the original distribution from syslinux > than a possibly-modified

The following changes since commit 4fc3fd1e14f4c1b9208ef262e5b6aef853e9fce4: graphics: make use of syslinux_force_text_mode() (2012-05-19 02:05:38 -0300) are available in the git repository at: git://github.com/aericson/syslinux.git elflink for you to fetch changes up to 2779b713bdd8644ee2b52962ece6daa209b4ba6b: com32: remove duplicate modules (2012-05-22 20:59:51 -0300)

Hi, When testing syslinux on Hygon Dhyana processor, there are some information as follows: boot: cpuidtest.c32 Vendor = Unknown Vendor ... boot: ifcpu.c32 debug multicore multicore : 1 cores on this system After adding support for Hygon Dhyana processor, the info- rmation is correct: boot: cpuidtest.c32 Vendor = Hygon ... boot: ifcpu.c32 debug multicore multicore : 64 cores on this

> > I boot my system with the attached extlinux.conf, which has some > entries to boot old kernels. When i'm booting the old versions i'd > like to have a reminder message recalling me that the most recent > kernel is not being used, so that i don't forget to switch back to it, > for example after many days of uptime. > > Now, is it normal that _every_ SAY

I wrote a new module "whichsys.c32" which detemines which command to execute, based on the Syslinux bootloader variant. In the near future it should/can be replaced by a lua script. But for people who want small binaries: whichsys.c32 is +/- eighty times smaller than lua.c32, atm. Usage: whichsys.c32 [-iso- command] [-pxe- command] [-sys- command] Examples: whichsys.c32 -iso-

This is an attempt to avoid potential confusion. Here are some example sizes for the two Syslinux versions mentioned in the e-mail subject. Your build results might be different. 4.06: 1 55 Sep 22 22:23 modules/int18.com 1 108 Nov 1 18:07 version.mk 1 138 Nov 1 18:07 version.gen 1 138 Nov 1 18:07 version.h 1 239 Sep 22 22:23 modules/poweroff.com 1 408 Sep 22 22:25

diff U3 syslinux-6.04-pre1/com32/modules/Makefile b/com32/modules/Makefile --- syslinux-6.04-pre1/com32/modules/Makefile Fri Mar 04 02:09:01 2016 +++ b/com32/modules/Makefile Fri Jun 30 20:09:01 2017 @@ -25,9 +25,9 @@ # All-architecture modules MOD_ALL = cat.c32 cmd.c32 config.c32 cptime.c32 cpuid.c32 cpuidtest.c32 \ - debug.c32 dir.c32 dmitest.c32 hexdump.c32 host.c32 ifcpu.c32 \ -

After 64 prereleases, 626 commits, 52,742 lines of changes, and tons of work by many, many people, Syslinux 4.00 is now officially released. Syslinux 4.00 is the first of a set of major code restructuring releases. The single biggest new features are btrfs and ext4 support, and support for disks larger than 2 TiB. Huge thanks to: - Intel, for sponsoring mine, Alek Du's and Feng Tang's