Mageia forum

Hello!

Before open this topic, I have searched a lof at Google, this forum and others about problems with bluetooth on Linux, but without luck. My notebook is a Dell Inspiron 1525 with internal adapter, that worked well at my Windows 7 and Mandriva 2011. Here in Mageia 3, I have installed bluez (and all packs related to it), bluedevil and blueman and I also tried the following:

Code: Select all

dmesg | grep "Blue"
[  247.867138] Bluetooth: Core ver 2.16
[  247.868903] Bluetooth: HCI device and connection manager initialized
[  247.868913] Bluetooth: HCI socket layer initialized
[  247.868917] Bluetooth: L2CAP socket layer initialized
[  247.868927] Bluetooth: SCO socket layer initialized
[  247.876954] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  247.876959] Bluetooth: BNEP filters: protocol multicast
[  247.876970] Bluetooth: BNEP socket layer initialized
[  247.934069] Bluetooth: RFCOMM TTY layer initialized
[  247.934085] Bluetooth: RFCOMM socket layer initialized
[  247.934087] Bluetooth: RFCOMM ver 1.11

Code: Select all

rfkill list all
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

Code: Select all

hcitool dev
Devices:

Code: Select all

hciconfig --all

Nothing returns...

Code: Select all

systemctl status dbus-org.bluez.service
bluetooth.service - Bluetooth Manager
          Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
          Active: activating (start) since Tue, 2013-06-25 21:44:11 BRT; 57s ago
        Main PID: 4120 (bluetoothd)
          CGroup: name=systemd:/system/bluetooth.service
                  └ 4120 /usr/sbin/bluetoothd -n

Jun 25 21:44:11 localhost systemd[1]: Starting Bluetooth Manager...
Jun 25 21:44:11 localhost bluetoothd[4120]: bluetoothd[4120]: Bluetooth daemon 4.101
Jun 25 21:44:11 localhost bluetoothd[4120]: Bluetooth daemon 4.101
Jun 25 21:44:11 localhost bluetoothd[4120]: Starting SDP server
Jun 25 21:44:11 localhost bluetoothd[4120]: Bluetooth Management interface initialized
Jun 25 21:44:11 localhost bluetoothd[4120]: bluetoothd[4120]: Starting SDP server
Jun 25 21:44:11 localhost bluetoothd[4120]: bluetoothd[4120]: Bluetooth Management interface initialized


Even with this saying that bluetooth is active, the bluedevil shows the message "No adapters found".

Is it the same problem as described here?

https://bugs.mageia.org/show_bug.cgi?id=6618

No, it did not work...

Code: Select all

# hciconfig

Nothing returns...

Code: Select all

# systemctl restart dbus-org.bluez.service
Job for bluetooth.service failed. See 'systemctl status bluetooth.service' and 'journalctl -n' for details.

Code: Select all

# systemctl status bluetooth.service dbus-org.bluez.service
bluetooth.service - Bluetooth Manager
          Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
          Active: activating (start) since Wed, 2013-06-26 11:58:34 BRT; 1min 2s ago
        Main PID: 4139 (bluetoothd)
          CGroup: name=systemd:/system/bluetooth.service
                  └ 4139 /usr/sbin/bluetoothd -n

Jun 26 11:58:34 localhost systemd[1]: Failed to start Bluetooth Manager.
Jun 26 11:58:34 localhost systemd[1]: Unit bluetooth.service entered failed state
Jun 26 11:58:34 localhost systemd[1]: Starting Bluetooth Manager...
Jun 26 11:58:34 localhost bluetoothd[4139]: Bluetooth daemon 4.101
Jun 26 11:58:34 localhost bluetoothd[4139]: Starting SDP server
Jun 26 11:58:34 localhost bluetoothd[4139]: Bluetooth Management interface initialized
Jun 26 11:58:34 localhost bluetoothd[4139]: bluetoothd[4139]: Bluetooth daemon 4.101
Jun 26 11:58:34 localhost bluetoothd[4139]: bluetoothd[4139]: Starting SDP server
Jun 26 11:58:34 localhost bluetoothd[4139]: bluetoothd[4139]: Bluetooth Management interface initialized

bluetooth.service - Bluetooth Manager
          Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
          Active: activating (start) since Wed, 2013-06-26 11:58:34 BRT; 1min 2s ago
        Main PID: 4139 (bluetoothd)
          CGroup: name=systemd:/system/bluetooth.service
                  └ 4139 /usr/sbin/bluetoothd -n

