[syslinux] EFI: HP + syslinux = crash
Patrick Masotta
masottaus at yahoo.com
Wed Aug 5 01:01:53 PDT 2015
>>>
Okay, the code in efi/ uses Print() from gnu_efi, but generic code from
core/ like core/elflink/load_env32.c prints their messages and debugging
stuff using printf(). These messages end up nowhere. This may explain
why I never saw anything beyond a certain point, even with debugging
turned on.
<<<
isn't it redirected at all??
>>>
I was busy adding some code to dprintf.h to add a wrapper that converts
the dprintf calls to a APrint("%a", buf) calls when I got an idea... The
ILO4 environment provides a virtual COM2 port. I was reluctant to
hook something to COM1 as I have to order some hardware for that, but this
also works very well. A pity I didn't think of using it earlier.
<<<
You can set the com address for debugging (com1/com2/ whatever) if you like
>>>
Still miss the printf output, though, so error messages from the shared
code don't reach the user.
<<<
guau...
>>>
Got some result!
I was using 'vesamenu.c32' to display a menu. Changing this to
'menu.c32' resulted in a booting system! Okay, the menu is not that
beautiful, but the system boots very well right now.
Now... why is vesamenu.c32 crashing like it does now?
<<<
Are you still loading PNGs?
Have you tried vesamenu w/o a background image?
>>>
Why is the version I tried without Gene's latest patches crashing before even beginning to load the
first stage: ldlinux.e64?
<<<
when you do not see the transfer of ldlinux.e64 the chances are you are suffering the multi-nic bug.
If you see "anything" after syslinux.efi transferred correctly that tells us the multi-nic bug is gone and
there might be something else going on now.
Best,
Patrick
More information about the Syslinux
mailing list