#1 Hier à 19:48
- RMX
Bluetooth instable - activation impossible
Bonjour,
Je rencontre un problème avec l'activation du bluetooth (marchait auparavant)
Graphiquement losque je vais dans Paramètres>Bluetooth le bouton fais le yo-yo on/off losque j'essaie de l'activer
Après plusieurs recherches sur le web, en lançant la commande:
>Sudo journalctl -b 0 | grep blue
Je constate une ribambelle de message:
Quelqu'un a-t-il une idée de ce comportement ?
Merci de votre éclairage car je sèche:|
ar 13 19:31:05 BeeTux systemd[1]: Reached target bluetooth.target - Bluetooth Support.
mar 13 19:31:05 BeeTux systemd[2512]: Reached target bluetooth.target - Bluetooth.
mar 13 19:31:07 BeeTux systemd[2512]: Stopped target bluetooth.target - Bluetooth.
mar 13 19:31:07 BeeTux systemd[1]: Stopped target bluetooth.target - Bluetooth Support.
mar 13 19:31:07 BeeTux systemd[2512]: Reached target bluetooth.target - Bluetooth.
mar 13 19:31:07 BeeTux systemd[1]: Reached target bluetooth.target - Bluetooth Support.
mar 13 19:31:09 BeeTux systemd[2512]: Stopped target bluetooth.target - Bluetooth.
mar 13 19:31:09 BeeTux systemd[1]: Stopped target bluetooth.target - Bluetooth Support.
mar 13 19:31:09 BeeTux systemd[2512]: Reached target bluetooth.target - Bluetooth.
mar 13 19:31:09 BeeTux systemd[1]: Reached target bluetooth.target - Bluetooth Support.
mar 13 19:31:11 BeeTux systemd[2512]: Stopped target bluetooth.target - Bluetooth.
mar 13 19:31:11 BeeTux systemd[1]: Stopped target bluetooth.target - Bluetooth Support.
mar 13 19:31:12 BeeTux systemd[2512]: Reached target bluetooth.target - Bluetooth.
mar 13 19:31:12 BeeTux systemd[1]: Reached target bluetooth.target - Bluetooth Support.
mar 13 19:31:13 BeeTux systemd[2512]: Stopped target bluetooth.target - Bluetooth.
mar 13 19:31:13 BeeTux systemd[1]: Stopped target bluetooth.target - Bluetooth Support.
mar 13 19:31:14 BeeTux systemd[1]: Reached target bluetooth.target - Bluetooth Support.
mar 13 19:31:14 BeeTux systemd[2512]: Reached target bluetooth.target - Bluetooth.
mar 13 19:31:15 BeeTux systemd[2512]: Stopped target bluetooth.target - Bluetooth.
mar 13 19:31:15 BeeTux systemd[1]: Stopped target bluetooth.target - Bluetooth Support.
Hors ligne
#2 Hier à 19:49
- xubu1957
Re : Bluetooth instable - activation impossible
Bonjour,
Il faudrait fournir, en te servant du Retour utilisable de commande :
uname -a; lspci -nnk | grep -iA3 net; lsusb; sudo dmesg | grep -i bluetooth; sudo dmesg | grep -i firmware; lsmod | grep bluetooth
dpkg -l | grep blue
rfkill list all
sudo service bluetooth status | cat
Astuce pour copier / coller sans erreur :
triple clic gauche pour sélectionner et copier une ligne entière
clic molette pour coller dans le terminal
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
Hors ligne
#3 Hier à 21:04
- RMX
Re : Bluetooth instable - activation impossible
Bonjour, merci de votre réponse
>uname -a; lspci -nnk | grep -iA3 net; lsusb fourni:
Linux BeeTux 6.8.0-55-generic #57-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 12 23:42:21 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
01:00.0 Network controller [0280]: Intel Corporation Wireless 3165 [8086:3165] (rev 81)
Subsystem: Intel Corporation Dual Band Wireless AC 3165 [Stone Peak 1x1] [8086:4010]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
DeviceName: Onboard LAN Brodcom
Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:0123]
Kernel driver in use: r8169
Kernel modules: r8169
03:00.0 Non-Volatile memory controller [0108]: Intel Corporation SSD 660P Series [8086:f1a8] (rev 03)
/********************************************************************************************************************************************************/
>lsusb; sudo dmesg | grep -i bluetooth fourni:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 003: ID 046d:c077 Logitech, Inc. Mouse
Bus 001 Device 004: ID 046d:c34b Logitech, Inc. USB Keyboard
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 059f:106b LaCie, Ltd Rugged Mini HDD
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 029: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
/*************************************************************************************************************/
[ 5.491245] Bluetooth: Core ver 2.22
[ 5.491280] NET: Registered PF_BLUETOOTH protocol family
[ 5.491283] Bluetooth: HCI device and connection manager initialized
[ 5.491290] Bluetooth: HCI socket layer initialized
[ 5.491294] Bluetooth: L2CAP socket layer initialized
[ 5.491302] Bluetooth: SCO socket layer initialized
[ 7.708372] Bluetooth: hci0: command 0x0c03 tx timeout
[ 7.708388] Bluetooth: hci0: sending initial HCI reset failed (-110)
[ 9.272160] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 9.272167] Bluetooth: BNEP filters: protocol multicast
[ 9.272175] Bluetooth: BNEP socket layer initialized
[ 13.028020] Bluetooth: hci0: sending initial HCI reset failed (-19)
[ 15.169037] Bluetooth: hci0: sending initial HCI reset failed (-19)
[ 17.314170] Bluetooth: hci0: sending initial HCI reset failed (-19)
[ 19.443242] Bluetooth: hci0: sending initial HCI reset failed (-19)
[ 21.576227] Bluetooth: hci0: sending initial HCI reset failed (-19)
[ 23.707234] Bluetooth: hci0: sending initial HCI reset failed (-19)
[ 25.840213] Bluetooth: hci0: sending initial HCI reset failed (-19)
etc................
/****************************************************************************************************************************************/
>sudo dmesg | grep -i firmware; lsmod | grep bluetooth fourni:
[ 5.658547] iwlwifi 0000:01:00.0: Allocated 0x00400000 bytes for firmware monitor.
[ 9.006583] [drm] Found VCN firmware Version ENC: 1.15 DEC: 3 VEP: 0 Revision: 0
[ 9.006606] amdgpu 0000:04:00.0: amdgpu: Will use PSP to load VCN firmware
bluetooth 1028096 15 btrtl,btmtk,btintel,btbcm,bnep,btusb
ecdh_generic 16384 1 bluetooth
Hors ligne
#4 Hier à 21:11
- RMX
Re : Bluetooth instable - activation impossible
Après avoir effectué :
>dpkg -l | grep blue
>rfkill list all
1: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
501: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
/****************************************************************************************************************************/
rfkill list all
1: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
501: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
me@BeeTux:~$ sudo service bluetooth status | cat
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
Active: active (running) since Thu 2025-03-13 20:48:03 CET; 18min ago
Docs: man:bluetoothd(8)
Main PID: 996 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 16623)
Memory: 2.8M (peak: 3.1M)
CPU: 157ms
CGroup: /system.slice/bluetooth.service
└─996 /usr/libexec/bluetooth/bluetoothd
mar 13 20:48:03 BeeTux bluetoothd[996]: Starting SDP server
mar 13 20:48:03 BeeTux bluetoothd[996]: src/plugin.c:plugin_init() System does not support csip plugin
mar 13 20:48:03 BeeTux bluetoothd[996]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
mar 13 20:48:03 BeeTux bluetoothd[996]: src/plugin.c:plugin_init() System does not support micp plugin
mar 13 20:48:03 BeeTux systemd[1]: Started bluetooth.service - Bluetooth service.
mar 13 20:48:03 BeeTux bluetoothd[996]: src/plugin.c:plugin_init() System does not support vcp plugin
mar 13 20:48:03 BeeTux bluetoothd[996]: src/plugin.c:plugin_init() System does not support mcp plugin
mar 13 20:48:03 BeeTux bluetoothd[996]: src/plugin.c:plugin_init() System does not support bass plugin
mar 13 20:48:03 BeeTux bluetoothd[996]: src/plugin.c:plugin_init() System does not support bap plugin
mar 13 20:48:03 BeeTux bluetoothd[996]: Bluetooth management interface 1.22 initialized
J'ai toujours le même comportement plusieurs fois par secondes
mar 13 21:10:09 BeeTux systemd[2579]: Stopped target bluetooth.target - Bluetooth.
mar 13 21:10:09 BeeTux systemd[1]: Stopped target bluetooth.target - Bluetooth Support.
mar 13 21:10:09 BeeTux systemd[1]: Reached target bluetooth.target - Bluetooth Support.
mar 13 21:10:09 BeeTux systemd[2579]: Reached target bluetooth.target - Bluetooth.
Hors ligne
#5 Hier à 21:34
- xubu1957
Re : Bluetooth instable - activation impossible
Pour éviter aux aidants de se crever les yeux > Lecture conseillée mémento des balises code.
uname -a; lspci -nnk | grep -iA3 net;
Linux BeeTux 6.8.0-55-generic #57-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 12 23:42:21 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
01:00.0 Network controller [0280]: Intel Corporation Wireless 3165 [8086:3165] (rev 81)
Subsystem: Intel Corporation Dual Band Wireless AC 3165 [Stone Peak 1x1] [8086:4010]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
DeviceName: Onboard LAN Brodcom
Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:0123]
Kernel driver in use: r8169
Kernel modules: r8169
03:00.0 Non-Volatile memory controller [0108]: Intel Corporation SSD 660P Series [8086:f1a8] (rev 03)
lsusb; sudo dmesg | grep -i bluetooth :
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 003: ID 046d:c077 Logitech, Inc. Mouse
Bus 001 Device 004: ID 046d:c34b Logitech, Inc. USB Keyboard
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 059f:106b LaCie, Ltd Rugged Mini HDD
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 029: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
[ 5.491245] Bluetooth: Core ver 2.22
[ 5.491280] NET: Registered PF_BLUETOOTH protocol family
[ 5.491283] Bluetooth: HCI device and connection manager initialized
[ 5.491290] Bluetooth: HCI socket layer initialized
[ 5.491294] Bluetooth: L2CAP socket layer initialized
[ 5.491302] Bluetooth: SCO socket layer initialized
[ 7.708372] Bluetooth: hci0: command 0x0c03 tx timeout
[ 7.708388] Bluetooth: hci0: sending initial HCI reset failed (-110)
[ 9.272160] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 9.272167] Bluetooth: BNEP filters: protocol multicast
[ 9.272175] Bluetooth: BNEP socket layer initialized
[ 13.028020] Bluetooth: hci0: sending initial HCI reset failed (-19)
[ 15.169037] Bluetooth: hci0: sending initial HCI reset failed (-19)
[ 17.314170] Bluetooth: hci0: sending initial HCI reset failed (-19)
[ 19.443242] Bluetooth: hci0: sending initial HCI reset failed (-19)
[ 21.576227] Bluetooth: hci0: sending initial HCI reset failed (-19)
[ 23.707234] Bluetooth: hci0: sending initial HCI reset failed (-19)
[ 25.840213] Bluetooth: hci0: sending initial HCI reset failed (-19)
etc................
sudo dmesg | grep -i firmware; lsmod | grep bluetooth
[ 5.658547] iwlwifi 0000:01:00.0: Allocated 0x00400000 bytes for firmware monitor.
[ 9.006583] [drm] Found VCN firmware Version ENC: 1.15 DEC: 3 VEP: 0 Revision: 0
[ 9.006606] amdgpu 0000:04:00.0: amdgpu: Will use PSP to load VCN firmware
bluetooth 1028096 15 btrtl,btmtk,btintel,btbcm,bnep,btusb
ecdh_generic 16384 1 bluetooth
Après avoir effectué :
>dpkg -l | grep blue
rfkill list all
1: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
501: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
me@BeeTux:~$ sudo service bluetooth status | cat
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
Active: active (running) since Thu 2025-03-13 20:48:03 CET; 18min ago
Docs: man:bluetoothd(8)
Main PID: 996 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 16623)
Memory: 2.8M (peak: 3.1M)
CPU: 157ms
CGroup: /system.slice/bluetooth.service
└─996 /usr/libexec/bluetooth/bluetoothd
mar 13 20:48:03 BeeTux bluetoothd[996]: Starting SDP server
mar 13 20:48:03 BeeTux bluetoothd[996]: src/plugin.c:plugin_init() System does not support csip plugin
mar 13 20:48:03 BeeTux bluetoothd[996]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
mar 13 20:48:03 BeeTux bluetoothd[996]: src/plugin.c:plugin_init() System does not support micp plugin
mar 13 20:48:03 BeeTux systemd[1]: Started bluetooth.service - Bluetooth service.
mar 13 20:48:03 BeeTux bluetoothd[996]: src/plugin.c:plugin_init() System does not support vcp plugin
mar 13 20:48:03 BeeTux bluetoothd[996]: src/plugin.c:plugin_init() System does not support mcp plugin
mar 13 20:48:03 BeeTux bluetoothd[996]: src/plugin.c:plugin_init() System does not support bass plugin
mar 13 20:48:03 BeeTux bluetoothd[996]: src/plugin.c:plugin_init() System does not support bap plugin
mar 13 20:48:03 BeeTux bluetoothd[996]: Bluetooth management interface 1.22 initialized
J'ai toujours le même comportement plusieurs fois par secondes
mar 13 21:10:09 BeeTux systemd[2579]: Stopped target bluetooth.target - Bluetooth.
mar 13 21:10:09 BeeTux systemd[1]: Stopped target bluetooth.target - Bluetooth Support.
mar 13 21:10:09 BeeTux systemd[1]: Reached target bluetooth.target - Bluetooth Supp
===========
dpkg -l | grep blue
n'est pas fourni.
Dernière modification par xubu1957 (Hier à 21:37)
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
Hors ligne