Difference between revisions of "Bering-uClibc 5.x - User Guide - Appendices - Troubleshooting/FAQ"

From bering-uClibc
Jump to: navigation, search
Line 11: Line 11:
 
== My freshly made USB key won't boot, what's wrong with the instructions ? ==
 
== 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.
+
 
 +
 
 +
I get this cryptic syslinux message: "failed to load com32 file <code class="filename">vesamenu.c32</code>" ! This is because the syslinux version used to create the USB key bootloader <code class="filename">ldlinux.sys</code> does not match the <code class="filename">*.c32</code> files version present in the Bering-uClibc 5.3.1 <code class="filename">/syslinux</code> distribution directory.  
 +
 
 +
Whatever syslinux version you are using, make sure to copy '''that''' syslinux's "<code class="filename">hdt.c32, menu.c32 and vesamenu.c32</code>" files to your USB key <code class="filename">/syslinux</code> directory.  
 +
 
 +
At the time of this writing, latest version 6.0.3 of syslinux also complains it is missing some more <code class="filename">*.c32</code> files (<code class="filename">libutil.c32</code> ...), so again copy them in your USB key <code class="filename">/syslinux</code> directory.  
 +
 
 +
In other words, do not use the <code class="filename">*.c32</code> files present in the Bering uClibc distribution unless you know from which syslinux version they come from.
  
 
== My firewall randomly assigns eth0 to either of my two NICs on bootup... that is very bad ! ==
 
== My firewall randomly assigns eth0 to either of my two NICs on bootup... that is very bad ! ==

Revision as of 18:20, 24 April 2015

Appendices - Troubleshooting/FAQ
Prev Bering-uClibc 5.x - User Guide Next


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 key /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 USB key /syslinux directory.

In other words, do not use the *.c32 files present in the Bering uClibc distribution unless you know from which syslinux version they come from.

My firewall randomly assigns eth0 to either of my two NICs on bootup... that is very bad !

For those of you who missed it, there is a bbnameif.lrp package that address this problem. Add it to your LRP="root license local bbnameif dhcpcd keyboard ..." list of packages to load, reboot and make sure it is executed before /etc/init.d/ifupdown by adjusting /etc/init.d/nameif's RCDLINKS="2,S04". Pick any unused S0X number lower than ifupdown. Find this unused X number by looking at your /etc/rc?.d . For Bering uClibc 5.1.3, ifupdown uses S04, so I use S03 for nameif, since it is free for my setup. Don't forget to add /etc/init.d/nameif to local.local... and save your config, so your changes are there on the next bootup !

lrcfg
    3) Packages configuration
    3) local 
    1) list of files that should be saved
lrcfg
    s) Save configuration



Prev Up Next