search for: e820h

..." for any kernel that has a hard-coded load address and that > linux.c32 and all 5.xx+ (they're actually the same code) are less > likely to be able to succeed in loading these kernels due to how the > core/linux.c32 responds to the memory map passed to it by the BIOS(INT > 15h E820h). > Not quite. "Ancient kernel" means Linux kernel boot protocol < 2.00. This hard-codes memory use at address 0x90000, which is almost universally occupied by the PXE stack. What we need to do is estimate how much memory will be freed up by the PXE stack on unload -- unless we...

> On 06/28/2013 05:32 PM, Patrick Verner wrote: > > I have updated syslinux in Parted Magic's test version to the 5.10 release. > > With 4.06 I booted plop like this: > > > > LINUX /boot/plpbt/plpbt.bin > > > > Now it says /boot/plpbt/plpbt.bin... ok > > Booting kernel failed: Invalid argument > > > > Other "extras" like

...stays resident and the memory it uses wont get overwritten, for example even when loading a kernel or by yet another comboot file? If the comboot file could be instructed to load in a reserved high segment, or even just after the BDA, the available memory reported by the bios (INT 12 and INT 15 AX=E820h) could be reduced, but I dont know if this approach will work under syslinux. >From the source, it looks like comboot_seg is 4000, right in the middle. Also, related to the first question, if I want to disable one of my ISR's just before loading a kernel, I need to execute another smaller c...

Like a lot of people, I am using SYSLINUX + MEMDISK to make a technician universal boot disk on a USB key (I have done the same with ISOLINUX and MEMDISK for a CD using Bart's method for bootable CDs) I *LOVE* Syslinux and MEMDISK, and what I can do with floppy images! I have a few problems that have cropped up, most notably the DOCMEMORY program (www.simmstester.com) boots fing, but the

Hi, It is possible for some BIOSes to return non-page-aligned values for the start and length of regions in the BIOS memory map (through int 15h, e820h). As a result, the initrd is loaded by linux.c32 (a provided com32 module) in a manner such that the last page contains both a portion of initrd and some BIOS data. The linux kernel treats this page as part of the ramdisk file system and ends up corrupting the BIOS data. Here is a patch (against...

...t useful project. I apologize in advance for posting this question as it is in part off topic, but I have searched extensively with little results. Are there any alternatives to memdisk for use with pxelinux for booting troublesome floppy images with such applications that fail to use INT 15h, AX=E820h. Having spent some time experimenting with diskemu's diskem1x.bin and cdshell's implementation of diskemu as a module for use with bootable cdroms, I have seen memdisk and diskemu work from a common loader as alternative kernels for booting floppy images (for use with bootable cd-rom). Is...

..."ancient kernel" for any kernel that has a hard-coded load address and that linux.c32 and all 5.xx+ (they're actually the same code) are less likely to be able to succeed in loading these kernels due to how the core/linux.c32 responds to the memory map passed to it by the BIOS(INT 15h E820h). Let's say the kernel must be loaded to 0x100000 but the core sees that the memory at that address is reserved (and not by itself). At this point, the core/linux.c32 refuses to execute it for safety reasons. My guess at the PXE-smasher is that the BIOS doesn't properly report the memory...

...ects so I can understand what i should > be looking at (bios i[?m guessing ] to understand why one wont work without > this setting and one wont work with it. They each use RAM differently. meminfo.c32 will print the results from INT 15h AH=88h, INT 15h AX=E801h, and the map from INT 15h AX=E820h. com32/lib/syslinux/load_linux.c:bios_boot_linux() line 180 is the code that deals with the option. Line 298 is where it's then added to the memory map. Details like make, model, BIOS/firmware revision, whether the machine is (U)EFI-based in CSM-mode versus a traditional BIOS system, exactly...

I"m sorry if this is not the correct place for this question but i have not been able to locate any documentation on the mem=size option for memdisk The only thing i have found is mem=size Mark available memory above this point as Reserved. But i'm not sure if this is accurate and i'd like to understand the purpose of this option I am PXE booting a LENOVO machine which

..." for any kernel that has a hard-coded load address and that > linux.c32 and all 5.xx+ (they're actually the same code) are less > likely to be able to succeed in loading these kernels due to how the > core/linux.c32 responds to the memory map passed to it by the BIOS(INT > 15h E820h). > > Let's say the kernel must be loaded to 0x100000 but the core sees that > the memory at that address is reserved (and not by itself). At this > point, the core/linux.c32 refuses to execute it for safety reasons. > > My guess at the PXE-smasher is that the BIOS doesn...