similar to: SYSLINUX 3.10-pre6

> Could you perhaps test the attached patch and see what it does to your > system? > -hpa > diff -u -r1.181 ldlinux.asm > --- ldlinux.asm 18 Jan 2005 13:13:50 -0000 1.181 > +++ ldlinux.asm 3 Aug 2005 00:28:18 -0000 > @@ -328,7 +328,7 @@ > ; > ; We have EDD support... > ; > - mov byte

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

A question was asked on the IRC channel about how to get the address of a real-mode symbol -- or any assembly symbol in general. The answer is that you have to declare it global. In NASM syntax: global func func: In GAS syntax: .globl func func: -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

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 i want to add the FreeBSD 6.2 release to our installserver according to the manual http://syslinux.zytor.com/archives/2007-April/008420.html But if I type FreeBSD-6.2 at the pxelinux boot prompt the created image load but nothing happens. ?boot: FreeBSD-6.2 Loading memdisk.... Loading

I have just pushed out SYSLINUX 3.10-pre9. Please test it out, especially everyone who has been working with me on various systems trying to get them to work, or have had recent breakage. -hpa

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.

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

Folks, I've just spun a 4.07 prerelease. People were asking for a release that contained the commits that have been sitting in the master branch, and I've heard that distros are packaging the master branch just to get at them. --- Matt Fleming (4): extlinux: Avoid dereferencing a garbage pointer Merge branch 'searchdir_leak-406' of

Hello all. Again I call upon the greats of this mailing list to help me with an issue related to MEMDISK - notably when paired with various Dell OptiPlex and Latitude systems. The issue presented itself sometime ago and I best dealt with it by remaining with version 3.83 of the SYSLINUX package. But valuing the improved changes fostered by newer versions, I would prefer to move forward with

Hi, I need a little information from you all. Kindly update me about the file systems that are supported by SYSLINUX for ramdisk image... Thanks in advance and regards, Pankaj Agarwal

Hello, While attempting to build syslinux-3.52-pre6 for testing (my SCSI machine won't boot from CD-ROM with 3.51) I hit this problem: nasm -O99 -f bin -DDATE_STR="'3.52-pre6'" -DHEXDATE="0x46c22b21" \ -DMAP=pxelinux.map -l pxelinux.lsr -o pxelinux.bin pxelinux.asm pxelinux.asm:1206: error: short jump is out of range nasm -version NASM version

Most excellent! The pre-compiled syslinux6.03-pre6 binaries work great! I'm able to load syslinux.efi and all necessary support libs. I get my expected syslinux boot menu. I've used syslinux 5 / vesamenu for yrs (Legacy PXE boots). So I know my way around from here. Thanks Gene & Feri. And thanks Peter, for making me feel better -- it's the TFTP protocol that's bizarre, I

Hello I just tested my pxelinux installation with 5.00-pre6. For the installation I did first the same steps as I did with 4.05. I copied the following files out of the archive into my /tftpboot folder: syslinux-5.00-pre6/core/pxelinux.0 syslinux-5.00-pre6/com32/menu/menu.c32 syslinux-5.00-pre6/memdisk/memdisk With only this files, it was not working and I also had to copy this two

I have decided to make SYSLINUX 2.10-pre6 a release candidate. Please test it out if you can; if it works OK I will release it as 2.10 some time in the middle of the week. Thanks! -hpa

I have, hopefully, found and fixed the issue with non-kernel binaries that appeared in 3.35. As a result, I have pushed out 3.36-pre6 and am classifying it as a release candidate. Please try it out, especially if you have had problems with 3.35. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

An ext3 patch for the latest Linus kernel is at http://www.uow.edu.au/~andrewm/linux/ext3/ The changes are quite small: - Tided up some code now that quotas in Linus and -ac kernels are synced up. - Fix a race which can cause a null-pointer deref in ext3_writepage(). This bug has been there for a long time, but only manifested in 2.3.13-pre for some reason. I've tested this pretty

Hi, just tried 1.73-pre6 pxelinux: - booting linux works - memdisk with 1.44M Dos image works - the 'kbdmap'-parameter fails: [..] Unknown keyword in config file. Missing parameter in config file. boot: - and it doesn't remap any keys. I tried 1.66 with the same config file and it works, it accepts 'kbdmap' and also remaps the keys. Regards, Josef

Hi, I tested this version and it works all right ! Thanks a lot for the quick fix. Do you still want to see the output in order to check everything is OK, or you don't need it ? --------------------- Sylvain Faivre EdifiXio - AIH Team +33 1 56 90 51 24 www.edifixio.com > -----Message d'origine----- > De : H. Peter Anvin [mailto:hpa at zytor.com] > Envoy? : mardi 18 novembre

Okay, this applies particularly to SYSLINUX, not ISO/PXE/EXTLINUX. If you have a system on which 2.13 boots and 3.0x don't, I would like to get as much information as possible about it. In particular, I would like to know: - What device are you booting from (floppy, USB, IDE harddrive...) - Motherboard manufacturer/model - CPU manufacturer/model (a dump of /proc/cpuinfo would