Bug#756947: unble to re-enable wifi/bt after hardware or software disable

2014-08-25 Thread Alan Wilson
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 swit

Bug#756947: unble to re-enable wifi/bt after hardware or software disable

2014-08-24 Thread Ben Hutchings
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, > >

Bug#756947: unble to re-enable wifi/bt after hardware or software disable

2014-08-18 Thread Tomasz Nitecki
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

Bug#756947: unble to re-enable wifi/bt after hardware or software disable

2014-08-18 Thread Ben Hutchings
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

Bug#756947: unble to re-enable wifi/bt after hardware or software disable

2014-08-14 Thread Tomasz Nitecki
tags 756947 - moreinfo reassign 756947 firmware-ipw2x00 found 756947 0.36+wheezy.1 thanks Hey, A quick summary of the problem: Alan is using '02:04.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)' with ipw2200 driver and correctly loaded non-f

Bug#756947: unble to re-enable wifi/bt after hardware or software disable

2014-08-11 Thread Alan Wilson
On Sat, 2014-08-09 at 16:22 +0200, Tomasz Nitecki wrote: > Hey, > > Can you please send that last email to bug tracker too? Anything you > send to 756...@bugs.debian.org will show up in the web browsable version > [1] which will allow more people to look into your problem. As a matter > of fact, I

Bug#756947: unble to re-enable wifi/bt after hardware or software disable

2014-08-11 Thread Alan Wilson
Take two On Sun, 2014-08-10 at 21:58 +0200, Tomasz Nitecki wrote: > Hey, > > > On 10/08/14 01:38, Alan Wilson wrote: > > Hello, > > > > dpkg -s firmware-ipw2x00 | grep Version returns: > > > > 'Version: 0.36+wheezy.1' > > Ok, that is the latest stable version. > > > However, I see neither t

Bug#756947: unble to re-enable wifi/bt after hardware or software disable

2014-08-07 Thread Tomasz Nitecki
Hey, You seem to be using '02:04.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)' with ipw2200 driver (+ correctly loaded non-free firmware blob 'ipw2200-bss.fw') as your wireless card and '03f0:011d Hewlett-Packard Bluetooth 1.2 Interface [Broad

Bug#756947: unble to re-enable wifi/bt after hardware or software disable

2014-08-05 Thread Alan Wilson
no problem, lspci - 00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03) 00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801F

Bug#756947: unble to re-enable wifi/bt after hardware or software disable

2014-08-05 Thread Alan Wilson
dmesg --- [1.005427] NET: Registered protocol family 17 [1.005432] Registering the dns_resolver key type [1.005455] Using IPI No-Shortcut mode [1.00] PM: Hibernation image not present or could not be loaded. [1.005566] registered taskstats version 1

Bug#756947: unble to re-enable wifi/bt after hardware or software disable

2014-08-04 Thread Tomasz Nitecki
tags 756947 + moreinfo thanks Hey, Al, can you please provide us with some more information about your system? It would help if you could attach the output of 'lspci', 'lsusb', 'lsmod' and 'dmesg' commands. You should run 'dmesg' only after the problem occurred. Regards, T. signature.asc De