Clover General discussion

[maclinuxG4]

on mac os sierra, with the last release  r5126, I get a KP then halt I restart then ok. (KP with a kext......)

 

there is a something to understand, during phase loaded kext may be unsuccessful 

 

 

 

Edited October 31, 2020 by maclinuxG4

[LockDown]

Hi

Does ForceHPET still have use on newer clover or it has been marked as deprecated?

[Slice]

25 minutes ago, ellaosx said:

Hi

Does ForceHPET still have use on newer clover or it has been marked as deprecated?

Not deprecated. But usage depends on hardware if it allow this or not.

[SavageAUS]

10 hours ago, D-an-W said:

Apologies for the slightly off topic but your a clever bunch in here!

 

Does anyone know if it's ok / safe to remove this Update partition and if so what's the best way to do it?

 

  Hide contents

 

+1 bugs me to see it in Catalina. 

[Cyberdevs]

12 hours ago, D-an-W said:

Apologies for the slightly off topic but your a clever bunch in here!

 

Does anyone know if it's ok / safe to remove this Update partition and if so what's the best way to do it?

Spoiler

Just select the Update volume and remove it by clicking the - button

[D-an-W]

4 minutes ago, Cyberdevs said:

  Reveal hidden contents

Just select the Update volume and remove it by clicking the - button

 

Thanks, wasn't sure if thats the best way and if it would impact anything else?

[Slice]

@all

How do you think will it be useful to implement injecting Device->Properties depending on macOS version?

Up for now there is no MatchOS setting.

[Cyberdevs]

21 minutes ago, D-an-W said:

Thanks, wasn't sure if thats the best way and if it would impact anything else?

AFIAK it doesn't affect anything. I removed it on Big Sur and I didn't have an issue so far

[Denisuu]

21 hours ago, kushwavez said:

You should use only BrcmBluetoothInjector, BrcmFirmwareData and BrcmPatchRAM3 if they're in Clover/kexts. BrcmFirmwareRepo is only for L/E. 

 

Also I can't really see the texts correctly but for me it saying "Still waiting for root device" That means the system can't see your internal drives. 

 

Here I made you a new EFI. 

Deleted unused kexts:

