search for: runkernel

Attempts to load *.lkrn images were failing with "Not enough memory to load specified image". These images have the su_ramdisk_max header field set to zero, and the code in core/runkernel.inc was limiting MyHighMemSize too early (before the load_high call used to load the main part of the kernel). Signed-off-by: Sergey Vlasov <vsu at altlinux.ru> --- core/runkernel.inc | 13 ++++++------- 1 files changed, 6 insertions(+), 7 deletions(-) diff --git a/core/runkernel.inc b/c...

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

...rt jump is out of range ui.inc:517: error: short jump is out of range ui.inc:520: error: short jump is out of range ui.inc:523: error: short jump is out of range ui.inc:525: error: short jump is out of range ui.inc:534: error: short jump is out of range ui.inc:537: error: short jump is out of range runkernel.inc:135: error: short jump is out of range runkernel.inc:210: error: short jump is out of range runkernel.inc:212: error: short jump is out of range runkernel.inc:253: error: short jump is out of range runkernel.inc:334: error: short jump is out of range runkernel.inc:557: error: short jump is out...

...odd; 255 is the kernel limit +max_cmd_len equ 1023 ; Must be odd; 255 is the kernel limit HIGHMEM_MAX equ 037FFFFFFh ; DEFAULT highest address for an initrd DEFAULT_BAUD equ 9600 ; Default baud rate for serial port BAUD_DIVISOR equ 115200 ; Serial port parameter diff -urN syslinux-3.08-pre10/runkernel.inc syslinux-3.08-pre11/runkernel.inc --- syslinux-3.08-pre10/runkernel.inc 2005-01-06 14:34:06.000000000 -0800 +++ syslinux-3.08-pre11/runkernel.inc 2005-05-08 14:47:03.000000000 -0700 @@ -1,4 +1,4 @@ -;; $Id: runkernel.inc,v 1.19 2005/01/06 22:34:06 hpa Exp $ +;; $Id: runkernel.inc,v 1.20 2005/05...

...6, I think I've found a problem in com32/lib/syslinux/load_linux.c that leads to cmdline being truncated unnecessarily when e.g. linux.c32 is used. The patch below fixes the problem for me. But I don't know, whether the patch is safe in all cases. I tried to reproduce the logic found in runkernel.inc, but I might have missed something. So, feel free to tell me what's wrong with it. Please CC me, as I'm not on the list. Thank you, Bodo ------------------------------------------------------------ From: Bodo Stroesser <bstroesser at ts.fujitsu.com> If a com32 modules uses lo...

...documentation, %ecx must contain the descriptor list byte length, but it's set with such list end address instead. Fix. Signed-off-by: Ahmed S. Darwish <darwish.07 at gmail.com> -- core/bcopy32.inc | 2 ++ core/bcopyxx.inc | 2 ++ core/bootsect.inc | 8 +++++--- core/runkernel.inc | 2 +- 4 files changed, 10 insertions(+), 4 deletions(-) diff --git a/core/bcopy32.inc b/core/bcopy32.inc index 6537546..ab60145 100644 --- a/core/bcopy32.inc +++ b/core/bcopy32.inc @@ -65,6 +65,8 @@ bcopy: jecxz .ret ; If len == 0: this marks the end of the list; dst indicates ;...

...rt jump is out of range ui.inc:515: error: short jump is out of range ui.inc:517: error: short jump is out of range ui.inc:523: error: short jump is out of range ui.inc:525: error: short jump is out of range ui.inc:534: error: short jump is out of range ui.inc:537: error: short jump is out of range runkernel.inc:135: error: short jump is out of range runkernel.inc:210: error: short jump is out of range runkernel.inc:212: error: short jump is out of range runkernel.inc:253: error: short jump is out of range runkernel.inc:557: error: short jump is out of range pxelinux.asm:1108: error: short jump is out...

Hi, I'm booting an qemu VM from a virtual disk. In the success case the virtual console shows something like this: SYSLINUX 4.05 0x54f93f16 Copyright (C) 1994-2011 H. Peter Anvin et al Loading vmlinuz......... Loading initramfs.img...................................ready. [ 0.000000] Initializing cgroup subsys cpuset <etc> In the failure case I'm seeing something like this:

...s environment. So far so good. > > I had a look at the syslinux code to find a proper place to ask for the > password. The idea is to add a parameter to the APPEND line which, when > present, makes ldlinux.sys ask for the actual password and append it to the > kernel command line in runkernel.inc. This should happen after the initial > and copyright messages. What is a good place to add a small module like > that, between all_read: and %include "runkernel.inc"? > The right way to do this is with a COM32 module. -hpa

