Jump to content

Clover General discussion


ErmaC
30,167 posts in this topic

Recommended Posts

2 minutes ago, Jief_Machak said:

@everyone. As far as I know, there is NO special processing when it's a main partition or not. For Clover it's just a partition that contains an .efi, so let's boot it.

Nothing is made in Clover to make a main partition bootable or not. That's why I said that it was an Apple change. No commit, either old ones or new ones will change that.

But I'm doing now is to hide main BS partition. That's all.

Exactly.

Link to comment
Share on other sites

2 hours ago, Download-Fritz said:

@jlrycm Please read what you quoted. Booting the main partition is not supported. If it worked before, nice that you had luck, but if now it doesn't, Apple does and will not care.

For example, in Catalina, I first installed the preboot which was to appear after the file copy process successfully.

From mojave to Bigsur, I have seen that pre-boot process all over again because I used opencore a while ago. Before coming to Clover

  • Thanks 1
Link to comment
Share on other sites

1 hour ago, Jief_Machak said:

Voici une version qui corrige MatchOS CloverX64-2020-10-19-19-09-31-2d124e4-dirty-jief.zip 

Faites-moi savoir si cela fonctionne, alors je l'engagerai.

 

boot with the latest CloverX64-2020-10-19-19-09-31-2d124e4-dirty-jief OK loads the DSDT here on my HP Envy Recline where I tested it has some points that are still not 100%

1 - with this file it takes more time to enter the graphical interface Clover!

2 - attempt to install Beta 10 is in gray screen with the mouse pointer is just that

3 - installation of the betas all until 9 I can pass the first phase, restart and in the second phase at the time that there should be the 29 minute discount, it just restarts and always stays on it without showing any kernel panic, the same happens with OpenCore!

 

Thanks for the work

 

google translate ! 

Spoiler

1191935163_Capturedecran2020-10-19a19_29_22.thumb.png.c793c7b4632ba73cdcb4c8b65668b05f.png1701278924_Capturedecran2020-10-19a19_29_14.thumb.png.703752f17d4667196359dd4185069068.png

 

debug.log

  • Like 2
Link to comment
Share on other sites

3 hours ago, Jief_Machak said:

Here is a version that fixes MatchOS CloverX64-2020-10-19-19-09-31-2d124e4-dirty-jief.zip 

Let me know if it's working, so I'll commit it.

 

mmmm something doesn't add up
with the configs with which I started Catalina and BS, now that I have defined matchos, it continues to work. Previously these configs with Mojaver, started it but at one point there was a KP; now with this new Clover commit, it just doesn't start.
Same thing with the config that started me mojave and catalina, with the MatchOS defined, Mojave does not start.

here are the logs, I generated them using the same config to start the various macOS

BS --> OK
Catalina --> OK
Mojave --> no boot

 

 

 

 

 

 

preboot.log

X570_BS_debug.log

X570_Catalina_debug.log

X570_Mojave_NOK_debug.log

Edited by iCanaro
  • Like 1
  • Confused 1
Link to comment
Share on other sites

1 hour ago, iCanaro said:

 

mmmm something doesn't add up
with the configs with which I started Catalina and BS, now that I have defined matchos, it continues to work. Previously these configs with Mojaver, started it but at one point there was a KP; now with this new Clover commit, it just doesn't start.
Same thing with the config that started me mojave and catalina, with the MatchOS defined, Mojave does not start.

here are the logs, I generated them using the same config to start the various macOS

BS --> OK
Catalina --> OK
Mojave --> no boot

 

 

 

 

 

 

preboot.log

X570_BS_debug.log

X570_Catalina_debug.log

X570_Mojave_NOK_debug.log

 

here for all systems this is 100%

I don't have any kernel panic to boot in between High Sierra 10.13.6, Mojave 10.14.6, Catalina 10.15.7 and finally BigSur Beta 10 as well as Windows boot correctly!

 

https://we.tl/t-V39jspV1iE

  • Like 2
  • Sad 1
Link to comment
Share on other sites

50 minutes ago, PG7 said:

here for all systems this is 100%

I don't have any kernel panic to boot in between High Sierra 10.13.6, Mojave 10.14.6, Catalina 10.15.7 and finally BigSur Beta 10 as well as Windows boot correctly!

