Bug#756947: unble to re-enable wifi/bt after hardware or software disable
removing hp_wmi seems to do the trick. After removing the module, I tried all of the software switches in all of the combinations for both wifi and bt, as well as the hardware switch. This included airplane mode. All seems to be okay, in that I can then re-enable the radio(s) by the various switches. One thing I did notice is that sw switch for airplane mode does not disable bt - I thought it used to do so, but I am not sure. Thanks, Al On Sun, 2014-08-24 at 14:44 -0700, Ben Hutchings wrote: > On Tue, 2014-08-19 at 00:32 +0200, Tomasz Nitecki wrote: > > On 18/08/14 21:10, Ben Hutchings wrote: > > > Older Intel wifi controllers don't include Bluetooth, so any mechanism > > > that affects both wifi and BT must be implemented elsewhere. So this > > > can't be a (wifi) firmware bug. > > > > Hey, > > > > It appears that the Bluetooth problem was just a false lead and > > Bluetooth is not affected by this issue: > > OK. > > > On 08/08/14 03:41, Alan Wilson wrote: > > > Bluetooth seems to be behaving itself since I re-installed the > > > firmware. It can be switched by both hardware and software back and > > > forth - behaves as it ought. > > > > That's why I didn't mention Bluetooth in my summary. I should have > > probably clearly stated that it not affected, despite being mentioned in > > the original bug report - sorry for that. Only a WiFi seems to be > > problematic. > > Even if this is a ipw2200 firmware bug, there will be no more updates to > that firmware so the problem can only be solved by a workaround in the > kernel. > > Alan, can you test what happens if you try to switch wifi off and on > while the hp_wmi driver is not loaded (i.e. run 'rmmod hp_wmi' before > testing)? > > Ben. > -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1409018140.5921.3.camel@debian1
Bug#756947: unble to re-enable wifi/bt after hardware or software disable
On Tue, 2014-08-19 at 00:32 +0200, Tomasz Nitecki wrote: > On 18/08/14 21:10, Ben Hutchings wrote: > > Older Intel wifi controllers don't include Bluetooth, so any mechanism > > that affects both wifi and BT must be implemented elsewhere. So this > > can't be a (wifi) firmware bug. > > Hey, > > It appears that the Bluetooth problem was just a false lead and > Bluetooth is not affected by this issue: OK. > On 08/08/14 03:41, Alan Wilson wrote: > > Bluetooth seems to be behaving itself since I re-installed the > > firmware. It can be switched by both hardware and software back and > > forth - behaves as it ought. > > That's why I didn't mention Bluetooth in my summary. I should have > probably clearly stated that it not affected, despite being mentioned in > the original bug report - sorry for that. Only a WiFi seems to be > problematic. Even if this is a ipw2200 firmware bug, there will be no more updates to that firmware so the problem can only be solved by a workaround in the kernel. Alan, can you test what happens if you try to switch wifi off and on while the hp_wmi driver is not loaded (i.e. run 'rmmod hp_wmi' before testing)? Ben. -- Ben Hutchings Everything should be made as simple as possible, but not simpler. - Albert Einstein signature.asc Description: This is a digitally signed message part
Bug#756947: unble to re-enable wifi/bt after hardware or software disable
On 18/08/14 21:10, Ben Hutchings wrote: > Older Intel wifi controllers don't include Bluetooth, so any mechanism > that affects both wifi and BT must be implemented elsewhere. So this > can't be a (wifi) firmware bug. Hey, It appears that the Bluetooth problem was just a false lead and Bluetooth is not affected by this issue: On 08/08/14 03:41, Alan Wilson wrote: > Bluetooth seems to be behaving itself since I re-installed the > firmware. It can be switched by both hardware and software back and > forth - behaves as it ought. That's why I didn't mention Bluetooth in my summary. I should have probably clearly stated that it not affected, despite being mentioned in the original bug report - sorry for that. Only a WiFi seems to be problematic. Regards, T. signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#756947: unble to re-enable wifi/bt after hardware or software disable
Processing control commands: > reassign -1 src:linux 3.2.60-1+deb7u3 Bug #756947 [firmware-ipw2x00] general: unble to re-enable wifi/bt after hardware or software disable Bug reassigned from package 'firmware-ipw2x00' to 'src:linux'. No longer marked as found in versions firmware-nonfree/0.36+wheezy.1. Ignoring request to alter fixed versions of bug #756947 to the same values previously set Bug #756947 [src:linux] general: unble to re-enable wifi/bt after hardware or software disable Marked as found in versions linux/3.2.60-1+deb7u3. -- 756947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756947 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b756947.140838905731578.transcr...@bugs.debian.org
Bug#756947: unble to re-enable wifi/bt after hardware or software disable
Control: reassign -1 src:linux 3.2.60-1+deb7u3 On Fri, 2014-08-15 at 01:35 +0200, Tomasz Nitecki wrote: > tags 756947 - moreinfo > reassign 756947 firmware-ipw2x00 > found 756947 0.36+wheezy.1 [...] Older Intel wifi controllers don't include Bluetooth, so any mechanism that affects both wifi and BT must be implemented elsewhere. So this can't be a (wifi) firmware bug. The bug is probably in the rfkill driver (specifically hp_wmi in this case), or else it's in the BIOS and needs to be worked around in that driver. I'm assuming you use the latest kernel version. Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity. signature.asc Description: This is a digitally signed message part
