Fedora Linux Support Community & Resources Center

Go Back   FedoraForum.org > Fedora 17/18 > Servers & Networking
FedoraForum Search

Forgot Password? Join Us!

Servers & Networking Discuss any Fedora server problems and Networking issues such as dhcp, IP numbers, wlan, modems, etc.

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 31st December 2010, 10:33 AM
AloneInTheDark Offline
Registered User
 
Join Date: Jul 2005
Posts: 39
linuxfedorafirefox
Atheros AR5001 NIC doesn't work on my eeepc

Hello all,
F13 on a EEEPC 1000HD.

I have big problems with my wireless card.
lspci says:

Code:
01.00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)

One problem is that I can't use Network Manager (it continue to ask me for the WPA password9.
So I stopped it and I use command line, following this:
http://home.roadrunner.com/~computer.../wireless.html

From the log I can see that it tried to associate to AP and after a lot of tries: it connects BUT the connection is really SLOW and UNSTABLE!
(pinging hosts on the same network gives me about 50% packets loss)

I am worried about this entry in the log:
Code:
ath5k phy0: unsupported jumbo
I am going to try to install madwifi, but before that I'd like to have your opinion and listen your experience!
I see a lot on infos about ath5k, but I'd like to be pointed to the right direction!

Thanks and have a good New Year!
Reply With Quote
  #2  
Old 31st December 2010, 10:36 AM
stevea's Avatar
stevea Offline
Registered User
 
Join Date: Apr 2006
Location: Ohio, USA
Posts: 8,346
linuxfedorafirefox
Re: Atheros AR5001 NIC doesn't work on my eeepc

There was some bug in F13 Networkmanager where it would continue to ask for passwd and fail. I believe it resolves once you get the connection entered in the gconf.

I wouldn't worry about jumbo packets msg. Non-issue.
__________________
None are more hopelessly enslaved than those who falsely believe they are free.
Johann Wolfgang von Goethe
Reply With Quote
  #3  
Old 31st December 2010, 10:50 AM
AloneInTheDark Offline
Registered User
 
Join Date: Jul 2005
Posts: 39
linuxfedorafirefox
Re: Atheros AR5001 NIC doesn't work on my eeepc

Thanks, but as I told, I get rid of NM and I used wpa_supplicant, ifconfig,iwlist...and the problem is still here!
So is not NM related.
Reply With Quote
  #4  
Old 31st December 2010, 10:58 AM
jakebpg Offline
Registered User
 
Join Date: Feb 2009
Location: Northeast
Posts: 292
linuxfedorafirefox
Re: Atheros AR5001 NIC doesn't work on my eeepc

Quote:
Originally Posted by AloneInTheDark View Post
Hello all,
F13 on a EEEPC 1000HD.

I have big problems with my wireless card.
lspci says:

Code:
01.00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)

One problem is that I can't use Network Manager (it continue to ask me for the WPA password9.
So I stopped it and I use command line, following this:
http://home.roadrunner.com/~computer.../wireless.html

From the log I can see that it tried to associate to AP and after a lot of tries: it connects BUT the connection is really SLOW and UNSTABLE!
(pinging hosts on the same network gives me about 50% packets loss)

I am worried about this entry in the log:
Code:
ath5k phy0: unsupported jumbo
I am going to try to install madwifi, but before that I'd like to have your opinion and listen your experience!
I see a lot on infos about ath5k, but I'd like to be pointed to the right direction!

Thanks and have a good New Year!
Sounds like you are using wpa supplicant. Turn this off. and use network manager. I have the exact same card as reported by lspci and have no problem at all.

Open a terminal and su - to root. Then type in system-config-network. delete any entry you see for the card save and exit. Then reboot and log back in. Open terminal again su - to root and type system-config-network, add the card back in by clicking on new, select wireless device and add the atherose card back in following all the prompts until finished. Click on file save. Then double click the entry and fill in all of you network settings and click save once again. Reboot and the card should be working. I found that using the provided link to network configuration does not work correctly even after entering the root password so invoke it from a root terminal login instead You also may even find that the card is not even listed in system-config-network when you first open the window through the terminal window and is the reason it does not work as expected.
You also may need to copy all files in /etc/sysconfig/networking/profiles/default to /etc/networkmanager/system-connections. Only do this if the latter folder is empty.

