**** BEGIN LOGGING AT Fri Sep 15 03:00:01 2017 Sep 15 15:34:19 hello **** BEGIN LOGGING AT Fri Sep 15 16:05:51 2017 Sep 15 20:55:51 I think my wifi issues may have been due to using not quite the correct driver for the Beaglebone Wireless' wifi chip. I guess I'll know in a few days if it goes down Sep 15 20:56:08 What hinted me in the direction: https://e2e.ti.com/support/wireless_connectivity/wilink_wifi_bluetooth/f/307/t/244840 Sep 15 21:04:37 (my syslogs were full of similar errors about problems with wl1271... sdio kinda errors whereas it now loads wl18xx stuff) Sep 15 21:37:16 wl1271 is definitely wrong Sep 15 23:43:58 it's gotten me curious to look at how drivers are matched with hardware in linux Sep 15 23:54:09 in this case it should actually be specified in DT Sep 15 23:54:36 so I don't quite get how it might end up loading the wrong driver Sep 15 23:57:04 which kernel are you using? Sep 16 00:02:49 the curious thing is, in that E2E thread they're saying to load wlcore_sdio instead of wl12xx_sdio, but if I look at wlcore/sdio.c in the kernel sources then that driver *is called* wl1271_sdio ... http://elixir.free-electrons.com/linux/v4.4.88/source/drivers/net/wireless/ti/wlcore/sdio.c#L430 Sep 16 00:04:13 lemme see what I enabled in my kernel builds for wl18xx Sep 16 00:04:41 4.4.30-ti-r64 Sep 16 00:05:10 I'm not sure what it was before I upgraded. I'd have to boot up the other one i have Sep 16 00:05:26 ok, so pretty old kernel Sep 16 00:06:08 I suppose so. But that's typically what the major images use (old everything) Sep 16 00:06:31 here's what I configured... https://github.com/dutchanddutch/bb-kernel/blob/am33x-v4.9/patches/defconfig#L1329-L1336 Sep 16 00:06:54 let's see what it actually loaded for me Sep 16 00:07:28 wl18xx, wlcore, wlcore_sdio Sep 16 00:09:10 Okay, I do have a record of it from a couple weeks ago. 4.4 prior, but no other sub version info. Sep 16 00:09:41 I'll take a look at the other BBBW next week and see what it's story is (which drivers, kernel version) Sep 16 00:10:54 it looks like wlcore_sdio is the module name, and wl1271_sdio is the name of the driver therein Sep 16 00:12:28 Well, all I know is that if I physically look at the chip it says "WL18 something something" Sep 16 00:13:20 yes, it looks like the driver name "wl1271_sdio" is simply a case of the name being awkwardly specific while it's actually for the whole wilink family it seems Sep 16 00:24:46 https://hastebin.com/raw/utenefonuz some relevant bits **** ENDING LOGGING AT Sat Sep 16 03:00:01 2017