Description of problem: since kernel 3.2.2 update bluedevil does not see my bluetooth dongle with kinfo i see a strange thing : OHCI host controller /USB Tablet/bluetooth dongle (hci mode) harddrake does not see the bluetooth dongle with mandriva 2010.2 kinfo i see : OHCI host controller / bluetooth dongle (hci mode)
what is the output of lsusb, lspcidrake -v and hcitools scan ?
[root@localhost ~]# lsusb -bash: lsusb : commande introuvable (not found command) [root@localhost ~]# [root@localhost ~]# hcitool scan Device is not available: No such device [root@localhost ~]# [root@localhost ~]# lspcidrake -v ahci : Intel Corporation|82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] [STORAGE_SATA] (vendor:8086 device:2829) (rev: 02) ehci_hcd : Intel Corporation|82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller [SERIAL_USB] (vendor:8086 device:265c) i2c_piix4 : Intel Corporation|82371AB/EB/MB PIIX4 ACPI [BRIDGE_OTHER] (vendor:8086 device:7113) (rev: 08) ohci_hcd : Apple Computer Inc.|KeyLargo/Intrepid USB [SERIAL_USB] (vendor:106b device:003f) snd_hda_intel : Intel Corporation|82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (vendor:8086 device:2668 subv:8384 subd:7680) (rev: 01) vboxguest : InnoTek Systemberatung GmbH|VirtualBox Guest Service [SYSTEM_OTHER] (vendor:80ee device:cafe) e1000 : Intel Corporation|82540EM Gigabit Ethernet Controller [NETWORK_ETHERNET] (vendor:8086 device:100e subv:8086 subd:001e) (rev: 02) Card:VirtualBox virtual video card: InnoTek Systemberatung GmbH|VirtualBox Graphics Adapter [DISPLAY_VGA] (vendor:80ee device:beef) ata_piix : Intel Corporation|82371AB/EB/MB PIIX4 IDE [STORAGE_IDE] (vendor:8086 device:7111) (rev: 01) unknown : Intel Corporation|82371SB PIIX3 ISA [Natoma/Triton II] [BRIDGE_ISA] (vendor:8086 device:7000) unknown : Intel Corporation|440FX - 82441FX PMC [Natoma] [BRIDGE_HOST] (vendor:8086 device:1237) (rev: 02) [root@localhost ~]#
[root@localhost ~]# lsusb Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) [root@localhost ~]# usbutils packet not installed by default !
seems you use Virtualbox, so are you sure the usb is enable ? (and the device) >usbutils packet not installed by default ! by default ? ie ?
(In reply to comment #4) > seems you use Virtualbox, so are you sure the usb is enable ? (and the device) > as i said "since kernel 3.2.2" then this was working then the dongle is in the Vbox usb list since i test mageaia2a3 > >usbutils packet not installed by default ! > by default ? ie ? i did not choose anything during mageia installation process
That's not what he asked. The question is why should we install it by default?
CC: (none) => thierry.vignaud
i found kernel log, dmesg i only found in "messages" : Jan 28 16:43:17 localhost kernel: Bluetooth: hci0 command xtmot<3>Bluetooth: hci0 command tx timeout Jan 28 16:43:17 localhost resolvconf[1217]: Lancement de resolvconf : [ OK ] Jan 28 16:43:18 localhost kernel: ata1.00: configured for UDMA/133 Jan 28 16:43:18 localhost kernel: ata1: EH complete Jan 28 16:43:18 localhost kernel: Bluetooth: hci0 command tx timeout Jan 28 16:43:18 localhost kernel: EXT4-fs (sda1): re-mounted. Opts: acl,commit=0 Jan 28 16:43:18 localhost udisks-daemon[1226]: **** /proc/self/mountinfo changed Jan 28 16:43:18 localhost udisks-daemon[1226]: **** /proc/self/mountinfo changed Jan 28 16:43:18 localhost kernel: EXT4-fs (sda6): re-mounted. Opts: acl,commit=0 Jan 28 16:43:19 localhost kernel: Bluetooth: hci0 command tx timeout Jan 28 16:43:20 localhost kernel: Bluetooth: hci0 command tx timeout Jan 28 16:43:21 localhost kernel: Bluetooth: hci0 command tx timeout Jan 28 16:43:22 localhost kernel: Bluetooth: hci0 command tx timeout Jan 28 16:43:23 localhost kernel: Bluetooth: hci0 command tx timeout Jan 28 16:43:23 localhost network[1587]: Démarrage de l'interface loopback : [ OK ] Jan 28 16:43:24 localhost bluetoothd[1205]: bluetoothd[1420]: Can't init device hci0: Connection timed out (110) Jan 28 16:43:24 localhost bluetoothd[1420]: Can't init device hci0: Connection timed out (110) if i unplug then plug the dongle then i have this : Jan 28 17:26:49 localhost bluetoothd[1205]: bluetoothd[1205]: HCI dev 0 unregistered Jan 28 17:26:49 localhost bluetoothd[1205]: bluetoothd[1205]: Stopping hci0 event socket Jan 28 17:26:49 localhost bluetoothd[1205]: HCI dev 0 unregistered Jan 28 17:26:49 localhost bluetoothd[1205]: Stopping hci0 event socket Jan 28 17:26:49 localhost kernel: usb 1-2: USB disconnect, device number 3 Jan 28 17:26:49 localhost systemd[1]: Service bluetooth.target is not needed anymore. Stopping. Jan 28 17:26:55 localhost kernel: usb 1-2: new full-speed USB device number 4 using ohci_hcd Jan 28 17:26:55 localhost kernel: usb 1-2: New USB device found, idVendor=0a12, idProduct=0001 Jan 28 17:26:55 localhost kernel: usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Jan 28 17:26:55 localhost bluetoothd[1205]: bluetoothd[1205]: HCI dev 0 registered Jan 28 17:26:55 localhost bluetoothd[1205]: bluetoothd[1205]: Listening for HCI events on hci0 Jan 28 17:26:55 localhost bluetoothd[1205]: HCI dev 0 registered Jan 28 17:26:55 localhost bluetoothd[1205]: Listening for HCI events on hci0 Jan 28 17:26:56 localhost bluetoothd[1205]: bluetoothd[1205]: HCI dev 0 up Jan 28 17:26:56 localhost bluetoothd[1205]: HCI dev 0 up Jan 28 17:26:56 localhost kernel: Bluetooth: RFCOMM TTY layer initialized Jan 28 17:26:56 localhost kernel: Bluetooth: RFCOMM socket layer initialized Jan 28 17:26:56 localhost kernel: Bluetooth: RFCOMM ver 1.11 Jan 28 17:26:56 localhost bluetoothd[1205]: bluetoothd[1205]: Could not get the contents of DMI chassis type Jan 28 17:26:57 localhost bluetoothd[1205]: Could not get the contents of DMI chassis type Jan 28 17:26:57 localhost bluetoothd[1205]: bluetoothd[1205]: HCI dev 0 down Jan 28 17:26:57 localhost bluetoothd[1205]: HCI dev 0 down Jan 28 17:26:57 localhost bluetoothd[1205]: bluetoothd[1205]: Adapter /org/bluez/1205/hci0 has been disabled Jan 28 17:26:57 localhost bluetoothd[1205]: Adapter /org/bluez/1205/hci0 has been disabled Jan 28 17:27:10 localhost dbus-daemon[1274]: dbus[1274]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper) Jan 28 17:27:10 localhost dbus[1274]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper) Jan 28 17:27:10 localhost dbus-daemon[1274]: no kernel backlight interface found Jan 28 17:27:11 localhost org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave. Jan 28 17:27:11 localhost dbus-daemon[1274]: dbus[1274]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' Jan 28 17:27:11 localhost dbus[1274]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' and bluedevil appears in the systray activate/unactivate bluedevil works well we see the dongle flashing then stops flashing
i have this pb with mandriva 2010.2 since i use kernel 3.0 then 3.1 surfing internet i found this : with several distributions there is this pb : ubuntu, opensuse etc. a person has the same pb with linux cyrus this person found a solution : "The problem seems to have been solved after kernel and linux header update." it seems that bluetooth uses bnep and btusb driver addendum : do you know how to enable the adapter with a command instead of unplug then plug it ?
another hypothesis : systemd pb
how to disable parallelism with systemd ?
1. experiment with mandriva 2010.2 bluedevil does not see the dongle then /usr/sbin/bluetoothd stop then bluedevil sees the dongle i can activate and unactivate the dongle then /usr/sbin/bluetoothd start then bluedevil sees the dongle i can activate and unactivate the dongle 2. Experiment with mageia 2 alpha 3 /usr/sbin/bluetoothd stop then bluedevil does not see the dongle then /usr/sbin/bluetoothd start then bluedevil does not see the dongle then hciconfig hc0 down hciconfig hc0 up then bluedevil sees the dongle i can activate and unactivate the dongle
kernel errors.log file contents when starting mageia 2 alpha 3: Feb 1 12:32:23 localhost kernel: Bluetooth: hci0 command tx timeout Feb 1 12:32:24 localhost kernel: Bluetooth: hci0 command tx timeout Feb 1 12:32:25 localhost kernel: Bluetooth: hci0 command tx timeout Feb 1 12:32:26 localhost kernel: Bluetooth: hci0 command tx timeout Feb 1 12:32:27 localhost kernel: Bluetooth: hci0 command tx timeout Feb 1 12:32:28 localhost kernel: Bluetooth: hci0 command tx timeout Feb 1 12:32:29 localhost kernel: Bluetooth: hci0 command tx timeout Feb 1 12:32:30 localhost kernel: Bluetooth: hci0 command tx timeout Feb 1 12:32:32 localhost kernel: Bluetooth: hci0 command tx timeout
mageia 2 beta 1 since the update today afternoon about systemd there is no more pb the bluetooth dongle is seen then bluetooth is activated
Status: NEW => RESOLVEDResolution: (none) => FIXED
this worked one time only
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
it's a random phenomenon. perhaps a systemd parallelism technology pb ?
CC: (none) => mageia
Random question, is bluedevil running all the time (I'm not familiar with how it works generally). If so does simply killing and restarting it solve the problem too? I'm wondering if it's being started before bluetooth stuff is finialised and not coping well? FWIW, I have bluetooth in my laptop (not via dongle) and it's been working fine in gnome for ages. Can you perhaps try using gnome instead and see if you get similar bluetooth problems there? That would at least narrow it down to a plumbing layer issue (which I kinda suspect really, but it's nice to discount the higher level stuff if it can be done easily!)
> Random question, is bluedevil running all the time yes when it does not detect any bluetooth device it is hidden in the systray and when you click on it then answer is "no found adapter" > If so does simply killing and restarting it solve the problem too? see my comment #11 hciconfig hc0 down hciconfig hc0 up then bluedevil sees the dongle i can activate and unactivate the dongle > I'm wondering if it's being started before bluetooth stuff is finialised and > not coping well? bluedevil is started when you open kde session if i understand well i tried this : - no bluedevil started in kde session when opening a kde session - i start manualy bluedevil after several minutes result : - bluedevil stays hidden in the systray - when clicking on it then "no found adapter"
today kernel was updated to 3.2.9 then i have something new [root@localhost ~]# hciconfig hc0 down [root@localhost ~]# hciconfig hc0 up Can't init device hci0: Connection timed out (110)
no more pb with mageia 2 beta 2
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
CC: (none) => gouessej
Hi I reproduce this bug on Mageia 2. I use the same device. [root@localhost gouessej]# hciconfig hci0: Type: BR/EDR Bus: USB BD Address: 00:15:83:C9:32:3D ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING RX bytes:914 acl:0 sco:0 events:33 errors:0 TX bytes:140 acl:0 sco:0 commands:32 errors:0