[bluetooth] BCM4352 ne détecte pas d'appareil bluetooth

Reconnaissance et configuration du matériel / kernel linux
Répondre
furious.builder
newbie
Messages : 5
Inscription : sam. 06 mai 2017, 19:06

[bluetooth] BCM4352 ne détecte pas d'appareil bluetooth

Message par furious.builder »

Bonjour à tous !


Je fais aujourd'hui appel à vous car j'ai un problème. J'essai d'appairer la BCM4352 avec mon UE BOOM 2. Hors, je n'y arrive pas, même en passant par

Code : Tout sélectionner

bluetoothctl
power on 
agent on
default-agent
scan on
trust XX:XX:XX:XX:XX
pair XX:XX:XX:XX:XX
bluetoothctl est toujours en "attempting" puis "failed". j'utilise actuellement broadcom-wl comme driver.
L'enceinte marche correctement puisqu'elle marche avec mon téléphone.

Pourriez-vous, s'il vous plaît, m'aider ?
Merci beaucoup !
lemust83
yeomen
Messages : 206
Inscription : ven. 11 déc. 2015, 21:20

Re: [bluetooth] BCM4352 ne détecte pas d'appareil bluetooth

Message par lemust83 »

Bonjour
Souvent, c'est l'appareil qui est déjà automatiquement connecté au téléphone (ou autres). Du coup, l'appairage échoue avec le PC.
Tour: Arch (Xfce) 64 Testing: 6-Core: AMD Ryzen 5 2600X type: MT MCP speed: 2152 MHz min/max: 2200/3600 MH
UEFI: American Megatrends v: 3803 date: 01/22/2018
Graphics:
Device-1: AMD Baffin [Radeon RX 460/560D / Pro
450/455/460/555/555X/560/560X]
driver: amdgpu v: kernel
Display: server: X.Org 1.20.8 driver: amdgpu,ati unloaded: modesetting
resolution: 1920x1080~60Hz
OpenGL: renderer: Radeon RX 560 Series
Manjaro en Dual (grub).
furious.builder
newbie
Messages : 5
Inscription : sam. 06 mai 2017, 19:06

Re: [bluetooth] BCM4352 ne détecte pas d'appareil bluetooth

Message par furious.builder »

@lemust83 : j'aurai bien aimé que ça soit aussi simple, malheureusement j'avais déjà tout déconnecté de l'enceinte et je l'ai même réinitialisée pour voir si ça changeait quelque chose :/
lemust83
yeomen
Messages : 206
Inscription : ven. 11 déc. 2015, 21:20

Re: [bluetooth] BCM4352 ne détecte pas d'appareil bluetooth

Message par lemust83 »

C'est souvent un point qu'on oublie de vérifier :)
Je ne vois pas la commande connect xx.xx.xx.xx ?
Tour: Arch (Xfce) 64 Testing: 6-Core: AMD Ryzen 5 2600X type: MT MCP speed: 2152 MHz min/max: 2200/3600 MH
UEFI: American Megatrends v: 3803 date: 01/22/2018
Graphics:
Device-1: AMD Baffin [Radeon RX 460/560D / Pro
450/455/460/555/555X/560/560X]
driver: amdgpu v: kernel
Display: server: X.Org 1.20.8 driver: amdgpu,ati unloaded: modesetting
resolution: 1920x1080~60Hz
OpenGL: renderer: Radeon RX 560 Series
Manjaro en Dual (grub).
furious.builder
newbie
Messages : 5
Inscription : sam. 06 mai 2017, 19:06

Re: [bluetooth] BCM4352 ne détecte pas d'appareil bluetooth

Message par furious.builder »

Ahah c'est vrai ! :D Pareil que pour la commande pair, ça reste sur failed avec une erreur Bluez :cry:
lemust83
yeomen
Messages : 206
Inscription : ven. 11 déc. 2015, 21:20

Re: [bluetooth] BCM4352 ne détecte pas d'appareil bluetooth

Message par lemust83 »

J'ai vérifié avec mon casque BT, la toute dernière version de Bluez 5.45-1 fonctionne.
Essaye éventuellement de le rétrograder .
Tour: Arch (Xfce) 64 Testing: 6-Core: AMD Ryzen 5 2600X type: MT MCP speed: 2152 MHz min/max: 2200/3600 MH
UEFI: American Megatrends v: 3803 date: 01/22/2018
Graphics:
Device-1: AMD Baffin [Radeon RX 460/560D / Pro
450/455/460/555/555X/560/560X]
driver: amdgpu v: kernel
Display: server: X.Org 1.20.8 driver: amdgpu,ati unloaded: modesetting
resolution: 1920x1080~60Hz
OpenGL: renderer: Radeon RX 560 Series
Manjaro en Dual (grub).
furious.builder
newbie
Messages : 5
Inscription : sam. 06 mai 2017, 19:06

Re: [bluetooth] BCM4352 ne détecte pas d'appareil bluetooth

