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 if it
Larry Finger wrote:
There could be a bug in the software that processes whatever WMI
info that your system generates. WMI (Windows Management Interface)
code handles the functions of the top row of your keyboard that are
generated by a fn+FX key.
The BIOS is rarely if ever involved in any of
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
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
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
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
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
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
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
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)
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.
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
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
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
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
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
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
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).
On 02/06/2010 01:08 PM, strk wrote:
Hi everybody,
my excuses in advance for asking something which was likely
asked a lot more in the past.
I just switched to usin b43legacy from bmcxxx (from linux 2.6.18
to linux 2.6.26) and am having some problems with the wireless
card. In particular I
On Sat, Feb 06, 2010 at 02:43:36PM -0600, Larry Finger wrote:
After bcm43xx was split into b43 and b43legacy, both were upgraded to take
account of the computers radio kill switch. Changes in the hardware switch
input are causing the Radio hardware ENABLED/DISABLED messages.
How does the
[ 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 a
On 02/06/2010 03:14 PM, strk wrote:
On Sat, Feb 06, 2010 at 02:43:36PM -0600, Larry Finger wrote:
After bcm43xx was split into b43 and b43legacy, both were upgraded to take
account of the computers radio kill switch. Changes in the hardware switch
input are causing the Radio hardware
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
/\
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 ?
On 02/06/2010 06:49 PM, strk wrote:
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
25 matches
Mail list logo
