Wifi dongle issues (Edimax EW-7811UN) - some questions on BBB power options, and powered USB hubs

[Marcos Scriven]

I'm trying to get an Edimax EW-7811UN working on my BBB rev A5C, which is listed on the Beagleboard wiki as working: http://www.elinux.org/Beagleboard:BeagleBoneBlack#WIFI_Adapters

Frustratingly, it sort of works for a few minutes (I get an IP, and can log in), but then seems to stop.  I see no logs to suggest the dongle has disconnected, or any networking errors logs. I'm sure there's nothing wrong physically with the dongle, as I've tried two of them, both of which work fine in my Raspberry Pi for long periods

There appears to be three aspects here:

1) Driver issues - there seems to be the rtl8192cu in mainline kernel, and various dynamic kernel modules (such as https://github.com/pvaret/rtl8192cu-fixes) that apparently exist due to the drivers being flaky. I know the RaspberryPi kernel uses a very similar fork of the open source 'fixed' module, but is instead compiled into the kernel RPi uses in its distributions

 

2) Kernel version - related to the driver issues, but so far as I know the rtl8192cu driver in mainline has had some improvements in the 4.4 kernel. I've tried both at 4.1.x kernel (from Elias's 'Kamikazee' fork or Robert's image build), and Robert's own latest 4.4.9-ti-r25 kernel (of the 2GB ubuntu flasher variety). The problem is Elias's build is convenient as it has everything setup for the Replicape, but is an older kernel.

 

3) Power - this is the most opaque issue to me. I've tried both with and without a powered USB hub, but I've no way of telling if the USB hub is doing its job, and supplying power to the Wifi dongle directly, rather than asking the BBB host for it. I'm using this 'Amazon Basics' one, which appears to be a rebranded VIA labs model): https://www.amazon.co.uk/AmazonBasics-4-Port-USB-3-0-Plug/dp/B00E0NH7DQ/ref=sr_1_9?s=electronics&ie=UTF8&qid=1464001382&sr=1-9&keywords=amazon+usb+hub

Questions:

1) For an RTL8188CUS based chip, on a >= 4.4.9 kernel, am I best off using the builtin driver, or compiling the open source one?

2) Why does the wifi interface name change from wlan0 to wlx801f02a693cf upon connmanctl connection?

3) Why do I need to 'disable wifi' in connmanctl before enabling it a second time, for it to see 'wifi' as an available 'technology' 

4) What's my next step if things like 'dmesg' aren't showing any issues? (I'm not seeing the USB device repeatedly being disconnected/connected for instance, or repeated DHCP reqs or anything. In fact, between the device having a connection and not, I sometimes see not further dmesg logs at all.

5) If the BBB is powered via the mini-USB port, but I'm using a powered hub, is it still a problem for the BBB?

6) How can I tell for sure the powered hub is supplying power to the dongle instead of the BBB?

7) Eventually I'm going to attached the Replicape, which is itself will be powered by a computer PSU, and will actually provide the BBB with 5V through the cape. What would the USB power situation be then? Would the BBB host then be able to provide enough power?

 

It's the combination of driver vs open source dynamic module, kernel version, and opaque (to me) USB power issues that I think is making this Wifi connection flakiness frustrating.

Debug info:

uname 

Linux arm 4.4.9-ti-r25 #1 SMP Fri May 6 10:28:56 UTC 2016 armv7l armv7l armv7l GNU/Linux

lsusb

Bus 001 Device 003: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]

Bus 001 Device 002: ID 2109:2811 VIA Labs, Inc. Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lsmod

Module                  Size  Used by

ccm                     6653  2

arc4                    2019  2

rtl8192cu              52212  0

rtl_usb                 8788  1 rtl8192cu

rtl8192c_common        37683  1 rtl8192cu

rtlwifi                54043  3 rtl_usb,rtl8192c_common,rtl8192cu

mac80211              484877  3 rtl_usb,rtlwifi,rtl8192cu

cfg80211              417677  2 mac80211,rtlwifi

usb_f_ecm               9400  1

g_ether                 4976  0

usb_f_rndis            22191  2 g_ether

u_ether                11917  3 usb_f_ecm,usb_f_rndis,g_ether

libcomposite           43461  3 usb_f_ecm,usb_f_rndis,g_ether

pruss_intc              3592  0

snd_soc_simple_card     8385  0

pru_rproc              11295  0

omap_rng                4423  0

omap_sham              21629  0

pruss                  11615  1 pru_rproc

omap_aes_driver        18917  0

rng_core                7471  1 omap_rng

bluetooth             417817  2

rfkill                 18226  5 cfg80211,bluetooth

snd_soc_davinci_mcasp    16596  2

snd_soc_edma            1290  1 snd_soc_davinci_mcasp

snd_soc_omap            3058  1 snd_soc_davinci_mcasp

spi_omap2_mcspi        10764  0

snd_soc_hdmi_codec      5842  1

snd_soc_core          155592  5 snd_soc_hdmi_codec,snd_soc_davinci_mcasp,snd_soc_edma,snd_soc_omap,snd_soc_simple_card

snd_pcm_dmaengine       5209  2 snd_soc_core,snd_soc_omap

snd_pcm                82689  5 snd_soc_hdmi_codec,snd_soc_davinci_mcasp,snd_soc_core,snd_soc_omap,snd_pcm_dmaengine

snd_timer              19720  1 snd_pcm

snd                    59559  3 snd_soc_core,snd_timer,snd_pcm

soundcore               7601  1 snd

evdev                  10695  2

uio_pdrv_genirq         3539  0

uio                     8822  1 uio_pdrv_genirq

tilcdc                 26364  0

tda998x                12754  0

[Marcos Scriven]

Just to add, might be worth noting I'm using a serial connection to the BBB jtag to connect while I'm setting up the Wifi dongle (rather than SSH in over wired connection), to be sure the ethernet connection is not interfering. 

[Robert Nelson]

On Mon, May 23, 2016 at 6:23 AM, Marcos Scriven <mar...@scriven.org> wrote:

I'm trying to get an Edimax EW-7811UN working on my BBB rev A5C, which is listed on the Beagleboard wiki as working: http://www.elinux.org/Beagleboard:BeagleBoneBlack#WIFI_Adapters

Frustratingly, it sort of works for a few minutes (I get an IP, and can log in), but then seems to stop.  I see no logs to suggest the dongle has disconnected, or any networking errors logs. I'm sure there's nothing wrong physically with the dongle, as I've tried two of them, both of which work fine in my Raspberry Pi for long periods

There appears to be three aspects here:

