search for: myinitrd

Hello, I am using lpxelinux.0 (latest stable version 6.03, using the official binaries from kernel.org) to kickstart servers as http transfers really helps over links with poor latencies... These servers are being booted in legacy mode, not in UEFI. This has worked very well until recently. Starting with RHEL 7.5, on some servers, we would see the machine rebooting while pxelinux is in the

...e same version, not just lpxelinux.0. Alternatively (and in many cases, even better) you could try current Debian's "Unstable" packages, which are "more up-to-date" than 6.04-pre1. B_ In the configuration file, instead of using: ### LABEL mylabel KERNEL mykernel INITRD myinitrd APPEND myoptions ### try: ### LABEL mylabel LINUX mykernel INITRD myinitrd APPEND myoptions ### and/or also try: ### LABEL mylabel2 COM32 linux.c32 APPEND initrd=myinitrd myoptions ### (Reminder: use linux.c32 and the lib*.c32 modules from the same version as lpxelinux.0 and ldlinux.c32.)...

...ly respond to shutdown/reboot commands from xm I''m having trouble converting them. I believe need to convert the menu from something like this: root (hd0,0) kernel /xen.gz-2.6.18-53.1.14.el5 module /vmlinuz-2.6.18-53.1.14.el5xen ro root=LABEL=/ module /myinitrd.img to something like this: root (hd0,0) kernel /vmlinuz-2.6.18-53.1.14.el5xen ro root=LABEL=/ initrd /myinitrd.img The Debian 6 VMs I have appear to use grub2, which is a pain in the rear as far as I can tell. I expect there are good reasons for it, but being able to...

Hello, i would like create a bootdisk , that can be boot from Old BIOS, EFI32 and EFI64. But for EFI Boot there is only one directory /EFI/BOOT/ In this directory I can copy BOOTia32.EFI and BOOTx64.EFI. But the *.c32 files for EFI32 & EFI64 , I can install to this directory at the same time. Is there a way to load the *.c32 from different directory ? Or is there a other solution ?

...mod --with jbd --with ahci --with dm_mod --with dm_multipath --with dm_snapshot --with dm_zero --with dm_mirror --with pcspkr --with mii --with 8139too --with 8139cp --with i2c_piix4 --with serio_raw --with parport --with parport_pc --with lp --with ac --with asus_acpi --with battery --with autofs4 myinitrd.img 2.6.16.33-xen But, it is occuring error on boot. Would you advice on me? Please, help me. I''m getting tired.. I tried for 2 weeks. $ uname -r 2.6.18-92.1.10.el5 $ lsmod Module Size Used by ipt_MASQUERADE 7617 0 iptable_nat 11205 0 ip_nat...

On Wed, Oct 4, 2017 at 11:10 AM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > FWIW, the _need_ to use linux.c32 is becoming more common (in the sense > that other loading methods are not always capable of loading > newer/current kernels+initrams+additional_files, considering their > sizes). Unfortunately, only a minority of users seem to be aware of > Syslinux's

...as a bit of confusion. > > 1) You never said if you saw tests to get just the core (isolinux.bin > and ldlinux.c32) loaded. Did you try my simple config? > > > #syslinux.cfg-begin > DEFAULT linux > PROMPT 1 > > LABEL linux > LINUX vmlinuz > APPEND initrd=myinitrd.cgz my-options > #syslinux.cfg-end > PASSED > > 2) If that passes, the core is OK and let's look at loading simple > COM32s like ls.c32. Does ls.c32 work? > PASSED > 3) If that passes, reading the file system and loading linked > libraries are OK. Next, from a &...

...om sid, this version has the same issue. I had also tried official 6.04-pre but not all of them as some are known to be broken: they didn't work either... > B_ In the configuration file, instead of using: > [...] > try: > > ### > LABEL mylabel > LINUX mykernel > INITRD myinitrd > APPEND myoptions > ### Because our installer has a long history, we were still using: LABEL KERNEL APPEND I tried using LINUX with INITRD and APPEND but the behavior is the same: the host reboots. > and/or also try: > > ### > LABEL mylabel2 > COM32 linux.c32 > APPEND i...

...must be commented out. Booting such a build may take a long time while data is pumped over the serial. Although perhaps not helpful in this case, I'd normally suggest a simpler config like the following: #syslinux.cfg-begin DEFAULT linux PROMPT 1 LABEL linux LINUX vmlinuz APPEND initrd=myinitrd.cgz my-options #syslinux.cfg-end The sole use such a simpler config could serve in this instance is to minimize the serial-debug data generated by a working build to compare against a broken build. -- -Gene

To remind you once again. ISOLINUX >= 6.00 built with GCC >= 5.0.0 causes a broken boot. This relates specifically to the use of the vesamenu.c32, menu.c32 works without problemos. This "code" is already in 6.03, therefore this is not a fix for it! Revert "SYSAPPEND: Fix space stripping" This reverts commit 3106dcd http://repo.or.cz/w/syslinux.git/commit/3106dcd Fixes

...ust the core (isolinux.bin >>> and ldlinux.c32) loaded. Did you try my simple config? >>> >>> >>> #syslinux.cfg-begin >>> DEFAULT linux >>> PROMPT 1 >>> >>> LABEL linux >>> LINUX vmlinuz >>> APPEND initrd=myinitrd.cgz my-options >>> #syslinux.cfg-end >>> >> >> PASSED >> >>> >>> 2) If that passes, the core is OK and let's look at loading simple >>> COM32s like ls.c32. Does ls.c32 work? >>> >> >> PASSED >> >>&g...

