..running on raspberry pi 3. Second Paolo -- this really should be the
default since most folks who use a wifi dongle on a raspberry pi really
want to use it for wifi analytics such as monitor mode sniffing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
After rebuilding the kernel with only the rtlwifi source and object
files, I am able to put the 8818CUS chipset in monitor mode. This is on
4.9.13-v7+
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577
Hi, chiming in to record that this bug affects anyone who is trying to
put the 8188CUS chipset into monitor mode.
Debian distrubutions for x86 use the driver rtl8192cu, and that works
just fine in both managed and monitor modes.
Raspbian on Raspberry PI3 (I have tried many versions including 4.4.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577421
Title:
** Description changed:
+ SRU justification:
+
+ Impact: as part of the RaspberryPI BSP we got an out of tree Realtek
+ driver that predates the upstream rtlwifi driver:
+
+ commit 352ad803b031478b4f5ae55835225a699afa5ed3
+ Author: popcornmix
+ Date: Mon Sep 3 17:10:23 2012 +0100
+
+ Add
fwiw, on my realtek 8912 based dongle AP mode works pretty much fine in
4.4 kernel on beaglebone... maybe the mainline/staging driver has
improved enough between 4.0 and 4.4?
Is there a way we cna have both modules and hint which will be picked
with priority? If so we could allow device builders t
