Description of problem: When I plug in USB Bluetooth dongle BCM92045B3 ROM bluetoothd fails with the following message: May 21 22:43:21 localhost bluetoothd[8255]: Can't init device hci1: Operation not possible due to RF-kill (132) Version-Release number of selected component (if applicable): How reproducible: Plugin USB Bluetooth dongle BCM92045B3 ROM in any USB port. Here's the full messages log: May 21 22:43:21 localhost kernel: [ 6921.884074] usb 2-3: new full-speed USB device number 5 using ohci_hcd May 21 22:43:21 localhost kernel: [ 6922.040140] usb 2-3: New USB device found, idVendor=0a5c, idProduct=2101 May 21 22:43:21 localhost kernel: [ 6922.040147] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 May 21 22:43:21 localhost kernel: [ 6922.040151] usb 2-3: Product: BCM92045B3 ROM May 21 22:43:21 localhost kernel: [ 6922.040154] usb 2-3: Manufacturer: Broadcom Corp May 21 22:43:21 localhost bluetoothd[970]: HCI dev 1 registered May 21 22:43:21 localhost bluetoothd[970]: Listening for HCI events on hci1 May 21 22:43:21 localhost bluetoothd[8255]: Can't init device hci1: Operation not possible due to RF-kill (132) Exact same problem with another USB Bluetooth dongle: May 21 22:58:15 localhost kernel: [ 7815.176061] usb 1-3: new full-speed USB device number 4 using ohci_hcd May 21 22:58:15 localhost kernel: [ 7815.331726] usb 1-3: New USB device found, idVendor=0a5c, idProduct=2101 May 21 22:58:15 localhost kernel: [ 7815.331732] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 May 21 22:58:15 localhost kernel: [ 7815.331736] usb 1-3: Product: BCM2045A May 21 22:58:15 localhost kernel: [ 7815.331740] usb 1-3: Manufacturer: Broadcom Corp May 21 22:58:15 localhost kernel: [ 7815.331742] usb 1-3: SerialNumber: 0002720C4324 May 21 22:58:15 localhost bluetoothd[970]: HCI dev 0 registered May 21 22:58:15 localhost bluetoothd[970]: Listening for HCI events on hci0 May 21 22:58:15 localhost bluetoothd[8827]: Can't init device hci0: Operation not possible due to RF-kill (132)
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
Exact same thing is happening with Mageia 2. Here's the /var/log/messages May 27 23:36:49 localhost kernel: [73597.917046] usb 2-2: new full-speed USB device number 5 using ohci_hcd May 27 23:36:49 localhost kernel: [73598.073106] usb 2-2: New USB device found, idVendor=0a5c, idProduct=2101 May 27 23:36:49 localhost kernel: [73598.073111] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 May 27 23:36:49 localhost kernel: [73598.073116] usb 2-2: Product: BCM92045B3 ROM May 27 23:36:49 localhost kernel: [73598.073119] usb 2-2: Manufacturer: Broadcom Corp May 27 23:36:49 localhost bluetoothd[28772]: HCI dev 0 registered May 27 23:36:49 localhost bluetoothd[28772]: Listening for HCI events on hci0 May 27 23:36:49 localhost bluetoothd[29132]: Can't init device hci0: Operation not possible due to RF-kill (132) Here's the other bluetooth dongle on Mageia 2 May 28 00:21:11 localhost kernel: [76259.974078] usb 2-3: new full-speed USB device number 8 using ohci_hcd May 28 00:21:11 localhost kernel: [76260.131134] usb 2-3: New USB device found, idVendor=0a5c, idProduct=2101 May 28 00:21:11 localhost kernel: [76260.131140] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 May 28 00:21:11 localhost kernel: [76260.131144] usb 2-3: Product: BCM2045A May 28 00:21:11 localhost kernel: [76260.131148] usb 2-3: Manufacturer: Broadcom Corp May 28 00:21:11 localhost kernel: [76260.131150] usb 2-3: SerialNumber: 0002720C4324 May 28 00:21:11 localhost bluetoothd[28772]: HCI dev 0 registered May 28 00:21:11 localhost bluetoothd[28772]: Listening for HCI events on hci0 May 28 00:21:11 localhost bluetoothd[30863]: Can't init device hci0: Operation not possible due to RF-kill (132)
Version: Cauldron => 2
Keywords: NEEDINFO => (none)CC: (none) => sander.lepik
Hi, thanks for reporting this bug. Assigned to the package maintainer. (Please set the status to 'assigned' if you are working on it)
Keywords: (none) => TriagedComponent: Installer => RPM PackagesAssignee: bugsquad => dmorganecSource RPM: (none) => bluez
Assignee: dmorganec => bugsquad
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD