Drovosek

Hey. I have a Dell Vostro 3267 system unit. It has a Skylake processor Intel Core i5-6400 with integrated graphics Intel HD 530, 8 GB RAM, 256 GB SSD. The monitor is connected via HDMI. I faced a problem that if I enter Hackintosh in a sleep mode, and then I press something on the keyboard, the system unit wakes up (I hear as coolers begin to turn), but the monitor does not react in any way. I tried to disconnect and reconnect the HDMI cord, tried to inject EDID in config tried to change SMBIOS on MacMini8,1, but it did not change the situation. How to solve the problem? P.S. All in Mojave 10.14.6 CLOVER.7z

I conducted an experiment like this. I looked in /System/Library/Extensions / IOBluetoothFamily.kext/Contents/PlugIns/IOBluetoothUSBDFU.kext/Contents/Resources and there saw a certain number of files .dfu (volde would have been 22 files). Then I created folder and made in it 22 copies one of .dfu files (AthrBT_0x31010000_ss01.dfu), which was in the drivers of my Bluetooth module and renamed these copies in the same way as the files in /System/Library/Extensions/IOBluetoothFamily are called.kext/Contents/PlugIns/IOBluetoothUSBDFU.kext/Contents/Resources and then replaced the files from there with the files I "created". Then I rebooted, but the OS gave kernel panic. Added in 29 minutes 21 seconds: I also tried to follow this review (https://osxlatitude.com/forums/topic/2925-bluetooth-firmware-uploader/page/65/?tab=comments#comment-88003)I removed the kexts IOUSBFamily and IOUSBBluetoothFamily from /S/L/E and put instead kexts that were attached to the comment. I rebooted the system but only saw kernel panic. PS I did it in macOS Mojave 10.14.6

Hello. I have system unit Dell Vostro 3267 (i5-6400, Skylake). Information in signature. In this system block module installed Atheros AR9565 802.11 b/g/n Wireless Network Adapter, which, as I understand it, combines Wi-Fi - Atheros AR9565 and Bluetooth Qualcomm QCA9565. I managed to get working Wifi with kext from chunnann. https://www.insanelymac.com/forum/topic/312045-atheros-wireless-driver-os-x-101112-for-unsupported-cards/?page=17&tab=comments#comment-2509900 https://www.insanelymac.com/forum/topic/328426-qualcomm-atheros-ar9565-wireless-for-os-x-108-1014/ Bluetooth works only if you first boot into Windows and then reboot into macOS from it. At the same time, you need to install drivers for bluetooth in Windows from the official Dell website, because the original drivers that Windows downloaded and installed itself - did not allow the bluetooth module to work even in Windows. In bluetooth settings, the power button was inactive and there was an eternal search for devices (if macOS was loaded immediately after the PC started). Enable button disable I cured just by adding the folder /kexts/Other kext BrcmBluetoothInjector by writing inside it in the Info.the plist file corresponds to the VendorID and ProductID of my bluetooth (which are displayed in the system report). BrcmBluetoothInjector_Mod.kext.zip I am disappointed that Windows is able to automatically download the firmware to the bluetooth module during the download, and Hackintosh macOS has not yet done such a kext. In the search for solutions to the problem I came across here are the options for the text: IOath3kfrmw (OS-X-Atheros-3k-Firmware) https://bitbucket.org/RehabMan/os-x-atheros-3k-firmware/downloads/ https://github.com/RehabMan/OS-X-Atheros-3k-Firmware https://github.com/headkaze/OS-X-Atheros-3k-Firmware OS-X-BrcmPatchRAM https://github.com/the-darkvoid/BrcmPatchRAM https://github.com/RehabMan/OS-X-BrcmPatchRAM https://bitbucket.org/RehabMan/os-x-brcmpatchram/downloads/ https://bitbucket.org/anonymous_writer/os-x-brcmpatchram-catalina/downloads/ https://github.com/headkaze/OS-X-BrcmPatchRAM BTFirmwareUploader (as I understand it, this is an improved IOath3kfrmwr) https://osxlatitude.com/forums/topic/2925-bluetooth-firmware-uploader/ And here's a way - to use a virtual machine to the OS from it to download the firmware to the bluetooth module https://osxlatitude.com/forums/topic/10127-updated-nov-2017-fix-btfirmwareuploader-in-macos-high-sierra/ Unfortunately, not one of these options did not help me to ensure that bluetooth worked when "cold" start the PC in macOS. 1. I started to read more about kexts. In texte BrcmPatchRAM says that it is possible to add support for their bluetooth module in this kext. I downloaded the drivers for my bluetooth from the official site and extracted from .exe installer driver files themselves (This is easily done using 7-zip in Windows or using Keka in macOS). There were more files .dfu than others. As I found out .dfu files are compiled firmware files that the driver loads into the bluetooth module. In the instructions to BrcmPatchRAM States only .hex firmware files for Broadcom. I started looking for information on the Internet and found out that .hex files are the original "text" of the firmware as well .dfu is compiled .hex files. I immediately started looking for converters/decompilers/disassemblers from .in dfu .hex, but found only what's out .hex does .dfu file: https://github.com/pjsg/hex2dfu https://github.com/plietar/dfuse-tool https://github.com/kuro68k/ihex2dfu https://github.com/vpelletier/python-dfu As well as console utilities "dfu-tool" and "dfu-util" in Linux. I found out that dfu-util can be installed in macOS using Homebrew or use this option (it differs in functionality) https://github.com/the-darkvoid/dfu-util-osx 2. I also learned that .dfu files are used in macOS /System/Library/Extensions/IOBluetoothFamily.kext/Contents/PlugIns/IOBluetoothUSBDFU.kext/Contents/Resources I think we should try to replace all of them on that file that Windows loads the bluetooth module (I think if you try to do so, you need to make several copies of this file and rename it to the original ones .dfu files to be deleted). 3. As is the idea is just mine .dfu file rename to file .zhx and add it to the kext OS-X-BrcmPatchRAM (in BrcmFirmwareRepo.kext). But there is a problem - first, I don't know which one .dfu files are downloaded to my bluetooth, maybe even a few, because there are 3 files > 40 KB IN size and a lot of files ~ 2 KB in size. 4. In "dfu-tool" and "dfu-util" I saw commands that extract firmware from the device. Maybe it will be possible to boot into Linux and if bluetooth starts working there, then try to extract the firmware from bluetooth with these utilities, and then add this firmware to kexts somehow. 5. In the file BTFirmwareUploader.kex/Contents/MacOS/BTFirmwareUploader inside already have a list of firmwares, but they are in .hex format. Maybe there's a way to replace them with the contents .dfu file? I will continue to describe the ideas and results of the experiments. If you have any ideas or you can help to solve this problem, do not hesitate to write. Screenshots: Links to download drivers: https://www.dell.com/support/home/us/en/19/drivers/driversdetails?driverid=g66t8&oscode=wt64a&productcode=vostro-3267-desktop&lwp=rt Extracted bluetooth drivers: https://yadi.sk/d/cYGax0NEdoCF3w QCA9565 Bluetooth-Driver.7z https://www.acer.com/ac/en/US/content/support-product/5977?b=1&pn=NX.MVGER.002 https://global-download.acer.com/GDFiles/Driver/Bluetooth/Bluetooth_Atheros_10.0.1.0_W10x64_A.zip?acerid=635736531919697771&Step1=NOTEBOOK&Step2=ASPIRE&Step3=ASPIRE E5-573G&OS=ALL&LC=ru&BC=ACER&SC=EMEA_23 BrcmBluetoothInjector_Mod.kext.zip

Hello. I have system unit Dell Vostro 3267 (i5-6400, Skylake). Information in signature. In this system block module installed Atheros AR9565 802.11 b/g/n Wireless Network Adapter, which, as I understand it, combines Wi-Fi - Atheros AR9565 and Bluetooth Qualcomm QCA9565. I managed to get working Wifi with kext from chunnann. https://www.insanelymac.com/forum/topic/312045-atheros-wireless-driver-os-x-101112-for-unsupported-cards/?page=17&tab=comments#comment-2509900 https://www.insanelymac.com/forum/topic/328426-qualcomm-atheros-ar9565-wireless-for-os-x-108-1014/ Bluetooth works only if you first boot into Windows and then reboot into macOS from it. At the same time, you need to install drivers for bluetooth in Windows from the official Dell website, because the original drivers that Windows downloaded and installed itself - did not allow the bluetooth module to work even in Windows. In bluetooth settings, the power button was inactive and there was an eternal search for devices (if macOS was loaded immediately after the PC started). Enable button disable I cured just by adding the folder /kexts/Other kext BrcmBluetoothInjector by writing inside it in the Info.the plist file corresponds to the VendorID and ProductID of my bluetooth (which are displayed in the system report). BrcmBluetoothInjector_Mod.kext.zip I am disappointed that Windows is able to automatically download the firmware to the bluetooth module during the download, and Hackintosh macOS has not yet done such a kext. In the search for solutions to the problem I came across here are the options for the text: IOath3kfrmw (OS-X-Atheros-3k-Firmware) https://bitbucket.org/RehabMan/os-x-atheros-3k-firmware/downloads/ https://github.com/RehabMan/OS-X-Atheros-3k-Firmware https://github.com/headkaze/OS-X-Atheros-3k-Firmware OS-X-BrcmPatchRAM https://github.com/the-darkvoid/BrcmPatchRAM https://github.com/RehabMan/OS-X-BrcmPatchRAM https://bitbucket.org/RehabMan/os-x-brcmpatchram/downloads/ https://bitbucket.org/anonymous_writer/os-x-brcmpatchram-catalina/downloads/ https://github.com/headkaze/OS-X-BrcmPatchRAM BTFirmwareUploader (as I understand it, this is an improved IOath3kfrmwr) https://osxlatitude.com/forums/topic/2925-bluetooth-firmware-uploader/ And here's a way - to use a virtual machine to the OS from it to download the firmware to the bluetooth module https://osxlatitude.com/forums/topic/10127-updated-nov-2017-fix-btfirmwareuploader-in-macos-high-sierra/ Unfortunately, not one of these options did not help me to ensure that bluetooth worked when "cold" start the PC in macOS. 1. I started to read more about kexts. In texte BrcmPatchRAM says that it is possible to add support for their bluetooth module in this kext. I downloaded the drivers for my bluetooth from the official site and extracted from .exe installer driver files themselves (This is easily done using 7-zip in Windows or using Keka in macOS). There were more files .dfu than others. As I found out .dfu files are compiled firmware files that the driver loads into the bluetooth module. In the instructions to BrcmPatchRAM States only .hex firmware files for Broadcom. I started looking for information on the Internet and found out that .hex files are the original "text" of the firmware as well .dfu is compiled .hex files. I immediately started looking for converters/decompilers/disassemblers from .in dfu .hex, but found only what's out .hex does .dfu file: https://github.com/pjsg/hex2dfu https://github.com/plietar/dfuse-tool https://github.com/kuro68k/ihex2dfu https://github.com/vpelletier/python-dfu As well as console utilities "dfu-tool" and "dfu-util" in Linux. I found out that dfu-util can be installed in macOS using Homebrew or use this option (it differs in functionality) https://github.com/the-darkvoid/dfu-util-osx 2. I also learned that .dfu files are used in macOS /System/Library/Extensions/IOBluetoothFamily.kext/Contents/PlugIns/IOBluetoothUSBDFU.kext/Contents/Resources I think we should try to replace all of them on that file that Windows loads the bluetooth module (I think if you try to do so, you need to make several copies of this file and rename it to the original ones .dfu files to be deleted). 3. As is the idea is just mine .dfu file rename to file .zhx and add it to the kext OS-X-BrcmPatchRAM (in BrcmFirmwareRepo.kext). But there is a problem - first, I don't know which one .dfu files are downloaded to my bluetooth, maybe even a few, because there are 3 files > 40 KB IN size and a lot of files ~ 2 KB in size. 4. In "dfu-tool" and "dfu-util" I saw commands that extract firmware from the device. Maybe it will be possible to boot into Linux and if bluetooth starts working there, then try to extract the firmware from bluetooth with these utilities, and then add this firmware to kexts somehow. 5. In the file BTFirmwareUploader.kex/Contents/MacOS/BTFirmwareUploader inside already have a list of firmwares, but they are in .hex format. Maybe there's a way to replace them with the contents .dfu file? I will continue to describe the ideas and results of the experiments. If you have any ideas or you can help to solve this problem, do not hesitate to write. Screenshots: Links to download drivers: https://www.dell.com/support/home/us/en/19/drivers/driversdetails?driverid=g66t8&oscode=wt64a&productcode=vostro-3267-desktop&lwp=rt Extracted bluetooth drivers: https://yadi.sk/d/cYGax0NEdoCF3w QCA9565 Bluetooth-Driver.7z https://www.acer.com/ac/en/US/content/support-product/5977?b=1&pn=NX.MVGER.002 https://global-download.acer.com/GDFiles/Driver/Bluetooth/Bluetooth_Atheros_10.0.1.0_W10x64_A.zip?acerid=635736531919697771&Step1=NOTEBOOK&Step2=ASPIRE&Step3=ASPIRE E5-573G&OS=ALL&LC=ru&BC=ACER&SC=EMEA_23 BrcmBluetoothInjector_Mod.kext.zip

AppleImageLoader Secure AppleEfiFat binary driver with implementation of AppleLoadImage protocol with EfiBinary signature verification. It provides secure loading of Apple EFI binary files into memory by pre-authenticating its signature. https://github.com/acidanthera/AppleSupportPkg https://www.elitemacx86.com/resources/applesupportpkg.97/

Wrong link to MaciASL. Please, fix it.

Thanks for the advice. I managed to cope with the problem. I read the relevant topic on the applelife forum, they recommend using the special boot argument with ACPIBatteryManager.kext, either use VirtualSMC with a driver and additional cakes, or use cakes from HWSensors3. Links: https://applelife.ru/threads/applesmartbattery-batareja-noutbukov.31744/ ----- https://bitbucket.org/RehabMan/os-x-acpi-battery-driver/downloads/ https://github.com/RehabMan/OS-X-ACPI-Battery-Driver/commit/28a0fbdcd5ed7598315948af4e1228683ff2fff2#diff-04c6e90faac2675aa89e2176d2eec7d8 https://sourceforge.net/projects/hwsensors3.hwsensors.p/ https://github.com/acidanthera/VirtualSMC/releases What did I do: In ACPI / patched put your patched DSDT Removed ACPIBatteryManager.kext I downloaded HWSensors3 and dropped the other cakes into the Other folder - FakeSMC.kext, VoodooBatterySMC.kext and just in case ACPIMonitor.kext (but judging by what is written in the Readme it is not needed for the battery, but this is not certain). The bug with the freezing of the charge indicator is 100% corrected. But there is a mini-bug: Sometimes the charge percentage indicator freezes at random values, for example, 92% and then the N-th number of minutes does not change. If you click on the charge icon in the top panel, then after a couple of seconds, the charge indicator will be updated to the current one, for example, 98%. Perhaps after a large number of minutes, the indicator will update itself, but the figure with the charge percentage "will make the jump." Slice told me that most likely the SMC or something else is involved in updating the charge in macOS and to fix it, it is necessary that the HWMonitorSMC2 application be launched and it updates the charge itself. Then I deleted FakeSMC.kext, VoodooBatterySMC.kext and ACPIMonitor.kext and used the cakes and driver from VirtualSMC. He was all the same as above with the HWSensors3 cakes. So, we can assume that the problem is solved.

Hey, thank you)). With your DSDT file, the battery power can be drained after reaching 100% and the power is turned off. I haven't checked other situations yet (battery work in Windows or battery work in mac OS after reboot), but can you describe what kind of magic you did? PS I tried to open my DSDT file and yours and compare on this site (http://text.num2word.ru/). I looked a bit but realized that you renamed my 16-bit registers and remade SMD and SMD methods. Could you describe in more detail what you need to do to repeat your result? Also I did not disable any patches in config.plist. I don't know what patches there affect the battery, could you name them? https://vk.com/doc183234383_509797234 UPDATE: I did some "tests" and laptop reboots (sometimes with CMOS reset) and noticed that with your DSDT the charge indicator still hangs sometimes. I don't know what this has to do with. Also it is sometimes corrected when I connect an Android smartphone as a USB modem (this was 1 time).

