staging.inyokaproject.org

kurt@kurt-1000HE:~$ cat /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
kurt@kurt-1000HE:~$ 
kurt@kurt-1000HE:~$ 

Dann lasse uns mal was machen

sudo -H leafpad /etc/bluetooth/hcid.conf

Inhalt löschen und folgendes einfügen

[General]
device 34:88:5D:22:C6:42 {
    name "Logitech Keyboard K480";
    auth enable;
    encrypt enable;}

Speichern,dann

sudo -H leafpad /etc/bluetooth/input.conf

unten anfügen

UserspaceHID=true

Speichern,dann

sudo -H leafpad /etc/bluetooth/main.conf

unter anfügen

AutoEnable=true

Speichern,Neustart. Nach dem Neustart nicht die Tastatur verbinden sondern folgende Ausgabe zeigen

lsmod | grep hidp

Bis gleich 😉

Der letzte Befehl erzeugt nichts.

Das habe ich mir gedacht,nun

sudo modprobe hidp

wie sieht es nun aus mit der Tastatur?

Leider noch nichts ☹

Ich bin leider bis Mittwoch nicht erreichbar, darf ich mich dann nochmal melden?

Na klar,vielleicht ist bis dahin ja eine Lösung in Sicht 😈

sicher 👍

Kleiner Versuch mit großer Hoffnung 😉 Zuerst was löschen was angelegt wurde

sudo rm /etc/default/bluetooth

Dann wie schon mal gehabt (sind ein paar Änderungen drin)

sudo -H leafpad /etc/btkbd.conf

eintrag

BTKBDMAC="34:88:5D:22:C6:42"
HCIDEVICE="hci0"

nächste

sudo -H leafpad /etc/systemd/system/btkbd.service

eintrag

[Unit]
Description=systemd Unit to automatically start a Bluetooth keyboard
Documentation=https://wiki.archlinux.org/index.php/Bluetooth_Keyboard
ConditionPathExists=/etc/btkbd.conf
ConditionPathExists=/usr/bin/hcitool
ConditionPathExists=/usr/bin/hciconfig

[Service]
Type=oneshot
EnvironmentFile=/etc/btkbd.conf
ExecStart=
ExecStart=/usr/bin/hciconfig ${HCIDEVICE} up
# ignore errors on connect, spurious problems with bt? so start next command with -
ExecStart=-/usr/bin/hcitool cc ${BTKBDMAC}
ExecStartPost=/bin/echo "Bluetooth_Keyboard_gestartet"

[Install]
WantedBy=bluetooth.target

Aktivieren

sudo systemctl enable btkbd.service

Nach Neustart zeige

dmesg | egrep -i 'blue|firm'

sowie

sudo systemctl status bluetooth

kurt@kurt-1000HE:~$ dmesg | egrep -i 'blue|firm'
[    0.242415] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query honored via cmdline
[    0.247119] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
[    0.341150] pci 0000:03:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format)
[    7.052231] psmouse serio1: elantech: assuming hardware version 2 (with firmware version 0x020030)
[   26.561887] Bluetooth: Core ver 2.22
[   26.561980] Bluetooth: HCI device and connection manager initialized
[   26.561991] Bluetooth: HCI socket layer initialized
[   26.561999] Bluetooth: L2CAP socket layer initialized
[   26.562037] Bluetooth: SCO socket layer initialized
[   40.408397] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   40.408402] Bluetooth: BNEP filters: protocol multicast
[   40.408414] Bluetooth: BNEP socket layer initialized
[  104.408680] Bluetooth: RFCOMM TTY layer initialized
[  104.408696] Bluetooth: RFCOMM socket layer initialized
[  104.408720] Bluetooth: RFCOMM ver 1.11
[  111.814096] Bluetooth: Unexpected continuation frame (len 0)
[  116.090270] Bluetooth: Unexpected continuation frame (len 0)
[  133.102504] Bluetooth: Unexpected continuation frame (len 0)
[  147.560266] Bluetooth: Unexpected continuation frame (len 0)
[  147.588201] Bluetooth: Unexpected continuation frame (len 0)
kurt@kurt-1000HE:~$ 

kurt@kurt-1000HE:~$ sudo systemctl status bluetooth
[sudo] Passwort für kurt: 
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset
   Active: active (running) since Wed 2017-12-06 18:50:32 CET; 4min 54s ago
     Docs: man:bluetoothd(8)
 Main PID: 531 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
           └─531 /usr/lib/bluetooth/bluetoothd

Dez 06 18:50:27 kurt-1000HE systemd[1]: Starting Bluetooth service...
Dez 06 18:50:28 kurt-1000HE bluetoothd[531]: Bluetooth daemon 5.46
Dez 06 18:50:32 kurt-1000HE systemd[1]: Started Bluetooth service.
Dez 06 18:50:33 kurt-1000HE bluetoothd[531]: Starting SDP server
Dez 06 18:50:34 kurt-1000HE bluetoothd[531]: Bluetooth management interface 1.14
Dez 06 18:51:46 kurt-1000HE bluetoothd[531]: No cache for 34:88:5D:22:C6:42
Dez 06 18:51:50 kurt-1000HE bluetoothd[531]: No cache for 34:88:5D:22:C6:42
Dez 06 18:52:07 kurt-1000HE bluetoothd[531]: No cache for 34:88:5D:22:C6:42
Dez 06 18:52:21 kurt-1000HE bluetoothd[531]: No cache for 34:88:5D:22:C6:42
lines 1-19/19 (END)


● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2017-12-06 18:50:32 CET; 4min 54s ago
     Docs: man:bluetoothd(8)
 Main PID: 531 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
           └─531 /usr/lib/bluetooth/bluetoothd

Dez 06 18:50:27 kurt-1000HE systemd[1]: Starting Bluetooth service...
Dez 06 18:50:28 kurt-1000HE bluetoothd[531]: Bluetooth daemon 5.46
Dez 06 18:50:32 kurt-1000HE systemd[1]: Started Bluetooth service.
Dez 06 18:50:33 kurt-1000HE bluetoothd[531]: Starting SDP server
Dez 06 18:50:34 kurt-1000HE bluetoothd[531]: Bluetooth management interface 1.14 initialized
Dez 06 18:51:46 kurt-1000HE bluetoothd[531]: No cache for 34:88:5D:22:C6:42
Dez 06 18:51:50 kurt-1000HE bluetoothd[531]: No cache for 34:88:5D:22:C6:42
Dez 06 18:52:07 kurt-1000HE bluetoothd[531]: No cache for 34:88:5D:22:C6:42
Dez 06 18:52:21 kurt-1000HE bluetoothd[531]: No cache for 34:88:5D:22:C6:42
~
~
~
~
lines 1-19/19 (END)

Da waren wir ja schon mal

No cache for 34:88:5D:22:C6:42

Weiter habe ich auch keine Idee.Lösche alles und dann war es das von meiner Seite aus.

sudo systemctl disable btkbd.service

sudo rm /etc/systemd/system/btkbd.service

sudo rm /etc/btkbd.conf

Das mache ich und vielen, vielen Dank.