NEWS
Bluetooth auf Raspberry 5 aktivieren
-
Hallo
Bluetooth war nie ein Thema für meine Raspi, ich möchte aber jetzt Radar2 mal testen.
Aktuell sieht Bluetooth bei mir so aus:pi@rp5:~ $ sudo systemctl enable bluetooth.service sudo systemctl start bluetooth.service Synchronizing state of bluetooth.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable bluetooth pi@rp5:~ $ blacklist hci_uart blacklist btbcm -bash: blacklist: command not found -bash: blacklist: command not found pi@rp5:~ $ sudo modprobe btusb pi@rp5:~ $ sudo systemctl start bluetooth.service pi@rp5:~ $ sudo systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; preset: enabled) Active: active (running) since Mon 2025-11-24 17:14:06 CET; 33min ago Docs: man:bluetoothd(8) Main PID: 675 (bluetoothd) Status: "Running" Tasks: 1 (limit: 19366) CPU: 360ms CGroup: /system.slice/bluetooth.service └─675 /usr/libexec/bluetooth/bluetoothd Nov 24 17:14:06 rp5 bluetoothd[675]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled Nov 24 17:14:06 rp5 bluetoothd[675]: src/plugin.c:plugin_init() Failed to init mcp plugin Nov 24 17:14:06 rp5 bluetoothd[675]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled Nov 24 17:14:06 rp5 bluetoothd[675]: src/plugin.c:plugin_init() Failed to init bap plugin Nov 24 17:14:06 rp5 bluetoothd[675]: Bluetooth management interface 1.23 initialized Nov 24 17:14:06 rp5 bluetoothd[675]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. Nov 24 17:14:06 rp5 bluetoothd[675]: sap-server: Operation not permitted (1) Nov 24 17:14:06 rp5 bluetoothd[675]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. Nov 24 17:14:06 rp5 bluetoothd[675]: sap-server: Operation not permitted (1) Nov 24 17:14:06 rp5 bluetoothd[675]: Failed to set mode: Failed (0x03)Wie bekomme ich das sauber hin?
P.S. Trixi Installation ist in Vorbereitung ;-) -
Hallo
Bluetooth war nie ein Thema für meine Raspi, ich möchte aber jetzt Radar2 mal testen.
Aktuell sieht Bluetooth bei mir so aus:pi@rp5:~ $ sudo systemctl enable bluetooth.service sudo systemctl start bluetooth.service Synchronizing state of bluetooth.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable bluetooth pi@rp5:~ $ blacklist hci_uart blacklist btbcm -bash: blacklist: command not found -bash: blacklist: command not found pi@rp5:~ $ sudo modprobe btusb pi@rp5:~ $ sudo systemctl start bluetooth.service pi@rp5:~ $ sudo systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; preset: enabled) Active: active (running) since Mon 2025-11-24 17:14:06 CET; 33min ago Docs: man:bluetoothd(8) Main PID: 675 (bluetoothd) Status: "Running" Tasks: 1 (limit: 19366) CPU: 360ms CGroup: /system.slice/bluetooth.service └─675 /usr/libexec/bluetooth/bluetoothd Nov 24 17:14:06 rp5 bluetoothd[675]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled Nov 24 17:14:06 rp5 bluetoothd[675]: src/plugin.c:plugin_init() Failed to init mcp plugin Nov 24 17:14:06 rp5 bluetoothd[675]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled Nov 24 17:14:06 rp5 bluetoothd[675]: src/plugin.c:plugin_init() Failed to init bap plugin Nov 24 17:14:06 rp5 bluetoothd[675]: Bluetooth management interface 1.23 initialized Nov 24 17:14:06 rp5 bluetoothd[675]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. Nov 24 17:14:06 rp5 bluetoothd[675]: sap-server: Operation not permitted (1) Nov 24 17:14:06 rp5 bluetoothd[675]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. Nov 24 17:14:06 rp5 bluetoothd[675]: sap-server: Operation not permitted (1) Nov 24 17:14:06 rp5 bluetoothd[675]: Failed to set mode: Failed (0x03)Wie bekomme ich das sauber hin?
P.S. Trixi Installation ist in Vorbereitung ;-)@michihorn sagte in Bluetooth auf Raspberry 5 aktivieren:
P.S. Trixi Installation ist in Vorbereitung ;-)
Dann schau unter der Trixie per
rfkillmal nach den Schnittstellen.
-
H Homoran verschob dieses Thema von ioBroker Allgemein am
-
@michihorn sagte in Bluetooth auf Raspberry 5 aktivieren:
P.S. Trixi Installation ist in Vorbereitung ;-)
Dann schau unter der Trixie per
rfkillmal nach den Schnittstellen.
@Thomas-Braun sagte in Bluetooth auf Raspberry 5 aktivieren:
rfkill
Die aktuelle Maschine spuckt folgendes aus:
pi@rp5:~ $ rfkill ID TYPE DEVICE SOFT HARD 0 bluetooth hci0 unblocked unblocked 2 wlan phy0 unblocked unblocked -
Hallo
Bluetooth war nie ein Thema für meine Raspi, ich möchte aber jetzt Radar2 mal testen.
Aktuell sieht Bluetooth bei mir so aus:pi@rp5:~ $ sudo systemctl enable bluetooth.service sudo systemctl start bluetooth.service Synchronizing state of bluetooth.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable bluetooth pi@rp5:~ $ blacklist hci_uart blacklist btbcm -bash: blacklist: command not found -bash: blacklist: command not found pi@rp5:~ $ sudo modprobe btusb pi@rp5:~ $ sudo systemctl start bluetooth.service pi@rp5:~ $ sudo systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; preset: enabled) Active: active (running) since Mon 2025-11-24 17:14:06 CET; 33min ago Docs: man:bluetoothd(8) Main PID: 675 (bluetoothd) Status: "Running" Tasks: 1 (limit: 19366) CPU: 360ms CGroup: /system.slice/bluetooth.service └─675 /usr/libexec/bluetooth/bluetoothd Nov 24 17:14:06 rp5 bluetoothd[675]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled Nov 24 17:14:06 rp5 bluetoothd[675]: src/plugin.c:plugin_init() Failed to init mcp plugin Nov 24 17:14:06 rp5 bluetoothd[675]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled Nov 24 17:14:06 rp5 bluetoothd[675]: src/plugin.c:plugin_init() Failed to init bap plugin Nov 24 17:14:06 rp5 bluetoothd[675]: Bluetooth management interface 1.23 initialized Nov 24 17:14:06 rp5 bluetoothd[675]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. Nov 24 17:14:06 rp5 bluetoothd[675]: sap-server: Operation not permitted (1) Nov 24 17:14:06 rp5 bluetoothd[675]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. Nov 24 17:14:06 rp5 bluetoothd[675]: sap-server: Operation not permitted (1) Nov 24 17:14:06 rp5 bluetoothd[675]: Failed to set mode: Failed (0x03)Wie bekomme ich das sauber hin?
P.S. Trixi Installation ist in Vorbereitung ;-)@michihorn sagte in Bluetooth auf Raspberry 5 aktivieren:
Radar2 mal testen.
hast du folgendes ausgeführt?
sudo apt-get install -y coreutils libcap2-bin arp-scan bluetooth bluez libbluetooth-dev libudev-dev net-tools -
@michihorn sagte in Bluetooth auf Raspberry 5 aktivieren:
Radar2 mal testen.
hast du folgendes ausgeführt?
sudo apt-get install -y coreutils libcap2-bin arp-scan bluetooth bluez libbluetooth-dev libudev-dev net-tools -
@crunchip sagte in Bluetooth auf Raspberry 5 aktivieren:
sudo apt-get install -y coreutils libcap2-bin arp-scan bluetooth bluez libbluetooth-dev libudev-dev net-tools
Moin, ja hab ich aus der Doku des Adapters
Gruß
MichaelBei mir (allerdings ein RPi4 auf Trixie) werden ganz andere Module geladen:
echad@chet:~ $ lsmod | grep "blue\|bt" btbcm 24576 1 hci_uart bluetooth 651264 29 hci_uart,btbcm,bnep,rfcomm ecdh_generic 16384 2 bluetooth libaes 12288 4 aes_arm64,bluetooth,ghash_ce,aes_generic rfkill 32768 4 bluetooth,cfg80211 echad@chet:~ $Wo hast du die Info für deine Einstellungen her?
Bei mir startet der bluetooth.service auf sauber:
echad@chet:~ $ systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled) Active: active (running) since Thu 2025-11-20 15:30:38 CET; 4 days ago Invocation: e86385c2415d4f3980a67edb437c90a2 Docs: man:bluetoothd(8) Main PID: 503 (bluetoothd) Status: "Running" Tasks: 1 (limit: 8748) CPU: 14min 58.813s CGroup: /system.slice/bluetooth.service └─503 /usr/libexec/bluetooth/bluetoothd Nov 20 15:30:38 chet systemd[1]: Starting bluetooth.service - Bluetooth service... Nov 20 15:30:38 chet (uetoothd)[503]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists b> Nov 20 15:30:38 chet bluetoothd[503]: Bluetooth daemon 5.82 Nov 20 15:30:38 chet bluetoothd[503]: Starting SDP server Nov 20 15:30:38 chet bluetoothd[503]: Bluetooth management interface 1.23 initialized Nov 20 15:30:38 chet bluetoothd[503]: Battery Provider Manager created Nov 20 15:30:38 chet systemd[1]: Started bluetooth.service - Bluetooth service. -
Im Prinzip ist bei mir nur eine Zeile Sauber: "Bluetooth management.....
alles andere will ich weg habenNov 24 17:14:06 rp5 bluetoothd[675]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
Nov 24 17:14:06 rp5 bluetoothd[675]: src/plugin.c:plugin_init() Failed to init mcp plugin
Nov 24 17:14:06 rp5 bluetoothd[675]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
Nov 24 17:14:06 rp5 bluetoothd[675]: src/plugin.c:plugin_init() Failed to init bap plugin
Nov 24 17:14:06 rp5 bluetoothd[675]: Bluetooth management interface 1.23 initialized
Nov 24 17:14:06 rp5 bluetoothd[675]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Nov 24 17:14:06 rp5 bluetoothd[675]: sap-server: Operation not permitted (1)
Nov 24 17:14:06 rp5 bluetoothd[675]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Nov 24 17:14:06 rp5 bluetoothd[675]: sap-server: Operation not permitted (1)
Nov 24 17:14:06 rp5 bluetoothd[675]: Failed to set mode: Failed (0x03) -
Im Prinzip ist bei mir nur eine Zeile Sauber: "Bluetooth management.....
alles andere will ich weg habenNov 24 17:14:06 rp5 bluetoothd[675]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
Nov 24 17:14:06 rp5 bluetoothd[675]: src/plugin.c:plugin_init() Failed to init mcp plugin
Nov 24 17:14:06 rp5 bluetoothd[675]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
Nov 24 17:14:06 rp5 bluetoothd[675]: src/plugin.c:plugin_init() Failed to init bap plugin
Nov 24 17:14:06 rp5 bluetoothd[675]: Bluetooth management interface 1.23 initialized
Nov 24 17:14:06 rp5 bluetoothd[675]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Nov 24 17:14:06 rp5 bluetoothd[675]: sap-server: Operation not permitted (1)
Nov 24 17:14:06 rp5 bluetoothd[675]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Nov 24 17:14:06 rp5 bluetoothd[675]: sap-server: Operation not permitted (1)
Nov 24 17:14:06 rp5 bluetoothd[675]: Failed to set mode: Failed (0x03) -
hci0: Type: Primary Bus: UART
BD Address: 88:A2:9E:37:34:B3 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING
RX bytes:4650318 acl:842 sco:0 events:169193 errors:0
TX bytes:1497277 acl:831 sco:0 commands:89694 errors:0
pi@rp5:~ $ bluetoothctl
Agent registered
[CHG] Controller 88:A2:9E:37:34:B3 Pairable: yes
[CHG] Controller 88:A2:9E:37:34:B3 Powered: yes
[DEL] Device 4C:66:A6:8D:BB:1C Galaxy-Micha
[bluetooth]# -
hci0: Type: Primary Bus: UART
BD Address: 88:A2:9E:37:34:B3 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING
RX bytes:4650318 acl:842 sco:0 events:169193 errors:0
TX bytes:1497277 acl:831 sco:0 commands:89694 errors:0
pi@rp5:~ $ bluetoothctl
Agent registered
[CHG] Controller 88:A2:9E:37:34:B3 Pairable: yes
[CHG] Controller 88:A2:9E:37:34:B3 Powered: yes
[DEL] Device 4C:66:A6:8D:BB:1C Galaxy-Micha
[bluetooth]#Läuft doch. Was ist konkret das Problem?
-
Ich weiß nicht woher die so Einträge kommen wie "Sap driver initialization failed." usw.
Es gibt einige Einträge wie z.B. Galaxy-Micha, mal connected mal nicht usw.
Das Handy liegt neben mir wir nicht bewegt. Ich denke das wird auch beim Radar2 auffallen, dann ist eine Anwesenheitserkennung schwierig
[CHG] Controller 88:A2:9E:37:34:B3 Powered: no
[CHG] Controller 88:A2:9E:37:34:B3 Discovering: no
[CHG] Controller 88:A2:9E:37:34:B3 Powered: yes
[NEW] Device 4C:66:A6:8D:BB:1C Galaxy-Micha
[CHG] Device 4C:66:A6:8D:BB:1C Connected: no
[DEL] Device 4C:66:A6:8D:BB:1C Galaxy-Micha
[CHG] Controller 88:A2:9E:37:34:B3 Powered: no
[CHG] Controller 88:A2:9E:37:34:B3 Discovering: no
[CHG] Controller 88:A2:9E:37:34:B3 Powered: yes
[NEW] Device 4C:66:A6:8D:BB:1C Galaxy-Micha
[CHG] Device 4C:66:A6:8D:BB:1C Connected: no
[DEL] Device 4C:66:A6:8D:BB:1C Galaxy-Micha
[CHG] Controller 88:A2:9E:37:34:B3 Powered: no
[CHG] Controller 88:A2:9E:37:34:B3 Discovering: no
[CHG] Controller 88:A2:9E:37:34:B3 Powered: yes
[CHG] Controller 88:A2:9E:37:34:B3 Powered: no
[CHG] Controller 88:A2:9E:37:34:B3 Discovering: no
[CHG] Controller 88:A2:9E:37:34:B3 Powered: yes
[CHG] Controller 88:A2:9E:37:34:B3 Powered: no
[CHG] Controller 88:A2:9E:37:34:B3 Discovering: no
[CHG] Controller 88:A2:9E:37:34:B3 Powered: yes
[CHG] Controller 88:A2:9E:37:34:B3 Powered: no
[CHG] Controller 88:A2:9E:37:34:B3 Discovering: no
[CHG] Controller 88:A2:9E:37:34:B3 Powered: yes
[NEW] Device 4C:66:A6:8D:BB:1C Galaxy-Micha
[CHG] Device 4C:66:A6:8D:BB:1C Connected: no
[DEL] Device 4C:66:A6:8D:BB:1C Galaxy-Micha
[CHG] Controller 88:A2:9E:37:34:B3 Powered: no
[CHG] Controller 88:A2:9E:37:34:B3 Discovering: no
[CHG] Controller 88:A2:9E:37:34:B3 Powered: yes
[NEW] Device 4C:66:A6:8D:BB:1C Galaxy-Micha
[CHG] Device 4C:66:A6:8D:BB:1C Connected: no
[CHG] Controller 88:A2:9E:37:34:B3 Powered: no
[CHG] Controller 88:A2:9E:37:34:B3 Discovering: no
[CHG] Controller 88:A2:9E:37:34:B3 Powered: yes
[DEL] Device 4C:66:A6:8D:BB:1C Galaxy-Micha -
Ich weiß nicht woher die so Einträge kommen wie "Sap driver initialization failed." usw.
Es gibt einige Einträge wie z.B. Galaxy-Micha, mal connected mal nicht usw.
Das Handy liegt neben mir wir nicht bewegt. Ich denke das wird auch beim Radar2 auffallen, dann ist eine Anwesenheitserkennung schwierig
[CHG] Controller 88:A2:9E:37:34:B3 Powered: no
[CHG] Controller 88:A2:9E:37:34:B3 Discovering: no
[CHG] Controller 88:A2:9E:37:34:B3 Powered: yes
[NEW] Device 4C:66:A6:8D:BB:1C Galaxy-Micha
[CHG] Device 4C:66:A6:8D:BB:1C Connected: no
[DEL] Device 4C:66:A6:8D:BB:1C Galaxy-Micha
[CHG] Controller 88:A2:9E:37:34:B3 Powered: no
[CHG] Controller 88:A2:9E:37:34:B3 Discovering: no
[CHG] Controller 88:A2:9E:37:34:B3 Powered: yes
[NEW] Device 4C:66:A6:8D:BB:1C Galaxy-Micha
[CHG] Device 4C:66:A6:8D:BB:1C Connected: no
[DEL] Device 4C:66:A6:8D:BB:1C Galaxy-Micha
[CHG] Controller 88:A2:9E:37:34:B3 Powered: no
[CHG] Controller 88:A2:9E:37:34:B3 Discovering: no
[CHG] Controller 88:A2:9E:37:34:B3 Powered: yes
[CHG] Controller 88:A2:9E:37:34:B3 Powered: no
[CHG] Controller 88:A2:9E:37:34:B3 Discovering: no
[CHG] Controller 88:A2:9E:37:34:B3 Powered: yes
[CHG] Controller 88:A2:9E:37:34:B3 Powered: no
[CHG] Controller 88:A2:9E:37:34:B3 Discovering: no
[CHG] Controller 88:A2:9E:37:34:B3 Powered: yes
[CHG] Controller 88:A2:9E:37:34:B3 Powered: no
[CHG] Controller 88:A2:9E:37:34:B3 Discovering: no
[CHG] Controller 88:A2:9E:37:34:B3 Powered: yes
[NEW] Device 4C:66:A6:8D:BB:1C Galaxy-Micha
[CHG] Device 4C:66:A6:8D:BB:1C Connected: no
[DEL] Device 4C:66:A6:8D:BB:1C Galaxy-Micha
[CHG] Controller 88:A2:9E:37:34:B3 Powered: no
[CHG] Controller 88:A2:9E:37:34:B3 Discovering: no
[CHG] Controller 88:A2:9E:37:34:B3 Powered: yes
[NEW] Device 4C:66:A6:8D:BB:1C Galaxy-Micha
[CHG] Device 4C:66:A6:8D:BB:1C Connected: no
[CHG] Controller 88:A2:9E:37:34:B3 Powered: no
[CHG] Controller 88:A2:9E:37:34:B3 Discovering: no
[CHG] Controller 88:A2:9E:37:34:B3 Powered: yes
[DEL] Device 4C:66:A6:8D:BB:1C Galaxy-Micha@michihorn sagte in Bluetooth auf Raspberry 5 aktivieren:
Ich weiß nicht woher die so Einträge kommen wie "Sap driver initialization failed." usw.
Die sind wurscht.
Edit: Wenn es stört:
https://www.heise.de/ratgeber/BlueZ-kann-ominoesen-SAP-Server-nicht-starten-4716249.htmlEs gibt einige Einträge wie z.B. Galaxy-Micha, mal connected mal nicht usw.
Möglicherweise legt das Handy Bluetooth Schlafen, wenn es nicht gebraucht wird.
Und BITTE Text aus der Konsole in CODETAGS einbetten...