Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: Bluetooth device pairs after reboot, then becomes unresponsive after a couple of minutes

  1. #1
    Join Date
    Jun 2008
    Location
    Pacific Northwest
    Posts
    369

    Default Bluetooth device pairs after reboot, then becomes unresponsive after a couple of minutes

    Not sure what the problem is. The mouse worked as expected with an earlier version of Leap 15.0 install. However, that install resulted in a machine that was slow to boot. It pulled up about half a dozen boot possibilities.

    I did a reinstall, and selected the option to delete prior partitions. The install was flawless. Boot time is fast. The machine not works great. Well almost.

    After a reboot, I can pair the mouse to the machine using the bluetooth image on the right hand corner, or using the configure desktop tool. When I use either tool, it shows a variety of bluetooth devices near my location. I can easily pair the device.

    After about 2 minutes, the bluetooth mouse becomes unresponsive. If I attempt to re-pair the device, the bluetooth tool will not disconnect from the device. If I attempt to connect to another bluetooth device, it does not show any devices in the area and appears to be frozen.

    I tried setting the power management function to leave the bluetooth driver on at all times and performed a reboot. This did not help.

    Per YaST, the following software packages are installed searching for bluetooth: bluedevil5, bluez, libbluetooth3, lissbc1, pulseaudio-module-bluetooth, sbc. All show the most recent versions are installed.

    I think I have the correct software installed. I think I am using the bluetooth paring tool correctly.

    Any ideas would be helpful. Maybe I need to use bash? I forget what bash command I need to use.

    Thank you in advance.
    The greatest obstacle to discovery is not ignorance, it is the illusion of knowledge.
    Daniel J. Boorstin US Patent Office

  2. #2
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    3,661

    Default AW: Bluetooth device pairs after reboot, then becomes unresponsive after a couple of minutes

    Please post as root:
    Code:
    journalctl -b | grep -i bluet
    Use Code-Tags, the small # in the editor.

  3. #3
    Join Date
    Jun 2008
    Location
    Pacific Northwest
    Posts
    369

    Default Re: Bluetooth device pairs after reboot, then becomes unresponsive after a couple of minutes

    Code:
    # journalctl -b | grep -i bluet
    Apr 13 19:55:37 linux-blh6 kernel: Bluetooth: Core ver 2.22
    Apr 13 19:55:37 linux-blh6 kernel: Bluetooth: HCI device and connection manager initiali
    zed
    Apr 13 19:55:37 linux-blh6 kernel: Bluetooth: HCI socket layer initialized
    Apr 13 19:55:37 linux-blh6 kernel: Bluetooth: L2CAP socket layer initialized
    Apr 13 19:55:37 linux-blh6 kernel: Bluetooth: SCO socket layer initialized
    Apr 13 19:55:37 linux-blh6 kernel: Bluetooth: hci0: read Intel version: 370710010002030d
    56
    Apr 13 19:55:37 linux-blh6 kernel: Bluetooth: hci0: Intel device is already patched. pat
    ch num: 56
    Apr 13 19:55:39 linux-blh6 systemd[1]: Starting Bluetooth service...
    Apr 13 19:55:39 linux-blh6 bluetoothd[1048]: Bluetooth daemon 5.48
    Apr 13 19:55:39 linux-blh6 bluetoothd[1048]: Starting SDP server
    Apr 13 19:55:39 linux-blh6 systemd[1]: Started Bluetooth service.
    Apr 13 19:55:39 linux-blh6 systemd[1]: Reached target Bluetooth.
    Apr 13 19:55:39 linux-blh6 kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    Apr 13 19:55:39 linux-blh6 kernel: Bluetooth: BNEP filters: protocol multicast
    Apr 13 19:55:39 linux-blh6 kernel: Bluetooth: BNEP socket layer initialized
    Apr 13 19:55:39 linux-blh6 dbus-daemon[1053]: [system] Activating via systemd: service n
    ame='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested 
    by ':1.1' (uid=0 pid=1048 comm="/usr/lib/bluetooth/bluetoothd ")
    Apr 13 19:55:39 linux-blh6 bluetoothd[1048]: Bluetooth management interface 1.14 initial
    ized
    Apr 13 19:55:42 linux-blh6 NetworkManager[1304]: <info>  [1555210542.4114] Loaded device
     plugin: NMBluezManager (/usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so)
    Apr 13 19:55:58 linux-blh6 bluetoothd[1048]: Endpoint registered: sender=:1.37 path=/Med
    iaEndpoint/A2DPSource
    Apr 13 19:55:58 linux-blh6 bluetoothd[1048]: Endpoint registered: sender=:1.37 path=/Med
    iaEndpoint/A2DPSink
    Apr 13 19:55:58 linux-blh6 kernel: Bluetooth: RFCOMM TTY layer initialized
    Apr 13 19:55:58 linux-blh6 kernel: Bluetooth: RFCOMM socket layer initialized
    Apr 13 19:55:58 linux-blh6 kernel: Bluetooth: RFCOMM ver 1.11
    Apr 13 19:56:00 linux-blh6 kdeinit5[1877]: bluedevil: Bluetooth operational changed true
    Apr 13 19:56:04 linux-blh6 plasmashell[1921]: Warning: all files used by qml by the plas
    moid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.
    plasma.bluetooth/contents/code/logic.js" was expected at QUrl("file:///usr/share/plasma/
    plasmoids/org.kde.plasma.bluetooth/contents/ui/logic.js")
    Apr 13 19:56:04 linux-blh6 plasmashell[1921]: org.kde.plasmaquick: New Applet  "Bluetoot
    h" with a weight of 92
    Apr 13 19:56:05 linux-blh6 plasmashell[1921]: org.kde.plasmaquick: Delayed preload of  "
    Bluetooth" after 0.193 seconds
    Apr 13 19:56:05 linux-blh6 plasmashell[1921]: org.kde.plasmaquick: Applet "Bluetooth" lo
    aded after 145 msec
    Apr 13 19:56:11 linux-blh6 plasmashell[1921]: org.kde.plasmaquick: Applet "Bluetooth" lo
    aded after 0 msec
    Apr 13 19:56:11 linux-blh6 plasmashell[1921]: org.kde.plasmaquick: Increasing score for 
    "Bluetooth" to 97
    Apr 13 19:56:20 linux-blh6 kernel: Bluetooth: HIDP (Human Interface Emulation) ver 1.2
    Apr 13 19:56:20 linux-blh6 kernel: Bluetooth: HIDP socket layer initialized
    Apr 13 19:56:20 linux-blh6 bluetoothd[1048]: Can't get HIDP connection info
    Apr 13 19:56:22 linux-blh6 kernel: input: Insignia Bluetooth Mouse as /devices/pci0000:0
    0/0000:00:13.0/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:256/0005:0A5C:F789.0003/input/input1
    0
    Apr 13 19:56:22 linux-blh6 kernel: hid-generic 0005:0A5C:F789.0003: input,hidraw2: BLUET
    OOTH HID v0.01 Mouse [Insignia Bluetooth Mouse] on d0:7e:35:70:b5:3d
    Apr 13 19:56:23 linux-blh6 upowerd[1755]: treating change event as add on /sys/devices/p
    ci0000:00/0000:00:13.0/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:256/0005:0A5C:F789.0003/powe
    r_supply/hid-20:73:24:03:59:f9-battery
    Apr 13 20:00:11 linux-blh6 kernel: Bluetooth: hci0 command 0x0804 tx timeout
    Apr 13 20:08:44 linux-blh6 kernel: Bluetooth: hci0 link tx timeout
    Apr 13 20:08:44 linux-blh6 kernel: Bluetooth: hci0 killing stalled connection 20:73:24:0
    3:59:f9
    Apr 13 20:08:46 linux-blh6 kernel: Bluetooth: hci0 command 0x041f tx timeout
    Apr 13 20:08:47 linux-blh6 bluetoothd[1048]: Endpoint unregistered: sender=:1.37 path=/M
    ediaEndpoint/A2DPSource
    Apr 13 20:08:47 linux-blh6 bluetoothd[1048]: Endpoint unregistered: sender=:1.37 path=/M
    ediaEndpoint/A2DPSink
    Apr 13 20:08:47 linux-blh6 systemd[1]: bluetooth.target: Unit not needed anymore. Stoppi
    ng.
    Apr 13 20:08:47 linux-blh6 systemd[1]: Stopped target Bluetooth.
    Apr 13 20:08:47 linux-blh6 dbus-daemon[1053]: [system] Rejected send message, 1 matched 
    rules; type="error", sender=":1.37" (uid=1000 pid=1952 comm="/usr/bin/pulseaudio --start
     --log-target=syslog ") interface="(unset)" member="(unset)" error name="org.bluez.Media
    Endpoint1.Error.NotImplemented" requested_reply="0" destination=":1.1" (uid=0 pid=1048 c
    omm="/usr/lib/bluetooth/bluetoothd ")
    Apr 13 20:08:47 linux-blh6 dbus-daemon[1053]: [system] Rejected send message, 1 matched 
    rules; type="error", sender=":1.37" (uid=1000 pid=1952 comm="/usr/bin/pulseaudio --start
     --log-target=syslog ") interface="(unset)" member="(unset)" error name="org.bluez.Media
    Endpoint1.Error.NotImplemented" requested_reply="0" destination=":1.1" (uid=0 pid=1048 c
    omm="/usr/lib/bluetooth/bluetoothd ")
    Apr 13 20:08:47 linux-blh6 dbus-daemon[1053]: [system] Rejected send message, 1 matched 
    rules; type="error", sender=":1.37" (uid=1000 pid=1952 comm="/usr/bin/pulseaudio --start
     --log-target=syslog ") interface="(unset)" member="(unset)" error name="org.bluez.Media
    Endpoint1.Error.NotImplemented" requested_reply="0" destination=":1.1" (uid=0 pid=1048 c
    omm="/usr/lib/bluetooth/bluetoothd ")
    Apr 13 20:08:47 linux-blh6 dbus-daemon[1053]: [system] Rejected send message, 1 matched 
    rules; type="error", sender=":1.37" (uid=1000 pid=1952 comm="/usr/bin/pulseaudio --start
     --log-target=syslog ") interface="(unset)" member="(unset)" error name="org.bluez.Media
    Endpoint1.Error.NotImplemented" requested_reply="0" destination=":1.1" (uid=0 pid=1048 c
    omm="/usr/lib/bluetooth/bluetoothd ")
    Apr 13 20:08:47 linux-blh6 kernel: Bluetooth: hci0: read Intel version: 370710010002030d
    56
    Apr 13 20:08:47 linux-blh6 kernel: Bluetooth: hci0: Intel device is already patched. pat
    ch num: 56
    Apr 13 20:08:47 linux-blh6 bluetoothd[1048]: Endpoint registered: sender=:1.37 path=/Med
    iaEndpoint/A2DPSource
    Apr 13 20:08:47 linux-blh6 bluetoothd[1048]: Endpoint registered: sender=:1.37 path=/Med
    iaEndpoint/A2DPSink
    Apr 13 20:08:48 linux-blh6 systemd[1]: Reached target Bluetooth.
    
    
    The greatest obstacle to discovery is not ignorance, it is the illusion of knowledge.
    Daniel J. Boorstin US Patent Office

  4. #4
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    10,414
    Blog Entries
    1

    Default Re: Bluetooth device pairs after reboot, then becomes unresponsive after a couple of minutes

    Regarding Bluetooth, it's important to post the Desktop you're using because DEs like KDE have their own BT components... And, from your posted log I see you are indeed using KDE Plasma.

    Based on the following log entry you posted
    Code:
    Apr 13 19:56:23 linux-blh6 upowerd[1755]: treating change event as add on /sys/devices/pci0000:00/0000:00:13.0/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:256/0005:0A5C:F789.0003/powe
    r_supply/hid-20:73:24:03:59:f9-battery
    I suspect you are configured to run in a power saving mode.
    Find that KDE setting and change it to "Performance" or something similar, to not save power.

    Assuming you are running on a laptop,
    My SOP is to configure the laptop to run "Full Performance" when plugged into AC and enable a power saving mode when running on battery, and I further adjust my display to dim slightly when on battery so that I know when something has happened to my AC.

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  5. #5
    Join Date
    Jun 2008
    Location
    Pacific Northwest
    Posts
    369

    Default Re: Bluetooth device pairs after reboot, then becomes unresponsive after a couple of minutes

    Thanks. Sorry about not indicating I am using Leap 15.0.

    I think I have the energy savings correct.The power saving settings are set to turn the screen off after 10 minutes (the default). I manually set the wireless controls to leave on WiFi and bluetooth.

    Also, the hardware is a bare-bones Zotac box.
    The greatest obstacle to discovery is not ignorance, it is the illusion of knowledge.
    Daniel J. Boorstin US Patent Office

  6. #6
    Join Date
    Jun 2008
    Location
    Pacific Northwest
    Posts
    369

    Default Re: Bluetooth device pairs after reboot, then becomes unresponsive after a couple of minutes

    This keeps getting more weird.
    I did a logout/login. The bluetooth adapter shows bluetooth is powered off. I clicked the checkbox to power it, clicked apply and the box unchecked itself.

    Code:
     # journalctl -b | grep -i bluet
    Apr 15 09:21:34 linux-blh6 kernel: Bluetooth: Core ver 2.22
    Apr 15 09:21:34 linux-blh6 kernel: Bluetooth: HCI device and connection manager initialized
    Apr 15 09:21:34 linux-blh6 kernel: Bluetooth: HCI socket layer initialized
    Apr 15 09:21:34 linux-blh6 kernel: Bluetooth: L2CAP socket layer initialized
    Apr 15 09:21:34 linux-blh6 kernel: Bluetooth: SCO socket layer initialized
    Apr 15 09:21:34 linux-blh6 kernel: Bluetooth: hci0: read Intel version: 370710010002030d00
    Apr 15 09:21:34 linux-blh6 kernel: Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.0.2.3.d.bseq
    Apr 15 09:21:34 linux-blh6 kernel: Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
    Apr 15 09:21:36 linux-blh6 systemd[1]: Starting Bluetooth service...
    Apr 15 09:21:36 linux-blh6 bluetoothd[1103]: Bluetooth daemon 5.48
    Apr 15 09:21:36 linux-blh6 systemd[1]: Started Bluetooth service.
    Apr 15 09:21:36 linux-blh6 systemd[1]: Reached target Bluetooth.
    Apr 15 09:21:36 linux-blh6 bluetoothd[1103]: Starting SDP server
    Apr 15 09:21:36 linux-blh6 kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    Apr 15 09:21:36 linux-blh6 kernel: Bluetooth: BNEP filters: protocol multicast
    Apr 15 09:21:36 linux-blh6 kernel: Bluetooth: BNEP socket layer initialized
    Apr 15 09:21:36 linux-blh6 bluetoothd[1103]: Bluetooth management interface 1.14 initialized
    Apr 15 09:21:36 linux-blh6 dbus-daemon[1027]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='
    dbus-org.freedesktop.hostname1.service' requested by ':1.4' (uid=0 pid=1103 comm="/usr/lib/bluetooth/bluetoothd ")
    Apr 15 09:21:38 linux-blh6 NetworkManager[1284]: <info>  [1555345298.9179] Loaded device plugin: NMBluezManager (/usr/lib64/Ne
    tworkManager/libnm-device-plugin-bluetooth.so)
    Apr 15 09:21:55 linux-blh6 bluetoothd[1103]: Endpoint registered: sender=:1.35 path=/MediaEndpoint/A2DPSource
    Apr 15 09:21:55 linux-blh6 bluetoothd[1103]: Endpoint registered: sender=:1.35 path=/MediaEndpoint/A2DPSink
    Apr 15 09:21:55 linux-blh6 kernel: Bluetooth: RFCOMM TTY layer initialized
    Apr 15 09:21:55 linux-blh6 kernel: Bluetooth: RFCOMM socket layer initialized
    Apr 15 09:21:55 linux-blh6 kernel: Bluetooth: RFCOMM ver 1.11
    Apr 15 09:21:56 linux-blh6 kdeinit5[1855]: bluedevil: Bluetooth operational changed true
    Apr 15 09:22:02 linux-blh6 plasmashell[1900]: Warning: all files used by qml by the plasmoid should be in ui/. The file in the
     path "file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/code/logic.js" was expected at QUrl("file:///usr/s
    hare/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/logic.js")
    Apr 15 09:22:02 linux-blh6 plasmashell[1900]: org.kde.plasmaquick: New Applet  "Bluetooth" with a weight of 92
    Apr 15 09:22:03 linux-blh6 plasmashell[1900]: org.kde.plasmaquick: Delayed preload of  "Bluetooth" after 0.484 seconds
    Apr 15 09:22:03 linux-blh6 plasmashell[1900]: org.kde.plasmaquick: Applet "Bluetooth" loaded after 221 msec
    Apr 15 09:22:09 linux-blh6 plasmashell[1900]: org.kde.plasmaquick: Applet "Bluetooth" loaded after 0 msec
    Apr 15 09:22:09 linux-blh6 plasmashell[1900]: org.kde.plasmaquick: Increasing score for "Bluetooth" to 97
    Apr 15 09:22:12 linux-blh6 kernel: Bluetooth: HIDP (Human Interface Emulation) ver 1.2
    Apr 15 09:22:12 linux-blh6 kernel: Bluetooth: HIDP socket layer initialized
    Apr 15 09:22:12 linux-blh6 bluetoothd[1103]: Can't get HIDP connection info
    Apr 15 09:22:14 linux-blh6 kernel: input: Insignia Bluetooth Mouse as /devices/pci0000:00/0000:00:13.0/usb6/6-1/6-1:1.0/blueto
    oth/hci0/hci0:256/0005:0A5C:F789.0003/input/input10
    Apr 15 09:22:14 linux-blh6 kernel: hid-generic 0005:0A5C:F789.0003: input,hidraw2: BLUETOOTH HID v0.01 Mouse [Insignia Bluetoo
    th Mouse] on d0:7e:35:70:b5:3d
    Apr 15 09:22:15 linux-blh6 upowerd[1733]: treating change event as add on /sys/devices/pci0000:00/0000:00:13.0/usb6/6-1/6-1:1.
    0/bluetooth/hci0/hci0:256/0005:0A5C:F789.0003/power_supply/hid-20:73:24:03:59:f9-battery
    Apr 15 09:26:18 linux-blh6 kernel: Bluetooth: hci0 command 0x0804 tx timeout
    Apr 15 09:26:18 linux-blh6 bluetoothd[1103]: Endpoint unregistered: sender=:1.35 path=/MediaEndpoint/A2DPSource
    Apr 15 09:26:18 linux-blh6 bluetoothd[1103]: Endpoint unregistered: sender=:1.35 path=/MediaEndpoint/A2DPSink
    Apr 15 09:26:20 linux-blh6 kernel: Bluetooth: hci0 command 0x0c52 tx timeout
    Apr 15 09:26:30 linux-blh6 bluetoothd[1103]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource
    Apr 15 09:26:30 linux-blh6 bluetoothd[1103]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSink
    Apr 15 09:26:32 linux-blh6 kdeinit5[3242]: bluedevil: Bluetooth operational changed true
    Apr 15 09:26:41 linux-blh6 plasmashell[3287]: Warning: all files used by qml by the plasmoid should be in ui/. The file in the
     path "file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/code/logic.js" was expected at QUrl("file:///usr/s
    hare/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/logic.js")
    Apr 15 09:26:41 linux-blh6 plasmashell[3287]: org.kde.plasmaquick: New Applet  "Bluetooth" with a weight of 89
    Apr 15 09:26:42 linux-blh6 plasmashell[3287]: org.kde.plasmaquick: Delayed preload of  "Bluetooth" after 0.86 seconds
    Apr 15 09:26:43 linux-blh6 plasmashell[3287]: org.kde.plasmaquick: Applet "Bluetooth" loaded after 252 msec
    Apr 15 09:26:49 linux-blh6 plasmashell[3287]: org.kde.plasmaquick: Applet "Bluetooth" loaded after 0 msec
    Apr 15 09:26:49 linux-blh6 plasmashell[3287]: org.kde.plasmaquick: Increasing score for "Bluetooth" to 94
    Apr 15 09:27:21 linux-blh6 plasmashell[3287]: org.kde.plasmaquick: Applet "Bluetooth" loaded after 0 msec
    Apr 15 09:27:21 linux-blh6 plasmashell[3287]: org.kde.plasmaquick: Increasing score for "Bluetooth" to 99
    Apr 15 09:27:29 linux-blh6 kernel: Bluetooth: hci0 command 0xfc3f tx timeout
    Apr 15 09:27:37 linux-blh6 bluetoothd[1103]: Failed to remove UUID: Not Powered (0x0f)
    Apr 15 09:27:37 linux-blh6 kernel: Bluetooth: hci0: turning off Intel device LED failed (-110)
    Apr 15 09:28:42 linux-blh6 kernel: Bluetooth: hci0 urb ffff8802eec8c900 failed to resubmit (113)
    Apr 15 09:28:50 linux-blh6 bluetoothd[1103]: Failed to set mode: Failed (0x03)
    Apr 15 09:28:52 linux-blh6 kernel: Bluetooth: hci0 urb ffff8802c370c400 failed to resubmit (113)
    Apr 15 09:29:00 linux-blh6 bluetoothd[1103]: Failed to set mode: Failed (0x03)
    Apr 15 09:29:13 linux-blh6 kernel: Bluetooth: hci0 urb ffff8802baa32000 failed to resubmit (113)
    Apr 15 09:29:21 linux-blh6 bluetoothd[1103]: Failed to set mode: Failed (0x03)
    Apr 15 09:29:23 linux-blh6 kernel: Bluetooth: hci0 urb ffff8802ba467d00 failed to resubmit (113)
    Apr 15 09:29:31 linux-blh6 bluetoothd[1103]: Failed to set mode: Failed (0x03)
    Apr 15 09:29:34 linux-blh6 kernel: Bluetooth: hci0 urb ffff8802cf5e8c00 failed to resubmit (113)
    Apr 15 09:29:42 linux-blh6 bluetoothd[1103]: Failed to set mode: Failed (0x03)
    Apr 15 09:29:44 linux-blh6 kernel: Bluetooth: hci0 urb ffff8802d290b800 failed to resubmit (113)
    Apr 15 09:29:52 linux-blh6 bluetoothd[1103]: Failed to set mode: Failed (0x03)
    Apr 15 09:29:54 linux-blh6 kernel: Bluetooth: hci0 urb ffff8802dc9b3d00 failed to resubmit (113)
    Apr 15 09:30:02 linux-blh6 bluetoothd[1103]: Failed to set mode: Failed (0x03)
    
    
    The greatest obstacle to discovery is not ignorance, it is the illusion of knowledge.
    Daniel J. Boorstin US Patent Office

  7. #7
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    10,414
    Blog Entries
    1

    Default Re: Bluetooth device pairs after reboot, then becomes unresponsive after a couple of minutes

    Googled your error.
    You might see if the first hit from the archwiki bbs applies to you, too.

    https://www.google.com/search?q=hci0...c3f+tx+timeout

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  8. #8
    Join Date
    Jun 2008
    Location
    Pacific Northwest
    Posts
    369

    Default Re: Bluetooth device pairs after reboot, then becomes unresponsive after a couple of minutes

    Thank you for the insight. It looks like I am getting the same timeout error. Here is a portion of dmesg:

    Code:
    #dsmesg
    ...
     1820.313211] Bluetooth: hci0: link tx timeout
    [ 1820.313221] Bluetooth: hci0: killing stalled connection 20:73:24:03:59:f9
    [ 1834.230895] usb 6-1: reset full-speed USB device number 2 using ohci-pci
    [ 1854.899106] usb 6-1: reset full-speed USB device number 2 using ohci-pci
    [ 1861.231073] usb 6-1: reset full-speed USB device number 2 using ohci-pci
    [ 1864.207180] usb 6-1: reset full-speed USB device number 2 using ohci-pci
    [ 1917.799359] usb 6-1: reset full-speed USB device number 2 using ohci-pci
    [ 1920.703451] usb 6-1: reset full-speed USB device number 2 using ohci-pci
    [ 1923.719515] usb 6-1: reset full-speed USB device number 2 using ohci-pci
    
    The MAC address shown is for the mouse.

    The post indicates something about autosave. I have no idea how to implement that.
    The greatest obstacle to discovery is not ignorance, it is the illusion of knowledge.
    Daniel J. Boorstin US Patent Office

  9. #9
    Join Date
    Jun 2008
    Location
    Pacific Northwest
    Posts
    369

    Default Re: Bluetooth device pairs after reboot, then becomes unresponsive after a couple of minutes

    A searched this bug. It appears there has been a longstanding problem with the Intel firmware driver for the bluetooth device. The wifi device is an Intel AC3160.

    Code:
    inux-kerc:/lib/firmware> ls --size | grep 3160
     596 iwlwifi-3160-10.ucode
     668 iwlwifi-3160-12.ucode
     676 iwlwifi-3160-13.ucode
     900 iwlwifi-3160-16.ucode
     900 iwlwifi-3160-17.ucode
     656 iwlwifi-3160-7.ucode
     652 iwlwifi-3160-8.ucode
     656 iwlwifi-3160-9.ucode
    
    
    version 17 is the latest. Strange that its size is identical to version 16.
    The greatest obstacle to discovery is not ignorance, it is the illusion of knowledge.
    Daniel J. Boorstin US Patent Office

  10. #10
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    3,661

    Default AW: Bluetooth device pairs after reboot, then becomes unresponsive after a couple of minutes

    Is this an Laptop?

    Are laptop-mode-tools or tlp installed?
    Code:
    zypper se -si laptop tlp
    Last edited by Sauerland; 18-Apr-2019 at 22:42.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •