This version is no longer supported. If this is still reproducible on a
newer/supported version, please reopen.


** Changed in: linux (Ubuntu)
       Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/180659

Title:
  No Bluetooth Device Detected in hcitool dev

Status in Linux:
  New
Status in bluez-utils package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  My TOSHIBA Satellite A100 has a built-in Bluetooth device (so I
  suppose this must be a PCI hw), and the wireless adapter has an
  external switch for turning on/off. The problem is that no device is
  found in "hcitool dev". I dont find anything related to Bluetooth in
  lspci. It sometimes works fine when I restart the system for ten
  times, but other times I can't get it to work, no matter how many
  times I restart the Bluetooth daemon or turn it off and on again. It
  works absolutely fine in Win XP. I also get no results from hciconfig,
  however the following lines are present in dmesg when the system
  starts up

  [   21.100000] Failure registering capabilities with primary security module.
  [   21.280000] Bluetooth: Core ver 2.11
  [   21.280000] NET: Registered protocol family 31
  [   21.280000] Bluetooth: HCI device and connection manager initialized
  [   21.280000] Bluetooth: HCI socket layer initialized
  [   21.292000] Bluetooth: L2CAP ver 2.8
  [   21.292000] Bluetooth: L2CAP socket layer initialized
  [   21.340000] Bluetooth: RFCOMM socket layer initialized
  [   21.340000] Bluetooth: RFCOMM TTY layer initialized
  [   21.340000] Bluetooth: RFCOMM ver 1.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/180659/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to