Bluetooth is not working on Fedora 10 cambridge Laptop

[dipanchandra]

Hi all,

I am facing an issue with my bluetooth. I am not able to detect any bluetooth enabled mobile or laptop with that of mine.

In my System > Preference > Hardware > Bluetooth

I am having following options only :

[ ] never display an icon[*] only when adaptor present (checked)
[ ] always display an icon


moreover-

==
[root@zzzzz net]# lsmod | grep bluetooth
bluetooth 48608 5 sco,bnep,l2cap
==

I tried going thru similar posts on forum , but in vain.
I am not sure what is wrong .... please help.

-Dipan

[trigpoint]

Try

hcitool scan

[dipanchandra]

hi Trigpoint,

thanks for the reply. I am getting this message :

[net@dipan ~]$ hcitool scan
Device is not available: No such device

[trigpoint]

It looks like your dongle has not been detected.

Plug in your dongle and then run dmesg, I get the following

usb 3-1: new full speed USB device using uhci_hcd and address 19
usb 3-1: configuration #1 chosen from 1 choice
usb 3-1: New USB device found, idVendor=0a12, idProduct=0001
usb 3-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
usb 3-1: Product: EDRClassone

When I run lsmod | grep bluetooth, I get

bluetooth              48608  15 rfcomm,btusb,sco,bnep,l2cap

It looks to me as though you are missing some services.

Does the Bluetooth icon appear?

If not try running Fedora 10 from a live CD.

If you run lsusb you should see something like

Bus 003 Device 019: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

HTH

[dipanchandra]

It looks like your dongle has not been detected

.
Oh............ silly me !!!!!
Actually my machine is a Toshiba satellite with built in Bluetooth. So, there is no role of bluetooth dongle. I should have posted it in the first place. Sorry for that.

Well,

[root@zzzzz net]# lsmod | grep bluetooth

output is

bluetooth 48608 5 sco,bnep,l2cap

and

[

net@dipan ~]$ dmesg | grep -y -n blue

returns

687:Bluetooth: Core ver 2.13
689:Bluetooth: HCI device and connection manager initialized
690:Bluetooth: HCI socket layer initialized
691:Bluetooth: L2CAP ver 2.11
692:Bluetooth: L2CAP socket layer initialized
693:Bluetooth: BNEP (Ethernet Emulation) ver 1.3
694:Bluetooth: BNEP filters: protocol multicast
696:Bluetooth: SCO (Voice Link) ver 0.6
697:Bluetooth: SCO socket layer initialized

still wondering+wandering

[phosphide]

Hi

I have a very similar issue with F11 and Toshiba A300D.

[phosphide@f11-toshiba ~]$ lsmod | grep bluetooth
bluetooth              53300  5 sco,bnep,l2cap

[phosphide@f11-toshiba ~]$ hcitool scan
Device is not available: No such device

[phosphide@f11-toshiba ~]$ lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0bda:8198 Realtek Semiconductor Corp. 
Bus 001 Device 002: ID 04f2:b008 Chicony Electronics Co., Ltd USB 2.0 Camera
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

[phosphide@f11-toshiba ~]$ dmesg | grep -y -n blue
825:Bluetooth: Core ver 2.15
827:Bluetooth: HCI device and connection manager initialized
828:Bluetooth: HCI socket layer initialized
829:Bluetooth: L2CAP ver 2.13
830:Bluetooth: L2CAP socket layer initialized
831:Bluetooth: BNEP (Ethernet Emulation) ver 1.3
832:Bluetooth: BNEP filters: protocol multicast
834:Bluetooth: SCO (Voice Link) ver 0.6
835:Bluetooth: SCO socket layer initialized

What makes it strange is that it worked out of the box with F11-Preview, but after I updated to Release the bluetooth device automagically disappeared (I can't tell if it was right after the update, I don't use bluetooth very often)
Even the wireless switch worked for bluetooth before the update.

With F10 I got it working by the way of trying to get some support for Fn-keys and battery status by installing all Toshiba-related utilities I found. Unfortunately, I haven't used F10 much here because many ACPI features still weren't working, so I don't remember what those apps were.

phosphide

[dipanchandra]

Hi phosphide ,
Thanks for the rep. As you just said :

With F10 I got it working by the way of trying to get some support for Fn-keys and battery status by installing all Toshiba-related utilities

Can you please share the above links , rpm adresses with me??

It would be of great help ...

Thanks,
Dipan

[phosphide]

I also said I hadn't figured out all acpi issues, so I left it as they were making the system unusable.
I came back to it when F11-Preview was released, which worked amazingly well.

I might have installed (or tried to install) compat-wireless, fnfx, omnibook, acpitool, maybe some other utilities. I have no idea which one helped, if any.
I must have googled 'toshiba brightness fedora', 'a300 acpi linux', 'toshiba battery fedora' etc. I remember some guides came from Ubuntu forums. For sure I wasn't trying to get bluetooth working, just power management and some keyboard multimedia functions.

The A300 seems to differ much from older Satellites: no /dev/toshiba - no support from toshiba_acpi and toshiba modules. Together with poor ATI support, it doesn't make a Linux-friendly device

phosphide

[luoluo]

Hi friend,

I have same bluetooth issue with you now, I want to ask you how to solve this issue?

Thanks,

Robin

[phosphide]

Hi

I, for example, sold the laptop :-)

But when I still had it I found out that booting into Windows, enabling bluetooth (if it's disabled) and then rebooting back to Fedora makes bluetooth device appear again. I guess it has to do with power management?

I never upgraded to a higher Fedora version on that laptop (I didn't want to go through ATI drivers' hell again), so I don't know if anything changed in more recent versions.

[dipanchandra]

Hi guys,

Miracles do happen... yeah !! even on weekends !!
I reinstalled the same ISO of fedora and lo !!!
everything worked as a charm