Jun 26 11:58:34 localhost systemd[1]: Failed to start Bluetooth Manager.
Jun 26 11:58:34 localhost systemd[1]: Unit bluetooth.service entered failed state
Jun 26 11:58:34 localhost systemd[1]: Starting Bluetooth Manager...
Jun 26 11:58:34 localhost bluetoothd[4139]: Bluetooth daemon 4.101
Jun 26 11:58:34 localhost bluetoothd[4139]: Starting SDP server
Jun 26 11:58:34 localhost bluetoothd[4139]: Bluetooth Management interface initialized
Jun 26 11:58:34 localhost bluetoothd[4139]: bluetoothd[4139]: Bluetooth daemon 4.101
Jun 26 11:58:34 localhost bluetoothd[4139]: bluetoothd[4139]: Starting SDP server
Jun 26 11:58:34 localhost bluetoothd[4139]: bluetoothd[4139]: Bluetooth Management interface initialized

Code: Select all

# journalctl -n
-- Logs begin at Tue, 2013-06-18 10:54:38 BRT, end at Wed, 2013-06-26 12:00:04 BRT. --
Jun 26 12:00:04 localhost bluetoothd[4139]: bluetoothd[4139]: Terminating
Jun 26 12:00:04 localhost bluetoothd[4139]: bluetoothd[4139]: Stopping SDP server
Jun 26 12:00:04 localhost bluetoothd[4139]: bluetoothd[4139]: Exit
Jun 26 12:00:04 localhost bluetoothd[4139]: Terminating
Jun 26 12:00:04 localhost bluetoothd[4139]: Stopping SDP server
Jun 26 12:00:04 localhost bluetoothd[4139]: Exit
Jun 26 12:00:04 localhost dbus[1641]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.b
Jun 26 12:00:04 localhost dbus-daemon[1641]: dbus[1641]: [system] Activating via systemd: service name='org.blue
Jun 26 12:00:04 localhost systemd[1]: Failed to start Bluetooth Manager.
Jun 26 12:00:04 localhost systemd[1]: Unit bluetooth.service entered failed state

I really don't know what else I could do...

~topic moved by moderator

And please, place command-output between [CODE][/CODE]-tags to keep the forum readable.
Thanks in advance.

Please show the output from

Code: Select all

rfkill list

Does you machine have a hardware switch to enable bluetooth, or a function key?

I have already tried it

Code: Select all

rfkill list
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

But no success... I have already tried to use the function key that is the same of the wireless, wich is working well. But no result.

Uhmm, so your bluetooth device isn't even listed there or not properly enabled yet. Also the bluetooth service is in state "activating" but has never completed when you look at the output again. Plus it fails to launch the bluetooth manager .

Can you please do a reboot and afterwards enable bluetooth with the function key if not enabled by default and show the output of

Code: Select all

sudo journalctl -b | grep -i bluetooth

and

Code: Select all

lspcidrake -v | grep -i blue

Is there a separate LED for bluetooth?

Code: Select all

journalctl -b | grep -i bluetooth
Nothing returns...

Code: Select all

lspcidrake -v | grep -i blue
Nothing returns...

My notebook doesn't have led for bluetooth.

I have seen some "extreme" method in my search: install the Windows again, even in a VirtualBox, and wait to bluetooth work, then it will work on Mageia. Is this really necessary?

Did you run the first command as root? Please try again as root.
But the problem seems that your bluetooth adapter is not enabled currently, hence nothing related to bluetooth possible.
You need to find out how to enable it, so it's listed by the second command.
Also please post the make and model of your laptop.

Here it looks like this after enabling bluetooth:

Code: Select all

[doktor5000@Mageia3 ~]$ lspcidrake -v | grep -i blue
btusb           : Broadcom Corp|BCM2046 Bluetooth Device [Wireless|Radio Frequency|Bluetooth] (vendor:0a5c device:2151)

Without enabling it, no output, as you described.

Both commands I tried as root. Even searching in other places, I did not find any way to enable it. Because the topics I have seen, usually ended after those commands that I posted here... And nothing works here. My notebook is Dell Inspiron 1525, and I saw some Dell notebooks that had the same problem with Linux... Maybe they did it to work only in Windows, without it they stop... I don't doubt anything nowadays! (Just kidding)

I have two Bluetooh dongles. This one: Vendor: ‎Cambridge Silicon Radio, Ltd Description: ‎Bluetooth Dongle (HCI mode) works.

This one: Vendor: ‎Bluetooth v2.0 Description: ‎Bluetooth V2.0 Dongle does NOT work.

