From owner-freebsd-current@FreeBSD.ORG Sat Oct 4 03:45:05 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 063DB1065686 for ; Sat, 4 Oct 2008 03:45:05 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id BD5808FC16 for ; Sat, 4 Oct 2008 03:45:04 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m943j3c3050896 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Oct 2008 20:45:03 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <48E6E6BF.2020908@freebsd.org> Date: Fri, 03 Oct 2008 20:45:03 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: =?UTF-8?B?QXNoaXNoIFNodWtsYSDgpIbgpLbgpYDgpLcg4KS24KWB4KSV4KWN4KSy?= References: <20080929173223.183035ohkgl7jk3b@econet.encontacto.net> <20080930054432.GB5863@chateau.d.lf> <48E24842.4070409@freebsd.org> <87bpy5imh8.fsf@chateau.d.lf> <48E3A944.3030809@freebsd.org> <8763oct2u8.fsf@chateau.d.lf> <871vyze15z.fsf@chateau.d.lf> In-Reply-To: <871vyze15z.fsf@chateau.d.lf> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: freebsd-current Subject: Re: I lost ath0 support on current sometime between Sept 20 and Sept 26. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Oct 2008 03:45:05 -0000 Ashish Shukla आशीष शुक्ल wrote: > Ashish Shukla आशीष शुक्ल writes: > > >> At the moment, I'm not on my FreeBSD box, but as soon as I boot into my >> FreeBSD box, I'll verify it and will try rebuilding my kernel and >> world. >> > > Following is the output of dmesg, after I manually loaded ath_hal and > if_ath.ko: > > ---->8---->8---- > ath_hal: 0.10.5.10 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425, RF2417) > ath0: mem 0x91300000-0x9130ffff irq 16 at device 0.0 on pci1 > ath0: [ITHREAD] > ath0: WARNING: using obsoleted if_watchdog interface > ath0: mac 14.2 phy 7.0 radio 10.2 > wlan0: Ethernet address: 00:1f:3a:1a:50:b3 > wlan0: link state changed to UP > <...snip...> > abbe [~] monte-cristo% ifconfig > rl0: flags=8843 metric 0 mtu 1500 > options=8 > ether 00:1b:38:ea:5c:76 > inet6 fe80::21b:38ff:feea:5c76%rl0 prefixlen 64 scopeid 0x2 > inet6 fdcf:425d:3151::3 prefixlen 48 > media: Ethernet autoselect (none) > status: no carrier > lo0: flags=8049 metric 0 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 > ath0: flags=8843 metric 0 mtu 2290 > ether 00:1f:3a:1a:50:b3 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: associated > wlan0: flags=8843 metric 0 mtu 1500 > ether 00:1f:3a:1a:50:b3 > inet6 fe80::21f:3aff:fe1a:50b3%wlan0 prefixlen 64 scopeid 0x4 > inet 172.16.0.7 netmask 0xffffffe0 broadcast 172.16.0.31 > media: IEEE 802.11 Wireless Ethernet DS/1Mbps mode 11g > status: associated > ssid 18-B-PARVATIYA channel 6 (2437 Mhz 11g) bssid 00:1e:2a:76:f4:60 > regdomain 103 indoor ecm authmode WPA2/802.11i privacy ON > deftxkey UNDEF txpower 16 bmiss 7 scanvalid 450 bgscan bgscanintvl 300 > bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme burst > roaming MANUAL > abbe [~] monte-cristo% sudo ifconfig wlan0 scan > Password: > SSID BSSID CHAN RATE S:N INT CAPS > rpok 00:14:d1:41:ae:d6 1 54M -149:-96 100 EPS RSN WPS > 18-B-PARVATIYA 00:1e:2a:76:f4:60 6 54M -64:-96 100 EPS RSN WME ATH > linksys 00:18:f8:7b:66:47 6 54M -92:-96 100 EP > I've lost track of what you've tried. Try to simplify your configuration to isolate what is causing the problem. For example, disable WPA and see if you can associate and pass traffic. If that works then we know this is a crypto problem. If you cannot setup an open association then I probably need a packet trace from a 3rd station to see what's happening. I have the same card and it works fine for me. The only difference is my laptops are UP. Sam