1) Driver issues - there seems to be the rtl8192cu in mainline kernel, and various dynamic kernel modules (such as https://github.com/pvaret/rtl8192cu-fixes) that apparently exist due to the drivers being flaky. I know the RaspberryPi kernel uses a very similar fork of the open source 'fixed' module, but is instead compiled into the kernel RPi uses in its distributions

 

2) Kernel version - related to the driver issues, but so far as I know the rtl8192cu driver in mainline has had some improvements in the 4.4 kernel. I've tried both at 4.1.x kernel (from Elias's 'Kamikazee' fork or Robert's image build), and Robert's own latest 4.4.9-ti-r25 kernel (of the 2GB ubuntu flasher variety). The problem is Elias's build is convenient as it has everything setup for the Replicape, but is an older kernel.

He will move to v4.4.x when he's ready..  Elias's does a lot of work to make sure his Cape's works, so he will move when he's ready..

 

 

3) Power - this is the most opaque issue to me. I've tried both with and without a powered USB hub, but I've no way of telling if the USB hub is doing its job, and supplying power to the Wifi dongle directly, rather than asking the BBB host for it. I'm using this 'Amazon Basics' one, which appears to be a rebranded VIA labs model): https://www.amazon.co.uk/AmazonBasics-4-Port-USB-3-0-Plug/dp/B00E0NH7DQ/ref=sr_1_9?s=electronics&ie=UTF8&qid=1464001382&sr=1-9&keywords=amazon+usb+hub

Questions:

1) For an RTL8188CUS based chip, on a >= 4.4.9 kernel, am I best off using the builtin driver, or compiling the open source one?

It depends, the RTL8188's have been fussy, use either or, linux-headers-`uname -r` are in the repo for you to use..

 

2) Why does the wifi interface name change from wlan0 to wlx801f02a693cf upon connmanctl connection?

systemd does that: https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

 

3) Why do I need to 'disable wifi' in connmanctl before enabling it a second time, for it to see 'wifi' as an available 'technology' 

Because i have "wifi tether" enabled..

connmanctl> tether wifi off

 

4) What's my next step if things like 'dmesg' aren't showing any issues? (I'm not seeing the USB device repeatedly being disconnected/connected for instance, or repeated DHCP reqs or anything. In fact, between the device having a connection and not, I sometimes see not further dmesg logs at all. 

5) If the BBB is powered via the mini-USB port, but I'm using a powered hub, is it still a problem for the BBB?

6) How can I tell for sure the powered hub is supplying power to the dongle instead of the BBB? 

7) Eventually I'm going to attached the Replicape, which is itself will be powered by a computer PSU, and will actually provide the BBB with 5V through the cape. What would the USB power situation be then? Would the BBB host then be able to provide enough power?

Until you try powering the device via 5VDC power, there's not much to comment on above..

 

 

It's the combination of driver vs open source dynamic module, kernel version, and opaque (to me) USB power issues that I think is making this Wifi connection flakiness frustrating.

Personally, it smells like a power problem..

Regards,

--

Robert Nelson
https://rcn-ee.com/

[Wally Bkg]

On Monday, May 23, 2016 at 8:59:36 AM UTC-5, RobertCNelson wrote:

On Mon, May 23, 2016 at 6:23 AM, Marcos Scriven <mar...@scriven.org> wrote:

2) Why does the wifi interface name change from wlan0 to wlx801f02a693cf upon connmanctl connection?

systemd does that: https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

Great tidbit from that link, thanks! 

"I don't like this, how do I disable it?"

You pass the net.ifnames=0 on the kernel command line

Ubuntu 16.04 uses this scheme and it causes me grief when I use my BBB and multiple  BBG with the usb gadget Ethernet.   I've simple scripts to set up networking so the Ubuntu host can do NAT to give the bone internet access over the usb gadget, on the bone side its all the same (so far) but on the Ubuntu side the interface name changes with the board.  If there was a way to have multiple usb gadget interfaces (multiple bones) running  at the same time on a single host this might be helpful, but for me its just one more "oh crap, I forgot to change this :( " moment.

[Marcos Scriven]

Hi Robert

Thanks for the responses. I hope I didn't make it sound like I was demanding a new version of Kamikaze from Elias! I understand the whole reason for Kamikaze is that it 'just works' out of the box with the Replicape - the conundrum for me is whether I try and start with your image with a newer kernel (in the hope it has better kernel support for my wifi dongle), and repeat some of Elias's setup, or start with Kamikaze, and try and get a dynamic module working (which might not even work, and be a wasted effort if it works in a newer kernel).

Thanks to the joys of Amazon Prime Now, have ordered a 5v multi adapter, and unfortunately seeing the same behaviour. The voltage seems to be pretty stable at 5.10v:

I agree it 'smells like a power problem', but still getting the same issue with a 5V adapter.

Here's what I do to make a connection:

ubuntu@arm:~$ connmanctl disable wifi

Disabled wifi

ubuntu@arm:~$ connmanctl enable wifi

Enabled wifi

ubuntu@arm:~$ connmanctl scan wifi

Error /net/connman/technology/wifi: No carrier

ubuntu@arm:~$ connmanctl disable wifi

Disabled wifi

ubuntu@arm:~$ connmanctl enable wifi

Enabled wifi

ubuntu@arm:~$ connmanctl scan wifi

Scan completed for wifi

ubuntu@arm:~$ ping google.com

PING google.com (216.58.213.110) 56(84) bytes of data.

64 bytes from lhr25s02-in-f110.1e100.net (216.58.213.110): icmp_seq=1 ttl=54 time=13.8 ms

This works for a few minutes. Then:

ubuntu@arm:~$ ping google.com

PING google.com (216.58.213.110) 56(84) bytes of data.

From 192.168.1.109 icmp_seq=29 Destination Host Unreachable

I see nothing in dmesg that suggests the USB wifi dongle has disconnected or the connection itself has been dropped or being renegotiated in some way. 

Any guidance on what to try next would be gratefully received!

Here's the latest output of dmesg:

ubuntu@arm:~$ dmesg

[    0.000000] Booting Linux on physical CPU 0x0

[    0.000000] Initializing cgroup subsys cpuset

[    0.000000] Initializing cgroup subsys cpu

[    0.000000] Initializing cgroup subsys cpuacct

[    0.000000] Linux version 4.4.9-ti-r25 (root@b3-jetson-tk1-2gb) (gcc version 5.3.1 20160413 (Ubuntu/Linaro 5.3.1-14ubuntu2) ) #1 SMP Fri May 6 10:28:56 UTC 2016

