- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello StarBoy,
Thank you for posting on the Intel® communities. I want to understand what happened just as much as you do.
To have a better view of this behavior, I will need the following:
1. Did you run all the driver updates from your Linux distributor?
2. Is the Wi-Fi working?
3. Run the Intel® System Support Utility (Intel® SSU) to gather more details about the system.
- Download the Intel® SSU and save the application on your computer: https://www.intel.com/content/www/us/en/download/18895/26735/intel-system-support-utility-for-the-linux-operating-system.html?
- Open the application, check the "Everything" checkbox, and click "Scan" to see the system and device information. The Intel® SSU defaults to the "Summary View" on the output screen following the scan. Click the menu where it says "Summary" to change to "Detailed View".
- To save your scan, click Next and click Save.
4. Run the following commands and send us the outcome
- hciconfig -a -> check the details
- hciconfig -i <interface name> up -> Enable the adapter if hciconfig shows that adapter is down
- lsusb | grep 8087 -> check if the system is identifying adapter
- modinfo btintel -> check if bluetooth drivers are loaded
- dmesg | grep Bluetooth -> check the firmware version
- grep Bluetooth /var/log/syslog | grep -i -e "Firmware revision" -e "ibt" -> If the firmware version is not available in dmesg, then check in syslog
Best regards,
Deivid A.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Deivid
Thank you for your mail.
1- I am a newbie in using Linux. How exactly can I run driver updates from my linux distributor.
I have done sudo apt update and sudo upgrade
I tried downloading https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/ latest commit to my download folder and then copy paste the repo to lib/firmware directory and doing a cold reboot.
I tried using a older kernel 5.13
I tried using a external usb bluetooth dongle (TP Link UB500)
I tried erasing the disk and reinstalling ubuntu
None worked
2- Yes, wireless is working from out of the box.
3- I wasn't able to find the user interface for linux but I was able to run the ssu command with all params set to 1. Would that be sufficient. Is it safe to share the output txt publicly here? If yes, I can share the output txt here.
4-
hciconfig -a
hci0: Type: Primary Bus: USB
BD Address: F4:A4:75:AA:F9:D7 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN
RX bytes:2673 acl:0 sco:0 events:195 errors:0
TX bytes:6087 acl:0 sco:0 commands:173 errors:0
Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: PERIPHERAL ACCEPT
Name: 'ay19'
Class: 0x7c0104
Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony
Device Class: Computer, Desktop workstation
HCI Version: (0xc) Revision: 0x3484
LMP Version: (0xc) Subversion: 0x3484
Manufacturer: Intel Corp. (2)
________________________________________________________________________
________________________________________________________________________
lsusb | grep 8087
Bus 003 Device 003: ID 8087:0032 Intel Corp. AX210 Bluetooth
________________________________________________________________________
modinfo btintel
filename: /lib/modules/6.2.0-36-generic/kernel/drivers/bluetooth/btintel.ko
firmware: intel/ibt-12-16.ddc
firmware: intel/ibt-12-16.sfi
firmware: intel/ibt-11-5.ddc
firmware: intel/ibt-11-5.sfi
license: GPL
version: 0.1
description: Bluetooth support for Intel devices ver 0.1
author: Marcel Holtmann <marcel@holtmann.org>
srcversion: 68B7D184FCB1A38C3434228
depends: bluetooth
retpoline: Y
intree: Y
name: btintel
vermagic: 6.2.0-36-generic SMP preempt mod_unload modversions
sig_id: PKCS#7
signer: Build time autogenerated kernel key
sig_key: (I omitted here)
sig_hashalgo: sha512
signature: (I omitted here to shorten the message)
________________________________________________________________________
sudo dmesg | grep Bluetooth
[ 5.488897] Bluetooth: Core ver 2.22
[ 5.488921] Bluetooth: HCI device and connection manager initialized
[ 5.488924] Bluetooth: HCI socket layer initialized
[ 5.488926] Bluetooth: L2CAP socket layer initialized
[ 5.488931] Bluetooth: SCO socket layer initialized
[ 5.559714] Bluetooth: hci0: Firmware timestamp 2022.5 buildtype 1 build 38020
[ 5.565302] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
[ 5.565316] Bluetooth: hci0: Boot Address: 0x100800
[ 5.565318] Bluetooth: hci0: Firmware Version: 132-5.22
[ 5.565320] Bluetooth: hci0: Firmware already loaded
[ 8.004321] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 8.004324] Bluetooth: BNEP filters: protocol multicast
[ 8.004329] Bluetooth: BNEP socket layer initialized
[ 8.004989] Bluetooth: MGMT ver 1.22
[ 381.716150] Bluetooth: RFCOMM TTY layer initialized
[ 381.716156] Bluetooth: RFCOMM socket layer initialized
[ 381.716159] Bluetooth: RFCOMM ver 1.11
________________________________________________________________________
grep Bluetooth /var/log/syslog | grep -i -e "Firmware revision" -e "ibt"
Oct 31 20:47:57 ay19 kernel: [ 5.565302] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
This is how the outputs looks like. The ibt file names are different in dmesg(0041-0041) and btintel commands(11-16 & 11-5) commands does that mean anything?
Please let me know if you'd need further info.
Best,
Aras
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello StarBoy,
Thanks for your response. You can share the report from Intel® System Support Utility (Intel® SSU) in this thread, I will check if the information in your file will help me with the investigation. Do not worry about it.
I will be waiting for your response.
Regards,
Deivid A.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Deivid,
Here is the report from Intel® System Support Utility (Intel® SSU).
Please let me know if you'd need additional info.
Best,
Aras
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello StarBoy,
Thank you for the information provided
I will proceed to check the issue internally and post back soon with more details.
Best regards,
Deivid A.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello StarBoy,
Thanks for your patience. From your logs, I noticed that your Intel AX210 is at an older firmware version 59 (iwlwifi-ty-a0-gf-a0-59.ucode). I recommend you update to the newer mainline kernel (e.g. Ver. 6.5) from kernel.org and ensure the AX210 can be loaded with firmware version 83, then the Bluetooth shall be upgraded concurrently.
Please let me know if you were able to perform the update and if the issue persists.
Regards,
Deivid A.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello StarBoy,
I am following up to confirm if you were able to perform the firmware update and to know if the issue persists.
Let me know if you need further assistance.
Best regards,
Deivid A.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Deivid,
Thank you for getting back to me and for your patience on me following up your instructions.
As far as I understand the new linux-kernel(e.g. 6.5) is not fully supported on Ubuntu 22.04 LTS Jammy yet see here . However I saw some workaround using a ppa, see here.
At first I was able to boot with kernel 6.5 reaching to gui only in recovery mode, but after running sudo nvidia-smi the screen got locked and I logged in again and I was able to boot regular mode afterwards. I believe that nvidia-smi code reactivated the nvidia drivers.
Following the latest firmware git tree , I downloaded and moved the iwlwifi-ty-a0-gf-a0-81.ucode iwlwifi-ty-a0-gf-a0-83.ucode files in to /lib/firmware/ directory and this is the output I get:
aras@ay19:~$ uname -r
6.5-060500-generic
aras@ay19:~$ sudo dmesg | grep iwlwifi
[ 5.238142] iwlwifi 0000:08:00.0: enabling device (0000 -> 0002)
[ 5.240337] iwlwifi 0000:08:00.0: Detected crf-id 0x400410, cnv-id 0x400410 wfpm id 0x80000000
[ 5.240342] iwlwifi 0000:08:00.0: PCI dev 2725/0024, rev=0x420, rfid=0x10d000
[ 5.247467] iwlwifi 0000:08:00.0: api flags index 2 larger than supported by driver
[ 5.247507] iwlwifi 0000:08:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.41
[ 5.252451] iwlwifi 0000:08:00.0: loaded firmware version 83.e8f84e98.0 ty-a0-gf-a0-83.ucode op_mode iwlmvm
[ 5.394007] iwlwifi 0000:08:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
[ 5.402994] iwlwifi 0000:08:00.0: WRT: Invalid buffer destination
[ 5.543147] iwlwifi 0000:08:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
[ 5.543163] iwlwifi 0000:08:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[ 5.543181] iwlwifi 0000:08:00.0: WFPM_AUTH_KEY_0: 0x90
[ 5.543195] iwlwifi 0000:08:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x1
[ 5.543676] iwlwifi 0000:08:00.0: loaded PNVM version 64acdc51
[ 5.555610] iwlwifi 0000:08:00.0: Detected RF GF, rfid=0x10d000
[ 5.623508] iwlwifi 0000:08:00.0: base HW address: f4:a4:75:aa:f9:d3
[ 5.638371] iwlwifi 0000:08:00.0 wlp8s0: renamed from wlan0
[ 6.609631] iwlwifi 0000:08:00.0: WRT: Invalid buffer destination
[ 6.749752] iwlwifi 0000:08:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
[ 6.749769] iwlwifi 0000:08:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[ 6.749782] iwlwifi 0000:08:00.0: WFPM_AUTH_KEY_0: 0x90
[ 6.749799] iwlwifi 0000:08:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x1
[ 6.833377] iwlwifi 0000:08:00.0: Registered PHC clock: iwlwifi-PTP, with index: 1
aras@ay19:~$ sudo dmesg | grep Blue
[ 5.218283] Bluetooth: Core ver 2.22
[ 5.219066] Bluetooth: HCI device and connection manager initialized
[ 5.219071] Bluetooth: HCI socket layer initialized
[ 5.219073] Bluetooth: L2CAP socket layer initialized
[ 5.219079] Bluetooth: SCO socket layer initialized
[ 5.245926] Bluetooth: hci0: Firmware timestamp 2022.5 buildtype 1 build 38020
[ 5.257415] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
[ 5.257428] Bluetooth: hci0: Boot Address: 0x100800
[ 5.257430] Bluetooth: hci0: Firmware Version: 132-5.22
[ 5.257431] Bluetooth: hci0: Firmware already loaded
[ 6.488936] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 6.488938] Bluetooth: BNEP filters: protocol multicast
[ 6.488940] Bluetooth: BNEP socket layer initialized
[ 6.489577] Bluetooth: MGMT ver 1.22
[ 20.692162] Bluetooth: RFCOMM TTY layer initialized
[ 20.692167] Bluetooth: RFCOMM socket layer initialized
[ 20.692170] Bluetooth: RFCOMM ver 1.11
After this, the jbl flip 5 connects immidietly, however the sound either comes asynchorous or low quality. The HP 350/355 keyboard is not shown in the bluetooth list at all.
I just wanted to give you further updates but will continue investigation. Please let me know if something looks off.
kind regards,
Aras
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello StarBoy,
Thanks for your response. Before I continue with the investigation I want to know if the only difference after the updates is that the JBL flip 5 now gives asynchronous or low-quality sound and the keyboard does not show at all.
Also, have you encountered connection issues with other Bluetooth devices such as phones, mice, headsets, etc?
Regards,
Deivid A.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Deivid,
Before the updates, JBL flip 5 would rarely connect but now it connects at every trial. In both case it gives asynchronous or low-quality sound.
I tried to connect, PS5 Controller, apple magic keyboard and my iphone 13 but they wouldn't show up in the list. Airpods pro would show up in the list but couldn't pair.
Best,
Aras
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello StarBoy,
Thanks for the confirmation. This will allow me to continue with the investigation and will post back in case I need further information or if I have any recommendations for you.
Regards,
Deivid A.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello StarBoy,
Thanks for your time. I would like to let you know several factors can contribute to Bluetooth connectivity and quality, including Linux distributions, drivers, and Bluetooth hardware device variability.
I recommend you check with the Ubuntu distro or seek information or possible solutions from online resources or Linux communities. Also, you can try to move the WiFi network to 5GHz/6GHz so that there will be no interference for Bluetooth on 2.4 GHz.
You can get in contact with Asus to confirm Linux compatibility and keep your Kernel up-to-date as we're continually improving and fixing connectivity and performance in future releases.
Please keep in mind that this thread will no longer be monitored by Intel.
Regards,
Deivid A.
Intel Customer Support Technician
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page