← Back to team overview

kernel-packages team mailing list archive

[Bug 513777] Re: Karmic (9.10): bluetooth initialized but unavailable, Toshiba Satellite U400-24K

 

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux (Ubuntu)
       Status: New => Confirmed

-- 
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/513777

Title:
  Karmic (9.10): bluetooth initialized but unavailable, Toshiba
  Satellite U400-24K

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: udev-extras

  /var/log/kern.log:
  Jan 28 15:55:00 gvs kernel: [    0.000000] Linux version 2.6.31-18-generic (buildd@rothera) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #55-Ubuntu SMP Fri Jan 8 14:55:26 UTC 2010 (Ubuntu 2.6.31-18.55-generic)
  ...
  Jan 28 15:55:00 gvs kernel: [    0.000000] DMI present.
  ...
  Jan 28 15:55:00 gvs kernel: [    0.000000] ACPI: BIOS bug: multiple APIC/MADT found, using 0
  Jan 28 15:55:00 gvs kernel: [    0.000000] ACPI: If "acpi_apic_instance=2" works better, notify linux-acpi@xxxxxxxxxxxxxxx
  ...
  Jan 28 15:55:00 gvs kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.31-18-generic root=UUID=63e1b95c-d691-43c1-b4ad-00e764e73296 ro quiet splash
  ...
  Jan 28 15:55:00 gvs kernel: [    1.359147] PCI: Using ACPI for IRQ routing
  Jan 28 15:55:00 gvs kernel: [    1.359147] pci 0000:00:1c.0: BAR 13: can't allocate resource
  Jan 28 15:55:00 gvs kernel: [    1.359147] pci 0000:00:1c.0: BAR 14: can't allocate resource
  Jan 28 15:55:00 gvs kernel: [    1.359147] pci 0000:00:1c.0: BAR 15: can't allocate resource
  Jan 28 15:55:00 gvs kernel: [    1.359147] pci 0000:00:1c.4: BAR 13: can't allocate resource
  Jan 28 15:55:00 gvs kernel: [    1.359147] pci 0000:00:1c.4: BAR 14: can't allocate resource
  Jan 28 15:55:00 gvs kernel: [    1.359147] pci 0000:00:1c.4: BAR 15: can't allocate resource
  Jan 28 15:55:00 gvs kernel: [    1.359147] pci 0000:00:1c.5: BAR 13: can't allocate resource
  Jan 28 15:55:00 gvs kernel: [    1.359147] pci 0000:00:1c.5: BAR 14: can't allocate resource
  Jan 28 15:55:00 gvs kernel: [    1.359147] pci 0000:00:1c.5: BAR 15: can't allocate resource
  Jan 28 15:55:00 gvs kernel: [    1.368009] Bluetooth: Core ver 2.15
  Jan 28 15:55:00 gvs kernel: [    1.368021] NET: Registered protocol family 31
  Jan 28 15:55:00 gvs kernel: [    1.368021] Bluetooth: HCI device and connection manager initialized
  Jan 28 15:55:00 gvs kernel: [    1.368021] Bluetooth: HCI socket layer initialized
  Jan 28 15:55:00 gvs kernel: [    1.368021] NetLabel: Initializing
  ...
  Jan 28 15:55:00 gvs kernel: [    2.279773] NET: Registered protocol family 17
  Jan 28 15:55:00 gvs kernel: [    2.279788] Bluetooth: L2CAP ver 2.13
  Jan 28 15:55:00 gvs kernel: [    2.279790] Bluetooth: L2CAP socket layer initialized
  Jan 28 15:55:00 gvs kernel: [    2.279793] Bluetooth: SCO (Voice Link) ver 0.6
  Jan 28 15:55:00 gvs kernel: [    2.279794] Bluetooth: SCO socket layer initialized
  Jan 28 15:55:00 gvs kernel: [    2.279830] Bluetooth: RFCOMM TTY layer initialized
  Jan 28 15:55:00 gvs kernel: [    2.279833] Bluetooth: RFCOMM socket layer initialized
  Jan 28 15:55:00 gvs kernel: [    2.279835] Bluetooth: RFCOMM ver 1.11
  Jan 28 15:55:00 gvs kernel: [    2.280461] Using IPI No-Shortcut mode
  ...
  and that's it. Neither bluez-utils, nor hcitool can find bluetooth devices. Turning killswitch off/on resets WLAN and Bluetooth, but the latter remains unavailable. Tried omnibook module from trunk, unsuccessfully (didn't recognized chipset). Tried 2.6.32-6 kernel with the same effect. Didn't succeed with hid2hci 'cause didn't find proper options.

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