Hi,
I install opensuse 11.0 on acer aspire9300 with amd turion 64x2 and with
wireless card Atheros AR5005G.

But, for some reasons, I can not connect to internet.

When I do iwconfig, I see SSID which is not the one which I put in the configuration from YaST.

By the way, I install the device driver picked up from madwifi.org and
do "modprobe ath_pci".

Thank you.

Hello,

What do you have with 'lspci -v'?

Have you seen http://en.opensuse.org/Atheros_madwifi?

The following info is from "lspci -v":


00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
Subsystem: Acer Incorporated [ALI] Device 0112
Flags: bus master, 66MHz, fast devsel, latency 0
Capabilities: [44] HyperTransport: Slave or Primary Interface
Capabilities: [e0] HyperTransport: MSI Mapping Enable+ Fixed-

00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
Subsystem: Acer Incorporated [ALI] Device 0112
Flags: 66MHz, fast devsel

00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
Subsystem: Acer Incorporated [ALI] Device 0112
Flags: 66MHz, fast devsel

00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
Subsystem: Acer Incorporated [ALI] Device 0112
Flags: 66MHz, fast devsel

00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
Subsystem: Acer Incorporated [ALI] Device 0112
Flags: bus master, 66MHz, fast devsel, latency 0

00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
Subsystem: Acer Incorporated [ALI] Device 0112
Flags: bus master, 66MHz, fast devsel, latency 0
Capabilities: [44] #00 [00fe]
Capabilities: [fc] #00 [0000]

00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
Subsystem: Acer Incorporated [ALI] Device 0112
Flags: 66MHz, fast devsel

00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
Subsystem: Acer Incorporated [ALI] Device 0112
Flags: 66MHz, fast devsel

00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Capabilities: [40] Subsystem: nVidia Corporation Device 0000
Capabilities: [48] Power Management version 2
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1 Enable-
Capabilities: [60] HyperTransport: MSI Mapping Enable+ Fixed-
Capabilities: [80] Express Root Port (Slot+), MSI 00
Capabilities: [100] Virtual Channel <?>
Kernel driver in use: pcieport-driver
Kernel modules: shpchp

00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 00004000-00004fff
Memory behind bridge: c4000000-c40fffff
Capabilities: [40] Subsystem: nVidia Corporation Device 0000

After read http://en.opensuse.org/Atheros_madwifi, I add ath5k to blacklist in /etc/modprobe.d/blacklist.
My kernel release is 2.6.25.5-1.1, but the madwifi release installed is _0.9.4_2.6.25_2-1. Will it be ok?

The output from iwconfig after rebooted as follows:

lo no wireless extensions.

eth0 no wireless extensions.

wifi0 no wireless extensions.

ath0 IEEE 802.11g ESSID:"linksys" Nickname:""
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
Bit Rate:1 Mb/s Tx-Power:9 dBm Sensitivity=1/1
Retryff RTS thrff Fragment thrff
Encryption keyff
Power Managementff
Link Quality=4/70 Signal level=-86 dBm Noise level=-90 dBm
Rx invalid nwid:9260 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


By the way, ESSID is not "linksys", either.

ESSID shown in iwconfig is not the one I configurated.

The madwifi release that I am using is _0.9.4_2.6.25_2-1, with the default My kernel release is 2.6.25.5-1.1.

You might want to try 'lspci -v -nn -d 168c:001c' to get more information on your wireless card.

The Atheros card for my laptop appeared as a AR242x, although it was really an AR5007EG. Moreover, the rpm's from MadWiFi didn't work, but the one from the suse repository did http://download.opensuse.org/reposit.../openSUSE_11.0, probably because it was a AR5007EG.

Also, KnetworkManager didn't work. I could see the networks, but it never allowed me to connect. So, I used ifup (in Yast) and then use KwifiManager. Suspend also works, although I have to manually restart the network after a suspend.

Kind regards

Thank you for your help.

I visit the website provided by you, but the nic in my laptop is Atheros AR2413 (AR5005G).

There is not output for "lspci -v -nn -d 168c:001c".

There is no issue when I install opensuse 10.2, but, for suse 11.0, I can not connect to my NIC.

Okay, I am not sure that I can help me much further.

The web page http://en.opensuse.org/HCL/Network_Adapters_(Wireless) lists Atheros AR2413A as compatible with madwifi on 10.3 x86_64. Is yours listed as with the "A?"

Atheros 5005G is listed twice stating that it needs a nongpl kernel package. (The AR5007EG also requires the nongpl kernel, I used the default and it worked for me.)

There are some comments at http://madwifi.org/wiki/Compatibilit...AtherosAR5005G regarding this card.
Maybe going over the page http://en.opensuse.org/Atheros_madwifi making sure that all is in order.
You might try looking at other distros to see how they configured the card.

Sorry I can't help more.

Thank you for your help.

You do provide me a lot of info.

Thank you again.

After did a lot of researchs, finally, I found out a solution to solve the issue which I had. I will provide a solution for whom wants.

Issue: I have AR5005G with AR2413 chip in my laptop.
"tail /var/log/messages" will show eth0: no link during initialization.

Solution:
In YaST,
1.click network devices and netsetting.
2. select global setting, in network setup method,
select tranditional method with ifup

since knetworkmanager doest not work at all.

You need to run ifup on termianl owned by root.

ifup ath0.

using iwconfig to check.



By the way, I need to say "thank you " to daveny who mentioned this in
his response, but, at that time, I did not understand at all.

After I made it worked, finally, I do understand daveny's response.

jshih,

It's great to hear that things are up and running! The issue of not being compatible with knetworkmanager caused me some grief for a while as well, until I discovered from others who mentioned this issue.

Have a great day!