Atheros AR5006EG

[manin]

Hallo guys I run FEDORA 8.
Μy laptop has Atheros AR5006EG wireless adapter. I can see it in network configuration, and with iwconfig i get:

[root@manin-laptop etc]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


The problem is that in network configuration is inactive, and I can't activate it.
What should I do?

[Brian1]

With it being wlan0 I am assuming you are using the ndiswrapper package?

Brian

[manin]

I just installed Fedora, it recognise my card from it's own

[ppesci]

You have problem connecting to access point.

Try to restart and check as root, the last entries in the file /var/log/messages with the command:

tail -n20 /var/log/messages

and put the output here. Put the output of the command:

lsmod

HTH

[manin]

[root@manin-laptop ~]# tail -n20 /var/log/messages
Jan 26 19:17:44 manin-laptop avahi-daemon[2473]: Registering HINFO record with values 'I686'/'LINUX'.
Jan 26 19:17:44 manin-laptop avahi-daemon[2473]: Server startup complete. Host name is manin-laptop.local. Local service cookie is 4244581110.
Jan 26 19:17:45 manin-laptop avahi-daemon[2473]: Service "manin-laptop" (/services/ssh.service) successfully established.
Jan 26 19:17:48 manin-laptop acpid: client connected from 2538[68:68]
Jan 26 19:17:48 manin-laptop acpid: 1 client rule loaded
Jan 26 19:17:53 manin-laptop pcscd: winscard.c:219:SCardConnect() Reader E-Gate 0 0 Not Found
Jan 26 19:17:53 manin-laptop pcscd:last message repeated 3 times
Jan 26 19:17:53 manin-laptop acpid: client connected from 2733[0:0]
Jan 26 19:17:53 manin-laptop acpid: 1 client rule loaded
Jan 26 19:17:55 manin-laptop kernel: [drm] Initialized drm 1.1.0 20060810
Jan 26 19:17:55 manin-laptop kernel: [drm] Initialized i915 1.6.0 20060119 on minor 0
Jan 26 19:18:19 manin-laptop gconfd (manin-2851): starting (version 2.20.1), pid 2851 user 'manin'
Jan 26 19:18:19 manin-laptop gconfd (manin-2851): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jan 26 19:18:19 manin-laptop gconfd (manin-2851): Resolved address "xml:readwrite:/home/manin/.gconf" to a writable configuration source at position 1
Jan 26 19:18:19 manin-laptop gconfd (manin-2851): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jan 26 19:18:20 manin-laptop pulseaudio[2859]: alsa-util.c: Cannot find mixer control "Master".
Jan 26 19:18:20 manin-laptop pulseaudio[2859]: alsa-util.c: Cannot find fallback mixer control "PCM".
Jan 26 19:18:22 manin-laptop gconfd (manin-2851): Resolved address "xml:readwrite:/home/manin/.gconf" to a writable configuration source at position 0
Jan 26 19:18:22 manin-laptop hcid[2310]: Default passkey agent (:1.15, /org/bluez/passkey) registered
Jan 26 19:18:22 manin-laptop hcid[2310]: Default authorization agent (:1.15, /org/bluez/auth) registered

[Brian1]

Still confused on the wlan0. It usually refers to ndiswrapper and the b43 modules.
Post output of the following commands.
/sbin/lspci -v
/sbin/lsmod
cat /etc/modprobe.conf

Brian

[manin]

04:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01)
Subsystem: Askey Computer Corp. Unknown device 7128
Flags: bus master, fast devsel, latency 0, IRQ 220
Memory at d8000000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 2
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+
Capabilities: [60] Express Legacy Endpoint IRQ 0
Capabilities: [90] MSI-X: Enable- Mask- TabSize=1

[manin]

