Jump to content

Clover General discussion


ErmaC
29,866 posts in this topic

Recommended Posts

8 hours ago, Hervé said:
Clover r5133 installs, boots and run macOS 12 Monterey without even the hint of a hiccup. Not tried previous versions.


What about latest clover? 5136?

Might have to create a seperate partition and try it myself.

 


Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

Can confirm, just started the installation with v5136 on my Lenovo T440.

HD 4400 (Haswell) -> Supported, Had to change the SMBIOS from MacBookPro11,1 to 12,1.

Compatibility list excludes all MBP and Air with Haswell CPU/GPU but include Macmini7,1 (Late 2014), and that has HD 5000.

I smell marketing here...:P 

EDIT: Oh, my bad. MacBookPro11,4 is still supported and it has Haswell GPU. 

 

The installer also booted up on my X1C6 too, so I suppose there will be no complication whatsoever. 

As far as I can see the whole OS is just an under-the-hood update.

AirPlay and Universal Control are very welcome tho, I'll love them

Edited by kushwavez
Link to comment
Share on other sites

Hi @Slice@Jief_Machak

CLEAN INSTALL Monterey: Using Clover r5136 + latest Kexts (8th June) + USB pen drive, my Z390 config stuck at Aorus Gigabyte splash screen after first stage.

 

In debug.log file: OC: Opening file usr\standalone\OS.dmg.root_hash with 1 mode gave - Not Found

 

 

2021-06-08_07-58_BOOTX64.EFI.log
 

 

EDIT: No problem with Opencore 0.70, both Install macOS 12 Beta and macOS Installer are detected.

 

Spoiler

Screenshot.thumb.jpg.096ec7ff2b14989dc25f02fdad08bd3a.jpg

 

Edited by Matgen84
New screenshot from Opencore
Link to comment
Share on other sites

19 minutes ago, Matgen84 said:

Hi @Slice@Jief_Machak

CLEAN INSTALL Monterey: Using Clover r5136 + latest Kexts (8th June), my Z390 config stuck at Aorus Gigabyte splash screen after first stage.

 

In debug.log file: OC: Opening file usr\standalone\OS.dmg.root_hash with 1 mode gave - Not Found

 

 

2021-06-08_07-58_BOOTX64.EFI.log 69.47 kB · 0 downloads

I offer you to change SMC` is another character?

  • Like 1
Link to comment
Share on other sites

7 minutes ago, naiclub said:

I offer you to change SMC` is another character?

 

Sorry for my bad English: I don't understand what you mean. I use latest VirtualSMC Beta (build today). 

Link to comment
Share on other sites

13 minutes ago, Matgen84 said:

 

Sorry for my bad English: I don't understand what you mean. I use latest VirtualSMC Beta (build today). 

in the boot log file Yours is suing like that. I would like you to try switching to a different one and see if it resolves the issue.

  • Thanks 1
Link to comment
Share on other sites

19 minutes ago, SavageAUS said:

When will clover get an update for a “12” folder?


Sent from my iPhone using Tapatalk

Will be. It was night for me when Monterey was introduced and this moment I am at work. Wait please.

  • Like 2
  • Thanks 3
Link to comment
Share on other sites

@SavageAUS It is done automatically, no need for update. 

It's working.

[...]
24:582  0:000  AddKextsInArray from 12
24:582  0:000  ->Extra kext: 12\AppleALC.kext (v.1.5.7)
24:582  0:000  ->Extra kext: 12\IntelMausi.kext (v.1.0.3)
24:582  0:000  ->Extra kext: 12\Lilu.kext (v.1.5.0)
24:582  0:000  ->Extra kext: 12\Sinetek-rtsx.kext (v.9)
24:582  0:000  ->Extra kext: 12\SMCBatteryManager.kext (v.1.1.9)
24:582  0:000  ->Extra kext: 12\SMCProcessor.kext (v.1.1.9)
24:582  0:000  ->Extra kext: 12\USBPorts.kext (v.1.0)
24:582  0:000  ->Extra kext: 12\VirtualSMC.kext (v.1.1.9)
24:582  0:000  ->Extra kext: 12\VoodooPS2Controller.kext (v.2.2.2)
24:582  0:000      |-- PlugIn kext: 12\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Trackpad.kext (v.2.2.2)
24:582  0:000      |-- PlugIn kext: 12\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Keyboard.kext (v.2.2.2)
24:582  0:000  ->Extra kext: 12\VoodooRMI.kext (v.1.3.3)
24:582  0:000      |-- PlugIn kext: 12\VoodooRMI.kext\Contents\PlugIns\VoodooInput.kext (v.1.1.3)
24:582  0:000      |-- PlugIn kext: 12\VoodooRMI.kext\Contents\PlugIns\RMISMBus.kext (v.1.0)
24:582  0:000  ->Extra kext: 12\VoodooSMBus.kext (v.3.0)
24:582  0:000  ->Extra kext: 12\WhateverGreen.kext (v.1.4.5)
24:582  0:000  AddKextsInArray from 12_normal
24:582  0:000  AddKextsInArray from 12.0
24:582  0:000  AddKextsInArray from 12.0_normal
24:582  0:000  AddKextsInArray from 12.0.0
24:582  0:000  AddKextsInArray from 12.0.0_normal
[...]

 

  • Like 4
