Bug#943845: syslinux-common: error messages with grml boot stick
On Wed, 30 Oct 2019 22:41:48 +0100 Sven Joachim wrote: > On 2019-10-30 21:03 +0100, Lukas Schwaighofer wrote: > > 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. Unfortunately syslinux does not offer any "installer" to do that (nor does the Debian package). The admittedly poorly documented installation procedure is more or less to run the installer and copy any modules you need yourself to the correct folder. `syslinux -d boot/syslinux /dev/sdc1` does not install any c32 modules. This means any c32 modules present on your medium were copied by grml2usb. I don't know the details of how grml2usb installs syslinux, but they need to make sure whatever is installed to the volume boot record (`syslinux` or `extlinux` command) is consistent with the c32 modules. Either both must come from the host system or both from the installed medium. Regards Lukas
Bug#943845: syslinux-common: error messages with grml boot stick
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 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
Upcoming stable point release (10.2)
Hi, The next point release for "buster" (10.2) is scheduled for Saturday, November 16th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Processed: Re: Bug#943845: syslinux-common: error messages with grml boot stick
Processing control commands: > tags -1 + moreinfo Bug #943845 [syslinux-common] syslinux-common: error messages with grml boot stick Added tag(s) moreinfo. -- 943845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#943845: syslinux-common: error messages with grml boot stick
Control: tags -1 + moreinfo Hi Sven, thanks for your report! On Wed, 30 Oct 2019 18:58:12 +0100 Sven Joachim 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. 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? Is the image bootable when using `qemu-system-i386`? If all of the above does not help narrow down the problem, can you provide me with the necessary commands to build a similarly broken image myself? Thanks for your help Lukas
Bug#943845: syslinux-common: error messages with grml boot stick
Package: syslinux-common Version: 3:6.04~git20190206.bf6db5b4+dfsg1-1 Severity: important 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: ` There was supposed to be a nice boot menu, but since vesamenu.c32 failed to load it was not displayed. TAB completion at the boot prompt and actually booting worked, though. This may be related to #918915, although that bug is already archived. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.8-nouveau (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information
Re: Scheduling 10.2
Hi all Sorry for the late reply El 21/10/19 a las 21:26, Adam D. Barratt escribió: > Hi, > > It's (really past) time to consider a date for the second buster point > release. > > I've listed some suggested dates below; please indicate which you would > be available for. > > - November 2nd > - I'm not available; also means that the freeze would have to be this > coming weekend > - November 9th > - November 16th > - November 23rd > - November 30th > - a little late, and I'm not available Any weekend of November (except the 2nd) works for publicity. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
