Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
29,872 posts in this topic

Recommended Posts

Slice
Slice
Posted
Posted
13 hours ago, naiclub said:

Has anyone succeeded? bigsar 11
I waited hopefully.

To be honest, I am bored with many open cores.
I don't know my computer will crash, I still don't know what day.

I have joined to lucky club of clover booted macOS 11.0 BigSur. Respects to @Jief_Machak.

Moreover I made update from Beta3 to Beta 8 with this bootloader.

Continue developments.

  • Like 8
  • Haha 1
Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted

I can boot Big Sur  with Jief version on the OC side but when I switch to clover I get a reboot about halfway through booting. 
I’ll comb through my configs and check for differences. Will post results but looking good so far. Might even have a look at iCanaro EFI for hints. 

  • Like 3
Link to comment
Share on other sites
Guest
Guest
Posted
Posted
16 minutes ago, SavageAUS said:

I can boot Big Sur  with Jief version on the OC side but when I switch to clover I get a reboot about halfway through booting. 
I’ll comb through my configs and check for differences. Will post results but looking good so far. Might even have a look at iCanaro EFI for hints. 

Are you testing with your Ryzen rig?

If so are you using latest experimental patches (if you are using Big Sur greater than beta6)?

I have the same your behaviour with my thread ripper rig (I was in beta 8 and with all new kernel patches needed, and Opencore starts fine in this condition)

Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted
16 minutes ago, fabiosun said:

Are you testing with your Ryzen rig?

If so are you using latest experimental patches (if you are using Big Sur greater than beta6)?

I have the same your behaviour with my thread ripper rig (I was in beta 8 and with all new kernel patches needed, and Opencore starts fine in this condition)

Nah on my intel laptop.

Intel first then i'll try my Ryzen build.

The last line i recorded before the reboot is

RTC: Only Single RAM Bank (128 bytes)

Link to comment
Share on other sites
fusion71au
fusion71au
Posted
Posted
2 hours ago, Slice said:

I have joined to lucky club of clover booted macOS 11.0 BigSur. Respects to @Jief_Machak.

Moreover I made update from Beta3 to Beta 8 with this bootloader.

Continue developments.

 

Works for me too.  May I also join the club :hysterical:?

 

Tested Big Sur Beta6 USB Installer, Beta8 (already installed previously with OC 0.6.2) and Catalina 10.15.7 on my Skylake NUC6i5SYH.

Adapted my already working Clover config.plist with quirks from my OC 0.6.2 config.plist...

          added OC config.plist/Booter/Quirks ---> Clover config.plist/OcQuirks

          and OC config.plist/Kernel/Quirks --->  Clover config.plist/KernelAndKextPatches/OcQuirks

 

Spoiler

395210510_NewCloverconfig.thumb.png.49da1df89af44bbbef514ce34c46a646.png1483395158_Preboot11.thumb.png.8eb344b1e4ea1df17beb091b200cbed3.png

 

preboot.log

 

Thanks to @Jief_Machak, @iCanaro for your EFI template and the other testers :).

  • Like 4
  • Thanks 1
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
21 minutes ago, fusion71au said:

 

Works for me too.  May I also join the club :hysterical:?

 

Tested Big Sur Beta6 USB Installer, Beta8 (already installed previously with OC 0.6.2) and Catalina 10.15.7 on my Skylake NUC6i5SYH.

Adapted my already working Clover config.plist with quirks from my OC 0.6.2 config.plist...

          added OC config.plist/Booter/Quirks ---> Clover config.plist/OcQuirks

          and OC config.plist/Kernel/Quirks --->  Clover config.plist/KernelAndKextPatches/OcQuirks

 

 

preboot.log

 

Thanks to @Jief_Machak, @iCanaro for your EFI template and the other testers :).

 

Thanks to join the club. :hysterical: I don't test the Jief's version on Mojave or Catalina: can you boot these OS, do you have normal kext injection with 10.14 or 10.15 folder ! I believed that Jief's CloverX64 is using only "10 folder" instead of 10.14 or 10.15.

