Toshiba M60-121 not support for bluetooth

This got my Bluetooth working:

http://ubuntuforums.org/showthread.php?t=560475

Paul got not running the bluetooth with your tutorial, but if this way.
I have dual boot (with XP), and whether active in the bluetooth windows, upon his return to ubuntu that it works.
I think Windows XP takes control at the start of Bluetooth and therefore were not triggered.

Most probably this is a duplicate of #180659.

What error do you get when booting directly to linux and executing the command

sudo toshset -bluetooth on

?

As in the description (the parameter -bluetooth is like -b):
$ sudo toshset -bluetooth on
[sudo] password for shakaran:
required kernel toshiba support not enabled.

If you need any more log tell me.

I would be delighted that this problem is to solve Intrepid.

I've managed to get toshiba_acpi and toshset running on 8.10 - see my post in the forum:
http://ubuntuforums.org/showthread.php?p=6203606#post6203606
Also discussion on bug 269831 - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/269831

I follow step by step the howto of forum, the result:

$ sudo modprobe toshiba_acpi
FATAL: Error inserting toshiba_acpi (/lib/modules/2.6.27-8-generic/kernel/drivers/acpi/toshiba_acpi.ko): Unknown symbol in module, or unknown parameter (see dmesg)

Dmesg (relevant line):
$dmesg
[ 9426.570567] toshiba_acpi: Unknown parameter `hotkeys_over_acpi'

$ sudo toshset -bluetooth on
required kernel toshiba support not enabled.

$ sudo toshset -a
required kernel toshiba support not enabled.

Seems that hotkeys_over_acpi is the problem.

I have enable intrepid-proposed, no changes.

FYI: My model uses a Phoenix BIOS:
sudo dmidecode -t 0
# dmidecode 2.9
SMBIOS 2.34 present.

Handle 0x0000, DMI type 0, 20 bytes
BIOS Information
 Vendor: TOSHIBA
 Version: V1.60
 Release Date: 03/16/2006
 Address: 0xE4F90
 Runtime Size: 110704 bytes
 ROM Size: 512 kB
 Characteristics:
  PCI is supported
  PC Card (PCMCIA) is supported
  PNP is supported
  BIOS is upgradeable
  BIOS shadowing is allowed
  Boot from CD is supported
  Selectable boot is supported
  Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
  Print screen service is supported (int 5h)
  8042 keyboard services are supported (int 9h)
  Serial services are supported (int 14h)
  Printer services are supported (int 17h)
  CGA/mono video services are supported (int 10h)
  ACPI is supported
  USB legacy is supported
  AGP is supported
  Smart battery is supported
  BIOS boot specification is supported

If you need anything more, please tell me, I am waiting a fix (the holy fix) for over 11 months.

The kernel 2.6.27.10-20 in intrepid-proposed doesn't help.

$ sudo modprobe toshiba_acpi
FATAL: Error inserting toshiba_acpi (/lib/modules/2.6.27-10-generic/kernel/drivers/acpi/toshiba_acpi.ko): No such device

$ sudo toshset -b on
required kernel toshiba support not enabled.

My laptop have four years old, I hope that with Ubuntu I can have bluetooth some day befofe that I have that buy a new laptop.

toshset 1.74 is out!

The new changes include:
# now can query wireless status, and enable internal bluetooth adapter.
# now optionally uses the toshiba kernel interface (compile-time flag).

This can help to fix the problem with bluetooth and kernel. In jaunty the last version is 1.73-3

Same here Toshiba M60-182 ubuntu 8.10

dimitris@dimitris-laptop:~$ sudo modprobe toshiba_acpi
FATAL: Error inserting toshiba_acpi (/lib/modules/2.6.27-11-generic/kernel/drivers/acpi/toshiba_acpi.ko): No such device
dimitris@dimitris-laptop:~$ sudo toshset -b on
required kernel toshiba support not enabled.

bluetooth and xd reader notworking

Still not working

dimitris@dimitris-laptop:~$ sudo toshset -b on
required kernel toshiba support not enabled.

dimitris@dimitris-laptop:~$ sudo modprobe toshiba_acpi
FATAL: Error inserting toshiba_acpi (/lib/modules/2.6.31-19-generic/kernel/drivers/platform/x86/toshiba_acpi.ko): No such device

dimitris@dimitris-laptop:~$ uname -a
Linux dimitris-laptop 2.6.31-19-generic #56-Ubuntu SMP Thu Jan 28 01:26:53 UTC 2010 i686 GNU/Linux

Finally fixed in ubuntu 10.10 beta

Linux dimitris-laptop 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:34:50 UTC 2010 i686 GNU/Linux

lsusb
Bus 004 Device 003: ID 0930:0508 Toshiba Corp. Integrated Bluetooth HCI

So this is fixed now? Please confirm which Ubuntu version do you use? Thank you for helping us to make Ubuntu better!

Its fixed since 10.10
Now I am using 12.04 and working fine.

Linux dimitris-laptop 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux

Bus 004 Device 003: ID 0930:0508 Toshiba Corp. Integrated Bluetooth HCI

bluetooth 158438 23 rfcomm,btusb,bnep

I cannot ensure the fix. After 5 year of report this bug, now I have other laptops. For me this is a huge fail of report. When I report a bug it is reasonable wait months or a year for a fix, but 5 years it is a big fail using the software, at least consider this fully unsupported. I am very dissapointed with this.

This issue is still present on my Toshiba Qosmio F60 with Ubuntu 12.10. I need to enable wireless from within Windows 7. Fn+F8 just enables/disables the wireless using soft block under Ubuntu, while the LED light stays on. Wireless still needs to be enabled from within Windows for the soft block to work.

Out put of lsusb:
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 043: ID 0930:0508 Toshiba Corp. Integrated Bluetooth HCI
Bus 001 Device 006: ID 04f2:b130 Chicony Electronics Co., Ltd

Output of lspci -n:
00:00.0 0600: 8086:0044 (rev 12)
00:02.0 0300: 8086:0046 (rev 12)
00:16.0 0780: 8086:3b64 (rev 06)
00:1a.0 0c03: 8086:3b3c (rev 06)
00:1b.0 0403: 8086:3b56 (rev 06)
00:1c.0 0604: 8086:3b42 (rev 06)
00:1c.1 0604: 8086:3b44 (rev 06)
00:1c.2 0604: 8086:3b46 (rev 06)
00:1c.3 0604: 8086:3b48 (rev 06)
00:1c.5 0604: 8086:3b4c (rev 06)
00:1d.0 0c03: 8086:3b34 (rev 06)
00:1e.0 0604: 8086:2448 (rev a6)
00:1f.0 0601: 8086:3b09 (rev 06)
00:1f.2 0106: 8086:3b29 (rev 06)
00:1f.6 1180: 8086:3b32 (rev 06)
01:00.0 0805: 1180:e822 (rev 01)
01:00.1 0880: 1180:e230 (rev 01)
02:00.0 0280: 10ec:8172 (rev 10)
03:00.0 0480: 102f:01ba (rev 01)
05:00.0 0200: 10ec:8168 (rev 03)
ff:00.0 0600: 8086:2c62 (rev 02)
ff:00.1 0600: 8086:2d01 (rev 02)
ff:02.0 0600: 8086:2d10 (rev 02)
ff:02.1 0600: 8086:2d11 (rev 02)
ff:02.2 0600: 8086:2d12 (rev 02)
ff:02.3 0600: 8086:2d13 (rev 02)

It would be great if anybody could find a solution to this so that I will not need to dual boot.