Hardware Support: AR5007* (AR2425 chips)

I just tried the branch madwifi-hal-0.9.30.10, still get HAL status 13

I just tried branch/madwifi-hal-0.9.30.13, still get HAL status 13

Has it ever worked?

Replying to anonymous:

subversion r2318 still not working :(

Please stop this.

From what I can tell at this time, a new HAL might be necessary before AR5007 chipsets are supported (but this has yet to be confirmed by the HAL supplier). In other words: unless you see a new HAL committed to the repository (either in trunk or one of the branches), you tried this new HAL and still had no success, you don't need to tell us that any other change doesn't work.

HAL?

Replying to mike nillon:

I would know if there are some prevision for a futurer suport for this device on madwifi? thanks.

I don't think so... but recently I compiled the latest svn version of the madwifi-old-openhal branch. And surprisingly my ar2425 showed up as ath0, but when i tried to bring the interface up. My kernel started spitting outs errors. I'll post my dmesg output when I get home from work.

Can anyone else confirm this?

Replying to jose:

No, i have tried with openhal and the only thig that happens is the interface ath0 in te iwconfig list but no way to work =/. Actualy i'm wainting in hope of a new Hal with the support for this card. I need linux in my Notebook to work and the wifi driver is a big limitation for me.

same here. with openhal i have a wifi interface, but no connection possible. now i changed from 64bit to 32bit and installed the ndiswrapper with the windows xp 32bit driver. it works well - but it is only a workaround :( there are no windows xp 64bit driver for the ar2425 so i have to work with 32bit and wait for a new hal version ...

Good News! Recentily I've recevied an email from Sam Leffer in response for a question about the support for this chipset. In the e-mail he says "it's comming".

Replying to andre:

Recentily I've recevied an email from Sam Leffer in response for a question about the support for this chipset. In the e-mail he says "it's comming".

Thanks for the information.

Suport for AR2425 chipset it very soon?

In a discussion forum Sam Leffler The HAL developer said this:

"Support for the 2425 parts is in test and should happen soonish. With luck support for that will come with a new hal release as opposed to the test drops I've made that have all had issues making them unsuitable for general use.

Sam"

answering a question about hal support for a device.

I'm brazilian and english is not a common language here, but it seens that 2425 it's the chipset AR2425 (AR5007EG), or not?

Well, any news about this I'll post here. =D

it seens that 2425 it's the chipset AR2425 (AR5007EG), or not?

that is right! Do you have a link to the post?

greets grashalm

Replying to grashalm:

it seens that 2425 it's the chipset AR2425 (AR5007EG), or not?

that is right! Do you have a link to the post? greets grashalm

Replying to grashalm:

it seens that 2425 it's the chipset AR2425 (AR5007EG), or not?

that is right! Do you have a link to the post? greets grashalm

Yes : www.nabble.com/Atheros-AR5008E-3NX-chip-tf4057571.html#a11551164

Any "me too!" comments on this ticket will be summarily deleted. Please restrain yourselves to adding new and relevant information.

When a new HAL appears that supports this, it will be integrated at the normal rate.

I don't understand how I can be any more clear... When there is a new HAL, we will update MadWiFi to use it...

Bumping tickets won't make us fix them more quickly. The reason that they haven't been fixed, is because we don't know how to yet, or we haven't had time to yet. Bumping the tickets is likely to just annoy us. If we are not moving fast enough for you, then well-conceived and implemented patches are welcome, and are likely to be integrated quickly.

I would encourage any documentation and collected support information for getting cards working using NDISwrapper to be put on a relevant page on the wiki, not in the bug/task tracking system for the driver.

just out of curiosity how do you force a module onto a pci id?

I have Atheros AR5007EG (AR5BXB63) card in my Acer Aspire 3680. This is error that I got:-

Aug 19 08:03:49 computer kernel: ath_hal: module license 'Proprietary' taints kernel.
Aug 19 08:03:49 computer kernel: ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
Aug 19 08:03:49 computer kernel: wlan: 0.8.4.2 (0.9.3.1)
Aug 19 08:03:49 computer kernel: ath_pci: 0.9.4.5 (0.9.3.1)
Aug 19 08:03:49 computer kernel: PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
Aug 19 08:03:49 computer kernel: ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
Aug 19 08:03:49 computer kernel: wifi%d: unable to attach hardware: 'Hardware revision not supported' (HAL status 13)
Aug 19 08:03:49 computer kernel: ACPI: PCI interrupt for device 0000:03:00.0 disabled

lspci -v:

03:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01)
        Subsystem: AMBIT Microsystem Corp. Unknown device 0428
        Flags: bus master, fast devsel, latency 0, IRQ 17
        Memory at 6c100000 (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
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel

Thanks.

read the thread all of us are waiting for a new HAL version... if you are really desperate and can't wait you can use ndiswrapper (version 1.45+)

Can someone please run ath_info (trunk/tools/ath_info.c) on this card (after loading madwifi-old-openhal) and post the output ???

Replying to mickflemm:

Can someone please run ath_info (trunk/tools/ath_info.c) on this card (after loading madwifi-old-openhal) and post the output ???

Here is mine... I am running Ubuntu 7.10 (gusty) kernel 2.6.22-10 After loading openhal Dmesg:

[ 40.220151] ath_pci: 0.9.5.0-BSD (EXPERIMENTAL)

[ 40.220220] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16

[ 40.220231] PCI: Setting latency timer of device 0000:02:00.0 to 64

[ 40.260064] ath_hal: Atheros HW found

[ 40.260067] ath_hal: MAC version: 5213

[ 40.260069] ath_hal: PHY version: 5110

[ 40.260071] ath_hal: EEPROM version: 5.3

[ 40.260529] Build date: Sep 4 2007

[ 40.260531] Debugging version (IEEE80211)

[ 40.260534] ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps

[ 40.260544] ath0: H/W encryption support: WEP

[ 40.260548] ath0: mac 14.2 phy 7.0 radio 0.0

[ 40.260551] ath0: Use hw queue 1 for WME_AC_BE traffic

[ 40.260554] ath0: Use hw queue 0 for WME_AC_BK traffic

[ 40.260557] ath0: Use hw queue 2 for WME_AC_VI traffic

[ 40.260559] ath0: Use hw queue 3 for WME_AC_VO traffic

[ 40.260562] ath0: Use hw queue 6 for CAB traffic

[ 40.260564] ath0: Use hw queue 7 for beacons

[ 40.260566] Debugging version (ATH)

[ 40.260569] ath0: AR5212: mem=0x8c000000, irq=16

I think I am doing this wrong but... after compiling and running ath_info in the trunk i do

sudo ./ath_info 00:19:7D:F2:EC:XX <- my card's mac address... right?

i get...

Unable to read EEPROM Magic value !

Replying to anonymous:

Replying to mickflemm:

Can someone please run ath_info (trunk/tools/ath_info.c) on this card (after loading madwifi-old-openhal) and post the output ???

Here is mine... I am running Ubuntu 7.10 (gusty) kernel 2.6.22-10 After loading openhal Dmesg: [ 40.220151] ath_pci: 0.9.5.0-BSD (EXPERIMENTAL) [ 40.220220] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16 [ 40.220231] PCI: Setting latency timer of device 0000:02:00.0 to 64 [ 40.260064] ath_hal: Atheros HW found [ 40.260067] ath_hal: MAC version: 5213 [ 40.260069] ath_hal: PHY version: 5110 [ 40.260071] ath_hal: EEPROM version: 5.3 [ 40.260529] Build date: Sep 4 2007 [ 40.260531] Debugging version (IEEE80211) [ 40.260534] ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps [ 40.260544] ath0: H/W encryption support: WEP [ 40.260548] ath0: mac 14.2 phy 7.0 radio 0.0 [ 40.260551] ath0: Use hw queue 1 for WME_AC_BE traffic [ 40.260554] ath0: Use hw queue 0 for WME_AC_BK traffic [ 40.260557] ath0: Use hw queue 2 for WME_AC_VI traffic [ 40.260559] ath0: Use hw queue 3 for WME_AC_VO traffic [ 40.260562] ath0: Use hw queue 6 for CAB traffic [ 40.260564] ath0: Use hw queue 7 for beacons [ 40.260566] Debugging version (ATH) [ 40.260569] ath0: AR5212: mem=0x8c000000, irq=16 I think I am doing this wrong but... after compiling and running ath_info in the trunk i do sudo ./ath_info 00:19:7D:F2:EC:XX <- my card's mac address... right? i get... Unable to read EEPROM Magic value !

Oh shoot I am sorry... I should have read the source file first here is what i get now...

sudo ./ath_info 0x8c000000 Invalid EEPROM Magic number !

Ubuntu 7.10 kernel 2.6.22-10 svn r2704

[320509.396117] ath_hal: OpenHAL loaded (AR5210, AR5211, AR5212, RF5110/1/2)
[320509.401359] wlan: 0.8.6.0 (EXPERIMENTAL)
[320509.402582] ath_rate_sample: 1.2
[320509.407365] ath_pci: 0.9.5.0-BSD (EXPERIMENTAL)
[320509.407614] ACPI: PCI Interrupt 0000:07:00.0[A] -> GSI 17 (level, low) -> IRQ 17
[320509.407626] PCI: Setting latency timer of device 0000:07:00.0 to 64
[320509.407648] ath_hal: Device not supported (0xffffffff)
[320509.407652] ath_attach: unable to attach hardware: 'Hardware revision not supported' (HAL status 8)
[320509.407665] ACPI: PCI interrupt for device 0000:07:00.0 disabled

sudo lspci -vv
07:00.0 Ethernet controller: Atheros Communications, Inc. Unknown device 001c (rev 01)
        Subsystem: ABIT Computer Corp. Unknown device 1033
        Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin A routed to IRQ 17
        Region 0: Memory at fd6f0000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [40] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
                Address: 00000000  Data: 0000
        Capabilities: [60] Express Legacy Endpoint IRQ 0
                Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
                Device: Latency L0s <512ns, L1 <64us
                Device: AtnBtn- AtnInd- PwrInd-
                Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
                Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
                Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
                Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 0
                Link: Latency L0s <512ns, L1 <64us
                Link: ASPM Disabled RCB 128 bytes CommClk- ExtSynch-
                Link: Speed 2.5Gb/s, Width x1
        Capabilities: [90] MSI-X: Enable- Mask- TabSize=1
                Vector table: BAR=0 offset=00000000
                PBA: BAR=0 offset=00000000

sudo ./ath_info 0xfd6f0000
Unable to read EEPROM Magic value !

Replying to anonymous:

You do a great job, but Atheros does not deserve our money or your effort unless they provide for timely HAL updates.

HAL updates are not delivered by Atheros, but by Sam Leffler. So Atheros is not to blame in this case.

Replying to mrenzmann:

HAL updates are not delivered by Atheros, but by Sam Leffler. So Atheros is not to blame in this case.

but for lack of official Linux support they are to blame.

Regardless of who is responsible for the lack of support, is there any way we can speed up the process?

Though I do understand that these things take time, it pains me to continue using Windows on a daily basis just because my Atheros chipset remains unsupported..

Replying to smoobs:

Regardless of who is responsible for the lack of support, is there any way we can speed up the process?

It won't make sense to push Sam for AR5007 support in his HAL, as he said he's already working on it. He is known to be a busy person, mostly because of the fact he's self-employed. Pushing him likely annoys him, but does not help AR5007 support to occur earlier.

A better option would be to test madwifi-old-openhal and/or ath5k with your card and report the results back. The output of ath_info will also be helpful. This will help to make AR5007 support happen inside the OpenHAL (assuming that AR5007 is similar to the other Atheros chipsets).

but ath_info doesn't even work with this card...

Replying to anonymous:

but ath_info doesn't even work with this card...

Details, please. Did you try the latest version of ath_info (r2706)? What problems did you spot exactly?

Ubuntu 7.10 kernel 2.6.22-11 svn r2706

sudo lspci -v
07:00.0 Ethernet controller: Atheros Communications, Inc. Unknown device 001c (rev 01)
        Subsystem: ABIT Computer Corp. Unknown device 1033
        Flags: fast devsel, IRQ 17
        Memory at fd6f0000 (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

sudo ./ath_info 0xfd6f0000
Unable to read EEPROM Magic value !

perhaps I'm making a mistake?

Replying to anonymous:

perhaps I'm making a mistake?

If the driver modules are not loaded (or if they are not able to initialize the card, which would be the case here) you need to enable the card with setpci first (as explained in the ath_info manpage). In your case that command is:

setpci -s 07:00.0 command=0x41f cache_line_size=0x10

Please try and give a short feedback.

@mrenzmann,

Point taken. As a relative newbie I'm anxious to help as much as I can, but I can't figure out how to compile or install ath_info. If you can help me out there I'll be happy to post the results.

Otherwise, I'll just assume I should leave this stuff to the techies.

Replying to smoobs:

@mrenzmann, Point taken. As a relative newbie I'm anxious to help as much as I can, but I can't figure out how to compile or install ath_info. If you can help me out there I'll be happy to post the results. Otherwise, I'll just assume I should leave this stuff to the techies.

same result

sudo setpci -s 07:00.0 command=0x41f cache_line_size=0x10
sudo ./ath_info 0xfd6f0000
Unable to read EEPROM Magic value !

Replying to mrenzmann:

Replying to anonymous:

perhaps I'm making a mistake?

If the driver modules are not loaded (or if they are not able to initialize the card, which would be the case here) you need to enable the card with setpci first (as explained in the ath_info manpage). In your case that command is: {{{ setpci -s 07:00.0 command=0x41f cache_line_size=0x10 }}} Please try and give a short feedback.

Fedora 7 2.6.22.4-65.fc7 - r2706

ath_hal: OpenHAL loaded (AR5210, AR5211, AR5212, RF5110/1/2)
wlan: 0.8.6.0 (EXPERIMENTAL)
ath_rate_sample: 1.2
ath_pci: 0.9.5.0-BSD (EXPERIMENTAL)
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:03:00.0 to 64
ath_hal: Device not supported (0xe2)
ath_attach: unable to attach hardware: 'Hardware revision not supported' (HAL status 8)
ACPI: PCI interrupt for device 0000:03:00.0 disabled

lspci -v

03:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01)
        Subsystem: AMBIT Microsystem Corp. Unknown device 0428
        Flags: bus master, fast devsel, latency 0, IRQ 17
        Memory at 6c100000 (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
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel

./ath_info 0x6c100000

[root@izwan-computer tools]# ./ath_info 0x6c100000
Invalid EEPROM Magic number !

For me is the same:

Debian Sid 2.6.23-rc5 - svn 2706 (madwifi-ng not openhal)

lspci -v

05:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01)
	Subsystem: AMBIT Microsystem Corp. Unknown device 0428
	Flags: fast devsel, IRQ 18
	Memory at d0100000 (64-bit, non-prefetchable) [disabled] [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
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Virtual Channel

dmseg:

ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.30.13 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133)
wlan: 0.8.4.2 (0.9.4)
ath_pci: 0.9.4.5 (0.9.4)
ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:05:00.0 to 64
ath_attach: devid 0x1c
MadWifi: unable to attach hardware: 'Hardware revision not supported' (HAL status 13)
ACPI: PCI interrupt for device 0000:05:00.0 disabled

./ath_info 0xd0100000

Unable to read EEPROM Magic value !

Tried also with openhal... same result. Thanks for your work.

Replying to Marco:

Memory at d0100000 (64-bit, non-prefetchable) [disabled] [size=64K]

Looks like you did not enable the device with setpci as explained above.

Hello ppl, i updated ath_info, plz try again (ignore phy revision for now, i don't know it yet so it'll print the last name on the list instead of the normal name -hopefully after your feedback we'll learn the phy revision as well-).

Whoo Hoo!!!

Got some different output running sudo ./ath_info 0x8c000000

Warning: Invalid EEPROM Magic number !
 -==Device Information==-
MAC Version:  2425 (0xe0)
MAC Revision: 2425 (0xe2)
PHY Revision: 5110 (0x0)
 -==EEPROM Information==-
EEPROM Version:     5.3
EEPROM Size:        4K
Regulatory Domain:  0x65
 -==== Capabilities ====-
|  802.11a Support: no   |
|  802.11b Support: no   |
|  802.11g Support: yes  |
|  RFKill  Support: yes  |
|  32KHz   Crystal: no   |
 ========================
GPIO registers: CR 00000000 DO 300000000 DI e200000003

Fedora 7

[root@izwan-computer ~]# ./ath_info 0x6c100000
Warning: Invalid EEPROM Magic number !
 -==Device Information==-
MAC Version:  2425 (0xe0) 
MAC Revision: 2425 (0xe2) 
PHY Revision: 5110 (0x0) 
 -==EEPROM Information==-
EEPROM Version:     5.3 
EEPROM Size:        4K
Regulatory Domain:  0x65 
 -==== Capabilities ====-
|  802.11a Support: no   |
|  802.11b Support: no   |
|  802.11g Support: yes  |
|  RFKill  Support: yes  |
|  32KHz   Crystal: no   |
 ========================
GPIO registers: CR 00008000 DO 00000000 DI 0000000b

ubuntu 7.10 kernel 2.6.22-11 svn r2707

lspci -vv
07:00.0 Ethernet controller: Atheros Communications, Inc. Unknown device 001c (rev 01)
        Subsystem: ABIT Computer Corp. Unknown device 1033
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 17
        Region 0: Memory at fd6f0000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [40] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
                Address: 00000000  Data: 0000
        Capabilities: [60] Express Legacy Endpoint IRQ 0
                Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
                Device: Latency L0s <512ns, L1 <64us
                Device: AtnBtn- AtnInd- PwrInd-
                Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
                Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
                Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
                Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 0
                Link: Latency L0s <512ns, L1 <64us
                Link: ASPM Disabled RCB 128 bytes CommClk- ExtSynch-
                Link: Speed 2.5Gb/s, Width x1
        Capabilities: [90] MSI-X: Enable- Mask- TabSize=1
                Vector table: BAR=0 offset=00000000
                PBA: BAR=0 offset=00000000

sudo setpci -s 07:00.0 command=0x41f cache_line_size=0x10

sudo ath_info 0xfd6f0000
Unable to read EEPROM Magic value !

I'm obviously missing something here... anyone can point me to my mistake?

02:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01)
        Subsystem: AMBIT Microsystem Corp. Unknown device 0428
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at 8c100000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [40] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
                Address: 00000000  Data: 0000
        Capabilities: [60] Express Legacy Endpoint IRQ 0
                Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
                Device: Latency L0s <512ns, L1 <64us
                Device: AtnBtn- AtnInd- PwrInd-
                Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
                Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
                Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
                Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 0
                Link: Latency L0s <512ns, L1 <64us
                Link: ASPM Disabled RCB 128 bytes CommClk+ ExtSynch-
                Link: Speed 2.5Gb/s, Width x1
        Capabilities: [90] MSI-X: Enable- Mask- TabSize=1
                Vector table: BAR=0 offset=00000000
                PBA: BAR=0 offset=00000000
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel

# ./ath_info 0x8c100000
Warning: Invalid EEPROM Magic number !
 -==Device Information==-
MAC Version:  2425 (0xe0) 
MAC Revision: 2425 (0xe2) 
PHY Revision: 5110 (0x0) 
 -==EEPROM Information==-
EEPROM Version:     5.3 
EEPROM Size:        4K
Regulatory Domain:  0x65 
 -==== Capabilities ====-
|  802.11a Support: no   |
|  802.11b Support: no   |
|  802.11g Support: yes  |
|  RFKill  Support: yes  |
|  32KHz   Crystal: no   |
 ========================
GPIO registers: CR 00000000 DO 00000000 DI 0000000a

I tried again vith ath_info from svn r2707. lspci -v: (This thime with setpci -s 05:00.0 command=0x41f cache_line_size=0x10)

05:00.0 Ethernet controller: Atheros Communications, Inc. Unknown device 001c (rev 01)
	Subsystem: AMBIT Microsystem Corp. Unknown device 0428
	Flags: bus master, fast devsel, latency 0, IRQ 18
	Memory at d0100000 (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
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Virtual Channel

But the result is always:

Unable to read EEPROM Magic value !

Perhaps I did something wrong....

Last thing is strange, because anonymous with same hardware, i think (Subsystem: AMBIT Microsystem Corp. Unknown device 0428) succeded in obtaining ath_info.

The only thing different from a diff of lspci --vv are (bolded):

---

anonymous:

Control: I/O+ Mem+ BusMaster?+ SpecCycle?- MemWINV- VGASnoop- ParErr?- Stepping- SERR- FastB2B-

Flags: PMEClk- DSI- D1- D2- AuxCurrent?=375mA PME(D0-,D1-,D2-,D3hot+,D3cold-)

---

mine:

Control: I/O+ Mem+ BusMaster?+ SpecCycle?- MemWINV- VGASnoop- ParErr?- Stepping- SERR+ FastB2B-

Flags: PMEClk- DSI- D1- D2- AuxCurrent?=375mA PME(D0-,D1-,D2-,D3hot-,D3cold-)

Only my 2 cents.

ubuntu 7.10 kernel 2.6.22-11 svn r2709

sudo setpci -s 07:00.0 command=0x41f cache_line_size=0x10

07:00.0 Ethernet controller: Atheros Communications, Inc. Unknown device 001c (rev 01)
        Subsystem: ABIT Computer Corp. Unknown device 1033
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 17
        Region 0: Memory at fd6f0000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [40] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
                Address: 00000000  Data: 0000
        Capabilities: [60] Express Legacy Endpoint IRQ 0
                Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
                Device: Latency L0s <512ns, L1 <64us
                Device: AtnBtn- AtnInd- PwrInd-
                Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
                Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
                Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
                Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 0
                Link: Latency L0s <512ns, L1 <64us
                Link: ASPM Disabled RCB 128 bytes CommClk- ExtSynch-
                Link: Speed 2.5Gb/s, Width x1
        Capabilities: [90] MSI-X: Enable- Mask- TabSize=1
                Vector table: BAR=0 offset=00000000
                PBA: BAR=0 offset=00000000

sudo ./ath_info 0xfd6f0000
Unable to read EEPROM Magic value !

help?

ubuntu 7.10 kernel 2.6.22-11 svn r2709

ath_info fd6f0000
Warning: Invalid EEPROM Magic number !
 -==Device Information==-
MAC Version:  5210 (0x0) 
MAC Revision: 5210 (0x0) 
5Ghz PHY Revision: 5110 (0x9) 
2Ghz PHY Revision: 5110 (0x9) 
 -==EEPROM Information==-
EEPROM Version:     5.c63 
EEPROM Size:        4K
Regulatory Domain:  0x5C63 
 -==== Capabilities ====-
|  802.11a Support: yes  |
|  802.11b Support: yes  |
|  802.11g Support: no   |
|  RFKill  Support: yes  |
|  32KHz   Crystal: yes  |
 ========================
GPIO registers: CR 00000000 DO 00000000 DI 00000000

got it ;)

Replying to roadkill:

ubuntu 7.10 kernel 2.6.22-11 svn r2709 {{{ ath_info fd6f0000 Warning: Invalid EEPROM Magic number ! -==Device Information==- MAC Version: 5210 (0x0) MAC Revision: 5210 (0x0) 5Ghz PHY Revision: 5110 (0x9) 2Ghz PHY Revision: 5110 (0x9) -==EEPROM Information==- EEPROM Version: 5.c63 EEPROM Size: 4K Regulatory Domain: 0x5C63 -==== Capabilities ====- | 802.11a Support: yes | | 802.11b Support: yes | | 802.11g Support: no | | RFKill Support: yes | | 32KHz Crystal: yes | ======================== GPIO registers: CR 00000000 DO 00000000 DI 00000000 }}} got it ;)

it looks like a different card

ubuntu 7.10 kernel 2.6.22-11 svn r2712

sudo setpci -s 07:00.0 command=0x41f cache_line_size=0x10

07:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01)
        Subsystem: ABIT Computer Corp. Unknown device 1033
        Flags: fast devsel, IRQ 17
        Memory at fd6f0000 (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

sudo ./ath_info fd6f0000
Unable to read EEPROM Magic value !

sudo ./ath_info 0xfd6f0000
Unable to read EEPROM Magic value !

Looks like last changes have broken ath_info for me ...

Fedora 7 - r2712

Warning: Invalid EEPROM Magic number !
 -==Device Information==-
MAC Version:  2425 (0xe0) 
MAC Revision: 2425 (0xe2) 
PHY Revision: 5110 (0x0) 
 -==EEPROM Information==-
EEPROM Version:     5.3 
EEPROM Size:        4K
Regulatory Domain:  0x65 
 -==== Capabilities ====-
|  802.11a Support: no   |
|  802.11b Support: no   |
|  802.11g Support: yes  |
|  RFKill  Support: yes  |
|  32KHz   Crystal: no   |
 ========================
GPIO registers: CR 00000000 DO 00000000 DI 0000000b

sudo lspci -v

07:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01)
        Subsystem: ABIT Computer Corp. Unknown device 1033
        Flags: fast devsel, IRQ 17
        Memory at fd6f0000 (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

sudo ./ath_info fd6f0000

Warning: Invalid EEPROM Magic number !
 -==Device Information==-
MAC Version:  5210 (0x0) 
MAC Revision: 5210 (0x0) 
PHY Revision: 5110 (0x9) 
 -==EEPROM Information==-
EEPROM Version:     1.62 
EEPROM Size:        4K
Regulatory Domain:  0x1062 
 -==== Capabilities ====-
|  802.11a Support: no   |
|  802.11b Support: yes  |
|  802.11g Support: no   |
|  RFKill  Support: no   |
 ========================
GPIO registers: CR 00000000 DO 00000000 DI 00000000

I did absolutely nothing different I don't get it...

I didn't managed to make it work either, Gullible would it be possible to post a log/dmesg so we could see what have we done diffrently?

i have only manage for now to bring device UP ..

[ 2031.598212] ath_hal: OpenHAL loaded (AR5210, AR5211, AR5212, RF5110/1/2) [ 2031.623263] wlan: 0.8.6.0 (EXPERIMENTAL) [ 2031.625124] ath_rate_sample: 1.2 [ 2031.627507] ath_pci: 0.9.5.0-BSD (EXPERIMENTAL) [ 2031.627571] ACPI: PCI Interrupt 0000:05:00.0[A] -> Link [LK4E] -> GSI 19 (level, low) -> IRQ 19 [ 2031.627585] PCI: Setting latency timer of device 0000:05:00.0 to 64 [ 2031.667363] ath_hal: MAC revision: 2425 (0xe2) [ 2031.667368] ath_hal: EEPROM version: 5.3 [ 2031.667657] Build date: Oct 12 2007 [ 2031.667661] Debugging version (IEEE80211) [ 2031.667664] ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps [ 2031.667675] ath0: H/W encryption support: WEP [ 2031.667678] ath0: mac 14.2 phy 7.0 radio 0.0 [ 2031.667682] ath0: Use hw queue 1 for WME_AC_BE traffic [ 2031.667684] ath0: Use hw queue 0 for WME_AC_BK traffic [ 2031.667686] ath0: Use hw queue 2 for WME_AC_VI traffic [ 2031.667689] ath0: Use hw queue 3 for WME_AC_VO traffic [ 2031.667691] ath0: Use hw queue 6 for CAB traffic [ 2031.667694] ath0: Use hw queue 7 for beacons [ 2031.667695] Debugging version (ATH) [ 2031.667699] ath0: AR5212: mem=0xf0400000, irq=19 [ 2031.733924] ath5k_hw_set_txpower_limit: changing txpower to 100 [ 2031.733930] ath5k_hw_txpower: invalid tx power: 100 root@rut-laptop:~#

root@rut-laptop:~# ath_info 0xf0400000 Warning: Invalid EEPROM Magic number !

-==Device Information==-

MAC Version: 2425 (0xe0) MAC Revision: 2425 (0xe2) PHY Revision: 5110 (0x0)

-==EEPROM Information==-

EEPROM Version: 5.3 EEPROM Size: 4K Regulatory Domain: 0x65

-==== Capabilities ====-

| 802.11a Support: no | | 802.11b Support: no | | 802.11g Support: yes | | RFKill Support: yes | | 32KHz Crystal: no |

========================

GPIO registers: CR 00008000 DO b00000000 DI e20000000b root@rut-laptop:~#

that's all for now .. now i have to make it working ..

Hey everybody. I would like to help getting this card supported. I need somebody with at least kernel compiling experience, the above mentioned card and some spare time (should take less than an hour). If you have all of the above, please join the irc channel #madwifi on irc.freenode.net and contact nbd

Thanks :)