Please, can you tell to me the behavoir for kext injection: upload preboot.log (Mojave or Catalina) if you can.

  • Like 1
  • Haha 1
Link to comment
Share on other sites
fusion71au
fusion71au
Posted
Posted (edited)
14 hours ago, Matgen84 said:

 

Thanks to join the club. :hysterical: I don't test the Jief's version on Mojave or Catalina: can you boot these OS, do you have normal kext injection with 10.14 or 10.15 folder ! I believed that Jief's CloverX64 is using only "10 folder" instead of 10.14 or 10.15.

Please, can you tell to me the behavoir for kext injection: upload preboot.log (Mojave or Catalina) if you can.

 

Yes, tested OK booting to Catalina 10.15.7 as well as Big Sur Beta8.  Kext injection works from "Other" folder, as well as 10.15 folder (or 10.14, 10.13 etc)...

 

Spoiler

1315738740_Catalinaboot.thumb.png.a55121d3735b44b1eb0e9e279eb5dbb2.png1624988598_BigSurboot.thumb.png.d1804d5f913ee4559083ce46b2283427.png

 

Full boot log booting to 10.15.7...debug.log

Spoiler 

45:044  0:058  UniOSVersion == 10.15.7
45:107  0:062  UniShortOSVersion == 10.15
45:168  0:060  AddKextsInArray from EFI\CLOVER\OEM\NUC6i5SYB\UEFI\kexts\Other
45:228  0:059  ->Extra kext: EFI\CLOVER\OEM\NUC6i5SYB\UEFI\kexts\Other\Lilu.kext (v.1.4.8)
45:331  0:103  ->Extra kext: EFI\CLOVER\OEM\NUC6i5SYB\UEFI\kexts\Other\IntelMausiEthernet.kext (v.2.4.0d0)
45:389  0:058  ->Extra kext: EFI\CLOVER\OEM\NUC6i5SYB\UEFI\kexts\Other\WhateverGreen.kext (v.1.4.3)
45:452  0:063  ->Extra kext: EFI\CLOVER\OEM\NUC6i5SYB\UEFI\kexts\Other\EFICheckDisabler.kext (v.0.5)
45:517  0:064  ->Extra kext: EFI\CLOVER\OEM\NUC6i5SYB\UEFI\kexts\Other\SMCProcessor.kext (v.1.1.7)
45:576  0:058  ->Extra kext: EFI\CLOVER\OEM\NUC6i5SYB\UEFI\kexts\Other\AppleALC.kext (v.1.5.3)
45:675  0:099  ->Extra kext: EFI\CLOVER\OEM\NUC6i5SYB\UEFI\kexts\Other\USBInjectAll.kext (v.0.6.7)
45:736  0:060  ->Extra kext: EFI\CLOVER\OEM\NUC6i5SYB\UEFI\kexts\Other\VirtualSMC.kext (v.1.1.7)
45:808  0:071  AddKextsInArray from \EFI\CLOVER\kexts\Off
45:866  0:058  AddKextsInArray from EFI\CLOVER\OEM\NUC6i5SYB\UEFI\kexts\10
45:926  0:059  AddKextsInArray from EFI\CLOVER\OEM\NUC6i5SYB\UEFI\kexts\10_normal
46:041  0:114  AddKextsInArray from EFI\CLOVER\OEM\NUC6i5SYB\UEFI\kexts\10.15
46:141  0:100  AddKextsInArray from EFI\CLOVER\OEM\NUC6i5SYB\UEFI\kexts\10.15_normal
46:202  0:060  AddKextsInArray from EFI\CLOVER\OEM\NUC6i5SYB\UEFI\kexts\10.15.7
46:264  0:062  AddKextsInArray from EFI\CLOVER\OEM\NUC6i5SYB\UEFI\kexts\10.15.7_normal
46:325  0:061  Bridge kext to OC : Path=Lilu.kext
46:384  0:059  Bridge kext to OC : Path=VirtualSMC.kext
46:454  0:069  Bridge kext to OC : Path=WhateverGreen.kext
46:522  0:067  Bridge kext to OC : Path=AppleALC.kext
46:614  0:092  Bridge kext to OC : Path=SMCProcessor.kext
46:678  0:063  Bridge kext to OC : Path=IntelMausiEthernet.kext
46:745  0:066  Bridge kext to OC : Path=EFICheckDisabler.kext
46:801  0:056  Bridge kext to OC : Path=USBInjectAll.kext

 

 

 

