Bug#943845: syslinux-common: error messages with grml boot stick

[Sven Joachim <svenjoac@gmx.de>]

On 2019-10-30 21:03 +0100, Lukas Schwaighofer wrote:

> Control: tags -1 + moreinfo
>
> Hi Sven,
>
> thanks for your report!
>
> On Wed, 30 Oct 2019 18:58:12 +0100
> Sven Joachim <svenjoac@gmx.de> wrote:
>
>> Today I built myself a USB stick with grml on it (see #943838 for the
>> problems I had with that).  When booting an old 32-bit laptop with
>> this stick syslinux threw some error messages before its prompt:
>>
>> ,----
>> | Undef symbol FAIL: x86_init_fpu
>> | Failed to load libcom32.c32
>> | Failed to load COM32 file vesamenu.c32
>> | boot:
>> `----
>
> I'm unable to reproduce this at the moment using the syslinux version
> 3:6.04~git20190206.bf6db5b4+dfsg1-1 .
>
> I'm suspecting that there is somehow a mismatch between the version of
> syslinux/extlinux used while installing (i.e. running `extlinux -i`)
> and the c32 files installed on the medium.

Indeed, this was the case.  While the version of syslinux installed in
the boot sector was the one from Debian, the support files in the
boot/syslinux directory came from the grml iso.  After replacing them
with the files from /usr/lib/syslinux/modules/bios/ everything was fine.

> Can you check whether the c32 files installed on the medium
> (probably in /boot/syslinux or /boot/extlinux) match the one
> from /usr/lib/syslinux/modules/bios on the host system? If they do
> match, can you re-run the syslinux installation from the host system
> and then try again?

They do not match, but I have a question: how would I get those files
onto the boot medium with syslinux commands?  The naive command
"syslinux -d boot/syslinux /dev/sdc1" (or whatever device instead of
/dev/sdc1) does not do that, yet grml2usb apparently relies on it.

Cheers,
       Sven