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 On Monday, May 23, 2016 at 8:21:49 PM UTC+1, William Hermans 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. > > On Mon, May 23, 2016 at 9:27 AM, Marcos Scriven <[email protected] > <javascript:>> wrote: > >> 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 >> >> >> On Monday, May 23, 2016 at 5:19:39 PM UTC+1, Wally Bkg wrote: >>> >>> 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 >>> >>> >>> >>> On Monday, May 23, 2016 at 11:00:20 AM UTC-5, Marcos Scriven wrote: >>>> >>>> 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) >>>> >>>> On Monday, May 23, 2016 at 4:51:07 PM UTC+1, RobertCNelson wrote: >>>>> >>>>> >>>>> >>>>> On Mon, May 23, 2016 at 10:24 AM, Marcos Scriven <[email protected]> >>>>> 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: >>>>>> >>>>>> >>>>>> <https://lh3.googleusercontent.com/-KMeNMJN8Zjs/V0MeYDK8_BI/AAAAAAABKuI/jMP4dFdl3uoe1mdpl1wDblhFLlGEwDD1QCLcB/s1600/IMG_1143.JPG> >>>>>> >>>>>> >>>>>> 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, >>>>> >>>>> -- >>>>> Robert Nelson >>>>> https://rcn-ee.com/ >>>>> >>>> -- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/9d0ef660-c830-40db-901d-3a5b5ece39f8%40googlegroups.com >> >> <https://groups.google.com/d/msgid/beagleboard/9d0ef660-c830-40db-901d-3a5b5ece39f8%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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/589a5513-1221-48a6-a262-beb3959a811a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