14 hours ago, D-an-W said:

Are there any specific Quirks that need to be enabled for Big Sur to boot?

 

Quirk settings depend on your specific hardware - see Dortania OC guide.

 

The same config boots all the OSes so most likely will work for Big Sur if it also works for Catalina (assuming your SMBIOS and hardware are supported in Big Sur of course). 

 

 

11 hours ago, SavageAUS said:

Can all the members of the club that have booted Big Sur with Clover please confirm that Windows boots as windows with native aml and not as bootcamp.

 

Windows OEM info unchanged from original on my NUC6i5SYH...

Spoiler

712481194_WindowsCloverBoot.thumb.png.94ec830ce380c5105ca7fb015628e376.png

 

Edited by fusion71au
Added screenshots
  • Thanks 1
Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted (edited)

Can all the members of the club that have booted Big Sur with Clover please confirm that Windows boots as windows with native aml and not as bootcamp. 
 

Also would anybody be willing to help me to get mine booting?

 

I have a working OC for Big Sur and Catalina and a working Clover for Catalina. 
I have been trying for hours, even using iCanaro EFI as a base.

 

I’ll attach files to this post after my laptop has charged a bit. But it’s all on my github also. 

Edited by SavageAUS
Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted (edited)
14 hours ago, iCanaro said:

@naiclub my EFI Z370 BS ready https://mega.nz/file/GvgCRRiK#7fmYQfvLmfMDEEWeoilF-WkbhbLhuiy3__s_Y06frjQ

Finally I was able to boot into Big Sur using your EFI as a base but I’ve noticed that all of my smbios info was not injected. Are you seeing this also?

Edited by SavageAUS
  • Sad 1
Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted
3 hours ago, SavageAUS said:

Can all the members of the club that have booted Big Sur with Clover please confirm that Windows boots as windows with native aml and not as bootcamp. 
 

Also would anybody be willing to help me to get mine booting?

 

I have a working OC for Big Sur and Catalina and a working Clover for Catalina. 
I have been trying for hours, even using iCanaro EFI as a base.

 

I’ll attach files to this post after my laptop has charged a bit. But it’s all on my github also. 

 

me too. hope native aml and vendor and manufactor. bcuz i don't use bootcamp.

hope clover keep going for macOS without effect other OS(Windows and Etc)

Link to comment
Share on other sites
iCanaro
iCanaro
Posted
Posted (edited)
3 hours ago, Slice said:

Yes, I successfully booted windows, but I don’t know details yet.

 

I was sick, I assumed clover would regularly start windows, but in my Z370 does not start with custom entries as set by default or even setting auto

 

windows crashes immediately as soon as the rotating balls start loading
i on efi separate win10 pro and win10 LTSC

 

PS: even linux mageia makes me exactly like windows, immediate freeze as you select activate its boot

Edited by iCanaro
  • Thanks 1
Link to comment
Share on other sites
naiclub
naiclub
Posted
Posted (edited)
18 hours ago, iCanaro said:

@naiclub my EFI Z370 BS ready https://mega.nz/file/GvgCRRiK#7fmYQfvLmfMDEEWeoilF-WkbhbLhuiy3__s_Y06frjQ

Thanks to iCanaro, courtesy EFI.
Reported now I can boot running 10.13 10.14 10.15 10.16 or 11 works flawlessly. But stuck at Windows 10 still can't boot

Anyway, there will be no open cores blocking my BIOS entrance.
Sorry. My English is not good.

