Gaaaaah! Damn it, gmail. I'm sending this email again. The first copy of this email was rejected by the ML's spam filter, due to the presence of an HTML part. I'm sorry for spamming y'all. > Looks like with the hub it can work at least some hours. Correct? There was an ~18 hour timespan between when the device was physically plugged in and when freaky error messages were dumped to the kernel log, so that's good. However, it's worth noting the device wasn't really "available" that entire time. The kernel log shows that the device appears to be physically disconnected and reconnected five or six times in that timespan. (The device remained physically untouched.) The device is set up as a high-speed USB device again after each disconnect, which is good, but those disconnects shouldn't happen in the first place. I'm doing as you've suggested: 1. Start collecting log messages with `journalctl -k --follow -n 0 > mylogfile.txt` 2. Plug in USB hub. 3. Plug in TL-WN722N. 4. Execute `sudo bash -c 'echo none > /sys/class/leds/ath9k_htc-phy11/trigger'` 5. `sudo ip link set dev wlp0s19f2u4u2 up` 6. Wait. I'm currently on step six. I'll post an update when appropriate. —Jeremy 'Ichimonji10' Audet -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