Good Luck.

Last edited by jakebpg; 31st December 2010 at 11:06 AM.
Reply With Quote
  #5  
Old 31st December 2010, 01:06 PM
AloneInTheDark Offline
Registered User
 
Join Date: Jul 2005
Posts: 39
linuxfedorafirefox
Re: Atheros AR5001 NIC doesn't work on my eeepc

Quote:
Originally Posted by jakebpg View Post
Sounds like you are using wpa supplicant. Turn this off. and use network manager.
Jake, this is no clear: how can I turn off wpa_suppl? Do you mean the service ? I did it!
But I see that NM calls the exe everytime! I think this is correct!


Open a terminal and su - to root. Then type in system-config-network. delete any entry you see for the card save and exit.
Did it!

You also may need to copy all files in /etc/sysconfig/networking/profiles/default to /etc/networkmanager/system-connections. Only do this if the latter folder is empty.

Indeed the dir was blank, so I copied every file!
The problem is still here: NM continues to ask me for the WPA password,but when it connects the connection in unusable!

I really don't know where to look!

This is the log:
Code:
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) starting connection 'Auto honeypot'
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> (wlan0): device state change: 3 -> 4 (reason 0)
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> (wlan0): bringing up device.
Dec 31 14:56:42 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0/wireless): access point 'Auto honeypot' has security, but secrets are required.
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> (wlan0): device state change: 5 -> 6 (reason 0)
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> (wlan0): device state change: 6 -> 4 (reason 0)
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0/wireless): connection 'Auto honeypot' has security, and secrets exist.  No new secrets needed.
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Config: added 'ssid' value 'honeypot'
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Config: added 'scan_ssid' value '1'
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Config: added 'psk' value '<omitted>'
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Config: set interface ap_scan to 1
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> (wlan0): supplicant connection state:  scanning -> disconnected
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> (wlan0): supplicant connection state:  disconnected -> scanning
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> (wlan0): supplicant connection state:  scanning -> associating
Dec 31 14:56:43 localhost kernel: ath5k phy0: unsupported jumbo
Dec 31 14:56:54 localhost kernel: ath5k phy0: unsupported jumbo
Dec 31 14:56:57 localhost NetworkManager[3444]: <warn> (wlan0): link timed out.
Dec 31 14:57:02 localhost NetworkManager[3444]: <info> (wlan0): supplicant connection state:  associating -> disconnected
Dec 31 14:57:02 localhost NetworkManager[3444]: <info> (wlan0): supplicant connection state:  disconnected -> scanning
Dec 31 14:57:03 localhost NetworkManager[3444]: <info> (wlan0): supplicant connection state:  scanning -> associating
Dec 31 14:57:07 localhost NetworkManager[3444]: <warn> Activation (wlan0/wireless): association took too long.
Dec 31 14:57:07 localhost NetworkManager[3444]: <info> (wlan0): device state change: 5 -> 6 (reason 0)
Dec 31 14:57:07 localhost NetworkManager[3444]: <warn> Activation (wlan0/wireless): asking for new secrets
Dec 31 14:57:07 localhost NetworkManager[3444]: <info> (wlan0): supplicant connection state:  associating -> disconnected
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> (wlan0): device state change: 6 -> 4 (reason 0)
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Activation (wlan0/wireless): connection 'Auto honeypot' has security, and secrets exist.  No new secrets needed.
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Config: added 'ssid' value 'honeypot'
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Config: added 'scan_ssid' value '1'
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Config: added 'psk' value '<omitted>'
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Config: set interface ap_scan to 1
Dec 31 14:57:10 localhost NetworkManager[3444]: <info> (wlan0): supplicant connection state:  disconnected -> associating
If I try by hand:
wpa.conf
Code:
network={
	ssid="honeypot"
	psk=f13c6506950c68fff3bff98753347a7a1cd387b11bc30b56c3051fbd04b06748
}

