All.
Just booted my PocketBeagle using the image
'bone-debian-9.1-iot-armhf-2017-09-21-4gb.img'. I downloaded the image,
unpacked it and used dd to copy it to a micro-SD card (old school, don't
want to use the GUI tool, whatever it's called). The PocketBeagle boots,
and from my Debian 8 host, I can log in using the serial terminal created
when I plug the PocketBeagle into the host USB port. So, I can confirm that
the Beagle is booted and seems to be running correctly. I logged in as root
and created a new user:
login: bomr
Password:
Last login: Fri Sep 22 07:47:37 UTC 2017 on ttyGS0
Linux beaglebone 4.4.88-ti-r125 #1 SMP Thu Sep 21 19:23:24 UTC 2017 armv7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
bomr@beaglebone:~$
The problem I'm having is with the 'virtual ethernet' that is supposed to
get created on my host computer. After the Beagle boots, I see two network
devices show up on my Debian host computer:
# /sbin/ifconfig
enx6064055efaeb Link encap:Ethernet HWaddr 60:64:05:5e:fa:eb
inet6 addr: fe80::6264:5ff:fe5e:faeb/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:40 errors:0 dropped:0 overruns:0 frame:0
TX packets:109 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6868 (6.7 KiB) TX bytes:21055 (20.5 KiB)
enx6064055efaee Link encap:Ethernet HWaddr 60:64:05:5e:fa:ee
inet6 addr: fe80::6264:5ff:fe5e:faee/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:39 errors:0 dropped:0 overruns:0 frame:0
TX packets:90 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6828 (6.6 KiB) TX bytes:12812 (12.5 KiB)
eth0 Link encap:Ethernet HWaddr 00:1e:33:93:d1:86
UP 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)
However, there seems to be nothing I can do to make those two devices work.
I've tried assigning IPs using *dhclient*. I've paddled around with Network
Manager, but I'm never really sure what it is actually doing. I see two
drivers report in *dmesg* when I plug the Beagle into the host USB port:
[4676809.800067] usb 1-2: new high-speed USB device number 116 using
ehci-pci
[4676809.932950] usb 1-2: New USB device found, idVendor=1d6b,
idProduct=0104
[4676809.932971] usb 1-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[4676809.932983] usb 1-2: Product: BeagleBone
[4676809.932993] usb 1-2: Manufacturer: BeagleBoard.org
[4676809.933002] usb 1-2: SerialNumber: 1736GPB20135
[4676809.940717] rndis_host 1-2:1.0 eth1: register 'rndis_host' at
usb-0000:00:12.2-2, RNDIS device, 60:64:05:5e:fa:eb
[4676809.945409] cdc_ether 1-2:1.2 eth2: register 'cdc_ether' at
usb-0000:00:12.2-2, CDC Ethernet Device, 60:64:05:5e:fa:ee
[4676809.947827] cdc_acm 1-2:1.4: This device cannot do calls on its own.
It is not a modem.
[4676809.948980] cdc_acm 1-2:1.4: ttyACM0: USB ACM device
[4676809.952381] usb-storage 1-2:1.6: USB Mass Storage device detected
[4676809.953491] scsi20 : usb-storage 1-2:1.6
[4676810.953237] scsi 20:0:0:0: Direct-Access Linux File-Stor Gadget
0404 PQ: 0 ANSI: 2
[4676810.957685] sd 20:0:0:0: Attached scsi generic sg3 type 0
[4676810.959726] sd 20:0:0:0: [sdd] 36864 512-byte logical blocks: (18.8
MB/18.0 MiB)
[4676810.960451] sd 20:0:0:0: [sdd] Write Protect is on
[4676810.960469] sd 20:0:0:0: [sdd] Mode Sense: 0f 00 80 00
[4676810.961211] sd 20:0:0:0: [sdd] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[4676810.988173] sdd: sdd1
[4676811.001349] sd 20:0:0:0: [sdd] Attached SCSI removable disk
>From above, it looks like I should be seeing eth1 & eth2 devices, but
instead I see those two oddly named devices that can't seem to do anything.
The Beagle shows up as a mass storage device, and I've run the script in
the Linux drivers part of the filesystem it provides, but all it does is
update a few udev rules that only seem to be related to the mass storage
part of the USB interface. I've tried mounting and unmounting the mass
storage part of the USB interface, and nothing seems to make a difference.
So, I'm looking for suggestions about how to make my Pocket Beagle into a
virtual ethernet device. I would like to be able to mount the Beagle as an
NFS share or have the Beagle mount my Debian host computer as a shared
filesystem, so I can easily test software written for the Beagle, but
developed on the host computer. Some time ago, I was able to easily make
the virtual ethernet work on a BBB, using the same host computer, but it
may have been a different host OS. I don't have access to the BBB for
comparative testing any more.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/457ee823-0548-446a-adbc-be2863f3d932%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
