similar to: problem loading initrd

folks, Im finding that using a config like this: SERIAL 0 19200 #IPAPPEND 2 PROMPT 1 TIMEOUT 100 IMPLICIT 0 APPEND console=ttyS0,19200n81 root=/dev/nfs nfsaddrs=10.10.10.100:10.10.10.2:10.10.10.2:255.255.255.0:soekris:eth0 nfsroot=10.10.10.2:/nfshost/truck panic=15 LABEL deb268 KERNEL vmlinuz-2.6.8-1-386 initrd=initrd.img-2.6.8-1-386 panic=10 LABEL deb268-ram KERNEL vmlinuz-2.6.8-1-386

the following config-file triggers a couple of odd corner-cases in 3.08-pre5 ; SERIAL 0 19200 CONSOLE 0 APPEND console=ttyS0,19200n81 root=/dev/hda1 IMPLICIT 0 #DEFAULT sk1 #DEFAULT menu.c32 DEFAULT sk1 PROMPT 0 MENU TITLE Simple Boot Menu LABEL sk1 KERNEL vmlinuz-2.6.10-sk1 APPEND console=ttyS0,19200n81 root=/dev/nfs

Hi I have noticed that some versions of syslinux later than 1.66 fail to install a working boot block on a CF card in Soekris net4521 board. The Bios is: comBIOS ver. 1.05 20020419 Copyright (C) 2000-2001 Soekris Engineering. The card is a 64M Sandisk and I am useing a version of LEAF called WISP-dist but I also experianced the same problem with the Bering distro. Here is my syslinux.cfg:

folks, Im trying to boot to runlevel 4 explicitly, using this stanza: ie with a single 4 at end of APPEND line. LABEL 2.6.11-r10c2-soekris-v1 MENU LABEL ^j. runlevel 4 2.6.11-r10c2-soekris-v1 # 4 MENU DEFAULT KERNEL vmlinuz-2.6.11-r10c2-soekris-v1 APPEND console=ttyS0,19200n81 root=/dev/nfs nfsroot=192.168.42.1:/nfshost/foo

hpa etal, Im trying to get PIRT running on an SBC which has no CD-ROM drive. (an 8 MB ISO which demo's RTAI - RealTime Application Interface, on linux patched with Adeos) (BTW, PIRT uses isolinux) anyway, Im trying to use pxelinux to chainload / memdisk / mboot it, Im having no success. Ive also tried booting memtest86, which I can boot on my laptop using grub, ie title memtest

HDT 0.3.3 has just been released. This release aims at solving some CLI bugs and adds a some new memory mapping detection. I'd like to thanks Dag Wieers for reporting many CLI bugs & pierre for his work on the memory mapping. Here come the changelog: - A new memory mode Memory items can be reached via the new "memory>" mode. - Memory mapping display Pierre did integrate

HDT 0.3.3 has just been released. This release aims at solving some CLI bugs and adds a some new memory mapping detection. I'd like to thanks Dag Wieers for reporting many CLI bugs & pierre for his work on the memory mapping. Here come the changelog: - A new memory mode Memory items can be reached via the new "memory>" mode. - Memory mapping display Pierre did integrate

Good day again Daniel, So the first thing I did was to remove the >NUL for your XMSDSK line and put a PAUSE after it in AUTOEXEC.BAT. That way, I could see the error message: *** XMS RAMdisk v1.9I (FU - 08/98): XMS get free mem error. Then I noticed that if you run AUTOEXEC.BAT manually from the DOS CLI, XMSDSK actually succeeds! So that led to a new test: Duplicate the XMSDSK line. ...

1. \ at end of lines (in pxelinux.cfg/default, etc) causing/allowing line-wrap ? for those of us who prefer 80 column screens, and 1 item per line. 2. label-specific APPEND adds onto global APPEND ( currently replaces it IIUC ) maybe this needs a separate keyword ADDAPPEND (255 char limit still applies im sure) 3. strip trailing # comments ( I havent verified that it

When you add "quiet" to the append line, Syslinux doesn't display the file reading progress anymore. When you use this option to boot an image with MEMDISK, you still get a lot of text. ========================== LABEL mydisk LINUX memdisk INITRD mydisk.img APPEND raw quiet ========================== The following patch makes MEMDISK silent when the quiet keyword is passed to the

>>Could you do screen captures of the output of meminfo.c32 when booting ISOLINUX-4.06 as a CD and SYSLINUX-4.06 as a USB? The results both match for booting 4.06 via CD and USB: SYSLINUX 4.06 EDD 2012-10-23 boot: meminfo.c32 INT 15h = f000:f859 DOS RAM: 639K (0x9fc00) INT 12h: 639K (0x9fc00) INT 15 88: 0xfc00 (64512K) INT 15 E801: 0x3c00 (15360K) 0xbee8 (3127808K) 0

I'm not exactly sure what you need. Is this it? ISOLINUX 4.06 0x513e88f5 isolinux: Starting up, DL = 82 isolinux: Loaded spec packet OK, drive = 82 isolinux: Main image LBA = 0000011D isolinux: Main image read, jumping to main code... I created an iso with isolinux-debug.bin as the boot loader and booted it on that machine. If this is not what you are looking for, what are correct steps?

On Wed, Jul 3, 2013 at 5:06 PM, Patrick Verner <distrozilla at gmail.com> wrote: >>>Could you do screen captures of the output of meminfo.c32 when booting > ISOLINUX-4.06 as a CD and SYSLINUX-4.06 as a USB? > > The results both match for booting 4.06 via CD and USB: Thanks. > SYSLINUX 4.06 EDD 2012-10-23 > boot: meminfo.c32 > INT 15h = f000:f859 DOS RAM: 639K

Hi Erwan, I finally reviewed the latest HDT 0.3.6 on a few systems (IBM x3650, hs20 and VMware 3.5 guests). = IBM x3650 On the IBM x3650 (using a remote web-based KVM solution) the window blanking (cleaning a window with black before rewriting it with gray/blue content) is very noticable. It would be less of a problem when the window would not be cleared (or at least not with black :-))

