Ticket #859 (closed enhancement: fixed)

Opened 5 years ago

Last modified 4 years ago

Hardware Support: AR5006EG (PCI Express)

Reported by: Tupac Assigned to:
Priority: minor Milestone: version 0.9.3
Component: madwifi: HAL Version: v0.9.2
Keywords: AR5006EG PCI Express PCIe 001c Cc:
Patch is attached: 0 Pending:

Description (Last modified by mrenzmann)

This is from my syslog when i load the 0.9.2 

Sep  5 12:44:37 localhost kernel: [17180388.592000] ath_pci: driver unloaded
Sep  5 12:44:51 localhost kernel: [17180403.224000] ath_pci: 0.9.4.5 (0.9.2)
Sep  5 12:44:51 localhost kernel: [17180403.224000] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 233
Sep  5 12:44:51 localhost kernel: [17180403.224000] PCI: Setting latency timer of device 0000:02:00.0 to 64
Sep  5 12:44:51 localhost kernel: [17180403.228000] wifi%%d: unable to attach hardware: 'Hardware revision not supported' (HAL status 13)
Sep  5 12:44:51 localhost kernel: [17180403.228000] ACPI: PCI interrupt for device 0000:02:00.0 disabled

Thnx guys =)

Attachments

Change History

09/05/06 20:25:00 changed by mrenzmann

  • keywords set to AR5006EG PCI Express.
  • version set to v0.9.2.
  • type changed from defect to enhancement.
  • description changed.
  • summary changed from When madwifi will support AR5006EG to Support for AR5006EG-based (PCI express) cards.

This would be more a question to be posed on the madwifi-users mailing list. But anyway...

I remember Atheros mentioning that the EG (which is the only PCI Express chipset that is currently available from Atheros afaik) should be supported in the current HAL. Can you post some details about the card, and maybe also the output of lspci -l (only the part about your WLAN card, the rest doesn't matter)? Thanks in advance.

09/06/06 15:23:39 changed by Tupac

Hey again.. thnx for the reply and the information about the card is the following:

Atheros AR5006EG I check the bulletin in atheros website so i found out the chipset is: AR2423 OS im using: Ubuntu

here is the full lspci:

0000:00:00.0 Host bridge: ATI Technologies Inc: Unknown device 5a31 (rev 01) 0000:00:01.0 PCI bridge: ATI Technologies Inc: Unknown device 5a3f 0000:00:04.0 PCI bridge: ATI Technologies Inc: Unknown device 5a36 0000:00:06.0 PCI bridge: ATI Technologies Inc: Unknown device 5a38 0000:00:07.0 PCI bridge: ATI Technologies Inc: Unknown device 5a39 0000:00:12.0 IDE interface: ATI Technologies Inc ATI 4379 Serial ATA Controller (rev 80) 0000:00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80) 0000:00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80) 0000:00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller (rev 80) 0000:00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 82) 0000:00:14.1 IDE interface: ATI Technologies Inc Standard Dual Channel PCI IDE Controller ATI (rev 80) 0000:00:14.2 0403: ATI Technologies Inc: Unknown device 437b (rev 01) 0000:00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge (rev 80) 0000:00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge (rev 80) 0000:01:05.0 VGA compatible controller: ATI Technologies Inc: Unknown device 5a62 0000:02:00.0 Ethernet controller: Atheros Communications, Inc.: Unknown device 001c (rev 01) 0000:0b:06.0 CardBus bridge: ENE Technology Inc CB1410 Cardbus Controller (rev 01) 0000:0b:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

Here a lspci -m:

00:00.0 Host bridge ATI Technologies Inc 5a31 01 00 Toshiba America Info Systems ff10 00:01.0 PCI bridge ATI Technologies Inc 5a3f 00 00 0000 0000 00:04.0 PCI bridge ATI Technologies Inc 5a36 00 00 0000 0000 00:06.0 PCI bridge ATI Technologies Inc 5a38 00 00 0000 0000 00:07.0 PCI bridge ATI Technologies Inc 5a39 00 00 0000 0000 00:12.0 IDE interface ATI Technologies Inc ATI 4379 Serial ATA Controller 80 8f Toshiba America Info Systems ff10 00:13.0 USB Controller ATI Technologies Inc IXP SB400 USB Host Controller 80 10 Toshiba America Info Systems ff10 00:13.1 USB Controller ATI Technologies Inc IXP SB400 USB Host Controller 80 10 Toshiba America Info Systems ff10 00:13.2 USB Controller ATI Technologies Inc IXP SB400 USB2 Host Controller 80 20 Toshiba America Info Systems ff10 00:14.0 SMBus ATI Technologies Inc IXP SB400 SMBus Controller 82 00 Toshiba America Info Systems ff10 00:14.1 IDE interface ATI Technologies Inc Standard Dual Channel PCI IDE Controller ATI 80 8a Toshiba America Info Systems ff10 00:14.2 0403 ATI Technologies Inc 437b 01 00 Toshiba America Info Systems ff10 00:14.3 ISA bridge ATI Technologies Inc IXP SB400 PCI-ISA Bridge 80 00 ATI Technologies Inc IXP SB400 PCI-ISA Bridge 00:14.4 PCI bridge ATI Technologies Inc IXP SB400 PCI-PCI Bridge 80 01 0000 0000 01:05.0 VGA compatible controller ATI Technologies Inc 5a62 00 00 Toshiba America Info Systems ff10 02:00.0 Ethernet controller Atheros Communications, Inc. 001c 01 00 Askey Computer Corp. 7106 0b:06.0 CardBus bridge ENE Technology Inc CB1410 Cardbus Controller 01 00 Toshiba America Info Systems ff10 0b:07.0 Ethernet controller Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ 10 00 Toshiba America Info Systems ff10

Thnx for the help and hope this debug can help.

09/06/06 15:36:24 changed by kastor

i got the same.. it's from toshiba laptop

the sticker in the laptop says: AR5BXB61

here is the output

02:00.0 Ethernet controller: Atheros Communications, Inc. Unknown device 001c (rev 01)