For my laptop Hp Pavilion 15-au028ur worked patch for HP 3165sf I also experimented with manual patching and assembled my own version: #Maintained by: RehabMan for: Laptop Patches #Battery_HP-DV6-1380ek.txt # created by RehabMan 2019-xx-xx # based on Battery_HP-DV6-1380ek.txt # additional patches for dv6-1380ek provided by chihab222, credit gsly # works for: # HP Pavilion 15-au028ur, per Drovosek into method label B1B2 remove_entry; into definitionblock code_regex . insert begin Method (B1B2, 2, NotSerialized) { Return (Or (Arg0, ShiftLeft (Arg1, 8))) }\n end; # 16-bit EC0 registers # BADC, 16, # BFCC, 16, # MCUR, 16, # MBRM, 16, # MBCV, 16, into device label EC0 code_regex BADC,\s+16, replace_matched begin ADC0,8,ADC1,8, end; into device label EC0 code_regex BFCC,\s+16, replace_matched begin FCC0,8,FCC1,8, end; into device label EC0 code_regex MCUR,\s+16, replace_matched begin CUR0,8,CUR1,8, end; into device label EC0 code_regex MBRM,\s+16, replace_matched begin BRM0,8,BRM1,8, end; into device label EC0 code_regex MBCV,\s+16, replace_matched begin BCV0,8,BCV1,8, end; # 16-bit method access into method label CLRI code_regex (\^.*)MBRM replaceall_matched begin B1B2\(%1BRM0,%1BRM1\) end; into method label UPBS code_regex (\^.*)MBRM replaceall_matched begin B1B2\(%1BRM0,%1BRM1\) end; into method label UPBI code_regex (\^.*)BFCC replaceall_matched begin B1B2\(%1FCC0,%1FCC1\) end; into method label UPBS code_regex (\^.*)MCUR replaceall_matched begin B1B2\(%1CUR0,%1CUR1\) end; into method label UPBS code_regex (\^.*)MBCV replaceall_matched begin B1B2\(%1BCV0,%1BCV1\) end; The only problem - when it reaches 100% charge, it no longer falls until you reset the CMOS (15-30 seconds hold down the power button on the laptop). In the rehabman guide there is a patch for ASUS in this case, there is a patch method FBST. There is no such method in my DSDT. Can someone help? Here's a patched and clean DSDT: https://vk.com/doc183234383_509697931