From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 204589] Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
Date: Wed, 11 Jan 2023 22:06:42 +0000 [thread overview]
Message-ID: <bug-204589-62941-Pjw8FCdf79@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204589-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204589
--- Comment #12 from queeup (queeup@zoho.com) ---
```
$ lspci -nnk | grep 0280 -A3
03:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723]
(rev 1a)
Subsystem: Intel Corporation Wi-Fi 6 AX200NGW [8086:0084]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
$ lsusb -d 8087:
Bus 001 Device 004: ID 8087:0029 Intel Corp. AX200 Bluetooth
$ bluetoothctl info
Device 84:FC:FE:E0:A5:F0 (public)
Alias: Apple Magic Trackpad
Class: 0x00002594
Icon: input-tablet
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
WakeAllowed: yes
LegacyPairing: yes
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: usb:v05ACp030Ed0160
$ uname -a
Linux fedora 5.19.6-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Aug 31 17:58:15
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/os-release
NAME="Fedora Linux"
VERSION="36.20220902.0 (Silverblue)"
ID=fedora
VERSION_ID=36
VERSION_CODENAME=""
PLATFORM_ID="platform:f36"
PRETTY_NAME="Fedora Linux 36.20220902.0 (Silverblue)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:36"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora-silverblue/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=36
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=36
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
VARIANT="Silverblue"
VARIANT_ID=silverblue
OSTREE_VERSION='36.20220902.0'
$ rpm -qa linux-firmware iwlax2xx-firmware bluez
bluez-5.65-1.fc36.x86_64
iwlax2xx-firmware-20220815-138.fc36.noarch
linux-firmware-20220815-138.fc36.noarch
$ dmesg | grep firmware
[ 3.059539] i915 0000:00:02.0: [drm] Finished loading DMC firmware
i915/kbl_dmc_ver1_04.bin (v1.4)
[ 7.048785] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 7.101611] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[ 7.181529] iwlwifi 0000:03:00.0: Direct firmware load for
iwlwifi-cc-a0-72.ucode failed with error -2
[ 7.242302] iwlwifi 0000:03:00.0: loaded firmware version 71.058653f6.0
cc-a0-71.ucode op_mode iwlmvm
[ 8.865213] Bluetooth: hci0: Waiting for firmware download to complete
$ dmesg | grep Bluetooth
[ 6.876698] Bluetooth: Core ver 2.22
[ 6.876723] Bluetooth: HCI device and connection manager initialized
[ 6.876727] Bluetooth: HCI socket layer initialized
[ 6.876728] Bluetooth: L2CAP socket layer initialized
[ 6.876734] Bluetooth: SCO socket layer initialized
[ 7.047790] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[ 7.048779] Bluetooth: hci0: Device revision is 1
[ 7.048781] Bluetooth: hci0: Secure boot is enabled
[ 7.048782] Bluetooth: hci0: OTP lock is enabled
[ 7.048783] Bluetooth: hci0: API lock is enabled
[ 7.048784] Bluetooth: hci0: Debug lock is disabled
[ 7.048785] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 7.101611] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[ 7.101745] Bluetooth: hci0: Boot Address: 0x24800
[ 7.101747] Bluetooth: hci0: Firmware Version: 20-28.22
[ 8.865213] Bluetooth: hci0: Waiting for firmware download to complete
[ 8.865758] Bluetooth: hci0: Firmware loaded in 1722796 usecs
[ 8.865806] Bluetooth: hci0: Waiting for device to boot
[ 8.880761] Bluetooth: hci0: Device booted in 14623 usecs
[ 8.880768] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[ 8.883561] Bluetooth: hci0: Found Intel DDC parameters:
intel/ibt-20-1-3.ddc
[ 8.885766] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 8.886770] Bluetooth: hci0: Firmware revision 0.3 build 20 week 28 2022
[ 8.948322] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 8.948325] Bluetooth: BNEP filters: protocol multicast
[ 8.948330] Bluetooth: BNEP socket layer initialized
[ 10.495877] Bluetooth: RFCOMM TTY layer initialized
[ 10.495885] Bluetooth: RFCOMM socket layer initialized
[ 10.495932] Bluetooth: RFCOMM ver 1.11
$ dmesg | grep iwlwifi
[ 7.081904] iwlwifi 0000:03:00.0: enabling device (0000 -> 0002)
[ 7.181529] iwlwifi 0000:03:00.0: Direct firmware load for
iwlwifi-cc-a0-72.ucode failed with error -2
[ 7.242004] iwlwifi 0000:03:00.0: api flags index 2 larger than supported by
driver
[ 7.242021] iwlwifi 0000:03:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version:
89.3.35.37
[ 7.242302] iwlwifi 0000:03:00.0: loaded firmware version 71.058653f6.0
cc-a0-71.ucode op_mode iwlmvm
[ 7.535978] iwlwifi 0000:03:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz,
REV=0x340
[ 7.692651] iwlwifi 0000:03:00.0: Detected RF HR B3, rfid=0x10a100
[ 7.765022] iwlwifi 0000:03:00.0: base HW address: 8c:c6:81:9d:1c:5a
[ 7.784984] iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0
$ dmesg | grep Bluetooth
[ 6.876698] Bluetooth: Core ver 2.22
[ 6.876723] Bluetooth: HCI device and connection manager initialized
[ 6.876727] Bluetooth: HCI socket layer initialized
[ 6.876728] Bluetooth: L2CAP socket layer initialized
[ 6.876734] Bluetooth: SCO socket layer initialized
[ 7.047790] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[ 7.048779] Bluetooth: hci0: Device revision is 1
[ 7.048781] Bluetooth: hci0: Secure boot is enabled
[ 7.048782] Bluetooth: hci0: OTP lock is enabled
[ 7.048783] Bluetooth: hci0: API lock is enabled
[ 7.048784] Bluetooth: hci0: Debug lock is disabled
[ 7.048785] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 7.101611] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[ 7.101745] Bluetooth: hci0: Boot Address: 0x24800
[ 7.101747] Bluetooth: hci0: Firmware Version: 20-28.22
[ 8.865213] Bluetooth: hci0: Waiting for firmware download to complete
[ 8.865758] Bluetooth: hci0: Firmware loaded in 1722796 usecs
[ 8.865806] Bluetooth: hci0: Waiting for device to boot
[ 8.880761] Bluetooth: hci0: Device booted in 14623 usecs
[ 8.880768] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[ 8.883561] Bluetooth: hci0: Found Intel DDC parameters:
intel/ibt-20-1-3.ddc
[ 8.885766] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 8.886770] Bluetooth: hci0: Firmware revision 0.3 build 20 week 28 2022
[ 8.948322] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 8.948325] Bluetooth: BNEP filters: protocol multicast
[ 8.948330] Bluetooth: BNEP socket layer initialized
[ 10.495877] Bluetooth: RFCOMM TTY layer initialized
[ 10.495885] Bluetooth: RFCOMM socket layer initialized
[ 10.495932] Bluetooth: RFCOMM ver 1.11
```
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-01-11 22:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 10:19 [Bug 204589] New: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes bugzilla-daemon
2022-01-11 17:20 ` [Bug 204589] " bugzilla-daemon
2022-06-15 22:19 ` bugzilla-daemon
2022-06-16 13:04 ` bugzilla-daemon
2023-01-11 21:15 ` bugzilla-daemon
2023-01-11 21:19 ` bugzilla-daemon
2023-01-11 21:23 ` bugzilla-daemon
2023-01-11 22:06 ` bugzilla-daemon [this message]
2023-05-22 11:54 ` bugzilla-daemon
2023-06-02 16:37 ` bugzilla-daemon
2023-06-23 14:23 ` bugzilla-daemon
2023-11-02 8:17 ` bugzilla-daemon
2023-12-14 20:54 ` bugzilla-daemon
2023-12-16 23:20 ` bugzilla-daemon
2023-12-17 0:31 ` bugzilla-daemon
2024-01-24 16:49 ` bugzilla-daemon
2024-01-24 19:41 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-204589-62941-Pjw8FCdf79@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).