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

2010-02-07 Thread strk
On Sat, Feb 06, 2010 at 06:54:44PM -0600, Larry Finger wrote: You can get the wireless-compat sources for kernel 2.6.26 and build that. Othersise, go to kernel.org and get the full sources. I opted for an upgrade first (debian lenny to debian squeeze). So I'm now at kernel version 2.6.32 and

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

2010-02-07 Thread Rafał Miłecki
2010/2/7 strk s...@keybit.net: On Sat, Feb 06, 2010 at 06:54:44PM -0600, Larry Finger wrote: You can get the wireless-compat sources for kernel 2.6.26 and build that. Othersise, go to kernel.org and get the full sources. I opted for an upgrade first (debian lenny to debian squeeze). So I'm

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

2010-02-07 Thread Michael Buesch
On Sunday 07 February 2010 13:48:59 Rafał Miłecki wrote: 2010/2/7 strk s...@keybit.net: On Sat, Feb 06, 2010 at 06:54:44PM -0600, Larry Finger wrote: You can get the wireless-compat sources for kernel 2.6.26 and build that. Othersise, go to kernel.org and get the full sources. I opted

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

2010-02-07 Thread Rafał Miłecki
2010/2/7 Michael Buesch m...@bu3sch.de: On Sunday 07 February 2010 13:48:59 Rafał Miłecki wrote: 2010/2/7 strk s...@keybit.net: On Sat, Feb 06, 2010 at 06:54:44PM -0600, Larry Finger wrote: You can get the wireless-compat sources for kernel 2.6.26 and build that. Othersise, go to

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

2010-02-07 Thread Michael Buesch
On Sunday 07 February 2010 14:18:43 Rafał Miłecki wrote: So pressing something like Fn+FX can eventually be handled by BIOS and can cause hardware (physical) enabling radio? Yeah, could be the case. It could also be handled by another kernel driver (wmi). In no case will the wireless driver be

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

2010-02-07 Thread Rafał Miłecki
W dniu 7 lutego 2010 14:22 użytkownik Michael Buesch m...@bu3sch.de napisał: On Sunday 07 February 2010 14:18:43 Rafał Miłecki wrote: So pressing something like Fn+FX can eventually be handled by BIOS and can cause hardware (physical) enabling radio? Yeah, could be the case. It could also be

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

2010-02-07 Thread strk
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 be laptops with broadcom cards where rfkill can be changed by software. But that's done by other means (BIOS) and the broadcom

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

2010-02-07 Thread Michael Buesch
On Sunday 07 February 2010 15:09:05 Rafał Miłecki wrote: W dniu 7 lutego 2010 14:22 użytkownik Michael Buesch m...@bu3sch.de napisał: On Sunday 07 February 2010 14:18:43 Rafał Miłecki wrote: So pressing something like Fn+FX can eventually be handled by BIOS and can cause hardware (physical)

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

2010-02-07 Thread Michael Buesch
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 be laptops with broadcom cards where rfkill can be changed by software.

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 be

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

2010-02-07 Thread Michael Buesch
On Sunday 07 February 2010 15:44:01 strk wrote: 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

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 Michael Buesch
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 here the situation can be on of these: 1) b43legacy driver is wrong while reading kill switch state

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

2010-02-07 Thread Rafał Miłecki
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 here the situation can be on of these:  1) b43legacy driver is

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

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

2010-02-07 Thread Larry Finger
On 02/07/2010 05:57 AM, strk wrote: On Sat, Feb 06, 2010 at 06:54:44PM -0600, Larry Finger wrote: You can get the wireless-compat sources for kernel 2.6.26 and build that. Othersise, go to kernel.org and get the full sources. I opted for an upgrade first (debian lenny to debian squeeze).