search

zearp / Nucintosh

Intel NUC Hackintosh Stuff
730 stars 87 forks source link

Bluetooth failed to load after a day's sleep #64

Closed ajai-akkarapaka closed 3 years ago

ajai-akkarapaka commented 3 years ago

Please provide the follow information:

tried all by changing kexts order and resetting nvram and loading efi from usb stick but bluetooth doesn't turn on

it was working fine after updating from Big Sur. Connections were stable until a deep sleep

ajai-akkarapaka commented 3 years ago

Screen Shot 2021-10-29 at 10 51 28 AM do I need to reinstall the OS

ajai-akkarapaka commented 3 years ago

log.txt

The log

zearp commented 3 years ago

Make sure you use the latest release. There might still be some bugs regarding 3rd party bluetooth. I have a test machine with the Intel wireless and bluetooth enabled. I've paired a mouse with it and it works ok also after sleep. You may have encountered a bug that must be fixed by either Apple or the community.

There's not much more I can do then update the kexts to their latest versions when there are new commits that fix bluetooth issues. But it is known that Monterey is causing bluetooth issues. This also happens on real Macs with 3rd party bluetooth cards.

You can also try updating the BlueToolFixup kext yourself by using the latest builds form the Dortania website.

The kext is inside this package: https://dortania.github.io/builds/?product=BrcmPatchRAM&viewall=true&version=2.6.1

I will put the test machine to sleep and see if I can reproduce this issue. I did not test anything with prolonged sleep. Only short sleep as my time has been limited lately. I can't put in the hours I used to.

zearp commented 3 years ago

I just noticed you're using a Broadcom bluetooth card. So the above fix is useless for you. You may have to try some different things that I can't really help out with now as my time is too limited to help out with setting up any hardware that's not in the machine by default.

The best you can do is to search for your card model in combination with Monterey. It is likely others will run into the same issues. I don't have any 4350 based cards myself so I can't test anything in that regard.

I'm using real AirPort cards in my NUCs except for the test machine which remains unmodified. My Broadcom cards work fine as they're natively supported by Monterey.

ajai-akkarapaka commented 3 years ago

I am using the builtin intel bluetooth that came with the machine unmodified. After updating with the latest EFI and upgrading it to Monterey yesterday. everything was working fine. After last night sleep, woke up in the computer and Bluetooth as missing. so restarted the machine but it was not showing at all. So I guess some thing with the bluetoolfixup issue.

zearp commented 3 years ago

Make sure you use the latest release from the repo. On my test machine the bluetooth module works correctly and it shows up differently than in your screenshot: Screenshot 2021-10-29 at 14 25 24 Note there is no mention of Broadcom on my screenshot. It shows up as 3rd party dongle. I'm using the latest release from the repo on my test machine. Bluetooth works and doesn't disappear after sleep. But I can't test overnight sleep on the machine any time soon. I can test sleep for a few hours and that's it.

Make sure your bluetooth module shows up like in my screenshot. I'm quite sure you're having an older version of BlueToolFixup installed.

My test machine is a stock NUC with nothing modified and all settings done according to the guide and the EFI only has the serials changed.

ajai-akkarapaka commented 3 years ago

I have disabled the kexts completely yet.. it is showing bluetooth is off despite showing bluetooth unavailable. Yesterday I had a third party dongle unknown chipset but not today. now I disabled and remove Screen Shot 2021-10-29 at 6 23 17 PM d intel bluetooth kext and blue tool fix kext too.. and removed all the plist files of bluetooth and restarted the machine

ajai-akkarapaka commented 3 years ago

my nuc is also stock

zearp commented 3 years ago

I find it very weird that you get a different chipset showing up. If you're using the same kexts as me we should get the same results. Specially since both machines are stock. What model NUC are you using?

Please download the latest release from the repo and use that. Don't change kexts or change the order or change anything other than the serials and optionally the mac address.

If you still get different results from me when we're using the exact same EFI on the exact same machine then I really have no clue what's going on. Unless you added a Broadcom card in the m.2 slot it should not show up as Broadcom but as 3rd party dongle like in my screenshot.

ajai-akkarapaka commented 3 years ago

initially nothing in the efi has been changed. only added the serial of SMBIOS and updated it. I am using the latest repo. I haven't added any m.2 device a I am using it for my HDD. Anyways, now I loaded bios and disabled the in built bluetooth and loaded the OS. it is still showing me that bluetooth module is present instead of showing it as unavailable.

zearp commented 3 years ago

What is your NUC model?

ajai-akkarapaka commented 3 years ago

its NUC8i5BEH

ajai-akkarapaka commented 3 years ago

how to do a reset of NVRAM apart from the EFI boot, in the OS ? so that I can reset it and reboot it

zearp commented 3 years ago

NVRAM reset can be done from the boot menu. I find it really weird that you get a Broadcom showing up, and that if you disable bluetooth in the BIOS you still get a device showing up. It just points to something not being stock or being broken or something like that.

I have the exact same model as you have. Several of them. I have not run into anything like before and I can't reproduce it. I don't think I can help you and I don't have the time to step by step troubleshoot these kind of issues.

Once I start doing this more issues might be opened and people come to expect some kind of installation support because if I help you then someone else will expect me to help them too. I simply don't have the time for that.

The best I can offer is to update to the latest BIOS, reset all BIOS settings, reset NVRAM and try again from scratch.

ajai-akkarapaka commented 3 years ago

Hi, I have gotten back the bluetooth again,, after deleting the EFI and loading the same from USB stick. It is really strange.. I don't know what happened and why. Will keep you posted

Screen Shot 2021-10-29 at 6 50 35 PM

ajai-akkarapaka commented 3 years ago

I am going to update the BIOS to 089 now and will update changes if any. Thanks a lot for your support and keep up the great work. God bless you

zearp commented 3 years ago

Most likely is that the EFI folder got messed up somehow. Or you were loading an older EFI from usb and not internal disk. Luckily with our machines it's easy to start over. Just use the latest release and copy over your serials to the config. Then remove any existing EFI folders from both installer usb and any internal disks and copy the latest release to the disks.

I've had weird issues once when I forgot to remove the installer stick from the back of a NUC and was trying to make changes to the EFI on the internal disk. I didn't realise it was booting from the stick not the internal disk, so none of my changes were applied. It is not always clear what the NUC uses to boot from if you leave a bootable usb stick in there. Remove it or use F10 to select a boot disk to make sure.

Since you own the same machine you should be able to get it going just fine. Specially since its unmodified.

Good luck and thank you for the kind words and understanding.

ajai-akkarapaka commented 3 years ago

yep.. as you say.. my EFI folder is messed up, it is actually showing 100 mb free instead of 190.. so I guess the over written folders from the past is present there despite not showing.. anyways I will reformat the EFI drive and put the folder again Thank again

zearp commented 3 years ago

I was able to overnight sleep test and my bluetooth mouse worked fine the next morning. It may depend on the device. I really have no clue. It is impossible for me to fix things that I can't reproduce but I will update all kexts in a few days and make a new release. Hopefully it will fix some bluetooth issues.

ajai-akkarapaka commented 3 years ago

Thank you for writing me back on this issue. After my last conversation, I never had an issue with regards to bluetooth since then. I had multiple times restarted, overnight deep sleep of the machine as well. So, as we had discussed, it's got to be the EFI drive corruption. Anyways will post and update if any issues arise. HAVE A GREAT DAY.