Leaderboard

@everybody please report.! here is fix file. EFI-FIX.zip

@Slice hope release latest r5106 once again for 10.15.4 beta6 or newer CLOVER UEFI, FakeSMC(Rehabman), Patched AppleHDA, BT, SDCARD. etc, everything is work! i felt boot speed is very fast best of macOS series.

replacement boox64.efi and cloverx64.efi

thank you for testing committed! enjoy

Works like a charm on my SkyLake desktop. I updated from 10.15.3 to 10.15.4 beta6 with no issues. Thanks man! Great work as always

Click to word "Version" and you'll see build number.

try this config (2).plist.zip

ok give a minut i will check this

You're a legend - thank you! . I copied the Clover folder and dropped it in and it got to the install screen with your help. Unfortunately I can't install because the resolution is too low. Its all working but I just can't see the buttons as they are off the bottom of the screen. So I have made brilliant progress but I am still stuck

@3cn3rw4l http://cvad-mac.narod.ru/index/bootdiskutility_exe/0-5 https://www.aioboot.com/en/clover-boot-disk/

I don't even know who found this solution but the patch is assingning a memory region (base address and length) compatible with boot.efi and macOS.

Of course you already know: IT DOES WORK! What I did: 1). I follow 100% of you recommandations. Did a few boots to tests also writing directly to NVRAM thanks to the 'nvram' command. 2). I uninstalled also CloverDeamonNew and I ran additional boots. May I ask you how you generate the SSDT patch? I'm missing knowledge, but I love to understand each step.

It works. Well done.

I guess of yes. There was a tiny mistake solved by Pene.

You can chose or write the theme name to load for the next boot without editing the config.plist. The theme name is saved in nvram (which is persistent across reboots) and take precedence over the config.plist. This doesn't install a theme (which eventually you can do it by pressing "Manager") but only the theme to load, which must exist. If you ever run the theme Manager, the pull down will have a complete list of the known themes.

@n.d.k you can add device hotplug support and device removal support!

Because I am a OverClocker and have a golden 9900k that lives under a well made loop and can handle 5.2ghz with ease as a 24/7 overclock.

The version I gave is my latest unreleased version already. Nothing newer. Check the thread for new releases. When I do one I put up a big notice. Next one will around the same time as 10.15.4 is released and it will just be 057 touched up for release. new versions of clover and NDK EFIs will be released then too. I leave you with this thought and saying....... if it’s working well for you then why would you want the latest version because if it ain’t broke then don’t fix it! good night and enjoy your hack

@3cn3rw4l check this config.plist use it just as reference config.plist.zip

Today I decided to give a new look to VirtualSMC. For a long time, I consider it to unstable for my legacy configuration and relied on FakeSMC as I did for years. Just searching the web, I have discovered that VirtualSMC is updated regulary, FakeSMC is not updated as a release since October. Slice has taken over the developement of FakeSMC last year, but I suspect that FakeSMC is already becoming deprecated, like Chameleon became deprecated in favour of Clover. So, if Slice of Vector Sigma see this, I ask: Is this true? Would Slice become a developer of VirtualSMC instead of FakeSMC? If so, would you advise me to switch to VirtualSMC from FakeSMC on a legacy machine running Catalina?

Patched bios v. 3003 according to your guide above with UEFIPatch. Booting perfect without any kernel patches but still panic after wake from sleep. Any suggestions? Kernel_2020-03-19-184639_iMacPro.panic

Ah, don't tell to me, here in Italy we started long before. I made my first Netflix account as I never had time before. So now I'm coding and coding and for the remaining time I watch Star trek (old series since 1991)

Just rename the Label.png to No_label.png, but you don't have to do that anymore with latest commit, it's auto turn off for your low screen resolution.