[    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=50c5387d

[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache

[    0.000000] Machine model: TI AM335x BeagleBone Black

[    0.000000] cma: Reserved 24 MiB at 0x9e000000

[    0.000000] Memory policy: Data cache writeback

[    0.000000] On node 0 totalpages: 130560

[    0.000000] free_area_init_node: node 0, pgdat c0c299c0, node_mem_map df96d000

[    0.000000]   Normal zone: 1152 pages used for memmap

[    0.000000]   Normal zone: 0 pages reserved

[    0.000000]   Normal zone: 130560 pages, LIFO batch:31

[    0.000000] CPU: All CPU(s) started in SVC mode.

[    0.000000] AM335X ES2.0 (sgx neon )

[    0.000000] PERCPU: Embedded 13 pages/cpu @df923000 s24268 r8192 d20788 u53248

[    0.000000] pcpu-alloc: s24268 r8192 d20788 u53248 alloc=13*4096

[    0.000000] pcpu-alloc: [0] 0

[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 129408

[    0.000000] Kernel command line: console=ttyO0,115200n8 root=UUID=14a9c7d7-9990-49c6-92e1-7650b64af3fe ro rootfstype=ext4 rootwait coherent_pool=1M quiet cape_universal=enable

[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)

[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)

[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)

[    0.000000] Memory: 474396K/522240K available (7311K kernel code, 913K rwdata, 3700K rodata, 588K init, 906K bss, 23268K reserved, 24576K cma-reserved, 0K highmem)

[    0.000000] Virtual kernel memory layout:

                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)

                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)

                   vmalloc : 0xe0800000 - 0xff800000   ( 496 MB)

                   lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)

                   pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)

                   modules : 0xbf800000 - 0xbfe00000   (   6 MB)

                     .text : 0xc0008000 - 0xc0ac9000   (11012 kB)

                     .init : 0xc0ac9000 - 0xc0b5c000   ( 588 kB)

                     .data : 0xc0b5c000 - 0xc0c40658   ( 914 kB)

                      .bss : 0xc0c43000 - 0xc0d25b50   ( 907 kB)

[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

[    0.000000] Hierarchical RCU implementation.

[    0.000000]  Build-time adjustment of leaf fanout to 32.

[    0.000000]  RCU restricting CPUs from NR_CPUS=2 to nr_cpu_ids=1.

[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=1

[    0.000000] NR_IRQS:16 nr_irqs:16 16

[    0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts

[    0.000000] OMAP clockevent source: timer2 at 24000000 Hz

[    0.000011] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns

[    0.000029] clocksource: timer1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns

[    0.000041] OMAP clocksource: timer1 at 24000000 Hz

[    0.000220] Console: colour dummy device 80x30

[    0.000245] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'

[    0.000253] This ensures that you still see kernel messages. Please

[    0.000259] update your kernel commandline.

[    0.000277] Calibrating delay loop... 995.32 BogoMIPS (lpj=1990656)

[    0.046911] pid_max: default: 32768 minimum: 301

[    0.047047] Security Framework initialized

[    0.047060] Yama: becoming mindful.

[    0.047092] AppArmor: AppArmor disabled by boot time parameter

[    0.047253] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)

[    0.047266] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)

[    0.048036] Initializing cgroup subsys io

[    0.048067] Initializing cgroup subsys memory

[    0.048107] Initializing cgroup subsys devices

[    0.048123] Initializing cgroup subsys freezer

[    0.048138] Initializing cgroup subsys net_cls

[    0.048152] Initializing cgroup subsys perf_event

[    0.048166] Initializing cgroup subsys net_prio

[    0.048180] Initializing cgroup subsys pids

[    0.048236] CPU: Testing write buffer coherency: ok

[    0.048289] ftrace: allocating 33920 entries in 67 pages

[    0.132378] CPU0: thread -1, cpu 0, socket -1, mpidr 0

[    0.132506] Setting up static identity map for 0x80008240 - 0x8000828c

[    0.135970] Brought up 1 CPUs

[    0.135992] SMP: Total of 1 processors activated (995.32 BogoMIPS).

[    0.136000] CPU: All CPU(s) started in SVC mode.

[    0.137425] devtmpfs: initialized

[    0.155546] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3

[    0.173699] omap_hwmod: debugss: _wait_target_disable failed

[    0.227391] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns

[    0.229453] xor: measuring software checksum speed

[    0.266913]    arm4regs  :  1221.000 MB/sec

[    0.306908]    8regs     :  1093.000 MB/sec

[    0.346907]    32regs    :  1055.000 MB/sec

[    0.386908]    neon      :  1759.000 MB/sec

[    0.386915] xor: using function: neon (1759.000 MB/sec)

[    0.387011] pinctrl core: initialized pinctrl subsystem

[    0.388952] NET: Registered protocol family 16

[    0.392418] DMA: preallocated 1024 KiB pool for atomic coherent allocations

[    0.393615] cpuidle: using governor ladder

[    0.393637] cpuidle: using governor menu

[    0.398750] OMAP GPIO hardware version 0.1

[    0.411210] No ATAGs?

[    0.411242] hw-breakpoint: debug architecture 0x4 unsupported.

[    0.411816] omap4_sram_init:Unable to allocate sram needed to handle errata I688

[    0.411830] omap4_sram_init:Unable to get sram pool needed to handle errata I688

[    0.491022] raid6: int32x1  gen()   269 MB/s

[    0.559065] raid6: int32x1  xor()   192 MB/s

[    0.627007] raid6: int32x2  gen()   392 MB/s

[    0.694982] raid6: int32x2  xor()   235 MB/s

[    0.762927] raid6: int32x4  gen()   429 MB/s

[    0.830995] raid6: int32x4  xor()   272 MB/s

[    0.899071] raid6: int32x8  gen()   367 MB/s

[    0.966983] raid6: int32x8  xor()   239 MB/s

[    1.034918] raid6: neonx1   gen()  1452 MB/s

[    1.102934] raid6: neonx1   xor()   846 MB/s

[    1.170914] raid6: neonx2   gen()  1788 MB/s

[    1.238914] raid6: neonx2   xor()  1146 MB/s

[    1.306929] raid6: neonx4   gen()  1205 MB/s

[    1.374931] raid6: neonx4   xor()   995 MB/s

[    1.442917] raid6: neonx8   gen()   924 MB/s

[    1.510913] raid6: neonx8   xor()   804 MB/s

[    1.510920] raid6: using algorithm neonx2 gen() 1788 MB/s

[    1.510927] raid6: .... xor() 1146 MB/s, rmw enabled

[    1.510934] raid6: using intx1 recovery algorithm

[    1.519796] edma 49000000.edma: TI EDMA DMA engine driver

[    1.524534] SCSI subsystem initialized

[    1.524917] libata version 3.00 loaded.

[    1.525256] usbcore: registered new interface driver usbfs

[    1.525333] usbcore: registered new interface driver hub

[    1.525430] usbcore: registered new device driver usb

[    1.525991] omap_i2c 44e0b000.i2c: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux@800/pinmux_i2c0_pins, deferring probe

[    1.526036] omap_i2c 4819c000.i2c: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux@800/pinmux_i2c2_pins, deferring probe

[    1.526156] media: Linux media interface: v0.10

[    1.526216] Linux video capture interface: v2.00

[    1.526304] pps_core: LinuxPPS API ver. 1 registered

[    1.526311] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giom...@linux.it>

[    1.526337] PTP clock support registered

[    1.527222] omap-mailbox 480c8000.mailbox: omap mailbox rev 0x400

[    1.528442] NetLabel: Initializing

[    1.528456] NetLabel:  domain hash size = 128

[    1.528462] NetLabel:  protocols = UNLABELED CIPSOv4

[    1.528518] NetLabel:  unlabeled traffic allowed by default

[    1.528891] clocksource: Switched to clocksource timer1

[    1.636226] NET: Registered protocol family 2

[    1.637076] TCP established hash table entries: 4096 (order: 2, 16384 bytes)

[    1.637125] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)

