View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000741 | channel: elrepo/el7 | --elrepo--request-for-enhancement-- | public | 2017-05-15 13:59 | 2017-10-05 00:16 |
Reporter | DarkLogix | Assigned To | pperry | ||
Priority | normal | Severity | minor | Reproducibility | N/A |
Status | closed | Resolution | won't fix | ||
Summary | 0000741: Asus USB-AC53 Nano | ||||
Description | Would it be possible to create a package for the Asus USB-AC53 Nano? Per the following link it looks to be the realtek RTL8812BU https://wikidevi.com/wiki/ASUS_USB-AC53_Nano | ||||
Tags | No tags attached. | ||||
Reported upstream | |||||
|
The page you referenced indicates the USB ID is not seen in the linux kernel. Do you know if there is a linux driver provided by the manufacturer? |
|
I thought i had seen one, I'm looking but so far the closes is this http://www.linksys.com/us/support-article?articleNum=226197 It seems both the WUSB6400M and ASUS USB-AC53 use the RTL8812BU chip, and linksys has a MAC driver, so I figure maybe that's close since MAC's run BSD. I'll keep looking incase I find a better match. |
|
Ok so far it looks like the Edimax EW-7822ULC might use the same chipset, I'm still researching to confirm, if that is the case then it looks that they have a linux driver. http://us.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-7822ULC_Linux_Driver_1.0.0.9.zip http://us.edimax.com/edimax/download/download/data/edimax/us/download/for_home/wireless_adapters/wireless_adapters_ac1200_dual-band/ew-7822ulc |
|
Interestingly while the devwiki says RTL8812BU there's a github https://github.com/brandon-bailey/rtl8822bu Which says both the Asus and Edimax use the RTL8822BU. The github has a driver package though I'd expect the one from edimax to be more current. |
|
Thanks for collecting the info. We'll see what we can do. |
|
The code does not build on RHEL 7.4, most likely because RHEL have backported the wireless stack in RHEL 7.4 from kernel-4.11 and the code believes it's a 3.10 kernel. I'm not inclined to build upstream OEM drivers that do not support RHEL or build on RHEL, and (a) they are not trivial for me to fix, and (b) I will need to repeat that work for each new release of RHEL. This is work the OEM vendor should be doing. Sorry, for the sake of $20 I'd recommend purchasing a supported device. Closing as won't fix. |
Date Modified | Username | Field | Change |
---|---|---|---|
2017-05-15 13:59 | DarkLogix | New Issue | |
2017-05-15 13:59 | DarkLogix | Status | new => assigned |
2017-05-15 13:59 | DarkLogix | Assigned To | => stindall |
2017-05-16 11:00 | burakkucat | Assigned To | stindall => toracat |
2017-05-16 11:00 | burakkucat | Category | --elrepo--OTHER-- => --elrepo--request-for-enhancement-- |
2017-05-17 00:24 | toracat | Note Added: 0005190 | |
2017-05-17 12:18 | DarkLogix | Note Added: 0005199 | |
2017-05-17 12:29 | DarkLogix | Note Added: 0005201 | |
2017-05-17 12:59 | DarkLogix | Note Added: 0005202 | |
2017-05-17 13:04 | toracat | Note Added: 0005203 | |
2017-05-17 13:42 | burakkucat | Relationship added | related to 0000739 |
2017-05-17 13:55 | toracat | Assigned To | toracat => burakkucat |
2017-10-04 17:42 | burakkucat | Assigned To | burakkucat => pperry |
2017-10-05 00:16 | pperry | Note Added: 0005545 | |
2017-10-05 00:16 | pperry | Status | assigned => closed |
2017-10-05 00:16 | pperry | Resolution | open => won't fix |