Difference between revisions of "Bering-uClibc 5.x - User Guide - Appendices - Troubleshooting/FAQ"
m (→My firewall randomly assigns eth0 to either of my two NICs on bootup... that is very bad !) |
|||
(13 intermediate revisions by 2 users not shown) | |||
Line 9: | Line 9: | ||
− | == 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 ? == |
+ | [[Bering-uClibc_5.x_-_User_Guide_-_Installing_the_Disk_Image#Do_these_extra_steps_if_you_are_using_the_.2A_syslinux_vga..2A_images|See updated instructions !]] | ||
+ | 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> file's version present in the Bering-uClibc 5.3.1 distribution <code class="filename">/syslinux</code> directory. | |
− | + | ||
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 eth0 to either of my two NICs on bootup... that is very bad ! == | + | |
For those of you who missed it, there is a <code class="filename">bbnameif.lrp</code> package that address this problem. | For those of you who missed it, there is a <code class="filename">bbnameif.lrp</code> package that address this problem. | ||
Line 27: | Line 26: | ||
Add it to your <code class="filename">LRP="root license local '''bbnameif''' dhcpcd keyboard ..."</code> list of packages to load and reboot. | Add it to your <code class="filename">LRP="root license local '''bbnameif''' dhcpcd keyboard ..."</code> 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''' | ||
+ | Save your configuration and reboot! | ||
---- | ---- |
Latest revision as of 17:36, 13 June 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
Save your configuration and reboot!
Prev | Up | Next |