1437593746_ScreenShot2563-09-27at22_42_25.thumb.png.a9d084e6f9bae32c0b3b9fd44de806f7.png2040178352_ScreenShot2563-09-27at23_21_47.thumb.png.37e5adcb75a204b78e08d5b3363f2d98.png653694467_2563-09-2722_52_24.thumb.png.a644139af0ada607134155f1c418331f.png810873346_2563-09-2723_04_34.thumb.png.54f7c67817a72cc2b76fd47a4ca11ca0.png

Edited by naiclub
Link to comment
Share on other sites
naiclub
naiclub
Posted
Posted
Just now, SavageAUS said:

Finally I was able to boot into Big Sur using your EFI as a base but I’ve noticed that all of my smbios info was not injected. Are you seeing this also?

In this section, you need to inject more.
As you understand it, SMBIOS must belong to each machine.

Link to comment
Share on other sites
1Revenger1
1Revenger1
Posted
Posted
1 hour ago, mifjpn said:

I'm happy that the raw BIOS data is used to boot Windows on Clover.
The reason is that in OpenCore, when Windows is booted, it becomes a disguised BIOS, which causes problems with the operation of Windows and the BIOS.

OpenCore can be told to not inject SMBIOS info into windows/Linux (mostly be redirecting it to a different EFI variable iirc and applying a kernel patch to macOS). It'll still do ACPI modifications though.

Link to comment
Share on other sites
naiclub
naiclub
Posted
Posted (edited)
38 minutes ago, mifjpn said:

 Thank you so much.It is useful infomation.You said "mostly be redirecting it to a different EFI variable iirc".If so, is there a any WebPage that details that? I want to refer to it.
 And If so, is there a WebPage that details that? I want to refer to it.
 But I'm sad about the modification of ACPI. (I think it's the difference in the development philosophy of not having boot manager and booter together.)

Thnak you.

 

According to my understanding that The developers intentionally wrote that (If there is a violation) or fix the SMBIOS will immediately suspend the use. By blocking the BIOS entrance in order to reset the BIOS. (Or in general) Kill the motherboard. Or because of fear of violating the copyright?

Still, I believe it's definitely not better than this Clover

Edited by naiclub
Link to comment
Share on other sites
1Revenger1
1Revenger1
Posted
Posted (edited)
1 hour ago, mifjpn said:

 Thank you so much.It is useful infomation.You said "mostly be redirecting it to a different EFI variable iirc".
 And If so, is there a WebPage that details that? I want to refer to it.
 But I'm sad about the modification of ACPI. (I think it's the difference in the development philosophy of not having boot manager and booter together.)

Thnak you.

 

The configuration.pdf in the OpenCorePkg repo talks about it under the docs folder, iirc it's PlatformInfo->CreateSMBIOSMode = "Custom" (normally people set it to "Create") and under Kernel->Quirks, set CustomSMBIOSGUID = true.

 

42 minutes ago, naiclub said:

According to my understanding that The developers intentionally wrote that (If there is a violation) or fix the SMBIOS will immediately suspend the use. By blocking the BIOS entrance in order to reset the BIOS. (Or in general) Kill the motherboard. Or because of fear of violating the copyright?

OpenCore can't know what your going to do once your in the picker. What if you boot open shell, or boot macOS and you get kicked out of boot.efi, and then decide to boot windows? ACPI modifications will already have been done as well as memory quirks. It's mostly about keeping a consistent environment, something which is predictable.

Edit: Oh, here's the post from DF about it:

 

Edited by 1Revenger1
  • Sad 1
Link to comment
Share on other sites
JorgeMax
JorgeMax
Posted
Posted
22 hours ago, iCanaro said:

@naiclub my EFI Z370 BS ready https://mega.nz/file/GvgCRRiK#7fmYQfvLmfMDEEWeoilF-WkbhbLhuiy3__s_Y06frjQ

Thanks for sharing friend

 

Tests also made with FakeSMC, but it gets stuck right after the Clover selection screen.
Only boots with VirtualSMC, so I lost most of the sensors on my motherboard

 

@Jief_Machakdoes this modified Clover not inject with FakeSMC? Thanks for your work man

  • Sad 1
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...