jamesh wrote: ↑
Wed Jun 06, 2018 8:32 pm
I just read through this thread again to see if there is anything I can suggest, but without having the particular wifi dongle being used it difficult to make any assessment. I'm pretty sure its the stick or the driver for the stick, if only because huge numbers of users of the 3B and 3B+ have no problems at all with the onboard Wifi (and wifi dongles on the 2). If you use the onboard Wifi of the 3B does that work OK?
I tryed 3 Alpha AWUS(148f:3070 Ralink Technology, Corp. RT2870/RT3070) and a 1 Tenda Stick, this has the same RT Base Chip but other addtitional Chips. The Alpha sticks are very common and very famous cause they have the best sensitivity&Signal quality.
Cause its was 4 different Sticks(3 of them running fine 24/7 on Desktop Linux) it cant be the stick.
It may be the driver (the driver firmware is the same like on Desktop Linux CRC32 compared). The Desktop runned different Linux(Backtrack/2 Kali versions), with none there was a problem.
The Answer for my Question why a "dead" device is listed by ifconfig/iwconfig/lsusb would too intresting. If a device doesnt responds it should be dropped by Linux.
I disabled onboard Wifi cause of this bug and Random wlan0/wlan1. Monitor Mode doesnt work with it and it has very bad sensitivity&Signal.
Other People that have working wifi may often use the "Managed Mode" or use small wifi sticks/onboard that doesnt get much wifi traffic.
-It may possible that the bug has todo with the Monitor Mode part.
-Cause the bug frequency has increased over the Time, it has todo with increased wifi devices&traffic
-It seems sticks with less sensitivity trigger the bug a bit less.
-It may be something like the driver/packed filter that get a malicous 802.11 frame and crash (driver may modified from original Debian sources or not ported well, eg. datatype "long" is today usual 64Bit but on rpi its 32 Bit).