Date: Mon, 20 Oct 2008 16:00:46 -0500 From: eculp@cloudmaster.info To: freebsd-mobile@freebsd.org Subject: Re: I lost ath0 support on current sometime between Sept 20 and Sept 26. Message-ID: <20081020160046.17qwm4xcsbdws40k4@cloudmail.cloudmaster.info> In-Reply-To: <48FBA87B.3030404@freebsd.org> References: <7affaed60810091639n2714fae1mbd34048bc8be89c3@mail.gmail.com> <7affaed60810100658k354550abs2754a2c1ea1b0958@mail.gmail.com> <7affaed60810120614l79670870t7e4914615094056f@mail.gmail.com> <200810122351.13564.jhugo@meraka.csir.co.za> <48F2915B.6090507@freebsd.org> <7affaed60810122012n526929e1j9d38b977a029251e@mail.gmail.com> <48FBA87B.3030404@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Sam Leffler <sam@freebsd.org>: > Edwin L. Culp W. wrote: >> On Sun, Oct 12, 2008 at 7:07 PM, Sam Leffler <sam@freebsd.org> wrote: >> >>> Johann Hugo wrote: >>> >>>> On Sunday 12 October 2008, Edwin L. Culp W. wrote: >>>> >>>> >>>>> On Fri, Oct 10, 2008 at 8:58 AM, Edwin L. Culp W. <edwinlculp@gmail.co= m> >>>>> >>>>> >>>> wrote: >>>> >>>> >>>>>> On Thu, Oct 9, 2008 at 9:21 PM, Sam Leffler <sam@freebsd.org> wrote: >>>>>> >>>>>> >>>>>>> Edwin L. Culp W. wrote: >>>>>>> >>>>>>> >>>>>>>> I started this thread on current but I lost it to Ashish Shukla so = I'm >>>>>>>> going to try here and see if I can explain it better and solve this >>>>>>>> strange issue. >>>>>>>> >>>>>>>> I was happily using Sam's ath_hal-20080528 patch and IIRC the >>>>>>>> committed ath_hal fixes until Sept 20. I didn't build another new >>>>>>>> kernel until Sept 26. From that date on I have been unable to get = it >>>>>>>> working. The sept 20 kernel still works great. I'm using it to sen= d >>>>>>>> this email. I don't have to change anything I just start kernel.ol= d >>>>>>>> and run it rather than today's kernel that has no problems other th= an >>>>>>>> bringing up ath0/wlan0. >>>>>>>> >>>>>>>> Some general info for both kernels that I can find no important >>>>>>>> differences and now really doubt that the problem is hal_ath but >>>>>>>> something else that has changed and is causing the problem. I have >>>>>>>> thought of dhcp, ifconfig, ??? The general information for both >>>>>>>> follows: >>>>>>>> >>>>>>>> >>>>>>>> FreeBSD 8.0-CURRENT #50: Thu Oct 9 05:27:41 CDT 2008 >>>>>>>> root@ed.local.net.mx:/usr/obj/usr/src/sys/ENCONTACTO >>>>>>>> >>>>>>>> rc.conf that doesn't change and works for sept 20 kernel but not >>>>>>>> todays: >>>>>>>> >>>>>>>> wlans_ath0=3Dwlan0 >>>>>>>> ifconfig_wlan0=3D"DHCP ssid virus wepmode on wepkey 1:0x2373FE951= 5 >>>>>>>> weptxkey 1" >>>>>>>> >>>>>>>> ifconfig with todays kernel for ath0 and wlan0: >>>>>>>> >>>>>>>> >>>>>>>> ath0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0= mtu >>>>>>>> 2290 ether 00:1d:d9:27:5c:e5 >>>>>>>> media: IEEE 802.11 Wireless Ethernet autoselect mode 11g >>>>>>>> status: associated >>>>>>>> wlan0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric = 0 mtu >>>>>>>> 1500 >>>>>>>> ether 00:1d:d9:27:5c:e5 >>>>>>>> media: IEEE 802.11 Wireless Ethernet OFDM/48Mbps mode 11g >>>>>>>> status: associated >>>>>>>> ssid virus channel 6 (2437 Mhz 11g) bssid 00:1d:7e:51:e1:4d >>>>>>>> regdomain 101 indoor ecm authmode OPEN privacy ON deftxkey 1 >>>>>>>> wepkey 1:40-bit txpower 16 bmiss 7 scanvalid 450 bgscan >>>>>>>> bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmod= e >>>>>>>> CTS wme burst roaming MANUAL >>>>>>>> >>>>>>>> The part of the dmesg that show ath0 and wlan0 with hal >>>>>>>> >>>>>>>> ath_hal: 0.10.5.10 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, >>>>>>>> RF2413, RF5413, RF2133, RF2425, RF2417) >>>>>>>> >>>>>>>> ath0: <Atheros 5424/2424> mem 0xd0400000-0xd040ffff irq 19 at devic= e >>>>>>>> 0.0 on pci5 >>>>>>>> ath0: [ITHREAD] >>>>>>>> ath0: WARNING: using obsoleted if_watchdog interface >>>>>>>> ath0: mac 14.2 phy 7.0 radio 10.2 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -------------------------------------------------------------------= ---- >>>>>>>> ------------------------- >>>>>>>> >>>>>>>> The same information for the Sept 20 kernel. >>>>>>>> >>>>>>>> FreeBSD ed.local.net.mx 8.0-CURRENT FreeBSD 8.0-CURRENT #34: Sat Se= p >>>>>>>> 20 05:37:05 CDT 2008 >>>>>>>> root@ed.local.net.mx:/usr/obj/usr/src/sys/ENCONTACTO i386 >>>>>>>> >>>>>>>> rc.conf is the same. >>>>>>>> >>>>>>>> If config for Sept 20 kernel: >>>>>>>> >>>>>>>> ath0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0= mtu >>>>>>>> 2290 ether 00:1d:d9:27:5c:e5 >>>>>>>> media: IEEE 802.11 Wireless Ethernet autoselect mode 11g >>>>>>>> status: associated >>>>>>>> wlan0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric = 0 mtu >>>>>>>> 1500 >>>>>>>> ether 00:1d:d9:27:5c:e5 >>>>>>>> inet 172.16.0.7 netmask 0xffffff00 broadcast 172.16.0.255 >>>>>>>> media: IEEE 802.11 Wireless Ethernet DS/5.5Mbps mode 11g >>>>>>>> status: associated >>>>>>>> ssid virus channel 6 (2437 Mhz 11g) bssid 00:1d:7e:51:e1:4d >>>>>>>> regdomain 101 indoor ecm authmode OPEN privacy ON deftxkey 1 >>>>>>>> wepkey 1:40-bit txpower 16 bmiss 7 scanvalid 60 bgscan >>>>>>>> bgscanintvl 300 >>>>>>>> bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme burst >>>>>>>> >>>>>>>> Same parts of the dmesg form Sept 20 kernel. >>>>>>>> >>>>>>>> ath_hal: 0.10.5.10 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, >>>>>>>> RF2413, RF5413, RF2133, RF2425, RF2417) >>>>>>>> >>>>>>>> ath0: <Atheros 5424/2424> mem 0xd0400000-0xd040ffff irq 19 at devic= e >>>>>>>> 0.0 on pci5 >>>>>>>> ath0: [ITHREAD] >>>>>>>> ath0: WARNING: using obsoleted if_watchdog interface >>>>>>>> ath0: mac 14.2 phy 7.0 radio 10.2 >>>>>>>> >>>>>>>> >>>>>>> Does it work w/o WEP? Do you any crypto errors show up in wlanstats >>>>>>> and/or athstats output? >>>>>>> >>>>>>> Sam >>>>>>> >>>>>>> >>>>>> I haven't tried it and I should have since I'm pretty sure that it is >>>>>> something external. I've got travel in a few minutes but I'll do it >>>>>> tomorrow on my AP at home to not interrupt anyone. >>>>>> >>>>>> >>>>> Good morning, Sam. I just disabled encryption on my router and >>>>> changed my rc.conf to >>>>> ifconfig_wlan0=3D"DHCP ssid virus2" >>>>> and as you probably knew, it works flawlessly. >>>>> >>>>> Now I have to ask, what I can do about wep that works on my Sept 20 >>>>> and earlier kernels and doesn't work on my recent kernels? >>>>> >>>>> Thanks, >>>>> >>>>> ed >>>>> >>>>> >>>> I don't know it this is related, but something changed with the WEP-key >>>> index. On my EeePC I had to change my wpa_supplicant.conf file to use >>>> wep_tx_keyidx=3D0 and wep_key0=3Dmywepkey before I could get it to work= . I the >>>> past it always worked with wep_tx_keyidx=3D1 and wep_key1=3Dxxxxx. >>>> >>>> The funny thing is that ifconfig reports it as deftxkey 1 and wepkey 1 = if >>>> I use index 0 in wpa_supplicant and ifconfig will report deftxkey 2 and >>>> wepkey 2 if I use index 1 in wpa_supplicant.conf >>>> >>>> >>> I believe it has always been true that key indices reported by ifconfig = are >>> in the rage [1..4] while wpa_supplicant key indices specified in the con= fig >>> file are [0..3]. I don't recall anything changing in that area for a lo= ng >>> time but I did make changes to the net80211 crypto code around that time= . >>> >>> Sam >>> >> >> Thanks, Sam. What worries me is that I seem to be alone with this proble= m. >> > > This should be fixed by r184063. Please let me know if it does not =20 > and sorry for taking so long to look at the problem. > > Sam Sam, thanks so much. It works perfectly. I just cvsuped and rebuilt =20 all and rebooted and no problem what so ever with WEP plus it gave me =20 the opportunity to learn more about the new wlan0, WEP and WPA. Thanks, again. ed
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081020160046.17qwm4xcsbdws40k4>