similar to: Fw: Issue with pxelinux

I've begun tinkering with syslinux v3 and have uncovered an anomoly with the DISPLAY file when called by pxelinux.0. If I have: DISPLAY boot.msg With an "^Xsplash.lss\n" in the file boot.msg (exactly: 18 73 70 6C 61 73 68 2E 6C 73 73 0A) file, it will fail to load the rle image. And produce some goofy results in the tftpd log: Jun 5 06:27:06 pxe in.tftpd[24649]: RRQ from

Hey, I just wanted to mention that the same problem still exists for me in version 3.09, altough the changelog mentions: Reduce the command line to 511 characters; 1023 caused memory overflows. Was this meant to be a solution for this problem, or does this entry of the changelog apply to another bug? thx, marco >Yesterday Curtis Doty said: > > > >>I've begun

using simple menu and a timeout, and no menu default; if I choose forex the 3rd boot-target, but dont hit return, it will timeout, and reset the selection to thte 1st (default) boot target. another timeout, and it boots that 1st target. it seems more appropriate to either a. end the timeout, and just wait for the user (grub, lilo do this iirc) b. boot the manually selected target when timeout

hi, - big and ugly mail. If you don't like them, delete it now :-) - I have collected and classified some information of: http://home.earthlink.net/~rwhron/kernel/bigbox.html And I observed that ext3 performance is worse than previous kernels(2.4.19...). -ac and -aa are here only as reference. Complete information is in the upper URL. dbench: Performance is worse. dbench (Numbers are in

Hi, I am a happy user of version 4.06 and have been hoping to upgrade the 5.x series (for the HTTP bits). I have the following problems with the 5.11-pre7 build: 1. TFTP load is horribly slow ... even when the two REAL machines are connected to the same switch. For a typical RHEL installation, the vmlinuz loads ... the initrd.img loads very very slowly and just times out (I waited over 10 mins)

I am hoping for some advice regarding another index problem. The code below is intended to assign a value of 'V' if values on certain variables are >= 1, assign a value of 'N' if values on certain variables are >= 1 on other variables and assign a 'O' if values on any variable which have a value <= 0. The outcome of this code is to assign a single

Dirk Haus wrote: >What would be the syntax to call other NBPs vom >pxelinux (and has someone already tried it with 3Com`s >Boot Image Editor "imgedit" bootstraps)? I haven`t >found a single word about this feature in the pre-7 >tarball. Mr. Haus, I would very much like to know about your experience invoking another NBP from PXELINUX. I'm trying and failing to

Hi! as i know that you like test reports, here are some... Testing environment: CompactFlash card, connected with an USB adapter to a Compaq Evo D310 frontal USB port. This machine boots via USB quite well with syslinux. 3.09 boots ok, no problem 3.10-pre2 does not boot 3.10-pre3 does not boot 3.10-pre4 does not boot 3.10-pre5 locks up pc 3.10-pre6 locks up pc 3.10-pre7 writes

I have released 3.08-pre10, which includes a version of 'raw' support which should work when the CPU is in big real mode (called 'bigraw', appropriately enough.) Note that it will ALWAYS put DS and ES in big mode; there isn't any really sane way to test if they should be or not. -hpa

Hi, HPA: Thanks for the nice new features, appreciate that. Syslinux is always a nice program. For the new version, 3.10-pre20, I encountered a problem now, my client machine uses sis900 chip, and it still can not run simple menu with pxelinux in this version (3.10-pre20). It's same situation as I encountered when I used syslinux 3.07, 3.08 and 3.09. For 3.10-pre20, I compiled in Fedora

Hi again... The text under "BTX loader..." should appear as a block where each line is 56 characters long. "BTX halted" is on its own line. Apologies for my mailer... -Chris -----Original Message----- From: McMahon, Chris Sent: Wednesday, November 19, 2003 8:32 AM To: 'H. Peter Anvin'; McMahon, Chris Cc: 'syslinux at zytor.com'; 'mike at

The syslinux-4.0.04-pre11 and pre10 have 20MB tar.sign files that other versions don't, and has dates for Jan 01 1970. It appears these are the uncompressed tar files rather than a signature for the file? ftp://ftp.kernel.org/pub/linux/boot/syslinux/Testing/syslinux-4.04-pre1 1.tar.sign One other note. Last time I checked, it was still using 2010 as the latest date in the

Hi, syslinux-6.02-pre10 works! I'll get my menu. -- Regards, Igor

At first I thought, I was dealing with the known EBIOS/CBIOS-problem. The symptom was exactly the same (hangs at ...EBIOS). As 3.10-pre8 and 3.10-pre9, in contrary what was mentioned in the ML, did not bring any improvement, I looked deeper into what could be my specific problem. I found out that the program just halted at 'cmp [esi],edx' (line 658; ldlinux.asm 3.10-pre9)! By replacing

I found that the version of isolinux.bin (and the debug version too) doesn't work on my Via C3 system. I get the SAY text, but never the boot: prompt. C-A-Del doesn't reboot either. The debug version does not print anything after announcing it's opening the config file. Only the single SAY text follows. The cursor sits on the next blank line, useless (no responses to key presses).

Im trying to use newer simple-menu features, and have found that the following config-file (closely based on wiki pxelinux example) - fails for 3.62-pre11, - works for 3.62-pre10 where 'working' is successive reloads such that re-edits of file are seen on next reload and broken is issuing this error: Initial menu has no LABEL entries! boot: #>

Hi all, I've searched the depths of the resources on the internet; however I'm having trouble deploying a pxeboot solution via pxelinux. So far what I have successfully implemented in my infrastructure is a successful pxeboot setup for FreeBSD ( without the use of pxelinux ). I'd ultimately like to have a solution that will allow me to choose a network install of various Unix-like

Hello, I hope this doesn't bounce again... I'm having trouble passing control of the PXE process from PXELINUX to the FreeBSD "pxeboot" program. I tried invoking "pxeboot" from the PXELINUX "boot:" prompt. This causes an error "Invalid or corrupt kernel image." I named pxeboot "pxeboot.0" and tried invoking pxeboot.0 from the

Attempting to PXE boot from the BaseOS/x86_64/kickstart/images/pxeboot/ files results in repeating messages Invalid or corrupt kernel image eventually changing to Could not find kernel image: centos8.2.x86_64/vmlinuz I downloaded the files again, from a different mirror, and they are all the same. Wiped the files and recreated /tftpboot/linux-install/centos8.2.x86_64/. No dice. First mirror

Hi all! I'm new to the list (and syslinux for that matter!) but I've searched as best I can for a similar problem to no avail. I've been using pxelinux.0 + menu.c32 + memdisk to load MS-DOS boot images for a few months now using version 3.07. When I introduced a new Intel 945G based machine to the network I started getting very erratic behavior, ranging from reboots to hangs, to