Closed ZeroChaos- closed 5 years ago
Give med "lsusb" with adaptere. They must be added to "usb_intf.c"
Not really any more info here than was in the above paste, but if it makes you happy:
Bus 001 Device 024: ID 2357:0115 TP-Link
Bus 001 Device 025: ID 20f4:808a TRENDnet
Bus 001 Device 026: ID 7392:c822 Edimax Technology Co., Ltd
Bus 001 Device 027: ID 2357:011e TP-Link
Bus 001 Device 030: ID 0bda:c811 Realtek Semiconductor Corp.
Bus 001 Device 029: ID 0bda:b812 Realtek Semiconductor Corp.
Bus 001 Device 028: ID 7392:b822 Edimax Technology Co., Ltd
Please note, I looked all these up and they are all 88xxau according to my research, but I don't know specifically which are 12 vs 14 vs 21 or whatever. I tried adding the ids through the new_id functionality and none of them worked :-(
Easier to read it from lsusb, yes. check them with wikidevi. Like the on top isn't supported.. it's a rtl8812BU..
https://wikidevi.com/wiki/TP-LINK_Archer_T4U_v3
I can always fork and add support to that driver to, but it's not supported by the rtl8812AU
Same as the "7392:c822" this is another driver unfortunately.. 8812BU, not 8812AU
oh, my fault, I missed the distinction when I checked.
the other 5 will be added? I am happy to test whatever before you commit if you tell me what to test, or I can test after
I think they are rtl8812bu all of them, checked 3 of them, but I for no time to check them all right away
I've bought several dongles off Amazon, and I'm having the issue I just can't find any of the AU dongles. I'm not sure how to support the RTL8812BU with this driver. It's not as simple as CONFIG_RTL8822B=y
since it's not plumbed through.
I can't seem to get packet injection working on the drivers for this chipset, either. I guess it's just burden you guys have to deal with being the best :(.
EDIT I am confused now. I though 0bda:b812 was the 8812BU... but, it's listed as an 8822BU in the code?
@ZeroChaos- take a look at this!!
https://github.com/kimocoder/rtw88-usb
brand new 8822B driver... and THIS is the case.. 8822B is actually 8812BU supported! I'll start working on it as I yesterday fixed 8812au v5.3.4 injection and more, and today I finished up some rtl8188eus kernel support + more.
Give me a week and I'll add frame injection and more to it :1st_place_medal:
More information found https://lwn.net/Articles/786478/ From kernel tree.. over here https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw88?id=f85841b6b36ec1e28d5c702ebf2c8cd2997bf910
this one is actually interesting! mac80211 supported, several VIF.. damn.. here I may pull some stuff out of!
People... we've got another branch coming up! Brace for impact, I can't wait :1st_place_medal:
This USB ID's belongs to 8812BU, which is in the 8822B driver unfortunately. Don't have time to maintain another driver at this time :/
@ZeroChaos- you really want the rtw88 driver when it's ready. It uses the newer mac80211 instead of nl80211/cfg80211 mix.
Take a look https://lwn.net/Articles/768372/ It's a driver work-in-progress. Worth following
I have been watching it get added to the kernel for a while now, hoping it would add usb support for the 8812 :-)
On Sun, May 26, 2019, 08:30 Christian Bremvåg notifications@github.com wrote:
@ZeroChaos- https://github.com/ZeroChaos- you really want the rtw88 driver when it's ready. It uses the newer mac80211 instead of nl80211/cfg80211 mix.
Take a look https://lwn.net/Articles/768372/ It's a driver work-in-progress. Worth following
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/aircrack-ng/rtl8812au/issues/347?email_source=notifications&email_token=AAMX56PENR5ZKTPGC6H7WGDPXJ7HLA5CNFSM4HNOTWEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWIEYMY#issuecomment-495995955, or mute the thread https://github.com/notifications/unsubscribe-auth/AAMX56ODF676N7D3AO2YNYTPXJ7HLANCNFSM4HNOTWEA .
Yeah me too, I'll follow it up. Meeting Realtek and Alfa Networks in Taiwan in august at COSCUP, I'll know what thoughts I'll share with 'em
The LPS patch/fix they added to rtw88, they also added to the v5.6.4 branch. And with the other fixes, it's actually acting stable and the range seems to act waaay better. Finally I say
FYI some new consolidation has happened in the rtw88 driver: https://lwn.net/Articles/817736/
There may be some overlap here with other bugs (t2u nano, t4u) but I have a small stack of wifi cards which I expect to work with this driver and don't. How can I help get them supported?