3:12 p.m.
On 18/1/17 6:40 am, Rick Stevens wrote:
On 01/17/2017 12:12 PM, Stephen Morris wrote:
> On 17/1/17 7:49 am, Rick Stevens wrote:
>> On 01/16/2017 12:22 PM, Joe Zeff wrote:
>>> On 01/16/2017 12:17 PM, Stephen Morris wrote:
>>>> I am using kde at the moment and I have cut and pasted the wifi
>>>> password
>>>> back into the Networkmanager definition, and had the new password
>>>> stored
>>>> in Kwallet, but Networkmanager still refuses to recognize that the
>>>> device is a device it can connect to.
>>> Therefor the password isn't the issue. And, as it works under Windows,
>>> it's not hardware.
>> First try "ethtool -i <name-of-device>" to see what driver is
loaded
>> (if any). If you get data back then try "iwlist wlan0 scan" (replace
>> "wlan0" with your device) to see what access points are in the area.
>>
>> If all that works, then the wireless itself is working under Linux and
>> there's something odd about the way NetworkManager (NM) and your device
>> talk to each other. At that point you could try to disable NM and use
>> the wpa_supplicant programs directly to try to get it up (such as
>> running wpa_supplicant in the background and using something like
>> wpa_supplicant_gui to manipulate it). If you're successful there, then
>> try to get NM to talk nice or bugzilla it to the NM list.
> Sorry Rick, how do I determine what the device name is? The only
> information I have been able to determine is that lsusb shows me that
> the usb device is there, and iwconfig says that there are no devices
> with wireless extensions, but I don't see a device in that list that I
> am expecting (I don't remember exactly what the device name was when it
> was being used but I think is started with 'wp').
First, try (as root) "ifconfig -a". A simple "ifconfig" will only
show
interfaces that are "up" and have an IP address.
You could also try (again as root) "iw dev". You should see something
like:
[root@golem4 ~]# iw dev
phy#0
Interface wlan0
ifindex 3
wdev 0x1
addr bc:77:37:51:11:5c
type managed
channel 6 (2437 MHz), width: 20 MHz, center1: 2437 MHz
That shows that my laptop has one physical wireless device whose
physical ID is "phy#0". As far as networking is concerned, the NIC
(network interface card) is called "wlan0" and it has a hardware MAC
(media access controller) address of bc:77:37:51:11:5c. It is currently
associated with a wireless network over channel 6, which means it's got
an IP address on that network and "ifconfig" will display that:
---------------- CUT HERE -------------------------------------
[root@golem4 ~]# ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 4195 bytes 355528 (347.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4195 bytes 355528 (347.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
p4p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.52 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::16fe:b5ff:fea9:a48e prefixlen 64 scopeid 0x20<link>
ether 14:fe:b5:a9:a4:8e txqueuelen 1000 (Ethernet)
RX packets 703055 bytes 437801892 (417.5 MiB)
RX errors 0 dropped 1 overruns 0 frame 0
TX packets 419055 bytes 34250049 (32.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 52:54:00:95:7c:a1 txqueuelen 1000 (Ethernet)
RX packets 51562 bytes 6038644 (5.7 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 55954 bytes 54927745 (52.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.247 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::be77:37ff:fe51:115c prefixlen 64 scopeid 0x20<link>
ether bc:77:37:51:11:5c txqueuelen 1000 (Ethernet)
RX packets 158408 bytes 20391376 (19.4 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 397 bytes 80743 (78.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
---------------- CUT HERE -------------------------------------
Note the entry starting with "wlan0". Also, just for reference, here's
the "ifconfig -a" output:
---------------- CUT HERE -------------------------------------
[root@golem4 ~]# ifconfig -a
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 4195 bytes 355528 (347.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4195 bytes 355528 (347.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
p4p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.52 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::16fe:b5ff:fea9:a48e prefixlen 64 scopeid 0x20<link>
ether 14:fe:b5:a9:a4:8e txqueuelen 1000 (Ethernet)
RX packets 703836 bytes 437862421 (417.5 MiB)
RX errors 0 dropped 1 overruns 0 frame 0
TX packets 419752 bytes 34301624 (32.7 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 52:54:00:95:7c:a1 txqueuelen 1000 (Ethernet)
RX packets 51562 bytes 6038644 (5.7 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 55954 bytes 54927745 (52.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0-nic: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 52:54:00:95:7c:a1 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.247 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::be77:37ff:fe51:115c prefixlen 64 scopeid 0x20<link>
ether bc:77:37:51:11:5c txqueuelen 1000 (Ethernet)
RX packets 158425 bytes 20393862 (19.4 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 397 bytes 80743 (78.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
---------------- CUT HERE -------------------------------------
Note the data for "virbr0-nic" in the "iwconfig -a" output that is
missing from the regular "ifconfig" output. That's because that
interface is not "up" and is not associated with a network. Don't worry
about why, I'm just trying to show that "iwconfig" only returns
"up"
interfaces. If you want to see ALL of them, you must use "ifconfig -a".
Now, with all that being said, if you don't have an appropriate driver
or firmware for the device, the "iw dev" or "ifconfig -a" commands
may
not find it. Yes, physically it's in your USB port and "lsusb" sees it,
but that's just the USB part of the hardware. Without firmware, it may
not work on the network.
Can you send me the USB ID (e.g. the four digit hex "idVendor" and the
four digit hex "idProduct" values from "lsusb -v")? That way we can
see
if it's actually supported and what (if any) firmware is required. It
may even be just that there is an appropriate driver but doesn't
recognize the USB ID so the system won't automatically load it. We can
force a load of the driver and set up the system so it gets loaded even
if the system can't automatically associate that device with that
driver.
> The only difference between the last time I used the wifi device (which
> was probably 6 months ago, I've been using an ethernet 'Home Plug'
> device) and now is that I have put on multiple system upgrades for F24,
> plus at the moment I don't know whether the issue is NetworkManager,
> Kernels or something else.
That's why we want to see if the kernel actually sees it. If the kernel
doesn't see it, why? If the kernel does see it, why won't NM talk to it?
Thanks Rick. The ifconfig -a output is below, the last device listed,
wlp4s6 is the usb wifi device.
enp7s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.138 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::d250:99ff:fe14:547d prefixlen 64 scopeid 0x20<link>
ether d0:50:99:14:54:7d txqueuelen 1000 (Ethernet)
RX packets 1923 bytes 558919 (545.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1275 bytes 172001 (167.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 20 bytes 1736 (1.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 20 bytes 1736 (1.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast
192.168.122.255
ether 00:00:00:00:00:00 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0-nic: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 52:54:00:5d:b8:54 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp4s6: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d8:5d:4c:b4:48:47 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
The iw dev output is also below.
phy#0
Interface wlp4s6
ifindex 3
wdev 0x1
addr d8:5d:4c:b4:48:47
type managed
The lsusb output for that device is also below.
Bus 010 Device 002: ID 2001:331a D-Link Corp.
I did find a command once, when I was trying to determine why for this
AC device Linux refused to use the 5GHz channel, that told me the driver
that had been auto loaded for this device, but I don't remember what the
command was. From memory this command told me the device was using the
ATH9K driver. At the time I was also trying to work out why this driver
was being assigned rather than the ATH10K driver, which some information
I found and again I don't remember where, indicated that the ATH10K
driver may have support the 5GHz channel.
regards,
Steve
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- Batteries not included. Offer not valid in some states. -
- Your mileage may vary. Void where prohibited. -
----------------------------------------------------------------------
4:14 p.m.
New subject: Networkmanagre Refuses to use my Dlink DWA-192 USB Wifi Device in
F24
On 01/17/2017 01:12 PM, Stephen Morris wrote:
On 18/1/17 6:40 am, Rick Stevens wrote:
> On 01/17/2017 12:12 PM, Stephen Morris wrote:
>> On 17/1/17 7:49 am, Rick Stevens wrote:
>>> On 01/16/2017 12:22 PM, Joe Zeff wrote:
>>>> On 01/16/2017 12:17 PM, Stephen Morris wrote:
>>>>> I am using kde at the moment and I have cut and pasted the wifi
>>>>> password
>>>>> back into the Networkmanager definition, and had the new password
>>>>> stored
>>>>> in Kwallet, but Networkmanager still refuses to recognize that the
>>>>> device is a device it can connect to.
>>>> Therefor the password isn't the issue. And, as it works under
>>>> Windows,
>>>> it's not hardware.
>>> First try "ethtool -i <name-of-device>" to see what driver is
loaded
>>> (if any). If you get data back then try "iwlist wlan0 scan"
(replace
>>> "wlan0" with your device) to see what access points are in the
area.
>>>
>>> If all that works, then the wireless itself is working under Linux and
>>> there's something odd about the way NetworkManager (NM) and your device
>>> talk to each other. At that point you could try to disable NM and use
>>> the wpa_supplicant programs directly to try to get it up (such as
>>> running wpa_supplicant in the background and using something like
>>> wpa_supplicant_gui to manipulate it). If you're successful there, then
>>> try to get NM to talk nice or bugzilla it to the NM list.
>> Sorry Rick, how do I determine what the device name is? The only
>> information I have been able to determine is that lsusb shows me that
>> the usb device is there, and iwconfig says that there are no devices
>> with wireless extensions, but I don't see a device in that list that I
>> am expecting (I don't remember exactly what the device name was when it
>> was being used but I think is started with 'wp').
> First, try (as root) "ifconfig -a". A simple "ifconfig" will only
show
> interfaces that are "up" and have an IP address.
>
> You could also try (again as root) "iw dev". You should see something
> like:
>
> [root@golem4 ~]# iw dev
> phy#0
> Interface wlan0
> ifindex 3
> wdev 0x1
> addr bc:77:37:51:11:5c
> type managed
> channel 6 (2437 MHz), width: 20 MHz, center1: 2437 MHz
>
> That shows that my laptop has one physical wireless device whose
> physical ID is "phy#0". As far as networking is concerned, the NIC
> (network interface card) is called "wlan0" and it has a hardware MAC
> (media access controller) address of bc:77:37:51:11:5c. It is currently
> associated with a wireless network over channel 6, which means it's got
> an IP address on that network and "ifconfig" will display that:
>
> ---------------- CUT HERE -------------------------------------
> [root@golem4 ~]# ifconfig
> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
> inet 127.0.0.1 netmask 255.0.0.0
> inet6 ::1 prefixlen 128 scopeid 0x10<host>
> loop txqueuelen 1 (Local Loopback)
> RX packets 4195 bytes 355528 (347.1 KiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 4195 bytes 355528 (347.1 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> p4p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> inet 192.168.1.52 netmask 255.255.255.0 broadcast
> 192.168.1.255
> inet6 fe80::16fe:b5ff:fea9:a48e prefixlen 64 scopeid
> 0x20<link>
> ether 14:fe:b5:a9:a4:8e txqueuelen 1000 (Ethernet)
> RX packets 703055 bytes 437801892 (417.5 MiB)
> RX errors 0 dropped 1 overruns 0 frame 0
> TX packets 419055 bytes 34250049 (32.6 MiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> inet 192.168.122.1 netmask 255.255.255.0 broadcast
> 192.168.122.255
> ether 52:54:00:95:7c:a1 txqueuelen 1000 (Ethernet)
> RX packets 51562 bytes 6038644 (5.7 MiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 55954 bytes 54927745 (52.3 MiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> inet 192.168.1.247 netmask 255.255.255.0 broadcast
> 192.168.1.255
> inet6 fe80::be77:37ff:fe51:115c prefixlen 64 scopeid
> 0x20<link>
> ether bc:77:37:51:11:5c txqueuelen 1000 (Ethernet)
> RX packets 158408 bytes 20391376 (19.4 MiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 397 bytes 80743 (78.8 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> ---------------- CUT HERE -------------------------------------
>
> Note the entry starting with "wlan0". Also, just for reference, here's
> the "ifconfig -a" output:
>
> ---------------- CUT HERE -------------------------------------
> [root@golem4 ~]# ifconfig -a
> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
> inet 127.0.0.1 netmask 255.0.0.0
> inet6 ::1 prefixlen 128 scopeid 0x10<host>
> loop txqueuelen 1 (Local Loopback)
> RX packets 4195 bytes 355528 (347.1 KiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 4195 bytes 355528 (347.1 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> p4p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> inet 192.168.1.52 netmask 255.255.255.0 broadcast
> 192.168.1.255
> inet6 fe80::16fe:b5ff:fea9:a48e prefixlen 64 scopeid
> 0x20<link>
> ether 14:fe:b5:a9:a4:8e txqueuelen 1000 (Ethernet)
> RX packets 703836 bytes 437862421 (417.5 MiB)
> RX errors 0 dropped 1 overruns 0 frame 0
> TX packets 419752 bytes 34301624 (32.7 MiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> inet 192.168.122.1 netmask 255.255.255.0 broadcast
> 192.168.122.255
> ether 52:54:00:95:7c:a1 txqueuelen 1000 (Ethernet)
> RX packets 51562 bytes 6038644 (5.7 MiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 55954 bytes 54927745 (52.3 MiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> virbr0-nic: flags=4098<BROADCAST,MULTICAST> mtu 1500
> ether 52:54:00:95:7c:a1 txqueuelen 1000 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> inet 192.168.1.247 netmask 255.255.255.0 broadcast
> 192.168.1.255
> inet6 fe80::be77:37ff:fe51:115c prefixlen 64 scopeid
> 0x20<link>
> ether bc:77:37:51:11:5c txqueuelen 1000 (Ethernet)
> RX packets 158425 bytes 20393862 (19.4 MiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 397 bytes 80743 (78.8 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> ---------------- CUT HERE -------------------------------------
>
> Note the data for "virbr0-nic" in the "iwconfig -a" output that
is
> missing from the regular "ifconfig" output. That's because that
> interface is not "up" and is not associated with a network. Don't
worry
> about why, I'm just trying to show that "iwconfig" only returns
"up"
> interfaces. If you want to see ALL of them, you must use "ifconfig -a".
>
> Now, with all that being said, if you don't have an appropriate driver
> or firmware for the device, the "iw dev" or "ifconfig -a"
commands may
> not find it. Yes, physically it's in your USB port and "lsusb" sees
it,
> but that's just the USB part of the hardware. Without firmware, it may
> not work on the network.
>
> Can you send me the USB ID (e.g. the four digit hex "idVendor" and the
> four digit hex "idProduct" values from "lsusb -v")? That way we
can see
> if it's actually supported and what (if any) firmware is required. It
> may even be just that there is an appropriate driver but doesn't
> recognize the USB ID so the system won't automatically load it. We can
> force a load of the driver and set up the system so it gets loaded even
> if the system can't automatically associate that device with that
> driver.
>
>> The only difference between the last time I used the wifi device (which
>> was probably 6 months ago, I've been using an ethernet 'Home Plug'
>> device) and now is that I have put on multiple system upgrades for F24,
>> plus at the moment I don't know whether the issue is NetworkManager,
>> Kernels or something else.
> That's why we want to see if the kernel actually sees it. If the kernel
> doesn't see it, why? If the kernel does see it, why won't NM talk to it?
Thanks Rick. The ifconfig -a output is below, the last device listed,
wlp4s6 is the usb wifi device.
enp7s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.138 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::d250:99ff:fe14:547d prefixlen 64 scopeid 0x20<link>
ether d0:50:99:14:54:7d txqueuelen 1000 (Ethernet)
RX packets 1923 bytes 558919 (545.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1275 bytes 172001 (167.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 20 bytes 1736 (1.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 20 bytes 1736 (1.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast
192.168.122.255
ether 00:00:00:00:00:00 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0-nic: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 52:54:00:5d:b8:54 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp4s6: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d8:5d:4c:b4:48:47 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
The iw dev output is also below.
phy#0
Interface wlp4s6
ifindex 3
wdev 0x1
addr d8:5d:4c:b4:48:47
type managed
The lsusb output for that device is also below.
Bus 010 Device 002: ID 2001:331a D-Link Corp.
I did find a command once, when I was trying to determine why for this
AC device Linux refused to use the 5GHz channel, that told me the driver
that had been auto loaded for this device, but I don't remember what the
command was. From memory this command told me the device was using the
ATH9K driver. At the time I was also trying to work out why this driver
was being assigned rather than the ATH10K driver, which some information
I found and again I don't remember where, indicated that the ATH10K
driver may have support the 5GHz channel.
Well, it certainly appears the NIC is seen by the system (it's NIC
name is "wlp4s6"). So, to see what driver is actually being used, as
root:
ethtool -i wlp4s6
As to why NM isn't talking to it, you can try manually configuring NM
to use it. My instructions (using Xfce):
1. Right-click on the NM icon and select "Edit Connections"
2. In the next window, click "Add"
3. In the next window ("Choose a Connection Type"), select
"Wi-Fi"
4. Authenticate
5. In the next window:
a. Set the "Connection name:" appropriately
b. In the "SSID:" box, enter the SSID of the network you
wish to join
c. In the "Mode:" box, select "Client"
d. In the "Device:" box, put in "d8:5d:4c:b4:48:47" (the MAC
address of the device)
e. Leave the rest set to default
f. Click "Create"
That should set up a profile you can use. Close everything down,
left-click on the NM icon and select the network profile you created
(what you entered in step 5b).
From what I can see, that's a D-Link DWA-192 or something, based on
Realtek's 8188 chipset. I'd expect it to be using the rtlwifi driver
and its support items.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- The Theory of Rapitivity: E=MC Hammer -
- -- Glenn Marcus (via TopFive.com) -
----------------------------------------------------------------------
3:02 a.m.
New subject: Networkmanagre Refuses to use my Dlink DWA-192 USB Wifi Device in
F24
On 18/1/17 8:14 am, Rick Stevens wrote:
On 01/17/2017 01:12 PM, Stephen Morris wrote:
> On 18/1/17 6:40 am, Rick Stevens wrote:
>> On 01/17/2017 12:12 PM, Stephen Morris wrote:
>>> On 17/1/17 7:49 am, Rick Stevens wrote:
>>>> On 01/16/2017 12:22 PM, Joe Zeff wrote:
>>>>> On 01/16/2017 12:17 PM, Stephen Morris wrote:
>>>>>> I am using kde at the moment and I have cut and pasted the wifi
>>>>>> password
>>>>>> back into the Networkmanager definition, and had the new
password
>>>>>> stored
>>>>>> in Kwallet, but Networkmanager still refuses to recognize that
the
>>>>>> device is a device it can connect to.
>>>>> Therefor the password isn't the issue. And, as it works under
>>>>> Windows,
>>>>> it's not hardware.
>>>> First try "ethtool -i <name-of-device>" to see what
driver is loaded
>>>> (if any). If you get data back then try "iwlist wlan0 scan"
(replace
>>>> "wlan0" with your device) to see what access points are in the
area.
>>>>
>>>> If all that works, then the wireless itself is working under Linux and
>>>> there's something odd about the way NetworkManager (NM) and your
device
>>>> talk to each other. At that point you could try to disable NM and use
>>>> the wpa_supplicant programs directly to try to get it up (such as
>>>> running wpa_supplicant in the background and using something like
>>>> wpa_supplicant_gui to manipulate it). If you're successful there,
then
>>>> try to get NM to talk nice or bugzilla it to the NM list.
>>> Sorry Rick, how do I determine what the device name is? The only
>>> information I have been able to determine is that lsusb shows me that
>>> the usb device is there, and iwconfig says that there are no devices
>>> with wireless extensions, but I don't see a device in that list that I
>>> am expecting (I don't remember exactly what the device name was when it
>>> was being used but I think is started with 'wp').
>> First, try (as root) "ifconfig -a". A simple "ifconfig" will
only show
>> interfaces that are "up" and have an IP address.
>>
>> You could also try (again as root) "iw dev". You should see something
>> like:
>>
>> [root@golem4 ~]# iw dev
>> phy#0
>> Interface wlan0
>> ifindex 3
>> wdev 0x1
>> addr bc:77:37:51:11:5c
>> type managed
>> channel 6 (2437 MHz), width: 20 MHz, center1: 2437 MHz
>>
>> That shows that my laptop has one physical wireless device whose
>> physical ID is "phy#0". As far as networking is concerned, the NIC
>> (network interface card) is called "wlan0" and it has a hardware MAC
>> (media access controller) address of bc:77:37:51:11:5c. It is currently
>> associated with a wireless network over channel 6, which means it's got
>> an IP address on that network and "ifconfig" will display that:
>>
>> ---------------- CUT HERE -------------------------------------
>> [root@golem4 ~]# ifconfig
>> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
>> inet 127.0.0.1 netmask 255.0.0.0
>> inet6 ::1 prefixlen 128 scopeid 0x10<host>
>> loop txqueuelen 1 (Local Loopback)
>> RX packets 4195 bytes 355528 (347.1 KiB)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 4195 bytes 355528 (347.1 KiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>>
>> p4p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>> inet 192.168.1.52 netmask 255.255.255.0 broadcast
>> 192.168.1.255
>> inet6 fe80::16fe:b5ff:fea9:a48e prefixlen 64 scopeid
>> 0x20<link>
>> ether 14:fe:b5:a9:a4:8e txqueuelen 1000 (Ethernet)
>> RX packets 703055 bytes 437801892 (417.5 MiB)
>> RX errors 0 dropped 1 overruns 0 frame 0
>> TX packets 419055 bytes 34250049 (32.6 MiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>>
>> virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
>> inet 192.168.122.1 netmask 255.255.255.0 broadcast
>> 192.168.122.255
>> ether 52:54:00:95:7c:a1 txqueuelen 1000 (Ethernet)
>> RX packets 51562 bytes 6038644 (5.7 MiB)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 55954 bytes 54927745 (52.3 MiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>>
>> wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>> inet 192.168.1.247 netmask 255.255.255.0 broadcast
>> 192.168.1.255
>> inet6 fe80::be77:37ff:fe51:115c prefixlen 64 scopeid
>> 0x20<link>
>> ether bc:77:37:51:11:5c txqueuelen 1000 (Ethernet)
>> RX packets 158408 bytes 20391376 (19.4 MiB)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 397 bytes 80743 (78.8 KiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>> ---------------- CUT HERE -------------------------------------
>>
>> Note the entry starting with "wlan0". Also, just for reference,
here's
>> the "ifconfig -a" output:
>>
>> ---------------- CUT HERE -------------------------------------
>> [root@golem4 ~]# ifconfig -a
>> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
>> inet 127.0.0.1 netmask 255.0.0.0
>> inet6 ::1 prefixlen 128 scopeid 0x10<host>
>> loop txqueuelen 1 (Local Loopback)
>> RX packets 4195 bytes 355528 (347.1 KiB)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 4195 bytes 355528 (347.1 KiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>>
>> p4p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>> inet 192.168.1.52 netmask 255.255.255.0 broadcast
>> 192.168.1.255
>> inet6 fe80::16fe:b5ff:fea9:a48e prefixlen 64 scopeid
>> 0x20<link>
>> ether 14:fe:b5:a9:a4:8e txqueuelen 1000 (Ethernet)
>> RX packets 703836 bytes 437862421 (417.5 MiB)
>> RX errors 0 dropped 1 overruns 0 frame 0
>> TX packets 419752 bytes 34301624 (32.7 MiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>>
>> virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
>> inet 192.168.122.1 netmask 255.255.255.0 broadcast
>> 192.168.122.255
>> ether 52:54:00:95:7c:a1 txqueuelen 1000 (Ethernet)
>> RX packets 51562 bytes 6038644 (5.7 MiB)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 55954 bytes 54927745 (52.3 MiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>>
>> virbr0-nic: flags=4098<BROADCAST,MULTICAST> mtu 1500
>> ether 52:54:00:95:7c:a1 txqueuelen 1000 (Ethernet)
>> RX packets 0 bytes 0 (0.0 B)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 0 bytes 0 (0.0 B)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>>
>> wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>> inet 192.168.1.247 netmask 255.255.255.0 broadcast
>> 192.168.1.255
>> inet6 fe80::be77:37ff:fe51:115c prefixlen 64 scopeid
>> 0x20<link>
>> ether bc:77:37:51:11:5c txqueuelen 1000 (Ethernet)
>> RX packets 158425 bytes 20393862 (19.4 MiB)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 397 bytes 80743 (78.8 KiB)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>> ---------------- CUT HERE -------------------------------------
>>
>> Note the data for "virbr0-nic" in the "iwconfig -a" output
that is
>> missing from the regular "ifconfig" output. That's because that
>> interface is not "up" and is not associated with a network. Don't
worry
>> about why, I'm just trying to show that "iwconfig" only returns
"up"
>> interfaces. If you want to see ALL of them, you must use "ifconfig
-a".
>>
>> Now, with all that being said, if you don't have an appropriate driver
>> or firmware for the device, the "iw dev" or "ifconfig -a"
commands may
>> not find it. Yes, physically it's in your USB port and "lsusb" sees
it,
>> but that's just the USB part of the hardware. Without firmware, it may
>> not work on the network.
>>
>> Can you send me the USB ID (e.g. the four digit hex "idVendor" and the
>> four digit hex "idProduct" values from "lsusb -v")? That way
we can see
>> if it's actually supported and what (if any) firmware is required. It
>> may even be just that there is an appropriate driver but doesn't
>> recognize the USB ID so the system won't automatically load it. We can
>> force a load of the driver and set up the system so it gets loaded even
>> if the system can't automatically associate that device with that
>> driver.
>>
>>> The only difference between the last time I used the wifi device (which
>>> was probably 6 months ago, I've been using an ethernet 'Home
Plug'
>>> device) and now is that I have put on multiple system upgrades for F24,
>>> plus at the moment I don't know whether the issue is NetworkManager,
>>> Kernels or something else.
>> That's why we want to see if the kernel actually sees it. If the kernel
>> doesn't see it, why? If the kernel does see it, why won't NM talk to it?
> Thanks Rick. The ifconfig -a output is below, the last device listed,
> wlp4s6 is the usb wifi device.
>
> enp7s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> inet 192.168.1.138 netmask 255.255.255.0 broadcast 192.168.1.255
> inet6 fe80::d250:99ff:fe14:547d prefixlen 64 scopeid 0x20<link>
> ether d0:50:99:14:54:7d txqueuelen 1000 (Ethernet)
> RX packets 1923 bytes 558919 (545.8 KiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 1275 bytes 172001 (167.9 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
> inet 127.0.0.1 netmask 255.0.0.0
> inet6 ::1 prefixlen 128 scopeid 0x10<host>
> loop txqueuelen 1 (Local Loopback)
> RX packets 20 bytes 1736 (1.6 KiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 20 bytes 1736 (1.6 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> inet 192.168.122.1 netmask 255.255.255.0 broadcast
> 192.168.122.255
> ether 00:00:00:00:00:00 txqueuelen 1000 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> virbr0-nic: flags=4098<BROADCAST,MULTICAST> mtu 1500
> ether 52:54:00:5d:b8:54 txqueuelen 1000 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> wlp4s6: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> ether d8:5d:4c:b4:48:47 txqueuelen 1000 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> The iw dev output is also below.
>
> phy#0
> Interface wlp4s6
> ifindex 3
> wdev 0x1
> addr d8:5d:4c:b4:48:47
> type managed
>
> The lsusb output for that device is also below.
>
> Bus 010 Device 002: ID 2001:331a D-Link Corp.
>
> I did find a command once, when I was trying to determine why for this
> AC device Linux refused to use the 5GHz channel, that told me the driver
> that had been auto loaded for this device, but I don't remember what the
> command was. From memory this command told me the device was using the
> ATH9K driver. At the time I was also trying to work out why this driver
> was being assigned rather than the ATH10K driver, which some information
> I found and again I don't remember where, indicated that the ATH10K
> driver may have support the 5GHz channel.
Well, it certainly appears the NIC is seen by the system (it's NIC
name is "wlp4s6"). So, to see what driver is actually being used, as
root:
ethtool -i wlp4s6
This command said it couldn't get the driver information
because it
couldn't find the device.
As to why NM isn't talking to it, you can try manually configuring NM
to use it. My instructions (using Xfce):
1. Right-click on the NM icon and select "Edit Connections"
2. In the next window, click "Add"
3. In the next window ("Choose a Connection Type"), select
"Wi-Fi"
4. Authenticate
The NM on my system didn't offer me step 4, it went straight
from step 3
to step 5.
5. In the next window:
a. Set the "Connection name:" appropriately
b. In the "SSID:" box, enter the SSID of the network you
wish to join
c. In the "Mode:" box, select "Client"
I don't get
'client' as an option here, I only get 'Infrastructure',
'Ad-hoc' or 'Access Point'.
d. In the "Device:" box, put in
"d8:5d:4c:b4:48:47" (the MAC
address of the device)
e. Leave the rest set to default
f. Click "Create"
That should set up a profile you can use. Close everything down,
left-click on the NM icon and select the network profile you created
(what you entered in step 5b).
>From what I can see, that's a D-Link DWA-192 or something, based on
Realtek's 8188 chipset. I'd expect it to be using the rtlwifi driver
and its support items.
It is a DWA-192 1900 ac device. I would have thought that it
would use
the realtek driver as well.
regards,
Steve
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- The Theory of Rapitivity: E=MC Hammer -
- -- Glenn Marcus (via TopFive.com) -
----------------------------------------------------------------------
2 p.m.
New subject: [...] D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
On 17.01.2017 22:12, Stephen Morris wrote:
[...]
The lsusb output for that device is also below.
Bus 010 Device 002: ID 2001:331a D-Link Corp.
[...]
D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
https://wikidevi.com/wiki/D-Link_DWA-192
http://support.dlink.com/ProductInfo.aspx?m=DWA-192
ftp://files.dlink.com.au/products/DWA-192
https://openitforum.pl/index/recenzje/karty/d-link-dwa-192-r225
https://wikidevi.com/wiki/Edimax_EW-7833UAC
http://www.edimax.com/edimax/download/download/data/edimax/global/downloa...
http://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-...
https://github.com/pld-linux/rtl8812au
https://github.com/diederikdehaas/rtl8812AU
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
$ unzip EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip
$ cd EW7833UAC_linux_4.3.21_kernel_3.16-4.4/EW7833UAC_linux_v4.3.21_17997.20160531/
$ curl -s https://raw.githubusercontent.com/pld-linux/rtl8812au/master/disable-debu...
| patch -p1
$ curl -s https://github.com/diederikdehaas/rtl8812AU/commit/e6d6beb.patch | patch -p1
$ curl -s https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.7.patch |
patch -p1
$ curl -s https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.8.patch |
patch -p1
$ make -j3
$ su
# cp 8814au.ko /lib/modules/$(uname -r)/updates/
# depmod
# modinfo 8814au | grep 2001
# modprobe -v 8814au
# dmesg:
...
RTL871X: module init start
RTL871X: rtl8814au v4.3.21_17997.20160531
RTL871X: build time: Jan 21 2017 20:04:38
usbcore: registered new interface driver rtl8814au
RTL871X: module init ret=0
...
# modprobe -rv 8814au
# dmesg:
...
RTL871X: module exit start
usbcore: deregistering interface driver rtl8814au
RTL871X: module exit success
...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Wifi ball works now?
HW add.
https://wikidevi.com/wiki/ASUS_USB-AC68
https://www.asus.com/Networking/USB-AC68/HelpDesk_Download
https://wikidevi.com/wiki/TP-LINK_Archer_T9UH
http://www.tp-link.com/en/download/Archer-T9UH.html
https://wikidevi.com/wiki/TRENDnet_TEW-809UB
https://www.trendnet.com/support/supportdetail.asp?prod=100_TEW-809UB
SW add.
https://github.com/abperiasamy/rtl8812AU_8821AU_linux
https://github.com/austinmarton/rtl8812au_linux
8:43 a.m.
New subject: [...] D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
On 21.01.2017 21:00, poma wrote:
On 17.01.2017 22:12, Stephen Morris wrote:
[...]
> The lsusb output for that device is also below.
>
> Bus 010 Device 002: ID 2001:331a D-Link Corp.
>
[...]
D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
https://wikidevi.com/wiki/D-Link_DWA-192
http://support.dlink.com/ProductInfo.aspx?m=DWA-192
ftp://files.dlink.com.au/products/DWA-192
https://openitforum.pl/index/recenzje/karty/d-link-dwa-192-r225
https://wikidevi.com/wiki/Edimax_EW-7833UAC
http://www.edimax.com/edimax/download/download/data/edimax/global/downloa...
http://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-...
https://github.com/pld-linux/rtl8812au
https://github.com/diederikdehaas/rtl8812AU
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
$ unzip EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip
$ cd EW7833UAC_linux_4.3.21_kernel_3.16-4.4/EW7833UAC_linux_v4.3.21_17997.20160531/
$ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/disable-debu... | patch
-p1
$ curl -s https://github.com/diederikdehaas/rtl8812AU/commit/e6d6beb.patch | patch -p1
$ curl -s https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.7.patch |
patch -p1
$ curl -s https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.8.patch |
patch -p1
$ make -j3
$ su
# cp 8814au.ko /lib/modules/$(uname -r)/updates/
# depmod
# modinfo 8814au | grep 2001
# modprobe -v 8814au
# dmesg:
...
RTL871X: module init start
RTL871X: rtl8814au v4.3.21_17997.20160531
RTL871X: build time: Jan 21 2017 20:04:38
usbcore: registered new interface driver rtl8814au
RTL871X: module init ret=0
...
# modprobe -rv 8814au
# dmesg:
...
RTL871X: module exit start
usbcore: deregistering interface driver rtl8814au
RTL871X: module exit success
...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Wifi ball works now?
HW add.
https://wikidevi.com/wiki/ASUS_USB-AC68
https://www.asus.com/Networking/USB-AC68/HelpDesk_Download
https://wikidevi.com/wiki/TP-LINK_Archer_T9UH
http://www.tp-link.com/en/download/Archer-T9UH.html
https://wikidevi.com/wiki/TRENDnet_TEW-809UB
https://www.trendnet.com/support/supportdetail.asp?prod=100_TEW-809UB
SW add.
https://github.com/abperiasamy/rtl8812AU_8821AU_linux
https://github.com/austinmarton/rtl8812au_linux
OR
according to "rtl8814au? #10"
https://github.com/diederikdehaas/rtl8812AU/issues/10
$ git clone -b driver-4.3.21 https://github.com/uminokoe/rtl8812AU.git RTL8814AU-uminokoe
$ cd RTL8814AU-uminokoe/
$ git revert -n 9260f77 8d33100
// "Disabled debugging code."
$ curl -s https://github.com/diederikdehaas/rtl8812AU/commit/3e80ebc.patch | patch -p1
// Enables CONFIG_MP_VHT_HW_TX_MODE
$ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
$ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
OR
$ git clone https://github.com/diederikdehaas/rtl8814AU.git RTL8814AU-diederikdehaas
$ cd RTL8814AU-diederikdehaas/
// Adds missing Vendor/Product ID
$ sed -i '/0xA834/ a\\t{USB_DEVICE(0x7392, 0xA833), .driver_info = RTL8814A}, /*
Edimax - Edimax */' os_dep/linux/usb_intf.c
// "Added VHT capabilities."
$ curl -s https://github.com/uminokoe/rtl8812AU/commit/5f75242.patch | patch -p1
// Enables CONFIG_MP_VHT_HW_TX_MODE
$ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
$ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
$ make -j3
$ su
# cp 8814au.ko /lib/modules/$(uname -r)/updates/
# depmod
# modinfo 8814au
# modprobe -v 8814au
# dmesg:
...
RTL871X: module init start
RTL871X: rtl8814au v4.3.21_17997.20160531
usbcore: registered new interface driver rtl8814au
RTL871X: module init ret=0
...
# modprobe -rv 8814au
# dmesg:
...
RTL871X: module exit start
usbcore: deregistering interface driver rtl8814au
RTL871X: module exit success
...
Hello Diederik,
it seems there are only two Linux RTL8814AU users, so far.
Morris, when you catch some time, would you mind to run a couple iperf tests with
DWA-192,
to see real network throughput results.
2:49 p.m.
New subject: [...] D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
On 23/01/2017 00:43, poma wrote:
On 21.01.2017 21:00, poma wrote:
> On 17.01.2017 22:12, Stephen Morris wrote:
> [...]
>> The lsusb output for that device is also below.
>>
>> Bus 010 Device 002: ID 2001:331a D-Link Corp.
>>
> [...]
>
> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
>
> https://wikidevi.com/wiki/D-Link_DWA-192
> http://support.dlink.com/ProductInfo.aspx?m=DWA-192
> ftp://files.dlink.com.au/products/DWA-192
> https://openitforum.pl/index/recenzje/karty/d-link-dwa-192-r225
>
> https://wikidevi.com/wiki/Edimax_EW-7833UAC
>
http://www.edimax.com/edimax/download/download/data/edimax/global/downloa...
>
http://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-...
>
> https://github.com/pld-linux/rtl8812au
> https://github.com/diederikdehaas/rtl8812AU
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> $ unzip EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip
> $ cd EW7833UAC_linux_4.3.21_kernel_3.16-4.4/EW7833UAC_linux_v4.3.21_17997.20160531/
>
> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/disable-debu... | patch
-p1
> $ curl -s https://github.com/diederikdehaas/rtl8812AU/commit/e6d6beb.patch | patch
-p1
> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.7.patch | patch -p1
> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.8.patch | patch -p1
>
> $ make -j3
> $ su
> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
> # depmod
> # modinfo 8814au | grep 2001
>
> # modprobe -v 8814au
> # dmesg:
> ...
> RTL871X: module init start
> RTL871X: rtl8814au v4.3.21_17997.20160531
> RTL871X: build time: Jan 21 2017 20:04:38
> usbcore: registered new interface driver rtl8814au
> RTL871X: module init ret=0
> ...
> # modprobe -rv 8814au
> # dmesg:
> ...
> RTL871X: module exit start
> usbcore: deregistering interface driver rtl8814au
> RTL871X: module exit success
> ...
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Wifi ball works now?
> HW add.
> https://wikidevi.com/wiki/ASUS_USB-AC68
> https://www.asus.com/Networking/USB-AC68/HelpDesk_Download
>
> https://wikidevi.com/wiki/TP-LINK_Archer_T9UH
> http://www.tp-link.com/en/download/Archer-T9UH.html
>
> https://wikidevi.com/wiki/TRENDnet_TEW-809UB
> https://www.trendnet.com/support/supportdetail.asp?prod=100_TEW-809UB
>
> SW add.
> https://github.com/abperiasamy/rtl8812AU_8821AU_linux
> https://github.com/austinmarton/rtl8812au_linux
>
OR
according to "rtl8814au? #10"
https://github.com/diederikdehaas/rtl8812AU/issues/10
$ git clone -b driver-4.3.21 https://github.com/uminokoe/rtl8812AU.git
RTL8814AU-uminokoe
$ cd RTL8814AU-uminokoe/
$ git revert -n 9260f77 8d33100
// "Disabled debugging code."
$ curl -s https://github.com/diederikdehaas/rtl8812AU/commit/3e80ebc.patch | patch -p1
// Enables CONFIG_MP_VHT_HW_TX_MODE
$ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
$ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
OR
$ git clone https://github.com/diederikdehaas/rtl8814AU.git RTL8814AU-diederikdehaas
$ cd RTL8814AU-diederikdehaas/
// Adds missing Vendor/Product ID
$ sed -i '/0xA834/ a\\t{USB_DEVICE(0x7392, 0xA833), .driver_info = RTL8814A}, /*
Edimax - Edimax */' os_dep/linux/usb_intf.c
// "Added VHT capabilities."
$ curl -s https://github.com/uminokoe/rtl8812AU/commit/5f75242.patch | patch -p1
// Enables CONFIG_MP_VHT_HW_TX_MODE
$ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
$ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
$ make -j3
$ su
# cp 8814au.ko /lib/modules/$(uname -r)/updates/
# depmod
# modinfo 8814au
# modprobe -v 8814au
# dmesg:
...
RTL871X: module init start
RTL871X: rtl8814au v4.3.21_17997.20160531
usbcore: registered new interface driver rtl8814au
RTL871X: module init ret=0
...
# modprobe -rv 8814au
# dmesg:
...
RTL871X: module exit start
usbcore: deregistering interface driver rtl8814au
RTL871X: module exit success
...
Hello Diederik,
it seems there are only two Linux RTL8814AU users, so far.
Morris, when you catch some time, would you mind to run a couple iperf tests with
DWA-192,
to see real network throughput results.
I can't run any at the moment because
Fedora is refusing to actually use
the device at all.
I have also just upgraded to F25 and nothing has changed.
The last time I used this device was on 08/10/2016 and it was using the
ATH9K driver. The main reason I upgraded to this USB device was that I
upgraded my router to a faster version, and I found that unlike the
DWA182 I didn't have to compile my own driver, the kernel had inbuilt
support for the DWA192.
It is possible that I have managed to Blacklist the device in some way,
not by the conventional Blacklist.conf, and I have forgotten how so I
can't find where I've done it to reverse it.
Also, having never done it before, I also don't know how to run iperf tests.
regards,
Steve
4:27 p.m.
New subject: [...] D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
On 22.01.2017 21:49, Stephen Morris wrote:
On 23/01/2017 00:43, poma wrote:
> On 21.01.2017 21:00, poma wrote:
>> On 17.01.2017 22:12, Stephen Morris wrote:
>> [...]
>>> The lsusb output for that device is also below.
>>>
>>> Bus 010 Device 002: ID 2001:331a D-Link Corp.
>>>
>> [...]
>>
>> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
>>
>> https://wikidevi.com/wiki/D-Link_DWA-192
>> http://support.dlink.com/ProductInfo.aspx?m=DWA-192
>> ftp://files.dlink.com.au/products/DWA-192
>> https://openitforum.pl/index/recenzje/karty/d-link-dwa-192-r225
>>
>> https://wikidevi.com/wiki/Edimax_EW-7833UAC
>>
http://www.edimax.com/edimax/download/download/data/edimax/global/downloa...
>>
http://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-...
>>
>> https://github.com/pld-linux/rtl8812au
>> https://github.com/diederikdehaas/rtl8812AU
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> $ unzip EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip
>> $ cd
EW7833UAC_linux_4.3.21_kernel_3.16-4.4/EW7833UAC_linux_v4.3.21_17997.20160531/
>>
>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/disable-debu... | patch
-p1
>> $ curl -s https://github.com/diederikdehaas/rtl8812AU/commit/e6d6beb.patch |
patch -p1
>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.7.patch | patch -p1
>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.8.patch | patch -p1
>>
>> $ make -j3
>> $ su
>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
>> # depmod
>> # modinfo 8814au | grep 2001
>>
>> # modprobe -v 8814au
>> # dmesg:
>> ...
>> RTL871X: module init start
>> RTL871X: rtl8814au v4.3.21_17997.20160531
>> RTL871X: build time: Jan 21 2017 20:04:38
>> usbcore: registered new interface driver rtl8814au
>> RTL871X: module init ret=0
>> ...
>> # modprobe -rv 8814au
>> # dmesg:
>> ...
>> RTL871X: module exit start
>> usbcore: deregistering interface driver rtl8814au
>> RTL871X: module exit success
>> ...
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> Wifi ball works now?
>>
>>
>> HW add.
>> https://wikidevi.com/wiki/ASUS_USB-AC68
>> https://www.asus.com/Networking/USB-AC68/HelpDesk_Download
>>
>> https://wikidevi.com/wiki/TP-LINK_Archer_T9UH
>> http://www.tp-link.com/en/download/Archer-T9UH.html
>>
>> https://wikidevi.com/wiki/TRENDnet_TEW-809UB
>> https://www.trendnet.com/support/supportdetail.asp?prod=100_TEW-809UB
>>
>> SW add.
>> https://github.com/abperiasamy/rtl8812AU_8821AU_linux
>> https://github.com/austinmarton/rtl8812au_linux
>>
>>
>>
> OR
> according to "rtl8814au? #10"
> https://github.com/diederikdehaas/rtl8812AU/issues/10
>
> $ git clone -b driver-4.3.21 https://github.com/uminokoe/rtl8812AU.git
RTL8814AU-uminokoe
> $ cd RTL8814AU-uminokoe/
> $ git revert -n 9260f77 8d33100
> // "Disabled debugging code."
> $ curl -s https://github.com/diederikdehaas/rtl8812AU/commit/3e80ebc.patch | patch
-p1
> // Enables CONFIG_MP_VHT_HW_TX_MODE
> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
>
> OR
> $ git clone https://github.com/diederikdehaas/rtl8814AU.git RTL8814AU-diederikdehaas
> $ cd RTL8814AU-diederikdehaas/
> // Adds missing Vendor/Product ID
> $ sed -i '/0xA834/ a\\t{USB_DEVICE(0x7392, 0xA833), .driver_info = RTL8814A}, /*
Edimax - Edimax */' os_dep/linux/usb_intf.c
> // "Added VHT capabilities."
> $ curl -s https://github.com/uminokoe/rtl8812AU/commit/5f75242.patch | patch -p1
> // Enables CONFIG_MP_VHT_HW_TX_MODE
> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
>
>
> $ make -j3
> $ su
> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
> # depmod
> # modinfo 8814au
>
> # modprobe -v 8814au
> # dmesg:
> ...
> RTL871X: module init start
> RTL871X: rtl8814au v4.3.21_17997.20160531
> usbcore: registered new interface driver rtl8814au
> RTL871X: module init ret=0
> ...
> # modprobe -rv 8814au
> # dmesg:
> ...
> RTL871X: module exit start
> usbcore: deregistering interface driver rtl8814au
> RTL871X: module exit success
> ...
>
>
> Hello Diederik,
> it seems there are only two Linux RTL8814AU users, so far.
>
> Morris, when you catch some time, would you mind to run a couple iperf tests with
DWA-192,
> to see real network throughput results.
I can't run any at the moment because Fedora is refusing to actually use
the device at all.
I have also just upgraded to F25 and nothing has changed.
The last time I used this device was on 08/10/2016 and it was using the
ATH9K driver. The main reason I upgraded to this USB device was that I
upgraded my router to a faster version, and I found that unlike the
DWA182 I didn't have to compile my own driver, the kernel had inbuilt
support for the DWA192.
It is possible that I have managed to Blacklist the device in some way,
not by the conventional Blacklist.conf, and I have forgotten how so I
can't find where I've done it to reverse it.
Also, having never done it before, I also don't know how to run iperf tests.
regards,
Steve
Did I understand you correctly, what you're saying here is that:
D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
therefore the USB based device, was driven by:
$ modinfo --description ath9k
Support for Atheros 802.11n wireless LAN cards.
https://wireless.wiki.kernel.org/en/users/drivers/ath9k
"ath9k is a completely FOSS wireless driver for all Atheros IEEE 802.11n
PCI/PCI-Express and AHB WLAN based chipsets."
https://wiki.debian.org/ath9k
"Atheros 802.11n PCI/PCI-E devices (ath9k)"
2:14 p.m.
New subject: [...] D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
On 23/01/2017 08:27, poma wrote:
On 22.01.2017 21:49, Stephen Morris wrote:
> On 23/01/2017 00:43, poma wrote:
>> On 21.01.2017 21:00, poma wrote:
>>> On 17.01.2017 22:12, Stephen Morris wrote:
>>> [...]
>>>> The lsusb output for that device is also below.
>>>>
>>>> Bus 010 Device 002: ID 2001:331a D-Link Corp.
>>>>
>>> [...]
>>>
>>> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
>>>
>>> https://wikidevi.com/wiki/D-Link_DWA-192
>>> http://support.dlink.com/ProductInfo.aspx?m=DWA-192
>>> ftp://files.dlink.com.au/products/DWA-192
>>> https://openitforum.pl/index/recenzje/karty/d-link-dwa-192-r225
>>>
>>> https://wikidevi.com/wiki/Edimax_EW-7833UAC
>>>
http://www.edimax.com/edimax/download/download/data/edimax/global/downloa...
>>>
http://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-...
>>>
>>> https://github.com/pld-linux/rtl8812au
>>> https://github.com/diederikdehaas/rtl8812AU
>>>
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>
>>> $ unzip EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip
>>> $ cd
EW7833UAC_linux_4.3.21_kernel_3.16-4.4/EW7833UAC_linux_v4.3.21_17997.20160531/
>>>
>>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/disable-debu... | patch
-p1
>>> $ curl -s https://github.com/diederikdehaas/rtl8812AU/commit/e6d6beb.patch |
patch -p1
>>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.7.patch | patch -p1
>>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.8.patch | patch -p1
>>>
>>> $ make -j3
>>> $ su
>>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
>>> # depmod
>>> # modinfo 8814au | grep 2001
>>>
>>> # modprobe -v 8814au
>>> # dmesg:
>>> ...
>>> RTL871X: module init start
>>> RTL871X: rtl8814au v4.3.21_17997.20160531
>>> RTL871X: build time: Jan 21 2017 20:04:38
>>> usbcore: registered new interface driver rtl8814au
>>> RTL871X: module init ret=0
>>> ...
>>> # modprobe -rv 8814au
>>> # dmesg:
>>> ...
>>> RTL871X: module exit start
>>> usbcore: deregistering interface driver rtl8814au
>>> RTL871X: module exit success
>>> ...
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>
>>> Wifi ball works now?
>>>
>>>
>>> HW add.
>>> https://wikidevi.com/wiki/ASUS_USB-AC68
>>> https://www.asus.com/Networking/USB-AC68/HelpDesk_Download
>>>
>>> https://wikidevi.com/wiki/TP-LINK_Archer_T9UH
>>> http://www.tp-link.com/en/download/Archer-T9UH.html
>>>
>>> https://wikidevi.com/wiki/TRENDnet_TEW-809UB
>>> https://www.trendnet.com/support/supportdetail.asp?prod=100_TEW-809UB
>>>
>>> SW add.
>>> https://github.com/abperiasamy/rtl8812AU_8821AU_linux
>>> https://github.com/austinmarton/rtl8812au_linux
>>>
>>>
>>>
>> OR
>> according to "rtl8814au? #10"
>> https://github.com/diederikdehaas/rtl8812AU/issues/10
>>
>> $ git clone -b driver-4.3.21 https://github.com/uminokoe/rtl8812AU.git
RTL8814AU-uminokoe
>> $ cd RTL8814AU-uminokoe/
>> $ git revert -n 9260f77 8d33100
>> // "Disabled debugging code."
>> $ curl -s https://github.com/diederikdehaas/rtl8812AU/commit/3e80ebc.patch |
patch -p1
>> // Enables CONFIG_MP_VHT_HW_TX_MODE
>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
>>
>> OR
>> $ git clone https://github.com/diederikdehaas/rtl8814AU.git
RTL8814AU-diederikdehaas
>> $ cd RTL8814AU-diederikdehaas/
>> // Adds missing Vendor/Product ID
>> $ sed -i '/0xA834/ a\\t{USB_DEVICE(0x7392, 0xA833), .driver_info = RTL8814A},
/* Edimax - Edimax */' os_dep/linux/usb_intf.c
>> // "Added VHT capabilities."
>> $ curl -s https://github.com/uminokoe/rtl8812AU/commit/5f75242.patch | patch -p1
>> // Enables CONFIG_MP_VHT_HW_TX_MODE
>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
>>
>>
>> $ make -j3
>> $ su
>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
>> # depmod
>> # modinfo 8814au
>>
>> # modprobe -v 8814au
>> # dmesg:
>> ...
>> RTL871X: module init start
>> RTL871X: rtl8814au v4.3.21_17997.20160531
>> usbcore: registered new interface driver rtl8814au
>> RTL871X: module init ret=0
>> ...
>> # modprobe -rv 8814au
>> # dmesg:
>> ...
>> RTL871X: module exit start
>> usbcore: deregistering interface driver rtl8814au
>> RTL871X: module exit success
>> ...
>>
>>
>> Hello Diederik,
>> it seems there are only two Linux RTL8814AU users, so far.
>>
>> Morris, when you catch some time, would you mind to run a couple iperf tests with
DWA-192,
>> to see real network throughput results.
> I can't run any at the moment because Fedora is refusing to actually use
> the device at all.
>
> I have also just upgraded to F25 and nothing has changed.
>
> The last time I used this device was on 08/10/2016 and it was using the
> ATH9K driver. The main reason I upgraded to this USB device was that I
> upgraded my router to a faster version, and I found that unlike the
> DWA182 I didn't have to compile my own driver, the kernel had inbuilt
> support for the DWA192.
>
> It is possible that I have managed to Blacklist the device in some way,
> not by the conventional Blacklist.conf, and I have forgotten how so I
> can't find where I've done it to reverse it.
>
> Also, having never done it before, I also don't know how to run iperf tests.
>
> regards,
> Steve
>
Did I understand you correctly, what you're saying here is that:
D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
therefore the USB based device, was driven by:
$ modinfo --description ath9k
Support for Atheros 802.11n wireless LAN cards.
https://wireless.wiki.kernel.org/en/users/drivers/ath9k
"ath9k is a completely FOSS wireless driver for all Atheros IEEE 802.11n
PCI/PCI-Express and AHB WLAN based chipsets."
https://wiki.debian.org/ath9k
"Atheros 802.11n PCI/PCI-E devices (ath9k)"
Yes, when the device was
working iwconfig reported the driver as being
ATH9K, but if refused to use the 5GHz channel. Following a suggestion on
this list I tried compiling my own kernel and setting a recommended
flag, but that had no effect on its ability to use the 5GHz channel. It
was from compiling my own kernel I found that it looked like the ATH10K
driver would support the 5GHz channel, which Winfried de Heiden is
confirming, so at the time I couldn't work out why the system wasn't
assigning the ATH10K driver instead of the ATH9K driver.
From what you are saying it sounds like that various updates to F24
(and in F25 which I am using now) have changed the functionality of
ATH9K to not support USB devices, which would potentially go a long way
towards explaining why my adapter is no longer recognized any more.
Also it seems to me that you are suggesting that I need to go back to
compiling a driver for this card again (if I have to do this will the
driver support the 5GHz channel), if this is so given that from when I
first started using this adapter up until 08/10/2016 there was native
support in the kernel for the device, why has this support been dropped?
I first started using this adapter in F23.
regards,
Steve
11:12 p.m.
New subject: [...] D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
On 23.01.2017 21:14, Stephen Morris wrote:
On 23/01/2017 08:27, poma wrote:
> On 22.01.2017 21:49, Stephen Morris wrote:
>> On 23/01/2017 00:43, poma wrote:
>>> On 21.01.2017 21:00, poma wrote:
>>>> On 17.01.2017 22:12, Stephen Morris wrote:
>>>> [...]
>>>>> The lsusb output for that device is also below.
>>>>>
>>>>> Bus 010 Device 002: ID 2001:331a D-Link Corp.
>>>>>
>>>> [...]
>>>>
>>>> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
>>>>
>>>> https://wikidevi.com/wiki/D-Link_DWA-192
>>>> http://support.dlink.com/ProductInfo.aspx?m=DWA-192
>>>> ftp://files.dlink.com.au/products/DWA-192
>>>> https://openitforum.pl/index/recenzje/karty/d-link-dwa-192-r225
>>>>
>>>> https://wikidevi.com/wiki/Edimax_EW-7833UAC
>>>>
http://www.edimax.com/edimax/download/download/data/edimax/global/downloa...
>>>>
http://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-...
>>>>
>>>> https://github.com/pld-linux/rtl8812au
>>>> https://github.com/diederikdehaas/rtl8812AU
>>>>
>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>
>>>> $ unzip EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip
>>>> $ cd
EW7833UAC_linux_4.3.21_kernel_3.16-4.4/EW7833UAC_linux_v4.3.21_17997.20160531/
>>>>
>>>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/disable-debu... | patch
-p1
>>>> $ curl -s
https://github.com/diederikdehaas/rtl8812AU/commit/e6d6beb.patch | patch -p1
>>>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.7.patch | patch -p1
>>>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.8.patch | patch -p1
>>>>
>>>> $ make -j3
>>>> $ su
>>>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
>>>> # depmod
>>>> # modinfo 8814au | grep 2001
>>>>
>>>> # modprobe -v 8814au
>>>> # dmesg:
>>>> ...
>>>> RTL871X: module init start
>>>> RTL871X: rtl8814au v4.3.21_17997.20160531
>>>> RTL871X: build time: Jan 21 2017 20:04:38
>>>> usbcore: registered new interface driver rtl8814au
>>>> RTL871X: module init ret=0
>>>> ...
>>>> # modprobe -rv 8814au
>>>> # dmesg:
>>>> ...
>>>> RTL871X: module exit start
>>>> usbcore: deregistering interface driver rtl8814au
>>>> RTL871X: module exit success
>>>> ...
>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>
>>>> Wifi ball works now?
>>>>
>>>>
>>>> HW add.
>>>> https://wikidevi.com/wiki/ASUS_USB-AC68
>>>> https://www.asus.com/Networking/USB-AC68/HelpDesk_Download
>>>>
>>>> https://wikidevi.com/wiki/TP-LINK_Archer_T9UH
>>>> http://www.tp-link.com/en/download/Archer-T9UH.html
>>>>
>>>> https://wikidevi.com/wiki/TRENDnet_TEW-809UB
>>>> https://www.trendnet.com/support/supportdetail.asp?prod=100_TEW-809UB
>>>>
>>>> SW add.
>>>> https://github.com/abperiasamy/rtl8812AU_8821AU_linux
>>>> https://github.com/austinmarton/rtl8812au_linux
>>>>
>>>>
>>>>
>>> OR
>>> according to "rtl8814au? #10"
>>> https://github.com/diederikdehaas/rtl8812AU/issues/10
>>>
>>> $ git clone -b driver-4.3.21 https://github.com/uminokoe/rtl8812AU.git
RTL8814AU-uminokoe
>>> $ cd RTL8814AU-uminokoe/
>>> $ git revert -n 9260f77 8d33100
>>> // "Disabled debugging code."
>>> $ curl -s https://github.com/diederikdehaas/rtl8812AU/commit/3e80ebc.patch |
patch -p1
>>> // Enables CONFIG_MP_VHT_HW_TX_MODE
>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
>>>
>>> OR
>>> $ git clone https://github.com/diederikdehaas/rtl8814AU.git
RTL8814AU-diederikdehaas
>>> $ cd RTL8814AU-diederikdehaas/
>>> // Adds missing Vendor/Product ID
>>> $ sed -i '/0xA834/ a\\t{USB_DEVICE(0x7392, 0xA833), .driver_info =
RTL8814A}, /* Edimax - Edimax */' os_dep/linux/usb_intf.c
>>> // "Added VHT capabilities."
>>> $ curl -s https://github.com/uminokoe/rtl8812AU/commit/5f75242.patch | patch
-p1
>>> // Enables CONFIG_MP_VHT_HW_TX_MODE
>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
>>>
>>>
>>> $ make -j3
>>> $ su
>>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
>>> # depmod
>>> # modinfo 8814au
>>>
>>> # modprobe -v 8814au
>>> # dmesg:
>>> ...
>>> RTL871X: module init start
>>> RTL871X: rtl8814au v4.3.21_17997.20160531
>>> usbcore: registered new interface driver rtl8814au
>>> RTL871X: module init ret=0
>>> ...
>>> # modprobe -rv 8814au
>>> # dmesg:
>>> ...
>>> RTL871X: module exit start
>>> usbcore: deregistering interface driver rtl8814au
>>> RTL871X: module exit success
>>> ...
>>>
>>>
>>> Hello Diederik,
>>> it seems there are only two Linux RTL8814AU users, so far.
>>>
>>> Morris, when you catch some time, would you mind to run a couple iperf tests
with DWA-192,
>>> to see real network throughput results.
>> I can't run any at the moment because Fedora is refusing to actually use
>> the device at all.
>>
>> I have also just upgraded to F25 and nothing has changed.
>>
>> The last time I used this device was on 08/10/2016 and it was using the
>> ATH9K driver. The main reason I upgraded to this USB device was that I
>> upgraded my router to a faster version, and I found that unlike the
>> DWA182 I didn't have to compile my own driver, the kernel had inbuilt
>> support for the DWA192.
>>
>> It is possible that I have managed to Blacklist the device in some way,
>> not by the conventional Blacklist.conf, and I have forgotten how so I
>> can't find where I've done it to reverse it.
>>
>> Also, having never done it before, I also don't know how to run iperf tests.
>>
>> regards,
>> Steve
>>
> Did I understand you correctly, what you're saying here is that:
> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
> therefore the USB based device, was driven by:
> $ modinfo --description ath9k
> Support for Atheros 802.11n wireless LAN cards.
> https://wireless.wiki.kernel.org/en/users/drivers/ath9k
> "ath9k is a completely FOSS wireless driver for all Atheros IEEE 802.11n
PCI/PCI-Express and AHB WLAN based chipsets."
> https://wiki.debian.org/ath9k
> "Atheros 802.11n PCI/PCI-E devices (ath9k)"
Yes, when the device was working iwconfig reported the driver as being
ATH9K, but if refused to use the 5GHz channel. Following a suggestion on
this list I tried compiling my own kernel and setting a recommended
flag, but that had no effect on its ability to use the 5GHz channel. It
was from compiling my own kernel I found that it looked like the ATH10K
driver would support the 5GHz channel, which Winfried de Heiden is
confirming, so at the time I couldn't work out why the system wasn't
assigning the ATH10K driver instead of the ATH9K driver.
From what you are saying it sounds like that various updates to F24
(and in F25 which I am using now) have changed the functionality of
ATH9K to not support USB devices, which would potentially go a long way
towards explaining why my adapter is no longer recognized any more.
Also it seems to me that you are suggesting that I need to go back to
compiling a driver for this card again (if I have to do this will the
driver support the 5GHz channel), if this is so given that from when I
first started using this adapter up until 08/10/2016 there was native
support in the kernel for the device, why has this support been dropped?
I first started using this adapter in F23.
regards,
Steve
This should show the WiFi devices that are connected to the machine:
$ echo ; lspci -knn -d ::0280 ; echo ; lsusb ; echo ; lsusb -t ; echo
Would you mind copy and paste the output here.
8:17 a.m.
New subject: [...] D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
Stephen,
I think that Poma finds it extraordinary that your device was working with
a driver for a completely different chipset. I know I do.
On Tue, Jan 24, 2017 at 12:12 AM, poma <pomidorabelisima(a)gmail.com> wrote:
On 23.01.2017 21:14, Stephen Morris wrote:
> On 23/01/2017 08:27, poma wrote:
>> On 22.01.2017 21:49, Stephen Morris wrote:
>>> On 23/01/2017 00:43, poma wrote:
>>>> On 21.01.2017 21:00, poma wrote:
>>>>> On 17.01.2017 22:12, Stephen Morris wrote:
>>>>> [...]
>>>>>> The lsusb output for that device is also below.
>>>>>>
>>>>>> Bus 010 Device 002: ID 2001:331a D-Link Corp.
>>>>>>
>>>>> [...]
>>>>>
>>>>> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
>>>>>
>>>>> https://wikidevi.com/wiki/D-Link_DWA-192
>>>>> http://support.dlink.com/ProductInfo.aspx?m=DWA-192
>>>>> ftp://files.dlink.com.au/products/DWA-192
>>>>> https://openitforum.pl/index/recenzje/karty/d-link-dwa-192-r225
>>>>>
>>>>> https://wikidevi.com/wiki/Edimax_EW-7833UAC
>>>>> http://www.edimax.com/edimax/download/download/data/edimax/
global/download/for_home/wireless_adapters/wireless_
adapters_ac1750_dual-band/ew-7833uac
>>>>> http://www.edimax.com/edimax/mw/cufiles/files/download/
Driver_Utility/EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip
>>>>>
>>>>> https://github.com/pld-linux/rtl8812au
>>>>> https://github.com/diederikdehaas/rtl8812AU
>>>>>
>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>
>>>>> $ unzip EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip
>>>>> $ cd EW7833UAC_linux_4.3.21_kernel_3.16-4.4/EW7833UAC_linux_v4.3.
21_17997.20160531/
>>>>>
>>>>> $ curl -s https://raw.githubusercontent.com/pld-linux/rtl8812au/
master/disable-debug.patch | patch -p1
>>>>> $ curl -s https://github.com/diederikdehaas/rtl8812AU/
commit/e6d6beb.patch | patch -p1
>>>>> $ curl -s https://raw.githubusercontent.com/pld-linux/rtl8812au/
master/linux-4.7.patch | patch -p1
>>>>> $ curl -s https://raw.githubusercontent.com/pld-linux/rtl8812au/
master/linux-4.8.patch | patch -p1
>>>>>
>>>>> $ make -j3
>>>>> $ su
>>>>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
>>>>> # depmod
>>>>> # modinfo 8814au | grep 2001
>>>>>
>>>>> # modprobe -v 8814au
>>>>> # dmesg:
>>>>> ...
>>>>> RTL871X: module init start
>>>>> RTL871X: rtl8814au v4.3.21_17997.20160531
>>>>> RTL871X: build time: Jan 21 2017 20:04:38
>>>>> usbcore: registered new interface driver rtl8814au
>>>>> RTL871X: module init ret=0
>>>>> ...
>>>>> # modprobe -rv 8814au
>>>>> # dmesg:
>>>>> ...
>>>>> RTL871X: module exit start
>>>>> usbcore: deregistering interface driver rtl8814au
>>>>> RTL871X: module exit success
>>>>> ...
>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>
>>>>> Wifi ball works now?
>>>>>
>>>>>
>>>>> HW add.
>>>>> https://wikidevi.com/wiki/ASUS_USB-AC68
>>>>> https://www.asus.com/Networking/USB-AC68/HelpDesk_Download
>>>>>
>>>>> https://wikidevi.com/wiki/TP-LINK_Archer_T9UH
>>>>> http://www.tp-link.com/en/download/Archer-T9UH.html
>>>>>
>>>>> https://wikidevi.com/wiki/TRENDnet_TEW-809UB
>>>>> https://www.trendnet.com/support/supportdetail.asp?
prod=100_TEW-809UB
>>>>>
>>>>> SW add.
>>>>> https://github.com/abperiasamy/rtl8812AU_8821AU_linux
>>>>> https://github.com/austinmarton/rtl8812au_linux
>>>>>
>>>>>
>>>>>
>>>> OR
>>>> according to "rtl8814au? #10"
>>>> https://github.com/diederikdehaas/rtl8812AU/issues/10
>>>>
>>>> $ git clone -b driver-4.3.21 https://github.com/uminokoe/
rtl8812AU.git RTL8814AU-uminokoe
>>>> $ cd RTL8814AU-uminokoe/
>>>> $ git revert -n 9260f77 8d33100
>>>> // "Disabled debugging code."
>>>> $ curl -s https://github.com/diederikdehaas/rtl8812AU/
commit/3e80ebc.patch | patch -p1
>>>> // Enables CONFIG_MP_VHT_HW_TX_MODE
>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
>>>>
>>>> OR
>>>> $ git clone https://github.com/diederikdehaas/rtl8814AU.git
RTL8814AU-diederikdehaas
>>>> $ cd RTL8814AU-diederikdehaas/
>>>> // Adds missing Vendor/Product ID
>>>> $ sed -i '/0xA834/ a\\t{USB_DEVICE(0x7392, 0xA833), .driver_info =
RTL8814A}, /* Edimax - Edimax */' os_dep/linux/usb_intf.c
>>>> // "Added VHT capabilities."
>>>> $ curl -s https://github.com/uminokoe/rtl8812AU/commit/5f75242.patch
| patch -p1
>>>> // Enables CONFIG_MP_VHT_HW_TX_MODE
>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
>>>>
>>>>
>>>> $ make -j3
>>>> $ su
>>>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
>>>> # depmod
>>>> # modinfo 8814au
>>>>
>>>> # modprobe -v 8814au
>>>> # dmesg:
>>>> ...
>>>> RTL871X: module init start
>>>> RTL871X: rtl8814au v4.3.21_17997.20160531
>>>> usbcore: registered new interface driver rtl8814au
>>>> RTL871X: module init ret=0
>>>> ...
>>>> # modprobe -rv 8814au
>>>> # dmesg:
>>>> ...
>>>> RTL871X: module exit start
>>>> usbcore: deregistering interface driver rtl8814au
>>>> RTL871X: module exit success
>>>> ...
>>>>
>>>>
>>>> Hello Diederik,
>>>> it seems there are only two Linux RTL8814AU users, so far.
>>>>
>>>> Morris, when you catch some time, would you mind to run a couple
iperf tests with DWA-192,
>>>> to see real network throughput results.
>>> I can't run any at the moment because Fedora is refusing to actually
use
>>> the device at all.
>>>
>>> I have also just upgraded to F25 and nothing has changed.
>>>
>>> The last time I used this device was on 08/10/2016 and it was using the
>>> ATH9K driver. The main reason I upgraded to this USB device was that I
>>> upgraded my router to a faster version, and I found that unlike the
>>> DWA182 I didn't have to compile my own driver, the kernel had inbuilt
>>> support for the DWA192.
>>>
>>> It is possible that I have managed to Blacklist the device in some way,
>>> not by the conventional Blacklist.conf, and I have forgotten how so I
>>> can't find where I've done it to reverse it.
>>>
>>> Also, having never done it before, I also don't know how to run iperf
tests.
>>>
>>> regards,
>>> Steve
>>>
>> Did I understand you correctly, what you're saying here is that:
>> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
>> therefore the USB based device, was driven by:
>> $ modinfo --description ath9k
>> Support for Atheros 802.11n wireless LAN cards.
>> https://wireless.wiki.kernel.org/en/users/drivers/ath9k
>> "ath9k is a completely FOSS wireless driver for all Atheros IEEE
802.11n PCI/PCI-Express and AHB WLAN based chipsets."
>> https://wiki.debian.org/ath9k
>> "Atheros 802.11n PCI/PCI-E devices (ath9k)"
> Yes, when the device was working iwconfig reported the driver as being
> ATH9K, but if refused to use the 5GHz channel. Following a suggestion on
> this list I tried compiling my own kernel and setting a recommended
> flag, but that had no effect on its ability to use the 5GHz channel. It
> was from compiling my own kernel I found that it looked like the ATH10K
> driver would support the 5GHz channel, which Winfried de Heiden is
> confirming, so at the time I couldn't work out why the system wasn't
> assigning the ATH10K driver instead of the ATH9K driver.
> From what you are saying it sounds like that various updates to F24
> (and in F25 which I am using now) have changed the functionality of
> ATH9K to not support USB devices, which would potentially go a long way
> towards explaining why my adapter is no longer recognized any more.
> Also it seems to me that you are suggesting that I need to go back to
> compiling a driver for this card again (if I have to do this will the
> driver support the 5GHz channel), if this is so given that from when I
> first started using this adapter up until 08/10/2016 there was native
> support in the kernel for the device, why has this support been dropped?
> I first started using this adapter in F23.
>
> regards,
> Steve
This should show the WiFi devices that are connected to the machine:
$ echo ; lspci -knn -d ::0280 ; echo ; lsusb ; echo ; lsusb -t ; echo
Would you mind copy and paste the output here.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
3:17 p.m.
New subject: [...] D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
On 25/01/2017 00:17, Terry Polzin wrote:
Stephen,
I think that Poma finds it extraordinary that your device was working
with a driver for a completely different chipset. I know I do.
I can understand
that. The iwconfig output could have been showing the
wrong driver, but at the time I also raised a bug on bugzilla around the
fact that the driver would not active the 5GHz channel on the adapter,
which at the moment has gone nowhere.
regards,
Steve
On Tue, Jan 24, 2017 at 12:12 AM, poma <pomidorabelisima(a)gmail.com
<mailto:pomidorabelisima@gmail.com>> wrote:
On 23.01.2017 21:14, Stephen Morris wrote:
> On 23/01/2017 08:27, poma wrote:
>> On 22.01.2017 21:49, Stephen Morris wrote:
>>> On 23/01/2017 00:43, poma wrote:
>>>> On 21.01.2017 21:00, poma wrote:
>>>>> On 17.01.2017 22:12, Stephen Morris wrote:
>>>>> [...]
>>>>>> The lsusb output for that device is also below.
>>>>>>
>>>>>> Bus 010 Device 002: ID 2001:331a D-Link Corp.
>>>>>>
>>>>> [...]
>>>>>
>>>>> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
>>>>>
>>>>> https://wikidevi.com/wiki/D-Link_DWA-192
<https://wikidevi.com/wiki/D-Link_DWA-192>
>>>>> http://support.dlink.com/ProductInfo.aspx?m=DWA-192
<http://support.dlink.com/ProductInfo.aspx?m=DWA-192>
>>>>> ftp://files.dlink.com.au/products/DWA-192
<ftp://files.dlink.com.au/products/DWA-192>
>>>>>
https://openitforum.pl/index/recenzje/karty/d-link-dwa-192-r225
<https://openitforum.pl/index/recenzje/karty/d-link-dwa-192-r225>
>>>>>
>>>>> https://wikidevi.com/wiki/Edimax_EW-7833UAC
<https://wikidevi.com/wiki/Edimax_EW-7833UAC>
>>>>>
http://www.edimax.com/edimax/download/download/data/edimax/global/downloa...
<http://www.edimax.com/edimax/download/download/data/edimax/global/downloa...
>>>>>
http://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-...
<http://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-...
>>>>>
>>>>> https://github.com/pld-linux/rtl8812au
<https://github.com/pld-linux/rtl8812au>
>>>>> https://github.com/diederikdehaas/rtl8812AU
<https://github.com/diederikdehaas/rtl8812AU>
>>>>>
>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>
>>>>> $ unzip EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip
>>>>> $ cd
EW7833UAC_linux_4.3.21_kernel_3.16-4.4/EW7833UAC_linux_v4.3.21_17997.20160531/
>>>>>
>>>>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/disable-debu...
<https://raw.githubusercontent.com/pld-linux/rtl8812au/master/disable-debu...
| patch -p1
>>>>> $ curl -s
https://github.com/diederikdehaas/rtl8812AU/commit/e6d6beb.patch
<https://github.com/diederikdehaas/rtl8812AU/commit/e6d6beb.patch>
| patch -p1
>>>>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.7.patch
<https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.7.pa...
| patch -p1
>>>>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.8.patch
<https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.8.pa...
| patch -p1
>>>>>
>>>>> $ make -j3
>>>>> $ su
>>>>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
>>>>> # depmod
>>>>> # modinfo 8814au | grep 2001
>>>>>
>>>>> # modprobe -v 8814au
>>>>> # dmesg:
>>>>> ...
>>>>> RTL871X: module init start
>>>>> RTL871X: rtl8814au v4.3.21_17997.20160531
>>>>> RTL871X: build time: Jan 21 2017 20:04:38
>>>>> usbcore: registered new interface driver rtl8814au
>>>>> RTL871X: module init ret=0
>>>>> ...
>>>>> # modprobe -rv 8814au
>>>>> # dmesg:
>>>>> ...
>>>>> RTL871X: module exit start
>>>>> usbcore: deregistering interface driver rtl8814au
>>>>> RTL871X: module exit success
>>>>> ...
>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>
>>>>> Wifi ball works now?
>>>>>
>>>>>
>>>>> HW add.
>>>>> https://wikidevi.com/wiki/ASUS_USB-AC68
<https://wikidevi.com/wiki/ASUS_USB-AC68>
>>>>> https://www.asus.com/Networking/USB-AC68/HelpDesk_Download
<https://www.asus.com/Networking/USB-AC68/HelpDesk_Download>
>>>>>
>>>>> https://wikidevi.com/wiki/TP-LINK_Archer_T9UH
<https://wikidevi.com/wiki/TP-LINK_Archer_T9UH>
>>>>> http://www.tp-link.com/en/download/Archer-T9UH.html
<http://www.tp-link.com/en/download/Archer-T9UH.html>
>>>>>
>>>>> https://wikidevi.com/wiki/TRENDnet_TEW-809UB
<https://wikidevi.com/wiki/TRENDnet_TEW-809UB>
>>>>>
https://www.trendnet.com/support/supportdetail.asp?prod=100_TEW-809UB
<https://www.trendnet.com/support/supportdetail.asp?prod=100_TEW-809UB>
>>>>>
>>>>> SW add.
>>>>> https://github.com/abperiasamy/rtl8812AU_8821AU_linux
<https://github.com/abperiasamy/rtl8812AU_8821AU_linux>
>>>>> https://github.com/austinmarton/rtl8812au_linux
<https://github.com/austinmarton/rtl8812au_linux>
>>>>>
>>>>>
>>>>>
>>>> OR
>>>> according to "rtl8814au? #10"
>>>> https://github.com/diederikdehaas/rtl8812AU/issues/10
<https://github.com/diederikdehaas/rtl8812AU/issues/10>
>>>>
>>>> $ git clone -b driver-4.3.21
https://github.com/uminokoe/rtl8812AU.git
<https://github.com/uminokoe/rtl8812AU.git> RTL8814AU-uminokoe
>>>> $ cd RTL8814AU-uminokoe/
>>>> $ git revert -n 9260f77 8d33100
>>>> // "Disabled debugging code."
>>>> $ curl -s
https://github.com/diederikdehaas/rtl8812AU/commit/3e80ebc.patch
<https://github.com/diederikdehaas/rtl8812AU/commit/3e80ebc.patch>
| patch -p1
>>>> // Enables CONFIG_MP_VHT_HW_TX_MODE
>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
>>>>
>>>> OR
>>>> $ git clone https://github.com/diederikdehaas/rtl8814AU.git
<https://github.com/diederikdehaas/rtl8814AU.git>
RTL8814AU-diederikdehaas
>>>> $ cd RTL8814AU-diederikdehaas/
>>>> // Adds missing Vendor/Product ID
>>>> $ sed -i '/0xA834/ a\\t{USB_DEVICE(0x7392, 0xA833),
.driver_info = RTL8814A}, /* Edimax - Edimax */'
os_dep/linux/usb_intf.c
>>>> // "Added VHT capabilities."
>>>> $ curl -s
https://github.com/uminokoe/rtl8812AU/commit/5f75242.patch
<https://github.com/uminokoe/rtl8812AU/commit/5f75242.patch> |
patch -p1
>>>> // Enables CONFIG_MP_VHT_HW_TX_MODE
>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
>>>>
>>>>
>>>> $ make -j3
>>>> $ su
>>>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
>>>> # depmod
>>>> # modinfo 8814au
>>>>
>>>> # modprobe -v 8814au
>>>> # dmesg:
>>>> ...
>>>> RTL871X: module init start
>>>> RTL871X: rtl8814au v4.3.21_17997.20160531
>>>> usbcore: registered new interface driver rtl8814au
>>>> RTL871X: module init ret=0
>>>> ...
>>>> # modprobe -rv 8814au
>>>> # dmesg:
>>>> ...
>>>> RTL871X: module exit start
>>>> usbcore: deregistering interface driver rtl8814au
>>>> RTL871X: module exit success
>>>> ...
>>>>
>>>>
>>>> Hello Diederik,
>>>> it seems there are only two Linux RTL8814AU users, so far.
>>>>
>>>> Morris, when you catch some time, would you mind to run a
couple iperf tests with DWA-192,
>>>> to see real network throughput results.
>>> I can't run any at the moment because Fedora is refusing to
actually use
>>> the device at all.
>>>
>>> I have also just upgraded to F25 and nothing has changed.
>>>
>>> The last time I used this device was on 08/10/2016 and it was
using the
>>> ATH9K driver. The main reason I upgraded to this USB device
was that I
>>> upgraded my router to a faster version, and I found that
unlike the
>>> DWA182 I didn't have to compile my own driver, the kernel had
inbuilt
>>> support for the DWA192.
>>>
>>> It is possible that I have managed to Blacklist the device in
some way,
>>> not by the conventional Blacklist.conf, and I have forgotten
how so I
>>> can't find where I've done it to reverse it.
>>>
>>> Also, having never done it before, I also don't know how to
run iperf tests.
>>>
>>> regards,
>>> Steve
>>>
>> Did I understand you correctly, what you're saying here is that:
>> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
>> therefore the USB based device, was driven by:
>> $ modinfo --description ath9k
>> Support for Atheros 802.11n wireless LAN cards.
>> https://wireless.wiki.kernel.org/en/users/drivers/ath9k
<https://wireless.wiki.kernel.org/en/users/drivers/ath9k>
>> "ath9k is a completely FOSS wireless driver for all Atheros
IEEE 802.11n PCI/PCI-Express and AHB WLAN based chipsets."
>> https://wiki.debian.org/ath9k
>> "Atheros 802.11n PCI/PCI-E devices (ath9k)"
> Yes, when the device was working iwconfig reported the driver as
being
> ATH9K, but if refused to use the 5GHz channel. Following a
suggestion on
> this list I tried compiling my own kernel and setting a recommended
> flag, but that had no effect on its ability to use the 5GHz
channel. It
> was from compiling my own kernel I found that it looked like the
ATH10K
> driver would support the 5GHz channel, which Winfried de Heiden is
> confirming, so at the time I couldn't work out why the system wasn't
> assigning the ATH10K driver instead of the ATH9K driver.
> From what you are saying it sounds like that various updates to F24
> (and in F25 which I am using now) have changed the functionality of
> ATH9K to not support USB devices, which would potentially go a
long way
> towards explaining why my adapter is no longer recognized any more.
> Also it seems to me that you are suggesting that I need to go
back to
> compiling a driver for this card again (if I have to do this
will the
> driver support the 5GHz channel), if this is so given that from
when I
> first started using this adapter up until 08/10/2016 there was
native
> support in the kernel for the device, why has this support been
dropped?
> I first started using this adapter in F23.
>
> regards,
> Steve
This should show the WiFi devices that are connected to the machine:
$ echo ; lspci -knn -d ::0280 ; echo ; lsusb ; echo ; lsusb -t ; echo
Would you mind copy and paste the output here.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
<mailto:users@lists.fedoraproject.org>
To unsubscribe send an email to
users-leave(a)lists.fedoraproject.org
<mailto:users-leave@lists.fedoraproject.org>
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
3:24 p.m.
New subject: [...] D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
bus 010 device 002 is a pci device not a usb device the way I read this
output.
On Thu, Jan 26, 2017 at 4:17 PM, Stephen Morris <samorris(a)netspace.net.au>
wrote:
On 25/01/2017 00:17, Terry Polzin wrote:
> Stephen,
>
> I think that Poma finds it extraordinary that your device was working
> with a driver for a completely different chipset. I know I do.
>
I can understand that. The iwconfig output could have been showing the
wrong driver, but at the time I also raised a bug on bugzilla around the
fact that the driver would not active the 5GHz channel on the adapter,
which at the moment has gone nowhere.
regards,
Steve
> On Tue, Jan 24, 2017 at 12:12 AM, poma <pomidorabelisima(a)gmail.com
> <mailto:pomidorabelisima@gmail.com>> wrote:
>
> On 23.01.2017 21:14, Stephen Morris wrote:
> > On 23/01/2017 08:27, poma wrote:
> >> On 22.01.2017 21:49, Stephen Morris wrote:
> >>> On 23/01/2017 00:43, poma wrote:
> >>>> On 21.01.2017 21:00, poma wrote:
> >>>>> On 17.01.2017 22:12, Stephen Morris wrote:
> >>>>> [...]
> >>>>>> The lsusb output for that device is also below.
> >>>>>>
> >>>>>> Bus 010 Device 002: ID 2001:331a D-Link Corp.
> >>>>>>
> >>>>> [...]
> >>>>>
> >>>>> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
> >>>>>
> >>>>> https://wikidevi.com/wiki/D-Link_DWA-192
> <https://wikidevi.com/wiki/D-Link_DWA-192>
> >>>>> http://support.dlink.com/ProductInfo.aspx?m=DWA-192
> <http://support.dlink.com/ProductInfo.aspx?m=DWA-192>
> >>>>> ftp://files.dlink.com.au/products/DWA-192
> <ftp://files.dlink.com.au/products/DWA-192>
> >>>>>
> https://openitforum.pl/index/recenzje/karty/d-link-dwa-192-r225
> <https://openitforum.pl/index/recenzje/karty/d-link-dwa-192-r225>
> >>>>>
> >>>>> https://wikidevi.com/wiki/Edimax_EW-7833UAC
> <https://wikidevi.com/wiki/Edimax_EW-7833UAC>
> >>>>>
> http://www.edimax.com/edimax/download/download/data/edimax/g
> lobal/download/for_home/wireless_adapters/wireless_adapters_
> ac1750_dual-band/ew-7833uac
> <http://www.edimax.com/edimax/download/download/data/edimax/
> global/download/for_home/wireless_adapters/wireless_adapters
> _ac1750_dual-band/ew-7833uac>
> >>>>>
> http://www.edimax.com/edimax/mw/cufiles/files/download/Drive
> r_Utility/EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip
> <http://www.edimax.com/edimax/mw/cufiles/files/download/Driv
> er_Utility/EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip>
> >>>>>
> >>>>> https://github.com/pld-linux/rtl8812au
> <https://github.com/pld-linux/rtl8812au>
> >>>>> https://github.com/diederikdehaas/rtl8812AU
>
> <https://github.com/diederikdehaas/rtl8812AU>
> >>>>>
> >>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >>>>>
> >>>>> $ unzip EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip
> >>>>> $ cd
> EW7833UAC_linux_4.3.21_kernel_3.16-4.4/EW7833UAC_linux_v4.3.
> 21_17997.20160531/
> >>>>>
> >>>>> $ curl -s
> https://raw.githubusercontent.com/pld-linux/rtl8812au/master
> /disable-debug.patch
> <https://raw.githubusercontent.com/pld-linux/rtl8812au/
> master/disable-debug.patch>
> | patch -p1
> >>>>> $ curl -s
> https://github.com/diederikdehaas/rtl8812AU/commit/e6d6beb.patch
> <https://github.com/diederikdehaas/rtl8812AU/commit/e6d6beb.patch>
> | patch -p1
> >>>>> $ curl -s
> https://raw.githubusercontent.com/pld-linux/rtl8812au/master
> /linux-4.7.patch
> <https://raw.githubusercontent.com/pld-linux/rtl8812au/
> master/linux-4.7.patch>
> | patch -p1
> >>>>> $ curl -s
> https://raw.githubusercontent.com/pld-linux/rtl8812au/master
> /linux-4.8.patch
> <https://raw.githubusercontent.com/pld-linux/rtl8812au/
> master/linux-4.8.patch>
> | patch -p1
> >>>>>
> >>>>> $ make -j3
> >>>>> $ su
> >>>>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
> >>>>> # depmod
> >>>>> # modinfo 8814au | grep 2001
> >>>>>
> >>>>> # modprobe -v 8814au
> >>>>> # dmesg:
> >>>>> ...
> >>>>> RTL871X: module init start
> >>>>> RTL871X: rtl8814au v4.3.21_17997.20160531
> >>>>> RTL871X: build time: Jan 21 2017 20:04:38
> >>>>> usbcore: registered new interface driver rtl8814au
> >>>>> RTL871X: module init ret=0
> >>>>> ...
> >>>>> # modprobe -rv 8814au
> >>>>> # dmesg:
> >>>>> ...
> >>>>> RTL871X: module exit start
> >>>>> usbcore: deregistering interface driver rtl8814au
> >>>>> RTL871X: module exit success
> >>>>> ...
> >>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >>>>>
> >>>>> Wifi ball works now?
> >>>>>
> >>>>>
> >>>>> HW add.
> >>>>> https://wikidevi.com/wiki/ASUS_USB-AC68
> <https://wikidevi.com/wiki/ASUS_USB-AC68>
> >>>>> https://www.asus.com/Networking/USB-AC68/HelpDesk_Download
> <https://www.asus.com/Networking/USB-AC68/HelpDesk_Download>
> >>>>>
> >>>>> https://wikidevi.com/wiki/TP-LINK_Archer_T9UH
> <https://wikidevi.com/wiki/TP-LINK_Archer_T9UH>
> >>>>> http://www.tp-link.com/en/download/Archer-T9UH.html
> <http://www.tp-link.com/en/download/Archer-T9UH.html>
> >>>>>
> >>>>> https://wikidevi.com/wiki/TRENDnet_TEW-809UB
> <https://wikidevi.com/wiki/TRENDnet_TEW-809UB>
> >>>>>
> https://www.trendnet.com/support/supportdetail.asp?prod=100_TEW-809UB
> <https://www.trendnet.com/support/supportdetail.asp?prod=
> 100_TEW-809UB>
> >>>>>
> >>>>> SW add.
> >>>>> https://github.com/abperiasamy/rtl8812AU_8821AU_linux
> <https://github.com/abperiasamy/rtl8812AU_8821AU_linux>
> >>>>> https://github.com/austinmarton/rtl8812au_linux
>
> <https://github.com/austinmarton/rtl8812au_linux>
> >>>>>
> >>>>>
> >>>>>
> >>>> OR
> >>>> according to "rtl8814au? #10"
> >>>> https://github.com/diederikdehaas/rtl8812AU/issues/10
> <https://github.com/diederikdehaas/rtl8812AU/issues/10>
> >>>>
> >>>> $ git clone -b driver-4.3.21
> https://github.com/uminokoe/rtl8812AU.git
> <https://github.com/uminokoe/rtl8812AU.git> RTL8814AU-uminokoe
> >>>> $ cd RTL8814AU-uminokoe/
> >>>> $ git revert -n 9260f77 8d33100
> >>>> // "Disabled debugging code."
> >>>> $ curl -s
> https://github.com/diederikdehaas/rtl8812AU/commit/3e80ebc.patch
> <https://github.com/diederikdehaas/rtl8812AU/commit/3e80ebc.patch>
> | patch -p1
> >>>> // Enables CONFIG_MP_VHT_HW_TX_MODE
> >>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
> >>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
> >>>>
> >>>> OR
> >>>> $ git clone https://github.com/diederikdehaas/rtl8814AU.git
> <https://github.com/diederikdehaas/rtl8814AU.git>
> RTL8814AU-diederikdehaas
> >>>> $ cd RTL8814AU-diederikdehaas/
> >>>> // Adds missing Vendor/Product ID
> >>>> $ sed -i '/0xA834/ a\\t{USB_DEVICE(0x7392, 0xA833),
> .driver_info = RTL8814A}, /* Edimax - Edimax */'
> os_dep/linux/usb_intf.c
> >>>> // "Added VHT capabilities."
> >>>> $ curl -s
> https://github.com/uminokoe/rtl8812AU/commit/5f75242.patch
> <https://github.com/uminokoe/rtl8812AU/commit/5f75242.patch> |
> patch -p1
> >>>> // Enables CONFIG_MP_VHT_HW_TX_MODE
> >>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
> >>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
> >>>>
> >>>>
> >>>> $ make -j3
> >>>> $ su
> >>>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
> >>>> # depmod
> >>>> # modinfo 8814au
> >>>>
> >>>> # modprobe -v 8814au
> >>>> # dmesg:
> >>>> ...
> >>>> RTL871X: module init start
> >>>> RTL871X: rtl8814au v4.3.21_17997.20160531
> >>>> usbcore: registered new interface driver rtl8814au
> >>>> RTL871X: module init ret=0
> >>>> ...
> >>>> # modprobe -rv 8814au
> >>>> # dmesg:
> >>>> ...
> >>>> RTL871X: module exit start
> >>>> usbcore: deregistering interface driver rtl8814au
> >>>> RTL871X: module exit success
> >>>> ...
> >>>>
> >>>>
> >>>> Hello Diederik,
> >>>> it seems there are only two Linux RTL8814AU users, so far.
> >>>>
> >>>> Morris, when you catch some time, would you mind to run a
> couple iperf tests with DWA-192,
> >>>> to see real network throughput results.
> >>> I can't run any at the moment because Fedora is refusing to
> actually use
> >>> the device at all.
> >>>
> >>> I have also just upgraded to F25 and nothing has changed.
> >>>
> >>> The last time I used this device was on 08/10/2016 and it was
> using the
> >>> ATH9K driver. The main reason I upgraded to this USB device
> was that I
> >>> upgraded my router to a faster version, and I found that
> unlike the
> >>> DWA182 I didn't have to compile my own driver, the kernel had
> inbuilt
> >>> support for the DWA192.
> >>>
> >>> It is possible that I have managed to Blacklist the device in
> some way,
> >>> not by the conventional Blacklist.conf, and I have forgotten
> how so I
> >>> can't find where I've done it to reverse it.
> >>>
> >>> Also, having never done it before, I also don't know how to
> run iperf tests.
> >>>
> >>> regards,
> >>> Steve
> >>>
> >> Did I understand you correctly, what you're saying here is that:
> >> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
> >> therefore the USB based device, was driven by:
> >> $ modinfo --description ath9k
> >> Support for Atheros 802.11n wireless LAN cards.
> >> https://wireless.wiki.kernel.org/en/users/drivers/ath9k
> <https://wireless.wiki.kernel.org/en/users/drivers/ath9k>
> >> "ath9k is a completely FOSS wireless driver for all Atheros
> IEEE 802.11n PCI/PCI-Express and AHB WLAN based chipsets."
> >> https://wiki.debian.org/ath9k
> >> "Atheros 802.11n PCI/PCI-E devices (ath9k)"
> > Yes, when the device was working iwconfig reported the driver as
> being
> > ATH9K, but if refused to use the 5GHz channel. Following a
> suggestion on
> > this list I tried compiling my own kernel and setting a recommended
> > flag, but that had no effect on its ability to use the 5GHz
> channel. It
> > was from compiling my own kernel I found that it looked like the
> ATH10K
> > driver would support the 5GHz channel, which Winfried de Heiden is
> > confirming, so at the time I couldn't work out why the system
wasn't
> > assigning the ATH10K driver instead of the ATH9K driver.
> > From what you are saying it sounds like that various updates to F24
> > (and in F25 which I am using now) have changed the functionality of
> > ATH9K to not support USB devices, which would potentially go a
> long way
> > towards explaining why my adapter is no longer recognized any more.
> > Also it seems to me that you are suggesting that I need to go
> back to
> > compiling a driver for this card again (if I have to do this
> will the
> > driver support the 5GHz channel), if this is so given that from
> when I
> > first started using this adapter up until 08/10/2016 there was
> native
> > support in the kernel for the device, why has this support been
> dropped?
> > I first started using this adapter in F23.
> >
> > regards,
> > Steve
>
>
> This should show the WiFi devices that are connected to the machine:
> $ echo ; lspci -knn -d ::0280 ; echo ; lsusb ; echo ; lsusb -t ; echo
>
> Would you mind copy and paste the output here.
>
>
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> <mailto:users@lists.fedoraproject.org>
> To unsubscribe send an email to
> users-leave(a)lists.fedoraproject.org
> <mailto:users-leave@lists.fedoraproject.org>
>
>
>
>
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
3:38 p.m.
New subject: [...] D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
On 27/01/2017 07:24, Terry Polzin wrote:
bus 010 device 002 is a pci device not a usb device the way I read
this output.
The output that shows bus 010 device 002 as being a Dlink device
(which
is what my usb device is, and is the only Dlink device I have) is from
lsusb, which I thought only showed usb interfaces and not pci, is that
not correct?
regards,
Steve
On Thu, Jan 26, 2017 at 4:17 PM, Stephen Morris
<samorris(a)netspace.net.au <mailto:samorris@netspace.net.au>> wrote:
On 25/01/2017 00:17, Terry Polzin wrote:
Stephen,
I think that Poma finds it extraordinary that your device was
working with a driver for a completely different chipset. I
know I do.
I can understand that. The iwconfig output could have been showing
the wrong driver, but at the time I also raised a bug on bugzilla
around the fact that the driver would not active the 5GHz channel
on the adapter, which at the moment has gone nowhere.
regards,
Steve
On Tue, Jan 24, 2017 at 12:12 AM, poma
<pomidorabelisima(a)gmail.com
<mailto:pomidorabelisima@gmail.com>
<mailto:pomidorabelisima@gmail.com
<mailto:pomidorabelisima@gmail.com>>> wrote:
On 23.01.2017 21:14, Stephen Morris wrote:
> On 23/01/2017 08:27, poma wrote:
>> On 22.01.2017 21:49, Stephen Morris wrote:
>>> On 23/01/2017 00:43, poma wrote:
>>>> On 21.01.2017 21:00, poma wrote:
>>>>> On 17.01.2017 22:12, Stephen Morris wrote:
>>>>> [...]
>>>>>> The lsusb output for that device is also below.
>>>>>>
>>>>>> Bus 010 Device 002: ID 2001:331a D-Link Corp.
>>>>>>
>>>>> [...]
>>>>>
>>>>> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
>>>>>
>>>>> https://wikidevi.com/wiki/D-Link_DWA-192
<https://wikidevi.com/wiki/D-Link_DWA-192>
<https://wikidevi.com/wiki/D-Link_DWA-192
<https://wikidevi.com/wiki/D-Link_DWA-192>>
>>>>> http://support.dlink.com/ProductInfo.aspx?m=DWA-192
<http://support.dlink.com/ProductInfo.aspx?m=DWA-192>
<http://support.dlink.com/ProductInfo.aspx?m=DWA-192
<http://support.dlink.com/ProductInfo.aspx?m=DWA-192>>
>>>>> ftp://files.dlink.com.au/products/DWA-192
<ftp://files.dlink.com.au/products/DWA-192>
<ftp://files.dlink.com.au/products/DWA-192
<ftp://files.dlink.com.au/products/DWA-192>>
>>>>>
https://openitforum.pl/index/recenzje/karty/d-link-dwa-192-r225
<https://openitforum.pl/index/recenzje/karty/d-link-dwa-192-r225>
<https://openitforum.pl/index/recenzje/karty/d-link-dwa-192-r225
<https://openitforum.pl/index/recenzje/karty/d-link-dwa-192-r225>>
>>>>>
>>>>> https://wikidevi.com/wiki/Edimax_EW-7833UAC
<https://wikidevi.com/wiki/Edimax_EW-7833UAC>
<https://wikidevi.com/wiki/Edimax_EW-7833UAC
<https://wikidevi.com/wiki/Edimax_EW-7833UAC>>
>>>>>
http://www.edimax.com/edimax/download/download/data/edimax/global/downloa...
<http://www.edimax.com/edimax/download/download/data/edimax/global/downloa...
<http://www.edimax.com/edimax/download/download/data/edimax/global/downloa...
<http://www.edimax.com/edimax/download/download/data/edimax/global/downloa...
>>>>>
http://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-...
<http://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-...
<http://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-...
<http://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-...
>>>>>
>>>>> https://github.com/pld-linux/rtl8812au
<https://github.com/pld-linux/rtl8812au>
<https://github.com/pld-linux/rtl8812au
<https://github.com/pld-linux/rtl8812au>>
>>>>> https://github.com/diederikdehaas/rtl8812AU
<https://github.com/diederikdehaas/rtl8812AU>
<https://github.com/diederikdehaas/rtl8812AU
<https://github.com/diederikdehaas/rtl8812AU>>
>>>>>
>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>
>>>>> $ unzip EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip
>>>>> $ cd
EW7833UAC_linux_4.3.21_kernel_3.16-4.4/EW7833UAC_linux_v4.3.21_17997.20160531/
>>>>>
>>>>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/disable-debu...
<https://raw.githubusercontent.com/pld-linux/rtl8812au/master/disable-debu...
<https://raw.githubusercontent.com/pld-linux/rtl8812au/master/disable-debu...
<https://raw.githubusercontent.com/pld-linux/rtl8812au/master/disable-debu...
| patch -p1
>>>>> $ curl -s
https://github.com/diederikdehaas/rtl8812AU/commit/e6d6beb.patch
<https://github.com/diederikdehaas/rtl8812AU/commit/e6d6beb.patch>
<https://github.com/diederikdehaas/rtl8812AU/commit/e6d6beb.patch
<https://github.com/diederikdehaas/rtl8812AU/commit/e6d6beb.patch>>
| patch -p1
>>>>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.7.patch
<https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.7.pa...
<https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.7.patch
<https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.7.pa...
| patch -p1
>>>>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.8.patch
<https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.8.pa...
<https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.8.patch
<https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.8.pa...
| patch -p1
>>>>>
>>>>> $ make -j3
>>>>> $ su
>>>>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
>>>>> # depmod
>>>>> # modinfo 8814au | grep 2001
>>>>>
>>>>> # modprobe -v 8814au
>>>>> # dmesg:
>>>>> ...
>>>>> RTL871X: module init start
>>>>> RTL871X: rtl8814au v4.3.21_17997.20160531
>>>>> RTL871X: build time: Jan 21 2017 20:04:38
>>>>> usbcore: registered new interface driver rtl8814au
>>>>> RTL871X: module init ret=0
>>>>> ...
>>>>> # modprobe -rv 8814au
>>>>> # dmesg:
>>>>> ...
>>>>> RTL871X: module exit start
>>>>> usbcore: deregistering interface driver rtl8814au
>>>>> RTL871X: module exit success
>>>>> ...
>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>
>>>>> Wifi ball works now?
>>>>>
>>>>>
>>>>> HW add.
>>>>> https://wikidevi.com/wiki/ASUS_USB-AC68
<https://wikidevi.com/wiki/ASUS_USB-AC68>
<https://wikidevi.com/wiki/ASUS_USB-AC68
<https://wikidevi.com/wiki/ASUS_USB-AC68>>
>>>>>
https://www.asus.com/Networking/USB-AC68/HelpDesk_Download
<https://www.asus.com/Networking/USB-AC68/HelpDesk_Download>
<https://www.asus.com/Networking/USB-AC68/HelpDesk_Download
<https://www.asus.com/Networking/USB-AC68/HelpDesk_Download>>
>>>>>
>>>>> https://wikidevi.com/wiki/TP-LINK_Archer_T9UH
<https://wikidevi.com/wiki/TP-LINK_Archer_T9UH>
<https://wikidevi.com/wiki/TP-LINK_Archer_T9UH
<https://wikidevi.com/wiki/TP-LINK_Archer_T9UH>>
>>>>> http://www.tp-link.com/en/download/Archer-T9UH.html
<http://www.tp-link.com/en/download/Archer-T9UH.html>
<http://www.tp-link.com/en/download/Archer-T9UH.html
<http://www.tp-link.com/en/download/Archer-T9UH.html>>
>>>>>
>>>>> https://wikidevi.com/wiki/TRENDnet_TEW-809UB
<https://wikidevi.com/wiki/TRENDnet_TEW-809UB>
<https://wikidevi.com/wiki/TRENDnet_TEW-809UB
<https://wikidevi.com/wiki/TRENDnet_TEW-809UB>>
>>>>>
https://www.trendnet.com/support/supportdetail.asp?prod=100_TEW-809UB
<https://www.trendnet.com/support/supportdetail.asp?prod=100_TEW-809UB>
<https://www.trendnet.com/support/supportdetail.asp?prod=100_TEW-809UB
<https://www.trendnet.com/support/supportdetail.asp?prod=100_TEW-809UB>...
>>>>>
>>>>> SW add.
>>>>>
https://github.com/abperiasamy/rtl8812AU_8821AU_linux
<https://github.com/abperiasamy/rtl8812AU_8821AU_linux>
<https://github.com/abperiasamy/rtl8812AU_8821AU_linux
<https://github.com/abperiasamy/rtl8812AU_8821AU_linux>>
>>>>> https://github.com/austinmarton/rtl8812au_linux
<https://github.com/austinmarton/rtl8812au_linux>
<https://github.com/austinmarton/rtl8812au_linux
<https://github.com/austinmarton/rtl8812au_linux>>
>>>>>
>>>>>
>>>>>
>>>> OR
>>>> according to "rtl8814au? #10"
>>>> https://github.com/diederikdehaas/rtl8812AU/issues/10
<https://github.com/diederikdehaas/rtl8812AU/issues/10>
<https://github.com/diederikdehaas/rtl8812AU/issues/10
<https://github.com/diederikdehaas/rtl8812AU/issues/10>>
>>>>
>>>> $ git clone -b driver-4.3.21
https://github.com/uminokoe/rtl8812AU.git
<https://github.com/uminokoe/rtl8812AU.git>
<https://github.com/uminokoe/rtl8812AU.git
<https://github.com/uminokoe/rtl8812AU.git>> RTL8814AU-uminokoe
>>>> $ cd RTL8814AU-uminokoe/
>>>> $ git revert -n 9260f77 8d33100
>>>> // "Disabled debugging code."
>>>> $ curl -s
https://github.com/diederikdehaas/rtl8812AU/commit/3e80ebc.patch
<https://github.com/diederikdehaas/rtl8812AU/commit/3e80ebc.patch>
<https://github.com/diederikdehaas/rtl8812AU/commit/3e80ebc.patch
<https://github.com/diederikdehaas/rtl8812AU/commit/3e80ebc.patch>>
| patch -p1
>>>> // Enables CONFIG_MP_VHT_HW_TX_MODE
>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/'
Makefile
>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
>>>>
>>>> OR
>>>> $ git clone
https://github.com/diederikdehaas/rtl8814AU.git
<https://github.com/diederikdehaas/rtl8814AU.git>
<https://github.com/diederikdehaas/rtl8814AU.git
<https://github.com/diederikdehaas/rtl8814AU.git>>
RTL8814AU-diederikdehaas
>>>> $ cd RTL8814AU-diederikdehaas/
>>>> // Adds missing Vendor/Product ID
>>>> $ sed -i '/0xA834/ a\\t{USB_DEVICE(0x7392, 0xA833),
.driver_info = RTL8814A}, /* Edimax - Edimax */'
os_dep/linux/usb_intf.c
>>>> // "Added VHT capabilities."
>>>> $ curl -s
https://github.com/uminokoe/rtl8812AU/commit/5f75242.patch
<https://github.com/uminokoe/rtl8812AU/commit/5f75242.patch>
<https://github.com/uminokoe/rtl8812AU/commit/5f75242.patch
<https://github.com/uminokoe/rtl8812AU/commit/5f75242.patch>> |
patch -p1
>>>> // Enables CONFIG_MP_VHT_HW_TX_MODE
>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/'
Makefile
>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
>>>>
>>>>
>>>> $ make -j3
>>>> $ su
>>>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
>>>> # depmod
>>>> # modinfo 8814au
>>>>
>>>> # modprobe -v 8814au
>>>> # dmesg:
>>>> ...
>>>> RTL871X: module init start
>>>> RTL871X: rtl8814au v4.3.21_17997.20160531
>>>> usbcore: registered new interface driver rtl8814au
>>>> RTL871X: module init ret=0
>>>> ...
>>>> # modprobe -rv 8814au
>>>> # dmesg:
>>>> ...
>>>> RTL871X: module exit start
>>>> usbcore: deregistering interface driver rtl8814au
>>>> RTL871X: module exit success
>>>> ...
>>>>
>>>>
>>>> Hello Diederik,
>>>> it seems there are only two Linux RTL8814AU users, so
far.
>>>>
>>>> Morris, when you catch some time, would you mind to run a
couple iperf tests with DWA-192,
>>>> to see real network throughput results.
>>> I can't run any at the moment because Fedora is
refusing to
actually use
>>> the device at all.
>>>
>>> I have also just upgraded to F25 and nothing has changed.
>>>
>>> The last time I used this device was on 08/10/2016 and
it was
using the
>>> ATH9K driver. The main reason I upgraded to this USB
device
was that I
>>> upgraded my router to a faster version, and I found that
unlike the
>>> DWA182 I didn't have to compile my own driver, the
kernel had
inbuilt
>>> support for the DWA192.
>>>
>>> It is possible that I have managed to Blacklist the
device in
some way,
>>> not by the conventional Blacklist.conf, and I have
forgotten
how so I
>>> can't find where I've done it to reverse it.
>>>
>>> Also, having never done it before, I also don't know
how to
run iperf tests.
>>>
>>> regards,
>>> Steve
>>>
>> Did I understand you correctly, what you're saying here
is that:
>> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
>> therefore the USB based device, was driven by:
>> $ modinfo --description ath9k
>> Support for Atheros 802.11n wireless LAN cards.
>> https://wireless.wiki.kernel.org/en/users/drivers/ath9k
<https://wireless.wiki.kernel.org/en/users/drivers/ath9k>
<https://wireless.wiki.kernel.org/en/users/drivers/ath9k
<https://wireless.wiki.kernel.org/en/users/drivers/ath9k>>
>> "ath9k is a completely FOSS wireless driver for all Atheros
IEEE 802.11n PCI/PCI-Express and AHB WLAN based chipsets."
>> https://wiki.debian.org/ath9k
>> "Atheros 802.11n PCI/PCI-E devices (ath9k)"
> Yes, when the device was working iwconfig reported the
driver as
being
> ATH9K, but if refused to use the 5GHz channel. Following a
suggestion on
> this list I tried compiling my own kernel and setting a
recommended
> flag, but that had no effect on its ability to use the 5GHz
channel. It
> was from compiling my own kernel I found that it looked
like the
ATH10K
> driver would support the 5GHz channel, which Winfried de
Heiden is
> confirming, so at the time I couldn't work out why the
system wasn't
> assigning the ATH10K driver instead of the ATH9K driver.
> From what you are saying it sounds like that various
updates to F24
> (and in F25 which I am using now) have changed the
functionality of
> ATH9K to not support USB devices, which would
potentially go a
long way
> towards explaining why my adapter is no longer
recognized any more.
> Also it seems to me that you are suggesting that I need
to go
back to
> compiling a driver for this card again (if I have to do this
will the
> driver support the 5GHz channel), if this is so given
that from
when I
> first started using this adapter up until 08/10/2016
there was
native
> support in the kernel for the device, why has this
support been
dropped?
> I first started using this adapter in F23.
>
> regards,
> Steve
This should show the WiFi devices that are connected to
the machine:
$ echo ; lspci -knn -d ::0280 ; echo ; lsusb ; echo ;
lsusb -t ; echo
Would you mind copy and paste the output here.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
<mailto:users@lists.fedoraproject.org>
<mailto:users@lists.fedoraproject.org
<mailto:users@lists.fedoraproject.org>>
To unsubscribe send an email to
users-leave(a)lists.fedoraproject.org
<mailto:users-leave@lists.fedoraproject.org>
<mailto:users-leave@lists.fedoraproject.org
<mailto:users-leave@lists.fedoraproject.org>>
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
<mailto:users@lists.fedoraproject.org>
To unsubscribe send an email to
users-leave(a)lists.fedoraproject.org
<mailto:users-leave@lists.fedoraproject.org>
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
<mailto:users@lists.fedoraproject.org>
To unsubscribe send an email to
users-leave(a)lists.fedoraproject.org
<mailto:users-leave@lists.fedoraproject.org>
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
3:12 p.m.
New subject: [...] D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
On 24/01/2017 15:12, poma wrote:
On 23.01.2017 21:14, Stephen Morris wrote:
> On 23/01/2017 08:27, poma wrote:
>> On 22.01.2017 21:49, Stephen Morris wrote:
>>> On 23/01/2017 00:43, poma wrote:
>>>> On 21.01.2017 21:00, poma wrote:
>>>>> On 17.01.2017 22:12, Stephen Morris wrote:
>>>>> [...]
>>>>>> The lsusb output for that device is also below.
>>>>>>
>>>>>> Bus 010 Device 002: ID 2001:331a D-Link Corp.
>>>>>>
>>>>> [...]
>>>>>
>>>>> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
>>>>>
>>>>> https://wikidevi.com/wiki/D-Link_DWA-192
>>>>> http://support.dlink.com/ProductInfo.aspx?m=DWA-192
>>>>> ftp://files.dlink.com.au/products/DWA-192
>>>>> https://openitforum.pl/index/recenzje/karty/d-link-dwa-192-r225
>>>>>
>>>>> https://wikidevi.com/wiki/Edimax_EW-7833UAC
>>>>>
http://www.edimax.com/edimax/download/download/data/edimax/global/downloa...
>>>>>
http://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-...
>>>>>
>>>>> https://github.com/pld-linux/rtl8812au
>>>>> https://github.com/diederikdehaas/rtl8812AU
>>>>>
>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>
>>>>> $ unzip EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip
>>>>> $ cd
EW7833UAC_linux_4.3.21_kernel_3.16-4.4/EW7833UAC_linux_v4.3.21_17997.20160531/
>>>>>
>>>>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/disable-debu... | patch
-p1
>>>>> $ curl -s
https://github.com/diederikdehaas/rtl8812AU/commit/e6d6beb.patch | patch -p1
>>>>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.7.patch | patch -p1
>>>>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.8.patch | patch -p1
>>>>>
>>>>> $ make -j3
>>>>> $ su
>>>>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
>>>>> # depmod
>>>>> # modinfo 8814au | grep 2001
>>>>>
>>>>> # modprobe -v 8814au
>>>>> # dmesg:
>>>>> ...
>>>>> RTL871X: module init start
>>>>> RTL871X: rtl8814au v4.3.21_17997.20160531
>>>>> RTL871X: build time: Jan 21 2017 20:04:38
>>>>> usbcore: registered new interface driver rtl8814au
>>>>> RTL871X: module init ret=0
>>>>> ...
>>>>> # modprobe -rv 8814au
>>>>> # dmesg:
>>>>> ...
>>>>> RTL871X: module exit start
>>>>> usbcore: deregistering interface driver rtl8814au
>>>>> RTL871X: module exit success
>>>>> ...
>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>
>>>>> Wifi ball works now?
>>>>>
>>>>>
>>>>> HW add.
>>>>> https://wikidevi.com/wiki/ASUS_USB-AC68
>>>>> https://www.asus.com/Networking/USB-AC68/HelpDesk_Download
>>>>>
>>>>> https://wikidevi.com/wiki/TP-LINK_Archer_T9UH
>>>>> http://www.tp-link.com/en/download/Archer-T9UH.html
>>>>>
>>>>> https://wikidevi.com/wiki/TRENDnet_TEW-809UB
>>>>>
https://www.trendnet.com/support/supportdetail.asp?prod=100_TEW-809UB
>>>>>
>>>>> SW add.
>>>>> https://github.com/abperiasamy/rtl8812AU_8821AU_linux
>>>>> https://github.com/austinmarton/rtl8812au_linux
>>>>>
>>>>>
>>>>>
>>>> OR
>>>> according to "rtl8814au? #10"
>>>> https://github.com/diederikdehaas/rtl8812AU/issues/10
>>>>
>>>> $ git clone -b driver-4.3.21 https://github.com/uminokoe/rtl8812AU.git
RTL8814AU-uminokoe
>>>> $ cd RTL8814AU-uminokoe/
>>>> $ git revert -n 9260f77 8d33100
>>>> // "Disabled debugging code."
>>>> $ curl -s
https://github.com/diederikdehaas/rtl8812AU/commit/3e80ebc.patch | patch -p1
>>>> // Enables CONFIG_MP_VHT_HW_TX_MODE
>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
>>>>
>>>> OR
>>>> $ git clone https://github.com/diederikdehaas/rtl8814AU.git
RTL8814AU-diederikdehaas
>>>> $ cd RTL8814AU-diederikdehaas/
>>>> // Adds missing Vendor/Product ID
>>>> $ sed -i '/0xA834/ a\\t{USB_DEVICE(0x7392, 0xA833), .driver_info =
RTL8814A}, /* Edimax - Edimax */' os_dep/linux/usb_intf.c
>>>> // "Added VHT capabilities."
>>>> $ curl -s https://github.com/uminokoe/rtl8812AU/commit/5f75242.patch |
patch -p1
>>>> // Enables CONFIG_MP_VHT_HW_TX_MODE
>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
>>>>
>>>>
>>>> $ make -j3
>>>> $ su
>>>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
>>>> # depmod
>>>> # modinfo 8814au
>>>>
>>>> # modprobe -v 8814au
>>>> # dmesg:
>>>> ...
>>>> RTL871X: module init start
>>>> RTL871X: rtl8814au v4.3.21_17997.20160531
>>>> usbcore: registered new interface driver rtl8814au
>>>> RTL871X: module init ret=0
>>>> ...
>>>> # modprobe -rv 8814au
>>>> # dmesg:
>>>> ...
>>>> RTL871X: module exit start
>>>> usbcore: deregistering interface driver rtl8814au
>>>> RTL871X: module exit success
>>>> ...
>>>>
>>>>
>>>> Hello Diederik,
>>>> it seems there are only two Linux RTL8814AU users, so far.
>>>>
>>>> Morris, when you catch some time, would you mind to run a couple iperf
tests with DWA-192,
>>>> to see real network throughput results.
>>> I can't run any at the moment because Fedora is refusing to actually use
>>> the device at all.
>>>
>>> I have also just upgraded to F25 and nothing has changed.
>>>
>>> The last time I used this device was on 08/10/2016 and it was using the
>>> ATH9K driver. The main reason I upgraded to this USB device was that I
>>> upgraded my router to a faster version, and I found that unlike the
>>> DWA182 I didn't have to compile my own driver, the kernel had inbuilt
>>> support for the DWA192.
>>>
>>> It is possible that I have managed to Blacklist the device in some way,
>>> not by the conventional Blacklist.conf, and I have forgotten how so I
>>> can't find where I've done it to reverse it.
>>>
>>> Also, having never done it before, I also don't know how to run iperf
tests.
>>>
>>> regards,
>>> Steve
>>>
>> Did I understand you correctly, what you're saying here is that:
>> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
>> therefore the USB based device, was driven by:
>> $ modinfo --description ath9k
>> Support for Atheros 802.11n wireless LAN cards.
>> https://wireless.wiki.kernel.org/en/users/drivers/ath9k
>> "ath9k is a completely FOSS wireless driver for all Atheros IEEE 802.11n
PCI/PCI-Express and AHB WLAN based chipsets."
>> https://wiki.debian.org/ath9k
>> "Atheros 802.11n PCI/PCI-E devices (ath9k)"
> Yes, when the device was working iwconfig reported the driver as being
> ATH9K, but if refused to use the 5GHz channel. Following a suggestion on
> this list I tried compiling my own kernel and setting a recommended
> flag, but that had no effect on its ability to use the 5GHz channel. It
> was from compiling my own kernel I found that it looked like the ATH10K
> driver would support the 5GHz channel, which Winfried de Heiden is
> confirming, so at the time I couldn't work out why the system wasn't
> assigning the ATH10K driver instead of the ATH9K driver.
> From what you are saying it sounds like that various updates to F24
> (and in F25 which I am using now) have changed the functionality of
> ATH9K to not support USB devices, which would potentially go a long way
> towards explaining why my adapter is no longer recognized any more.
> Also it seems to me that you are suggesting that I need to go back to
> compiling a driver for this card again (if I have to do this will the
> driver support the 5GHz channel), if this is so given that from when I
> first started using this adapter up until 08/10/2016 there was native
> support in the kernel for the device, why has this support been dropped?
> I first started using this adapter in F23.
>
> regards,
> Steve
This should show the WiFi devices that are connected to the machine:
$ echo ; lspci -knn -d ::0280 ; echo ; lsusb ; echo ; lsusb -t ; echo
Would you mind copy and paste the output here.
I have input the commands and the
output is listed below.
echo ; lspci -knn -d ::0280 ; echo ; lsusb ; echo ; lsusb -t ; echo
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 045e:0750 Microsoft Corp. Wired Keyboard 600
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 011 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 010 Device 002: ID 2001:331a D-Link Corp.
Bus 010 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
/: Bus 11.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
/: Bus 10.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 480M
/: Bus 09.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
/: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/4p, 12M
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/2p, 12M
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/5p, 12M
|__ Port 2: Dev 2, If 0, Class=Human Interface Device,
Driver=usbhid, 12M
|__ Port 2: Dev 2, If 1, Class=Human Interface Device,
Driver=usbhid, 12M
|__ Port 2: Dev 2, If 2, Class=Human Interface Device,
Driver=usbhid, 12M
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/5p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device,
Driver=usbhid, 1.5M
|__ Port 1: Dev 2, If 1, Class=Human Interface Device,
Driver=usbhid, 1.5M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/4p, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/5p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/5p, 480M
Bus 010 Device 002 is the usb wifi adapter that is not recognized anymore.
regards,
Steve
5:20 a.m.
New subject: [...] D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
On 26.01.2017 22:12, Stephen Morris wrote:
On 24/01/2017 15:12, poma wrote:
> On 23.01.2017 21:14, Stephen Morris wrote:
>> On 23/01/2017 08:27, poma wrote:
>>> On 22.01.2017 21:49, Stephen Morris wrote:
>>>> On 23/01/2017 00:43, poma wrote:
>>>>> On 21.01.2017 21:00, poma wrote:
>>>>>> On 17.01.2017 22:12, Stephen Morris wrote:
>>>>>> [...]
>>>>>>> The lsusb output for that device is also below.
>>>>>>>
>>>>>>> Bus 010 Device 002: ID 2001:331a D-Link Corp.
>>>>>>>
>>>>>> [...]
>>>>>>
>>>>>> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
>>>>>>
>>>>>> https://wikidevi.com/wiki/D-Link_DWA-192
>>>>>> http://support.dlink.com/ProductInfo.aspx?m=DWA-192
>>>>>> ftp://files.dlink.com.au/products/DWA-192
>>>>>> https://openitforum.pl/index/recenzje/karty/d-link-dwa-192-r225
>>>>>>
>>>>>> https://wikidevi.com/wiki/Edimax_EW-7833UAC
>>>>>>
http://www.edimax.com/edimax/download/download/data/edimax/global/downloa...
>>>>>>
http://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-...
>>>>>>
>>>>>> https://github.com/pld-linux/rtl8812au
>>>>>> https://github.com/diederikdehaas/rtl8812AU
>>>>>>
>>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>
>>>>>> $ unzip EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip
>>>>>> $ cd
EW7833UAC_linux_4.3.21_kernel_3.16-4.4/EW7833UAC_linux_v4.3.21_17997.20160531/
>>>>>>
>>>>>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/disable-debu... | patch
-p1
>>>>>> $ curl -s
https://github.com/diederikdehaas/rtl8812AU/commit/e6d6beb.patch | patch -p1
>>>>>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.7.patch | patch -p1
>>>>>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.8.patch | patch -p1
>>>>>>
>>>>>> $ make -j3
>>>>>> $ su
>>>>>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
>>>>>> # depmod
>>>>>> # modinfo 8814au | grep 2001
>>>>>>
>>>>>> # modprobe -v 8814au
>>>>>> # dmesg:
>>>>>> ...
>>>>>> RTL871X: module init start
>>>>>> RTL871X: rtl8814au v4.3.21_17997.20160531
>>>>>> RTL871X: build time: Jan 21 2017 20:04:38
>>>>>> usbcore: registered new interface driver rtl8814au
>>>>>> RTL871X: module init ret=0
>>>>>> ...
>>>>>> # modprobe -rv 8814au
>>>>>> # dmesg:
>>>>>> ...
>>>>>> RTL871X: module exit start
>>>>>> usbcore: deregistering interface driver rtl8814au
>>>>>> RTL871X: module exit success
>>>>>> ...
>>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>
>>>>>> Wifi ball works now?
>>>>>>
>>>>>>
>>>>>> HW add.
>>>>>> https://wikidevi.com/wiki/ASUS_USB-AC68
>>>>>> https://www.asus.com/Networking/USB-AC68/HelpDesk_Download
>>>>>>
>>>>>> https://wikidevi.com/wiki/TP-LINK_Archer_T9UH
>>>>>> http://www.tp-link.com/en/download/Archer-T9UH.html
>>>>>>
>>>>>> https://wikidevi.com/wiki/TRENDnet_TEW-809UB
>>>>>>
https://www.trendnet.com/support/supportdetail.asp?prod=100_TEW-809UB
>>>>>>
>>>>>> SW add.
>>>>>> https://github.com/abperiasamy/rtl8812AU_8821AU_linux
>>>>>> https://github.com/austinmarton/rtl8812au_linux
>>>>>>
>>>>>>
>>>>>>
>>>>> OR
>>>>> according to "rtl8814au? #10"
>>>>> https://github.com/diederikdehaas/rtl8812AU/issues/10
>>>>>
>>>>> $ git clone -b driver-4.3.21
https://github.com/uminokoe/rtl8812AU.git RTL8814AU-uminokoe
>>>>> $ cd RTL8814AU-uminokoe/
>>>>> $ git revert -n 9260f77 8d33100
>>>>> // "Disabled debugging code."
>>>>> $ curl -s
https://github.com/diederikdehaas/rtl8812AU/commit/3e80ebc.patch | patch -p1
>>>>> // Enables CONFIG_MP_VHT_HW_TX_MODE
>>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
>>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
>>>>>
>>>>> OR
>>>>> $ git clone https://github.com/diederikdehaas/rtl8814AU.git
RTL8814AU-diederikdehaas
>>>>> $ cd RTL8814AU-diederikdehaas/
>>>>> // Adds missing Vendor/Product ID
>>>>> $ sed -i '/0xA834/ a\\t{USB_DEVICE(0x7392, 0xA833), .driver_info
= RTL8814A}, /* Edimax - Edimax */' os_dep/linux/usb_intf.c
>>>>> // "Added VHT capabilities."
>>>>> $ curl -s https://github.com/uminokoe/rtl8812AU/commit/5f75242.patch
| patch -p1
>>>>> // Enables CONFIG_MP_VHT_HW_TX_MODE
>>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
>>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
>>>>>
>>>>>
>>>>> $ make -j3
>>>>> $ su
>>>>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
>>>>> # depmod
>>>>> # modinfo 8814au
>>>>>
>>>>> # modprobe -v 8814au
>>>>> # dmesg:
>>>>> ...
>>>>> RTL871X: module init start
>>>>> RTL871X: rtl8814au v4.3.21_17997.20160531
>>>>> usbcore: registered new interface driver rtl8814au
>>>>> RTL871X: module init ret=0
>>>>> ...
>>>>> # modprobe -rv 8814au
>>>>> # dmesg:
>>>>> ...
>>>>> RTL871X: module exit start
>>>>> usbcore: deregistering interface driver rtl8814au
>>>>> RTL871X: module exit success
>>>>> ...
>>>>>
>>>>>
>>>>> Hello Diederik,
>>>>> it seems there are only two Linux RTL8814AU users, so far.
>>>>>
>>>>> Morris, when you catch some time, would you mind to run a couple
iperf tests with DWA-192,
>>>>> to see real network throughput results.
>>>> I can't run any at the moment because Fedora is refusing to actually
use
>>>> the device at all.
>>>>
>>>> I have also just upgraded to F25 and nothing has changed.
>>>>
>>>> The last time I used this device was on 08/10/2016 and it was using the
>>>> ATH9K driver. The main reason I upgraded to this USB device was that I
>>>> upgraded my router to a faster version, and I found that unlike the
>>>> DWA182 I didn't have to compile my own driver, the kernel had
inbuilt
>>>> support for the DWA192.
>>>>
>>>> It is possible that I have managed to Blacklist the device in some way,
>>>> not by the conventional Blacklist.conf, and I have forgotten how so I
>>>> can't find where I've done it to reverse it.
>>>>
>>>> Also, having never done it before, I also don't know how to run iperf
tests.
>>>>
>>>> regards,
>>>> Steve
>>>>
>>> Did I understand you correctly, what you're saying here is that:
>>> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
>>> therefore the USB based device, was driven by:
>>> $ modinfo --description ath9k
>>> Support for Atheros 802.11n wireless LAN cards.
>>> https://wireless.wiki.kernel.org/en/users/drivers/ath9k
>>> "ath9k is a completely FOSS wireless driver for all Atheros IEEE 802.11n
PCI/PCI-Express and AHB WLAN based chipsets."
>>> https://wiki.debian.org/ath9k
>>> "Atheros 802.11n PCI/PCI-E devices (ath9k)"
>> Yes, when the device was working iwconfig reported the driver as being
>> ATH9K, but if refused to use the 5GHz channel. Following a suggestion on
>> this list I tried compiling my own kernel and setting a recommended
>> flag, but that had no effect on its ability to use the 5GHz channel. It
>> was from compiling my own kernel I found that it looked like the ATH10K
>> driver would support the 5GHz channel, which Winfried de Heiden is
>> confirming, so at the time I couldn't work out why the system wasn't
>> assigning the ATH10K driver instead of the ATH9K driver.
>> From what you are saying it sounds like that various updates to F24
>> (and in F25 which I am using now) have changed the functionality of
>> ATH9K to not support USB devices, which would potentially go a long way
>> towards explaining why my adapter is no longer recognized any more.
>> Also it seems to me that you are suggesting that I need to go back to
>> compiling a driver for this card again (if I have to do this will the
>> driver support the 5GHz channel), if this is so given that from when I
>> first started using this adapter up until 08/10/2016 there was native
>> support in the kernel for the device, why has this support been dropped?
>> I first started using this adapter in F23.
>>
>> regards,
>> Steve
>
> This should show the WiFi devices that are connected to the machine:
> $ echo ; lspci -knn -d ::0280 ; echo ; lsusb ; echo ; lsusb -t ; echo
>
> Would you mind copy and paste the output here.
I have input the commands and the output is listed below.
echo ; lspci -knn -d ::0280 ; echo ; lsusb ; echo ; lsusb -t ; echo
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 045e:0750 Microsoft Corp. Wired Keyboard 600
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 011 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 010 Device 002: ID 2001:331a D-Link Corp.
Bus 010 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
/: Bus 11.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
/: Bus 10.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 480M
/: Bus 09.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
/: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/4p, 12M
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/2p, 12M
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/5p, 12M
|__ Port 2: Dev 2, If 0, Class=Human Interface Device,
Driver=usbhid, 12M
|__ Port 2: Dev 2, If 1, Class=Human Interface Device,
Driver=usbhid, 12M
|__ Port 2: Dev 2, If 2, Class=Human Interface Device,
Driver=usbhid, 12M
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/5p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device,
Driver=usbhid, 1.5M
|__ Port 1: Dev 2, If 1, Class=Human Interface Device,
Driver=usbhid, 1.5M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/4p, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/5p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/5p, 480M
Bus 010 Device 002 is the usb wifi adapter that is not recognized anymore.
Bus 10 Device 2
lsusb:
Bus 010 Device 002: ID 2001:331a D-Link Corp.
lsusb -t:
/: Bus 10.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 480M
8814au.ko when built, installed and loaded,
should show up as assigned to the device:
/: Bus 10 [...]
|__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=8814au, 480M
3:42 p.m.
New subject: [...] D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
On 27/01/2017 21:20, poma wrote:
On 26.01.2017 22:12, Stephen Morris wrote:
> On 24/01/2017 15:12, poma wrote:
>> On 23.01.2017 21:14, Stephen Morris wrote:
>>> On 23/01/2017 08:27, poma wrote:
>>>> On 22.01.2017 21:49, Stephen Morris wrote:
>>>>> On 23/01/2017 00:43, poma wrote:
>>>>>> On 21.01.2017 21:00, poma wrote:
>>>>>>> On 17.01.2017 22:12, Stephen Morris wrote:
>>>>>>> [...]
>>>>>>>> The lsusb output for that device is also below.
>>>>>>>>
>>>>>>>> Bus 010 Device 002: ID 2001:331a D-Link Corp.
>>>>>>>>
>>>>>>> [...]
>>>>>>>
>>>>>>> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
>>>>>>>
>>>>>>> https://wikidevi.com/wiki/D-Link_DWA-192
>>>>>>> http://support.dlink.com/ProductInfo.aspx?m=DWA-192
>>>>>>> ftp://files.dlink.com.au/products/DWA-192
>>>>>>>
https://openitforum.pl/index/recenzje/karty/d-link-dwa-192-r225
>>>>>>>
>>>>>>> https://wikidevi.com/wiki/Edimax_EW-7833UAC
>>>>>>>
http://www.edimax.com/edimax/download/download/data/edimax/global/downloa...
>>>>>>>
http://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-...
>>>>>>>
>>>>>>> https://github.com/pld-linux/rtl8812au
>>>>>>> https://github.com/diederikdehaas/rtl8812AU
>>>>>>>
>>>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>>
>>>>>>> $ unzip EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip
>>>>>>> $ cd
EW7833UAC_linux_4.3.21_kernel_3.16-4.4/EW7833UAC_linux_v4.3.21_17997.20160531/
>>>>>>>
>>>>>>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/disable-debu... | patch
-p1
>>>>>>> $ curl -s
https://github.com/diederikdehaas/rtl8812AU/commit/e6d6beb.patch | patch -p1
>>>>>>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.7.patch | patch -p1
>>>>>>> $ curl -s
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.8.patch | patch -p1
>>>>>>>
>>>>>>> $ make -j3
>>>>>>> $ su
>>>>>>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
>>>>>>> # depmod
>>>>>>> # modinfo 8814au | grep 2001
>>>>>>>
>>>>>>> # modprobe -v 8814au
>>>>>>> # dmesg:
>>>>>>> ...
>>>>>>> RTL871X: module init start
>>>>>>> RTL871X: rtl8814au v4.3.21_17997.20160531
>>>>>>> RTL871X: build time: Jan 21 2017 20:04:38
>>>>>>> usbcore: registered new interface driver rtl8814au
>>>>>>> RTL871X: module init ret=0
>>>>>>> ...
>>>>>>> # modprobe -rv 8814au
>>>>>>> # dmesg:
>>>>>>> ...
>>>>>>> RTL871X: module exit start
>>>>>>> usbcore: deregistering interface driver rtl8814au
>>>>>>> RTL871X: module exit success
>>>>>>> ...
>>>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>>
>>>>>>> Wifi ball works now?
>>>>>>>
>>>>>>>
>>>>>>> HW add.
>>>>>>> https://wikidevi.com/wiki/ASUS_USB-AC68
>>>>>>> https://www.asus.com/Networking/USB-AC68/HelpDesk_Download
>>>>>>>
>>>>>>> https://wikidevi.com/wiki/TP-LINK_Archer_T9UH
>>>>>>> http://www.tp-link.com/en/download/Archer-T9UH.html
>>>>>>>
>>>>>>> https://wikidevi.com/wiki/TRENDnet_TEW-809UB
>>>>>>>
https://www.trendnet.com/support/supportdetail.asp?prod=100_TEW-809UB
>>>>>>>
>>>>>>> SW add.
>>>>>>> https://github.com/abperiasamy/rtl8812AU_8821AU_linux
>>>>>>> https://github.com/austinmarton/rtl8812au_linux
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> OR
>>>>>> according to "rtl8814au? #10"
>>>>>> https://github.com/diederikdehaas/rtl8812AU/issues/10
>>>>>>
>>>>>> $ git clone -b driver-4.3.21
https://github.com/uminokoe/rtl8812AU.git RTL8814AU-uminokoe
>>>>>> $ cd RTL8814AU-uminokoe/
>>>>>> $ git revert -n 9260f77 8d33100
>>>>>> // "Disabled debugging code."
>>>>>> $ curl -s
https://github.com/diederikdehaas/rtl8812AU/commit/3e80ebc.patch | patch -p1
>>>>>> // Enables CONFIG_MP_VHT_HW_TX_MODE
>>>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
>>>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
>>>>>>
>>>>>> OR
>>>>>> $ git clone https://github.com/diederikdehaas/rtl8814AU.git
RTL8814AU-diederikdehaas
>>>>>> $ cd RTL8814AU-diederikdehaas/
>>>>>> // Adds missing Vendor/Product ID
>>>>>> $ sed -i '/0xA834/ a\\t{USB_DEVICE(0x7392, 0xA833),
.driver_info = RTL8814A}, /* Edimax - Edimax */' os_dep/linux/usb_intf.c
>>>>>> // "Added VHT capabilities."
>>>>>> $ curl -s
https://github.com/uminokoe/rtl8812AU/commit/5f75242.patch | patch -p1
>>>>>> // Enables CONFIG_MP_VHT_HW_TX_MODE
>>>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
>>>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
>>>>>>
>>>>>>
>>>>>> $ make -j3
>>>>>> $ su
>>>>>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
>>>>>> # depmod
>>>>>> # modinfo 8814au
>>>>>>
>>>>>> # modprobe -v 8814au
>>>>>> # dmesg:
>>>>>> ...
>>>>>> RTL871X: module init start
>>>>>> RTL871X: rtl8814au v4.3.21_17997.20160531
>>>>>> usbcore: registered new interface driver rtl8814au
>>>>>> RTL871X: module init ret=0
>>>>>> ...
>>>>>> # modprobe -rv 8814au
>>>>>> # dmesg:
>>>>>> ...
>>>>>> RTL871X: module exit start
>>>>>> usbcore: deregistering interface driver rtl8814au
>>>>>> RTL871X: module exit success
>>>>>> ...
>>>>>>
>>>>>>
>>>>>> Hello Diederik,
>>>>>> it seems there are only two Linux RTL8814AU users, so far.
>>>>>>
>>>>>> Morris, when you catch some time, would you mind to run a couple
iperf tests with DWA-192,
>>>>>> to see real network throughput results.
>>>>> I can't run any at the moment because Fedora is refusing to
actually use
>>>>> the device at all.
>>>>>
>>>>> I have also just upgraded to F25 and nothing has changed.
>>>>>
>>>>> The last time I used this device was on 08/10/2016 and it was using
the
>>>>> ATH9K driver. The main reason I upgraded to this USB device was that
I
>>>>> upgraded my router to a faster version, and I found that unlike the
>>>>> DWA182 I didn't have to compile my own driver, the kernel had
inbuilt
>>>>> support for the DWA192.
>>>>>
>>>>> It is possible that I have managed to Blacklist the device in some
way,
>>>>> not by the conventional Blacklist.conf, and I have forgotten how so
I
>>>>> can't find where I've done it to reverse it.
>>>>>
>>>>> Also, having never done it before, I also don't know how to run
iperf tests.
>>>>>
>>>>> regards,
>>>>> Steve
>>>>>
>>>> Did I understand you correctly, what you're saying here is that:
>>>> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
>>>> therefore the USB based device, was driven by:
>>>> $ modinfo --description ath9k
>>>> Support for Atheros 802.11n wireless LAN cards.
>>>> https://wireless.wiki.kernel.org/en/users/drivers/ath9k
>>>> "ath9k is a completely FOSS wireless driver for all Atheros IEEE
802.11n PCI/PCI-Express and AHB WLAN based chipsets."
>>>> https://wiki.debian.org/ath9k
>>>> "Atheros 802.11n PCI/PCI-E devices (ath9k)"
>>> Yes, when the device was working iwconfig reported the driver as being
>>> ATH9K, but if refused to use the 5GHz channel. Following a suggestion on
>>> this list I tried compiling my own kernel and setting a recommended
>>> flag, but that had no effect on its ability to use the 5GHz channel. It
>>> was from compiling my own kernel I found that it looked like the ATH10K
>>> driver would support the 5GHz channel, which Winfried de Heiden is
>>> confirming, so at the time I couldn't work out why the system wasn't
>>> assigning the ATH10K driver instead of the ATH9K driver.
>>> From what you are saying it sounds like that various updates to F24
>>> (and in F25 which I am using now) have changed the functionality of
>>> ATH9K to not support USB devices, which would potentially go a long way
>>> towards explaining why my adapter is no longer recognized any more.
>>> Also it seems to me that you are suggesting that I need to go back to
>>> compiling a driver for this card again (if I have to do this will the
>>> driver support the 5GHz channel), if this is so given that from when I
>>> first started using this adapter up until 08/10/2016 there was native
>>> support in the kernel for the device, why has this support been dropped?
>>> I first started using this adapter in F23.
>>>
>>> regards,
>>> Steve
>> This should show the WiFi devices that are connected to the machine:
>> $ echo ; lspci -knn -d ::0280 ; echo ; lsusb ; echo ; lsusb -t ; echo
>>
>> Would you mind copy and paste the output here.
> I have input the commands and the output is listed below.
>
> echo ; lspci -knn -d ::0280 ; echo ; lsusb ; echo ; lsusb -t ; echo
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 005 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
> Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 002: ID 045e:0750 Microsoft Corp. Wired Keyboard 600
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 011 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 010 Device 002: ID 2001:331a D-Link Corp.
> Bus 010 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> /: Bus 11.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
> /: Bus 10.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
> |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 480M
> /: Bus 09.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
> /: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
> /: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/4p, 12M
> /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/2p, 12M
> /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/5p, 12M
> |__ Port 2: Dev 2, If 0, Class=Human Interface Device,
> Driver=usbhid, 12M
> |__ Port 2: Dev 2, If 1, Class=Human Interface Device,
> Driver=usbhid, 12M
> |__ Port 2: Dev 2, If 2, Class=Human Interface Device,
> Driver=usbhid, 12M
> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/5p, 12M
> |__ Port 1: Dev 2, If 0, Class=Human Interface Device,
> Driver=usbhid, 1.5M
> |__ Port 1: Dev 2, If 1, Class=Human Interface Device,
> Driver=usbhid, 1.5M
> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/4p, 480M
> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/5p, 480M
> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/5p, 480M
>
> Bus 010 Device 002 is the usb wifi adapter that is not recognized anymore.
Bus 10 Device 2
lsusb:
Bus 010 Device 002: ID 2001:331a D-Link Corp.
lsusb -t:
/: Bus 10.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 480M
8814au.ko when built, installed and loaded,
should show up as assigned to the device:
/: Bus 10 [...]
|__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=8814au, 480M
I
can rebuild that driver like I was with the DWA-182 usb device when I
had it, but when I purchased the DWA-192, under Fedora 23 there was
native support for DWA-192 in the kernel, hence I did not have to
compile a driver anymore. At the time I also raised a Bugzilla around
the fact that the ATH9K driver (which is the driver the commands I
issued at the time, that I was advised to on this list, told me was the
one being used) did not provide access to the 5 GHz channel. That driver
was being used through F23 and F24, or at least native kernel support,
was provided up until 08/10/2016 at which time I switched over to an
Ethernet Home Plug interface to networking (this was because the device
became problematic in retaining connection to the network).
Now that I have switched back to the wifi device, because even on the
2.4 GHz channel this wifi device is faster than the Ethernet device, I
have found that the DWA-192 device appears to no longer be supported
natively by the kernel.
Why has support for this device been removed from the kernel? As a side
issue to this, I have also noticed that this device has exactly the same
non-support issue under Ubuntu 16.10.
regards,
Steve
2644
days inactive
2656
days old
15 comments
4 participants
participants (4)
-
poma -
Rick Stevens -
Stephen Morris -
Terry Polzin