They look identical but I think I bought them at different times. They look like the end of your thumb, rounded. They both work in Windows and did work in Mageia 2. The OP is right, there is a problem and I've spent a couple of hours going through this. Running "systemctl status bluetooth.service" shows another line of information that says the good one is enabled "Adapter /org/bluez/24293/hci0 has been enabled", while the bad one doesn't ever say enabled.

Everything looks good except that. This is one of those minor bugs I have spoken of but it may not be minor for those who have built in BT. I'll spend a little more time on it and see what I find but so far it's a tricky little bug and it may be in the hardware, that is, something not normal with the bad dongle!

What bluez packages do you have installed? Also, is bluez-firmware installed?

Apart from that, for some rare dongles you may need to manually switch them to operational mode,
I've seen that for one or two dongles, and also fixed it, but as it wasn't my box, cannot remember the exact command anymore
Either something with hcitool or hciconfig, but not hciconfig hciX up when I remember correctly, but you may also try that ...

Also, check the obvious stuff, is maybe some kill switch active?

Code: Select all

rfkill list all

EDIT: totally forgot, please post the pci IDs via lspcidrake'/lsusb which helps find more information

I have a similar problem with an Inspiron 1526.

I was a Mandriva user for years, and recently ditched Mint to go to Mageia. So far so good, but I can't get the Bluetooth card to work.

Mageia 4, MATE, 4GB RAM, Broadcom (BCM2045? 46? see below) bluetooth card that worked fine under Mint.


I have been using Linux for quite a while, and can usually fix most things. This one has got me though. Any assistance would be greatly appreciated.
This is my first post to the mageia forums, so if I screwed it up (formatting), I'm sorry.

a few items that could be telling:

Code: Select all

# lsusb
Bus 003 Device 004: ID 413c:8126 Dell Computer Corp. Wireless 355 Bluetooth
Bus 003 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)

Code: Select all

# systemctl status bluetooth.service dbus-org.bluez.service
bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled)
   Active: active (running) since Wed 2014-08-06 12:23:52 CDT; 14min ago
     Docs: man:bluetoothd(8)
 Main PID: 4209 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─4209 /usr/libexec/bluetooth/bluetoothd

Aug 06 12:23:52 mageinspiron systemd[1]: Starting Bluetooth service...
Aug 06 12:23:52 mageinspiron systemd[1]: Started Bluetooth service.
Aug 06 12:23:52 mageinspiron bluetoothd[4209]: Bluetooth daemon 5.11
Aug 06 12:23:52 mageinspiron bluetoothd[4209]: Starting SDP server
Aug 06 12:23:52 mageinspiron bluetoothd[4209]: Bluetooth management interface 1.3 initialized
Aug 06 12:23:52 mageinspiron bluetoothd[4209]: Endpoint registered: sender=:1.41 path=/MediaEndpoint/A2DPSource
Aug 06 12:23:52 mageinspiron bluetoothd[4209]: Endpoint registered: sender=:1.41 path=/MediaEndpoint/A2DPSink

bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled)
   Active: active (running) since Wed 2014-08-06 12:23:52 CDT; 14min ago
     Docs: man:bluetoothd(8)
 Main PID: 4209 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─4209 /usr/libexec/bluetooth/bluetoothd

Aug 06 12:23:52 mageinspiron systemd[1]: Starting Bluetooth service...
Aug 06 12:23:52 mageinspiron systemd[1]: Started Bluetooth service.
Aug 06 12:23:52 mageinspiron bluetoothd[4209]: Bluetooth daemon 5.11
Aug 06 12:23:52 mageinspiron bluetoothd[4209]: Starting SDP server
Aug 06 12:23:52 mageinspiron bluetoothd[4209]: Bluetooth management interface 1.3 initialized
Aug 06 12:23:52 mageinspiron bluetoothd[4209]: Endpoint registered: sender=:1.41 path=/MediaEndpoint/A2DPSource
Aug 06 12:23:52 mageinspiron bluetoothd[4209]: Endpoint registered: sender=:1.41 path=/MediaEndpoint/A2DPSink

Code: Select all

# lspcidrake -v | grep -i blue
btusb           : Broadcom Corp|BCM2045 [Wireless|Radio Frequency|Bluetooth] (vendor:413c device:8126)

Code: Select all

# rfkill list
0: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no
1: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no

Please create separate topics. Problem may seem similar, but mostly this mangles several issues into one big thread, and there are a lot drawbacs to that.

I have a bluetooth mouse, it worked fine until an update in M3 , I loaded linux mint and it worked fine. it's working now because I keep using a different pin. The auto recognition of the pin seems to be broken. It's probably a bug in something totally unconnected .

As a general hint and golden rule: Please only one problem per thread