Subsystem: Askey Computer Corp. Unknown device 7106 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 08 Interrupt: pin A routed to IRQ 11 Region 0: Memory at d0100000 (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: 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 <128ns, L1 <2us 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 L0s L1 Enabled 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

09/06/06 15:40:38 changed by Crypkey

Same problem over here with a Toshiba laptop satellite and AR5006EG... argh it should work.. my debugs are the same as Tupac.. so if you need anything else.. you can ask..

Thank you in advance, any help is good.

09/07/06 18:32:51 changed by Crypkey

Here is a lspci -v: 

0000:02:00.0 Ethernet controller: Atheros Communications, Inc.: Unknown device 001c (rev 01)
        Subsystem: Askey Computer Corp.: Unknown device 7106
        Flags: fast devsel, IRQ 233
        Memory at d0100000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [40] Power Management version 2
        Capabilities: [50] Message Signalled Interrupts: 64bit- Queue=0/0 Enable-
        Capabilities: [60] #10 [0011]
        Capabilities: [90] #11 [0000]

Hope can help this.

09/07/06 21:12:10 changed by kastor

Here it's mine.. it's a little diferent 

02:00.0 Ethernet controller: Atheros Communications, Inc. Unknown device 001c (rev 01)
        Subsystem: Askey Computer Corp. Unknown device 7106
        Flags: bus master, fast devsel, latency 0, IRQ 11
        Memory at d0100000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [40] Power Management version 2
        Capabilities: [50] Message Signalled Interrupts: 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

09/09/06 03:26:55 changed by sam <at> errno <dot> com

fixed in next version of the hal

09/09/06 15:42:52 changed by mrenzmann

Thanks for the information, Sam.

09/11/06 22:27:42 changed by Tupac

Hi there, and thnx sam, just wondering when this is happening?

Thnx.

09/12/06 19:09:41 changed by kastor

me too.. i tried with the lastest svn and hal doesn't recognize my chipset..

09/12/06 19:37:27 changed by Crypkey

Yep lol kastor I tried the same thing and well still not working..

btw the chipset of this card is: AR2423

Greetings.

09/14/06 11:43:57 changed by mrenzmann

I just committed a new HAL version in r1711. As mentioned by Sam in his comment to this ticket, that version is expected to solve the problems with the AR5006EG chipset. So everyone who suffers from these problems should give the new HAL version (0.9.18.0) a try. But please note that this HAL is not yet fully tested. Please report back about any problems you've spotted.

For those of you who don't want to use Subversion there is a snapshot tarball available for download.

09/14/06 14:14:25 changed by Crypkey

mmh Problems with the version r1711 this is the log: 

Sep 14 07:11:47 localhost kernel: [17181392.988000] ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
Sep 14 07:11:47 localhost kernel: [17181392.996000] ath_rate_sample: disagrees about version of symbol ieee80211_iterate_nodes
Sep 14 07:11:47 localhost kernel: [17181392.996000] ath_rate_sample: Unknown symbol ieee80211_iterate_nodes
Sep 14 07:11:47 localhost kernel: [17181392.996000] ath_rate_sample: Unknown symbol ieee80211_proc_vcreate
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: Unknown symbol ath_rate_tx_complete
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: disagrees about version of symbol ieee80211_encap
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: Unknown symbol ieee80211_encap
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: disagrees about version of symbol ieee80211_input
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: Unknown symbol ieee80211_input
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: disagrees about version of symbol ieee80211_ifattach
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: Unknown symbol ieee80211_ifattach
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: disagrees about version of symbol ieee80211_beacon_update
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: Unknown symbol ieee80211_beacon_update
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: Unknown symbol ieee80211_find_channel
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: disagrees about version of symbol ieee80211_find_rxnode
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: Unknown symbol ieee80211_find_rxnode
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: Unknown symbol ath_rate_attach
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: Unknown symbol ieee80211_vap_setup
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: disagrees about version of symbol ieee80211_ifdetach
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: Unknown symbol ieee80211_ifdetach
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: disagrees about version of symbol ieee80211_free_node
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: Unknown symbol ieee80211_free_node
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: Unknown symbol ieee80211_input_monitor
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: Unknown symbol ath_rate_newassoc
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: disagrees about version of symbol ieee80211_crypto_newkey
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: Unknown symbol ieee80211_crypto_newkey
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: disagrees about version of symbol ieee80211_crypto_setkey
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: Unknown symbol ieee80211_crypto_setkey
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: Unknown symbol ath_rate_dynamic_proc_register
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: disagrees about version of symbol ieee80211_dump_pkt
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: Unknown symbol ieee80211_dump_pkt
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: Unknown symbol ieee80211_ioctl_create_vap
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: Unknown symbol ieee80211_dfs_test_return
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: Unknown symbol ieee80211_stop_running
Sep 14 07:11:47 localhost kernel: [17181393.012000] ath_pci: disagrees about version of symbol ieee80211_cipher_none
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_cipher_none
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_note
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: disagrees about version of symbol ieee80211_crypto_delkey
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_crypto_delkey
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: disagrees about version of symbol ieee80211_media_change
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_media_change
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_beacon_miss
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: disagrees about version of symbol ieee80211_beacon_alloc
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_beacon_alloc
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_getcfframe
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: disagrees about version of symbol ieee80211_iterate_nodes
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_iterate_nodes
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_vap_attach
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: disagrees about version of symbol ieee80211_ibss_merge
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_ibss_merge
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ath_rate_node_cleanup
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_send_qosnulldata
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ath_rate_detach
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_create_vap
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_input_all
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: disagrees about version of symbol ieee80211_media_status
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_media_status
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_start_running
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_vap_detach
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: disagrees about version of symbol ieee80211_announce
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_announce
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_mark_dfs
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: disagrees about version of symbol ieee80211_chan2ieee
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_chan2ieee
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ath_rate_node_init
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ath_rate_findrate
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_dturbo_switch
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: disagrees about version of symbol ieee80211_crypto_encap
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_crypto_encap
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: disagrees about version of symbol ieee80211_chan2mode
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_chan2mode
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: disagrees about version of symbol ieee80211_getrssi
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: Unknown symbol ieee80211_getrssi
Sep 14 07:11:47 localhost kernel: [17181393.016000] ath_pci: disagrees about version of symbol ieee80211_find_txnode
Sep 14 07:11:47 localhost kernel: [17181393.020000] ath_pci: Unknown symbol ieee80211_find_txnode
Sep 14 07:11:47 localhost kernel: [17181393.020000] ath_pci: Unknown symbol ath_rate_newstate
Sep 14 07:11:47 localhost kernel: [17181393.020000] ath_pci: Unknown symbol ath_rate_setupxtxdesc

09/14/06 19:26:53 changed by Crypkey

ups i restarted my machine and then works! ;)

iwconfig: 

wifi0     no wireless extensions.

ath0      IEEE 802.11g  ESSID:""
          Mode:Managed  Channel:0  Access Point: Not-Associated
          Bit Rate:0 kb/s   Tx-Power:17 dBm   Sensitivity=0/3
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=0/94  Signal level=-95 dBm  Noise level=-95 dBm
          Rx invalid nwid:1277  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

But when i tried dhclient ath0 is not working.. and also seems that i cant do iwlist ath0 scan or put it in monitor mode, this is normal?

log from syslog, messages: 

