Icaunux - Le Forum

Forum de l'Association ICAUNUX

Vous n'êtes pas identifié(e).

Annonce

Les Inscriptions au forum sont temporairement désactivées en attendant de trouver une solution efficace contre les inscriptions fictives très nombreuses ces derniers temps. Si vous souhaitez vous inscrire sur le forum, merci d'envoyer une demande par mail à l'adresse contact@icaunux.org. Désolé de cette gène occasionnée.

#1 25-01-2023 16:29:58

wanica
Membre
Inscription : 13-11-2008
Messages : 2 070

Bluetooth sur Lenovo série T et divers vieux pc Ubuntu et Lubuntu

Le BT ?!

activé dans le bios !
Penser à activer aussi le modem (tu tu tut= cf anciennes connections en 56k)
Les deux sont souvent liés niveau hardware / firmware.

Redémarrer, pas de bouton BT ??

GNOME-BLUETOOTH pour Ubuntu
https://doc.ubuntu-fr.org/bluetooth#problemes_connus

Vérifier les paramètres dans l'utilitaire bluetooth (Paramètres systèmes→Matériel→Bluetooth) PAS ÇA DANS LUBUNTU ?

Cette page s'adresse aux utilisateurs de gnome-bluetooth installé par défaut sur Ubuntu. Pour les utilisateurs des variantes Lubuntu, Xubuntu et Ubuntu Mate, c'est l'utilitaire blueman qui est installé par défaut. 

FICHIER DE CONF

sudo leafpad /etc/bluetooth/main.conf 

(((Si l'utilitaire Bluetooth vous indique que le Bluetooth n'est pas activé, dans un terminal saisir la commande suivante :
sudo /etc/init.d/networking restart Ou  sudo service network-manager restart CF SITE POUR DIFFÉRENCE DE COMMANDE.===

BLUEMAN  lubuntu, mate, xfce
????? Si vous n'arrivez pas à connecter vos périphériques audio, ou si vous n'arrivez pas à vous connecter à un réseau mobile 3G, il est parfois plus simple de désinstaller blueman et d'installer le paquet gnome-bluetooth.  ?????
https://doc.ubuntu-fr.org/blueman

LE HARDWARE Le connaître

 lsusb; dmesg | egrep -i 'blue|firm'  
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 0a5c:2110 Broadcom Corp. BCM2045B (BDC-2) [Bluetooth Controller]
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[   37.121793] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
[   37.228928] iwl4965 0000:03:00.0: loaded firmware version 228.61.2.24
[   37.611735] Bluetooth: Core ver 2.22
[   37.611768] Bluetooth: HCI device and connection manager initialized
[   37.611774] Bluetooth: HCI socket layer initialized
[   37.611778] Bluetooth: L2CAP socket layer initialized
[   37.611821] Bluetooth: SCO socket layer initialized
[   40.572150] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   40.572152] Bluetooth: BNEP filters: protocol multicast
[   40.572160] Bluetooth: BNEP socket layer initialized
[   48.409724] iwl4965 0000:03:00.0: Enabling power save might cause firmware crashes
[   54.664110] Bluetooth: RFCOMM TTY layer initialized
[   54.664118] Bluetooth: RFCOMM socket layer initialized
[   54.664128] Bluetooth: RFCOMM ver 1.11

Info   [   48.409724] iwl4965 0000:03:00.0: Enabling power save might cause firmware crashes

Le chipset est Broadcom Corp. BCM2045B (BDC-2)

BT CONF

 sudo leafpad /etc/bluetooth/main.conf 
[General]

# Default adaper name
# Defaults to 'BlueZ X.YZ'
#Name = BlueZ

# Default device class. Only the major and minor device class bits are
# considered. Defaults to '0x000000'.
#Class = 0x000100

# How long to stay in discoverable mode before going back to non-discoverable
# The value is in seconds. Default is 180, i.e. 3 minutes.
# 0 = disable timer, i.e. stay discoverable forever
#DiscoverableTimeout = 0

# How long to stay in pairable mode before going back to non-discoverable
# The value is in seconds. Default is 0.
# 0 = disable timer, i.e. stay pairable forever
#PairableTimeout = 0

# Automatic connection for bonded devices driven by platform/user events.
# If a platform plugin uses this mechanism, automatic connections will be
# enabled during the interval defined below. Initially, this feature
# intends to be used to establish connections to ATT channels. Default is 60.
#AutoConnectTimeout = 60

# Use vendor id source (assigner), vendor, product and version information for
# DID profile support. The values are separated by ":" and assigner, VID, PID
# and version.
# Possible vendor id source values: bluetooth, usb (defaults to usb)
#DeviceID = bluetooth:1234:5678:abcd

# Do reverse service discovery for previously unknown devices that connect to
# us. This option is really only needed for qualification since the BITE tester
# doesn't like us doing reverse SDP for some test cases (though there could in
# theory be other useful purposes for this too). Defaults to 'true'.
#ReverseServiceDiscovery = true

# Enable name resolving after inquiry. Set it to 'false' if you don't need
# remote devices name and want shorter discovery cycle. Defaults to 'true'.
#NameResolving = true

# Enable runtime persistency of debug link keys. Default is false which
# makes debug link keys valid only for the duration of the connection
# that they were created for.
#DebugKeys = false

# Restricts all controllers to the specified transport. Default value # is "dual", i.e. both BR/EDR and LE enabled (when supported by the HW).
# Possible values: "dual", "bredr", "le" 
#ControllerMode = dual

# Enables Multi Profile Specification support. This allows to specify if # system supports only Multiple Profiles Single Device (MPSD) configuration
# or both Multiple Profiles Single Device (MPSD) and Multiple Profiles Multiple # Devices (MPMD) configurations.
# Possible values: "off", "single", "multiple"
#MultiProfile = off

# Permanently enables the Fast Connectable setting for adapters that # support it. When enabled other devices can connect faster to us,
# however the tradeoff is increased power consumptions. This feature # will fully work only on kernel version 4.1 and newer. Defaults to
# 'false'.
#FastConnectable = false

[Policy]

# The ReconnectUUIDs defines the set of remote services that should try to be reconnected to in case of a link loss (link supervision
# timeout). The policy plugin should contain a sane set of values by default, but this list can be overridden here. By setting the list to
# empty the reconnection feature gets disabled. 
#ReconnectUUIDs=00001112-0000-1000-8000-00805f9b34fb, 0000111f-0000-1000-8000-00805f9b34fb, 0000110a-0000-1000-8000-00805f9b34fb

# ReconnectAttempts define the number of attempts to reconnect after a link lost. Setting the value to 0 disables reconnecting feature.
#ReconnectAttempts=7

# ReconnectIntervals define the set of intervals in seconds to use in between attempts. If the number of attempts defined in ReconnectAttempts is bigger than the set of intervals the last interval is repeated until the last attempt. 
#ReconnectIntervals=1, 2, 4, 8, 16, 32, 64

# AutoEnable defines option to enable all controllers when they are found.
# This includes adapters present on start as well as adapters that are plugged
# in later on. Defaults to 'false'.
AutoEnable=true

Beaucoup de lignes sont commentées, il est probable que cette conf a déjà été modifiée ?!!

Hors ligne

Pied de page des forums