Difference between revisions of "Bering-uClibc 5.x - User Guide - Appendices - Troubleshooting/FAQ"
(→My firewall randomly assigns eth0 to either of my two NICs on bootup... that is very bad !) |
(→My freshly made USB key won't boot, what's wrong with the instructions ?) |
||
Line 18: | Line 18: | ||
Whatever syslinux version you are using, make sure to copy the files "<code class="filename">hdt.c32, menu.c32 and vesamenu.c32</code>" that comes with it to 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. | Whatever syslinux version you are using, make sure to copy the files "<code class="filename">hdt.c32, menu.c32 and vesamenu.c32</code>" that comes with it to 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. | ||
− | 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 these in 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">libcom32.c32, libutil.c32</code> ...), so again copy these in your USB key <code class="filename">/syslinux</code> directory. |
== My firewall randomly assigns <code class="filename">eth0</code> to either of my two NICs on bootup... that is very bad ! == | == My firewall randomly assigns <code class="filename">eth0</code> to either of my two NICs on bootup... that is very bad ! == |
Revision as of 19:43, 15 January 2016
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
file's version present in the Bering-uClibc 5.3.1 distribution /syslinux
directory.
Whatever syslinux version you are using, make sure to copy the files "hdt.c32, menu.c32 and vesamenu.c32
" that comes with it to 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.
At the time of this writing, latest version 6.0.3 of syslinux also complains it is missing some more *.c32
files (libcom32.c32, libutil.c32
...), so again copy these in your USB key /syslinux
directory.
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 and reboot.
Go to the bbnameif package configuration and fill:
2) busybox nameif configuration 1st step like so: ############################################################## # give temporary names to your interfaces to avoid name clashes # this is used by a first run of nameif to set the interfaces # to names different than ethxx so they are somewhat unique. # To use this file enter your desired interface name # followed by it's MAC address ############################################################### #t-eth0 00:00:00:00:00:00 eth0a 93:0c:6d:86:22:cf eth1a 0b:1c:25:38:5a:af
1) busybox nameif configuration final step like so: ################################################################ # enter the final names for your interfaces here # To use this file enter your desired interface name # followed by it's MAC address ############################################################### #eth0 00:00:00:00:00:00 eth0 93:0c:6d:86:22:cf eth1 0b:1c:25:38:5a:af
and save your configuration... and reboot !
/etc/init.d/nameif
must be run while eth0
and eth1
are down, this can be done by making sure it is executed before /etc/init.d/ifupdown
runs. You might have to change /etc/init.d/nameif
's RCDLINKS="2,S04" depending on your lrp list of packages.
Find out which RCDLINKS /etc/init.d/ifupdown
uses by looking at your /etc/rc?.d
. Pick any unused S0X number lower than the one ifupdown
uses, and assign it to nameif
.
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 !
Prev | Up | Next |