On Wed, Jul 3, 2013 at 8:57 PM, Patrick Verner <distrozilla at gmail.com> wrote: > I'm not exactly sure what you need. Is this it? > > ISOLINUX 4.06 0x513e88f5 > isolinux: Starting up, DL = 82 > isolinux: Loaded spec packet OK, drive = 82 > isolinux: Main image LBA = 0000011D > isolinux: Main image read, jumping to main code... > > I created an iso with

hey folks, Im using pxelinux to boot a Soekris box (which works fine to a default image) Ive added a bunch of LABEL, KERNEL pairs, but I cant read the display; Im buried in escape codes. Ive captured some of it to a typescript file: it starts out kosher, but goes unreadable rather quickly, 0005520 \r T F T P . 0005540 / \b \r 0005560 *

Christian Hesse <list at eworm.de> on Mon, 2013/11/11 18:41: > "H. Peter Anvin" <hpa at zytor.com> on Mon, 2013/11/11 08:09: > > On 11/11/2013 04:09 AM, Christian Hesse wrote: > > >> > > >> Let be know if you need any more info. > > > > > > Is anybody working on this? Is there a bug tracker I should report > > >

I have released SYSLINUX 3.08-pre5. Sparse files should now work correctly in extlinux. Symlink support still needs to be added, though. -hpa

I have a Compaq something with a PII-400 and an Intel 440BX/ZX/DX chipset. I put in a Maxtor Ultra133 PCI controller (which is a Promise PDC20269, same as their TX2) and connected the hard drive thereto. Before we go on, I should say that I **hate** both Promise and Compaq. I wouldn't actually BUY this junk. Don't look a gift horse in the mouth, as they say. :) (An old idiom I grew up

> Here are some tests. We did one on a similar machine and it worked. > We deleted the configuration file, obviously. > > # Dell OptiPlex GX620 > ISOLINUX 5.11 5.11-pre7 > isolinux: Starting up, DL = 82 > isolinux: Loaded spec packet OK, drive = 82 > isolinux: Main image LBA = 00000115 > isolinux: Image checksum error, sorry... > > # Dell OptiPlex GX620 >