[root@manin-laptop ~]# /sbin/lsmod
Module Size Used by
i915 23745 2
drm 67028 3 i915
rfcomm 36825 0
l2cap 25537 9 rfcomm
bluetooth 49316 4 rfcomm,l2cap
autofs4 20421 2
sunrpc 140765 1
nf_conntrack_ipv4 11717 12
ipt_REJECT 7617 2
iptable_filter 6465 1
ip_tables 14213 1 iptable_filter
nf_conntrack_ftp 10977 0
nf_conntrack_ipv6 18769 12
xt_state 6081 24
nf_conntrack 51977 4 nf_conntrack_ipv4,nf_conntrack_ftp,nf_conntrack_ip v6,xt_state
nfnetlink 8281 3 nf_conntrack_ipv4,nf_conntrack_ipv6,nf_conntrack
xt_tcpudp 6977 28
ip6t_ipv6header 6209 2
ip6t_REJECT 8257 2
ip6table_filter 6337 1
ip6_tables 15109 2 ip6t_ipv6header,ip6table_filter
x_tables 14277 7 ipt_REJECT,ip_tables,xt_state,xt_tcpudp,ip6t_ipv6h eader,ip6t_REJECT,ip6_tables
cpufreq_ondemand 10317 1
acpi_cpufreq 12365 1
loop 16581 0
dm_mirror 21697 0
dm_multipath 18249 0
dm_mod 46465 2 dm_mirror,dm_multipath
ipv6 245989 16 nf_conntrack_ipv6,ip6t_REJECT
snd_hda_intel 274657 2
snd_seq_dummy 6725 0
snd_seq_oss 29889 0
arc4 5953 2
ecb 6721 2
snd_seq_midi_event 9793 1 snd_seq_oss
snd_seq 44849 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
blkcipher 9029 1 ecb
snd_seq_device 10061 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 37569 0
snd_mixer_oss 16705 1 snd_pcm_oss
tifm_7xx1 9281 0
rc80211_simple 7361 1
snd_pcm 63685 2 snd_hda_intel,snd_pcm_oss
sdhci 17997 0
firewire_ohci 18113 0
tifm_core 11205 1 tifm_7xx1
firewire_core 36097 1 firewire_ohci
crc_itu_t 6081 1 firewire_core
mmc_core 27333 1 sdhci
snd_timer 20549 2 snd_seq,snd_pcm
video 19921 0
battery 14025 0
ac 8133 0
snd_page_alloc 11337 2 snd_hda_intel,snd_pcm
iTCO_wdt 13797 0
ath5k 85197 0
snd_hwdep 10309 1 snd_hda_intel
iTCO_vendor_support 7109 1 iTCO_wdt
output 6977 1 video
i2c_i801 12113 0
snd 43461 13 snd_hda_intel,snd_seq_oss,snd_seq,snd_seq_device,s nd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_hwd ep
button 10321 0
r8169 27589 0
mac80211 131409 2 rc80211_simple,ath5k
i2c_core 21825 1 i2c_i801
soundcore 9633 1 snd
joydev 11649 0
cfg80211 10441 1 mac80211
serio_raw 9029 0
sg 31965 0
sr_mod 17509 0
cdrom 33889 1 sr_mod
ata_generic 8901 0
ata_piix 16709 2
libata 99633 2 ata_generic,ata_piix
sd_mod 27329 3
scsi_mod 119757 4 sg,sr_mod,libata,sd_mod
ext3 110665 1
jbd 52457 1 ext3
mbcache 10177 1 ext3
uhci_hcd 23633 0
ohci_hcd 21445 0
ehci_hcd 31693 0

[manin]

I know that this is very tiring, and I appreciate this a lot.
Many many thanks

[root@manin-laptop ~]# cat /etc/modprobe.conf
alias eth0 r8169
alias scsi_hostadapter libata
alias scsi_hostadapter1 ata_piix
alias wlan0 ath5k
alias snd-card-0 snd-hda-intel
options snd-card-0 index=0
options snd-hda-intel index=0

[CraigWatson]

Try adding the Network Manager panel applet to your startup:

System --> Preferences --> Personal --> Sessions --> Add

Name: Network Manager
Command: nm-applet

If the card is detected, nm-applet should pick it up and give you a list of network choices.

[Brian1]

I have not got into the new ath5k modules. use to using madwifi for atheros based nics. But the chipset version as far as I know is not supported in the stable madwifi release. But I believe it is supported if you get the latest cvs version of madwifi. Read abut this somewhere on madwifi site. I would give that a start to see if ath5k is right or maybe the latest madwifi from cvs is better. If neither support then look into ndiswrapper.

Brian

[johnnymack]

brian,

reason for your confusion about "wlan" and "ndiswrapper" is that when using <madwifi> for an Atheros chipset driver, it names device to "athX" and when using new <ath5k> driver present in F8, it names the Atheros device "wlanX'.

jm

[nyjetshead]

Ath5k doesn't support this chipset.

I agree with Brian1
Madwifi with some patching:
Watch out... yum updates can undo your work if the fix isn't in the update.
or
NDISwrapper with the windows driver.
Be care here, 4K stack issue with Fedora kernels, its not as simple as "load and go".
Check this forum, google and the ndiswraper site.

[johnnymack]

manin,

OK, I see a problem with your "iwconfig" output: you have no essid set. You must set the essid and channel before you can associate with an A/P which has those same settings. Have you done this setup [using cmd "neat" maybe] before trying?

I'll try and walk you thru a manual setup. Lets assume you wish to call your A/P "manin08". and you wish to use channel 1. And, I assume, that you also wish to use DHCP to have an IP address automagically assigned to your laptop.

here is how I would get that set of choices working:

