similar to: Possible memdisk issue

> I'm having trouble getting memdisk 6.03pre18 to boot large floppies and > wondering whether I'm doing something incorrectly. > > 1) Download http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz > 2) gunzip FDOEM.144.gz > 3) newmkfloppyimg.sh 8 FDOEM144.img fdoem_8mb.img > 4) newmkfloppyimg.sh 9 FDOEM144.img fdoem_9mb.img > 5) Use following pxelinux.cfg: > >

On 08Jul2014--09Jul2014, Ady, Peter Anvin, Gene Cumm, Bernd Blaauw, Shao Miller, Kenneth Davis, wrote: > [...] Thank you all for your responses. You helped me solve my problem. For anyone else that runs into similar trouble and finds this thread, here follow summaries of what I've learned. To recap, our PXE server holds Dell BIOS updates in FreeDOS floppy images booted via MEMDISK.

Hi All, I am following: http://www.linuxinsight.com/how-to-flash-motherboard-bios-from-linux-no-dos-windows-no-floppy-drive.html to make a bootable CD to flash my bios I get to mkisofs step, but what I get is not what I think I want. I dont understand if I unmount /tmp/floppy how the Mkisofs command of: mkisofs -o bootcd.iso -b FDOEM.144 FDOEM.144 how I get everything in /tmp/floppy Here is

On Tue, 08 Jul 2014 15:54, H. Peter Anvin wrote: > >On 07/08/2014 11:26 AM, Ady wrote: >> >> It's interesting that you ask this, because every document related to >> newmkfloppyimg.sh specifically recommends adding: >> floppy c=$CYLINDERS s=$SECTORS h=$HEADS >> to the MEMDISK arguments. >> > >It would be important for floppies to know

> On 08Jul2014--09Jul2014, Ady, Peter Anvin, Gene Cumm, Bernd Blaauw, Shao > Miller, Kenneth Davis, wrote: > > [...] > > Thank you all for your responses. You helped me solve my problem. For > anyone else that runs into similar trouble and finds this thread, here > follow summaries of what I've learned. > > To recap, our PXE server holds Dell BIOS updates in

On 07/09/2014 04:00 PM, H. Peter Anvin wrote: > > So this would seem consistent that this is the FAT12/FAT16 boundary that > breaks stuff. Perhaps FreeDOS has a problem with FAT16 on floppies? If I understand things correctly, a bootable floppy has two key pieces of executable code: the 512-byte boot sector, and the kernel loaded by that boot sector. The kernel can be large, and thus

Hi, Since which version of pxelinux.0 is understood in pxelinux.cfg/default that kernel http://host.lan/netboot/vmlinuz means vmlinuz should be transported over HTTP? Since which version of pxelinux.0 is it possible to boot on UEFI? Those questions elaborated: What I want is fast netboot UEFI servers. What I'm looking for is an advice which version of PXELINUX between version

Op 2014-07-23 om 17:57 schreef Gene Cumm: > On Wed, Jul 23, 2014 at 10:32 AM, Geert Stappers <stappers at stappers.nl> wrote: > > Hi, > > > > Since which version of pxelinux.0 is understood in pxelinux.cfg/default that > > > > kernel http://host.lan/netboot/vmlinuz > > > > means vmlinuz should be transported over HTTP? > > For non-EFI

On Wed, Jul 23, 2014 at 10:32 AM, Geert Stappers <stappers at stappers.nl> wrote: > Hi, > > Since which version of pxelinux.0 is understood in pxelinux.cfg/default that > > kernel http://host.lan/netboot/vmlinuz > > means vmlinuz should be transported over HTTP? For non-EFI systems, this has meant use HTTP services if available (ie, iPXE/gPXE or lwIP as in

On 07/09/2014 01:54 PM, Alexander Perlis wrote: > > Ah, this might explain things although I don't know what is meant by > "intended". First, to clarify, newmkfloppyimg calls mkdosfs 3.0.12, and > grabs H/S from the output and then computes C. For all the sizes I've > tried, newmkfloppyimg always tells me H=64 S=32 and then C is the > approximately the number

