search for: vesalinux

On Wed, Aug 5, 2015 at 3:03 PM, Oscar Roozen via Syslinux <syslinux at zytor.com> wrote: > Unfortunately I can't test anymore until Friday. Maybe gnu-efi got > updated? I seem to remember seeing a shell script pulling in the > newest version during compilation... It's version locked to a certain commit ID. -- -Gene

...8702009 crashed because of some http pathprefix bug 8702009 contains the multinic bug so wouldn't work anyway e466d24 solves the mutlinic bug AND the http pathprefix bug e466d24 kept crashing on me because I mixed up libraries from 8702009 e466d24 still has an issue with png's in vesalinux causing crashes <<< This is a good report. Thanks ! Anyone there knows what's the fix in e466d24 solving the http pathprefix prefix issue? Best, Patrick

...ich I was referred by Gene in this mail: http://www.syslinux.org/archives/2015-August/023893.html This commit solves the multinic bug that affected my test machine. === end === I made some progress on the crashing issue. You all were right, they are not related. After the fix for multinic, vesalinux was the culprit. I probably messed up by mixing various versions of *.c32 modules, but right now commit e466d24 only crashes if I use vesamenu.c32 AND use a PNG for a background. If I comment out the PNG, the system boots fine. (ie. it really loads and runs the intended vmlinuz and initrd). No...

Updating myself again: On 07-08-15 16:03, Oscar Roozen wrote: > e466d24 still has an issue with png's in vesalinux causing crashes I can confirm this remaining crash is caused by the line "MENU BACKGROUND bootlogo.png". The original bootlogo.png is 640x480. Forcing the videomode with "MENU RESOLUTION 640 480" did not resolve the crashes, nor did resizing the png to 1024x768 and forcing...

...se of some http pathprefix bug > 8702009 contains the multinic bug so wouldn't work anyway > e466d24 solves the mutlinic bug AND the http pathprefix bug > e466d24 kept crashing on me because I mixed up libraries from 8702009 > e466d24 still has an issue with png's in vesalinux causing crashes > <<< > > This is a good report. Thanks ! > > Anyone there knows what's the fix in e466d24 solving the http pathprefix prefix issue? Looking further it could also be crashing because of some structure not initializing due to the multinic issue. There is...

>>> On 07-08-15 16:03, Oscar Roozen wrote: e466d24 still has an issue with png's in vesalinux causing crashes I can confirm this remaining crash is caused by the line "MENU BACKGROUND bootlogo.png". <<< Since last week I've been able to reproduce this problem. This is a weird bug affecting zlib but it looks like a compiler issue (v4.7.2) Please implement thes...

...n thread. Right now I have the following issues discussed in these two threads i started last week: 1) qemu + ipxe.rom + syslinux = 0xC (discussed in the other thread) 2) HP FW + ipxe.efi + syslinux = 0xC (also discussed there) 3) multinic (solved) 4) crashing when multinic fails 5) crashing when vesalinux fails 6) possibly some stupidity on my part with lib*.c32 so I have to retest 5. 7) suddenly solving 4 after recompiling with extra debugging info. 8) a possible problem with printf not working in EFI mode 9) running out of allocated time (not really a syslinux issue) (Where crashing == exceptions...

On 05-08-15 04:17, Ady via Syslinux wrote: >> Now... why is vesamenu.c32 crashing like it does now? Why is the version >> I tried without Gene's latest patches crashing before even beginning to >> load the first stage: ldlinux.e64? > I think you were "hinted" about this before. About what? Did I miss something obvious? I now know why it did not load