similar to: Editing the boot prompt

Hi there Gene! Thanks you about your quick response!! As for your request, here is my whole Syslinux.cfg file: default /syslinux/vesamenu.c32 prompt 0 timeout 00 menu hshift 15 menu width 49 menu title Boot menu menu background /syslinux/splash.png menu color title * #FFFFFFFF * menu color border * #00000000 #00000000 none menu color sel * #ffffffff #76a1d0ff * menu color hotsel 1;7;37;40

Hi > Maybe I'm missing something, but this has been working flawlessly for > us in Tails so far. What exactly fails? Are you using EFI Handover Protocol? It might explain the difference Thomas

Actually your Syslinux config is less relevant than the kernel config file. Indeed Syslinux infers the method to use from the kernel image itself. I assume the .config is public. I will take a look as soon as I can Thomas Le 04/08/2015 14:09, intrigeri via Syslinux a ?crit : > Thomas Letan via Syslinux wrote (04 Aug 2015 09:27:38 GMT) : >> Are you using EFI Handover Protocol? >

Hi, I've been trying to setup a dual livecd. However I am getting an error with parsing the isolinux.cfg. I am using 3.84. the relevant section of the isolinux.cfg is as follows label LiveCD1 kernel vmlinuz1 append livecd=livecd1 initrd=initrd1.gz root=/dev/rd/3 acpi=on splash=silent vga=788 keyb=us fstab=rw,noauto label LiveCD2 kernel vmlinuz2 append livecd=livecd2

Am 30.06.2013 23:05, schrieb atar: > Hi there!! > > I has been modified the syslinux.cfg file according to the rules to add > some boot parameters but since this modification, every time I that I > highlight the modified entry in the boot menu and hit the TAB button > on my > keyboard, the entry's boot parameters is displayed twice and when I > try to >

Hello, I hope that somebody can help me, I am trying to boot Knoppix from the third parition of an ipod nano with out loosing the player capabilities. After fdisk I have the following partitions: slr ~ # fdisk -l /dev/sda Disk /dev/sda: 4095 MB, 4095737344 bytes 255 heads, 63 sectors/track, 497 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End

Gene Cumm wrote:- >TC64 still has ISOLINUX. The basics are to use chain.c32 to boot >USB-B:p3 but syntax depends. Ideally, it's a modern enough Syslinux >version that you can use the "guid" or "label" options to auto-detect >its location rather than "chain.c32 hdN M". Hopefully your FS >label/GUID is unique sdb3 Boot Primary

I tried installing with several options (noacpi noapm; noprobe; noprobe skipddc noacpi noapm nodma). Always I get the same error. BUT this is not in fac a CentOS problem at all, because I get the same error always when I boot from hd (Fedora Core), IF there is a CD in the CD-ROM drive. (I tried with CentOS 1/4, CentOS 2/4 and a HP printer software CD.) It must be something with the CD drive!

Listee's... I have a 5.5 box and I have formatted a partition as ext4 however I can't mount it, the mount command is telling me its an unknown file system type. fsck tells me the partition is a clean ext4 partition but I can't mount it. Some reasearch has lead me to believe the problem is that ext4 isn't enabled in the kernel by default in 5.5 (this was originally a 5.2 box that

Thomas Letan via Syslinux wrote (04 Aug 2015 09:27:38 GMT) : > Are you using EFI Handover Protocol? What we're doing is: label livefailsafe menu label Live (failsafe) kernel /live/vmlinuz2 append initrd=/live/initrd2.img boot=live config live-media=removable apparmor=1 security=apparmor nopersistent noprompt timezone=Etc/UTC block.events_dfl_poll_msecs=1000 splash noautologin

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

On Jun 30, 2013 5:16 PM, "atar" <atar.yosef at gmail.com> wrote: > > Hi there!! > > I has been modified the syslinux.cfg file according to the rules to add > some boot parameters but since this modification, every time I that I > highlight the modified entry in the boot menu and hit the TAB button on my > keyboard, the entry's boot parameters is displayed

So ever since syzbot discovered fbcon, we have solid proof that it's full of bugs. And often the solution is to just delete code and remove features, e.g. 50145474f6ef ("fbcon: remove soft scrollback code"). Now the problem is that most modern-ish drivers really only treat fbcon as an dumb kernel console until userspace takes over, and Oops printer for some emergencies. Looking at

I have decided to promote SYSLINUX 3.31-pre4 to release candidate status. If it tests out OK, it will become 3.31 some time next week, probably. -hpa

Hello all, I have a few questions about the menuing system that I haven't been able to find in the archives (it would be nice if they were available in a searchable form other than having to click on a month-by month basis and read through them - if they are searchable I would love to find a way to do this but it hasn't jumped out at me). My first question is : What is menu.c32? I

The attached config works, but gives 2 error messages that get covered up by the GUI screen so fast I cannot read them. I think they are probably about having 'LABEL' with nothing after it. I was trying to follow the example in menu.doc but somehow I'm doing it wrong. Please consider helping me figure out how to get the same resulting GUI menu without any error messages. I am using

I have just released SYSLINUX 3.31. It is functionally identical to SYSLINUX 3.31-pre4. Changes in 3.31: * The simple menu system (menu.c32 and vesamenu.c32) now support loading more than one configuration file at a time, using MENU INCLUDE or by specifying multiple filenames. * The MENU COLOR statement can now control the shadowing mode. Changes in

Hola: ¿Existe alguna forma de obtener el valor numérico de los intervalos de confianza en una autocorrelación? O, por el contrario, ¿tengo que calcularlos «a mano»? (Llevo ya un rato buscando y nada.) Gracias por adelantado. Salud y Revolución. Lobo. -- Libertad es poder elegir en cualquier momento. Ahora yo elijo GNU/Linux, para no atar mis manos con las cadenas del soft propietario.

So ever since syzbot discovered fbcon, we have solid proof that it's full of bugs. And often the solution is to just delete code and remove features, e.g. 50145474f6ef ("fbcon: remove soft scrollback code"). Now the problem is that most modern-ish drivers really only treat fbcon as an dumb kernel console until userspace takes over, and Oops printer for some emergencies. Looking at

There is a maximum of 255 characters of parameters you can pass to the kernel. At least that's what I recall, but I may be wrong. -----Original Message----- From: Roberto De Leo [mailto:deleo at unica.it] Sent: Thursday, October 03, 2002 5:19 PM To: syslinux at zytor.com Subject: [syslinux] maximum number of characters in APPEND Hi, I wonder whether there is a maximum number of