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

From bering-uClibc
Jump to: navigation, search
(todo)
(My firewall randomly assigns eth0 to either of my two NIC's on bootup... that is very bad !)
Line 5: Line 5:
 
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 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.
  
== My firewall randomly assigns eth0 to either of my two NIC's on bootup... that is very bad ! ==
+
== 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 that address this problem. Get it and make sure it is executed before /etc/init.d/ifupdown by adjusting /etc/init.d/nameif RCDLINKS="2,S04". Use any free S0X number lower than ifupdown. Find this free 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 !
 
for those of you who missed it, there is a bbnameif.lrp that address this problem. Get it and make sure it is executed before /etc/init.d/ifupdown by adjusting /etc/init.d/nameif RCDLINKS="2,S04". Use any free S0X number lower than ifupdown. Find this free 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 !

Revision as of 21:29, 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.

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 that address this problem. Get it and make sure it is executed before /etc/init.d/ifupdown by adjusting /etc/init.d/nameif RCDLINKS="2,S04". Use any free S0X number lower than ifupdown. Find this free 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 3 1

lrcfg s