Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 17 Aug 2012 11:00:46 +0200
From:      Bernhard Schmidt <bschmidt@techwires.net>
To:        Adrian Chadd <adrian.chadd@gmail.com>
Cc:        freebsd-wireless@freebsd.org, weongyo@freebsd.org
Subject:   Re: [bwn] bcm4311 Acer Aspire One rf switch
Message-ID:  <CAAgh0_ZyrsmM_GWfQQsoGS8ja5z7c%2B3rVn3WUtTaejfH4gRnZw@mail.gmail.com>
In-Reply-To: <CAJ-Vmokd-hhEMGp6nCA9sb1KNoJV-t83UtLMCATHANZb1h%2BpOA@mail.gmail.com>
References:  <CAPXGr9thqx%2BBK2RBMeKWHnebm3as9s3iXOodmPt715%2BjMYyS1Q@mail.gmail.com> <CAJ-Vmokd-hhEMGp6nCA9sb1KNoJV-t83UtLMCATHANZb1h%2BpOA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Aug 12, 2012 at 4:54 AM, Adrian Chadd <adrian.chadd@gmail.com> wrote:
> Irs very likely an acpi problem. Therell be some IO line hooked in that
> acpi controls.

Not sure about that, the Linux driver polls the hardware for the RF
kill state, that smells like that there is no event at all.

> On Aug 11, 2012 7:02 PM, "skydrome" <chris2603@gmail.com> wrote:
>
>> I have the same setup as this person here
>> http://forums.freebsd.org/archive/index.php/t-29407.html
>>
>> the exactly problem is when issuing:
>> wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf
>>
>> RF Switch LED on laptop blinks once and i receive message:
>> bwn0: firmware version (rev 410 patch 2160 date 0x751a time 0x7c0a)
>> wlan0: ieee80211_new_state_locked: pending INIT -> SCAN transition lost
>> bwn0: status of RF switch is changed to OFF
>> bwn0: please turn on the RF switch
>>
>> Now the problem is is that the aspire one bios has no bios control for
>> explicitly en|dis|abling the rf switch, in fact, i cannot turn it off.
>> When i switch it, it remains on (light is on)
>>
>> Ive tried editing if_bwn.c, removing the check for rf_onoff() but to
>> no avail, ill have to read the source more in depth.
>> I wonder what else i can do to resolve this issue.
>>
>> Extra Info:
>> on linux (specifically archlinux), the rf switch doesnt do anything,
>> doesnt even trigger a acpi event. On fbsd no acpi event is trigger
>> either (debug.acpi.enabel_debug_object=1)

Does it make a difference if you reload the driver? eg. unload the
module, change switch state, reload driver?

-- 
Bernhard



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAAgh0_ZyrsmM_GWfQQsoGS8ja5z7c%2B3rVn3WUtTaejfH4gRnZw>