Jump to content
30960 posts in this topic

Recommended Posts

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
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
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

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
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?

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
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
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

I updated and compile Clover in the Monterey OS.

0:162  0:000  Now is 09.06.2021,  17:56:32 (GMT)
0:162  0:000  Starting Clover revision: 5136 (master, commit fd780172d) on American Megatrends EFI
0:162  0:000  Build id: unknown
0:162  0:000  Build with: [Args: --conf=/Users/sergey/src/CloverBootloader/Conf -D USE_LOW_EBDA -a X64 -b RELEASE -DLESS_DEBUG -t GCC53 -n 5 | OS: 12]

Xcode 11.2.1 is still compatible with OS 12.0

  • Like 2

Installation made on top of the beta version of Big Sur:

Spoiler

1894125950_CapturadeTela2021-06-10s08_39_49.thumb.png.51d9db42f48ef36d9ba5334a2f743108.png

Spoiler

556554555_CapturadeTela2021-06-10s08_38_03.thumb.png.1a281f17a3a4c4cddd34ad7a853a43a3.png

Spoiler

478286943_CapturadeTela2021-06-09s13_43_10.thumb.png.d64057b51cf8598568981031d04f0399.png

Spoiler

1941528381_CapturadeTela2021-06-10s08_40_29.png.95dddbe7c1875a1193f8da61a2254694.png

Spoiler

366232927_CapturadeTela2021-06-10s08_40_41.png.9685e7c11caf3caad0f1f7abbf0d3200.png

 

On the first reboot the bluetooth didn't work properly, because my mouse still worked with limitations, without scrolling pages.
Then I turned it off and started and there was the Bluetooth working fully, I didn't understand

  • Like 1
7 minutes ago, JorgeMax said:

Installation made on top of the beta version of Big Sur:

 

On the first reboot the bluetooth didn't work properly, because my mouse still worked with limitations, without scrolling pages.
Then I turned it off and started and there was the Bluetooth working fully, I didn't understand

 

Great :) What Clover r5136 commit did you use.

Hi @Slice

The latest commit don't understand "os_monterey" icon name for my two theme: the Monterey's USB stick is showing "os_mac.icns" instead. I use real icns format for the icon.

Very strange again :cry:

Any ideas. Please.

 

EDIT:
I apologize maybe missing: "Install%20Install%20macOS%20Monterey", "Install%20Install%20macOS%2012" or I 
misunderstood something, sorry for my bad English.

 

Spoiler

99708262_Capturedcran2021-06-1019_19_11.thumb.png.6b4fcf9dcb537289318f333d25b969cd.png

 

Edited by Matgen84
1 hour ago, Matgen84 said:

Hi @Slice

The latest commit don't understand "os_monterey" icon name for my two theme: the Monterey's USB stick is showing "os_mac.icns" instead. I use real icns format for the icon.

Very strange again :cry:

Any ideas. Please.

 

EDIT:
I apologize maybe missing: "Install%20Install%20macOS%20Monterey", "Install%20Install%20macOS%2012" or I 
misunderstood something, sorry for my bad English.

 

  Hide contents

99708262_Capturedcran2021-06-1019_19_11.thumb.png.6b4fcf9dcb537289318f333d25b969cd.png

 

Did you know that the file named "Install macOS 12"?

9 hours ago, Slice said:

Did you know that the file named "Install macOS 12"?


Hi @Slice

I made a Monterey's USB Installer to clean install the Preview. The key is "Install macOS 12 Beta"
Maybe, for others Beta, the usb stick will be named "Install%20Install%20macOS%20Monterey". Only Apple now.

 

Spoiler

1919531486_Capturedcran2021-06-1106_13_33.png.d61679a78998747891ab1ef779152995.png

 

  • Like 1

I just build recent commits for clover and got a kernel panic in Monterey when booting. Doesn’t happen with 5136 release clover.
I did also update kexts so it could be something else. I will test more and report.


Sent from my iPhone using Tapatalk

  • Like 1

@Jief_Machak @Fetta i can't figure out how to fix this alert on my amd hack

 

754800818_Schermata2021-06-16alle00_31_22.thumb.png.6465383475b5a587d8442547afbea71e.png

config-T-RyZo.plist

 

you need help or some indication... I checked the kerneltopatch section several times, but i couldn't find a solution to the warning, thank you

1017698654_Schermata2021-06-16alle01_46_47.thumb.png.2ba72ac127077f22d31a98f6d99a334d.png

 

strange situation... I checked that if I open the plist with clover configurator last release, then I use syncronize and save, then I no longer have any error reporting from the validator, but at the boot then it does not start, as it seems to upset something and the kernel patches are not loaded. If you leave the config with the error warning, the system (whether mojave, catalina, or big sur) then loads correctly.
I think it's a really weird bug.

 

Let's hope that with translators something comes up that you understand :D

 

  • Like 1
  • Sad 1
2 hours ago, iCanaro said:

@Jief_Machak @Fetta i can't figure out how to fix this alert on my amd hack

 

754800818_Schermata2021-06-16alle00_31_22.thumb.png.6465383475b5a587d8442547afbea71e.png

config-T-RyZo.plist

 

you need help or some indication... I checked the kerneltopatch section several times, but i couldn't find a solution to the warning, thank you

I guess because 3 "Find" were found "#Find" in your config.plist.

Try to fix it for re-testing.

  • Thanks 1
5 hours ago, iCanaro said:

 

strange situation... I checked that if I open the plist with clover configurator last release, then I use syncronize and save, then I no longer have any error reporting from the validator, but at the boot then it does not start, as it seems to upset something and the kernel patches are not loaded. If you leave the config with the error warning, the system (whether mojave, catalina, or big sur) then loads correctly.
I think it's a really weird bug.

 

Let's hope that with translators something comes up that you understand :D

 

 

Hi @iCanaro

I notice that in your config.plist:

  • algrey - Disable _i386_lbr_init have a Replace, but no Find (Line 2282)
  • algrey - Disable _i386_switch_lbrs: Idem (Line 2255)
  • algrey - Disable _i386_lbr_native_state_to_mach_thread_state: Idem (Line 2337)

 

Maybe, it's an explanation for the warnings. :)  I hope 

Edited by Matgen84
  • Thanks 1
×
×
  • Create New...