Hi All Back in September I posted about some problems I had getting wifi going on the BBB. I've taken another shot at it and I (think I) have something working now. This post also rolls in a few other assorted tidbits scattered around in other posts. Hope somebody finds this useful.
Read it here on my blog: Wifi On The Beaglebone Black With Systemd <http://madscientistlabs.blogspot.ca/2014/12/wifi-on-beaglebone-black-with-systemd.html> This is on the Jessie snapshot. I first tried it on my TP-Link TL-WN722N dongle but was getting kernel crashes again like I was in September. Bad hardware or ??? Things seem to work OK with a ZD1211 based dongle (any chance of getting zd1211-firmware in the image snapshot?), though I do see a few DUP! pings sometimes when the network has been idle for a while e.g. PING www.google.com (216.58.216.228) 56(84) bytes of data. 64 bytes from ord31s22-in-f4.1e100.net (216.58.216.228): icmp_seq=1 ttl=50 time=74.8 ms 64 bytes from ord31s22-in-f4.1e100.net (216.58.216.228): icmp_seq=2 ttl=50 time=68.3 ms 64 bytes from ord31s22-in-f4.1e100.net (216.58.216.228): icmp_seq=3 ttl=50 time=71.4 ms 64 bytes from ord31s22-in-f4.1e100.net (216.58.216.228): icmp_seq=4 ttl=50 time=70.5 ms 64 bytes from ord31s22-in-f4.1e100.net (216.58.216.228): icmp_seq=4 ttl=50 time=75.6 ms (DUP!) 64 bytes from ord31s22-in-f4.1e100.net (216.58.216.228): icmp_seq=4 ttl=50 time=76.2 ms (DUP!) 64 bytes from ord31s22-in-f4.1e100.net (216.58.216.228): icmp_seq=4 ttl=50 time=76.2 ms (DUP!) 64 bytes from ord31s22-in-f4.1e100.net (216.58.216.228): icmp_seq=4 ttl=50 time=76.5 ms (DUP!) 64 bytes from ord31s22-in-f4.1e100.net (216.58.216.228): icmp_seq=4 ttl=50 time=82.6 ms (DUP!) Thoughts? Comments? Questions? -- 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]. For more options, visit https://groups.google.com/d/optout.
