search for: 03dda0f1

On 11/11/2013 04:09 AM, Christian Hesse wrote: >> >> Let be know if you need any more info. > > Is anybody working on this? Is there a bug tracker I should report > this to so it does not get forgotten? Could not find one for > syslinux. > Hm... it is odd that 03dda0f1 etc. didn't fix this. Since this is extremely likely to be dependent on the memory map, this is likely to be very hard to determine without a debug trace, or at least the output of "meminfo.c32". -hpa

...gt; Let be know if you need any more info. > > > > > > Is anybody working on this? Is there a bug tracker I should report > > > this to so it does not get forgotten? Could not find one for > > > syslinux. > > > > > > > Hm... it is odd that 03dda0f1 etc. didn't fix this. > > > > Since this is extremely likely to be dependent on the memory map, this > > is likely to be very hard to determine without a debug trace, > > Will produce one. Is there a manual how to do this with syslinux? > > > or at > >...

...se wrote: > >> > >> Let be know if you need any more info. > > > > Is anybody working on this? Is there a bug tracker I should report > > this to so it does not get forgotten? Could not find one for > > syslinux. > > > > Hm... it is odd that 03dda0f1 etc. didn't fix this. > > Since this is extremely likely to be dependent on the memory map, this > is likely to be very hard to determine without a debug trace, Will produce one. Is there a manual how to do this with syslinux? > or at > least the output of "meminfo.c32&qu...

Christian Hesse <list at eworm.de> on Tue, 2013/10/22 13:14: > Christian Hesse <list at eworm.de> on Tue, 2013/10/22 12:56: > > Gene Cumm <gene.cumm at gmail.com> on Tue, 2013/10/22 06:35: > > > On Tue, Oct 22, 2013 at 5:41 AM, Christian Hesse <list at eworm.de> wrote: > > > > Hello everybody, > > > > > > > > iPXE builds