Public bug reported:

On my laptop, a Lenovo T61p I have two radio killswitches. One at the
front, to be considered as a hardware switch and a soft-key (Fn+F5). The
one at the front will disable all radio devices (BT, WLAN and WWAN if
available) and the soft-key will toggle between the different modes
(BT+WLAN, only BT, only WLAN, all off). At least, this was how it was in
Hardy.

Now in Intrepid the situation is as follows.
The hardware radio killswitch at the front will correctly disable all wireless 
devices present. When turning it back off (wireless enabled) only Bluetooth 
comes up. The event isn't even recognized. (see below)

>From syslog (when turning killswitch on)
Oct 25 23:59:18 gert-laptop kernel: [ 4955.195594] iwl3945: Radio Frequency 
Kill Switch is On:
Oct 25 23:59:18 gert-laptop kernel: [ 4955.195599] Kill switch must be turned 
off for wireless networking to work.

>From syslog (when turning killswitch off) 
Oct 25 23:59:29 gert-laptop kernel: [ 4966.480126] usb 1-1: new full speed USB 
device using uhci_hcd and address 4
Oct 25 23:59:29 gert-laptop kernel: [ 4966.647428] usb 1-1: configuration #1 
chosen from 1 choice
Oct 25 23:59:29 gert-laptop bluetoothd[6232]: HCI dev 0 registered
Oct 25 23:59:29 gert-laptop bluetoothd[6232]: HCI dev 0 up

Clearly, I miss a line like 'iwl3945: Radio Frequency Kill Switch is
Off'. I need to do a modprobe -r iwl3945 && modprobe iwl3945 to make
wireless work again.

Now, for the software killswitch: it doesn't even control the WLAN
module, only toggling the bluetooth state. This is inconsistent with
behaviour in Windows, Hardy and the Owner's Manual. It should toggle
between the states as described earlier.

The model of the laptop is T61p 6457, a 15.4" WUXGA display with NVidia
Quadro FX 570M and Intel PRO/Wireless 3945 WLAN.

** Affects: ubuntu
     Importance: Undecided
         Status: New

** Description changed:

  On my laptop, a Lenovo T61p I have two radio killswitches. One at the
  front, to be considered as a hardware switch and a soft-key (Fn+F5). The
  one at the front will disable all radio devices (BT, WLAN and WWAN if
  available) and the soft-key will toggle between the different modes
  (BT+WLAN, only BT, only WLAN, all off). At least, this was how it was in
  Hardy.
  
  Now in Intrepid the situation is as follows.
  The hardware radio killswitch at the front will correctly disable all 
wireless devices present. When turning it back off (wireless enabled) only 
Bluetooth comes up. The event isn't even recognized. (see below)
  
  From syslog (when turning killswitch on)
  Oct 25 23:59:18 gert-laptop kernel: [ 4955.195594] iwl3945: Radio Frequency 
Kill Switch is On:
  Oct 25 23:59:18 gert-laptop kernel: [ 4955.195599] Kill switch must be turned 
off for wireless networking to work.
  
  From syslog (when turning killswitch off) 
  Oct 25 23:59:29 gert-laptop kernel: [ 4966.480126] usb 1-1: new full speed 
USB device using uhci_hcd and address 4
  Oct 25 23:59:29 gert-laptop kernel: [ 4966.647428] usb 1-1: configuration #1 
chosen from 1 choice
  Oct 25 23:59:29 gert-laptop bluetoothd[6232]: HCI dev 0 registered
  Oct 25 23:59:29 gert-laptop bluetoothd[6232]: HCI dev 0 up
  
  Clearly, I miss a line like 'iwl3945: Radio Frequency Kill Switch is
  Off'. I need to do a modprobe -r iwl3945 && modprobe iwl3945 to make
  wireless work again.
  
  Now, for the software killswitch: it doesn't even control the WLAN
  module, only toggling the bluetooth state. This is inconsistent with
  behaviour in Windows, Hardy and the Owner's Manual. It should toggle
  between the states as described earlier.
+ 
+ The model of the laptop is T61p 6457, a 15.4" WUXGA display with NVidia
+ Quadro FX 570M and Intel PRO/Wireless 3945 WLAN.

-- 
[Intrepid] Radio killswitch off-event isn't recognized on Thinkpad T61p
https://bugs.launchpad.net/bugs/289286
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to