From owner-freebsd-questions@FreeBSD.ORG Sun Feb 7 08:38:27 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59CC9106566C for ; Sun, 7 Feb 2010 08:38:27 +0000 (UTC) (envelope-from james@colannino.org) Received: from smtp1.es.uci.edu (smtp1.es.uci.edu [128.200.80.34]) by mx1.freebsd.org (Postfix) with ESMTP id 2D30D8FC08 for ; Sun, 7 Feb 2010 08:38:26 +0000 (UTC) Received: from [192.168.1.100] (69-12-176-48.dsl.static.sonic.net [69.12.176.48]) (authenticated bits=0) by smtp1.es.uci.edu (8.13.1/8.13.1) with ESMTP id o178cOhq031056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 7 Feb 2010 00:38:25 -0800 X-UCInetID: jcolanni Message-ID: <4B6E7C00.60203@colannino.org> Date: Sun, 07 Feb 2010 00:38:24 -0800 From: James Colannino User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: The Atheros 9285 patch on 8.0-stable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Feb 2010 08:38:27 -0000 Hey everyone, I have an Asus EEE PC 1005HA, which has an Atheros 9285 wireless chipset. I discovered that Rui Paulo wrote a driver, and put up a patch for the 8.0 stable kernel here: http://people.freebsd.org/~rpaulo/ar9285_stable_8.diff It seems to have worked for some people. After patching and re-compiling my kernel, it did manage to detect the device on my machine, but unfortunately, I'm unable to scan for networks or associate with my network. Here's what happens: The machine boots, and I see the ath0 interface when I run ifconfig. I then run the command 'ifconfig wlan0 create wlandev ath0' and successfully create wlan0. However, when I run the command 'ifconfig wlan0 scan', the command doesn't seem to do anything, and I eventually have to CTRL-C it. Has anybody else had this problem? Is it a known issue? Maybe I'm doing something wrong? It was mentioned that testers were needed for this driver, and I'd love to help out if possible. If anybody wants me to send any additional information, just let me know. Thanks so much everyone! James