A few weeks ago, I bought 4 Tobi-Duo's, 4 Earth's, 1 Tobi, and some
odds & ends for power & console, etc. They all worked great initially. I
required 2 eth's for the end product and was doing development on the
Tobi with a usb ethernet device, using an 8g microSD for everything, and
then doing testing by inserting the card into one of the earth/tobi-duo
Over the weekend, I found one of the Tobi-Duo's no longer
would talk out eth1. I tried the same microSD card in the other setups,
they all worked fine. I had previously used this Duo for other things,
and eth1 worked fine. I figured, maybe it's something odd with my code,
maybe I misconfigured or goofed something in the kernel to cause it to
ignore eth1, so I booted it from a stock nand (which had already come on
the Earth, and had already worked in the past with both eth0 & eth1) and
got the same thing. This is a board which had previously worked, now
neither my own kernel nor the factory ones would work, and I tried all
the other Earth boards on that same Duo with the same results. It really
seems like the eth1 (the connector farthest from the power connector on
the duo) on this particular board is bad. The contents of /proc/net/dev
show only lo & eth0.
Or could it be something else? I have googled for
other problems, and I found & fixed the udev renaming/incrementing
issues with this, and a couple other little oddities. But basically, I
had booted it with no trouble, now I boot it and get nothing on eth1.
Get latest updates about Open Source Projects, Conferences and News.