similar to: colon in syslinux.cfg leads to "Unknown keyword"

Hi: I am having problems with isolinux.cfg I am receiving several error messages. 'Missing parameter in config file' and 'Unknown keyword in config file'. Here is a copy of my Isolinux.cfg maybe sombody can help me figure it out: default ks prompt 1 timeout 60 display custom.msg F1 boot.msg F2 options.msg F3 general.msg F4 param.msg F5 rescue.msg F7 custom.msg

I have problems getting the TIMEOUT value work the same way LILO/GRUB does it.. ie it should wait until the timeout and then use the default value. However, it goes straight for the default value without waiting a single second (and a TIMEOUT value of 500 should mean 50 seconds, as it counts in 1/10th of a second, right?) SYSLINUX (isolinux) 2.00 ----8<------8<---- SERIAL 0 38400 TIMEOUT

Hello all, I plan to make an (emergency) multi OS bootable CD which contain: - Win98 boot floppy (create from Win 98 control panel, add remove program) - WinME boot floppy (create from Win 98 control panel, add remove program) - Linux boot disk - Win NT boot disk - Win 2000 recovery console - Win XP recovery console - Winternal Administrative Pak (ERD Commander etc) I am new to Linux and feel

Hey all, I'am able to use pxelinux to successfully boot a particular kernel and image on various IBM PC's ex. 6287-41U and 6591-34U. However, using the same setup (ie. dhcp, tftp, pxelinux.0, pxelinux.cfg, networkcard, bootrom, ram memory) on an IBM 6282-73U my kernel and image decompress fine but I'am getting a... Kernel Panic: VFS: Unable to mount root fs on 01:01 I realize

On Sat, Nov 17, 2018 at 1:54 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > On Thu, Nov 15, 2018 at 1:10 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > > Here are some comments and questions for you. > > > > > > > Thanks. > > > > I've have my scripts to a better state, including

Hello ! Maybe passing argument root=/dev/ram0 or root=/dev/rd/0 would help ? I use isolinux and it works in the isolinux.cfg sylvain > Message: 3 > Date: Fri, 13 Sep 2002 14:11:38 -0300 (ADT) > From: Geddes <jgeddes at unb.ca> > To: syslinux at zytor.com > Subject: [syslinux] Unable to mount root fs > > > Hey all, > > I'am able to use pxelinux to

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: Two scripts (mkbd.fails and mkbd.works) are attached to this message. The only difference between them is in how syslinux.cfg (on a RedHat boot image) is replaced. mkbd.fails: syslinux.cfg is replaced via "mv -f". vmlinuz can't be found. mkbd.works: syslinux.cfg is replaced via "cp". vmlinuz is found. The only difference I can see between these two methods is that

Hi. I'm trying to make a simple boot floppy that would choose between booting with serial console or with keyboard/screen based on user's input. In the ideal world, I would like to have the following behaviour: On the serial console, it would show the welcome screen and say "Press Enter now to boot from serial console" and on the VGA screen (at the same time) it would

Hi, Another thing I'm strugglin with: When creating a new domain from scratch using the proposed XML format in the documentation, everything works fine - basically. A problem that I'd like to solve now is that I would expect to be able to create new volumes within libvirt. I started with a basic XML file in order to define a pool, but virsh told me that creating pools is not supported

Hi. I'm trying to put together a boot cd using isolinux, but I've run into a problem. The system I'm trying to boot with this cd complains that it "Could not find kernel image: linux". This is the isolinux.cfg file that I'm using default linux prompt 1 timeout 600 label linux kernel vmlinuz-2.2.14 append initrd=rootfs_new.img lang=

Hi all, I'm looking for some menu examples for Murali's menu system. Specifically, a headstart on creating a Kickstart menu which covers the most common options with the intention of creating this: label ks.menu kernel vmlinuz.ks.$DIST append ksdevice=eth0 ks=http://kickstartserver/$DIST/Custom/ks.cfg.$DIST initrd=initrd.ks.$DIST lang= devfs=nomount ramdisk_size=8192 Hmm...looking

Hi All, Interesting that I couldn't find this documented anywhere, but what happens to text that is typed after the label on the syslinux prompt? My current issue is I'm using PXE to do kickstart installations. I want the ability to do "rescue" boots also with PXE. I've gone looking at the current RH80 disk 1 which has this capability. It has a directory called

I had a little trouble installing WINE and, becuase of that, tried several different versions. It turned out the sound trouble was not a WINE issue, but a devfs issue, so I deactivated devfs (devfs=nomount). I am using the latest RPM of Codeweaver's WINE with Mandrake 8.1. I've got Codeweaver's WINE up and running now. When I first tried this, I could type a win .exe file from

I'm trying to install centos 6.4 on my server A (which has 512 MB ram and no cdrom) by PXE. I exported installation tree 'CentOS-6.4-i386-bin-DVD1.iso' via http on server 'Z', all according to Centos howto (copied vmlinuz, pxelinux.cfg, initrd.img , started tftpd+dhcpd services) Boot process is OK (in text mode! I think it's a memory problem); it's required keyboard

Here are some comments and questions for you. > I want to eufi boot this image: > http://cdn-fastly.deb.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/boot.img.gz I am going to assume that by "boot this image" you don't mean something like memdisk or equivalent, but rather that you want to transfer that image using "dd" to your

On Fri, Dec 7, 2018 at 7:47 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > On Thu, Dec 6, 2018 at 10:00 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > > First, I'm confused. In the prior "whole" setup (the one you generated > > > after my 15 steps, plus one workaround), was/is the basic boot menu at

Hi, I just upgraded syslinux to version 3.0.7 from 2.13, but my pxe client got some warning messages. The pxelinux config file looks like: default memtest timeout 70 prompt 1 #--------------------------------- label local localboot 0 #--------------------------------- label memtest # note! *.bin is specially purpose for syslinux, # do NOT use memtest86.bin, use memtest86 instead of

> Nicolas Boulay wrote: >> kernel vmlinuz >> append livecd=livecd initrd=initrd.gz root=/dev/rd/3 devfs=nomount \ >> acpi=ht nomce vga=normal keyb=fr console=ttyS0,19200n8 > > You're not actually using \-continuation lines, are you? None of the syslinux programs support them at this time. no i wrote it just for this mail. The only message from the booting

Hello all! I try mondo/mindi for some days now but it does not work and I don't know the reason. It is an intel Suse-8.0 Client and I use the Suse-8.0 packages from ftp.mondorescue.org. dhcp and tftp work fine. mondoarchive works, but I don't find any initrd.img for pxe/nfs. All initrd I have found ask for a CDROM and as they cannot find any they ask for a floppy when starting the pxe