# Impossible de lancer Bluetooth **URL:** \ **Category:** Support Debian\ **Created:** [Novembre 27, 2022, 4:26 UTC](https://www.debian-fr.org/t/impossible-de-lancer-bluetooth/87478 "2022-11-27T16:26:00Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![degolarson](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@degolarson](https://www.debian-fr.org/u/degolarson)\ **Post date:** [Novembre 27, 2022, 4:26 UTC](https://www.debian-fr.org/t/impossible-de-lancer-bluetooth/87478/1 "2022-11-27T16:26:00Z")
Bonjour Je ne parviens pas à faire détecter un petit haut-parleur Bluetooth JBL par mon ordinateur J’ai lu [ce sujet](https://www.debian-fr.org/t/impossible-de-lancer-le-bluetooth-sur-debian-11/85358) mais je m’y perds J’ai lu aussi [Debian facile Bluetooth](https://debian-facile.org/doc:systeme:bluetooth) et tenté quelques commandes Bluetooth est bien installé ```nohighlight joel@joel-k70ij:~$ apt policy bluetooth bluetooth: Installé : 5.55-3.1 Candidat : 5.55-3.1 Table de version : *** 5.55-3.1 500 500 http://deb.debian.org/debian bullseye/main amd64 Packages 500 http://deb.debian.org/debian bullseye/main i386 Packages 100 /var/lib/dpkg/status joel@joel-k70ij:~$ ``` ```nohighlight joel@joel-k70ij:~$ sudo service bluetooth start [sudo] Mot de passe de joel : joel@joel-k70ij:~$ ``` Apparemment il n’y a pas de détection ```nohighlight joel@joel-k70ij:~$ hcitool dev Devices: joel@joel-k70ij:~$ ``` ```nohighlight joel@joel-k70ij:~$ bluetoothctl Waiting to connect to bluetoothd... ``` ```nohighlight joel@joel-k70ij:~$ apt policy blueman-adapters N: Impossible de trouver le paquet blueman-adapters joel@joel-k70ij:~$ blueman-adapters blueman-adapters version 2.1.4 starting blueman-adapters 16.52.46 ERROR Adapter:53 __init__ : No adapter(s) found joel@joel-k70ij:~$ ``` ```nohighlight joel@joel-k70ij:~$ sudo apt install blueman-adapters [sudo] Mot de passe de joel : Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait E: Impossible de trouver le paquet blueman-adapters joel@joel-k70ij:~$ ``` et aussi : ```nohighlight joel@joel-k70ij:~$ apt policy bluez bluez: Installé : 5.55-3.1 Candidat : 5.55-3.1 Table de version : *** 5.55-3.1 500 500 http://deb.debian.org/debian bullseye/main amd64 Packages 100 /var/lib/dpkg/status joel@joel-k70ij:~$ ``` Edition du fichier /etc/default/bluetooth ```nohighlight # Defaults for bluez # start bluetooth on boot? # compatibility note: if this variable is _not_ found bluetooth will start BLUETOOTH_ENABLED=1 # This setting used to switch HID devices (e.g mouse/keyboard) to HCI mode, that # is you will have bluetooth functionality from your dongle instead of only # HID. This is accomplished for supported devices by udev in # /lib/udev/rules.d/62-bluez-hid2hci.rules by invoking hid2hci with correct # parameters. # See /usr/share/doc/bluez/NEWS.Debian.gz for further information. # Older daemons like pand dund and hidd can be found in bluez-compat package as # they are deprecated and provided for backward compatibility only. # Note that not every bluetooth dongle is capable of switching back to HID mode, # see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355497 HID2HCI_ENABLED=0 HID2HCI_UNDO=0 ``` en reprenant [ce sujet](https://www.debian-fr.org/t/impossible-de-lancer-le-bluetooth-sur-debian-11/85358) après avoir installé **rfkill** ```nohighlight joel@joel-k70ij:~$ sudo rfkill list all 0: asus-wwan: Wireless WAN Soft blocked: no Hard blocked: no 1: asus-wimax: WiMAX Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no joel@joel-k70ij:~$ ``` ```nohighlight joel@joel-k70ij:~$ lsmod | grep blue bluetooth 753664 0 ecdh_generic 16384 1 bluetooth libaes 16384 2 bluetooth,aes_generic rfkill 32768 6 bluetooth,asus_laptop,cfg80211 crc16 16384 2 bluetooth,ext4 joel@joel-k70ij:~$ ``` ensuite ```nohighlight joel@joel-k70ij:~$ systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: inactive (dead) Docs: man:bluetoothd(8) lines 1-4/4 (END)...skipping... ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: inactive (dead) Docs: man:bluetoothd(8) ``` ```nohighlight joel@joel-k70ij:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 09) 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 09) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 IDE interface: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 2 port SATA Controller [IDE mode] (rev 03) 00:1f.5 IDE interface: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 2 port SATA Controller [IDE mode] (rev 03) 02:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01) 03:00.0 Ethernet controller: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet (rev b0) joel@joel-k70ij:~$ ``` ```nohighlight joel@joel-k70ij:~$ sudo dmesg | grep firmware [sudo] Mot de passe de joel : [3.301718] psmouse serio4: elantech: assuming hardware version 2 (with firmware version 0x040101) [6.680798] platform regulatory.0: firmware: direct-loading firmware regulatory.db [6.681086] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s [918.562466] (NULL device *): firmware: direct-loading firmware regulatory.db [918.562506] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s [1841.736980] (NULL device *): firmware: direct-loading firmware regulatory.db [1841.737017] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s [1977.437401] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s [1977.437403] (NULL device *): firmware: direct-loading firmware regulatory.db joel@joel-k70ij:~$ ``` Le paquet iwlwifi n’est pas installé ```nohighlight joel@joel-k70ij:~$ apt policy iwlwifi N: Impossible de trouver le paquet iwlwifi ``` ```nohighlight joel@joel-k70ij:~$ sudo apt install iwlwifi [sudo] Mot de passe de joel : Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait E: Impossible de trouver le paquet iwlwifi joel@joel-k70ij:~$ ``` Le fichier `/etc/apt/sources.list` contient les bons dépôts ```nohighlight deb http://deb.debian.org/debian bullseye main contrib non-free #deb-src http://deb.debian.org/debian bullseye main contrib non-free deb http://deb.debian.org/debian-security/ bullseye-security main contrib non-free #deb-src http://deb.debian.org/debian-security/ bullseye-security main contrib non-free deb http://deb.debian.org/debian bullseye-updates main contrib non-free #deb-src http://deb.debian.org/debian bullseye-updates main contrib non-free ``` merci ---
**Author:** ![dindoun](https://www.debian-fr.org/user_avatar/www.debian-fr.org/dindoun/32/4281_2.png) [@dindoun](https://www.debian-fr.org/u/dindoun)\ **Post date:** [Novembre 27, 2022, 11:32 UTC](https://www.debian-fr.org/t/impossible-de-lancer-bluetooth/87478/2 "2022-11-27T23:32:05Z")
salut chez moi : ```auto # apt-get install blueman bluez bluez-obexd pulseaudio-module-bluetooth bluetooth # bluetoothctl Waiting to connect to bluetoothd... # systemctl start bluetooth # bluetoothctl Agent registered [SLM 5 B1]# ``` ---
**Author:** ![AnatomicJC](https://www.debian-fr.org/user_avatar/www.debian-fr.org/anatomicjc/32/3869_2.png) [@AnatomicJC](https://www.debian-fr.org/u/AnatomicJC)\ **Post date:** [Novembre 28, 2022, 5:38 UTC](https://www.debian-fr.org/t/impossible-de-lancer-bluetooth/87478/3 "2022-11-28T05:38:39Z")
Si des fois ça peut aider, je me suis écrit ce mémo : [Bluetooth pairing with command line | Linux and DevOps Stuff !](https://jcvassort.open-web.fr/cli-bluetooth-pairing/) ---
**Author:** ![degolarson](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@degolarson](https://www.debian-fr.org/u/degolarson)\ **Post date:** [Novembre 28, 2022, 8:40 UTC](https://www.debian-fr.org/t/impossible-de-lancer-bluetooth/87478/4 "2022-11-28T08:40:28Z")
Bonjour @AnatomicJC ```nohighlight joel@joel-k70ij:~$ [bluetooth]# list bash: [bluetooth]# : commande introuvable joel@joel-k70ij:~$ ``` @dindoun ```nohighlight joel@joel-k70ij:~$ bluetoothctl Waiting to connect to bluetoothd... ``` ```nohighlight joel@joel-k70ij:~$ systemctl start bluetooth joel@joel-k70ij:~$ bluetoothctl Waiting to connect to bluetoothd... ``` et là c’est comme la tarte tatin en langage Ch’ti : ah ben t’es là qu’t’attinds… :\>)) ---
**Author:** ![degolarson](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@degolarson](https://www.debian-fr.org/u/degolarson)\ **Post date:** [Novembre 28, 2022, 8:52 UTC](https://www.debian-fr.org/t/impossible-de-lancer-bluetooth/87478/5 "2022-11-28T08:52:54Z")
J’ai tenté aussi : ```nohighlight joel@joel-k70ij:~$ apt list --installed | grep blue WARNING: apt does not have a stable CLI interface. Use with caution in scripts. blueman/stable,now 2.1.4-1+b1 amd64 [installé] bluetooth/stable,stable,now 5.55-3.1 all [installé, automatique] bluez-firmware/stable,stable,now 1.2-4 all [installé] bluez-obexd/stable,now 5.55-3.1 amd64 [installé, automatique] bluez/stable,now 5.55-3.1 amd64 [installé, automatique] libbluetooth3/stable,now 5.55-3.1 amd64 [installé, automatique] pulseaudio-module-bluetooth/stable,now 14.2-2 amd64 [installé, automatique] joel@joel-k70ij:~$ ``` ```nohighlight joel@joel-k70ij:~$ apt policy hciconfig N: Impossible de trouver le paquet hciconfig joel@joel-k70ij:~$ sudo apt install hciconfig [sudo] Mot de passe de joel : Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait E: Impossible de trouver le paquet hciconfig joel@joel-k70ij:~$ ``` ---
**Author:** ![degolarson](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@degolarson](https://www.debian-fr.org/u/degolarson)\ **Post date:** [Novembre 28, 2022, 9:00 UTC](https://www.debian-fr.org/t/impossible-de-lancer-bluetooth/87478/6 "2022-11-28T09:00:48Z")
et aussi ```nohighlight joel@joel-k70ij:~$ sudo systemctl status NetworkManager -n 100 -l [sudo] Mot de passe de joel : ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendo> Active: active (running) since Mon 2022-11-28 08:16:52 CET; 12h left Docs: man:NetworkManager(8) Main PID: 630 (NetworkManager) Tasks: 3 (limit: 4616) Memory: 13.3M CPU: 5.359s CGroup: /system.slice/NetworkManager.service └─630 /usr/sbin/NetworkManager --no-daemon nov. 27 19:03:44 joel-k70ij NetworkManager[630]: [1669572224.9949] devi> nov. 27 19:03:45 joel-k70ij NetworkManager[630]: [1669572225.4694] poli> nov. 27 19:03:45 joel-k70ij NetworkManager[630]: [1669572225.4845] dhcp> nov. 27 19:03:45 joel-k70ij NetworkManager[630]: [1669572225.4894] poli> nov. 27 19:03:45 joel-k70ij NetworkManager[630]: [1669572225.4981] dhcp> nov. 27 19:08:42 joel-k70ij NetworkManager[630]: [1669572522.5055] dhcp> nov. 27 19:13:42 joel-k70ij NetworkManager[630]: [1669572822.4867] dhcp> nov. 27 19:18:42 joel-k70ij NetworkManager[630]: [1669573122.4872] dhcp> nov. 27 19:23:42 joel-k70ij NetworkManager[630]: [1669573422.4882] dhcp> nov. 27 19:25:29 joel-k70ij NetworkManager[630]: [1669573529.2112] mana> nov. 27 19:25:29 joel-k70ij NetworkManager[630]: [1669573529.2116] devi> nov. 27 19:25:29 joel-k70ij NetworkManager[630]: [1669573529.2128] mana> lines 1-23 ``` ---
**Author:** ![AnatomicJC](https://www.debian-fr.org/user_avatar/www.debian-fr.org/anatomicjc/32/3869_2.png) [@AnatomicJC](https://www.debian-fr.org/u/AnatomicJC)\ **Post date:** [Novembre 28, 2022, 9:26 UTC](https://www.debian-fr.org/t/impossible-de-lancer-bluetooth/87478/7 "2022-11-28T09:26:51Z")
> [@degolarson](#): > > ```plaintext > joel@joel-k70ij:~$ [bluetooth]# list > bash: [bluetooth]# : commande introuvable > > ``` Hello, A aucun moment il n’est indiqué d’entrer la commande **[bluetooth]# list** qui fait juste partie de l’image d’exemple de l’article 🤦‍♂️ Il faut juste lancer tout d’abord la commande **bluetoothctl** suivie de **show** afin de vérifier que le bluetooth fonctionne. Chez moi ça donne: ```plaintext $ bluetoothctl Agent registered [CHG] Controller B0:3C:DC:9D:75:7D Pairable: yes [bluetooth]# show Controller B0:3C:DC:9D:75:7D (public) Name: onyx Alias: onyx Class: 0x006c010c Powered: yes Discoverable: no DiscoverableTimeout: 0x000000b4 Pairable: yes UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: Headset (00001108-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0541 Discovering: no Roles: central Roles: peripheral Advertising Features: ActiveInstances: 0x00 (0) SupportedInstances: 0x0c (12) SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name SupportedSecondaryChannels: 1M SupportedSecondaryChannels: 2M SupportedSecondaryChannels: Coded ``` Il faut ensuite lire la suite de l’article. ---
**Author:** ![degolarson](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@degolarson](https://www.debian-fr.org/u/degolarson)\ **Post date:** [Novembre 28, 2022, 9:45 UTC](https://www.debian-fr.org/t/impossible-de-lancer-bluetooth/87478/8 "2022-11-28T09:45:03Z")
> [@degolarson](#): > > ```plaintext > joel@joel-k70ij:~$ bluetoothctl > Waiting to connect to bluetoothd… > > ``` > > et là c’est comme la tarte tatin en langage Ch’ti : ah ben t’es là qu’t’attinds… > :\>)) j’ai attendu un bon 30 minutes sans résultat.. Je crois que le problème est bien dans l’absence de détection ---
**Author:** ![dindoun](https://www.debian-fr.org/user_avatar/www.debian-fr.org/dindoun/32/4281_2.png) [@dindoun](https://www.debian-fr.org/u/dindoun)\ **Post date:** [Novembre 28, 2022, 12:57 UTC](https://www.debian-fr.org/t/impossible-de-lancer-bluetooth/87478/9 "2022-11-28T12:57:58Z")
salut dmesg te donne-t-il une info sur les drivers manquant? `sudo dmesg |egrep -i 'firmware|driver|error|bluettoth|hci'` tu peux aussi directement essayer l’installation de plein de driver et ensuite faire le ménage : > **[Programmes à installer deb11 ( bullseye ) amd64](https://dindoun.lautre.net/spip.php?article451)** > > Liste de sources.list #apt-get update && apt-get install apt-transport-https && sed ’s#http:#https:#’ -i (...) PS chez moi je n’ai pas hciconfig mais quand même des hci0 et hci1 dans dmesg ---
**Author:** ![degolarson](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@degolarson](https://www.debian-fr.org/u/degolarson)\ **Post date:** [Novembre 28, 2022, 3:04 UTC](https://www.debian-fr.org/t/impossible-de-lancer-bluetooth/87478/10 "2022-11-28T15:04:35Z")
voilà ```nohighlight joel@joel-k70ij:~$ sudo dmesg |egrep -i 'firmware|driver|error|bluettoth|hci' [0.316630] Performance Events: PEBS fmt0+, Core2 events, 4-deep LBR, Intel PMU driver. [0.326751] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [0.637169] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [1.858322] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251) [1.860396] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [1.864120] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [1.886208] microcode: Microcode Update Driver: v2.2. [2.338499] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [2.338509] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [2.338515] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [2.431833] usbcore: registered new interface driver usbfs [2.431847] usbcore: registered new interface driver hub [2.431866] usbcore: registered new device driver usb [2.453584] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [2.457495] ehci-pci: EHCI PCI platform driver [2.457707] ehci-pci 0000:00:1a.7: EHCI Host Controller [2.457721] ehci-pci 0000:00:1a.7: new USB bus registered, assigned bus number 1 [2.457738] ehci-pci 0000:00:1a.7: debug port 1 [2.461660] ehci-pci 0000:00:1a.7: cache line size of 32 is not supported [2.476143] ehci-pci 0000:00:1a.7: irq 18, io mem 0xfe9fbc00 [2.491202] ehci-pci 0000:00:1a.7: USB 2.0 started, EHCI 1.00 [2.491336] usb usb1: Product: EHCI Host Controller [2.491337] usb usb1: Manufacturer: Linux 5.10.0-19-amd64 ehci_hcd [2.493262] ehci-pci 0000:00:1d.7: EHCI Host Controller [2.493273] ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 2 [2.493290] ehci-pci 0000:00:1d.7: debug port 1 [2.497243] ehci-pci 0000:00:1d.7: cache line size of 32 is not supported [2.497418] ehci-pci 0000:00:1d.7: irq 23, io mem 0xfe9fb800 [2.509956] ehci-pci 0000:00:1d.7: USB 2.0 started, EHCI 1.00 [2.510082] usb usb2: Product: EHCI Host Controller [2.510084] usb usb2: Manufacturer: Linux 5.10.0-19-amd64 ehci_hcd [2.588342] uhci_hcd: USB Universal Host Controller Interface driver [2.588529] uhci_hcd 0000:00:1a.0: UHCI Host Controller [2.588540] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3 [2.588553] uhci_hcd 0000:00:1a.0: detected 2 ports [2.588594] uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000d880 [2.592103] usb usb3: Product: UHCI Host Controller [2.592105] usb usb3: Manufacturer: Linux 5.10.0-19-amd64 uhci_hcd [2.593138] uhci_hcd 0000:00:1a.1: UHCI Host Controller [2.593147] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4 [2.593155] uhci_hcd 0000:00:1a.1: detected 2 ports [2.593197] uhci_hcd 0000:00:1a.1: irq 21, io base 0x0000d800 [2.593283] usb usb4: Product: UHCI Host Controller [2.593285] usb usb4: Manufacturer: Linux 5.10.0-19-amd64 uhci_hcd [2.594157] uhci_hcd 0000:00:1a.2: UHCI Host Controller [2.594165] uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 5 [2.594174] uhci_hcd 0000:00:1a.2: detected 2 ports [2.594207] uhci_hcd 0000:00:1a.2: irq 19, io base 0x0000d480 [2.594699] usb usb5: Product: UHCI Host Controller [2.594701] usb usb5: Manufacturer: Linux 5.10.0-19-amd64 uhci_hcd [2.603591] uhci_hcd 0000:00:1d.0: UHCI Host Controller [2.603602] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6 [2.603611] uhci_hcd 0000:00:1d.0: detected 2 ports [2.603637] uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000d400 [2.606897] usb usb6: Product: UHCI Host Controller [2.606899] usb usb6: Manufacturer: Linux 5.10.0-19-amd64 uhci_hcd [2.614437] uhci_hcd 0000:00:1d.1: UHCI Host Controller [2.614448] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7 [2.614458] uhci_hcd 0000:00:1d.1: detected 2 ports [2.614484] uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000d080 [2.614977] usb usb7: Product: UHCI Host Controller [2.614978] usb usb7: Manufacturer: Linux 5.10.0-19-amd64 uhci_hcd [2.615931] uhci_hcd 0000:00:1d.2: UHCI Host Controller [2.615940] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8 [2.615948] uhci_hcd 0000:00:1d.2: detected 2 ports [2.615973] uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000d000 [2.616058] usb usb8: Product: UHCI Host Controller [2.616060] usb usb8: Manufacturer: Linux 5.10.0-19-amd64 uhci_hcd [2.745857] usb 1-3: new high-speed USB device number 2 using ehci-pci [3.005873] usb 6-1: new low-speed USB device number 2 using uhci_hcd [3.260147] cdrom: Uniform CD-ROM driver Revision: 3.20 [3.327798] hid: raw HID events driver (C) Jiri Kosina [3.345856] usbcore: registered new interface driver usbhid [3.345859] usbhid: USB HID core driver [3.348662] psmouse serio4: elantech: assuming hardware version 2 (with firmware version 0x040101) [5.631040] lp: driver loaded but no devices found [5.638939] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro [5.657797] ppdev: user-space parallel port driver [6.871253] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Index (0x00000001B) is beyond end of object (length 0x10) (20200925/exoparg2-393) [6.871370] ACPI Error: Aborting method \_SB.PCI0.SBRG.EC0.STBR due to previous error (AE_AML_BUFFER_LIMIT) (20200925/psparse-529) [6.871458] ACPI Error: Aborting method \_SB.PCI0.VGA.LCDD._BCM due to previous error (AE_AML_BUFFER_LIMIT) (20200925/psparse-529) [6.871546] ACPI Error: Evaluating _BCM failed (20200925/video-357) [7.191470] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [7.356435] platform regulatory.0: firmware: direct-loading firmware regulatory.db [7.356722] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s [7.757241] usbcore: registered new interface driver uvcvideo [7.757243] USB Video Class driver (1.1.1) [6071.972830] (NULL device *): firmware: direct-loading firmware regulatory.db [6071.972879] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s [6072.785909] usb 6-1: reset low-speed USB device number 2 using uhci_hcd [6075.148007] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Index (0x00000001B) is beyond end of object (length 0x10) (20200925/exoparg2-393) [6075.148026] ACPI Error: Aborting method \_SB.PCI0.SBRG.EC0.STBR due to previous error (AE_AML_BUFFER_LIMIT) (20200925/psparse-529) [6075.148043] ACPI Error: Aborting method \_SB.PCI0.VGA.LCDD._BCM due to previous error (AE_AML_BUFFER_LIMIT) (20200925/psparse-529) [6075.148060] ACPI Error: Evaluating _BCM failed (20200925/video-357) [6822.801778] (NULL device *): firmware: direct-loading firmware regulatory.db [6822.801851] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s [6823.549892] usb 6-1: reset low-speed USB device number 2 using uhci_hcd [6825.875770] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Index (0x00000001B) is beyond end of object (length 0x10) (20200925/exoparg2-393) [6825.875789] ACPI Error: Aborting method \_SB.PCI0.SBRG.EC0.STBR due to previous error (AE_AML_BUFFER_LIMIT) (20200925/psparse-529) [6825.875807] ACPI Error: Aborting method \_SB.PCI0.VGA.LCDD._BCM due to previous error (AE_AML_BUFFER_LIMIT) (20200925/psparse-529) [6825.875824] ACPI Error: Evaluating _BCM failed (20200925/video-357) [8059.752704] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s [8059.752765] (NULL device *): firmware: direct-loading firmware regulatory.db [8060.477890] usb 6-1: reset low-speed USB device number 2 using uhci_hcd [8062.652917] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Index (0x00000001B) is beyond end of object (length 0x10) (20200925/exoparg2-393) [8062.652936] ACPI Error: Aborting method \_SB.PCI0.SBRG.EC0.STBR due to previous error (AE_AML_BUFFER_LIMIT) (20200925/psparse-529) [8062.652953] ACPI Error: Aborting method \_SB.PCI0.VGA.LCDD._BCM due to previous error (AE_AML_BUFFER_LIMIT) (20200925/psparse-529) [8062.652970] ACPI Error: Evaluating _BCM failed (20200925/video-357) joel@joel-k70ij:~$ ``` ---
**Author:** ![dindoun](https://www.debian-fr.org/user_avatar/www.debian-fr.org/dindoun/32/4281_2.png) [@dindoun](https://www.debian-fr.org/u/dindoun)\ **Post date:** [Novembre 29, 2022, 2:05 UTC](https://www.debian-fr.org/t/impossible-de-lancer-bluetooth/87478/11 "2022-11-29T14:05:23Z")
bof je vois rien tu peux nous refaire un ```auto sudo apt-get install firmware-brcm80211 firmware-iwlwifi firmware-linux firmware-linux-free firmware-linux-nonfree firmware-misc-nonfree firmware-ralink sudo rfkill list all ``` ---
**Author:** ![degolarson](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@degolarson](https://www.debian-fr.org/u/degolarson)\ **Post date:** [Novembre 29, 2022, 4:10 UTC](https://www.debian-fr.org/t/impossible-de-lancer-bluetooth/87478/12 "2022-11-29T16:10:16Z")
Voilà ```nohighlight joel@joel-k70ij:~$ sudo apt-get install firmware-brcm80211 firmware-iwlwifi firmware-linux firmware-linux-free firmware-linux-nonfree firmware-misc-nonfree firmware-ralink [sudo] Mot de passe de joel : Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait Note : sélection de « firmware-misc-nonfree » au lieu de « firmware-ralink » firmware-linux-free est déjà la version la plus récente (20200122-1). firmware-linux-free passé en « installé manuellement ». firmware-iwlwifi est déjà la version la plus récente (20210315-3). firmware-misc-nonfree est déjà la version la plus récente (20210315-3). Les paquets supplémentaires suivants seront installés : amd64-microcode firmware-amd-graphics intel-microcode iucode-tool Les NOUVEAUX paquets suivants seront installés : amd64-microcode firmware-amd-graphics firmware-brcm80211 firmware-linux firmware-linux-nonfree intel-microcode iucode-tool 0 mis à jour, 7 nouvellement installés, 0 à enlever et 49 non mis à jour. Il est nécessaire de prendre 15,5 Mo dans les archives. Après cette opération, 73,9 Mo d'espace disque supplémentaires seront utilisés. Souhaitez-vous continuer ? [O/n] Réception de :1 http://deb.debian.org/debian bullseye/non-free amd64 amd64-microcode amd64 3.20191218.1 [35,5 kB] Réception de :2 http://deb.debian.org/debian bullseye/non-free amd64 firmware-amd-graphics all 20210315-3 [5 953 kB] Réception de :3 http://deb.debian.org/debian bullseye/non-free amd64 firmware-brcm80211 all 20210315-3 [5 304 kB] Réception de :4 http://deb.debian.org/debian bullseye/non-free amd64 firmware-linux-nonfree all 20210315-3 [23,3 kB] Réception de :5 http://deb.debian.org/debian bullseye/non-free amd64 firmware-linux all 20210315-3 [23,6 kB] Réception de :6 http://deb.debian.org/debian bullseye/contrib amd64 iucode-tool amd64 2.3.1-1 [62,4 kB] Réception de :7 http://deb.debian.org/debian bullseye/non-free amd64 intel-microcode amd64 3.20220510.1~deb11u1 [4 092 kB] 15,5 Mo réceptionnés en 1s (10,9 Mo/s) Sélection du paquet amd64-microcode précédemment désélectionné. (Lecture de la base de données... 161550 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../0-amd64-microcode_3.20191218.1_amd64.deb ... Dépaquetage de amd64-microcode (3.20191218.1) ... Sélection du paquet firmware-amd-graphics précédemment désélectionné. Préparation du dépaquetage de .../1-firmware-amd-graphics_20210315-3_all.deb ... Dépaquetage de firmware-amd-graphics (20210315-3) ... Sélection du paquet firmware-brcm80211 précédemment désélectionné. Préparation du dépaquetage de .../2-firmware-brcm80211_20210315-3_all.deb ... Dépaquetage de firmware-brcm80211 (20210315-3) ... Sélection du paquet firmware-linux-nonfree précédemment désélectionné. Préparation du dépaquetage de .../3-firmware-linux-nonfree_20210315-3_all.deb ... Dépaquetage de firmware-linux-nonfree (20210315-3) ... Sélection du paquet firmware-linux précédemment désélectionné. Préparation du dépaquetage de .../4-firmware-linux_20210315-3_all.deb ... Dépaquetage de firmware-linux (20210315-3) ... Sélection du paquet iucode-tool précédemment désélectionné. Préparation du dépaquetage de .../5-iucode-tool_2.3.1-1_amd64.deb ... Dépaquetage de iucode-tool (2.3.1-1) ... Sélection du paquet intel-microcode précédemment désélectionné. Préparation du dépaquetage de .../6-intel-microcode_3.20220510.1~deb11u1_amd64.deb ... Dépaquetage de intel-microcode (3.20220510.1~deb11u1) ... Paramétrage de iucode-tool (2.3.1-1) ... Paramétrage de intel-microcode (3.20220510.1~deb11u1) ... update-initramfs: deferring update (trigger activated) intel-microcode: microcode will be updated at next boot Paramétrage de amd64-microcode (3.20191218.1) ... update-initramfs: deferring update (trigger activated) amd64-microcode: microcode will be updated at next boot Paramétrage de firmware-brcm80211 (20210315-3) ... Paramétrage de firmware-amd-graphics (20210315-3) ... Paramétrage de firmware-linux-nonfree (20210315-3) ... Paramétrage de firmware-linux (20210315-3) ... Traitement des actions différées (« triggers ») pour man-db (2.9.4-2) ... Traitement des actions différées (« triggers ») pour initramfs-tools (0.140) ... update-initramfs: Generating /boot/initrd.img-5.10.0-19-amd64 joel@joel-k70ij:~$ ``` ```nohighlight joel@joel-k70ij:~$ sudo rfkill list all [sudo] Mot de passe de joel : 0: asus-wwan: Wireless WAN Soft blocked: no Hard blocked: no 1: asus-wimax: WiMAX Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no joel@joel-k70ij:~$ bluetoothctl Waiting to connect to bluetoothd... ``` toujours impossible ---
**Author:** ![Verner](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/v/34f0e0/32.png) [@Verner](https://www.debian-fr.org/u/Verner)\ **Post date:** [Novembre 29, 2022, 4:56 UTC](https://www.debian-fr.org/t/impossible-de-lancer-bluetooth/87478/13 "2022-11-29T16:56:08Z")
Que dit ceci: ``` systemctl start bluetooth systemctl status bluetooth ``` ---
**Author:** ![degolarson](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@degolarson](https://www.debian-fr.org/u/degolarson)\ **Post date:** [Novembre 29, 2022, 5:27 UTC](https://www.debian-fr.org/t/impossible-de-lancer-bluetooth/87478/14 "2022-11-29T17:27:28Z")
```nohighlight joel@joel-k70ij:~$ systemctl start bluetooth joel@joel-k70ij:~$ ``` ```nohighlight joel@joel-k70ij:~$ systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: inactive (dead) Docs: man:bluetoothd(8) lines 1-4/4 (END) ``` ---
**Author:** ![Verner](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/v/34f0e0/32.png) [@Verner](https://www.debian-fr.org/u/Verner)\ **Post date:** [Novembre 29, 2022, 5:30 UTC](https://www.debian-fr.org/t/impossible-de-lancer-bluetooth/87478/15 "2022-11-29T17:30:40Z")
Et maintenant: `bluetoothctl` ---
**Author:** ![crashcoq](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/c/7ea924/32.png) [@crashcoq](https://www.debian-fr.org/u/crashcoq)\ **Post date:** [Novembre 29, 2022, 9:36 UTC](https://www.debian-fr.org/t/impossible-de-lancer-bluetooth/87478/16 "2022-11-29T21:36:03Z")
Regarde que la ligne est bien commenté #kernel.modules\_disabled = 1 Dans /etc/sysctl.conf Ça peut bloquer la détection des modules USB mais ameliore la sécurité… ---
**Author:** ![degolarson](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@degolarson](https://www.debian-fr.org/u/degolarson)\ **Post date:** [Novembre 30, 2022, 10:43 UTC](https://www.debian-fr.org/t/impossible-de-lancer-bluetooth/87478/17 "2022-11-30T10:43:35Z")
Bonjour > [@crashcoq](#): > > Regarde que la ligne est bien commenté > #kernel.modules\_disabled = 1 La ligne n’apparaît pas ```plaintext # # /etc/sysctl.conf - Configuration file for setting system variables # See /etc/sysctl.d/ for additional system variables. # See sysctl.conf (5) for information. # #kernel.domainname = example.com # Uncomment the following to stop low-level messages on console #kernel.printk = 3 4 1 3 ################################################################### # Functions previously found in netbase # # Uncomment the next two lines to enable Spoof protection (reverse-path filter) # Turn on Source Address Verification in all interfaces to # prevent some spoofing attacks #net.ipv4.conf.default.rp_filter=1 #net.ipv4.conf.all.rp_filter=1 # Uncomment the next line to enable TCP/IP SYN cookies # See http://lwn.net/Articles/277146/ # Note: This may impact IPv6 TCP sessions too #net.ipv4.tcp_syncookies=1 # Uncomment the next line to enable packet forwarding for IPv4 #net.ipv4.ip_forward=1 # Uncomment the next line to enable packet forwarding for IPv6 # Enabling this option disables Stateless Address Autoconfiguration # based on Router Advertisements for this host #net.ipv6.conf.all.forwarding=1 ################################################################### # Additional settings - these settings can improve the network # security of the host and prevent against some network attacks # including spoofing attacks and man in the middle attacks through # redirection. Some network environments, however, require that these # settings are disabled so review and enable them as needed. # # Do not accept ICMP redirects (prevent MITM attacks) #net.ipv4.conf.all.accept_redirects = 0 #net.ipv6.conf.all.accept_redirects = 0 # _or_ # Accept ICMP redirects only for gateways listed in our default # gateway list (enabled by default) # net.ipv4.conf.all.secure_redirects = 1 # # Do not send ICMP redirects (we are not a router) #net.ipv4.conf.all.send_redirects = 0 # # Do not accept IP source route packets (we are not a router) #net.ipv4.conf.all.accept_source_route = 0 #net.ipv6.conf.all.accept_source_route = 0 # # Log Martian Packets #net.ipv4.conf.all.log_martians = 1 # ################################################################### # Magic system request Key # 0=disable, 1=enable all, >1 bitmask of sysrq functions # See https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html # for what other values do #kernel.sysrq=438 ``` ---
**Author:** ![degolarson](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@degolarson](https://www.debian-fr.org/u/degolarson)\ **Post date:** [Novembre 30, 2022, 11:20 UTC](https://www.debian-fr.org/t/impossible-de-lancer-bluetooth/87478/18 "2022-11-30T11:20:03Z")
@Verner ```auto Waiting to connect to bluetoothd... ``` rien depuis 10mn ---
**Author:** ![Verner](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/v/34f0e0/32.png) [@Verner](https://www.debian-fr.org/u/Verner)\ **Post date:** [Novembre 30, 2022, 12:37 UTC](https://www.debian-fr.org/t/impossible-de-lancer-bluetooth/87478/19 "2022-11-30T12:37:56Z")
Accessoirement, as-tu un appareil **Bluetooth en fonction** à proximité sur lequel ton PC serait susceptible de se connecter ? ---
**Author:** ![degolarson](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@degolarson](https://www.debian-fr.org/u/degolarson)\ **Post date:** [Novembre 30, 2022, 12:44 UTC](https://www.debian-fr.org/t/impossible-de-lancer-bluetooth/87478/20 "2022-11-30T12:44:47Z")
Je fais toujours les tests avec le haut parleur JBL allumé Sinon j’ai un smartphone à proximité avec le bluetooth en fonction [Page suivante](https://www.debian-fr.org/t/impossible-de-lancer-bluetooth/87478.md?page=2)