similar to: SYSLINUX 3.08-pre5

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

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

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

SYSLINUX 3.11-pre5 is hereby a bug fix release candidate. If I don't receive any problem reports, I will release it as-is on Tuesday, August 30. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

Okay, now, before 3.10 is finalized... what bug reports am I still forgetting? -hpa

hpa, etal, pxelinux works great from a push of the reset button. machine boots normally. However, after i issue 'reboot' command, my box fails to find the tftp server during reboot. This looks to be happening before pxelinux has any chance to participate, so it cannot be to blame. Im seeking corroboration here before I go badgering the bios-provider here's the relevant

Hi, I am trying to load kernel 2.6.6 on a Soekris net4521 from the network using PXE. I built my initrd with mkinitrd. RedHat nash (while running linuxrc) hangs after mounting /proc and says "Creating block devices". I am using the pxelinux.0 from the syslinux-2.10 distribution and the kernel and initrd were built on redhat 9.0. I built my kernel with BLK_DEV_RAM, RAMFS, TMPFS,

Hi A Optiplex GX270 with bios A06 (latest) freezes at the menu when I use 3.08pre5. Setup was simple menu (menu.c32) and pxe. When I tested with 3.07 everything worked as normal. I Have not had any problem with 3.08pre5 in other tests and machines. Also but not that important, I learned that for the hotkey highlight to work It must be uppercase for me. If lowercase the goto still works but

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:

Greetings all, Is there currently any mechanism in pxelinux the would send a mac address of the pxe booted interface through to the linux kernel much like ipappend can send the ip address? Kickstarting a system with multiple interfaces can be troublesome. ksdevice is helpful but only in some circumstances such as forcing eth0, but that doesn't always work since probe order changes depending

Dear all, I'm trying to boot a recent PXELINUX on a brand new Soekris net4501 (comBIOS 1.33). This combination appears to not work out of the box... I see much advice floating around from a few years ago, hinting that earlier versions of PXELINUX might have worked. However before resorting to archaeology I'd be interested in feedback from others who might have got through this. I

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

hi Peter, everyone, I recently installed extlinux on my CF drive. after a few botches, it works, with menu.c32 too. Heres a few notes/observations: - menuing seems pretty sensitive to presence of tabs in extlinux.conf, unlike with pxelinux.cfg/default, Is this an oversight, or something Im misremembering ? - extlinux doesnt have the timeout after menu-choice. if I dont choose, it times out and

http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=4d60422 also broken with this commit

Hi, everybody! My pxelinux.0/default file is: LABEL linux KERNEL vmlinuz-2.6.16 APPEND initrd=initrd-2.6.16.img root=192.168.4.110:/clients/192.168.4.100/root When mounting I get: switchroot: mount failed: 22 Kernel panic - not syncing: Attempted tp kill init! Before it I get some messages about: Can't find /dev/console. /clients/192.168.4.100/root/dev was empty. I've copied my

Hi, I have experimented with enabling the LoopVectorizer for SystemZ. I have come across a loop which, when vectorized, seems to have been poorly generated. In short, there seems to be a completely unnecessary sequence of shufflevector instructions, that doesn't get optimized away anywhere. In other words, there is a shuffling so that leads back to the original vector: [0 1 2 3

changing i386 COMMAND_LINE_SIZE to 1024 attached is a simplistic fix to change kernel's command-line size from 256 to 1024, tomatch capability in syslinux 3.08. It seems to work. Is this all there is to it ? One of the reasons I did this was to figure out what extra options are appearing, and why. b4 extending: (the last bit is truncated) Jun 4 06:31:05 truck kernel: Kernel command

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

I just want to send a quick note that I am running clean unpatched 2.4.15-pre5 with ext3 on root (and only) Linux partition on my notebook for a while, and it just works without a glitch. Congratulations to the developers (and users :) for getting this stuff in the mainstream distribution at last. Eugene

Are there any issues with ext3-2.4-0.0.7 on 2.4.6-pre5? The patch applies with offsets and no rejects. [I need the export reiserfs by knfsd functionality of -pre3 onwards. My intent for the test system is to protect all standard partitions /, /usr, /var with ext3 (easier to revert to ext2 and do OS upgrades) and try a mixture of ext3 and reiserfs for exporting of data and user home partitions.]