Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[SOLVED]Alfa AWUS036NHA install on debian jessie

Need help with peripherals or devices?
Post Reply
Message
Author
dafunk
Posts: 43
Joined: 2014-12-04 07:48

[SOLVED]Alfa AWUS036NHA install on debian jessie

#1 Post by dafunk »

Hi, I recently install debian 8 lxde (jessie) on a 1000HA eeepc but my alfa AWUS036NHA didn't work correctly.
With the last version of the os (debian 7 xfce) I'v install firmware-atheros and all goes well, but this time even if with lsusb the card seems detected the led card is off....I'v try also to install firmware-ath9k-htc but with no result....I'm noob of linux, so did you have any suggestion? (maybe systemd change something???).

Thanks

Alfa AWUS036NHA is an usb dongle. I'll post error message as soon as possible
Last edited by dafunk on 2017-10-07 10:08, edited 2 times in total.

User avatar
debiman
Posts: 3063
Joined: 2013-03-12 07:18

Re: Alfa AWUS036NHA install on debian jessie

#2 Post by debiman »

what is Alfa AWUS036NHA?
a wireless card? or usb wifi dongle?
and you cannot connect to the internet through it?
if so, please provide the information requested in this thread.


User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Alfa AWUS036NHA install on debian jessie

#4 Post by stevepusser »

Hope you don't have the "L" version of the chipset...seems like a scam for Linux users:
According to FCC test results, this adapter is ~5 times weaker (sure it's "weaker" just as "L" stands for "Low cost" details: https://github.com/qca/open-ath9k-htc-f ... -252649735)

than typical Wi-Fi adapters such as TP-LINK TL-WN722N. Although it's flagged high-power manufacturer never released driver to support high-power operation.
MX Linux packager and developer

dafunk
Posts: 43
Joined: 2014-12-04 07:48

Re: Alfa AWUS036NHA install on debian jessie

#5 Post by dafunk »

@shep: already follow the debian guide with no result...led is off and the device seems not work

@debiman: here the output messages

uname -rv

Code: Select all

3.16.0-4-686-pae #1 SMP Debian 3.16.43-2+deb8u5 (2017-09-19)
lspci -knn | grep -EiA2 net

Code: Select all

01:00.0 Ethernet controller [0200]: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) [168c:001c] (rev 01)
	Subsystem: AzureWave AW-GE780 802.11bg Wireless Mini PCIe Card [1a3b:1026]
	Kernel driver in use: ath5k
03:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet [1969:1026] (rev b0)
	Subsystem: ASUSTeK Computer Inc. Device [1043:8324]
	Kernel driver in use: ATL1E
dmesg|grep -Ei 'wlan|firmw|dhc'

Code: Select all

[    0.151614] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
[    3.095074] psmouse serio1: elantech: assuming hardware version 2 (with firmware version 0x020030)
[   24.525603] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   36.531661] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   39.051207] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   42.745357] wlan0: authenticate with 2c:b0:5d:58:f3:20
[   42.752871] wlan0: send auth to 2c:b0:5d:58:f3:20 (try 1/3)
[   42.754438] wlan0: authenticated
[   42.756536] wlan0: associate with 2c:b0:5d:58:f3:20 (try 1/3)
[   42.759127] wlan0: RX AssocResp from 2c:b0:5d:58:f3:20 (capab=0x411 status=0 aid=4)
[   42.759310] wlan0: associated
[   42.759544] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 8853.415670] wlan0: deauthenticating from 2c:b0:5d:58:f3:20 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 8855.882366] wlan0: authenticate with 2c:b0:5d:58:f3:20
[ 8855.890379] wlan0: send auth to 2c:b0:5d:58:f3:20 (try 1/3)
[ 8855.891892] wlan0: authenticated
[ 8855.892256] wlan0: associate with 2c:b0:5d:58:f3:20 (try 1/3)
[ 8855.894753] wlan0: RX AssocResp from 2c:b0:5d:58:f3:20 (capab=0x411 status=0 aid=3)
[ 8855.894927] wlan0: associated
[ 8856.051659] wlan0: deauthenticating from 2c:b0:5d:58:f3:20 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 8856.196601] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 8860.055886] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 8861.564904] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 8862.033960] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 8864.265815] wlan0: authenticate with 2c:b0:5d:58:f3:20
[ 8864.270198] wlan0: send auth to 2c:b0:5d:58:f3:20 (try 1/3)
[ 8864.271774] wlan0: authenticated
[ 8864.272969] wlan0: associate with 2c:b0:5d:58:f3:20 (try 1/3)
[ 8864.275536] wlan0: RX AssocResp from 2c:b0:5d:58:f3:20 (capab=0x411 status=0 aid=3)
[ 8864.275724] wlan0: associated
[ 8864.275866] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 9541.758878] usb 2-2: ath9k_htc: Firmware htc_9271.fw requested
[ 9541.775326] usb 2-2: firmware: direct-loading firmware htc_9271.fw
sudo cat /var/log/syslog | grep -Ei 'net|wpa|dhc'

