similar to: Boot failed!

This version cleans up the Ethersel (PCI config probing) changes I have been iterating with Alex Heinz. It's not the same code (so please test, especially Alex), but it should work the same. As before, if you have a machine for which 2.13 worked and 3.0x hasn't worked, please test this version too. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

Hi. I've ever wondered how nuch timeis left to timeout while waiting at the boot prompt, so I've writen this small patch to show it. This add a configuration command 'showtimeout'. If you like the patch I could improve it (for example to show the timeout in decimal because now it uses the writehex functions) Regards. -- ______ ________ / / \/ /___ ) I N T E G

I tried to replace display_labels asm code (ui.inc) with new C code (pm_display_labels), but the data i access in command_line doesn't seem to be always up to date. The patch i am working on is only for PXELINUX because of different vkernel structure: diff --git a/core/com32.inc b/core/com32.inc index 111590c..f19df7c 100644 --- a/core/com32.inc +++ b/core/com32.inc @@ -135,6 +135,7 @@

Hello List, I have below a patch (against Syslinux-1.62), which adds a pseudo-kernel 'swap' which swaps device numbers of the boot device and the first harddisk. It was made for a system equipped with a DiskOnChip (www.msys.com) device which 'steals' the device# of teh first harddisk, This patch is used to enable the syslinux on the DoC to continue booting from the harddisk as if

Well, with this simple patch I'm able to load initrd from a different disk. It's not finished, it's just to ask you if I'm going in the right direction... I have also some suggestion/question: - many boot sector I saw use [bp+xx] addressing to gain some bytes. Why don't you use such method? - had syslinux been tested with usb floppy? You test dl however using usb floppy dl ==

Well, with this simple patch I'm able to load initrd from a different disk. It's not finished, it's just to ask you if I'm going in the right direction... I have also some suggestion/question: - many boot sector I saw use [bp+xx] addressing to gain some bytes. Why don't you use such method? - had syslinux been tested with usb floppy? You test dl however using usb floppy dl ==

From: Gene Cumm <gene.cumm at gmail.com> COMBOOT API: Add calls for directory functions; Implement most only for FAT (SYSLINUX). Uses INT 22h AX= 001Fh, 0020h, 0021h and 0022h to prepare for the COM32 C functions getcwd(), opendir(), readdir(), and closedir(), respectively. INT22h, AX=001Fh will return a valid value for all variants. INT22h, AX= 0020h, 0021h, and 0022h are only

From: Gene Cumm <gene.cumm at gmail.com> COMBOOT API: Improve readdir. Now returns C struct stat st_mode compatible data in DX rather than the raw data from a FAT filesystem or C struct dirent d_mode compatible data. Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- If I return something that's compatible with the C struct stat st_mode member, this can be used for more

On Thu, Oct 08, 2015 at 01:24:26AM +0200, Geert Stappers via Syslinux wrote: > On Wed, Oct 07, 2015 at 05:58:51PM -0500, Clements, James wrote: > > > Correct me if I am wrong but if I understand correctly, syslinux.efi is > > what drives the request for ldlinux.e64. Is there a way we can enable > > some debug somehow to see why the request for ldlinux.e64 includes >

From: Gene Cumm <gene.cumm at gmail.com> COMBOOT API: Add calls for directory functions; Implement most only for FAT (SYSLINUX). Uses INT 22h AX= 001Eh, 001Fh, 0020h and 0021h to prepare for the COM32 C functions getcwd(), opendir(), readdir(), and closedir(), respectively. INT22h, AX=001Eh will return a valid value for all variants. INT22h, AX= 001Fh, 0020h, and 0021h are only

Hi, I have a problem with the extern declarations of optarg, optind, etc. We're currently moving getopt from being a statically linked function to a dynamically linked function as part of the Cygwin DLL. On Windows, this requires to generate special symbols (__imp__optarg, etc.), which is done by marking the exported variables in the corresponding header. Instead of extern char *optarg;

#!/bin/bash # a small shell script to: # 1) make a simple asm program # 2) compile that program with `nasm' # 3) convert resulting .bin to a .img with `dd' # 4) boot the reulting "hello.img" with qemu/kvm # I think this qualifies as a bootloader, sort of # sincerely hope it helps address Mr. Guilmette curiousity # -chris graff printf ' BITS 16 jmp

From: Gene Cumm <gene.cumm at gmail.com> SYSLINUX/COMBOOT: Abstract searchdir and fix the opendir call Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- First, change comboot.inc such that INT 22h AX=0020h (opendir) is about as simple and similar in behavior to INT 22h AX=0006h (openfile). Next, rename the function searchdir to searchdir4any, create a new function called

Hi, i am looking now at the code which i assume loads the rest of isolinux.bin. The entry point for program execution from the MBR is obviously at http://git.zytor.com/syslinux/syslinux.git/tree/core/isolinux.asm#n186 (Do i get it right that this is the Intel syntax ? (Gronfff)) If POP yields the victim of the most recent not yet popped PUSH, then this does not look correctly coordinated

Hi all, I recently ran into some problems with rsync. My plan is to renew some of our old administration concepts from early 90's, I already replaced rdist with rsync a few years ago. Because of the rdist legacy, the current method requires synchronizing files into 6 different locations, {/alt,/usr/alt}/{hostdep,sysdep,hutdep}, which in turn are prioritized by a tool that just symlinks

From: Gene Cumm <gene.cumm at gmail.com> CORE/cache: add cache priority parameter; Passing in DX=0 forces the cache entry to stay at the least recently used spot. Any other value allows it to continue on previous behavior of most recently used position in the list. Change ldlinux.asm and extlinux.asm (the only 2 users of cache) to pass in DX=1. Push/Pop DX unless it's definitely safe

hpa, Seeing your post about 3.71, I wanted to get a message out even though I don't have the stats right now. I am having a problem with memdisk with a lot of shuttle computers, but also affects a variety of other hardware (low though, 5%? less?). The image that I can most reliably test against is the Hitachi Drive fitness Test.

Recently a patch by HPA was added to the elflink branch, "isolinux: Clear upper half of EDX before using..." http://git.zytor.com/?p=syslinux/syslinux.git;a=commit;h=870b84dd8714d dfccc9288025331423efa6d76b7 The patch was then applied to the firmware branch too. The patch solves an issue introduced by a prior commit "isolinux: Update LBA in getlinsec loop". Since the

Hi, These patches contain support for some features that are already in Syslinux 4 but weren't working properly on the elflink branch. It's another step closer to feature parity with Syslinux 4. Having to jump through the comboot API for localboot support is less than ideal and I'll eventually fix that, probably when we move a big chunk of code from asm to C. Also, there's a

Attached patch allows isolinux to boot from a CDROM attached to a NCR/Symbios/LSIlogic SCSI controller (bios version 4.19). It appears this bios can't read more than 1 sector at the time using the ah=42h int13 call. The isolinux boot was failing early on when 4 sector are read. (bios returned error 0 !) I'm not sure if the same 'getlinsec' routine is called upon later to load