[    1.637183] TCP: Hash tables configured (established 4096 bind 4096)

[    1.637252] UDP hash table entries: 256 (order: 1, 8192 bytes)

[    1.637272] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)

[    1.637567] NET: Registered protocol family 1

[    1.638097] RPC: Registered named UNIX socket transport module.

[    1.638109] RPC: Registered udp transport module.

[    1.638116] RPC: Registered tcp transport module.

[    1.638122] RPC: Registered tcp NFSv4.1 backchannel transport module.

[    1.638701] Unpacking initramfs...

[    1.956187] Freeing initrd memory: 4392K (cfbb6000 - d0000000)

[    1.956847] hw perfevents: enabled with armv7_cortex_a8 PMU driver, 5 counters available

[    1.959374] futex hash table entries: 256 (order: 2, 16384 bytes)

[    1.959495] audit: initializing netlink subsys (disabled)

[    1.959571] audit: type=2000 audit(1.896:1): initialized

[    1.969311] zbud: loaded

[    1.969940] VFS: Disk quotas dquot_6.6.0

[    1.970185] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)

[    1.972770] NFS: Registering the id_resolver key type

[    1.972831] Key type id_resolver registered

[    1.972839] Key type id_legacy registered

[    1.972939] nfs4filelayout_init: NFSv4 File Layout Driver Registering...

[    1.973285] fuse init (API version 7.23)

[    1.973898] SGI XFS with ACLs, security attributes, realtime, no debug enabled

[    1.981491] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)

[    1.981717] io scheduler noop registered

[    1.981733] io scheduler deadline registered

[    1.981796] io scheduler cfq registered (default)

[    1.983126] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568

[    1.984568] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle

[    1.985984] Serial: 8250/16550 driver, 6 ports, IRQ sharing disabled

[    1.988763] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 158, base_baud = 3000000) is a 8250

[    1.996391] console [ttyS0] enabled

[    1.997931] [drm] Initialized drm 1.1.0 20060810

[    2.048963] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6

[    2.048984] davinci_mdio 4a101000.mdio: detected phy mask fffffffe

[    2.049327] davinci_mdio: dt: updated phy_id[0] from phy_mask[fffffffe]

[    2.056663] libphy: 4a101000.mdio: probed

[    2.056695] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720

[    2.057526] cpsw 4a100000.ethernet: Detected MACID = 90:59:af:56:ea:16

[    2.059202] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

[    2.059256] ehci-platform: EHCI generic platform driver

[    2.059436] ehci-omap: OMAP-EHCI Host Controller driver

[    2.059845] usbcore: registered new interface driver usb-storage

[    2.061636] 47401300.usb-phy supply vcc not found, using dummy regulator

[    2.063800] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)

[    2.063816] musb-hdrc: MHDRC RTL version 2.0

[    2.063824] musb-hdrc: setup fifo_mode 4

[    2.063842] musb-hdrc: 28/31 max ep, 16384/16384 memory

[    2.065101] 47401b00.usb-phy supply vcc not found, using dummy regulator

[    2.067115] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)

[    2.067129] musb-hdrc: MHDRC RTL version 2.0

[    2.067136] musb-hdrc: setup fifo_mode 4

[    2.067150] musb-hdrc: 28/31 max ep, 16384/16384 memory

[    2.067281] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver

[    2.067314] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 1

[    2.067574] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002

[    2.067586] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1

[    2.067596] usb usb1: Product: MUSB HDRC host driver

[    2.067605] usb usb1: Manufacturer: Linux 4.4.9-ti-r25 musb-hcd

[    2.067614] usb usb1: SerialNumber: musb-hdrc.1.auto

[    2.068406] hub 1-0:1.0: USB hub found

[    2.068457] hub 1-0:1.0: 1 port detected

[    2.077816] mousedev: PS/2 mouse device common for all mice

[    2.080083] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0

[    2.080859] i2c /dev entries driver

[    2.082575] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec

[    2.083365] omap_hsmmc 48060000.mmc: Got CD GPIO

[    2.146269] hidraw: raw HID events driver (C) Jiri Kosina

[    2.146897] usbcore: registered new interface driver usbhid

[    2.146909] usbhid: USB HID core driver

[    2.147163] ashmem: initialized

[    2.147930]  remoteproc0: wkup_m3 is available

[    2.147943]  remoteproc0: Note: remoteproc is still under development and considered experimental.

[    2.147950]  remoteproc0: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.

[    2.151512] NET: Registered protocol family 10

[    2.156211] mip6: Mobile IPv6

[    2.156239] NET: Registered protocol family 17

[    2.156361] Key type dns_resolver registered

[    2.156376] mpls_gso: MPLS GSO support

[    2.156646] omap_voltage_late_init: Voltage driver support not added

[    2.164071] PM: Cannot get wkup_m3_ipc handle

[    2.168857] ThumbEE CPU extension supported.

[    2.168996] Registering SWP/SWPB emulation handler

[    2.170068] registered taskstats version 1

[    2.170308] zswap: loaded using pool lzo/zbud

[    2.176631] Btrfs loaded

[    2.199927] Key type encrypted registered

[    2.202852] input: tps65217_pwr_but as /devices/platform/ocp/44e0b000.i2c/i2c-0/0-0024/input/input0

[    2.203019] mmc1: MAN_BKOPS_EN bit is not set

[    2.204841] mmc1: new high speed MMC card at address 0001

[    2.205805] mmcblk0: mmc1:0001 MMC02G 1.79 GiB

[    2.206190] mmcblk0boot0: mmc1:0001 MMC02G partition 1 1.00 MiB

[    2.206551] mmcblk0boot1: mmc1:0001 MMC02G partition 2 1.00 MiB