Code: Select all

Oct  6 19:52:59 host dhclient: Killed old client process
Oct  6 19:53:00 host dhclient: Internet Systems Consortium DHCP Client 4.3.1
Oct  6 19:53:00 host dhclient: Copyright 2004-2014 Internet Systems Consortium.
Oct  6 19:53:00 host dhclient: All rights reserved.
Oct  6 19:53:00 host dhclient: For info, please visit https://www.isc.org/software/dhcp/
Oct  6 19:53:00 host dhclient: 
Oct  6 19:53:00 host dhclient: Listening on LPF/wlan0/00:22:43:4e:b5:76
Oct  6 19:53:00 host dhclient: Sending on   LPF/wlan0/00:22:43:4e:b5:76
Oct  6 19:53:00 host dhclient: Sending on   Socket/fallback
Oct  6 19:53:00 host dhclient: DHCPRELEASE on wlan0 to 192.168.0.1 port 67
Oct  6 19:53:00 host kernel: [ 8856.196601] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Oct  6 19:53:01 host dhclient: Internet Systems Consortium DHCP Client 4.3.1
Oct  6 19:53:01 host dhclient: Copyright 2004-2014 Internet Systems Consortium.
Oct  6 19:53:01 host dhclient: All rights reserved.
Oct  6 19:53:01 host dhclient: For info, please visit https://www.isc.org/software/dhcp/
Oct  6 19:53:01 host dhclient: 
Oct  6 19:53:01 host dhclient: Listening on LPF/eth0/00:23:54:34:dd:d2
Oct  6 19:53:01 host dhclient: Sending on   LPF/eth0/00:23:54:34:dd:d2
Oct  6 19:53:01 host dhclient: Sending on   Socket/fallback
Oct  6 19:53:01 host kernel: [ 8856.441290] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct  6 19:53:04 host kernel: [ 8860.055886] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Oct  6 19:53:06 host dhclient: Internet Systems Consortium DHCP Client 4.3.1
Oct  6 19:53:06 host dhclient: Copyright 2004-2014 Internet Systems Consortium.
Oct  6 19:53:06 host dhclient: All rights reserved.
Oct  6 19:53:06 host dhclient: For info, please visit https://www.isc.org/software/dhcp/
Oct  6 19:53:06 host dhclient: 
Oct  6 19:53:06 host dhclient: Listening on LPF/wlan0/00:22:43:4e:b5:76
Oct  6 19:53:06 host dhclient: Sending on   LPF/wlan0/00:22:43:4e:b5:76
Oct  6 19:53:06 host dhclient: Sending on   Socket/fallback
Oct  6 19:53:06 host dhclient: DHCPRELEASE on wlan0 to 192.168.0.1 port 67
Oct  6 19:53:06 host dhclient: send_packet: Network is unreachable
Oct  6 19:53:06 host dhclient: send_packet: please consult README file regarding broadcast address.
Oct  6 19:53:06 host dhclient: dhclient.c:2331: Failed to send 300 byte long packet over fallback interface.
Oct  6 19:53:06 host kernel: [ 8861.564904] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Oct  6 19:53:06 host dhclient: Internet Systems Consortium DHCP Client 4.3.1
Oct  6 19:53:06 host dhclient: Copyright 2004-2014 Internet Systems Consortium.
Oct  6 19:53:06 host dhclient: All rights reserved.
Oct  6 19:53:06 host dhclient: For info, please visit https://www.isc.org/software/dhcp/
Oct  6 19:53:06 host dhclient: 
Oct  6 19:53:06 host dhclient: Listening on LPF/eth0/00:23:54:34:dd:d2
Oct  6 19:53:06 host dhclient: Sending on   LPF/eth0/00:23:54:34:dd:d2
Oct  6 19:53:06 host dhclient: Sending on   Socket/fallback
Oct  6 19:53:06 host kernel: [ 8861.781310] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct  6 19:53:06 host dhclient: Internet Systems Consortium DHCP Client 4.3.1
Oct  6 19:53:06 host dhclient: Copyright 2004-2014 Internet Systems Consortium.
Oct  6 19:53:06 host dhclient: All rights reserved.
Oct  6 19:53:06 host dhclient: For info, please visit https://www.isc.org/software/dhcp/
Oct  6 19:53:06 host dhclient: 
Oct  6 19:53:06 host dhclient: Listening on LPF/wlan0/00:22:43:4e:b5:76
Oct  6 19:53:06 host dhclient: Sending on   LPF/wlan0/00:22:43:4e:b5:76
Oct  6 19:53:06 host dhclient: Sending on   Socket/fallback
Oct  6 19:53:06 host dhclient: DHCPRELEASE on wlan0 to 192.168.0.1 port 67
Oct  6 19:53:06 host dhclient: send_packet: Network is unreachable
Oct  6 19:53:06 host dhclient: send_packet: please consult README file regarding broadcast address.
Oct  6 19:53:06 host dhclient: dhclient.c:2331: Failed to send 300 byte long packet over fallback interface.
Oct  6 19:53:06 host kernel: [ 8862.033960] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Oct  6 19:53:09 host kernel: [ 8864.275866] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Oct  6 19:53:10 host dhclient: Internet Systems Consortium DHCP Client 4.3.1
Oct  6 19:53:10 host dhclient: Copyright 2004-2014 Internet Systems Consortium.
Oct  6 19:53:10 host dhclient: All rights reserved.
Oct  6 19:53:10 host dhclient: For info, please visit https://www.isc.org/software/dhcp/
Oct  6 19:53:10 host dhclient: 
Oct  6 19:53:10 host dhclient: Listening on LPF/wlan0/00:22:43:4e:b5:76
Oct  6 19:53:10 host dhclient: Sending on   LPF/wlan0/00:22:43:4e:b5:76
Oct  6 19:53:10 host dhclient: Sending on   Socket/fallback
Oct  6 19:53:10 host dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Oct  6 19:53:10 host dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Oct  6 19:53:10 host dhclient: DHCPOFFER from 192.168.0.1
Oct  6 19:53:10 host dhclient: DHCPACK from 192.168.0.1
Oct  6 19:53:10 host dhclient: bound to 192.168.0.3 -- renewal in 39083 seconds.
maybe I have to use some software to select the wifi network card??...in wicd under lxde I didn't found (or I don't know how ) any option...