On Sun, 22 Jun, at 06:15:50PM, Andrew Rae wrote: > > Matt - I'd love to try it - but I'm not so good at fixing compiling > issues. right now I get stuck at being unable to 'make' the efi32 or > efi64 components due to an error: Andrew, could you try out syslinux-6.03-pre18? Peter pushed the release button yesterday and -pre18 contains my change. It would be good to

> > From: Matt Fleming [matt at console-pimps.org] > > Sent: 25 June 2014 07:39 > > To: Andrew Rae > > Cc: Gene Cumm; syslinux at zytor.com > > Subject: Re: [syslinux] testing out 6.03 network booting... > > > > Andrew, could you try out syslinux-6.03-pre18? Peter pushed the release > > button yesterday and -pre18 contains my change. It would be

[This email is either empty or too large to be displayed at this time]

Trying to PXE boot a Dell Optiplex 990 with BIOS A16, which has Intel Boot Agent 1.3.81 (2.1 build 089). It gets network and launches lpxelinux.0, I see the PXELINUX banner line, but there it hangs. I tried both 6.03-pre18 and 5.10, same hanging behavior. If I instead use pxelinux.0 or gpxelinux.0, either 6.03-pre18 or 5.10 or 4.07, there are no problems. The problem seems isolated to

On 9 Jul 2014 at 6:01, Gene Cumm wrote: Date sent: Wed, 9 Jul 2014 06:01:22 -0400 Subject: Re: [syslinux] isohybrid binary not in 6.03-pre18? (utils bt is in bios/utils?) From: Gene Cumm <gene.cumm at gmail.com> To: "Michael D. Setzer, II" <mikes at kuentos.guam.net> Copies to: Syslinux at zytor.com > > On Jul 9, 2014 5:15 AM, "Michael D. Setzer II" >

On Jun 29, 2014 9:37 AM, "Wissam Shoukair" <wissams at mellanox.com> wrote: > > Hi Peter, > > I approached you before on this issue that I?m having with the SYSLINUX 6.03-pre18 when booting with iPXE option ROM. > > The issue was reproduced on different OEMs, and also on 2 different cards (Mellanox and Intel), with latest and 2 years old iPXE code. > > Just

On Jul 9, 2014 6:11 AM, "Michael D. Setzer II" <mikes at kuentos.guam.net> wrote: > > On 9 Jul 2014 at 6:01, Gene Cumm wrote: > > Date sent: Wed, 9 Jul 2014 06:01:22 -0400 > Subject: Re: [syslinux] isohybrid binary not in 6.03-pre18? (utils bt is in bios/utils?) > From: Gene Cumm <gene.cumm at gmail.com> > To: "Michael D. Setzer,

Hi I keep trying syslinux on my testing machine with BIOS and btrfs on root partition. I use syslinux 6.03pre18, kernel 3.15.4. A number of btrfs related bugs has been fixed in syslinux 6.03 recently, but I still see one more. Syslinux stops booting my kernel from btrfs partition. The partition itself is fine - I can mount it from other kernel booted from USB. The partition superblock is fine,

> From: Matt Fleming [matt at console-pimps.org] > Sent: 25 June 2014 07:39 > To: Andrew Rae > Cc: Gene Cumm; syslinux at zytor.com > Subject: Re: [syslinux] testing out 6.03 network booting... > > Andrew, could you try out syslinux-6.03-pre18? Peter pushed the release > button yesterday and -pre18 contains my change. It would be good to > know whether it improves

On 30/06/2014 16:30, Alex Bligh wrote: > I've upgraded from syslinux-4.05 to syslinux-6.03-pre18 (pre11 was the same) > and am having some issues getting lua.c32 to work. I'm using lpxelinux.0 > if that's relevant. > > My boot file and the contents of default.lua are below. As you can see they > are fantastically simple. Essentially I'm just using lua to put the