...*cmdline, enum kernel_type type) local_boot(strtoul(kernel, NULL, 0)); } else if (type == KT_PXE || type == KT_BSS || type == KT_BOOT) { chainboot_file(kernel, type); - } else { + } else if (type == KT_KERNEL) { /* Need add one item for kernel load, as we don't use * the assembly runkernel.inc any more */ new_linux_kernel((char *)kernel, (char *)cmdline); -- 1.7.3.4

...he memory used is an easy and standard solution which works always. Obviously the CD must work also on systems with less memory than the limit specified. So, the need for this patch. -- Andrea Mazzoleni 935A 2D3C 5C70 BCD6 CB0C ED89 7C19 4321 6340 3F6D -------------- next part -------------- --- runkernel.inc.ori 2003-08-22 05:39:37.000000000 +0200 +++ runkernel.inc 2003-10-05 17:18:16.000000000 +0200 @@ -198,6 +198,9 @@ %if HIGHMEM_SLOP != 0 sub ebx,HIGHMEM_SLOP %endif + cmp [cs:HighMemSize],ebx ; Set the memory only if less than the BIOS detected + jb skip_this_opt + mov [cs:HighMemSize]...

Hello, I'm having a challenge with increasing vmalloc memory beyond 512M using pxelinux.0 to boot. This config works fine: --- # Configuration file # linux-2.6.20-1.2962.fc6 DEFAULT linux LABEL linux kernel kernels/vmlinuz-2.6.20-1.2962.fc6 append initrd=initrds/bladeinitrd-2.6.20-1.2962.fc6.img enforcing=0 vmalloc=512M --- If I increase vmalloc to 513M, I get errors

...ze dw 16 ; Defaults to 16 byte font UserFont db 0 ; Using a user-specified font ScrollAttribute db 07h ; White on black (for text mode) ; ; Stuff for the command line; we do some trickery here with equ to avoid ; tons of zeros appended to our file and wasting space --- syslinux-2.08.orig/runkernel.inc 2003-08-22 05:39:37.000000000 +0200 +++ syslinux-2.08/runkernel.inc 2003-12-18 23:16:18.000000000 +0100 @@ -156,20 +156,32 @@ .notkeep: %endif push es ; Save ES -> real_mode_seg push cs pop es...

...ze dw 16 ; Defaults to 16 byte font UserFont db 0 ; Using a user-specified font ScrollAttribute db 07h ; White on black (for text mode) ; ; Stuff for the command line; we do some trickery here with equ to avoid ; tons of zeros appended to our file and wasting space --- syslinux-2.08.orig/runkernel.inc 2003-08-22 05:39:37.000000000 +0200 +++ syslinux-2.08/runkernel.inc 2003-12-18 23:16:18.000000000 +0100 @@ -156,20 +156,32 @@ .notkeep: %endif push es ; Save ES -> real_mode_seg push cs pop es...

Hello Peter, The attached patch contains three small (although 2 of them are fundamental :) fixes for pxelinux 1. Alignment error when more than one initramfs are loaded using initrd - the alignment of the last disk is discarded in calculations but is ALWAYS present when the loading procedure is called. As a result - the second image (cpio) is not recognized. 2. On some platforms

...gh CPU contention can cause similar symptoms. An 8vCPU VM needs 8 idle cores to have execution time. How many vCPUs (vCPU = vSockets * vCoresPerSocket)? Physical cores (not counting CPU threading)? > Also, can someone point me to the code that emits the dots while loading the > file? core/runkernel.inc calls dot_pause in core/abort.inc -- -Gene

...> su_cmd_line_ptr resd 1 ; 0228 > su_ramdisk_max resd 1 ; 022C > > But this puts su_ramdisklen at same address as su_bsklugeoffs, and so > all items after su_ramdisklen are 4 bytes off! > > Due to this when memdisk from their ISO is loaded, runkernel.inc looks > at su_cmd_line_ptr instead of at su_ramdisk_max, finds 0 there, and so > loads image at 0 - 0x5A000 = 0xFFFA6000. But there is no ram at > 0xFFFA6000, and so it does not quite work. > > So in addition to the fixing su_ramdisklen in kernel.inc it would be > nice i...

...using the 2.6 kernel feature initramfs. The resulting combination of a 2M kernel and a 45M file system was a file around 47M. When I tried to boot this kernel and file system combination using pxelinux, I got the error message "Invalid or corrupt kernel image.". I tracked this to the file runkernel.inc at the label "is_linux_kernel:" where it checks to see if the kernel is over 8M and determines that it is corrupt if it is. Commenting out the first two lines after the label which are the 8M check and jump to kernel_corrupt will allow me to use pxelinux to boot my 47M kernel and fi...

...d appears to load the kernel and initrd images, but reboots the system when it tries to run the kernel. When I use either isolinux.bin and isolinux-debug.bin, the last messages I see on screen are: Loading kernel....... Loading initrd.................. Ready. I've enabled the %debug block in runkernel.inc (line 470) to wait for a key to be pressed, and it does get to that point. I've been able to successfully boot the same kernel and initrd images using GRUB (via a network boot), I can boot my ISOLINUX ISO in a virtual environment (Parallels on Mac), and I can also boot a Ubuntu LiveCD ( 6....

Hello sylvian Thanks. I use kernel 2.4.3 so far, and the Linux Progress Patch seems to start at 2.4.13.... What I don't understand is, why the kernel whipes out the VGA-display, as both Syslinux and the kernel is setup for serial-console. best regards ole at danelec.dk * danelec electronics a/s * Blokken 44 * DK-3460 Birkeroed * DENMARK * Phone: +45 45821879 * Fax: +45 45821979 *