similar to: Where's the formal syntax?

Hi folks My ultimate goal is to be able to add an initramfs to the end my syslinux.cfg resulting in an additional initramfs being loaded when the system boots. So I need to work out how to get initrd+= to work. I?ve been trying for days now everything I possibly can to get initrd+= to work but nothing I do works. I've also been trying to get initrdfile= to work but no success with that

When a USBstiked-syslinux starts, it's the PC's firmare that's reading the USB ? But once the USBsyslinux takes over, has IT also got a USB driver? Since my MotherBoard & 2009 Slackware built USBstik syslinux booter were stolen I bought a <WinTel> laptop and USBextender to access my old IDE & SATA disks. With WinTel's new arrangement of not allowing the tail of the

On Mon, May 1, 2017 at 7:45 AM, eas lab via Syslinux <syslinux at zytor.com> wrote: >>Do you mean boot SYSLINUX from stik-A but then load files like a >>kernel/initrd from stikB:partition5? It's possible but only from a >>development version of Syslinux that has the multifs patch merged. > > Yes: before my x86MotherBoard & <syslinux>USBstik were stolen,

When a USBstiked-syslinux starts, it's the PC's firmare that's reading the USB ?. But once the USBsyslinux takes over, has IT also got a USB driver? So that USBsyslinux can install a different USBstik/partition? Ie. boot with stikA to install & run stikB:partition5 ? ------------ Is the following sound logic? > Do zero out the partition table first so you don't

> I don't think that syslinux be in concern here. If I understand well > Slackware is installed on a hard disk partition that you want to access > through the USB-adaptor to IDE/SATA. No. I'm not married to Slak. It's important to distinguish between verbatim/pasteable and what the old-writer merely thinks/remembers. I want to be able to boot ANY installation/partition as I

Yes this is the SAME question, that I can't get an answer from a month ago! I have the files, from a USBstik [now stolen] which I previously could edit at boot time, to boot any of my IDE or SATA partitions. Now, with a laptop, I want to boot the same IDE or SATA via a USB-adaptor to IDE/SATA. And also I want to boot a Toshiba 500GB USB disk. The obvious question is: why [if] the old system

Previously I've been using a laptop with an "Aptio Setup Utility...2015" to "Disable UEFI Boot" and allow a USBstik with partition1 having: /boot/isolinux/isolinux.bin , isolinux.cfg , menu.c32...etc. to boot 64bit TinyCore. Now this newer laptop has: "Aptio Setup Utility...2018" which is completely different from the 2015 version. I fail to boot linux from

AIM: from <isolinux> on USBstikA, boot Debian7 installation on USBstikB. EXISTING STATE: USBstikA is TinyCore64bit booter, with:- /boot/isolinux/* 61312 Oct 26 2016 menu.c32 24576 Oct 26 2016 isolinux.bin 2069 Nov 22 01:24 isolinux.cfg ... USBstikB-partition3: Currently boots a 32bit installation, via GRUB using the entry:----- menuentry 'Debian GNU/Linux, with Linux

My previous question: "can syslinux on a USBstik also boot installations on other USB devices ?" got no proper reply, so I'm now including more background detail. The new problem is that my 32bit partition of ETHOberon, only gives a proper font-size under Debian7:DVDinstaller:rescueMode, since I'm forced to use a laptop, after my previous systems were stolen. Neither gnome nor

>Do you mean boot SYSLINUX from stik-A but then load files like a >kernel/initrd from stikB:partition5? It's possible but only from a >development version of Syslinux that has the multifs patch merged. Yes: before my x86MotherBoard & <syslinux>USBstik were stolen, I could edit the <syslinux prompt> to boot to different partitions of the attatched IDE & SATA. Now

I want to be able to make a USBbootStik for my laptop, as I repeatedly did for the now stolen PC. I've got a copy of the required 2009, Slackware13 partition, saved to a USBdisk. And I've located the 175-line: <make bootStik script> . Of course just "chroot"ing Slak13, won't allow <make bootStik>. But why can't someone here, provide the info to make an

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

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

Hi, I tested the following config: DEFAULT AutoInstall PROMPT 0 LABEL AutoInstall KERNEL http://server/vmlinuz64 APPEND initrd=http://server/initrd64.img root=live:http://server/LiveOS/squashfs.img quiet lang=en keymap=de-latin1 systemd.unit=rescue.target system.unit=rescue.target system.unit=rescue.target I use VMWare Player 5.02 build 1031769 on Win2k8 R2 64bit. I found that the last

Op 2013-07-15 om 12:40 schreef Michael Szerencsits: > > If it is http://rosa.stappers.nl/ff/boot-efi-s100.cap > > then is at packet 2242 the client ( .243) started to send > > "TCP Dup ACK" of packet 2241 > > > > > > Thing I what to mention is that there packets of sizes bigger as 9000bytes. > } So large as a jumbo frame. > > > > I

Op 2013-07-13 om 19:58 schreef Michael Szerencsits: > Hi, > > I tested the following config: > > DEFAULT AutoInstall > PROMPT 0 > LABEL AutoInstall > KERNEL http://server/vmlinuz64 > APPEND initrd=http://server/initrd64.img > root=live:http://server/LiveOS/squashfs.img quiet lang=en > keymap=de-latin1 systemd.unit=rescue.target > system.unit=rescue.target

> I don't think that syslinux be in concern here. That's why I pasted the `ls -l` of the directory: to show that the previous working USBstik was *SYSLINUX* based.

On Sat, Dec 2, 2017 at 10:35 AM, eas lab via Syslinux <syslinux at zytor.com> wrote: > AIM: from <isolinux> on USBstikA, > boot Debian7 installation on USBstikB. I thought we answered this but perhaps it's not the "Can I boot ISOLINUX/SYSLINUX from USB-A and boot to USB-B" whose short answer is "No" but long answer is "It depends on the BIOS/CSM

> Yes this is the SAME question, that I can't get an answer from a month ago! > > I have the files, from a USBstik [now stolen] which I previously could > edit at boot time, to boot any of my IDE or SATA partitions. How exactly were you editing (something)? Do you mean that you somehow changed some boot command from the Syslinux boot prompt during boot? In that case, which

> ]You seem to be assuming that changing from a direct SATA and IDE > ] connections to some USB adapter would have no impact on how the > ] respective HDDs are recognized/detected by the BIOS. > > ] You seem to be > ] assuming that the BIOS from 2 different PCs/Laptops would recognize all > ] your devices in the same exact way and that there would be no changes > ] in