Link to comment
Share on other sites

[mention=1083558]SavageAUS[/mention] It is done automatically, no need for update. 
It's working.
[...]24:582  0:000  AddKextsInArray from 1224:582  0:000  ->Extra kext: 12\AppleALC.kext (v.1.5.7)24:582  0:000  ->Extra kext: 12\IntelMausi.kext (v.1.0.3)24:582  0:000  ->Extra kext: 12\Lilu.kext (v.1.5.0)24:582  0:000  ->Extra kext: 12\Sinetek-rtsx.kext (v.9)24:582  0:000  ->Extra kext: 12\SMCBatteryManager.kext (v.1.1.9)24:582  0:000  ->Extra kext: 12\SMCProcessor.kext (v.1.1.9)24:582  0:000  ->Extra kext: 12\USBPorts.kext (v.1.0)24:582  0:000  ->Extra kext: 12\VirtualSMC.kext (v.1.1.9)24:582  0:000  ->Extra kext: 12\VoodooPS2Controller.kext (v.2.2.2)24:582  0:000      |-- PlugIn kext: 12\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Trackpad.kext (v.2.2.2)24:582  0:000      |-- PlugIn kext: 12\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Keyboard.kext (v.2.2.2)24:582  0:000  ->Extra kext: 12\VoodooRMI.kext (v.1.3.3)24:582  0:000      |-- PlugIn kext: 12\VoodooRMI.kext\Contents\PlugIns\VoodooInput.kext (v.1.1.3)24:582  0:000      |-- PlugIn kext: 12\VoodooRMI.kext\Contents\PlugIns\RMISMBus.kext (v.1.0)24:582  0:000  ->Extra kext: 12\VoodooSMBus.kext (v.3.0)24:582  0:000  ->Extra kext: 12\WhateverGreen.kext (v.1.4.5)24:582  0:000  AddKextsInArray from 12_normal24:582  0:000  AddKextsInArray from 12.024:582  0:000  AddKextsInArray from 12.0_normal24:582  0:000  AddKextsInArray from 12.0.024:582  0:000  AddKextsInArray from 12.0.0_normal[...]

 


So you created a “12” folder and it works?


Sent from my iPhone using Tapatalk
Link to comment
Share on other sites

I installed Monterey just as update to Big Sur through System Preferences. Clover 5136 and no changes in config. But I have to exclude FileVault2 drivers: AppleUITheme, FirmwareVolume, UsbKbDxe. Don't know who is wrong.

Link to comment
Share on other sites

18 hours ago, Matgen84 said:

Hi @Slice@Jief_Machak

CLEAN INSTALL Monterey: Using Clover r5136 + latest Kexts (8th June) + USB pen drive, my Z390 config stuck at Aorus Gigabyte splash screen after first stage.

 

In debug.log file: OC: Opening file usr\standalone\OS.dmg.root_hash with 1 mode gave - Not Found

 

2021-06-08_07-58_BOOTX64.EFI.log 69.47 kB · 5 downloads
 

 

EDIT: No problem with Opencore 0.70, both Install macOS 12 Beta and macOS Installer are detected.

 

  Reveal hidden contents

Screenshot.thumb.jpg.096ec7ff2b14989dc25f02fdad08bd3a.jpg

 

 

Hi @Slice @Jief_Machak @MifJpn

I upload again the comment posted yesterday. If you can help me for this clean Install of Monterey on Z390 Aorus Master. Please.

As usual, all kexts are in Other folder.

Link to comment
Share on other sites

1 hour ago, Matgen84 said:

 

Hi @Slice @Jief_Machak @MifJpn

I upload again the comment posted yesterday. If you can help me for this clean Install of Monterey on Z390 Aorus Master. Please.

As usual, all kexts are in Other folder.

I see your log and found

after NVRAM boot-args=-v dart=0 darkwake=0 shikigva=80 brcmfx-country=#a brcmfx-driver=2

But using lilu you have to set lilubetaall la-la...

Link to comment
Share on other sites

18 minutes ago, Slice said:

I see your log and found

after NVRAM boot-args=-v dart=0 darkwake=0 shikigva=80 brcmfx-country=#a brcmfx-driver=2

But using lilu you have to set lilubetaall la-la...

 

Thanks. I also try with --lilubetaall. My Z390 stucks on Gigabyte Aorus Logo splash screen :cry:  I use a separate HDD to test Monterey. Now, I can't boot my Big Sur HDD or an USB pen drive: stucks on Gigabyte Aorus Logo splash screen

Any ideas ? Please.

 

Spoiler

2.jpg.1565478dc3078ff23b9ca9424db4a94f.jpg

 