[    2.208363]  mmcblk0: p1

[    2.226164] tps65217 0-0024: TPS65217 ID 0xe version 1.2

[    2.226687] at24 0-0050: 32768 byte 24c256 EEPROM, writable, 1 bytes/write

[    2.226915] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz

[    2.228507] at24 2-0054: 32768 byte 24c256 EEPROM, writable, 1 bytes/write

[    2.228971] at24 2-0055: 32768 byte 24c256 EEPROM, writable, 1 bytes/write

[    2.229364] at24 2-0056: 32768 byte 24c256 EEPROM, writable, 1 bytes/write

[    2.229735] at24 2-0057: 32768 byte 24c256 EEPROM, writable, 1 bytes/write

[    2.229772] omap_i2c 4819c000.i2c: bus 2 rev0.11 at 100 kHz

[    2.230801]  remoteproc0: powering up wkup_m3

[    2.230862]  remoteproc0: Booting fw image am335x-pm-firmware.elf, size 219735

[    2.231109]  remoteproc0: remote processor wkup_m3 is now up

[    2.231131] wkup_m3_ipc 44e11324.wkup_m3_ipc: CM3 Firmware Version = 0x191

[    2.236833] bone_capemgr bone_capemgr: Baseboard: 'A335BNLT,0A5C,2713BBBK7164'

[    2.236863] bone_capemgr bone_capemgr: compatible-baseboard=ti,beaglebone-black - #slots=4

[    2.276906] bone_capemgr bone_capemgr: slot #0: No cape found

[    2.320900] bone_capemgr bone_capemgr: slot #1: No cape found

[    2.364897] bone_capemgr bone_capemgr: slot #2: No cape found

[    2.408945] bone_capemgr bone_capemgr: slot #3: No cape found

[    2.414886] bone_capemgr bone_capemgr: initialized OK.

[    2.416525] PM: bootloader does not support rtc-only!

[    2.417104] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)

[    2.417130] of_cfs_init

[    2.417242] of_cfs_init: OK

[    2.422459] PM: Hibernation image not present or could not be loaded.

[    2.423630] Freeing unused kernel memory: 588K (c0ac9000 - c0b5c000)

[    2.469877] usb 1-1: new high-speed USB device number 2 using musb-hdrc

[    2.518781] random: systemd-udevd urandom read with 13 bits of entropy available

[    2.598431] usb 1-1: New USB device found, idVendor=7392, idProduct=7811

[    2.598455] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[    2.598464] usb 1-1: Product: 802.11n WLAN Adapter

[    2.598473] usb 1-1: Manufacturer: Realtek

[    2.598482] usb 1-1: SerialNumber: 00e04c000001

[    3.152138] tda998x 0-0070: found TDA19988

[    3.161279] tilcdc 4830e000.lcdc: bound 0-0070 (ops tda998x_ops [tda998x])

[    3.161309] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).

[    3.161316] [drm] No driver support for vblank timestamp query.

[    3.161747] tilcdc 4830e000.lcdc: No connectors reported connected with modes

[    3.161770] [drm] Cannot find any crtc or sizes - going 1024x768

[    3.189859] Console: switching to colour frame buffer device 128x48

[    3.226710] tilcdc 4830e000.lcdc: fb0:  frame buffer device

[    3.226741] [drm] Initialized tilcdc 1.0.0 20121205 on minor 0

[    3.560342] EXT4-fs (mmcblk0p1): INFO: recovery required on readonly filesystem

[    3.560365] EXT4-fs (mmcblk0p1): write access will be enabled during recovery

[    3.926543] EXT4-fs (mmcblk0p1): recovery complete

[    3.930268] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)

[    4.320148] systemd[1]: System time before build time, advancing clock.

[    4.472637] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN)

[    4.473468] systemd[1]: Detected architecture arm.

[    4.474936] systemd[1]: Set hostname to <arm>.

[    4.972515] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.

[    4.973312] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.

[    4.974325] systemd[1]: Created slice User and Session Slice.

[    4.974492] systemd[1]: Reached target Swap.

[    4.974802] systemd[1]: Listening on Syslog Socket.

[    4.975157] systemd[1]: Started Forward Password Requests to Wall Directory Watch.

[    4.975271] systemd[1]: Reached target Remote File Systems (Pre).

[    4.975360] systemd[1]: Reached target Encrypted Volumes.

[    4.976136] systemd[1]: Created slice System Slice.

[    4.977248] systemd[1]: Created slice system-getty.slice.

[    4.977389] systemd[1]: Reached target Slices.

[    4.977756] systemd[1]: Listening on udev Control Socket.

[    4.978629] systemd[1]: Created slice system-serial\x2dgetty.slice.

[    4.980352] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.

[    4.980645] systemd[1]: Listening on fsck to fsckd communication Socket.

[    4.980758] systemd[1]: Reached target Remote File Systems.

[    4.981239] systemd[1]: Listening on udev Kernel Socket.

[    4.981592] systemd[1]: Listening on Journal Socket.

[    4.985926] systemd[1]: Starting Create list of required static device nodes for the current kernel...

[    4.999181] systemd[1]: Starting Load Kernel Modules...

[    5.053457] systemd[1]: Started Read required files in advance.

[    5.109367] systemd[1]: Mounting POSIX Message Queue File System...

[    5.116701] systemd[1]: Starting File System Check on Root Device...

[    5.193287] systemd[1]: Mounting /sys/kernel/debug...

[    5.206265] systemd[1]: Listening on Journal Audit Socket.

[    5.206727] systemd[1]: Listening on Journal Socket (/dev/log).

[    5.261341] systemd[1]: Starting Journal Service...

[    5.323715] systemd[1]: Mounted POSIX Message Queue File System.

[    5.324003] systemd[1]: Mounted /sys/kernel/debug.

[    5.332096] systemd[1]: Started Create list of required static device nodes for the current kernel.

[    5.337355] systemd[1]: Started Load Kernel Modules.

[    5.340306] systemd[1]: ureadahead.service: Main process exited, code=exited, status=5/NOTINSTALLED

[    5.342835] systemd[1]: ureadahead.service: Unit entered failed state.

[    5.343039] systemd[1]: ureadahead.service: Failed with result 'exit-code'.

[    5.461323] systemd[1]: Started File System Check on Root Device.

[    5.602725] systemd[1]: Started Journal Service.

[    6.042592] EXT4-fs (mmcblk0p1): re-mounted. Opts: errors=remount-ro

[    7.647553] systemd-journald[177]: Received request to flush runtime journal from PID 1

[   11.307078] Bluetooth: Core ver 2.21

[   11.307219] NET: Registered protocol family 31