shep
Posts: 423
Joined: 2011-03-15 15:22

Re: Alfa AWUS036NHA install on debian jessie

#6 Post by shep »

01:00.0 Ethernet controller [0200]: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) [168c:001c] (rev 01)
Subsystem: AzureWave AW-GE780 802.11bg Wireless Mini PCIe Card [1a3b:1026]


This indicates that you also have an Atheros Mini PCIe card - is there a reason you do not want to use the built in wireless? This particular chip is well supported and firmware free. It will not be as fast 11b/g vs 11b/g/n but will be an easier setup and less junk to drag around when mobile.
Oct 6 19:53:10 host dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Oct 6 19:53:10 host dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Oct 6 19:53:10 host dhclient: DHCPOFFER from 192.168.0.1
Oct 6 19:53:10 host dhclient: DHCPACK from 192.168.0.1
Oct 6 19:53:10 host dhclient: bound to 192.168.0.3 -- renewal in 39083 seconds.
It actually looks like you are on line with this card.

dafunk
Posts: 43
Joined: 2014-12-04 07:48

Re: Alfa AWUS036NHA install on debian jessie

#7 Post by dafunk »

@shep: ok, but previously I'v debian 7 installed and the alfa wifi doongle has the led turned on,,,,and now I didn't see any improve to the wifi strengh signal....It's sure that is on??

thanks for the reply!

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Alfa AWUS036NHA install on debian jessie

#8 Post by stevepusser »

Your internal atheros wifi card is assigned wlan0 and is what is being used. If you want to use the USB card, you'll have to find what interface it has been assigned, (ifconfig -a as root or with sudo, probably wlan1), and, if you're using wicd, you have to tell wicd in its Preferences what interface to use. It won't find them automatically, unlike network-manager.

Another way to find out the interface is just to plug it in and run dmesg in a terminal; you'll be able to see it load the firmware and get assigned an interface.
MX Linux packager and developer

User avatar
debiman
Posts: 3063
Joined: 2013-03-12 07:18

Re: Alfa AWUS036NHA install on debian jessie

#9 Post by debiman »

maybe op thinks that

Code: Select all

more wifi cards == more signal strength
???

dafunk
Posts: 43
Joined: 2014-12-04 07:48

[SOLVED ]Re: Alfa AWUS036NHA install on debian jessie

#10 Post by dafunk »

@stevepusser: thanks you!!!..selecting wlan1 in wicd solve the problem....too much dust for a simple solution... :oops:

Post Reply