Difference between revisions of "Bering-uClibc 4.x - Known Issues"
(mention that lwp's are not part of release yet) |
Davidmbrooke (Talk | contribs) (Added note about BusyBox ntpd "hang") |
||
| Line 7: | Line 7: | ||
This will be fixed in further releases. | This will be fixed in further releases. | ||
| + | |||
| + | '''Boot-time "hang" at "Starting BusyBox ntpd".''' | ||
| + | |||
| + | With some system configurations the boot process can appear to "hang" at the message "Starting BusyBox ntpd". | ||
| + | This is due to ntpd not being able to resolve an IP address for its default NTP server. | ||
| + | After some delay this will time-out (with the message <tt>ntpd: bad address '0.pool.ntp.org'</tt>) after which the boot process will continue. | ||
| + | |||
| + | The problem is that the <tt>dnsmasq</tt> package is part of the default "LRP" package list in <code class="filename">leaf.cfg</code>, and so is <tt>dhcpcd</tt> but the two are not connected together in their default configuration. | ||
| + | The solution is to configure <tt>dnsmasq</tt> to use the right "resolv-file" setting, as described [[Bering-uClibc 4.x - User Guide - IPv4 Networking - Configure Dnsmasq#Using dnsmasq with dhcpcd|here]] or to configure alternative packages as appropriate. | ||
| + | |||
| + | [[Category:Bering-uClibc 4.x]] | ||
Revision as of 18:41, 27 November 2010
Currently there is no ISDN support.
The developers has no testbed for ISDN. If you do need ISDN support, please drop us a note on leaf-user@lists.sourceforge.net, so we may get in contact with you and providing packages for testing.
lwp's for webconf are not included in the images.
This will be fixed in further releases.
Boot-time "hang" at "Starting BusyBox ntpd".
With some system configurations the boot process can appear to "hang" at the message "Starting BusyBox ntpd". This is due to ntpd not being able to resolve an IP address for its default NTP server. After some delay this will time-out (with the message ntpd: bad address '0.pool.ntp.org') after which the boot process will continue.
The problem is that the dnsmasq package is part of the default "LRP" package list in leaf.cfg, and so is dhcpcd but the two are not connected together in their default configuration.
The solution is to configure dnsmasq to use the right "resolv-file" setting, as described here or to configure alternative packages as appropriate.