[   11.307229] Bluetooth: HCI device and connection manager initialized

[   11.307254] Bluetooth: HCI socket layer initialized

[   11.307271] Bluetooth: L2CAP socket layer initialized

[   11.307315] Bluetooth: SCO socket layer initialized

[   11.548958] random: nonblocking pool is initialized

[   11.867622] omap_rng 48310000.rng: OMAP Random Number Generator ver. 20

[   11.971773] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2

[   12.052357] ti-pruss 4a300000.pruss: creating PRU cores and other child platform devices

[   12.074195] omap-sham 53100000.sham: hw accel on OMAP rev 4.3

[   12.257706] net eth0: initializing cpsw version 1.12 (0)

[   12.264151] net eth0: phy found : id is : 0x7c0f1

[   12.297388] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

[   12.329420]  remoteproc1: 4a334000.pru0 is available

[   12.329447]  remoteproc1: Note: remoteproc is still under development and considered experimental.

[   12.329455]  remoteproc1: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.

[   12.332237]  remoteproc1: Direct firmware load for am335x-pru0-fw failed with error -2

[   12.332268]  remoteproc1: failed to load am335x-pru0-fw

[   12.379883] pru-rproc 4a334000.pru0: booting the PRU core manually

[   12.379910]  remoteproc1: powering up 4a334000.pru0

[   12.379975]  remoteproc1: Direct firmware load for am335x-pru0-fw failed with error -2

[   12.379990]  remoteproc1: request_firmware failed: -2

[   12.385195] pru-rproc 4a334000.pru0: rproc_boot failed

[   12.881715] asoc-simple-card sound: i2s-hifi <-> 48038000.mcasp mapping ok

[   12.909256]  remoteproc1: releasing 4a334000.pru0

[   12.909419] pru-rproc: probe of 4a334000.pru0 failed with error -2

[   12.909733]  remoteproc1: 4a338000.pru1 is available

[   12.909745]  remoteproc1: Note: remoteproc is still under development and considered experimental.

[   12.909754]  remoteproc1: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.

[   12.911320]  remoteproc1: Direct firmware load for am335x-pru1-fw failed with error -2

[   12.911349]  remoteproc1: failed to load am335x-pru1-fw

[   12.931998] pru-rproc 4a338000.pru1: booting the PRU core manually

[   12.932025]  remoteproc1: powering up 4a338000.pru1

[   12.932084]  remoteproc1: Direct firmware load for am335x-pru1-fw failed with error -2

[   12.932098]  remoteproc1: request_firmware failed: -2

[   12.937338] pru-rproc 4a338000.pru1: rproc_boot failed

[   13.253329]  remoteproc1: releasing 4a338000.pru1

[   13.253493] pru-rproc: probe of 4a338000.pru1 failed with error -2

[   14.905156] net eth0: initializing cpsw version 1.12 (0)

[   14.907553] net eth0: phy found : id is : 0x7c0f1

[   14.923777] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

[   15.340408] using random self ethernet address

[   15.340433] using random host ethernet address

[   15.340448] using host ethernet address: 90:59:AF:56:EA:18

[   15.340456] using self ethernet address: 90:59:AF:56:EA:10

[   15.350388] usb0: HOST MAC 90:59:af:56:ea:18

[   15.351109] usb0: MAC 90:59:af:56:ea:10

[   15.351268] using random self ethernet address

[   15.351283] using random host ethernet address

[   15.351409] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008

[   15.351420] g_ether gadget: g_ether ready

[   15.677899] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready

[   16.135210] rtl8192cu: Chip version 0x10

[   16.688167] rtl8192cu: MAC address: 80:1f:02:a6:93:cf

[   16.688199] rtl8192cu: Board Type 0

[   16.688330] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1

[   16.688490] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin

[   16.822937] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'

[   16.848090] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

[   16.857465] usbcore: registered new interface driver rtl8192cu

[   18.787106] cfg80211: World regulatory domain updated:

[   18.787136] cfg80211:  DFS Master region: unset

[   18.787144] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)

[   18.787157] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)

[   18.787167] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)

[   18.787176] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)

[   18.787187] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)

[   18.787198] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)

[   18.787207] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)

[   18.787216] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)

[   18.787225] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)

[  320.658705] rtl8192cu: MAC auto ON okay!

[  320.770449] rtl8192cu: Tx queue select: 0x05

[  321.339570] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

[  338.101261] rtl8192cu: MAC auto ON okay!

[  338.204702] rtl8192cu: Tx queue select: 0x05

[  338.896465] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

[  341.069943] wlan0: authenticate with 08:60:6e:ba:6d:e0

[  341.089020] wlan0: send auth to 08:60:6e:ba:6d:e0 (try 1/3)

[  341.094276] wlan0: authenticated

[  341.101068] wlan0: associate with 08:60:6e:ba:6d:e0 (try 1/3)

[  341.104854] wlan0: RX AssocResp from 08:60:6e:ba:6d:e0 (capab=0x411 status=0 aid=1)

[  341.214684] wlan0: associated

[  341.231684] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

ubuntu@arm:~$

[Marcos Scriven]

dmesg was truncated at the end of my last reply - will try again:

[Robert Nelson]

On Mon, May 23, 2016 at 10:24 AM, Marcos Scriven <mar...@scriven.org> wrote:

Hi Robert

Thanks for the responses. I hope I didn't make it sound like I was demanding a new version of Kamikaze from Elias! I understand the whole reason for Kamikaze is that it 'just works' out of the box with the Replicape - the conundrum for me is whether I try and start with your image with a newer kernel (in the hope it has better kernel support for my wifi dongle), and repeat some of Elias's setup, or start with Kamikaze, and try and get a dynamic module working (which might not even work, and be a wasted effort if it works in a newer kernel).

Thanks to the joys of Amazon Prime Now, have ordered a 5v multi adapter, and unfortunately seeing the same behaviour. The voltage seems to be pretty stable at 5.10v:

I agree it 'smells like a power problem', but still getting the same issue with a 5V adapter.

The other issue with that setup, the wifi antenna is really close to the HDMI interface..

From: /boot/uEnv.txt

Either disable both the hdmi & emmc via:

dtb=am335x-boneblack-overlay.dtb

Or just disable the hdmi via:

dtb=am335x-boneblack-emmc-overlay.dtb

Regards,

[Marcos Scriven]

Thanks again Robert - I'll try disabling HDMI and emmc.

However, would this not have been mitigated by using the powered USB hub (where the dongle was thus much further away)?

Is there any way to tell what's actually happening without some expensive diagnostic kit here, or is it just a case of trial and error?

I'm also going to try the combination of https://github.com/pvaret/rtl8192cu-fixes DKMS, with the 5V connector on (as it didn't seem to make a difference with the powered hub)