if you pass me the you kerneltopatch so i can check if that's my problem
 

Link to comment
Share on other sites

19 minutes ago, iCanaro said:

if you pass me the you kerneltopatch so i can check if that's my problem

 

 

<key>KernelToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>Disable panic kext logging on 10.14 Release kernel</string>
				<key>Disabled</key>
				<true/>
				<key>Find</key>
				<data>
				igKEwHRC
				</data>
				<key>MaskFind</key>
				<data>
				////////
				</data>
				<key>MaskReplace</key>
				<data>
				AAAAAP8A
				</data>
				<key>MatchOS</key>
				<string>10.14</string>
				<key>Replace</key>
				<data>
				igKEwOtC
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>Disable panic kext logging on 10.13 Release kernel</string>
				<key>Disabled</key>
				<true/>
				<key>Find</key>
				<data>
				igKEwHRE
				</data>
				<key>MatchOS</key>
				<string>10.13</string>
				<key>Replace</key>
				<data>
				igKEwOtE
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>Lapic panic patch example</string>
				<key>Disabled</key>
				<true/>
				<key>Find</key>
				<data>
				6AAA//+DAAAAAAAA
				</data>
				<key>MaskFind</key>
				<data>
				/wAA////AAAAAP//
				</data>
				<key>MaskReplace</key>
				<data>
				/wAA////////////
				</data>
				<key>MaskStart</key>
				<data>
				/////wA=
				</data>
				<key>MatchOS</key>
				<string>All</string>
				<key>RangeFind</key>
				<integer>200</integer>
				<key>Replace</key>
				<data>
				6AAA//8xwJCQkJCQ
				</data>
				<key>StartPattern</key>
				<data>
				ACnHeAAx241H+oM=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>Symbolic patch example got lapic panic</string>
				<key>Disabled</key>
				<true/>
				<key>Find</key>
				<data>
				6AAA//+DAAAAAAAA
				</data>
				<key>MaskFind</key>
				<data>
				/wAA////AAAAAP//
				</data>
				<key>MaskReplace</key>
				<data>
				/wAA////////////
				</data>
				<key>MaskStart</key>
				<data>
				/////wA=
				</data>
				<key>MatchOS</key>
				<string>All</string>
				<key>Procedure</key>
				<string>_lapic_interrupt</string>
				<key>RangeFind</key>
				<integer>200</integer>
				<key>Replace</key>
				<data>
				6AAA//8xwJCQkJCQ
				</data>
				<key>StartPattern</key>
				<data>
				ACnHeAAx241H+oM=
				</data>
			</dict>
		</array>
		<key>KernelXCPM</key>
		<false/>
		<key>PanicNoKextDump</key>
		<true/>
	</dict>
	<key>Quirks</key>
	<dict>
		<key>AppleXcpmExtraMsrs</key>
		<false/>
		<key>AppleXcpmForceBoost</key>
		<false/>
		<key>AvoidRuntimeDefrag</key>
		<true/>
		<key>DevirtualiseMmio</key>
		<false/>
		<key>DisableIoMapper</key>
		<true/>
		<key>DisableLinkeditJettison</key>
		<true/>
		<key>DisableRtcChecksum</key>
		<false/>
		<key>DisableSingleUser</key>
		<false/>
		<key>DisableVariableWrite</key>
		<false/>
		<key>DiscardHibernateMap</key>
		<false/>
		<key>DummyPowerManagement</key>
		<false/>
		<key>EnableSafeModeSlide</key>
		<true/>
		<key>EnableWriteUnprotector</key>
		<true/>
		<key>ExternalDiskIcons</key>
		<false/>
		<key>ForceExitBootServices</key>
		<false/>
		<key>FuzzyMatch</key>
		<true/>
		<key>IncreasePciBarSize</key>
		<false/>
		<key>KernelCache</key>
		<string>Auto</string>
		<key>MmioWhitelist</key>
		<array>
			<dict>
				<key>Address</key>
				<integer>4275159040</integer>
				<key>Comment</key>
				<string>Haswell: SB_RCBA is a 0x4 page memory region, containing SPI_BASE at 0x3800 (SPI_BASE_ADDRESS)</string>
				<key>Enabled</key>
				<false/>
			</dict>
			<dict>
				<key>Address</key>
				<integer>4278190080</integer>
				<key>Comment</key>
				<string>Generic: PCI root is a 0x1000 page memory region used by some firmwares</string>
				<key>Enabled</key>
				<false/>
			</dict>
		</array>
		<key>PowerTimeoutKernelPanic</key>
		<true/>
		<key>ProtectMemoryRegions</key>
		<false/>
		<key>ProtectSecureBoot</key>
		<false/>
		<key>ProtectUefiServices</key>
		<false/>
		<key>ProvideConsoleGopEnable</key>
		<true/>
		<key>ProvideCustomSlide</key>
		<false/>
		<key>ProvideMaxSlide</key>
		<integer>0</integer>
		<key>RebuildAppleMemoryMap</key>
		<false/>
		<key>SetupVirtualMap</key>
		<true/>
		<key>SignalAppleOS</key>
		<false/>
		<key>SyncRuntimePermissions</key>
		<true/>
		<key>ThirdPartyDrives</key>
		<true/>
		<key>XhciPortLimit</key>
		<false/>
	</dict>

