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

From bering-uClibc
Jump to: navigation, search
(→‎My firewall randomly assigns eth0 to either of my two NICs on bootup... that is very bad !)
m (→‎My firewall randomly assigns eth0 to either of my two NICs on bootup... that is very bad !)
 
(19 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
{| summary="Navigation header" width="100%"
 +
! colspan="3" align="center" | [[Bering-uClibc 5.x - User Guide - Appendices - Troubleshooting/FAQ|Appendices - Troubleshooting/FAQ]]
 +
|-
 +
| width="20%" align="left"  | [[Bering-uClibc 5.x - User Guide - Appendices - Working with Disk Image Files|Prev]]
 +
! width="60%" align="center" | [[Bering-uClibc 5.x - User Guide]]
 +
| width="20%" align="right"  | [[Bering-uClibc 5.x - User Guide - Appendices - Troubleshooting/FAQ|Next]]
 +
|}
 +
----
  
  
−
== 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 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>" !
  
−
== My firewall randomly assigns eth0 to either of my two NICs on bootup... that is very bad ! ==
+
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.
  
−
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 !
+
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.
  
−
<pre>lrcfg
+
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.
−
3
+
−
3
+
−
1
+
−
</pre>
+
  
−
<pre>lrcfg
+
== My firewall randomly assigns <code class="filename">eth0</code> to either of my two NICs on bootup... that is very bad ! ==
−
s
+
 
−
</pre>
+
For those of you who missed it, there is a <code class="filename">bbnameif.lrp</code> package that address this problem.
 +
 
 +
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!
 +
 
 +
----
 +
{| summary="Navigation footer" width="100%"
 +
| width="40%" align="left"  | [[Bering-uClibc 5.x - User Guide - Appendices - Working with Disk Image Files|Prev]]
 +
| width="20%" align="center" | [[Bering-uClibc 5.x - User Guide|Up]]
 +
| width="40%" align="right"  | [[Bering-uClibc 5.x - User Guide - Appendices - Troubleshooting/FAQ|Next]]
 +
|}
 +
 
 +
[[Category:Bering-uClibc 5.x]]
 +
[[Category:User Guide]]

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 ?

See updated 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
Retrieved from "http://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_5.x_-_User_Guide_-_Appendices_-_Troubleshooting/FAQ&oldid=2677"