I’ve been tinkering with these boards since their release, I recently pulled 2 of them out of storage to setup a mini weather station for my house.
Trouble is I can’t access them and wondering if I’m just missing the elusive obvious
2 boards (1 rev b, 1 rev c)
I’ve tried powering them via external DC adapter / usb
tried flashing them multiple times with various versions of Robert’s ubuntu flasher image & console sd driven
they will flash blue lights like their working
going so far is running through the cylon lights and then holding steady like they’ve finished correctly
but neither will register on my network through ethernet or be accessible through usb
ssh: connect to host 192.168.7.2 port 22: Connection timed out
I’m running ubuntu on my host system and can see them through
lsusb
Bus 005 Device 004: ID 0525:a4a2 Netchip Technology, Inc. Linux-USB Ethernet/RNDIS Gadget
I have added the udev rules
any ideas? seems like I’ve forgotten a simple step in the months since I last tinkered with one of these boards
I’ve always seen marginal success in USB connectivity with BBB. I recently acquired a couple of BBG, at first I thought these were solid, but now I am seeing problems.
There is a difference seen in the host computer from the shell command ifconfig -a.
Here is ifconfig -a for a working BBG:
The obvious difference is seen at eth4 for the non-working versus eth1 for the working board.
eth1 (the working board) is getting an inet address.
eth4 (the non-working board) is not getting an inet address.
The BBG which does not connect will keep trying over and over.
I am using Ubuntu 14.04.
sudo dhclient eth2 (or whatever is obviously the BBG from looking at ifconfig)
There is one line return and then nothing happens (after entering password due to sudo).
On a healthy board, at the first “sudo dhclient ethX”, there is a quick line feed and no messages.
The second time, I get
RTNETLINK answers: File exists
sudo dhclient eth2 (or whatever is obviously the BBG from looking at
ifconfig)
There is one line return and then nothing happens (after entering password
due to sudo).
"nothing happens"... on success, yes "nothing happens"..
check:
sudo ifconfig -a
On a healthy board, at the first "sudo dhclient ethX", there is a quick line
feed and no messages.
The second time, I get
RTNETLINK answers: File exists
That's an error, interface is already up and connected..
My mistake, I wasn’t clear at all. Allow me to restate…
There is one line return after issuing the command sudo dhclient eth2, and then the shell locks up.
There is no message returned. Only a blinking cursor and nothing further happens.
Let’s see if I can paste in what it looks like: