From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 00:13:21 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 768EF16A41F; Sun, 1 Jan 2006 00:13:21 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id EABC843D48; Sun, 1 Jan 2006 00:13:20 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id k010DFo7001277 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 31 Dec 2005 16:13:17 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <43B71EF7.2010803@errno.com> Date: Sat, 31 Dec 2005 16:14:47 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051227) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bill Paul References: <20051231212858.9F9D116A420@hub.freebsd.org> In-Reply-To: <20051231212858.9F9D116A420@hub.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Ondra Holecek , freebsd-acpi@freebsd.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: problems with wifi 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: Sun, 01 Jan 2006 00:13:21 -0000 Bill Paul wrote: >>yes, i can load if_ath, wireless card is found and i can set it up as >>ath0, but i still have no signal (and there are many ap's - i can see >>with different pcmcia card) > > > Note that if this in fact a problem with ACPI not supporting the > wireless enable switch on your laptop correctly, it won't work > with the NDISulator any better than it will with the ath(4) driver. > I think the wireless enable switch controls the connection to the > antenna(s), and is a separate device from the NIC itself that varies > in implementation depending on the laptop. The NDIS driver only knows > how to manipulate the NIC hardware: the NIC manufacturer can't really > customize the driver for each laptop out there (and the laptop > manufacturers usually don't customize the drivers either, beyond > sticking their logo on them). <...ndis related stuff deleted...> Handling this in the ath driver is actually very simple; I've just never done it 'cuz none of my laptops have the this setup to test with. When you hit the switch the driver gets an interrupt from the ath card and can then toggle the state of the rfkill pin. If you run the latest code out for testing there is also a sysctl that you can use to control this manually. Sam