Oscar Roozen
2015-Aug-05 17:25 UTC
[syslinux] EFI: HP + syslinux = crash [ brown paper bag update ]
Update: I added my debugging stuff (just a bunch of Print()s and dprintf()s) to the branch without the multinic fix to see if I could find a common cause somewhere. This is based on commit 8702009f. Where I expected the machine to crash again, it just exited back to the bootloader without crashing. So.. somehow adding this debug code solved the crashing problem? Or did it? Then I went back to the latest branch (e466d249) and lo and behold... It did not crash! Not even with the vesamenu.c32! The same binary! Okay, vesamenu.c32 is still crashing if I enable the bootlogo.png but otherwise it seems pretty stable.. What on earth could have 'cured' my machine? [ some time later ] I probably messed up in copying over libutil.c32 and libcom32.c32 along with the various versions of syslinux.efi. I'm still not sure what I did exactly everytime, so I will do more tests. But this could really be very embarrassing... I will wear a brown paper bag over my head for a while.
Oscar Roozen
2015-Aug-05 19:03 UTC
[syslinux] EFI: HP + syslinux = crash [ brown paper bag update ]
> I probably messed up in copying over libutil.c32 and libcom32.c32 along with > the various versions of syslinux.efi.On the other hand, there is no lib*.c32 involved in the case where it would not start to load ldlinux.e64 due to the multinic issue. So... How is it possible that a simple recompile with some debugging turned on, resolved the crashing issue. 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... -- Oscar Roozen Linux Developer oscar.roozen at brightcomputing.com Bright Computing BV Kingsfordweg 151 1043 GR Amsterdam The Netherlands Tel: +31 20 491 9324 www.BrightComputing.com
Gene Cumm
2015-Aug-05 22:43 UTC
[syslinux] EFI: HP + syslinux = crash [ brown paper bag update ]
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