Message par furious.builder »

J'obtiens les erreurs suivantes :

Code : Tout sélectionner

[clementpoiret@clement-pc ~]$ rfkill list
0: acer-wireless: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
3: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
[clementpoiret@clement-pc ~]$ bluetoothctl
[NEW] Controller 44:39:C4:16:E8:81 clement-pc [default]
[NEW] Device 88:C6:26:A0:02:1F UE BOOM 2
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
Discovery started
[CHG] Controller 44:39:C4:16:E8:81 Discovering: yes
[CHG] Device 88:C6:26:A0:02:1F RSSI: -59
[CHG] Device 88:C6:26:A0:02:1F UUIDs: 0000fe61-0000-1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Key: 0x0003
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x60
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x5d
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x30
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x09
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x88
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0xc6
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x26
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0xa0
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x02
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x1f
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x12
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Key: 0x0003
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x60
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x5d
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x30
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x09
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x88
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0xc6
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x26
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0xa0
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x02
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x1f
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x12
[bluetooth]# pair 88:C6:26:A0:02:1F
Attempting to pair with 88:C6:26:A0:02:1F
[CHG] Device 88:C6:26:A0:02:1F Connected: yes
Failed to pair: org.bluez.Error.AuthenticationFailed
[CHG] Device 88:C6:26:A0:02:1F Connected: no
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Key: 0x0003
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x60
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x5d
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x30
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x09
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x88
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0xc6
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x26
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0xa0
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x02
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x1f
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x12
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Key: 0x0003
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x60
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x5d
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x30
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x09
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x12
[bluetooth]# trust 88:C6:26:A0:02:1F
Changing 88:C6:26:A0:02:1F trust succeeded
[bluetooth]# pair 88:C6:26:A0:02:1F 
Attempting to pair with 88:C6:26:A0:02:1F
[CHG] Device 88:C6:26:A0:02:1F Connected: yes
Failed to pair: org.bluez.Error.AuthenticationFailed
[CHG] Device 88:C6:26:A0:02:1F Connected: no
[bluetooth]# connect 88:C6:26:A0:02:1F
Attempting to connect to 88:C6:26:A0:02:1F
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Key: 0x0003
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x60
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x5d
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x20
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x09
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x12
[CHG] Device 88:C6:26:A0:02:1F Connected: yes
Failed to connect: org.bluez.Error.Failed
[CHG] Device 88:C6:26:A0:02:1F Connected: no
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Key: 0x0003
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x60
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x5d
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x20
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x09
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x88
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0xc6
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x26
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0xa0
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x02
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x1f
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x12
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Key: 0x0003
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x60
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x5c
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x20
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x09
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x00
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x88
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0xc6
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x26
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0xa0
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x02
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x1f
[CHG] Device 88:C6:26:A0:02:1F ManufacturerData Value: 0x12
[bluetooth]# scan off
[CHG] Device 88:C6:26:A0:02:1F RSSI is nil
Discovery stopped
[CHG] Controller 44:39:C4:16:E8:81 Discovering: no
[bluetooth]# pair 88:C6:26:A0:02:1F
Attempting to pair with 88:C6:26:A0:02:1F
[CHG] Device 88:C6:26:A0:02:1F Connected: yes
Failed to pair: org.bluez.Error.AuthenticationFailed
[CHG] Device 88:C6:26:A0:02:1F Connected: no
Avatar de l’utilisateur
benjarobin
Maître du Kyudo
Messages : 17187
Inscription : sam. 30 mai 2009, 15:48
Localisation : Lyon

Re: [bluetooth] BCM4352 ne détecte pas d'appareil bluetooth

Message par benjarobin »

As tu bien suivi la documentation de ton appareil ? Voir http://www.ultimateears.com/fr-fr/ueboom2/support
Q: Comment coupler des dispositifs Bluetooth supplémentaires avec mon haut-parleur UE?
Car on dirait bien que l'appareil UE BOOM 2 n'est pas en mode couplage
Zsh | KDE | PC fixe : core i7, carte nvidia
Titre d'un sujet : [Thème] Sujet (état) / Règles du forum
furious.builder
newbie
Messages : 5
Inscription : sam. 06 mai 2017, 19:06

Re: [bluetooth] BCM4352 ne détecte pas d'appareil bluetooth

Message par furious.builder »

Oui, tout est bon, elle passe bien en mode couplage je peux la connecter à n'importe quoi même à des téléphones d'amis, c'est juste sous linux que ça ne veut pas :/
Le Limule
Hankyu
Messages : 35
Inscription : jeu. 02 août 2012, 20:42

Re: [bluetooth] BCM4352 ne détecte pas d'appareil bluetooth

Message par Le Limule »

ton matériel semble être du Broadcom. c'est peut-être un de ces matériels qui nécessite un flash du firmware. les explications ici:
https://wiki.archlinux.org/index.php/Bl ... com_device

j'avais un pb similaire, et ça l'a résolu (en partie).
Répondre