We have a couple of Beaglebones. Our LAN is 90% Windows with a windows domain server, and a few Linux machines. I put a RCN Ubuntu image on one of the Beaglebones. It was unclear to me how to connect to it, and I have never managed to connect using the build in serial port. Eventually I found it had been assigned an IP address, and spent several weeks experimenting with it. I have never even tried to connect to it via a Windows box, only Linux. (Except that I did put a test web page on it and accessed that.)
Over last weekend it apparently had a hardware failure. It appears to be booting (per the LEDs), but it was no longer possible to connect to it. It was also tested with the ‘as-shipped’ SD card with the angstrom image, with different cables, and by different developers trying to connect to different PCs. No joy.
So I am now using a different BeagleBone, but I can only connect to it on our network when using either the unmodified ubuntu image originally from
Or the original angstrom SD card.
If I try with any on which I rebuilt the kernel :
then the BB does not appear on the LAN - even though this identical configuration worked on the previous BeagleBone.
I assume that the identity of the card is partly in the SD card file system (‘hostname’), but that the network would identify it from the mac address. So I booted with the angstrom image, noted the mac address, rebooted with the ubuntu image and looked for that mac address with a network scanner. This worked with the original image referenced in the link above, but for the built kernel images an address was not to be found.
I have some further confusion in that I have connected to an angstrom image using 192.168.7.2, as per the docs, which implied that this was a fixed address. However, I have also seen the same angstrom image, on the same BB, as an address that was obviously assigned by our server.
So I’m hoping that someone can educate me about how network connectivity is handled differently in all these two cases, and how I can reliably find and connect to any newly imaged BeagleBone. Could something critical have somehow gotten turned off in the kernel config, and if so, what should I be looking for?