r2745 I think... but I have abit hardware not that mini-pci card

Tried it - same result.

Tried the svn revision 2815 and the hal error switched from 13 to 3. Nice.

Ubuntu 7.10 Kernel 2.6.22-14 SVN R2822 error code has changed

ath_hal: 0.9.30.13 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133)
wlan: 0.8.4.2 (svn r2818)
ath_pci: 0.9.4.5 (svn r2818)
ACPI: PCI Interrupt 0000:07:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:07:00.0 to 64
MadWifi: unable to attach hardware: 'Hardware didn't respond as expected' (HAL status 3)
ACPI: PCI interrupt for device 0000:07:00.0 disabled

Replying to kevmif@yahoo.com:

Can we please have an update on this?

There is no update to what has been said above already. But since the ticket starts to be a little crowded with comments, here's a summary of the status quo:

AR5007 is not yet supported. We as MadWifi developers can't do anything about it since the support needs to be implemented in the HAL. The HAL supplier stated that he is working on it, and now we're waiting for a release of the result.

but as I gather Madwifi is moving away from closed HAL to AR5K. couldn't something be done to support AR5007EG in AR5K? TIA

Hello ppl...

About ath5k support...

First the good news: It seems this card has the same EEPROM version as 5414/5424+ single chip cards and we can read it and hopefully get what we want from it (EEPROM has changed a lot on 5416/5418 so we 're lucky this card has the older EEPROM), ignore the invalid magic number (seems they have changed it from 5aa5 to a55a -plz someone try changing the value inside ath_info.c and retry). Also attach works ok and it has the same behaviour as 5414 on ath5k (at least that's what i've tested). So i believe when we fix 5414/5424 support (currently working on this) we can hope this card will work too.

And the not-so-good news: Although MAC is possible to match, it's possible that PHY part is much different and that it won't work at all ;-(

We'll keep you posted if we get something useful, until then Sam has the key...

Previous "anonymous" was me (grr session ended soon :P)

Replying to percy:

Where did they get that driver and where can I get it?

See About/ath5k and (soon) http://ath5k.org (right now that domain still just redirects, but soon will be a separate site).

svn co hxxp://svn.madwifi.org/ath5k/ make && sudo make install

I have a wireless card with the AR2417A chipset - newest member of the AR5007 family. I managed to get ath5k compiling on my MIPS platform using rev 2701 - btw in order to get all the symbols resolved for MIPS you need to include "linux/delay.h" into all .c files that use "mdelay" or "udelay", or you can put the include into ath5k.h. MIPS brings in these two functions statically and there were a couple of .c files that were implicitly defining the function since they were not including the header file and that was causing unresolved symbols during my insmod.

After I managed to get the the driver insmod'ed it was not probing my card. Turns out my PCI ID is "0x1D" and the list of supported ids in ath5k_base.c does not include this yet.

When do you expect to support this chipset? Is there any information I can pull off my card in order to expediate the process? I tried to blindly add my PCI ID to the table to force a probe and ath5k_hw.c kicked me out because of an unsupported "sver" (makes sense). I printk'd some values during probing and here they are:

Nov 13 18:32:25 localhost kernel: SDG: Probing ath5k Nov 13 18:32:25 localhost kernel: SDG: ah_version is 0x2 Nov 13 18:32:25 localhost kernel: SDG: ah_mac_srev is 0xf0 Nov 13 18:32:25 localhost kernel: SDG: ah_mac_version is 0xf Nov 13 18:32:25 localhost kernel: SDG: ah_mac_revision is 0x0 Nov 13 18:32:25 localhost kernel: ath5k: Device not supported (0xf0)

Let me know if there is anything else I can do to help add this chipset into the driver.

Replying to Sean:

Would it be possible to disguise this card in ath5k as a 5211 to see if it would work?

Maybe that would be possible, but even then it's a waste of time. Despite of the misinterpreted meaning of the driver name AR5007 differs from most other Atheros chipsets in the way the driver needs to talk to it. Making the driver think it deals with a different chipset thus obviously won't bring you anywhere closer to a working support.

Replying to kinaeng@gmail.com:

is this mean AR5007EG is finally supported by ath5k driver?

To the best of my knowledge: no.

Replying to mrenzmann:

Replying to kinaeng@gmail.com:

is this mean AR5007EG is finally supported by ath5k driver?

To the best of my knowledge: no.

But Fedora 8 got it working...

We got RF5413/5414 to work (well with poor RF quality but we 're working on it), patches are committed on current wireless-2.6 tree (http://www.linuxwireless.org/en/developers/git-guide). If anyone wants to try if that card is working too, plz edit drivers/net/wireless/ath5k/hw.c to skip srev check in ath5k_hw_attach and see what happens. We need feedback ppl and we might be lucky ;-)

I note that the new ASUS eee-pc is rumored to have the AR5007EG - the label on the bottom of it says it is a: Atheros AR5BXB63. lspci reports it as a AR5006EG, with Unknown device 1a3b:1026. The Ubuntu madwifi drivers give the same sorts of errors described above. We eee-pc owners are watching this thread closely... :) while we use ndiswrapper.

This is also of note, because ASUS ships a working ath_pci driver with their system - with hal, etc. (I don't understand all the intricacies.) ASUS is also not making the source code available.... We have whined to them to no avail, but y'all, having originated the software that they are using, would be in a better position to insist on source code release - perhaps to the benefit of everybody.

Guys, please stop the "me too" comments. We are aware that a lot of users are suffering from this problem, but unless you have new information all "me too" comments are just adding noise to the already pretty huge ticket.

So, mrenzmann, may I ask you to state briefly which steps are needed to compile and test the latest code, so that we owners of machines with this card can help more effectively?

There is no way for you to help with AR5007EG right now, unless you're a kernel hacker or reverse engineer.

Replying to Roadkill:

there is source code for eee available I just grabbed it (1.7GB!)

It's probably "nice to know" what driver etc. they use to solve this problem, but this won't help us for MadWifi. We won't incorporate a third-party HAL and we won't switch the HAL vendor, for various reasons (which I won't discuss here - questions in that regard should be forwarded to the madwifi-devel list, they will be ignored here).

Replying to Roadkill:

if I need to I'll modify it myself.

Of course you can do that. I just wanted to make sure people understand that this is not the road the project will take to get AR5007 support in MadWifi.

Hello ppl ;-)

There is a way to make regdumps from ndiswrapper, so even if madwifi doesn't support this chipset we can get what we want from the windows driver. Plz give us some time to work some things out first and then we'll ask for volunteers etc (currently we're stuck at some pci-e related issue, it seems that pci-e cards have a different wake-up process we need to find out before we continue)...

Replying to Roadkill:

Asus has released source code for eeepc

... but without the sources for their modified version of MadWifi (and I still believe that this is a version of MadWifi as Atheros seems to offer to its customers).

Replying to Lonni J Friedman <netllama@linux-sxs.org>:

the Acer Travelmate 2480 is also afflicted

Make that "can be" - I have a Travelmate 2483 with an AR5005-based WLAN card built in. To determine whether a Travelmate is affected by this issue look at the sticker on the bottom of the notebook - if it says the built-in WLAN card model is "AR5BXB63" it's based on the AR5007 chipset and thus is affected.

Replying to mrenzmann:

Replying to Lonni J Friedman <netllama@linux-sxs.org>:

the Acer Travelmate 2480 is also afflicted

Make that "can be" - I have a Travelmate 2483 with an AR5005-based WLAN card built in. To determine whether a Travelmate is affected by this issue look at the sticker on the bottom of the notebook - if it says the built-in WLAN card model is "AR5BXB63" it's based on the AR5007 chipset and thus is affected.

I'm not sure what you're getting at with your comment. Are you suggesting that Acer is shipping Travelmate 2480's with different wireless chipsets? I certainly wouldn't assume that your 2483 is the same as my 2480. Different model numbers would suggest different components.

At any rate, mine has the Atheros AR5BXB63, and is afflicted.

Replying to mrenzmann:

As far as I know they use a MadWifi-derivate that is maintained by Atheros and have a different HAL at hands. This won't help us, as we don't have access to that HAL and can't use it (no, not even it one of the Eee users would grab them off of their Eee and send it to us).

I have an EEE and I'd be happy to send you all the files you need! Just email me what you need and I'll get it for you.

Atheros posted a patch to a madwifi snapshot that will get madwifi working on a EEE. (with a 5007EG) See ticket #1679

My eee is working nicely with it in Ubuntu. :)

... a patch which unfortunately cannot be committed to MadWiFi due to ABI breakages.

I got it running with madwifi-ng-r2756

(forgot to edit the 'anonymous' in the above post)

Yes, it does seem to work! I'm writing this through wifi0, from the card.

I followed rifkill's advice, then I manually rmmoded ndiswrapper, modprobed ath_hal, wlan and finally ath_pci.

Then I opened Wireless Assistant, scanned, logged in, just the same as with ndiswrapper.

Notebook is Acer Aspire 5570z.

Now I can dump ndiswrapper! Very happy!

Here's some output:

neutron:/home/bruno# uname -a
Linux neutron 2.6.22-1-686 #1 SMP Sun Jul 29 14:37:42 UTC 2007 i686 GNU/Linux

dmesg (i never managed to see these lines before):

ath_hal: 0.10.2.2-ATHEROS (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425)
wlan: 0.8.4.2 (svn r2992)
ath_pci: 0.9.4.5 (svn r2992)
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:03:00.0 to 64
ath_pci: switching rfkill capability off
ath_rate_sample: 1.2 (svn r2992)
ath_pci: switching per-packet transmit power control off
wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
wifi0: H/W encryption support: WEP AES AES_CCM TKIP
wifi0: mac 14.2 phy 7.0 radio 10.2
wifi0: Use hw queue 1 for WME_AC_BE traffic
wifi0: Use hw queue 0 for WME_AC_BK traffic
wifi0: Use hw queue 2 for WME_AC_VI traffic
wifi0: Use hw queue 3 for WME_AC_VO traffic
wifi0: Use hw queue 8 for CAB traffic
wifi0: Use hw queue 9 for beacons
wifi0: Atheros 5424/2424: mem=0x8c100000, irq=17
udev: renamed network interface ath0 to wlan0
wlan0: no IPv6 routers present

lsmod:

neutron:/home/bruno# lsmod
Module                  Size  Used by
wlan_scan_sta          12480  1
ath_rate_sample        12736  1
ath_pci               138160  0
wlan                  206256  4 wlan_scan_sta,ath_rate_sample,ath_pci
ath_hal               279296  3 ath_rate_sample,ath_pci
i915                   22208  2
drm                    76020  3 i915
vmnet                  33012  12
vmmon                1800780  0
ppdev                   8676  0
parport_pc             33796  0
lp                     10980  0
parport                33960  3 ppdev,parport_pc,lp
button                  7920  0
ac                      5188  0
battery                 9988  0
ipv6                  236932  20
fuse                   41908  1
dm_snapshot            16516  0
dm_mirror              20896  0
dm_mod                 52000  2 dm_snapshot,dm_mirror
loop                   16932  0
pcmcia                 37100  0
firmware_class          9504  1 pcmcia
snd_hda_intel         239160  1
snd_pcm_oss            39200  0
snd_pcm                72324  2 snd_hda_intel,snd_pcm_oss
snd_mixer_oss          15424  1 snd_pcm_oss
tsdev                   7968  0
uvcvideo               42864  0
compat_ioctl32          1376  1 uvcvideo
videodev               26656  1 uvcvideo
v4l1_compat            12580  2 uvcvideo,videodev
joydev                  9568  0
snd_seq_dummy           3748  0
hci_usb                16220  0
v4l2_common            16608  2 uvcvideo,videodev
yenta_socket           24844  1
rsrc_nonstatic         11968  1 yenta_socket
pcmcia_core            37108  3 pcmcia,yenta_socket,rsrc_nonstatic
i2c_i801                8656  0
rtc                    12856  0
bluetooth              49348  1 hci_usb
iTCO_wdt                9924  0
snd_seq_oss            29408  0
snd_seq_midi_event      6880  1 snd_seq_oss
snd_seq                46320  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_timer              21028  2 snd_pcm,snd_seq
snd_seq_device          7692  3 snd_seq_dummy,snd_seq_oss,snd_seq
i2c_core               23552  1 i2c_i801
tifm_7xx1               7392  0
tifm_core              10180  1 tifm_7xx1
usbhid                 25792  0
hid                    25248  1 usbhid
snd                    48324  10 snd_hda_intel,snd_pcm_oss,snd_pcm,snd_mixer_oss,snd_seq_oss,snd_seq,snd_timer,snd_seq_device
psmouse                36016  0
serio_raw               6692  0
soundcore               7520  1 snd
snd_page_alloc          9512  2 snd_hda_intel,snd_pcm
sky2                   40616  0
intel_agp              23188  1
agpgart                31912  3 drm,intel_agp
evdev                   9312  8
reiserfs              220320  4
sg                     32668  0
sr_mod                 16516  0
cdrom                  32832  1 sr_mod
sd_mod                 27136  6
generic                 4836  0 [permanent]
ide_core              113764  1 generic
uhci_hcd               22960  0
ehci_hcd               30796  0
ata_piix               13348  5
ata_generic             7556  0
libata                115600  2 ata_piix,ata_generic
scsi_mod              136620  4 sg,sr_mod,sd_mod,libata
usbcore               125064  6 uvcvideo,hci_usb,usbhid,uhci_hcd,ehci_hcd
thermal                13416  0
processor              31016  1 thermal
fan                     4836  0

I'm happy to provide any detail to anybody. Just ask here.

Replying to kinaeng@gmail.com:

Replying to kacsa (admin@megacp.com):

hello, can you send patch for me, which you could download (because the patch was remove) Thanks! kacsa

I think we should wait news from madwifi. I believe they will release the patch file once they know the origin of that file.

Ohhh, i can't wait :( So i want to use wifi! Please send patch for me!

why was the patch removed from madwifi website?

---

Right. This ticket is getting cleaned up to pertinent information only. This is not as discussion forum, but an ticket for tracking on issue. Noise makes it useless.

Any further misuse will result in the ticket being locked.

---

Arg, Trac's administration interface seems to have had some issues with deleting the posts that I click on; my apologies for any information that may have been lost or dialogs that may not make any sense.

Also, if you wish to discuss what I have done here, you may do so on IRC (#madwifi), or by email (the -devel list, or my @madwifi.org address).

Replying to bruno:

why was the patch removed from madwifi website?

I removed the patch when it was initially posted, because it was not clear who owned copyright on the patch and whether it violated the license of the HAL. Violating copyright is bad, mmmkay.

For queries that are other than related to this ticket, please use our regular support channels.

For those who haven't noticed yet: "the" patch (for i386 AR5007 support) has been attached to ticket #1679 again. We're working with Atheros to find a solution to add AR5007 support also to the other platforms. Please be patient.

The new HAL from Sam Leffler should fix AR5007EG support

A new HAL has been made available by Sam Leffler (0.10.5.6) that supports AR2425 chips (AR5007* chipsets). This is a full HAL release so it should work for all platforms - that means x86-64.

The new HAL is currently in a branch, but should hopefull,y barring any other issues, be migrated to trunk soon. Tarballs are available from <http://snapshots.madwifi.org/special/> and Subversion access is at <https://svn.madwifi.org/madwifi/branches/madwifi-hal-0.10.5.6>.

Please would you test this HAL code and report any issues other to those in trunk to this ticket. A couple of replies saying it works would be nice, but please don't go overboard on the matter.

No luck with the new hal, on ubuntu 8.04, ath0 syas there are no scan results

second the failure to fix problem in ubuntu 8.04, no scan results

Error reporters, please provide following:

• Your name or nickname, not "anonymous"
• Output of "uname -a"
• Output of "lspci -vnnd 168c:"
• Output of iwconfig
• Relevant parts of the kernel log as shown by dmesg
• If there are any error messages from any command - the exact command and the exact error messages.
• Results of testing with other versions of MadWifi, preferably svn trunk.

If you need any help with installation, please use standard support channels.

Sorry, I was the second person to report that the svn link listed above did not work, but after a fresh install of Ubuntu Hardy 8.04, it does work, all I did was sudo apt-get update && apt-get dist-upgrade reboot sudo apt-get install build-essential subversion sudo svn checkout ...svn.... cd then sudo make && make install reboot and everything works fine

I've just tried the new HAL svn branch, unfortunately, like with the old one, dmesg reports a status 3 for HAL :

MadWifi: unable to attach hardware: 'Hardware didn't respond as expected' (HAL status 3)
ACPI: PCI interrupt for device 0000:14:00.0 disabled
APIC error on CPU0: 40(40)
APIC error on CPU1: 40(40)
APIC error on CPU0: 40(40)
APIC error on CPU1: 40(40)

At compile time, there's warnings :

warning:  Clock skew detected.  Your build may be incomplete.

uname

Linux dqsd 2.6.24.5-smp #2 SMP Wed Apr 30 13:41:38 CDT 2008 i686 AMD Turion(tm) 64 X2 Mobile Technology TL-60 AuthenticAMD GNU/Linux

lspci -v

14:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter [168c:001c] (rev 01)
        Subsystem: AMBIT Microsystem Corp. Unknown device [1468:042a]
        Flags: fast devsel, IRQ 20
        Memory at f8200000 (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, MSI 00
        Capabilities: [90] MSI-X: Enable- Mask- TabSize=1
        Capabilities: [100] Advanced Error Reporting <?>
        Capabilities: [140] Virtual Channel <?>
        Kernel modules: ath_pci

iwconfig

lo        no wireless extensions.

eth0      no wireless extensions.

Replying to polo: If you tried loading an old HAL, you must reboot. And while at that, please set your clock properly, just for general sanity.

After a reboot and a modprobe alias ath0, it works better, I can see an ath0 and wifi0 in output of iwconfig

thanks a lot

Replying to proski:

Replying to polo: If you tried loading an old HAL, you must reboot. And while at that, please set your clock properly, just for general sanity.

When I run lspci -v I get the following. I am also not able to get the wifi to work. I am running Ubunto 8.04

03:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)
	Subsystem: Hewlett-Packard Company Unknown device 137a
	Flags: fast devsel, IRQ 19
	Memory at f6000000 (64-bit, non-prefetchable) [disabled] [size=64K]
	Capabilities: <access denied>

Review of steps to fix this problem, as I understand it. (Please correct as needed.) Update HAL Reboot computer.

Anything else? Thanks

Please use "-vnn" is lspci option. "-nn" makes lspci show numeric IDs along with the names and "-v" ensures that the subsystem data is printed, as well as tells whether it's a PCIe card. The cards with the same vendor ID 168c:001c may be AR5006EG or AR5007EG. It's the subsystem ID that allows to distinguish between them.

My Atheros AR5007EG works ok with r3704 from branches/madwifi-hal-0.10.5.6. I tried ndiswrapper with limited success and have only just started to use madwifi so it might still be flaky but it works so far.

I can connect to my router using WPA-Personal TKIP which is defined in /etc/wpa_supplicant/wpa_supplicant.conf.

I am running gentoo on a toshiba satellite a215 s4747.

Bumping priority, as we can now do something about this, and adjusted milestone.

There does not seem to be much noise regarding failures of the new HAL. Should we think about merging it fairly rapidly?

Replying to proski:

Please use "-vnn" is lspci option. "-nn" makes lspci show numeric IDs along with the names and "-v" ensures that the subsystem data is printed, as well as tells whether it's a PCIe card. The cards with the same vendor ID 168c:001c may be AR5006EG or AR5007EG. It's the subsystem ID that allows to distinguish between them.

Below are the results of your advice. Thanks and I hope it helps. !!!

03:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter [168c:001c] (rev 01)
	Subsystem: Hewlett-Packard Company Unknown device [103c:137a]
	Flags: fast devsel, IRQ 19
	Memory at f6000000 (64-bit, non-prefetchable) [disabled] [size=64K]
	Capabilities: <access denied>

Replying to mentor:

There does not seem to be much noise regarding failures of the new HAL.

Please note this mail from Bruno on madwifi-devel and the following mails in response to it.

Should we think about merging it fairly rapidly?

I'd say that the cause of the issues that Bruno reported should be investigated first.

Replying to mrenzmann: Ack.

lspci (the device is AR5BXB63 - there is a sticker on la