From owner-freebsd-current@FreeBSD.ORG Sat Sep 20 01:55:50 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 724EB106566C; Sat, 20 Sep 2008 01:55:50 +0000 (UTC) (envelope-from bsd@fluffles.net) Received: from mail.fluffles.net (fluffles.net [80.69.95.190]) by mx1.freebsd.org (Postfix) with ESMTP id 387DB8FC1A; Sat, 20 Sep 2008 01:55:50 +0000 (UTC) (envelope-from bsd@fluffles.net) Received: from [10.10.0.2] (cust.95.160.adsl.cistron.nl [195.64.95.160]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: info@fluffles.net) by mail.fluffles.net (Postfix) with ESMTP id F0DA0B2A1F1; Sat, 20 Sep 2008 03:41:43 +0200 (CEST) Message-ID: <48D4552A.6080502@fluffles.net> Date: Sat, 20 Sep 2008 03:43:06 +0200 From: "fluffles.net" User-Agent: Thunderbird 2.0.0.16 (X11/20080724) MIME-Version: 1.0 To: =?UTF-8?B?QXNoaXNoIFNodWtsYSDgpIbgpLbgpYDgpLcg4KS24KWB4KSV4KWN4KSy?= References: <87bpyjkc6p.fsf@chateau.d.lf> <48D4292B.3010908@freebsd.org> <873ajvk9uk.fsf@chateau.d.lf> In-Reply-To: <873ajvk9uk.fsf@chateau.d.lf> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: Sam Leffler , freebsd-current@freebsd.org Subject: Re: Setting up atheros (168c:001c) wireless NIC in FreeBSD 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, 20 Sep 2008 01:55:50 -0000 Ashish Shukla आशीष शुक्ल wrote: > Sam Leffler writes: > > >> amd64 or i386? >> > > sorry, I forgot to mention, I'm running FreeBSD 8.0-CURRENT on amd64 > architecture built from a /usr/src checked out few hours ago. > I've been having the same problems with Dell 167G USB Wlan dongle using the "rum" driver. Also recent 8-CUR amd64. I cannot do a SSID scan because it returns me: ifconfig: unable to get scan results Just like you. So this appears not to be related to the actual ath driver. Hope any knows about a workaround or solution. Regards, Veronica