Edited by Matgen84
Link to comment
Share on other sites

20 minutes ago, Matgen84 said:

 

Thanks. I also try with --lilubetaall. My Z390 stucks on Gigabyte Aorus Logo splash screen :cry:  I use a separate HDD to test Monterey. Now, I can't boot my Big Sur HDD or an USB pen drive: stucks on Gigabyte Aorus Logo splash screen

Any ideas ? Please.

 

  Reveal hidden contents

 

Logo splash screen means your Clover is not started at all? Check your BIOS, your BIOS settings for boot, Boot variables. Check your Clover installation if it is in the right place.

  • Thanks 1
Link to comment
Share on other sites

29 minutes ago, Slice said:

Logo splash screen means your Clover is not started at all? Check your BIOS, your BIOS settings for boot, Boot variables. Check your Clover installation if it is in the right place.

 

Thanks. I use @AudioGod settings for my Z390 Aorus, since two years without any major problem. However, I have randomly instability (NVRAM, I suppose). What do you mean by "Boot variables. Check your Clover installation if it is in the right place."

Sory I don't understand because of my bad English.

 

EDIT 1: I just try to boot with OC's USB pen drive, no splash screen issue (without any changes in BIOS settings).

EDIT 2: Remember, it's a CLEAN INSTALL, not update

Edited by Matgen84
clean install of Monterey
Link to comment
Share on other sites

Attempt successful!

Hack Z170 in signature, with Clover 5136 I tried to update high sierra installed in HFS in monterey, the biggest difficulty was that the kexts compiled just before the attempt, one of them immediately sent the system into kernel panic on the first reboot, but using the old catalina kexts, adding boot arg -lilubetall -wegbeta as a precaution then everything went smoothly



PS: I was forgetting, I created folder 12 in Clover for kexts

At the moment the only problem seems to be the BT and wi-fi injector (BluetoothDevBroadcomInjector.kext BroadcomWiFiInjector.kext) they don't work, they block the monterey boot

 

1347086766_Schermata2021-06-09alle00_38_

  • Like 3
Link to comment
Share on other sites

34 minutes ago, Matgen84 said:

 

Thanks. I use @AudioGod settings for my Z390 Aorus, since two years without any major problem. However, I have randomly instability (NVRAM, I suppose). What do you mean by "Boot variables. Check your Clover installation if it is in the right place."

Sory I don't understand because of my bad English.

 

EDIT 1: I just try to boot with OC's USB pen drive, no splash screen issue (without any changes in BIOS settings).

EDIT 2: Remember, it's a CLEAN INSTALL, not update

My english is also not perfect. 

But then I don't understand what is the trouble for you? Splash screen? Apple logo? Panic? Crash? or what?

Link to comment
Share on other sites

1 hour ago, Matgen84 said:

 

Thanks. I use @AudioGod settings for my Z390 Aorus, since two years without any major problem. However, I have randomly instability (NVRAM, I suppose). What do you mean by "Boot variables. Check your Clover installation if it is in the right place."

Sory I don't understand because of my bad English.

 

EDIT 1: I just try to boot with OC's USB pen drive, no splash screen issue (without any changes in BIOS settings).

EDIT 2: Remember, it's a CLEAN INSTALL, not update


@Slice @Jief_Machak

Another strange behavior: when I try to boot from my Monterey's USB, to launch my Big Sur HDD: always BIOS splash screen (r5136). See debug.log: 

38:579  0:025  === [ GetEfiBootDeviceFromNvram ] ===============
38:605  0:025   - [!] efi-boot-device-data not found
38:631  0:025  Default boot entry not found

 

2021-06-08_07-58_BOOTX64.EFI.log

 

Edited by Matgen84
Link to comment
Share on other sites

2 hours ago, Matgen84 said:


@Slice @Jief_Machak

Another strange behavior: when I try to boot from my Monterey's USB, to launch my Big Sur HDD: always BIOS splash screen (r5136). See debug.log: 


38:579  0:025  === [ GetEfiBootDeviceFromNvram ] ===============
38:605  0:025   - [!] efi-boot-device-data not found
38:631  0:025  Default boot entry not found

 

2021-06-08_07-58_BOOTX64.EFI.log 67.95 kB · 1 download

 

WHat if you change GUI theme?

  • Like 1
Link to comment
Share on other sites

1 hour ago, Slice said:

WHat if you change GUI theme?

Good idea. :) But I use the same theme, since the beginning of Big Sur.

EDIT: I have no problem with Opencore. I want to keep Clover on my Z390 config.

 

TEMPORARY solution: I boot Big Sur with an Opencore's USB stick. When I arrive on the finder, I click shutdown. Few minutes later, I use a Clover's USB stick with a new theme, works, and my Big Sur HDD (Clover) can boot also :hysterical:

 

EDIT 2: 5 minutes later, the temporary solution do not work: splash screen again. :cry:

Edited by Matgen84
do not work
  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...