Intel AC 8265: Booting from Linux to Windows results in non-functional Bluetooth

[SSven]

When booting Linux, the Linux drivers upload firmware build 103 to the Bluetooth part of my Intel AC 8265 wireless adapter. Build 103 seems to be the latest one available to Linux users:

https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/commit/?id=1dcf7691f623c24762976e2debe05248d627e814 https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/commit/?id=1dcf7691f623c24762976e2debe05248d627e814

Then, when rebooting the into Windows, the Windows driver doesn't work. In the device manager, the Intel Bluetooth device is marked with a yellow triangle and STATUS_DEVICE_POWER_FAILURE is shown as an error message when checking the properties of the device.

When booting to Windows first, a subsequent reboot to Linux reports that the firmware of the Bluetooth adapter is build 107. My best guess here is that the Windows driver won't accept build 103 and thus refuses to work with it. It seems like the Windows driver does not or cannot upgrade the device firmware to build 107 if build 103 has already been uploaded. Ideally it would simply reset the device and upload whatever firmware it comes with.

Is this a known issue?

How can this issue be resolved?

How is the Windows driver supposed to behave in a dual boot environment?

[idata]

Hello Bannix,

We checked with our specialists and they confirmed the issue was present for the AC 7260. We would like to inform that the using the latest driver should resolve this condition:Intel® Wireless Bluetooth® for Windows® 10* [19.71.0]Intel® PROSet/Wireless Software and Drivers for Windows® 10* [19.70.0]Please let us know if the issue is solved with these updates.Regards,Jonathan B.

[KKleb]

Hi, yes it is indeed resolved for the 7260 already. My problem however was not the Windows driver as I initially thought (it was already up-to-date with the fix included). I fixed my problem in linux: I ran "sudo apt get install firmware-iwlwifi" in linux and after that the problem disappeared. So it seems that when both drivers are on the latest version, no problems should arise. Thank you anyway for the fast support!

Regards,

Bannix

[idata]

Hello Bannix,

We are glad to know the issue is resolved for you as well and that your system working fine now.Regards,Jonathan B.

[HYang27]

I would like to point out that the problem persists for AC 3160, which is expected since on the driver download page it states that the driver for AC 3160 remains to be the old version. I ended up disabling bluetooth in linux.

[idata]

Hello yangnw,

1. Which version of Windows* are you using?2. Which Linux* distribution and version are you using?3. Which PROSet/Wireless Software and driver version do you have installed in Windows*?Best regards,Carlos A.

[HYang27]

Thanks for responding.

1. Windows 10, 1709.

2. elementaryOS 0.4.1, based on Ubuntu 16.04.2 LTS.

3. Software versions are 20.10.2 (Latest) for WIFI and 20.0.0 (Latest) for bluetooth.

Also:

- After power cycling and logging in to Windows, bluetooth works.- When it works in Windows, after rebooting to Linux, bluetooth does not work. In `systemctl status bluetooth.service`, several errors states "Not enough free handles to register service." Then, after rebooting to Windows, bluetooth device goes yellow triangle and "Code 10."

- If in Linux I go `systemctl disable bluetooth.service` and power cycle, bluetooth works in in Windows regardless whether I have booted to Linux previously.

I did not test otherwise, because I don't use bluetooth in Linux (I use bluetooth for audio only). But it's still annoying when I boot a LiveCD, which enables bluetooth by default, and breaks the bluetooth.

[idata]

Hello yangnw,

Thank you for all the info. Please bear with us while we look into this.Best regards,Carlos A.

[idata]

Hello yangnw,

Although similar, this issue seems to have a different root cause than the one originally reported in this thread. We're currently investigating and will let you know as soon as we have any updates.Best regards,Carlos A.

[idata]

Hello yangnw,

Is it possible to send the system log (dmesg log) from Linux?

1. dmesg
2. hciconfig –a
3. uname –r

We are trying to reproduce the issue but it will be good to have a log. Please send those via private message if you do not want make the public.

Thanks

David O.

[HYang27]

I've PM'ed you the logs as requested.

I also noticed that, if the same bluetooth speaker is connected both on Windows and then on Linux, and when I power cycle to Windows, the bluetooth functionality is normal, but when I connect to the speaker, it auto-disconnects after a few seconds. But if I remove the device and re-connect to it, it works as normal.

You can reach me by posting here, since I am receiving email notifications for it.

[idata]

Hello yangnw

Thanks for sharing the log files. We will evaluate the information there and will let you know,

In the mean time can you please fill out the attached escalation checklist and send that back to me via PM?

thanks

David

[ACurc]

I've upgraded the Windows bluetooth driver to version 20.10 and seeing the problem again. It was previously solved with version 19.50.

Please fix it on the newer versions too.Thanks

[idata]

Hello htrex,

Thanks for the report. A new Bluetooth® driver should be available for you to test soon.In the mean time, please continue using the working version.Best regards,Carlos A.