Difference between revisions of "Bering-uClibc 5.x - User Guide - Appendices - Troubleshooting/FAQ"
From bering-uClibc
(→failed to load com32 file vesamenu.c32) |
(→Booting from my new USB key fails...) |
||
| Line 1: | Line 1: | ||
| − | == | + | == My freshly made USB key won't boot, what's wrong with the instructions ? == |
| − | + | ||
| + | I get this cryptic syslinux message: "failed to load com32 file vesamenu.c32" ! This is because the syslinux version used to create the USB key bootloader ldlinux.sys does not match the *.c32 files version present in the Bering-uClibc 5.3.1/syslinux distribution directory. Whatever syslinux version you are using, make sure to copy that syslinux's "hdt.c32, menu.c32 and vesamenu.c32" files to your USB /syslinux directory. At the time of this writing, latest version 6.0.3 of syslinux also complains it is missing some more *.c32 files (libutil.c32 ...), so again copy them in your /syslinux directory. Do not use the *.c32 files present in the distribution unless you know from which syslinux version they come from. | ||
| + | |||
=todo= | =todo= | ||
Revision as of 20:54, 19 April 2015
My freshly made USB key won't boot, what's wrong with the instructions ?
I get this cryptic syslinux message: "failed to load com32 file vesamenu.c32" ! This is because the syslinux version used to create the USB key bootloader ldlinux.sys does not match the *.c32 files version present in the Bering-uClibc 5.3.1/syslinux distribution directory. Whatever syslinux version you are using, make sure to copy that syslinux's "hdt.c32, menu.c32 and vesamenu.c32" files to your USB /syslinux directory. At the time of this writing, latest version 6.0.3 of syslinux also complains it is missing some more *.c32 files (libutil.c32 ...), so again copy them in your /syslinux directory. Do not use the *.c32 files present in the distribution unless you know from which syslinux version they come from.