[Wally Bkg]

This is from 2013, but the Edimax dongle seems to have reliability issues on the Raspberry Pi as well as the BBB.  This looks to be an easy solution to try:

http://forums.adafruit.com/viewtopic.php?f=50&t=44171&p=220622#p220593

[Marcos Scriven]

Thanks Wally 

I should have mentioned I tried that too, as it's mentioned in the readme for the open source driver I tried: https://github.com/pvaret/rtl8192cu-fixes/blame/master/README.md#L62

[William Hermans]

Gerald, if you're looking at this thread. isn't 5.10v too much ? I would not bother mentioning it, except I remember some discussion on that a while back. . . .

@Marcos

Can you list the things you have tried ? There are several known problems with the BBB and wifi. Ranging from hdmi interfering with the signal strength, to an antenna that is too close to the board which gets interfered with by the boards ground plane.

Robert has made wifi recommendations in the past, and all the ones I remember looking at were priced at around $15 usd or less.

--
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 beagleboard...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/9d0ef660-c830-40db-901d-3a5b5ece39f8%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Robert Nelson]

On Mon, May 23, 2016 at 2:21 PM, William Hermans <yyr...@gmail.com> wrote:

Gerald, if you're looking at this thread. isn't 5.10v too much ? I would not bother mentioning it, except I remember some discussion on that a while back. . . .

@Marcos

Can you list the things you have tried ? There are several known problems with the BBB and wifi. Ranging from hdmi interfering with the signal strength, to an antenna that is too close to the board which gets interfered with by the boards ground plane.

Robert has made wifi recommendations in the past, and all the ones I remember looking at were priced at around $15 usd or less.

Atheros! ;)

Regards,

[William Hermans]

@Robert

Just goes to show how "creepy" I am lol . . . how long ago do you think you made this post ? lol I have it in a text file in case I ever decide to buy a wifi dongle ;)

For a "mere" 2-3 more $'s you can get a WiFi dongle that'll work out
of the box without custom non-mainline drivers that do not always
work.

Atheros (atk9) based modules on amazon...
tl-wn721n
tl-wn722n

Just search "wifi" in this group, for all the problems with those
'tiny' wifi adapters...

Regards,

--

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 beagleboard...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYjT0COQjMpjK5c1zvuocYkzEZ6KEeEc4QVn%3DAy%3D8pqo1A%40mail.gmail.com.

[William Hermans]

Anyway, yeah, I'm not creepy, my memory just sucks. I can remember stuff people post about, just not exact details a lot of the time. But that text above is probably a couple years old.

[Marcos Scriven]

Hi William

So right now I've had the wifi working for an hour or so. The magic combination (which I'm skeptical about) appears to be:

1) Robert's latest Ubuntu Xenial console image (4.4.9-ti-r25)

2) pvaret's dynamic kernel module: https://github.com/pvaret/rtl8192cu-fixes (including his modprobe.d config to blacklist the mainline driver and disable power saving)

3) A 5V power supply

I've left the BBB connected on wifi for over an hour, and was able to just ping it and SSH into it (Before constantly pinging sometimes seemed to keep it working a little longer)

Other combinations of power (micro USB), USB connection (direct, non-powered hub, powered hub), and kernel (Kamikaze vs lastest official console image) didn't seem to work.

I'd not yet tried Robert's suggestion of disabling HDMI/eMMC yet.

A few questions remain answered in my mind:

1) How do we *really* know what's going wrong here, without seeing any issues in any system logs? Would it be a case of just speculating HDMI would cause interference, or has anyone hooked up oscilloscopes and other diagnostic equipment? I tried putting my multimeter in series with the barrel supply and the reading was always 500mA, so I don't think it's a power issue.

2) Is there a way to tell whether a powered USB hub is actually providing power to one of its ports by software monitoring alone ?

3) How can I gain confidence things really are working? Check errors with netstat -d -i ? Are there any other recommended tools to run in the background for a while to look for wifi issues? 

4) Even when the wifi is working via manually running connmanctl, there's some issue with the connman daemon not having the right perms to change the network name to automatically connect at startup (you see it waiting a couple of minutes in the kernel logs, but in syslog you see both connman and wpa_supplicant having issues:

May 23 18:16:47 arm kernel: [   13.883294] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready

May 23 18:16:47 arm avahi-daemon[326]: Joining mDNS multicast group on interface usb0.IPv4 with address 192.168.7.2.

May 23 18:16:47 arm connmand[435]: usb0 {add} route 192.168.7.0 gw 0.0.0.0 scope 253 <LINK>

May 23 18:16:47 arm avahi-daemon[326]: New relevant interface usb0.IPv4 for mDNS.

May 23 18:16:48 arm avahi-daemon[326]: Registering new address record for 192.168.7.2 on usb0.IPv4.

May 23 18:16:48 arm connmand[435]: usb0 {del} address 192.168.7.2/24 label usb0

May 23 18:16:48 arm avahi-daemon[326]: Withdrawing address record for 192.168.7.2 on usb0.

May 23 18:16:48 arm avahi-daemon[326]: Leaving mDNS multicast group on interface usb0.IPv4 with address 192.168.7.2.

May 23 18:16:48 arm connmand[435]: usb0 {del} route 192.168.7.0 gw 0.0.0.0 scope 253 <LINK>

May 23 18:16:48 arm avahi-daemon[326]: Interface usb0.IPv4 no longer relevant for mDNS.

May 23 18:16:48 arm avahi-daemon[326]: Joining mDNS multicast group on interface usb0.IPv4 with address 192.168.7.2.

May 23 18:16:48 arm avahi-daemon[326]: New relevant interface usb0.IPv4 for mDNS.

May 23 18:16:48 arm avahi-daemon[326]: Registering new address record for 192.168.7.2 on usb0.IPv4.

May 23 18:16:48 arm connmand[435]: usb0 {add} address 192.168.7.2/30 label usb0 family 2

May 23 18:16:48 arm connmand[435]: usb0 {add} route 192.168.7.0 gw 0.0.0.0 scope 253 <LINK>

May 23 18:16:48 arm udhcpd[503]: udhcpd (v1.22.1) started

May 23 18:16:48 arm systemd-udevd[234]: Error running install command for rtlwifi

May 23 18:16:48 arm dbus[329]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'

May 23 18:16:48 arm wpa_supplicant[416]: Successfully initialized wpa_supplicant

May 23 18:16:48 arm systemd[1]: Started WPA supplicant.

May 23 18:16:48 arm systemd[1]: Reached target Network.

May 23 18:16:48 arm systemd[1]: Starting OpenBSD Secure Shell server...

May 23 18:16:49 arm systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.

