On Fri, 3 Apr 2015, Robert Nelson wrote:
> > not worried about that ... what would be useful is a dump from
> > "udevadm monitor" while plugging in the BBB, to at least see the
> > uevents to figure out what that would map to.
>
> here you go:
>
> https://gist.github.com/RobertCNelson/50175bfc8f4cb8c521fb
a quick note on what i've seen on my fedora rawhide box, just to
make sure i'm on the right track. i first plugged in my (A5C) BBB via
serial console and started minicom just so i could track the boot
process -- that seems to work fine. (booting from SD card console
image, just to be clear.)
i started
$ udevadm monitor
then plugged in the USB cable for networking, and while the board was
booting, i was seeing nothing from udevadm, which i thought was odd.
finally, via minicom, i got a "boot" prompt and, almost immediately
thereafter, this blast from udevadm:
KERNEL[68599.502843] add /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.4
(usb)
KERNEL[68599.503607] add
/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.4/4-1.4:1.0 (usb)
KERNEL[68599.504712] add
/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.4/4-1.4:1.0/net/eth0 (net)
KERNEL[68599.504763] add
/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.4/4-1.4:1.0/net/eth0/queues/rx-0
(queues)
KERNEL[68599.504784] add
/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.4/4-1.4:1.0/net/eth0/queues/tx-0
(queues)
KERNEL[68599.505519] add
/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.4/4-1.4:1.1 (usb)
KERNEL[68599.559377] move
/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.4/4-1.4:1.0/net/enp0s29u1u4 (net)
first observation was ... no module events. in addition, i suddenly
got a corresponding net interface on the fedora box, but with no IP
address:
enp0s29u1u4: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 90:59:af:4b:3b:8d txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
and on the BBB end, no "usb0" interface that i was expecting, just
this:
eth0 Link encap:Ethernet HWaddr 90:59:af:4b:3b:8b
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)
Interrupt:40
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:65536 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)
so, just to be absolutely clear, on your loaded debian box, USB
networking to the BBB works just fine with the stock console image,
and this:
https://gist.github.com/RobertCNelson/50175bfc8f4cb8c521fb
is what you see on the host end as it comes up. at least i know what's
missing and i'll keep poking around.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
