Dear All,
I am trying to use the following WiFi USB adapter on F15:
TP-LINK TL-WN821N.
How can I install the respective driver?
Thanks in advance,
Paul
On Tue, 2011-08-23 at 20:15 +0100, Paul Smith wrote:
TP-LINK TL-WN821N
Can you post output of lsmod and lsusb. Have you installed the firmware for the device into /lib/firmware? If the device is supported by the kernel you won't be able to load the module without the firmware installed.
Google is your friend.
On Tue, Aug 23, 2011 at 8:34 PM, Terry Polzin foxec208@wowway.com wrote:
TP-LINK TL-WN821N
Can you post output of lsmod and lsusb. Have you installed the firmware for the device into /lib/firmware? If the device is supported by the kernel you won't be able to load the module without the firmware installed.
Google is your friend.
Thanks, Terry.
$ lsmod Module Size Used by fuse 62381 3 vboxnetadp 5674 0 vboxnetflt 17790 0 vboxdrv 1789793 2 vboxnetadp,vboxnetflt sunrpc 200079 1 cpufreq_ondemand 5934 2 acpi_cpufreq 9536 0 freq_table 5038 2 cpufreq_ondemand,acpi_cpufreq mperf 1449 1 acpi_cpufreq bnep 14635 2 bluetooth 191587 7 bnep ip6t_REJECT 3992 2 nf_conntrack_ipv6 7730 2 nf_defrag_ipv6 9083 1 nf_conntrack_ipv6 nf_conntrack_ipv4 8358 2 nf_defrag_ipv4 1513 1 nf_conntrack_ipv4 xt_state 1306 4 nf_conntrack 67613 3 nf_conntrack_ipv6,nf_conntrack_ipv4,xt_state ip6table_filter 1655 1 ip6_tables 16908 1 ip6table_filter snd_hda_codec_hdmi 22499 1 snd_hda_codec_conexant 54661 1 snd_hda_intel 23896 2 snd_hda_codec 82508 3 snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_hda_intel uvcvideo 57089 0 videodev 72104 1 uvcvideo media 11611 2 uvcvideo,videodev ath9k_htc 50165 0 ath9k_common 2496 1 ath9k_htc ath9k_hw 271229 2 ath9k_htc,ath9k_common snd_hwdep 6328 1 snd_hda_codec v4l2_compat_ioctl32 7377 1 videodev arc4 1417 2 snd_seq 52322 0 snd_seq_device 5941 1 snd_seq ath5k 162786 0 snd_pcm 78424 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec ath 15098 3 ath9k_htc,ath9k_hw,ath5k snd_timer 19372 2 snd_seq,snd_pcm mac80211 247332 2 ath9k_htc,ath5k snd 63380 13 snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer soundcore 6267 1 snd snd_page_alloc 7343 2 snd_hda_intel,snd_pcm cfg80211 148129 4 ath9k_htc,ath5k,ath,mac80211 r8169 38146 0 hp_wmi 8103 0 sparse_keymap 3358 1 hp_wmi rfkill 16436 5 bluetooth,cfg80211,hp_wmi i2c_i801 9237 0 serio_raw 4414 0 mii 4335 1 r8169 iTCO_wdt 13000 0 iTCO_vendor_support 2578 1 iTCO_wdt joydev 9615 0 microcode 18587 0 ipv6 284570 43 ip6t_REJECT,nf_conntrack_ipv6,nf_defrag_ipv6 uas 7775 0 ums_realtek 4859 0 usb_storage 46091 1 ums_realtek wmi 9033 1 hp_wmi i915 378728 2 drm_kms_helper 26474 1 i915 drm 193923 3 i915,drm_kms_helper i2c_algo_bit 4974 1 i915 i2c_core 25712 6 videodev,i2c_i801,i915,drm_kms_helper,drm,i2c_algo_bit video 12340 1 i915 $
$ lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 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 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 multicard reader Bus 001 Device 003: ID 04f2:b091 Chicony Electronics Co., Ltd Webcam Bus 002 Device 005: ID 0cf3:7015 Atheros Communications, Inc. Bus 007 Device 002: ID 04fc:0003 Sunplus Technology Co., Ltd CM1092 Optical Scroller Mouse $
Paul Smith writes:
On Tue, Aug 23, 2011 at 8:34 PM, Terry Polzin foxec208@wowway.com wrote:
TP-LINK TL-WN821N
Can you post output of lsmod and lsusb. Have you installed the firmware for the device into /lib/firmware? If the device is supported by the kernel you won't be able to load the module without the firmware installed.
Google is your friend.
Thanks, Terry.
Why do you believe you need to install some kind of a driver? From the below, it looks like your card is an atheros chip-based one, and you have a bunch of ath9 modules loaded.
What exactly is or is not working for you.
$ lsmod Module Size Used by fuse 62381 3 vboxnetadp 5674 0 vboxnetflt 17790 0 vboxdrv 1789793 2 vboxnetadp,vboxnetflt sunrpc 200079 1 cpufreq_ondemand 5934 2 acpi_cpufreq 9536 0 freq_table 5038 2 cpufreq_ondemand,acpi_cpufreq mperf 1449 1 acpi_cpufreq bnep 14635 2 bluetooth 191587 7 bnep ip6t_REJECT 3992 2 nf_conntrack_ipv6 7730 2 nf_defrag_ipv6 9083 1 nf_conntrack_ipv6 nf_conntrack_ipv4 8358 2 nf_defrag_ipv4 1513 1 nf_conntrack_ipv4 xt_state 1306 4 nf_conntrack 67613 3 nf_conntrack_ipv6,nf_conntrack_ipv4,xt_state ip6table_filter 1655 1 ip6_tables 16908 1 ip6table_filter snd_hda_codec_hdmi 22499 1 snd_hda_codec_conexant 54661 1 snd_hda_intel 23896 2 snd_hda_codec 82508 3 snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_hda_intel uvcvideo 57089 0 videodev 72104 1 uvcvideo media 11611 2 uvcvideo,videodev ath9k_htc 50165 0 ath9k_common 2496 1 ath9k_htc ath9k_hw 271229 2 ath9k_htc,ath9k_common snd_hwdep 6328 1 snd_hda_codec v4l2_compat_ioctl32 7377 1 videodev arc4 1417 2 snd_seq 52322 0 snd_seq_device 5941 1 snd_seq ath5k 162786 0 snd_pcm 78424 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec ath 15098 3 ath9k_htc,ath9k_hw,ath5k snd_timer 19372 2 snd_seq,snd_pcm mac80211 247332 2 ath9k_htc,ath5k snd 63380 13 snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,ssd_pcm,snd_timer soundcore 6267 1 snd snd_page_alloc 7343 2 snd_hda_intel,snd_pcm cfg80211 148129 4 ath9k_htc,ath5k,ath,mac80211 r8169 38146 0 hp_wmi 8103 0 sparse_keymap 3358 1 hp_wmi rfkill 16436 5 bluetooth,cfg80211,hp_wmi i2c_i801 9237 0 serio_raw 4414 0 mii 4335 1 r8169 iTCO_wdt 13000 0 iTCO_vendor_support 2578 1 iTCO_wdt joydev 9615 0 microcode 18587 0 ipv6 284570 43 ip6t_REJECT,nf_conntrack_ipv6,nf_defrag_ipv6 uas 7775 0 ums_realtek 4859 0 usb_storage 46091 1 ums_realtek wmi 9033 1 hp_wmi i915 378728 2 drm_kms_helper 26474 1 i915 drm 193923 3 i915,drm_kms_helper i2c_algo_bit 4974 1 i915 i2c_core 25712 6 videodev,i2c_i801,i915,drm_kms_helper,drm,i2c_algo_bit video 12340 1 i915 $
$ lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 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 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 multicard reader Bus 001 Device 003: ID 04f2:b091 Chicony Electronics Co., Ltd Webcam Bus 002 Device 005: ID 0cf3:7015 Atheros Communications, Inc. Bus 007 Device 002: ID 04fc:0003 Sunplus Technology Co., Ltd CM1092 Optical Scroller Mouse $ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
On Tue, Aug 23, 2011 at 9:22 PM, Sam Varshavchik mrsam@courier-mta.com wrote:
TP-LINK TL-WN821N
Can you post output of lsmod and lsusb. Have you installed the firmware for the device into /lib/firmware? If the device is supported by the kernel you won't be able to load the module without the firmware installed.
Google is your friend.
Thanks, Terry.
Why do you believe you need to install some kind of a driver? From the below, it looks like your card is an atheros chip-based one, and you have a bunch of ath9 modules loaded.
What exactly is or is not working for you.
Well, I plug the the USB device and nothing happens. According to the manual, a led should be turned on when I plug the USB.
Paul
On Tue, Aug 23, 2011 at 9:30 PM, Paul Smith phhs80@gmail.com wrote:
TP-LINK TL-WN821N
Can you post output of lsmod and lsusb. Have you installed the firmware for the device into /lib/firmware? If the device is supported by the kernel you won't be able to load the module without the firmware installed.
Google is your friend.
Thanks, Terry.
Why do you believe you need to install some kind of a driver? From the below, it looks like your card is an atheros chip-based one, and you have a bunch of ath9 modules loaded.
What exactly is or is not working for you.
Well, I plug the the USB device and nothing happens. According to the manual, a led should be turned on when I plug the USB.
A possible explanation is here:
http://forums.fedoraforum.org/showthread.php?t=268068
Paul
On Tue, Aug 23, 2011 at 11:36:06PM +0100, Paul Smith wrote:
On Tue, Aug 23, 2011 at 9:30 PM, Paul Smith phhs80@gmail.com wrote:
TP-LINK TL-WN821N
Can you post output of lsmod and lsusb. Have you installed the firmware for the device into /lib/firmware? If the device is supported by the kernel you won't be able to load the module without the firmware installed.
Google is your friend.
Thanks, Terry.
Why do you believe you need to install some kind of a driver? From the below, it looks like your card is an atheros chip-based one, and you have a bunch of ath9 modules loaded.
What exactly is or is not working for you.
Well, I plug the the USB device and nothing happens. According to the manual, a led should be turned on when I plug the USB.
A possible explanation is here:
That relates to the carl9170 driver. We don't have that firmware packaged in Fedora either -- no one ever bothered to review my package of the SH cross compiler used to build the firmware, and I haven't bothered to bang the drum about it either. Anyway, that's a different issue.
The ath9k_htc firmware used to be in the linux-firmware tree, but apparently they have stopped updating it there? Not sure...
Anyway, you can find the firmware and get it installed by starting here:
http://wireless.kernel.org/en/users/Drivers/ath9k_htc#Firmware
Hth!
John
On Wed, Aug 24, 2011 at 3:28 PM, John W. Linville linville@redhat.com wrote:
> TP-LINK TL-WN821N
Can you post output of lsmod and lsusb. Have you installed the firmware for the device into /lib/firmware? If the device is supported by the kernel you won't be able to load the module without the firmware installed.
Google is your friend.
Thanks, Terry.
Why do you believe you need to install some kind of a driver? From the below, it looks like your card is an atheros chip-based one, and you have a bunch of ath9 modules loaded.
What exactly is or is not working for you.
Well, I plug the the USB device and nothing happens. According to the manual, a led should be turned on when I plug the USB.
A possible explanation is here:
That relates to the carl9170 driver. We don't have that firmware packaged in Fedora either -- no one ever bothered to review my package of the SH cross compiler used to build the firmware, and I haven't bothered to bang the drum about it either. Anyway, that's a different issue.
The ath9k_htc firmware used to be in the linux-firmware tree, but apparently they have stopped updating it there? Not sure...
Anyway, you can find the firmware and get it installed by starting here:
http://wireless.kernel.org/en/users/Drivers/ath9k_htc#Firmware
Hth!
Thanks, John. Since the referred wireless adapter did not improve my signal reception, I returned it to the shop meanwhile. So, in my case, that is not anymore an issue. However, I did have the wireless adapter working with
kernel-2.6.38.8-35.fc15.x86_64
Paul
Paul Smith writes:
On Tue, Aug 23, 2011 at 9:22 PM, Sam Varshavchik mrsam@courier-mta.com wrote:
TP-LINK TL-WN821N
Can you post output of lsmod and lsusb. Have you installed the firmware for the device into /lib/firmware? If the device is supported by the kernel you won't be able to load the module without the firmware installed.
Google is your friend.
Thanks, Terry.
Why do you believe you need to install some kind of a driver? From the below, it looks like your card is an atheros chip-based one, and you have a bunch of ath9 modules loaded.
What exactly is or is not working for you.
Well, I plug the the USB device and nothing happens. According to the manual, a led should be turned on when I plug the USB.
That may not mean anything. These kinds of idiot lights are often software controlled. My laptop has a built-in idiot light for it's built-in wireless cards. It obediently lights up when I boot Windows. It stays off in Fedora. Maybe in blinks occasionally, but wireless works just fine. The kernel driver, I guess, doesn't bother to turn on the idiot light, when it initializes the adapter.
The most important thing is whether NetworkManager claims to see a wireless interface, and gives you a list of available access points your wireless card is hearing, and not whether some idiot light comes on.
A good source of clues is to look at what gets written into /var/log/messages, when you plug in the card.
On Wed, Aug 24, 2011 at 3:44 PM, Sam Varshavchik mrsam@courier-mta.com wrote:
TP-LINK TL-WN821N
Can you post output of lsmod and lsusb. Have you installed the firmware for the device into /lib/firmware? If the device is supported by the kernel you won't be able to load the module without the firmware installed.
Google is your friend.
Thanks, Terry.
Why do you believe you need to install some kind of a driver? From the below, it looks like your card is an atheros chip-based one, and you have a bunch of ath9 modules loaded.
What exactly is or is not working for you.
Well, I plug the the USB device and nothing happens. According to the manual, a led should be turned on when I plug the USB.
That may not mean anything. These kinds of idiot lights are often software controlled. My laptop has a built-in idiot light for it's built-in wireless cards. It obediently lights up when I boot Windows. It stays off in Fedora. Maybe in blinks occasionally, but wireless works just fine. The kernel driver, I guess, doesn't bother to turn on the idiot light, when it initializes the adapter.
The most important thing is whether NetworkManager claims to see a wireless interface, and gives you a list of available access points your wireless card is hearing, and not whether some idiot light comes on.
A good source of clues is to look at what gets written into /var/log/messages, when you plug in the card.
Thanks, Sam. You are absolutely right: the wireless adapter was working properly without any light being blinking or flashing.
Paul
On Wed, Aug 24, 2011 at 3:28 PM, John W. Linville linville@redhat.com wrote:
On Tue, Aug 23, 2011 at 11:36:06PM +0100, Paul Smith wrote:
On Tue, Aug 23, 2011 at 9:30 PM, Paul Smith phhs80@gmail.com wrote:
> TP-LINK TL-WN821N
Can you post output of lsmod and lsusb. Have you installed the firmware for the device into /lib/firmware? If the device is supported by the kernel you won't be able to load the module without the firmware installed.
Google is your friend.
Thanks, Terry.
Why do you believe you need to install some kind of a driver? From the below, it looks like your card is an atheros chip-based one, and you have a bunch of ath9 modules loaded.
What exactly is or is not working for you.
Well, I plug the the USB device and nothing happens. According to the manual, a led should be turned on when I plug the USB.
A possible explanation is here:
That relates to the carl9170 driver. We don't have that firmware packaged in Fedora either -- no one ever bothered to review my package of the SH cross compiler used to build the firmware, and I haven't bothered to bang the drum about it either. Anyway, that's a different issue.
The ath9k_htc firmware used to be in the linux-firmware tree, but apparently they have stopped updating it there? Not sure...
Anyway, you can find the firmware and get it installed by starting here:
http://wireless.kernel.org/en/users/Drivers/ath9k_htc#Firmware
Hth!
John
I also have a machine that has to use an external usb wifi adapter and in my case I have a tiny device that relies on rtl8712su or rtl8192su - which is a slight aside from the thread on ath9k...but similar issue in that there is no wireless driver by default.
Until f14/15 I was able to compile the driver from the source from realtek - and copy the firmware to /lib/firmware and it would work fine - however I recently installed f16 alpha rc5 and updated via ether - but the wireless driver won't compile - (yes I have kernel-devel and kernel-headers).
I could give the output of lsusb and other diagnostics but I wonder if anyone else has had a similar issue with f16a ? Any tips for rtl8712/8192 for usb would be appreciated.
-
John W. Linville -
mike cloaked -
Paul Smith -
Sam Varshavchik -
Terry Polzin