Sep 14 12:11:09 localhost dhclient: wifi0: unknown hardware address type 801
Sep 14 12:11:10 localhost dhclient: wifi0: unknown hardware address type 801
Sep 14 12:11:10 localhost dhclient: Listening on LPF/ath0/00:16:e3:28:3b:76
Sep 14 12:11:10 localhost dhclient: Sending on   LPF/ath0/00:16:e3:28:3b:76
Sep 14 12:11:10 localhost dhclient: Sending on   Socket/fallback
Sep 14 12:11:14 localhost dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5
Sep 14 12:11:19 localhost dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 12
Sep 14 12:11:20 localhost kernel: [17180229.072000] ath0: no IPv6 routers present
Sep 14 12:11:31 localhost dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 15
Sep 14 12:11:46 localhost dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 18
Sep 14 12:12:04 localhost dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 11
Sep 14 12:12:15 localhost dhclient: No DHCPOFFERS received.
Sep 14 12:12:15 localhost dhclient: No working leases in persistent database - sleeping.

when i tried iwlist ath0 scan and iwconfig ath0 mode monitor: 

root@jact:/home/crypkey# iwconfig ath0 mode monitor
Error for wireless request "Set Mode" (8B06) :
    SET failed on device ath0 ; Invalid argument.

ath0      Interface doesn't support scanning : Invalid argument

09/14/06 20:53:41 changed by Crypkey

Forgot the syslog: 

Sep 14 13:48:24 localhost kernel: [17179590.632000] Linux agpgart interface v0.101 (c) Dave Jones
Sep 14 13:48:24 localhost kernel: [17179590.664000] wlan: 0.8.4.2 (svn r1711)
Sep 14 13:48:24 localhost kernel: [17179590.696000] ath_hal: module license 'Proprietary' taints kernel.
Sep 14 13:48:24 localhost kernel: [17179590.696000] ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
Sep 14 13:48:24 localhost kernel: [17179590.724000] ath_rate_sample: 1.2 (svn r1711)
Sep 14 13:48:24 localhost kernel: [17179590.740000] ath_pci: 0.9.4.5 (svn r1711)
Sep 14 13:48:24 localhost kernel: [17179590.740000] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 233
Sep 14 13:48:24 localhost kernel: [17179590.740000] PCI: Setting latency timer of device 0000:02:00.0 to 64
Sep 14 13:48:24 localhost kernel: [17179591.568000] ACPI: PCI Interrupt 0000:00:14.2[A] -> GSI 16 (level, low) -> IRQ 233
Sep 14 13:48:24 localhost kernel: [17179591.568000] input: PC Speaker as /class/input/input1
Sep 14 13:48:24 localhost kernel: [17179592.272000] hda_codec: Unknown model for ALC861, trying auto-probe from BIOS...
Sep 14 13:48:24 localhost kernel: [17179592.320000] Real Time Clock Driver v1.12
Sep 14 13:48:24 localhost kernel: [17179592.356000] wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
Sep 14 13:48:24 localhost kernel: [17179592.356000] wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
Sep 14 13:48:24 localhost kernel: [17179592.356000] wifi0: H/W encryption support: WEP AES AES_CCM TKIP
Sep 14 13:48:24 localhost kernel: [17179592.356000] wifi0: mac 10.0 phy 6.1 radio 10.2
Sep 14 13:48:24 localhost kernel: [17179592.356000] wifi0: Use hw queue 1 for WME_AC_BE traffic
Sep 14 13:48:24 localhost kernel: [17179592.356000] wifi0: Use hw queue 0 for WME_AC_BK traffic
Sep 14 13:48:24 localhost kernel: [17179592.356000] wifi0: Use hw queue 2 for WME_AC_VI traffic
Sep 14 13:48:24 localhost kernel: [17179592.356000] wifi0: Use hw queue 3 for WME_AC_VO traffic
Sep 14 13:48:24 localhost kernel: [17179592.356000] wifi0: Use hw queue 8 for CAB traffic
Sep 14 13:48:24 localhost kernel: [17179592.356000] wifi0: Use hw queue 9 for beacons
Sep 14 13:48:24 localhost kernel: [17179592.888000] wifi0: Atheros 5424/2424: mem=0xd0100000, irq=233
Sep 14 13:48:24 localhost kernel: [17179592.896000] ACPI: PCI Interrupt 0000:0b:06.0[A] -> GSI 23 (level, low) -> IRQ 185
Sep 14 13:48:24 localhost kernel: [17179592.896000] Yenta: CardBus bridge found at 0000:0b:06.0 [1179:ff10]
Sep 14 13:48:24 localhost kernel: [17179592.896000] Yenta: Using CSCINT to route CSC interrupts to PCI
Sep 14 13:48:24 localhost kernel: [17179592.896000] Yenta: Routing CardBus interrupts to PCI
Sep 14 13:48:24 localhost kernel: [17179592.896000] Yenta TI: socket 0000:0b:06.0, mfunc 0x01111002, devctl 0x44
Sep 14 13:48:24 localhost kernel: [17179592.912000] wlan: 0.8.4.2 (svn 2006-07-10)
Sep 14 13:48:24 localhost kernel: [17179592.916000] new_ath_rate_sample: Unknown symbol new_ath_hal_computetxtime
Sep 14 13:48:24 localhost kernel: [17179592.920000] new_ath_pci: Unknown symbol new_ath_rate_node_cleanup
Sep 14 13:48:24 localhost kernel: [17179592.920000] new_ath_pci: Unknown symbol new_ath_hal_computetxtime
Sep 14 13:48:24 localhost kernel: [17179592.920000] new_ath_pci: Unknown symbol new_ath_hal_probe
Sep 14 13:48:24 localhost kernel: [17179592.920000] new_ath_pci: Unknown symbol _new_ath_hal_attach
Sep 14 13:48:24 localhost kernel: [17179592.920000] new_ath_pci: Unknown symbol new_ath_rate_setupxtxdesc
Sep 14 13:48:24 localhost kernel: [17179592.920000] new_ath_pci: Unknown symbol new_ath_hal_detach
Sep 14 13:48:24 localhost kernel: [17179592.920000] new_ath_pci: Unknown symbol new_ath_rate_newassoc
Sep 14 13:48:24 localhost kernel: [17179592.920000] new_ath_pci: Unknown symbol new_ath_rate_tx_complete
Sep 14 13:48:24 localhost kernel: [17179592.920000] new_ath_pci: Unknown symbol new_ath_hal_init_channels
Sep 14 13:48:24 localhost kernel: [17179592.920000] new_ath_pci: Unknown symbol new_ath_hal_getwirelessmodes
Sep 14 13:48:24 localhost kernel: [17179592.920000] new_ath_pci: Unknown symbol new_ath_rate_node_init
Sep 14 13:48:24 localhost kernel: [17179592.920000] new_ath_pci: Unknown symbol new_ath_rate_attach
Sep 14 13:48:24 localhost kernel: [17179592.920000] new_ath_pci: Unknown symbol new_ath_rate_detach
Sep 14 13:48:24 localhost kernel: [17179592.920000] new_ath_pci: Unknown symbol new_ath_rate_findrate
Sep 14 13:48:24 localhost kernel: [17179592.920000] new_ath_pci: Unknown symbol new_ath_rate_newstate
Sep 14 13:48:24 localhost kernel: [17179592.920000] new_ath_pci: Unknown symbol new_ath_hal_mhz2ieee