...To put it another way, the effect is the same. > Although perhaps not helpful in this case, I'd normally suggest a > simpler config like the following: > > > #syslinux.cfg-begin > DEFAULT linux > PROMPT 1 > > LABEL linux > LINUX vmlinuz > APPEND initrd=myinitrd.cgz my-options > #syslinux.cfg-end > > > The sole use such a simpler config could serve in this instance is to > minimize the serial-debug data generated by a working build to compare > against a broken build. >

...nu.c32. Let's start over since your problem statement has a bit of confusion. 1) You never said if you saw tests to get just the core (isolinux.bin and ldlinux.c32) loaded. Did you try my simple config? #syslinux.cfg-begin DEFAULT linux PROMPT 1 LABEL linux LINUX vmlinuz APPEND initrd=myinitrd.cgz my-options #syslinux.cfg-end 2) If that passes, the core is OK and let's look at loading simple COM32s like ls.c32. Does ls.c32 work? 3) If that passes, reading the file system and loading linked libraries are OK. Next, from a "boot: " prompt with the simple config, execute &...

...You never said if you saw tests to get just the core (isolinux.bin >> and ldlinux.c32) loaded. Did you try my simple config? >> >> >> #syslinux.cfg-begin >> DEFAULT linux >> PROMPT 1 >> >> LABEL linux >> LINUX vmlinuz >> APPEND initrd=myinitrd.cgz my-options >> #syslinux.cfg-end >> > > PASSED > >> >> 2) If that passes, the core is OK and let's look at loading simple >> COM32s like ls.c32. Does ls.c32 work? >> > > PASSED > >> 3) If that passes, reading the file system and lo...

...INCLUDE SYSLUEFI.CFG ### /EFI/BOOT/SYSLIA32.CFG end ### ### /EFI/BOOT/SYSLX64.CFG start ### PATH X64 INCLUDE SYSLUEFI.CFG ### /EFI/BOOT/SYSLX64.CFG end ### ### /EFI/BOOT/SYSLUEFI.CFG start ### UI vesamenu.c32 LABEL catl COM32 cat.c32 APPEND SYSLUEFI.CFG LABEL mylabel LINUX mykernel INITRD myinitrd APPEND myoptions ### /EFI/BOOT/SYSLUEFI.CFG end ### Just in case someone was not reading carefully, this method is available in 6.04-pre1 (not in 6.03). About the PATH directive, see: www.syslinux.org/wiki/index.php/Config#PATH HTH, Ady.

...### > > PATH X64 > INCLUDE SYSLUEFI.CFG > > ### /EFI/BOOT/SYSLX64.CFG end ### > > > ### /EFI/BOOT/SYSLUEFI.CFG start ### > > UI vesamenu.c32 > > LABEL catl > COM32 cat.c32 > APPEND SYSLUEFI.CFG > > LABEL mylabel > LINUX mykernel > INITRD myinitrd > APPEND myoptions > > ### /EFI/BOOT/SYSLUEFI.CFG end ### > > Just in case someone was not reading carefully, this method is available in > 6.04-pre1 (not in 6.03). > > About the PATH directive, see: > > www.syslinux.org/wiki/index.php/Config#PATH > > HTH,...

...gt; and ldlinux.c32) loaded. Did you try my simple config? >>>> >>>> >>>> #syslinux.cfg-begin >>>> DEFAULT linux >>>> PROMPT 1 >>>> >>>> LABEL linux >>>> LINUX vmlinuz >>>> APPEND initrd=myinitrd.cgz my-options >>>> #syslinux.cfg-end >>>> >>> >>> PASSED >>> >>>> >>>> 2) If that passes, the core is OK and let's look at loading simple >>>> COM32s like ls.c32. Does ls.c32 work? >>>> >>...

Hello, I'm having a challenge with increasing vmalloc memory beyond 512M using pxelinux.0 to boot. This config works fine: --- # Configuration file # linux-2.6.20-1.2962.fc6 DEFAULT linux LABEL linux kernel kernels/vmlinuz-2.6.20-1.2962.fc6 append initrd=initrds/bladeinitrd-2.6.20-1.2962.fc6.img enforcing=0 vmalloc=512M --- If I increase vmalloc to 513M, I get errors

...### > > PATH X64 > INCLUDE SYSLUEFI.CFG > > ### /EFI/BOOT/SYSLX64.CFG end ### > > > ### /EFI/BOOT/SYSLUEFI.CFG start ### > > UI vesamenu.c32 > > LABEL catl > COM32 cat.c32 > APPEND SYSLUEFI.CFG > > LABEL mylabel > LINUX mykernel > INITRD myinitrd > APPEND myoptions > > ### /EFI/BOOT/SYSLUEFI.CFG end ### > > Just in case someone was not reading carefully, this method is available in > 6.04-pre1 (not in 6.03). > > About the PATH directive, see: > > www.syslinux.org/wiki/index.php/Config#PATH > > HTH,...

Igor asked about APPEND: > In other words: Can I break up a long line into multiple lines > in 5.01 or 5.10pre now or is that still not supported? I also wonder: can one control whether the INITRD parameter gets prepended or appended? Right now it seems to be placed after APPEND parameters, but might be more useful if it came first. The Debian/Ubuntu installers will copy parameters