ifconfig wlan0 up
iwconfig wlan0 essid "manin08" channel 1
echo add a wpa_supplicant cmdline here is you're encrypted w/ WEP or WPA
dhclient wlan0
ifconfig wlan0

If there was no IP address assigned to wlan0, it is highly possible that <dhclient> was unable to talk to your A/P because the driver "ath5k" was unable to talk to your Atheros AR5006 chip. This would be because the "ath5k" driver is still Beta and does not recognize all chipsets yet; it is a work in progress. If this is the case, then you are going to have to get the "madwifi" driver installed and retry these steps [assuming that NM doesn't do them automagically]. Note however, that if you do install madwifi, that the device name will change from "wlan0" to "ath0".

BUT.. if that set of commands worked, you should have been assigned an IP address. So, now the only thing which remains, is to setup your default route.. and then you should be ready. The <dhclient> will save the default route IP address in the leases file. That file is usually here: /var/lib/dhclient/dhclient.leases and can be found in the line beginning with routers:

The data can be extracted with perl or gawk or whatever.. I use gawk like so:

GW=`gawk '$2~/routers/{semi=split($3,gw,";");print gw[1]}' /var/lib/dhclient/dhclient.leases | tail -1`
route add default gw ${GW}

HTH,

jm

[scottro]

For what it's worth

http://home.nyc.rr.com/computertaijutsu/rhwireless.html

There's a section towards the end on dealing with the 5007EG. There's a good chance that you have it, rather than the 5006 that lscpci says you have. (The 5007EG is sort of a ninja chipset, it travels in disguise.)

There's a few ways to tell. If there's a sticker on the bottom saying AR5BXB63 then the 5007EG is what you have and the link I gave may help.

[aprilian bandit]

For what it's worth

http://home.nyc.rr.com/computertaijutsu/rhwireless.html

There's a section towards the end on dealing with the 5007EG.

You sir, are a star :)

[CraigWatson]

A friend was having pretty much the same problem with ER5006EG - it was actually a 007EG chipset that was being wrongly identified as the 006EG.

Support for the 007EG isn't integrated into the main MadWifi installation packages, but there's a ticket open (http://madwifi.org/ticket/1679) on the MadWifi wiki which gives patching instructions. You can either do the patch yourself or download a pre-patched (http://snapshots.madwifi.org/special/madwifi-ng-r2756+ar5007.tar.gz) version - although for completeness I got my friend to do a manual patch.

Hope this helps a bit.

That's the

[Dangermouse]

Hi if its any help AR5007 is included in the script here
http://forums.fedoraforum.org/forum/showthread.php?t=171660

[scottro]

@aprilian_bandit

On that page is a link to an article by a fellow named Mike, about using wpa_supplicant. When I asked for permission to post the link, he said something to the effect he would be happy if I did. His purpose was to help others avoid all the aggravation he went through trying to get it to work. I feel the same way about the AR5007EG section--I'm delighted that it helps others avoid all the googling and false starts I went through.

[johnnymack]

Hey manin,

no word from you in 2+ weeks.. have you fixed your problem or just moved on?

I was just surfing tonight at one of the linux-wireless forums. AS "nyjetshead" said, ath5k doesn't yet support the AR5006/7 chipsets. But they are working on it, and have been making progress. So, the only path for you ATM is ndiswrapper, FWIW.

jm

[defigo]

manin,

Follow either scottro or dangermouses' posts. They should solve your problem. Chances are you have the AR5007EG rather than the 5006. The best way to check is using windows (if its installed - device manager) or under the actual machine - Atheros - AR5BXB63 will be the 5007. Either way, both scottro and dangermouse have scripts, explanations for madwifi drivers with both the 5006 and 5007 sets. Remember this is for a 32 bit machine. Good luck.

[dhimes]

Still only supported on the x386 architecture, no? Last I saw we were still waiting for the x_64 support. (No wonder Starbucks is in trouble.)

[scottro]

It seems so. The other day, I threw a 64 bit Ubuntu on it, because I was curious if core duo does, in fact support 64 bit. I did some googling--someone on a Mepis forum apparently had success installing the MadWifi stuff on a 64 bit machine, but I didn't. I couldn't get ndiswrapper to work either, with 64 or 32 bit drivers--it would scan the network, but wouldn't connect to anything.

[dhimes]

Dang. I'm really enjoying fedora and the linux experience--wifi would be a nice option (but at this point it's not necessary). I suppose if it was crucial I could purchase a card that worked...there must be a list somewhere.

[johnnymack]

OK, I just found this posting which sez that the Atheros A5006EG is supported using the madwifi tarball and a patch from the madwifi website. I haven't tried this but trust the posters expertise.

http://tchung.fedorapeople.org/madwifi/ar2425/howto.txt

[dhimes]

That refers to ticket 1679--I think that it's only for i386...