Hope this can works and help. Greetings

09/14/06 21:48:05 changed by Mister_X

CrypKey?, if you're not associated, asking a DHCP lease won't work

09/15/06 03:26:46 changed by mrenzmann

@Crypkey: In addition to what Mister_X already wrote, please note that you must destroy ath0 before you can create a new ath0 in monitor mode (see also: UserDocs/ChangingMode. Or change the name of the monitor VAP you're creating to something else, ath1 for example.

Next thing: you seem to make use of the strange stuff that Ubuntu provides (they prefixed madwifi-ng module names with new_, which probably causes some problems). Please double-check that your manually compiled modules are not loaded in a mix with the modules from Ubuntu - this will likely cause strange effects.

Last but not least, make sure that the wlan_scan_sta module is loaded before you try to scan.

09/15/06 15:50:32 changed by Crypkey

OK im working on it i will tell you if i find something, btw to connect to the AP you need to do the following:

iwconfig ath0 essid "something" ifconfig ath0 up iwlist ath0 scan iwconfig ath0 ap 11:22:33:44:55:66 dhcpcd ath0 or dhclient ath0

that should work right?

09/15/06 19:24:43 changed by Crypkey

Hey Mister_X well actually i did the following:

ifconfig ath0 up iwlist ath0 scan ( i found several APs ) iwconfig ath0 essid "essid_ap" iwconfig ath0 ap "bssid_ap" dhclient ath0

Not working.. dunno why.. ahy idea? doing something wrong here?

10/01/06 01:46:35 changed by bergo

Does anyone can tell that this card is currently working under Linux?

10/02/06 19:04:06 changed by mrenzmann

Support for PCI express cards has been fixed in HAL 0.9.18.0, which has been added in r1711. So it should work if you use a matching repository snapshot of r1711 or later (for example from http://snapshots.madwifi.org/madwifi-ng ). However, HAL 0.9.18.0 needs further testing and is currently suspicious of containing some bugs that need to be fixed.

10/02/06 19:05:40 changed by mrenzmann

  • status changed from new to closed.
  • resolution set to fixed.
  • milestone set to version 0.9.3.

For now I close this ticket as "fixed". Feel free to reopen it if it shows up that there are still issues with this PCI express chipsets in r1711 or later.

01/17/07 12:43:10 changed by VladoK

Hi, I've just tried an AR5006EG (168c:001c) card with latest madwifi (svn r1971) and all I get is 'Hardware revision not supported' (HAL status 13) error message together with some other weird messages about NMI and RAM chips: 

ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
wlan: 0.8.4.2 (svn r1971)
ath_rate_sample: 1.2 (svn r1971)
ath_pci: 0.9.4.5 (svn r1971)
ACPI: PCI Interrupt 0000:0c:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:0c:00.0 to 64
Uhhuh. NMI received for unknown reason a1 on CPU 0.
You probably have a hardware problem with your RAM chips
Dazed and confused, but trying to continue
wifi%d: unable to attach hardware: 'Hardware revision not supported' (HAL status 13)
ACPI: PCI interrupt for device 0000:0c:00.0 disabled

So, some details:

  • Card: AzureWave AW-GE780, FCC-ID PPD-AR5BXB63
  • System: Dell Latitude D420 (removed ipw3945 and inserted this card instead), kill switch disabled, Coro Solo cpu
  • Kernel: 2.6.19 preempt no-SMP, gcc 4.1.2

lspci: 

0c:00.0 Ethernet controller: Atheros Communications, Inc. Unknown device 001c (rev 01)
        Subsystem: Unknown device 1a3b:1026
        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 efdf0000 (64-bit, non-prefetchable) [disabled] [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

I don't like those 'RAM chips' related messages, never seen something like that before (and there are no memory problems otherwise). Unfortunately, I cannot test the card in different system since this one is the only one with MiniPCIe slot available, and also I cannot change memory since it is onboard, but it passed memtest86 without erros (with card inserted).

Have anyone experienced such problems with this card? Or could it possibly be madwifi-unrelated problem?

Thanks

01/17/07 12:52:05 changed by mrenzmann

Please see if the card works on a different system. From the messages in your log I'd say you face a hardware problem that is neither caused by the WLAN card nor related with MadWifi.

04/04/07 11:33:43 changed by dennis.schwan@leuchtturm-it.de

I also have a problem with this Chip: 

[ 2725.504000] ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
[ 2725.620000] wlan: 0.8.4.2 (0.9.3)
[ 2725.652000] ath_pci: 0.9.4.5 (0.9.3)
[ 2725.652000] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 19
[ 2725.652000] PCI: Setting latency timer of device 0000:02:00.0 to 64
[ 2725.660000] wifi%d: unable to attach hardware: 'Hardware revision not supported' (HAL status 13)
[ 2725.660000] ACPI: PCI interrupt for device 0000:02:00.0 disabled

uname -a: 

Linux nb-dschwan2 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

lspci -vv: 

02:00.0 Ethernet controller: Atheros Communications, Inc. Unknown device 001c (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-
        Interrupt: pin A routed to IRQ 19
        Region 0: Memory at d0200000 (64-bit, non-prefetchable) [disabled] [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

04/17/07 04:38:16 changed by Kvetch

Hey mrenzmann, I too cannot get my AR5006EG PCI express card working. Is there anyway to get this ticket re-opened or are there other steps I can try to get it to work? I have tried numerous svn releases and I can't get the card recognized.

lcpci output - 

03: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
        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 16
        Region 0: Memory at fdbf0000 (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: 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

# lsmod
Module                  Size  Used by
wlan_wep                6272  0
wlan_scan_sta          11904  0
ath_pci                84456  0
wlan                  182408  3 wlan_wep,wlan_scan_sta,ath_pci
ath_hal               216368  1 ath_pci
# iwconfig
eth0      no wireless extensions.
lo        no wireless extensions.
eth1      no wireless extensions.
tunl0     no wireless extensions.

Dmesg output - 

ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
wlan: 0.8.4.2 (0.9.3)
ath_pci: 0.9.4.5 (0.9.3)
PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [APC1] -> GSI 16 (level,
low) -> IRQ 16
PCI: Setting latency timer of device 0000:03:00.0 to 64
wifi%d: unable to attach hardware: 'Hardware didn't respond as
expected' (HAL status 3)

Thanks for all the great work guys.

04/17/07 15:26:04 changed by Kvetch

I forgot to post my lspci -n output 

03:00.0 0200: 168c:001c (rev 01)

Thanks again.

04/18/07 04:10:36 changed by proski

  • keywords changed from AR5006EG PCI Express to AR5006EG PCI Express PCIe 001c.
  • component changed from madwifi: other to madwifi: HAL.
  • status changed from closed to reopened.
  • resolution deleted.
  • milestone changed from version 0.9.3 to version 1.0.0 - first stable release.

We have too many reports that the issue is not fixed. I'm reopening the ticket.

04/18/07 11:56:31 changed by illth@gmx.de

I have exactly the same problem as Kvetch:

I can not get my Abit Airpace to work.

The Hal status is a) after a fresh coldboot: "13 Hardware revision not supported", b) after unloading / reloading the driver "3 Hardware didn't respod as expected".

I assume that the hal doesn't deinitialize the card corrctly. The Hal status 3 "survives" warm reboots, i really have to power down.

04/25/07 13:59:03 changed by developer@hiasl.net

My card fails to load: "Hardware didn't respond expected" (Hal status 3) (using latest version 0.9.30.10 from svn) 

lspci -vvd 168c:001c
04:00.0 Ethernet Controller: Atheros Communications, Inc. Unknown device 001c (rev 01)
Subsystem: Unknown device 1a3b:1026
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 18
Region 0: Memory at b3000000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40]
Capabilities: [50]
Capabilities: [60]
Capabilities: [90]
Capabilities: [100]
Capabilities: [140]

Do you need any more information -> please contact me :-) Thank you for looking into the matter, Matthias Wieser

(follow-up: ↓ 34 ) 05/17/07 18:48:42 changed by foot

Hi all . I have this problem too . dmesg wrote this PCI: Enabling device 0000:02:00.0 (0000 -> 0002) ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 18 (level, low) -> IRQ 185 PCI: Setting latency timer of device 0000:02:00.0 to 64 wifi%d: unable to attach hardware: 'Hardware didn't respond as expected' (HAL status 3) ACPI: PCI interrupt for device 0000:02:00.0 disabled

this is my lspci 00:00.0 Host bridge: Intel Corporation 82946GZ/PL/GL Memory Controller Hub (rev 02) 00:01.0 PCI bridge: Intel Corporation 82946GZ/PL/GL PCI Express Root Port (rev 02) 00:02.0 VGA compatible controller: Intel Corporation 82946GZ/GL Integrated Graphics Controller (rev 02) 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01) 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01) 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 01) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01) 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01) 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01) 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 01) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1) 00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01) 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01) 00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family) SATA IDE Controller (rev 01) 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01) 02:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01) 03:00.0 Ethernet controller: Attansic Technology Corp. L1 Gigabit Ethernet Adapter (rev b0) 05:00.0 Ethernet controller: VIA Technologies, Inc. VT6105 [Rhine-III] (rev 86)