May 23 18:16:49 arm systemd[1]: Stopping LSB: Start busybox udhcpd at boot time...

May 23 18:16:49 arm udhcpd[503]: Received SIGTERM

May 23 18:16:49 arm connmand[435]: wlan0 {create} index 4 type 1 <ETHER>

May 23 18:16:49 arm connmand[435]: wlan0 {update} flags 4098 <DOWN>

May 23 18:16:49 arm connmand[435]: wlan0 {newlink} index 4 address 80:1F:02:A6:93:CF mtu 1500

May 23 18:16:49 arm connmand[435]: wlan0 {newlink} index 4 operstate 2 <DOWN>

May 23 18:16:49 arm udhcpd[554]: Stopping very small Busybox based DHCP server: Stopped /usr/sbin/udhcpd (pid 503).

May 23 18:16:49 arm kernel: [   15.604349] usbcore: registered new interface driver rtl8192cu

May 23 18:16:49 arm systemd[1]: Stopped LSB: Start busybox udhcpd at boot time.

May 23 18:16:49 arm udhcpd[554]: udhcpd.

May 23 18:16:49 arm systemd[1]: Starting LSB: Start busybox udhcpd at boot time...

May 23 18:16:50 arm systemd[1]: Reached target Sound Card.

May 23 18:16:50 arm udhcpd[561]: Starting very small Busybox based DHCP server: udhcpd.

May 23 18:16:50 arm systemd[1]: Started LSB: Start busybox udhcpd at boot time.

May 23 18:16:50 arm sh[311]: Restarting udhcpd (via systemctl): udhcpd.service.

May 23 18:16:50 arm udhcpd[567]: udhcpd (v1.22.1) started

May 23 18:16:50 arm kernel: [   16.316078] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

May 23 18:16:50 arm connmand[435]: Adding interface wlan0 [ wifi ]

May 23 18:16:50 arm connmand[435]: wlan0 {update} flags 36867 <UP>

May 23 18:16:50 arm connmand[435]: wlan0 {newlink} index 4 address 80:1F:02:A6:93:CF mtu 1500

May 23 18:16:50 arm connmand[435]: wlan0 {newlink} index 4 operstate 2 <DOWN>

May 23 18:16:50 arm wpa_supplicant[416]: nl80211: Driver does not support authentication/association or connect commands

May 23 18:16:50 arm wpa_supplicant[416]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0

May 23 18:16:50 arm wpa_supplicant[416]: ioctl[SIOCSIWAP]: Operation not permitted

May 23 18:16:50 arm systemd-udevd[249]: error changing net interface name 'wlan0' to 'wlx801f02a693cf': Device or resource busy

May 23 18:16:50 arm wpa_supplicant[416]: ioctl[SIOCSIWENCODEEXT]: Invalid argument

May 23 18:16:50 arm wpa_supplicant[416]: ioctl[SIOCSIWENCODEEXT]: Invalid argument

May 23 18:16:50 arm connmand[435]: wlan0 {newlink} index 4 address 80:1F:02:A6:93:CF mtu 1500

May 23 18:16:50 arm systemd-udevd[249]: could not rename interface '4' from 'wlan0' to 'wlx801f02a693cf': Device or resource busy

May 23 18:16:50 arm connmand[435]: wlan0 {newlink} index 4 operstate 2 <DOWN>

May 23 18:16:50 arm wpa_supplicant[416]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none

May 23 18:16:50 arm wpa_supplicant[416]: dbus: Failed to construct signal

May 23 18:16:50 arm systemd-udevd[234]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99.

May 23 18:16:50 arm systemd[1]: Started Generic Board Startup.

May 23 18:16:50 arm systemd[1]: Started OpenBSD Secure Shell server.

May 23 18:16:51 arm kernel: [   17.500611] cfg80211: World regulatory domain updated:

May 23 18:16:51 arm kernel: [   17.500641] cfg80211:  DFS Master region: unset

May 23 18:16:51 arm kernel: [   17.500649] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)

May 23 18:16:51 arm kernel: [   17.500662] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)

May 23 18:16:51 arm kernel: [   17.500672] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)

May 23 18:16:51 arm kernel: [   17.500680] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)

May 23 18:16:51 arm kernel: [   17.500692] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)

May 23 18:16:51 arm kernel: [   17.500703] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)

May 23 18:16:51 arm kernel: [   17.500713] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)

May 23 18:16:51 arm kernel: [   17.500722] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)

May 23 18:16:51 arm kernel: [   17.500730] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)

May 23 18:16:52 arm systemd-udevd[231]: Process '/sbin/crda' failed with exit code 249.

May 23 18:17:01 arm CRON[614]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

May 23 18:18:47 arm systemd[1]: connman-wait-online.service: Main process exited, code=exited, status=110/n/a

May 23 18:18:47 arm rsyslogd-2007: action 'action 9' suspended, next retry is Mon May 23 18:19:17 2016 [v8.16.0 try http://www.rsyslog.com/e/2007 ]

May 23 18:18:47 arm systemd[1]: Failed to start Wait for network to be configured by ConnMan.

May 23 18:18:47 arm systemd[1]: connman-wait-online.service: Unit entered failed state.

May 23 18:18:47 arm systemd[1]: connman-wait-online.service: Failed with result 'exit-code'.

May 23 18:18:47 arm systemd[1]: Reached target Network is Online.

May 23 18:18:47 arm systemd[1]: Starting LSB: Advanced IEEE 802.11 management daemon...

May 23 18:18:47 arm systemd[1]: Starting /etc/rc.local Compatibility...

May 23 18:18:47 arm systemd[1]: Starting LSB: Apache2 web server...

May 23 18:18:47 arm systemd[1]: Started LSB: Advanced IEEE 802.11 management daemon.

May 23 18:18:47 arm systemd[1]: Started /etc/rc.local Compatibility.

 

Thanks again for everyone's help!

Marcos

[William Hermans]

@Marcos

Unless you *need* the HDMI, which I'm guessing you do not. You should disable it. Under best conditions it'll be something that could inject "undefined"  behavior. eMMC though I understand. Disabling the eMMC is something I'd personally rather not do. In fact, if I *had* to disable the eMMC for an external add on device. I'd probably do without using that external device.

As far as your current testing. I bet it's the power supply. I've proven to myself time, and time again. That you can run the beaglebone, and one on board peripheral like the serial debug port. Then that is it. You need a barrel jack 5v supply after that. How I proved this to myself. Was attempting to run ethernet, and a CANBUS cape at the same time. It would work *sometimes* ( when it felt like it ), but it was problematic enough that we had to put an external 2A supply on it. After that, all problems went away.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/589a5513-1221-48a6-a262-beb3959a811a%40googlegroups.com.