[BusyBox] udhcp woes
Michael D. Miller
michael.miller at prga.com
Sat Nov 1 15:15:15 UTC 2003
I'm trying to get udhcp to run on a SH4 system using BusyBox 1.0 pre3. I
used the 10/25/03 snapshot of uClibc for building with Dan Kegel's 0.24
crosstool kernel. I have a SMSC 91C111 NIC. After I insmod it and run
udhcpc I get a strange error message I haven't been able to track down. The
"error," would imply a call to LOG with a level of LOG_ERR but nothing seems
to match up with the start of the string.
I created scripts under /usr/share/udhcpc before invoking udhcpc that are
the same as the old 0.9.8 version. If I set an IP for the NIC via ifconfig
I can ping other boxes so basic ethernet connectivity seems to be working.
So two problems:
1) how to get udhcpc to run? I'm doing an insmod on the NIC and it goes to
eth0. I'm not performing any additional ifconfig of eth0 before executing
udhcpc, and didn't give udhcpc any parameters. My /etc directory is empty
of any of the normal *.conf files.
2) where is this most unhelpful error message coming from and how can we fix
it?
A snippet of the display is:
SMSC LAN91C111 Driver (v2.0), (Linux Kernel 2.4 + Support for Odd Byte)
09/24/01
- by Pramod Bhardwaj (pramod.bhardwaj at smsc.com)
Eth0: SMC91C11xFD(rev:1) at 0xa4000300 IRQ:1 MEMSIZE:8192b NOWAIT:0 ADDR:
4d:44:
50:00:00:01
# udhcpc
info, client (v0.9.9-pre) started
error, m
error, m
#
Regards,
Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.busybox.net/pipermail/busybox/attachments/20031101/1c39d3d6/attachment.htm
More information about the busybox
mailing list