lspci

00:00.0 Host bridge: Intel Corporation 82946GZ/PL/GL Memory Controller Hub (rev 02) 00:01.0 PCI bridge: Intel Corporation 82946GZ/PL/GL PCI Express Root Port (rev 02) 00:02.0 VGA compatible controller: Intel Corporation 82946GZ/GL Integrated Graphics Controller (rev 02) 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01) 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01) 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 01) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01) 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01) 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01) 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 01) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1) 00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01) 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01) 00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family) SATA IDE Controller (rev 01) 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01) 02:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01) 03:00.0 Ethernet controller: Attansic Technology Corp. L1 Gigabit Ethernet Adapter (rev b0) 05:00.0 Ethernet controller: VIA Technologies, Inc. VT6105 [Rhine-III] (rev 86)

this lspci -v

02:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01)

Subsystem: Unknown device 1a3b:1034 Flags: fast devsel, IRQ 185 Memory at fe9f0000 (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

Any one thera can help me ?

05/18/07 00:41:21 changed by strasak@bubakov.net

What about to play a bit with ACPI kernel parameters ? and MSI ones - on/off ? It seems that for some ppl it works, for some not, maybe PCI-E cards are more picky about these conditions ...

05/20/07 17:44:18 changed by foot

i tried start with noacpi and pci=noacpi parametrs but system don't boot. Anyone have some idea can help me ? i bit with this problem month/(windows drivers with ndiswrapper doesn't work too.

(in reply to: ↑ 31 ; follow-up: ↓ 35 ) 06/11/07 02:26:13 changed by ron@ronware.org

I have the exact same problem! In the past I used Atheros cards with madwifi without any problem - but this card is really having difficulty getting up and working.

(in reply to: ↑ 34 ) 06/11/07 02:28:51 changed by ron@ronware.org

I'm keeping track of my progress here: ronware.org/wiki/Pub:Linux_on_the_Acer_5100-5033

06/11/07 12:10:43 changed by strasak@bubakov.net

ron, foot are you using/tried latest trunk, aka development version - with HAL 0.9.30.13 included - of madwifi, or are you using stable version - 0.9.3.1 ATM or as in foot's case now deprecated 0.9.30.10 HAL branch?
ron, Acer branded notebooks are known to have problems with madwifi due to some weird modification Acer does to atheros based chipsets and stuff, take a look at other tickets related to Acer if something does ring the bell

06/12/07 00:45:56 changed by ron@ronware.org

It looks like I've got 0.9.3.1. I'll trye the dev version now to see if it helps me.

06/12/07 00:55:51 changed by ron@ronware.org

Er, well - the latest CVS version doesn't build: /home/ron/proj/madwifi/ath_hal/ah_osdep.c: In function 'ath_hal_sysctl_register': /home/ron/proj/madwifi/ath_hal/ah_osdep.c:516: error: too many arguments to function 'register_sysctl_table'

06/12/07 05:04:33 changed by kelmo

Take a look at the page about getting madwifi from SVN before you mention MadWifi and CVS again, please.

06/12/07 05:23:47 changed by ron@ronware.org

Ok. Rebuilt from the svn repository, and here is what I get: 

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

06/12/07 08:05:53 changed by strasak@bubakov.net

this really looks like hw issue - interrupt routing problem or something like that, could even be buggy card, i had similar problem with minipci cards which has somehow screwed eeproms or which got some collateral damage during thunderstorms. Does it work ok in other systems, if you are able to try it there?

06/12/07 17:33:22 changed by ron@ronware.org

I don't have another system I can try it in, but I'm more than willing to try to fix any potential IRQ routing problems. Do you have any suggestions as to kernel boot options I should try? I have tried "pci=noacpi" and "pci=nomsi" without help. On this machine, I do have to use "poll=idle" to get it to boot... it's got an AMD Turion 64 X2 TL-50 which I've now heard may be an issue in general.

However, besides the wifi card (and the SD reader), it works perfectly.

Thanks, Ron

06/12/07 17:38:49 changed by anonymous

Here I've got some collected information obviously concerning this problem. The infos are randomly collected at different times with respectively installed ndiswrapper or madwifi, not used simultaneously, as it could be understood misleadingly.

rafb.net/p/CoienB24.html

06/12/07 17:47:48 changed by ron@ronware.org

Yep, looks just like my problem :(

06/14/07 02:27:27 changed by ron@ronware.org

Here's the latest output with "ath_debug=9": 

ath_pci: 0.9.4.5 (svn r2438)
ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:02:00.0 to 64
ath_attach: devid 0x1c
MadWifi: unable to attach hardware: 'Hardware didn't respond as expected' (HAL status 3)
ACPI: PCI interrupt for device 0000:02:00.0 disabled

(follow-up: ↓ 64 ) 06/15/07 20:04:49 changed by ivka

Exactly the same errors for me too. Asus P5B-MX/WiFi Solo mainboard.

lspci output: 

02:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01)
        Subsystem: Unknown device 1a3b:1034
        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 18
        Region 0: Memory at feaf0000 (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

modprobe ath_pci output: 

ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
wlan: 0.8.4.2 (0.9.3.1)
ath_pci: 0.9.4.5 (0.9.3.1)
ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:02:00.0 to 64
wifi%d: unable to attach hardware: 'Hardware didn't respond as expected' (HAL status 3)
ACPI: PCI interrupt for device 0000:02:00.0 disabled

06/15/07 20:48:42 changed by ivka

Tried revision 2459. Same result.

06/19/07 21:12:00 changed by anonymous

I have the same problem with am Acer Aspire 3680. I first tried with the rfkill switch in both positions (the bios seems to remember the state, since different key codes are sent depending on current state). Then, when that did not help, I fetched the head version from svn and built it. Still, no luck. The dmesg output is below

This is with one setting of rfkill (probably "off"):

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 (svn r2484) ath_pci: 0.9.4.5 (svn r2484) PCI: Enabling device 0000:03:00.0 (0000 -> 0002) 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 MadWifi: unable to attach hardware: 'Hardware revision not supported' (HAL status 13) ACPI: PCI interrupt for device 0000:03:00.0 disabled

This is after I unload and try other rfkill setting (probably "on"):

ath_pci: driver unloaded ath_hal: driver unloaded wlan: driver unloaded atkbd.c: Unknown key pressed (translated set 2, code 0xd5 on isa0060/serio0). atkbd.c: Use 'setkeycodes e055 <keycode>' to make it known. atkbd.c: Unknown key released (translated set 2, code 0xd5 on isa0060/serio0). atkbd.c: Use 'setkeycodes e055 <keycode>' to make it known. ath_hal: 0.9.30.13 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133) wlan: 0.8.4.2 (svn r2484) ath_pci: 0.9.4.5 (svn r2484) PCI: Enabling device 0000:03:00.0 (0000 -> 0002) 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 MadWifi: unable to attach hardware: 'Hardware didn't respond as expected' (HAL status 3) ACPI: PCI interrupt for device 0000:03:00.0 disabled

Thank you for your help. Darrin

06/28/07 02:27:05 changed by Stefan

I just got my wifi to work with ndiswrapper. The problem was located in the wifi-software switch as first expected. After loading this module (although I'm using a Fujitsu Siemens Amilo laptop it just runs fine), the internal antenna got activated correctly:

code.google.com/p/aceracpi/

The next days I'll evaluate, if it also works with madwifi.

06/28/07 18:04:35 changed by Stefan

Seems so, that it only runs with ndiswrapper, what a pity. Perhaps I'll have one more - a little more intensive - try at the weekend.

06/29/07 02:35:53 changed by ron@ronware.org

My current attempt at ndiswrapper gives: 

ndiswrapper (ntoskernel_exit:2723): object f6ec48a0(2) was not freed, freeing it now
ndiswrapper version 1.47 loaded (smp=yes)
ndiswrapper: driver net5211 (,11/15/2006,5.1.1.9) loaded
ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 17
ndiswrapper (ZwClose:2246): closing handle 0xf37f9ca8 not implemented
PCI: Setting latency timer of device 0000:02:00.0 to 64
ndiswrapper (NdisWriteErrorLogEntry:192): log: C0001389, count: 4, return_address: f8f056d4
ndiswrapper (NdisWriteErrorLogEntry:195): code: 0xf6318a00
ndiswrapper (NdisWriteErrorLogEntry:195): code: 0x28
ndiswrapper (NdisWriteErrorLogEntry:195): code: 0xf8df8000
ndiswrapper (NdisWriteErrorLogEntry:195): code: 0xf8df8000
ndiswrapper (mp_init:216): couldn't initialize device: C000009A
ndiswrapper (pnp_start_device:439): Windows driver couldn't initialize the device (C0000001)
ndiswrapper (mp_halt:258): device f2aba500 is not initialized - not halting
ndiswrapper: device eth%d removed
ACPI: PCI interrupt for device 0000:02:00.0 disabled
ndiswrapper: probe of 0000:02:00.0 failed with error -22

06/29/07 15:58:07 changed by Stefan

You first have to uninstall madwifi temporarily and remove all corrsponding modules in /lib/modules/uname -r/net/, then reboot in order to use the wifi-device correctly (only unload the ath_pci,... modules didn't work for me either - I got the same error as you did). Then after modprobing ndiswrapper it should run, at least on my system.

06/30/07 01:18:13 changed by ron@ronware.org

hi, Stefan -

I did as you said ... and it works now!

I am using the ndiswrapper driver, specifically the XP driver for "Atheros AR5001", net5211

Thanks a million!

(follow-up: ↓ 56 ) 07/26/07 00:45:08 changed by anonymous

Hi guys. Ok - so I have the exact same card in a Toshiba Satellite A215-4757. Wireless is a complete failure. I've tried following your instructions here but there is so much of "do a little this and do a little that", that I'm not sure I'm following the instructions correctly. Can anyone type out a compete coherent set of instructions to get this card to work?

It's the same rev of the card> Same model number. AR58BX863, AR5006EG Mini PCI: 001c (rev 1). Sorry, I'm leaving parts out but believe me when I say it matches everything so far. Even the error is the same under dmesg.

I've tried MadWifi (SVN head), and ndiswrapper. Neither is working right now. To boot, I don't even have the wired lan working. But that's not a problem I want to deal w/ here.

Thanks.

Distro: Mandriva 2007.1 (Spring) i586 Hardware: AMD x86_64 (yes, I know I installed the 32 bit on purpose - the 64 bit would have required me to find 64 bit windows drivers) NDISWrapper: 1.21-2mdv MadWifi: SVN Head (with the latest HAL of course) (Not simultaneously of course).

I have not been able to get the acpi kernel modules to load - I noticed someone said something about using those.

Anyway. Here goes nothing.

Troubled With Toshiba

07/26/07 01:38:38 changed by mentor

  • priority changed from major to minor.
  • summary changed from Support for AR5006EG-based (PCI express) cards to Hardware Support: AR5006EG (PCI Express).

(in reply to: ↑ 54 ) 07/26/07 06:23:22 changed by mrenzmann

Replying to anonymous:

It's the same rev of the card Same model number. AR58BX863, AR5006EG Mini PCI

There is no card with that name (AR58BX863). If it's the AR5BXB63 then your issue is unrelated to this ticket, since that card has an AR5007EG chipset, which is not yet supported. In that case you might want to look at #1192.

07/26/07 20:09:39 changed by anonymous

Sorry. It's the AR5BXB63. I just can't read the 4 point text on the bottom of my laptop very well. It's not like I was able to open the box and look in.

Please help.. Troubled with Toshiba.

(follow-up: ↓ 59 ) 07/27/07 05:31:41 changed by anonymous

Ok - this is ridiculous. My computer reports all the same stuff. Even if the stupid sticker on the bottom of the box says B63. How can it be the 5007EG when the comptuer itself reports 5006EG???? As do all the specs???

Troubled with Toshiba.

(in reply to: ↑ 58 ; follow-up: ↓ 60 ) 07/27/07 06:51:18 changed by mrenzmann

Replying to anonymous:

How can it be the 5007EG when the comptuer itself reports 5006EG????

Where does the computer "report" that you have the AR5006EG chipset on your card? If you determine that with lspci: PCI IDs (which is what lspci uses) are no safe attribute to identify the chipset that is on the card.

As do all the specs???

Which specs? Have a link at hands?

(in reply to: ↑ 59 ) 08/04/07 18:15:12 changed by anonymous

I have the same problem with an Acer Aspire 7520. I tried the 0.9.3.1 version and the latest SVN version. lspci: 

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 f0400000 (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

dmesg: 

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

(follow-up: ↓ 62 ) 08/07/07 23:32:00 changed by Zack

I have a new system with the following:

04:00.0 "Ethernet controller" "Atheros Communications, Inc." "AR5006EG 802.11 b/g Wireless PCI Express Adapter" -r01 "Askey Computer Corp." "Unknown device 7128"

The current Jul 2007 version of Madwifi rejects this card. Why?

(in reply to: ↑ 61 ; follow-up: ↓ 63 ) 08/08/07 07:39:12 changed by mrenzmann

Replying to Zack:

The current Jul 2007 version of Madwifi rejects this card. Why?

Probably because it's mis-recognized by lspci and it's an AR5007EG instead? Can you provide further information on the card, such as the vendor and the product name?

(in reply to: ↑ 62 ) 08/18/07 16:59:59 changed by Zack

Replying to mrenzmann:

Replying to Zack:

The current Jul 2007 version of Madwifi rejects this card. Why?

Probably because it's mis-recognized by lspci and it's an AR5007EG instead? Can you provide further information on the card, such as the vendor and the product name?

Here's the verbose lspci output: 

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: fast devsel, IRQ 16
        Memory at d8000000 (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

It's in a Toshiba P205-S6307 laptop.

(in reply to: ↑ 46 ) 08/21/07 12:37:40 changed by anonymous

Replying to ivka:

Exactly the same errors for me too. Asus P5B-MX/WiFi Solo mainboard.

This motherboard does not use the AR5006EG chipset. At least my board came with an Azurewave AW-GA821 which has the AR5007EG chip. Support for that is coming up, hopefully soon, with a new HAL. See 1192 for more information.

10/11/07 12:34:41 changed by anonymous

My Asus P5B-MX/WiFi uses AR5006 (168c:001c rev_01). ath_hal returns status 13 :(

Subsystem differs from ivka m/b : 1a38:1024

10/22/07 18:54:23 changed by anonymous

I have an AR5006EG that came with my mac mini. It's worked for almost 2 months now, but trying to configure it (associate, etc) from the command line is unreliable at best, and wpa supplicant fails 75% of the time with funky errors. As a side note, when I try it with ndiswrapper, it works just fine until you try to use wpa supplicant, in which case it falls to the same problems that it does with the madwifi driver.

02/06/08 16:48:03 changed by mentor

lspci may mis-identify 168c:001c AR5007 chipsets as AR5006EG. AR5007 chipsets may benefit from the patch in #1679

02/14/08 16:07:35 changed by anonymous

I just updated to 0.9.4 but I still get:

wifi%d: unable to attach hardware: 'Hardware revision not supported' (HAL status 13)

(follow-up: ↓ 76 ) 02/14/08 16:14:43 changed by anonymous

well, are you really sure that you have a AR5006EG? or a AR5007? because the AR5007 isn't supported in 0.9.4 (see: the release notes) but in the current trunk...

(in reply to: ↑ 75 ; follow-up: ↓ 77 ) 02/14/08 19:24:01 changed by mrenzmann

Replying to anonymous:

because the AR5007 isn't supported in 0.9.4 (see: the release notes) but in the current trunk...

AR5008 support is in trunk, AR5007 is available as experimental patch only (see #1679). Nevertheless the hint as such is correct, this might be another case of AR5007 that gets misidentified as AR5006 in lspci.

(in reply to: ↑ 76 ; follow-ups: ↓ 80 ↓ 81 ) 02/14/08 20:34:06 changed by anonymous

Replying to mrenzmann:

AR5008 support is in trunk, AR5007 is available as experimental patch only (see #1679). Nevertheless the hint as such is correct, this might be another case of AR5007 that gets misidentified as AR5006 in lspci.

Oh, wow is it really that bad?! It's a pity that the "free" driver is in such a miserable shape.

But I guess, I one of the lucky ones that has at least some sort of access to binaries of Atheros' great proprietary driver for linux. I'm wondering if "the license" is a real business for them now...

(follow-up: ↓ 79 ) 02/15/08 00:43:31 changed by sgtcyrex

Well, seems like i got the same problem as everybody else here.

lspci shows 06:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01)

(This is a Acer Aspire 5720Z (bought in Norway)

my dmesg says: PCI: Setting latency timer of device 0000:06:00.0 to 64 wifi%d: unable to attach hardware: 'Hardware revision not supported' (HAL status 13)

followed the guide at hxxp://fedorasolved.org/mobile/fc-wireless/madwifi-yum-livna/?searchterm=madwifi

should be the latest release, right?

(in reply to: ↑ 78 ; follow-up: ↓ 82 ) 02/15/08 00:59:44 changed by mentor

Replying to sgtcyrex:

Well, seems like i got the same problem as everybody else here.

Then don't add noise to the ticket. The regular support channels are referenced widely.

lspci shows 06:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01)

And as said above lspci may be wrong.

(This is a Acer Aspire 5720Z (bought in Norway) my dmesg says: PCI: Setting latency timer of device 0000:06:00.0 to 64 wifi%d: unable to attach hardware: 'Hardware revision not supported' (HAL status 13) followed the guide at hxxp://fedorasolved.org/mobile/fc-wireless/madwifi-yum-livna/?searchterm=madwifi should be the latest release, right?

I just have no idea. Why don't you check the version numbers on the package?

(in reply to: ↑ 77 ; follow-up: ↓ 84 ) 02/15/08 01:00:51 changed by mentor

Replying to anonymous:

Replying to mrenzmann:

AR5008 support is in trunk, AR5007 is available as experimental patch only (see #1679). Nevertheless the hint as such is correct, this might be another case of AR5007 that gets misidentified as AR5006 in lspci.

Oh, wow is it really that bad?! It's a pity that the "free" driver is in such a miserable shape. But I guess, I one of the lucky ones that has at least some sort of access to binaries of Atheros' great proprietary driver for linux. I'm wondering if "the license" is a real business for them now...

This is useless noise! More than that it's useless noise with terrible use of inverted commas and sarcasm. Why?

(in reply to: ↑ 77 ) 02/15/08 05:47:09 changed by mrenzmann

Replying to anonymous:

Oh, wow is it really that bad?! It's a pity that the "free" driver is in such a miserable shape.

Please, don't feed this troll.

(in reply to: ↑ 79 ; follow-up: ↓ 83 ) 02/15/08 12:16:44 changed by sgtcyrex

Replying to mentor:

lspci shows 06:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01)

And as said above lspci may be wrong.

Is the sticker on the back of my laptop wrong too? cuz this clearly states what i said above. 0.9.3.3 is the package version

(in reply to: ↑ 82 ; follow-up: ↓ 85 ) 02/15/08 12:18:53 changed by mrenzmann

Replying to sgtcyrex:

Is the sticker on the back of my laptop wrong too?

What exactly is stated on the sticker in question?

(in reply to: ↑ 80 ) 02/15/08 15:02:36 changed by anonymous

Replying to mentor:

Replying to anonymous:

Replying to mrenzmann:

AR5008 support is in trunk, AR5007 is available as experimental patch only (see #1679). Nevertheless the hint as such is correct, this might be another case of AR5007 that gets misidentified as AR5006 in lspci.

Oh, wow is it really that bad?! It's a pity that the "free" driver is in such a miserable shape. But I guess, I one of the lucky ones that has at least some sort of access to binaries of Atheros' great proprietary driver for linux. I'm wondering if "the license" is a real business for them now...

This is useless noise! More than that it's useless noise with terrible use of inverted commas and sarcasm. Why?

(This is a bit OT, since it's about >=AR5008 and not about AR5007/AR5006 mis)

I really appreciate all the hard work that went into the madwifi driver! The driver was and still is one with the best support and hw-compatibility! Yes, I have about a few hundreds AR5212 as APs and Stations and they're still working great!

However these fine chips are showing their age and I evaluated these yesteryears "next generation" cards... And BAAAM, right into the mess (especially "AP-mode", since APs are based on ARM platforms). That's when I got that binary driver "ht_tp:/_/www.sparklan.com/download.php?support_id=163"... and finally, with this package these fine cards don't **** anymore!

(in reply to: ↑ 83 ) 02/15/08 17:18:18 changed by sgtcyrex

Replying to mrenzmann:

Replying to sgtcyrex:

Is the sticker on the back of my laptop wrong too?

What exactly is stated on the sticker in question?

AR5BXB63

My bad....

(follow-up: ↓ 87 ) 02/24/08 08:37:14 changed by ilredil@yahoo.com

Same issue here on my Acer 5050-3785.

problem (message appears on boot, pulled from dmesg) 

ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
wlan: 0.9.4
ath_pci: 0.9.4
Yenta TI: socket 0000:08:01.0 probing PCI interrupt failed, trying to fix
Yenta TI: socket 0000:08:01.0 no PCI interrupts. Fish. Please report.
Yenta: no PCI IRQ, CardBus support disabled for this socket.
Yenta: check your BIOS CardBus, BIOS IRQ or ACPI settings.
Yenta: ISA IRQ mask 0x00f8, PCI irq 0
Socket status: 30000006
Yenta: Raising subordinate bus# of parent bus (#08) from #09 to #0c
pcmcia: parent PCI bridge I/O window: 0xa000 - 0xafff
cs: IO port probe 0xa000-0xafff: clean.
pcmcia: parent PCI bridge Memory window: 0xb0300000 - 0xb03fffff
PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:02:00.0 to 64
wifi%d: unable to attach hardware: 'Hardware revision not supported' (HAL status 13)
ACPI: PCI interrupt for device 0000:02:00.0 disabled[/code]

lspci 

02:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01)

uname -a 

Linux the-laptop 2.6.24 #16 PREEMPT Sat Feb 23 22:05:17 PST 2008 i686 AMD Turion(tm) 64 Mobile Technology MK-38 AuthenticAMD GNU/Linux

using madwifi v0.9.4

According to the owner's manual, it has a "WLAN: Acer InviLink?(tm) 802.11b/g Wi-Fi CERTIFIED(tm) solution, supporting Acer SignalUp?(tm) wireless technology." So obviously Acer doesn't want to tell me that there is an Atheros chip in there. Ironically, the Atheros wifi card is one of the main things that persuaded me to go with this laptop instead of another brand.

If you need any additional info, let me know. If anyone knows what file needs hacked for this issue, let me know and I'll tale a stab at it. To me, the issue looks like this particular card/chipset just isn't supported.

--Adam

(in reply to: ↑ 86 ) 02/24/08 08:54:24 changed by mrenzmann

Replying to ilredil@yahoo.com:

Same issue here on my Acer 5050-3785.

Please look at the bottom of your notebook, there should be a sticker with further information on your WLAN card. If it says "AR5BXB63", then you're another victim of the "AR5007 card misidentified as AR5006" and an experimental solution for it is provided in ticket #1679.

02/24/08 20:40:28 changed by ilredil@yahoo.com

Yep you nailed it. It's an "AR5BXB63". I downloaded the patched tarball from #1679 and my card is now usable. :-)

02/25/08 05:57:06 changed by mrenzmann

  • status changed from reopened to closed.
  • resolution set to fixed.
  • milestone changed from version 1.0.0 - first stable release to version 0.9.3.

The original issue related to AR5006 support has been fixed already, so I close this ticket (again). I believe that all remaining reports are related to the same issue: AR5007 card gets misidentified as AR5006 by lspci. As mentioned above in various comments, experimental support for AR5007 is available in ticket #1679.

Please don't reopen this ticket or add to it unless you are absolutely sure that you do have a WLAN card with AR5006 chipset. Check twice, even if you think you're sure. Thanks.

05/08/08 19:55:06 changed by pierre@drici-gestoria.com

very strange. I've got same pbs as anybody here, except the sticker on my laptop says ARBXB63 and not AR5BXB63! lspci -n 168c:001c rev 1 on a packard bell easyNote.MX52-B-041 according to packard bell web site, my wifi card is a AzureWave? AW-GE780, which is "based on the Atheros AR5007EG chipset."

Add/Change #859 (Hardware Support: AR5006EG (PCI Express))