Bb xM no ethernet (hardware problem?)

GoogleGroups
1

I'm running Ubuntu 10.10 on my Bb xM. For many weeks I've had it
plugged into our router, and I've been accessing it via ssh.
Yesterday I had to move it, so I shut it down (shutdown -h now),
unplugged it, moved it, and plugged it back in. Now there's no
ethernet. ifconfig returns with lo and nothing else. The green and
orange LEDs are lit up, and the green one blinks now and then.

Have I forgotten to do something? How can I check the hardware?
BTW, my Ubuntu doesn't seem to have lspci. "route" returns entirely
empty.

I do have a card with Angstrom on it ... came with the Bb, I think,
but I've never done anything with it.

thanks,
gary

2

Hi Gary,

3

Hello,

Try the following commands, they worked on my bb xM:

sudo ifconfig -a
sudo dhclient usb1

Once you type the first command, you will retrieve 3 interfaces: lo, usb0 and usb1.

Then, the second command setup the network interface to work with usb1 (which is the name of the network interface, it´s like eth0 for desktops).

Good luck.

Best Regards,

Guilherme

4

Thanks for responding, Robert. Took me a while to get a terminal
working.
I've answered your questions below.

I also booted into Angstrom. The first time, I plugged in the
ethernet cable and every thing just worked. (although I did learn
that the network show up on usb0, not eth0). Later, I rebooted into
Angstrom with the ethernet cable already plugged in. No network. I
unplugged and I got a message "usb0: link down." I replugged, no
network. I unplugged and replugged again, finally the network came
up.

I tried unplugging an replugging on Ubuntu, no messages, no network.

I'll keep trying to find consistent behavior. In the meantime,
debugging pointers are appreciated.

FWIW, I paste the output of "ifconfig -a" below.

thanks, --gary

gary@omap:~$ ifconfig -
a
lo Link encap:Local
Loopback
          inet addr:127.0.0.1 Mask:
255.0.0.0
          inet6 addr: ::1/128
Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:
1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:
0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:
0
          collisions:0 txqueuelen:
0
          RX bytes:0 (0.0 B) TX bytes:0 (0.0
B)

usb0 Link encap:Ethernet HWaddr
26:29:06:61:5e:bd
          BROADCAST MULTICAST MTU:1500 Metric:
1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:
0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:
0
          collisions:0 txqueuelen:
1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0
B)

usb1 Link encap:Ethernet HWaddr a2:b7:0f:ee:
03:c6
          BROADCAST MULTICAST MTU:1492 Metric:
1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:
0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:
0
          collisions:0 txqueuelen:
1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Hi Gary,

> I'm running Ubuntu 10.10 on my Bb xM. For many weeks I've had it
> plugged into our router, and I've been accessing it via ssh.
> Yesterday I had to move it, so I shut it down (shutdown -h now),
> unplugged it, moved it, and plugged it back in. Now there's no
> ethernet. ifconfig returns with lo and nothing else. The green and
> orange LEDs are lit up, and the green one blinks now and then.

> Have I forgotten to do something? How can I check the hardware?
> BTW, my Ubuntu doesn't seem to have lspci. "route" returns entirely
> empty.

Give "lsusb" a try vs "lspci" (no pci bus)

gary@omap:~$
lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root
hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems
Corp.
Bus 001 Device 002: ID 0424:9514 Standard Microsystems
Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

For reference, what does "uname -r" return?

gary@omap:~$ uname -
r
2.6.35.9-l9

double check, what does: "dmesg | grep OMAP3" return?

gary@omap:~$ dmesg | grep
OMAP3
[ 0.000000] Machine: OMAP3 Beagle
Board
[ 0.000000] OMAP3630 ES1.0 (l2cache iva sgx neon isp
192mhz_clk )
[ 0.000000] OMAP3 Beagle Rev: xM
A
[ 2.680084] Not OMAP3
EVM!
[ 2.682830] Not OMAP3517 / AM3517
EVM!
[ 2.686645] OMAP3 Beagle/Devkit8000 SoC
init
[ 2.734344] Power Management for TI OMAP3.

5

Thanks for responding, Robert. Took me a while to get a terminal
working.
I've answered your questions below.

I also booted into Angstrom. The first time, I plugged in the
ethernet cable and every thing just worked. (although I did learn
that the network show up on usb0, not eth0). Later, I rebooted into
Angstrom with the ethernet cable already plugged in. No network. I
unplugged and I got a message "usb0: link down." I replugged, no
network. I unplugged and replugged again, finally the network came
up.

I tried unplugging an replugging on Ubuntu, no messages, no network.

I'll keep trying to find consistent behavior. In the meantime,
debugging pointers are appreciated.

Hi Gary,

I don't see anything obvious in the paste's...

Do you have usb1 defined in /etc/network/interfaces:

voodoo@beagle-xma-512mb:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug usb1
iface usb1 inet dhcp

?

gary@omap:~$ ifconfig - a

usb1 Link encap:Ethernet HWaddr a2:b7:0f:ee:
03:c6
BROADCAST MULTICAST MTU:1492 Metric:
1
RX packets:0 errors:0 dropped:0 overruns:0 frame:
0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:
0
collisions:0 txqueuelen:
1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

this looks good.. so "sudo dhclient usb1" should get you an ip..

gary@omap:~$ uname -r
2.6.35.9-l9

The good reliable, good..

gary@omap:~$ dmesg | grep OMAP3

[ 0.000000] OMAP3 Beagle Rev: xM A

(it found the right board, so the ehci power rail will be set correctly..)

Regards,

6

Thanks again Robert and Guilherme,

I needed "dhclient usb1"
(and I added those two lines to /etc/network/interfaces)

The odd thing is that I didn't need to do that in the past. I have to
execute that command manually after re-boot; connection is not made
automatically, but in the past it was automatic. I must have
accidentally changed something. At any rate, the problem was not with
the Beagleboard, so that's good news.

Thanks again, --gary