1600X 微星B350 Intel AX200 仍需要热启动才能用 about intelbluetoothfirmware HOT 19 CLOSED

I've noticed that clearing NVRAM usually results in bluetooth not loading on the next boot. As I checked I've found the bluetoothActiveControllerInfo entry in NVRAM and manually added it to the OpenCore section. Afterwards bluetooth did not fail to load anymore after an NVRAM clear. Next I'll try enabling deep sleep again to see if it has an effect.

from intelbluetoothfirmware.

If I understood correctly I'm experience the same issue on AMD Ryzen 3900X, AsRock X570 with the same Intel AX200.

After a cold start with the Injector and Firmware the system is wacky: Apps freeze, I see a lot of errors in the system logs and Bluetooth is not detected at all. If I then reboot everything comes up as expected and the system is working normally including working Bluetooth.

@wfsg00098 thanks for the hint, I'll try without the injector.

from intelbluetoothfirmware.

Nope, it doesn't work. I still need a hot start. @nvollmar

from intelbluetoothfirmware.

再补充一下，我的系统版本是 10.15.3

from intelbluetoothfirmware.

My test device is also ax200 which is well work with this kext, can you please provide your log via command "log show --last 1d | grep IntelFir" and more info to me.

from intelbluetoothfirmware.

By the way, you should remove -v boot param because of too many logs log by this kext, logging waste more time, if upload firmware rotinue last over 5 seconds, it will failed.

from intelbluetoothfirmware.

hot_start.txt
2月1日第一次启动是冷启动，只有firmware没有injector。后面几次操作就加入了injector
如果还需要什么启动测试，请回复我

from intelbluetoothfirmware.

I can not download the attachment, please send it to my email [email protected]

from intelbluetoothfirmware.

sent

from intelbluetoothfirmware.

According to the log, everything works fine, is it version 1.0.1 you are using?

from intelbluetoothfirmware.

yes!

from intelbluetoothfirmware.

On a cold boot with Bluetooth not working I found (only) these logs related to the firmware:

2020-02-01 14:09:37.463018+0100 0x25c      Default     0x0                  0      0    kernel: (IntelBluetoothFirmware) IntelFirmware: interrupt wait
2020-02-01 14:09:37.464686+0100 0x1b4      Default     0x0                  0      0    kernel: (IntelBluetoothFirmware) IntelFirmware: recv event=0x00ff, length=5
2020-02-01 14:09:37.464688+0100 0x1b4      Default     0x0                  0      0    kernel: (IntelBluetoothFirmware) IntelFirmware: 设备固件上传完成
2020-02-01 14:09:37.464691+0100 0x1b4      Default     0x0                  0      0    kernel: (IntelBluetoothFirmware) IntelFirmware: can not proceed response
2020-02-01 14:09:37.464695+0100 0x25c      Default     0x0                  0      0    kernel: (IntelBluetoothFirmware) IntelFirmware: interrupt continue
2020-02-01 14:09:37.464697+0100 0x25c      Default     0x0                  0      0    kernel: (IntelBluetoothFirmware) IntelFirmware: HCI_OP_INTEL_EVENT_MASK
2020-02-01 14:09:37.464698+0100 0x25c      Default     0x0                  0      0    kernel: (IntelBluetoothFirmware) IntelFirmware: opCode=0xfc52, paramLen=8
2020-02-01 14:09:37.464700+0100 0x25c      Default     0x0                  0      0    kernel: (IntelBluetoothFirmware) IntelFirmware: check=87
2020-02-01 14:09:37.467682+0100 0x25c      Default     0x0                  0      0    kernel: (IntelBluetoothFirmware) IntelFirmware: opCode=0xc03, paramLen=0

from intelbluetoothfirmware.

This issue still persists with macOS 10.15.4 and version 1.0.3 of this kext. I don't even see any logs related to IntelFirmware in cold boots.

from intelbluetoothfirmware.

It looks like disabling Deep Sleep in S5 in the BIOS improves the situation.

from intelbluetoothfirmware.

@aluveitie Thanks a lot. I will have a try

from intelbluetoothfirmware.

I've noticed that clearing NVRAM usually results in bluetooth not loading on the next boot. As I checked I've found the bluetoothActiveControllerInfo entry in NVRAM and manually added it to the OpenCore section. Afterwards bluetooth did not fail to load anymore after an NVRAM clear. Next I'll try enabling deep sleep again to see if it has an effect.

@aluveitie That's some exciting & insightful information! By chance, could you share what the NVRAM entry looks like and share just a bit more? Do cold boots now work consistently and is Deep Sleep the only factor causing it to fail in before?

Thanks a whole lot!

from intelbluetoothfirmware.

@alanxurox Here my NVRAM entry (zeroed out):

Disabling Deep Sleep fixed cold boots so far. I still got the issue from time to time when updating existing or adding new kexts in OC.

from intelbluetoothfirmware.

from intelbluetoothfirmware.

Should be fixed in v1.1.1, feel free to reopen of this issue still exists

from intelbluetoothfirmware.