#808: AR5006X gives HAL status 14.
---------------------------------+------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: madwifi: other | Version: v0.9.2
Resolution: | Keywords: AR5006X HAL status 14
Patch_attached: 0 |
---------------------------------+------------------------------------------
Comment (by fab dot mariotti gmail dot com ):
AR5006X - ath5k - some problems persist...[[BR]]
I cannot keep a stable connection:[[BR]]
ath5k phy0: calibration timeout (XXXXMHz).[[BR]]
ath5k phy0: ath5k_chan_set: unable to reset channel 1 (XXXX Mhz).[[BR]]
ath5k phy0: noise floor calibration timeout (XXXXMHz).
after a while I am not able to connect anymore (see further details).
But I would like to add:
- Primo: We might need a word from a coder who might help us to report
this specific trouble.[[BR]]
It looks to me that the problem is AR5006X specific but also
a bit random depending on hardware architecture and/or
kernel and/or kernel modules interaction. That is: NOT easy.
Because indeed it seems to work in some cases it is not a
major bug and we might be able to report on the problem
a bit better if instructed.
- Secondo: We might want to help ourself by confining the problem to
AR5006X cards. (I'll double check it too ;) )[[BR]]
The HP machines seem to be more involved in the problem.
I'll try to check (for what I can), but I guess that
positive reports on working AR5006Xs might be of help too.
1) I kept writing on this ticket (madwifi: ath5k ticket?) in the hope that
it might
give insight to developers.
2) So, to be consistent, I write my last report unless I get called back.
This is for ath5k.
The machine: HP Pavilion Media Center TV m7695.ch Desktop PC
/proc/cpuinfo - extract
{{{
vendor_id : AuthenticAMD
model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
}}}
uname
{{{
uname -a
Linux localhost.localdomain 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 16:52:18
EST 2008 x86_64 x86_64 x86_64 GNU/Linux
}}}
cat /etc/redhat-release - Linux distribution
{{{
Fedora release 7 (Moonshine)
}}}
lspci -vv - extract
{{{
04:01.0 Ethernet controller: Atheros Communications, Inc. AR5006X
802.11abg NIC (rev 01)
Subsystem: Lite-On Communications Inc Unknown device 5001
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 168 (2500ns min, 7000ns max), Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 16
Region 0: Memory at febf0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
}}}
Problem report:
The network connection is not stable: network hangs after a while. There
is no easy way to debug it.
- it looks like it is independent from having MS stuff putting it on a
given state.[[BR]]
- I got a second wifi router and set it up as open: no encription. The
first one uses WPA[[BR]]
via wpa_supplicant. It might have nothing to do with it but indeed the
open connection[[BR]]
seems to be more stable (It just last longer).[[BR]]
- The wifi/driver, or whatever, is working randomly. For example right
now I have a full (84%)
wifi connection since a couple of hours. Next boot might fail. I get no
particular error
messages. Except for the above mentioned timeout messages. But I
couldn't figure out
a consistent behaviour.
- I did try to wait for cooling down. Just in case the driver does
strange stuff and heat up a bit.
No changes: random behaviour. Of course I based this measure on a kind
of my common sense
which might be wrong. In any case the card didn't burn! Boot on XP and
it does work nicely.
- Of course I did trust fedora default parameters and 'wlan up'
procedure. I.e. I boot
a fedora core 7 (FC7) machine without any extra hand made changes.
Namely I use, at present,
NetworkManager service but I got the same behaviour using the
wlassisant tool.
My personal opinion is that the card AR5006X is not fully supported and on
some
hardware it might simply fail or simply work. The kernel itself has little
to do with it (the machine doesn't hung or misbehave) but a couple of
other
kernel modules might interfere. Was HAL status 14 before and it is dodgy
behaviour on ath5k driver. What's special on this AR5006X card? on HP
machines?
Best
Fabio
--
Ticket URL: <http://madwifi.org/ticket/808#comment:37>
madwifi.org <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