Thanks @Sherlocks for the tip with the Kabylake CPU Intel i5 -7600 to use the Broadwell FakeCPUID ... FULL SUCCESS !!! I was able to continue with the 2nd phase of 10.15.4 Beta6 and successfully finish it. Why did Apple put it this way? why does the processor now have to run as Broadwell even though it is a Kabylake .. who knows details about that? So I have in the Clover 5106 (it will probably also work in earlier versions like 5103), I will test later, this only manually with textedit (like earlier from old school, do not need a Clover Configurator!): <key> KernelAndKextPatches </key> <dict> <key>FakeCPUID</key> <string>0x040674</string> und another Standard Options continue here <key>AppleIntelCPUPM</key> <false /> My Hacki is an MSI B250 Mortar Board with i5-7600 CPU Just tested with earlier Clover 5103 works just as well with the entry of the FakeCPUID. I still have a 2nd Hacki with Skylake i5-6600 and MSI H110 ECO motherboard, my question, does anyone know what you can use for a fakeCPUID so that this 2nd Hacki boots Beta 6 again and the Beta6 is then full can install? Thanks for tips. UPDATE: Also runs with the same FakeCPUID on my 2nd Hacki with Intel i5-6600K. Is probably a universal fakeCPUID -

Macos version is 10.15.3 kernel.zip

Brightness control is working for 10.13.3 AppleBacklight.kext.zip

This is for the default display at B@1. below is my practical experience. Sierra 10.12.6, Brightness control is working what did I do: fix XOSI add device PNLF rename GFX0 to _GFX both DSDT and SSDTs rename PEGP to GFX0 both DSDT and SSDTs add device (HDAU) under PEG0 return (one) under device (EDP1) Brightness control shortcut key Method (_Q10, 0, NotSerialized) // _Qxx: EC Query { If (LEqual (GPUM, 0x05)) { Notify (PS2K, 0x0205) Notify (PS2K, 0x0285) } If (LEqual (GPUM, 0x03)) { Notify (^^^_GFX.DD1F, 0x87) } ElseIf (CondRefOf (\_SB.PCI0.PEG0.GFX0.EDP1)) { Notify (^^^PEG0.GFX0.EDP1, 0x87) } } Method (_Q11, 0, NotSerialized) // _Qxx: EC Query { If (LEqual (GPUM, 0x05)) { Notify (PS2K, 0x0206) Notify (PS2K, 0x0286) } If (LEqual (GPUM, 0x03)) { Notify (^^^_GFX.DD1F, 0x86) } ElseIf (CondRefOf (\_SB.PCI0.PEG0.GFX0.EDP1)) { Notify (^^^PEG0.GFX0.EDP1, 0x86) } } _DSM of Device (GFX0) Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x18) { "@1,AAPL,boot-display", Buffer (One) { 0x01 }, "@1,backlight-control", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "@1,display-type", Buffer (0x04) { "LCD" }, "@1,built-in", Buffer (One) { 0x01 }, "@0,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@1,connector-type", Buffer (0x04) { 0x00, 0x04, 0x00, 0x00 }, "@2,connector-type", Buffer (0x04) { 0x00, 0x04, 0x00, 0x00 }, "@3,connector-type", Buffer (0x04) { 0x00, 0x04, 0x00, 0x00 }, "@4,connector-type", Buffer (0x04) { 0x00, 0x04, 0x00, 0x00 }, "@5,connector-type", Buffer (0x04) { 0x00, 0x04, 0x00, 0x00 }, "@1,pwm-info", Buffer (0x14) { /* 0000 */ 0x01, 0x14, 0x00, 0x64, 0xA8, 0x61, 0x00, 0x00, /* 0008 */ 0x1E, 0x02, 0x00, 0x00, 0x2C, 0x00, 0x00, 0x00, /* 0010 */ 0x00, 0x04, 0x00, 0x00 }, "hda-gfx", Buffer (0x0A) { "onboard-1" } }) } admin’s iMac_builtin1_brightnessOk_butNoHDMI.ioreg DSDT.aml SSDT-10-84DB.aml SSDT-XOSI.aml

Thanks, Matgen84 I tried also with yours but it didn't make any difference. I am still getting the same error. But I don't think this is the Power Management issue cause with both ssdt-plug.aml power management loading correctly in ioreg. Anyway, I just decided to ignore this error.