826733695_Capturedecran2020-10-19a23_34_08.thumb.png.2df66d7ce624fe8fa0dd24e7807a0d26.png

  • Thanks 1
  • Sad 1
Link to comment
Share on other sites

2 minutes ago, iCanaro said:

ehhehe I misunderstood, I thought you had an AMD ryzen system with 17h kernel patches :D

 

 

Nop 

 

no AMD ... 

 

Intel + intel + intel ........... intel :graduated:

  • Like 2
  • Sad 1
Link to comment
Share on other sites

With the new changes that are coming / already implemented to hide main big sur volume does anyone have a guide on creating a custom entry for the preboot volume?

 

Also been bugging me for a while @Vinicius P. Miranda please fix your signature.

Spoiler

 

i7 3930k (Sady Bridge-E) - Rampage IV Extreme (x79) Bios 4901 Modified to NVME - AMD RX 5700XT - 16GB (4x4GB) Ripjaws 1866MHz - Catalina 10.15.7

 

To

 

i7 3930k (Sandy Bridge-E) - Rampage IV Extreme (x79) Bios 4901 Modified to NVME - AMD RX 5700XT - 16GB (4x4GB) Ripjaws 1866MHz - Catalina 10.15.7

 

 

  • Like 2
Link to comment
Share on other sites

@Vinicius P. Miranda

 

https://dortania.github.io/OpenCore-Install-Guide/config-HEDT/ivy-bridge-e.html

Maybe try the Ivy Bridge cpuid. Dortania says Sandy Bridge-E applies. It's worth a shot

Screen Shot 2020-10-20 at 12.12.50 AM.png

https://dortania.github.io/OpenCore-Install-Guide/config-HEDT/ivy-bridge-e.html

Maybe try the Ivy Bridge cpuid. Dortania says Sandy Bridge-E applies. It's worth a shot

Edited by jmacie
Link to comment
Share on other sites

40 minutes ago, gerard71 said:

hello everyone I have this config.plist which works fine with clover 5123, but no longer works with clover 5125 someone can tell me what change to make to start Big sur on Kaby lake
Z270 GAMING K3 Thank you

config.plist

IMG_0204.jpeg

Did you check the sample config for changes?

  • Like 1
Link to comment
Share on other sites

Quote

Here is a version that fixes MatchOS : CloverX64-2020-10-19-19-09-31-2d124e4-dirty-jief.zip 

Let me know if it's working, so I'll commit it. 

Bigsur10 could not be installed successfully.
But can boot into the pre-installed bigsur
I need to use opencore to complete the installation in order to use clover to boot into my system normally.

  • Confused 1
Link to comment
Share on other sites

55 minutes ago, SavageAUS said:

I’ll see what I can do. But is matchOS needed if Big Sur is the only OS I’m using?

it's always better to define all fields and entries correctly, even if you only use BUgFart :D

 

now with MatchOS in place, from me the previously posted config 29 correctly starts mojave, catalina and BS @Jief_Machak :thumbsup_anim:
 

PS: even the one I posted in 38 fields, now with matchos defined properly, I start mojave, catalina and BS

Edited by iCanaro
  • Like 2
  • Haha 1
Link to comment
Share on other sites

×
×
  • Create New...