root@localhost ~]# wpa_supplicant -Dwext -iwlan0 -cwpa.conf
Code:
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
Trying to associate with e0:92:f7:61:37:2c (SSID='honeypot' freq=2437 MHz)
Associated with 00:00:00:00:00:00
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
Trying to associate with e0:92:f7:61:37:2c (SSID='honeypot' freq=2437 MHz)
Authentication with e0:91:f5:61:37:2c timed out.
Trying to associate with a2:05:43:5b:35:31 (SSID='honeypot' freq=2437 MHz)
Authentication with e0:91:f5:61:37:2c timed out.
Reply With Quote
  #6  
Old 31st December 2010, 02:32 PM
jakebpg Offline
Registered User
 
Join Date: Feb 2009
Location: Northeast
Posts: 292
linuxfedorafirefox
Re: Atheros AR5001 NIC doesn't work on my eeepc

Quote:
Originally Posted by AloneInTheDark View Post
I really don't know where to look!

This is the log:
Code:
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) starting connection 'Auto honeypot'
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> (wlan0): device state change: 3 -> 4 (reason 0)
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> (wlan0): bringing up device.
Dec 31 14:56:42 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0/wireless): access point 'Auto honeypot' has security, but secrets are required.
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> (wlan0): device state change: 5 -> 6 (reason 0)
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> (wlan0): device state change: 6 -> 4 (reason 0)
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0/wireless): connection 'Auto honeypot' has security, and secrets exist.  No new secrets needed.
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Config: added 'ssid' value 'honeypot'
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Config: added 'scan_ssid' value '1'
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Config: added 'psk' value '<omitted>'
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> Config: set interface ap_scan to 1
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> (wlan0): supplicant connection state:  scanning -> disconnected
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> (wlan0): supplicant connection state:  disconnected -> scanning
Dec 31 14:56:42 localhost NetworkManager[3444]: <info> (wlan0): supplicant connection state:  scanning -> associating
Dec 31 14:56:43 localhost kernel: ath5k phy0: unsupported jumbo
Dec 31 14:56:54 localhost kernel: ath5k phy0: unsupported jumbo
Dec 31 14:56:57 localhost NetworkManager[3444]: <warn> (wlan0): link timed out.
Dec 31 14:57:02 localhost NetworkManager[3444]: <info> (wlan0): supplicant connection state:  associating -> disconnected
Dec 31 14:57:02 localhost NetworkManager[3444]: <info> (wlan0): supplicant connection state:  disconnected -> scanning
Dec 31 14:57:03 localhost NetworkManager[3444]: <info> (wlan0): supplicant connection state:  scanning -> associating
Dec 31 14:57:07 localhost NetworkManager[3444]: <warn> Activation (wlan0/wireless): association took too long.
Dec 31 14:57:07 localhost NetworkManager[3444]: <info> (wlan0): device state change: 5 -> 6 (reason 0)
Dec 31 14:57:07 localhost NetworkManager[3444]: <warn> Activation (wlan0/wireless): asking for new secrets
Dec 31 14:57:07 localhost NetworkManager[3444]: <info> (wlan0): supplicant connection state:  associating -> disconnected
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> (wlan0): device state change: 6 -> 4 (reason 0)
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Activation (wlan0/wireless): connection 'Auto honeypot' has security, and secrets exist.  No new secrets needed.
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Config: added 'ssid' value 'honeypot'
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Config: added 'scan_ssid' value '1'
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Config: added 'psk' value '<omitted>'
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Dec 31 14:57:09 localhost NetworkManager[3444]: <info> Config: set interface ap_scan to 1
Dec 31 14:57:10 localhost NetworkManager[3444]: <info> (wlan0): supplicant connection state:  disconnected -> associating
If I try by hand:
wpa.conf
Code:
network={
	ssid="honeypot"
	psk=f13c6506950c68fff3bff98753347a7a1cd387b11bc30b56c3051fbd04b06748
}

