|
Post by 3448689 on Feb 27, 2022 17:56:11 GMT
Hello! Bluetooth sees the mouse and keyboard, but does not connect. Need help.
|
|
|
Post by bitxotica on Apr 2, 2022 17:55:59 GMT
Same issue:
"Bluetooth Devices" picks up a device, seems to pair with it. The device itself (tried with a mouse, keyboard, and headphones on separate occasions) does not recognize the pairing, and the system doesn't respond.
I ran the usual bash stuff to confirm, and even there the system seems sure it has a device at the other end. I was eventually able to pair with bluetoothctl, but it would lose the pairing on wake up or restart; even during if idle for any length of time. Frustrating!
On top of that, the system settings panel doesn't recognize the built-in Bluetooth and instead asks me to insert a Bluetooth dongle.
Also tried using a generic Bluetooth dongle and had the same results -- including being asked for a Bluetooth dongle.]
|
|
|
Post by thewaiter on Apr 2, 2022 18:41:50 GMT
Hello and welcome
OK. So if I understand, you do use an internal BT device for connecting your external devices, right? When I try to help people with BT trouble my first advice is checking hw or sw device switch. We need to install rfkill for that: sudo apt install rfkill now run the command: rfkill and post the outcome here. We can see if your device is turned on.
Good another info is to know more about your BT device. Please post here inxi -Fxz command output for recognizing BT model. Another question. I would like to see some screenshot of settings warnings for better problem understandanding.
Stefan
|
|
|
Post by bitxotica on Apr 4, 2022 17:15:08 GMT
This is the result of rfkill:
And this is from inxi -Fxz:
System: Kernel: 5.4.0-104-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Moksha 0.3.4.17234 Distro: Ubuntu 20.04.4 LTS (Focal Fossa) Machine: Type: Laptop System: Apple product: MacBookAir4,2 v: 1.0 serial: <filter> Mobo: Apple model: Mac-742912EFDBEE19B3 v: MacBookAir4,2 serial: <filter> BIOS: Apple v: MBA41.88Z.0077.B0F.1201241549 date: 01/24/2012 Battery: ID-1: BAT0 charge: 41.9 Wh condition: 42.3/50.2 Wh (84%) model: SMP bq20z451 status: Full Device-1: hidpp_battery_0 model: Logitech Wireless Mouse charge: 55% (should be ignored) status: Discharging CPU: Topology: Dual Core model: Intel Core i5-2557M bits: 64 type: MT MCP arch: Sandy Bridge rev: 7 L2 cache: 3072 KiB flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 13600 Speed: 800 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Apple driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.13 driver: modesetting unloaded: fbdev,vesa resolution: 1440x900~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2) v: 3.3 Mesa 21.2.6 direct render: Yes Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k5.4.0-104-generic Network: Device-1: Broadcom and subsidiaries BCM43224 802.11a/b/g/n vendor: Apple AirPort Extreme driver: wl v: kernel port: efa0 bus ID: 02:00.0 IF: wlp2s0 state: up mac: <filter> Drives: Local Storage: total: 113.00 GiB used: 45.15 GiB (40.0%) ID-1: /dev/sda vendor: Apple model: SSD TS128C size: 113.00 GiB temp: 48 C Partition: ID-1: / size: 110.23 GiB used: 45.15 GiB (41.0%) fs: ext4 dev: /dev/sda3 Sensors: System Temperatures: cpu: 63.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 264 Uptime: 2d 21h 39m Memory: 3.75 GiB used: 2.30 GiB (61.2%) Init: systemd runlevel: 5 Compilers: gcc: 9.4.0 Shell: bash v: 5.0.17
inxi: 3.0.38
This is the problem in more [visual] detail. After setting up the device:
This is what happens in Settings:
Same behavior even if a dongle is actually inserted.
In Terminalogy, running blurtoothctl shows the keyboard when devices is entered at the prompt. connect, however fails for the keyboard. It is occasionally successful for a mouse, not for headphones. Even when connecting this way, the pairing is sporadic, and eventually fails. It reliably fails if the system is suspended and then woken up
Hope that helps!
|
|
|
Post by thewaiter on Apr 4, 2022 18:18:00 GMT
OK
May I see the lsusb command outcome also?
Moreover, I would like to see dmesg command outcome. In case the BT device has a bad firmware, we need to download it and copy to right place in /lib/firmware/ directory
Stefan
BTW, we are also on discord chat for faster feedback...
|
|
|
Post by bitxotica on Apr 4, 2022 18:53:28 GMT
lsusb gets this:
Bus 002 Device 003: ID 05ac:8404 Apple, Inc. Internal Memory Card Reader Bus 002 Device 002: ID 0424:2513 Microchip Technology, Inc. (formerly SMSC) 2.0 Hub Bus 002 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 001 Device 003: ID 05ac:850a Apple, Inc. FaceTime Camera Bus 001 Device 006: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 005: ID 05ac:024c Apple, Inc. FaceTime Camera (Built-in) Bus 001 Device 013: ID 05ac:821f Apple, Inc. Built-in Bluetooth 2.0+EDR HCI Bus 001 Device 015: ID 05ac:820b Apple, Inc. Bluetooth HID Mouse Bus 001 Device 014: ID 05ac:820a Apple, Inc. Bluetooth HID Keyboard Bus 001 Device 010: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 001 Device 002: ID 0424:2513 Microchip Technology, Inc. (formerly SMSC) 2.0 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
dmesg gets this:
[24693.189608] Bluetooth: hci0: command 0x2005 tx timeout [24695.205621] Bluetooth: hci0: command 0x200b tx timeout [24697.221635] Bluetooth: hci0: command 0x200c tx timeout [24721.549732] audit: type=1400 audit(1649091282.352:98): apparmor="DENIED" operation="open" profile="/usr/bin/evince-thumbnailer" name="/tmp/tumbler-XK60ZJ1.png" pid=85756 comm="evince-thumbnai" requested_mask="wc" denied_mask="wc" fsuid=1000 ouid=1000 [31580.417779] Bluetooth: hci0: urb 00000000681a086a failed to resubmit (113) [31580.418006] Bluetooth: hci0: urb 000000006b15254a failed to resubmit (113) [31580.418507] Bluetooth: hci0: urb 0000000059ef7794 failed to resubmit (113) [31590.745700] Bluetooth: hci0: urb 0000000052860bbd failed to resubmit (113) [31590.745940] Bluetooth: hci0: urb 00000000b629c74a failed to resubmit (113) [31590.746189] Bluetooth: hci0: urb 00000000618a011c failed to resubmit (113)
I appreciate all your time in this! Above and beyond...
|
|
|
Post by thewaiter on Apr 4, 2022 18:59:36 GMT
OK
One more command pls: sudo service bluetooth status
and then try sudo service bluetooth restart
and check if helps connecting devices
Stefan
|
|
|
Post by bitxotica on Apr 4, 2022 19:05:01 GMT
Here is the status response:
● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Fri 2022-04-01 15:15:59 EDT; 2 days ago Docs: man:bluetoothd(8) Main PID: 804 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4539) Memory: 2.4M CGroup: /system.slice/bluetooth.service └─804 /usr/lib/bluetooth/bluetoothd
Apr 04 12:08:08 xxxxxxxx bluetoothd[804]: Endpoint unregistered: sender=:1.5> Apr 04 12:08:10 xxxxxxxx bluetoothd[804]: Endpoint registered: sender=:1.58 > Apr 04 12:08:10 xxxxxxxx bluetoothd[804]: Endpoint registered: sender=:1.58 > Apr 04 12:08:49 xxxxxxxx bluetoothd[804]: Failed to set mode: Failed (0x03) Apr 04 12:13:01 xxxxxxxx bluetoothd[804]: Can't get HIDP connection info Apr 04 12:13:43 xxxxxxxx bluetoothd[804]: connect error: Connection refused > Apr 04 12:15:21 xxxxxxxx bluetoothd[804]: Can't get HIDP connection info Apr 04 12:16:02 xxxxxxxx bluetoothd[804]: connect error: Connection refused > Apr 04 14:49:09 xxxxxxxx bluetoothd[804]: Failed to set mode: Failed (0x03) Apr 04 14:49:19 xxxxxxxx bluetoothd[804]: Failed to set mode: Failed (0x03)
restart didn't have any effect... sigh...
|
|
|
Post by thewaiter on Apr 4, 2022 19:07:24 GMT
OK, thx
what about this trick?
sudo modprobe -r btusb sudo modprobe btusb
|
|
|
Post by bitxotica on Apr 4, 2022 19:19:30 GMT
Still nothing. It's also not finding new devices. I also tried adding a bluetooth soundbar, which I've been able to add to virtually every device I have at one time or another, which reliably shows up in the device list no matter what. Even that fails to pair.
I'd say "hardware issue" except that a generic Bluetooth dongle has the same result.
|
|
|
Post by thewaiter on Apr 4, 2022 19:21:30 GMT
May I see all relevant bluetooth lines in dmesg?
dmesg | grep -i 'blue'
|
|
|
Post by bitxotica on Apr 4, 2022 19:57:23 GMT
Sure:
[ 2.657990] usb 1-1.1.3: Product: Bluetooth USB Host Controller [ 5.894098] Bluetooth: Core ver 2.22 [ 5.894262] Bluetooth: HCI device and connection manager initialized [ 5.894267] Bluetooth: HCI socket layer initialized [ 5.894270] Bluetooth: L2CAP socket layer initialized [ 5.894289] Bluetooth: SCO socket layer initialized [ 6.338816] Bluetooth: hci0: BCM: chip id 63 build 0146 [ 6.339813] Bluetooth: hci0: BCM: product 05ac:821f [ 6.340802] Bluetooth: hci0: BCM: features 0x07 [ 6.356817] Bluetooth: hci0: Apple Bluetooth Device [ 8.487715] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 8.487717] Bluetooth: BNEP filters: protocol multicast [ 8.487723] Bluetooth: BNEP socket layer initialized [ 12.616946] Bluetooth: RFCOMM TTY layer initialized [ 12.616954] Bluetooth: RFCOMM socket layer initialized [ 12.616971] Bluetooth: RFCOMM ver 1.11 [21920.165584] Bluetooth: hci0: failed to restart LE scan: status 31 [21920.165592] Bluetooth: hci0: command 0x200c tx timeout [21929.346768] usb 1-1.1.3: Product: Bluetooth USB Host Controller [21929.459288] Bluetooth: hci0: BCM: chip id 63 build 0146 [21929.460287] Bluetooth: hci0: BCM: product 05ac:821f [21929.461282] Bluetooth: hci0: BCM: features 0x07 [21929.477310] Bluetooth: hci0: Apple Bluetooth Device [21933.093553] Bluetooth: hci0: command 0x200c tx timeout [21933.093566] Bluetooth: hci0: failed to restart LE scan: status 31 [21969.061598] Bluetooth: hci0: command 0x0c1a tx timeout [22220.916527] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [22220.916533] Bluetooth: HIDP socket layer initialized [22222.921537] Bluetooth: hci0: command 0x0405 tx timeout [22264.869633] Bluetooth: hci0: command 0x0408 tx timeout [22347.205631] Bluetooth: hci0: command 0x2005 tx timeout [22349.221643] Bluetooth: hci0: command 0x200b tx timeout [22351.237641] Bluetooth: hci0: command 0x200c tx timeout [22404.133620] Bluetooth: hci0: command 0x0408 tx timeout [24693.189608] Bluetooth: hci0: command 0x2005 tx timeout [24695.205621] Bluetooth: hci0: command 0x200b tx timeout [24697.221635] Bluetooth: hci0: command 0x200c tx timeout [31580.417779] Bluetooth: hci0: urb 00000000681a086a failed to resubmit (113) [31580.418006] Bluetooth: hci0: urb 000000006b15254a failed to resubmit (113) [31580.418507] Bluetooth: hci0: urb 0000000059ef7794 failed to resubmit (113) [31590.745700] Bluetooth: hci0: urb 0000000052860bbd failed to resubmit (113) [31590.745940] Bluetooth: hci0: urb 00000000b629c74a failed to resubmit (113) [31590.746189] Bluetooth: hci0: urb 00000000618a011c failed to resubmit (113) [32454.501608] Bluetooth: hci0: urb 000000001c472a06 failed to resubmit (113) [32454.501788] Bluetooth: hci0: urb 0000000078e6836a failed to resubmit (113) [32454.502287] Bluetooth: hci0: urb 00000000264eaf36 failed to resubmit (113) [32464.741591] Bluetooth: hci0: urb 000000003da9e45c failed to resubmit (113) [32464.741841] Bluetooth: hci0: urb 000000006fef9b44 failed to resubmit (113) [32464.742343] Bluetooth: hci0: urb 00000000cde8fcda failed to resubmit (113) [32789.183106] Bluetooth: hci0: BCM: chip id 63 build 0146 [32789.184097] Bluetooth: hci0: BCM: product 05ac:821f [32789.185099] Bluetooth: hci0: BCM: features 0x07 [32789.201072] Bluetooth: hci0: Apple Bluetooth Device [32987.436124] Bluetooth: hci0: urb 00000000678f0b02 failed to resubmit (2) [32990.118717] Bluetooth: hci0: BCM: chip id 63 build 0146 [32990.120699] Bluetooth: hci0: BCM: product 05ac:821f [32990.122695] Bluetooth: hci0: BCM: features 0x07 [32990.139703] Bluetooth: hci0: Bodhidharma [33112.613575] Bluetooth: hci0: inquiry failed: status 0x1f [33112.613582] Bluetooth: hci0: command 0x0401 tx timeout [33126.117629] Bluetooth: hci0: command 0x0405 tx timeout [33246.117659] Bluetooth: hci0: command 0x0408 tx timeout
|
|
|
Post by thewaiter on Apr 4, 2022 20:22:54 GMT
Too late for further investigation. We can continue tomorrow or someone here can help. We have enough data...
S
|
|
|
Post by bitxotica on Apr 4, 2022 20:33:18 GMT
No worries -- thank you for all your input and suggestions. It may be unfixable, which would be a shame, but isn't a disaster. The machine works perfectly in every other way.
Again, your time and effort was truly appreciated!
|
|