- CpuTscSync.kext (I think it's do nothing for you)

- HWPEnabler.kext (not needed)

- BrcmFirmwareRepo.kext (wrong, replaced with BrcmFirmwareData.kext)

- BrcmNonPatchRAM2.kext (wrong, use BrcmPatchRAM3 only)

 

Added new ones, also added CtlnaAHCIPort.kext for your internal drives, not sure if it's needed or not, I did that because you had "Still waiting for root device" error which is most likely because of an unsupported chipset and your drives aren't recognised.

 

Clover is now v5126 so CLOVERX64.efi is replaced with the new one

 

your config.plist have lot's of unused variables or unnecessary changes, so I modified mine instead, but the old one is also included (config_old.plist)

- In your "new" config.plist in ACPI/DSDT/Patches you have two EC renames (EC0 to EC and ECDV to EC) you should figure out which one do you need, and delete the unnecessary ones. 

- Your SMBIOS is wrong. According to your signature it's a 7700HQ, exactly the same as MacBookPro14,3 so I changed that.

- Boot args deleted: dart=0 (not needed), nv_disable=1 (you already disabled it by SSDT), -shikioff (idk why), gfxrst=1

I did not remove -disablegfxfirmware but I think it's not necessary, try to remove and boot. 

 

Replaced your drivers with the new one. You also had SMCHelper (for FakeSMC) and VirtualSMC.efi, you should use jsut one. In your case it's VirtualSMC.efi. 

 

I had to delete FlashProgrammingTool.efi, FWUpdLcl.efi, MEInfo.efi, MEManuf.efi, ACPI/origin, and themes/minimal because of the zip size is too big to upload because of them, if you want to use them you have to readd them.

 

Take a look

 

EDIT: if you have DSDT errors pls change ACPI/DSDT/Name from "BIOS.aml" to "DSDT.aml"

I forgot that.

 

N580VD Clover r5126.zip

 

Wow, thanks for the effort man!!!

 

Yea I knew it would be a big mess, it's was my first Hackintosh machine so I didn't know what I was doing at all. After re-adding CpuTscSync.kext and changing BIOS.aml to DSDT.aml my system booted.

 

I'm not sure why but from BIOS update 317 I needed VoodooTSCSync.kext or CpuTscSync.kext. The system still boots after removing 'CtlnaAHCIPort.kext' and -disablegfxfirmware

It looks like there is no ECDV in my DSDT so I removed the 'ECDV to EC' patch from 'ACPI/DSDT/Patches'

 

Sound, full shutdown and sleep aren't working anymore though. I thought it was because the device properties weren't added but it doesn't change anything.

I went through all tabs and tried to change all parameters like they were in my old config.plist, that doesn't help either.

 

I would think if I just removed these and injected layout 21 it would work, but it doesn't.

 

 

[Guest]

2 hours ago, Slice said:

@all

How do you think will it be useful to implement injecting Device->Properties depending on macOS version?

Up for now there is no MatchOS setting.

Yes for sure

but I think MatchOS could be more solid in its working.

have you read on GitHub issue I have opened?

and it is not a platform problem

it seems more deeper to debug

Edited October 31, 2020 by Guest

[kushwavez]

14 minutes ago, Denisuu said:

 

Wow, thanks for the effort man!!!

 

Yea I knew it would be a big mess, it's was my first Hackintosh machine so I didn't know what I was doing at all. After re-adding CpuTscSync.kext and changing BIOS.aml to DSDT.aml my system booted.

 

I'm not sure why but from BIOS update 317 I needed VoodooTSCSync.kext or CpuTscSync.kext. The system still boots after removing 'CtlnaAHCIPort.kext' and -disablegfxfirmware

It looks like there is no ECDV in my DSDT so I removed the 'ECDV to EC' patch from 'ACPI/DSDT/Patches'

 

Sound, full shutdown and sleep aren't working anymore though. I thought it was because the device properties weren't added but it doesn't change anything.

I went through all tabs and tried to change all parameters like they were in my old config.plist, that doesn't help either.

 

I would think if I just removed these and injected layout 21 it would work, but it doesn't.

 

For sleep try removing darkwake=0 bootflag and disable Power Nap. 

 

For audio I need to know your audio chip. If it's ALC298 you should try these audio layout-ids: 3, 11, 13, 21, 22, 28, 29, 30, 32, 47, 66, 72, 99. Try with 3 first. I suggest you to remove from Properties/Devices, and use just with. alcid=xx bootflag. Then if you got the working one use config.plist/Devices/Audio/Inject=xx

Also make sure you are using the native AppleHDA, not a patched one. And Only AppleALC.kext.

[Denisuu]

20 minutes ago, kushwavez said:

For sleep try removing darkwake=0 bootflag and disable Power Nap. 

 

For audio I need to know your audio chip. If it's ALC298 you should try these audio layout-ids: 3, 11, 13, 21, 22, 28, 29, 30, 32, 47, 66, 72, 99. Try with 3 first. I suggest you to remove from Properties/Devices, and use just with. alcid=xx bootflag. Then if you got the working one use config.plist/Devices/Audio/Inject=xx

Also make sure you are using the native AppleHDA, not a patched one. And Only AppleALC.kext.

 

My chip is Conexant Audio CX8150 so it should be 21 or 22 according to the AppleALC Wiki: https://github.com/acidanthera/AppleALC/wiki/Supported-codecs

I'll try to fix sleep first.

Edited October 31, 2020 by Denisuu

[kushwavez]

@Denisuu Oh I see. It's Conexant CX8150. 

Well then You need to add 2 KextToPatch too:

 

Add Properties:

 

and at Devices/Properties add layout-id just like you did. (OR) just start with alcid=21 (or Devices/Auido/Inject=21) to see if it's working or not.

 

Edited October 31, 2020 by kushwavez

[Matgen84]

2 hours ago, Slice said:

@all

How do you think will it be useful to implement injecting Device->Properties depending on macOS version?

Up for now there is no MatchOS setting.

@Slice I don't understand the interest of matchOS settings in Devices/Proprieties. Personally, I have only one macOS version by Hack  I think: this new feature could remain optional, and used only by those who need it.

[Denisuu]

1 hour ago, kushwavez said:

@Denisuu Oh I see. It's Conexant CX8150. 

Well then You need to add 2 KextToPatch too:

 

Add Properties:

 

and at Devices/Properties add layout-id just like you did. (OR) just start with alcid=21 (or Devices/Auido/Inject=21) to see if it's working or not.

 

 

I already re-added those, it doesn't work though. Now the strange thing is if I go back to my old EFI sound isn't working either... I don't understand how it can stop working al of a sudden, it always worked.

The alcid=21 and/or Devices/Audio/Inject=21 also don't do anything...  The kext is being loaded though. I tried installing it to L/E too but nothing seems to work. 

 

 

Also removing darkwake and disabling powernap doesn't solve sleep. This is the reason I moved back from OpenCore to Clover because it was impossible to get sleep to work.

It works perfectly on 5122, so maybe it has something to do with the quirks or OpenRuntime.efi?

Edited October 31, 2020 by Denisuu

[MacKonsti]

3 hours ago, Slice said:

@all

How do you think will it be useful to implement injecting Device->Properties depending on macOS version?

Up for now there is no MatchOS setting.

Hi @Slice thanks for your contributions even if I am still holding on Catalina and don't dare to test BugSur
I would suggest the same type of tag as found for kext patches e.g. the SSD one. 10.16 for all versions (or 10.16.x) and 10.16.1 for that particular minor version i.e. release dot major dot minor:

 

<key>MatchOS</key>
<string>10.15.x</string>

This is clearer to understand, visually, in Config too.

And depends if you can do mixing as well, like

<string>10.12,10.13</string>

 

Thanks. Do you consider a universal value for all OS? I saw in sample Config:

<key>MatchOS</key>

<string>All</string>

 

But not sure if it's valid for all expected value and places, nor which Clover forward this is implemented.

Cheers

[chris1111]

Hello to clover DEV @Slice @Jief_Machak @vector sigma I would like to give you some advice that I am testing for the use of the package on macOS Big Sur 11
It is quite easy to make it functional by changing the directory or creating the Symlink EFIROOTDIR which allows you to mount the EFI partition
For macOS big 11 it cannot be created on the Root you must adapt the EFIFOLDER, PRE and POST sript which is in Scripts.templates so that it is done in the /Private/tmp directory which is usable; the clover LOG must also be created in the accessible directory. You can also use another accessible directory but /Private/tmp works well I use it for many programs. This will also work on other macOS without any problem.

 

Thank your for your work and effort 

[Slice]

3 hours ago, Denisuu said:

 

My chip is Conexant Audio CX8150 so it should be 21 or 22 according to the AppleALC Wiki: https://github.com/acidanthera/AppleALC/wiki/Supported-codecs

I'll try to fix sleep first.

Sleep will not work until you repair sound.

Moreover sleep will work just after all devices will be maintained.

I may propose you to use VoodooHDA instead of AppleALC.

[iCanaro]

6 hours ago, Slice said:

@all

How do you think will it be useful to implement injecting Device->Properties depending on macOS version?

Up for now there is no MatchOS setting.

 

it may be useful to be able to define device properties for specific macOS in the matchos style of kerneltopatchs
but it may also be useful to be able to define the order in which the kexts are loaded; for example I know that those for the I2C trackpad is very important... so having a kind of SortedOrder for kexts along the lines of that for SSDTs, could help many.

But all of this depends on you developers, and the issues you face to achieve the goal.

 

PS: Personally I have the device properties very populated and until now I have not encountered any particular problems from sierra up to BigSur, but this does not detract from the fact that being able to determine on which macOS to activate them, can only be of help and useful  

Edited October 31, 2020 by iCanaro

[stevezheng]

Hi guys, thank for all the efforts on this bootloader.

 

I am still not able to use r5123+ to boot Mojave and Big Sur (tested on the latest commit https://github.com/CloverHackyColor/CloverBootloader/commit/9e7b4311cb2c552271dbc7bc6e67b50493518a72). With the same quirks settings in OpenCore, I can boot without problems, but in Clover no. A noticeable setting in OpenCore is that the `Default` `SecureBootModel` would always cause early boot problems like me. I set `SecureBootModel` to `Disabled` in OC and then I have no issues.

 

@Slice @Jief_MachakWould you guys mind have a look at SecureBootModel related codes in the OC integration part? If Clover uses SecureBootModel settings, please use `Disabled` as default. OpenCore default is `Default`, which is equivalent to Medium Security and causes some issues. If Clover doesn't use SecureBootModel related code at all, then I have no idea why I can't boot with r5126.

 

Here's my config, screenshot of boot failure, and Preboot log. Any help is appreciated.

 

config.plist

preboot.log

[LockDown]

Other=Common (chameleon)

IMO, Common/AllmacOS is a better alternative name

Edited November 1, 2020 by ellaosx

[Matgen84]

20 minutes ago, stevezheng said:

Hi guys, thank for all the efforts on this bootloader.

 

I am still not able to use r5123+ to boot Mojave and Big Sur (tested on the latest commit https://github.com/CloverHackyColor/CloverBootloader/commit/9e7b4311cb2c552271dbc7bc6e67b50493518a72). With the same quirks settings in OpenCore, I can boot without problems, but in Clover no. A noticeable setting in OpenCore is that the `Default` `SecureBootModel` would always cause early boot problems like me. I set `SecureBootModel` to `Disabled` in OC and then I have no issues.

 

@Slice @Jief_MachakWould you guys mind have a look at SecureBootModel related codes in the OC integration part? If Clover uses SecureBootModel settings, please use `Disabled` as default. OpenCore default is `Default`, which is equivalent to Medium Security and causes some issues. If Clover doesn't use SecureBootModel related code at all, then I have no idea why I can't boot with r5126.

 

Here's my config, screenshot of boot failure, and Preboot log. Any help is appreciated.

 

 

config.plist

preboot.log

Hi @stevezheng Clover r5126 can boot BS on my Z390 (with the Opencore same settings). What beta are you using ? I use 11.0 folder beside other folder with kexts to update to BS 11.0.1.

In you config.plist, Preboot is hidden. Clover for BS need Preboot, so remove it from Hidden section. You have to boot from Preboot not main partition. The new clover don't need Securebootmodel to update Big Sur. 

Please complete you signature with config details. 

[stevezheng]

21 minutes ago, Matgen84 said:

Hi @stevezheng Clover r5126 can boot BS on my Z390 (with the Opencore same settings). What beta are you using ? I use 11.0 folder beside other folder with kexts to update to BS 11.0.1.

In you config.plist, Preboot is hidden. Clover for BS need Preboot, so remove it from Hidden section. You have to boot from Preboot not main partition. The new clover don't need Securebootmodel to update Big Sur. 

Please complete you signature with config details. 

Thanks for the suggestion. I will remove Preboot from hidden items. However, I can not use Clover to boot Mojave and Catalina also. I got the same error as my screenshot.

[Matgen84]

12 minutes ago, stevezheng said:

Thanks for the suggestion. I will remove Preboot from hidden items. However, I can not use Clover to boot Mojave and Catalina also. I got the same error as my screenshot.

Try to upload debug.log and EFI folder, maybe some user can help you 

Please complete your signature with config details (desktop, laptop, motherboard, processor, graphics....) 

[stevezheng]

1 hour ago, Matgen84 said:

Try to upload debug.log and EFI folder, maybe some user can help you 

Please complete your signature with config details (desktop, laptop, motherboard, processor, graphics....) 

Thanks for your help. Here are the debug.log and CLOVER folder. Any help is appreciated.

 

CLOVER_stevezheng.zip

debug_stevezheng.log