root@localhost ~]# wpa_supplicant -Dwext -iwlan0 -cwpa.conf
Code:
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
Trying to associate with e0:92:f7:61:37:2c (SSID='honeypot' freq=2437 MHz)
Associated with 00:00:00:00:00:00
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
Trying to associate with e0:92:f7:61:37:2c (SSID='honeypot' freq=2437 MHz)
Authentication with e0:91:f5:61:37:2c timed out.
Trying to associate with a2:05:43:5b:35:31 (SSID='honeypot' freq=2437 MHz)
Authentication with e0:91:f5:61:37:2c timed out.
Ok, if the service is turned off, that's good as it causes problems with the athk5 driver since it is not a supported driver.

Yes you are correct in that network manager uses the wpa service but it does NOT need to be enabled in the services applet for the reason I mentioned above.
Here's a copy of my wpa_supplicant.conf file. Now keep in mind that I use WEP and not WPA but it will give you an idea of what the conf file should look like.
You will find the file in /etc/wpa_supplicant.

HTML Code:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel

network={
  ssid="linksys"
  key_mgmt=NONE
  # Keys in quotes are ASCII keys
  wep_key0="XXXXXXXXXX"
  # Keys specified without quotes are hex keys
  # wep_key1=0102030405
  # wep_key2="1234567890123"
  wep_tx_keyidx=0
  priority=5
}
Now this is what one looks like that I found on the net using wpa

HTML Code:
# allow frontend (e.g., wpa_cli) to be used by all users in 'wheel' group
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
#
# home network; allow all valid ciphers
network={

    ssid="home"

    scan_ssid=1

    key_mgmt=WPA-PSK

    psk="very secret passphrase" 
}
Now of course you will need to fill in your own info for ssid and psk.

Here's a link where the above example comes from for WPA use instead of WEP as I use.
http://linux.die.net/man/5/wpa_supplicant.conf

You can try this and see if it helps.

If I remember correctly if you do a locate wpa_supplicant in a terminal it will show you where all the current examples for wpa supplicant reside on your system which may be a better example since they are for the current version that is on your machine.

Also here is a copy of my wpa_supllicant file and it is located at /etc/sysconfig:


# Use the flag "-i" before each of your interfaces, like so:
# INTERFACES="-ieth1 -iwlan0"
INTERFACES="-iwlan0"

# Use the flag "-D" before each driver, like so:
# DRIVERS="-Dwext"
DRIVERS=""

# Other arguments
# -u Enable the D-Bus interface (required for use with NetworkManager)
# -f Log to /var/log/wpa_supplicant.log
# -P Write pid file to /var/run/wpa_supplicant.pid
# required to return proper codes by init scripts (e.g. double "start" action)
# -B to daemonize that has to be used together with -P is already in wpa_supplicant.init.d
OTHER_ARGS="-u -f /var/log/wpa_supplicant.log -P /var/run/wpa_supplicant.pid"

As you can see I do not specify a driver at all and only specify the interface of wlan0.

Hope this info helps. Oh and by the way this problem is not specific to just the atheros card.

Last edited by jakebpg; 31st December 2010 at 02:40 PM. Reason: added more info
Reply With Quote
  #7  
Old 1st January 2011, 09:32 AM
AloneInTheDark Offline
Registered User
 
Join Date: Jul 2005
Posts: 39
linuxfedorafirefox
Re: Atheros AR5001 NIC doesn't work on my eeepc

Jake, thanks a lot!
I spent a lot of time yesterday, but I discovered that I had a problem with the upgrade. (too much dupes rpms)!
As I resolved all the packages problem, everything worked!

Really, thanks and have a Good New Year!!
Reply With Quote
Reply

Tags
ar5001, atheros, eeepc, nic, work

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Asus eeePC 701 with Atheros AR242x PCI-E Adapter - can I install it as access point? Tiger22B Servers & Networking 0 4th September 2009 04:46 PM
Cannot get Atheros card to work Razorblade Hardware & Laptops 13 23rd September 2008 05:43 PM
Atheros + Madwifi + 2.6.25.11-97 on EeePC shywolf9982 Hardware & Laptops 0 26th July 2008 11:35 PM
Cannot get PCMCIA (atheros) wifi card to work zambizzi Servers & Networking 9 17th December 2007 03:12 PM
Making Madwifi and Atheros work living dissed Servers & Networking 6 27th March 2007 10:11 PM


Current GMT-time: 01:16 (Wednesday, 19-06-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat