my experience is based on verdex + buildroot, so not sure if this translates
directly to overo, but here's hoping it'll help :)
is the kernel able to load the correct driver and recognize at boot up? for
my system (verdex + buildroot) you could change the device by calling make
ARCH=arm menuconfig in the linux dir (/build_arm_nofpu/linux-2.6.21gum/) or
you could directly modify the .config
I also remember adding appropriate entries in /etc/netwrok/interfaces:
iface eth0 inet dhcp
and, if loading as modules, add a line in /etc/modules:
smc91x # my network module different from default default #smc911x
#smc911x # comment out default
> I can not get eth0 working. When I "ifconfig eth0" I get the error "error
> fetching interface information: Device not found".
> I am using the beta-2.img.bz2 image on the Overo Tobi
View this message in context: http://www.nabble.com/eth0-Device-not-found-tp24551084p24560045.html
Sent from the Gumstix mailing list archive at Nabble.com.