#1805: ath5k Version in kernel 2.6.24-mm1/2.6.25-rc1 and latest 2.6-git doesn't
work for me
--------------------------------------+-------------------------------------
      Reporter:  [EMAIL PROTECTED]  |       Owner:     
          Type:  defect               |      Status:  new
      Priority:  critical             |   Milestone:     
     Component:  ath5k                |     Version:     
    Resolution:                       |    Keywords:     
Patch_attached:  0                    |  
--------------------------------------+-------------------------------------
Comment (by [EMAIL PROTECTED]):

 Hi,


 I just did the following:

 As I reported this error, I was using debian testing. I upgraded to
 debian-unstable and fetched the latest 2.6-git and compiled it under
 kernel 2.6.24.2!

 And see, now it works! I'm not sure if it's kind of a version conflict or
 if very recently something in the ath5k has been changed which fixed this
 issue.

 WPA2 with preshared key works also. The only 'issue' I see right now, is,
 that txpower seems to be limited to 0dBm.

 tpad:/etc/openvpn# iwlist ath0 txpower
 ath0      unknown transmit-power information.

           Current Tx-Power=0 dBm        (1 mW)

 If I change txpower with iwconfig, it accepts every value (even such which
 are not supported by the card), but no change is displayed in iwconfig or
 iwlist.

 Is this 'normal' in this stage or should txpower set/get work?

 DHCP works for me.

 Greetings,
 M. Kramer


 Replying to [ticket:1805 [EMAIL PROTECTED]:
 > Hello,
 >
 >
 > I tryed to get ath5k working with kernel 2.6.24-mm1, 2.6.25-rc1 and the
 latest 2.6-git under kernel 2.6.24 with no success. The issues are always
 the same, as described below.
 >
 > Worked fine under kernel 2.6.24 with the latest madwifi-snapshot.
 >
 > Using the following card:
 >
 >  -==Device Information==-
 > MAC Version:  5212  (0x50)
 > MAC Revision: 5213A (0x59)
 > PHY Revision: 5110  (0x00)
 > PHY Revision: 5110  (0x00)
 >  -==EEPROM Information==-
 > EEPROM Version:     4.8
 > EEPROM Size:        16K
 > Regulatory Domain:  0x64
 >  -==== Capabilities ====-
 > |  802.11a Support: no   |
 > |  802.11b Support: yes  |
 > |  802.11g Support: yes  |
 > |  RFKill  Support: yes  |
 > |  32KHz   Crystal: yes  |
 >  ========================
 > GPIO registers: CR 00000000 DO 00000000 DI 00000007
 >
 > dmesg output:
 > ath5k_pci 0000:02:02.0: registered as 'phy0'
 > phy0: Selected rate control algorithm 'pid'
 > ath5k phy0: Atheros AR5213A chip found (MAC: 0x59, PHY: 0x43)
 > ath5k phy0: RF2112A 2GHz radio found (0x46)
 > iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10 (17-Aug-2007)
 > wlan0 renamed to ath0
 > udev: renamed network interface wlan0 to ath0
 >
 >
 > I can associate to networks:
 >
 > ath0      IEEE 802.11g  ESSID:"92"
 >           Mode:Managed  Frequency:2.447 GHz  Access Point:
 > 00:1B:2F:7A:AB:A6
 >           Bit Rate=54 Mb/s   Tx-Power=27 dBm
 >           Retry min limit:7   RTS thr:off   Fragment thr=2352 B
 >           Encryption key:off
 >           Link Quality=106/100  Signal level=-25 dBm  Noise level=-93
 dBm
 >           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
 >           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
 >
 > dmesg output:
 > ath0: Initial auth_alg=0
 > ath0: authenticate with AP 00:1b:2f:7a:ab:a6
 > ath0: RX authentication from 00:1b:2f:7a:ab:a6 (alg=0 transaction=2
 > status=0)
 > ath0: authenticated
 > ath0: associate with AP 00:1b:2f:7a:ab:a6
 > ath0: RX AssocResp from 00:1b:2f:7a:ab:a6 (capab=0x411 status=0 aid=1)
 > ath0: associated
 > ath0: CTS protection enabled (BSSID=00:1b:2f:7a:ab:a6)
 > ath0: switched to long barker preamble (BSSID=00:1b:2f:7a:ab:a6)
 >
 >
 >
 > But that's basically what i can do. I can't ping anything, don't get any
 > response to DHCP-requests/discovers. Can't reach the default Gateway of
 > the Netgear wireless-router (essid 92). The same setup works great with
 > kernel 2.6.24 and the latest madwifi-snapshot.
 >
 > I don't see any errors in dmesg, 'ping' doesn't output any errors, there
 > are just no replies. If i scan the whole network range with nmap, nmap
 > finishes very quick and states all hosts (except the local) as down.  I
 > ran a  wireshark session and saw some Samba-broadcasts, but can't ping
 > or scan the source IP.
 >
 > Any suggestions?
 >
 >
 >
 >
 > Greetings,
 > M. Kramer

-- 
Ticket URL: <http://madwifi.org/ticket/1805#comment:1>
madwifi.org <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets

Reply via email to