Re: b43legacy-phy3: Radio hardware status changed to XXX

2010-02-20 Thread strk
On Sun, Feb 07, 2010 at 05:45:30PM +0100, strk wrote: On Sun, Feb 07, 2010 at 04:27:02PM +0100, RafaÅ? MiÅ?ecki wrote: 2010/2/7 Michael Buesch m...@bu3sch.de: We are not going to add module options to workaround bugs. We fix the bug instead. ++ Please test first

Re: b43legacy-phy3: Radio hardware status changed to XXX

2010-02-07 Thread strk
to turn it on. Same suggestions applies ? Or was some load-time option added in 2.6.32 ? --strk; () Free GIS Flash consultant/developer /\ http://foo.keybit.net/~strk/services.html ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de

Re: b43legacy-phy3: Radio hardware status changed to XXX

2010-02-07 Thread strk
hardware doesn't know about it.) Uhm, but still I'm pretty sure there's no physical switch on this laptop (L5800C). Also, if there was one, surely I wasn't turning it on and off continuosly to justify those notices coming down to b43legacy. Note that bcm43xx used to work fine. --strk

Re: b43legacy-phy3: Radio hardware status changed to XXX

2010-02-07 Thread strk
On Sun, Feb 07, 2010 at 03:37:36PM +0100, Michael Buesch wrote: On Sunday 07 February 2010 15:30:18 strk wrote: On Sun, Feb 07, 2010 at 02:05:09PM +0100, Michael Buesch wrote: rfkill is a hardware lock in the case of broadcom. Software can only read the state. (There may

Re: b43legacy-phy3: Radio hardware status changed to XXX

2010-02-07 Thread strk
On Sun, Feb 07, 2010 at 03:48:07PM +0100, Michael Buesch wrote: On Sunday 07 February 2010 15:44:01 strk wrote: Ok, so supposedly here the situation can be on of these: 1) b43legacy driver is wrong while reading kill switch state 2) something (software) is toggling kill switch

Re: b43legacy-phy3: Radio hardware status changed to XXX

2010-02-07 Thread strk
On Sun, Feb 07, 2010 at 04:27:02PM +0100, RafaÅ? MiÅ?ecki wrote: 2010/2/7 Michael Buesch m...@bu3sch.de: On Sunday 07 February 2010 15:59:53 strk wrote: On Sun, Feb 07, 2010 at 03:48:07PM +0100, Michael Buesch wrote: On Sunday 07 February 2010 15:44:01 strk wrote: Ok, so supposedly

test

2010-02-06 Thread strk
Is it me or this list is misconfigured ? --srrk; ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

b43legacy-phy3: Radio hardware status changed to XXX

2010-02-06 Thread strk
or fix ? Thanks in advance. --strk; () Free GIS Flash consultant/developer /\ http://foo.keybit.net/~strk/services.html ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

b43legacy-phy3: Radio hardware status changed to XXX

2010-02-06 Thread strk
or fix ? Thanks in advance. --strk; () Free GIS Flash consultant/developer /\ http://foo.keybit.net/~strk/services.html ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Re: b43legacy-phy3: Radio hardware status changed to XXX

2010-02-06 Thread strk
://lists.berlios.de/pipermail/bcm43xx-dev/2008-November/004843.html ... but the thread has no happy end (I add the author of that post in Cc). Jorge, have you figured it out lately ? -- () Free GIS Flash consultant/developer /\ http://foo.keybit.net/~strk/services.html

Re: b43legacy-phy3: Radio hardware status changed to XXX

2010-02-06 Thread strk
[ sorry for repost, Jorge wasn't in recipient list ] On Sat, Feb 06, 2010 at 10:14:12PM +0100, strk wrote: On Sat, Feb 06, 2010 at 02:43:36PM -0600, Larry Finger wrote: How does the ASUS implement that switch? Some laptops have a slide switch with an on/off position, while others have

Re: b43legacy-phy3: Radio hardware status changed to XXX

2010-02-06 Thread strk
On Sat, Feb 06, 2010 at 06:20:15PM -0600, Larry Finger wrote: You could probably avoid the problems by disabling the RFKILL and RFKILL_INPUT options. How do I do that ? Runtime ? Compile-time ? --strk; () Free GIS Flash consultant/developer /\ http://foo.keybit.net/~strk

Re: b43legacy-phy3: Radio hardware status changed to XXX

2010-02-06 Thread strk
On Sat, Feb 06, 2010 at 06:29:03PM -0600, Larry Finger wrote: On 02/06/2010 06:22 PM, strk wrote: On Sat, Feb 06, 2010 at 06:20:15PM -0600, Larry Finger wrote: You could probably avoid the problems by disabling the RFKILL and RFKILL_INPUT options. How do I do that ? Runtime