Jump to content
30960 posts in this topic

Recommended Posts

8 minutes ago, Matgen84 said:

 

Hi @Slice

 

I build latest commit fab169d: exactly same issue :cry:

 

Have you see kuckkuck Clover r5119 mod + kexttopatch in Hackintool-forum.de: it's to boot BS Beta 3.

 

Clover r5119 mod load old /System/Library/PrelinkedKernels/prelinkedkernel

But Clover 5120 load new /System/Library/KernelCollections/BootKernelExtensions.kc

 

Maybe BootKernelExtensions.kc is harder to hack.:)

  • Like 2
17 minutes ago, crazybirdy said:

 

Clover r5119 mod load old /System/Library/PrelinkedKernels/prelinkedkernel

But Clover 5120 load new /System/Library/KernelCollections/BootKernelExtensions.kc

 

Maybe BootKernelExtensions.kc is harder to hack.:)

 

Right @crazybirdy What do you think of his KextToPatch !

10 minutes ago, Matgen84 said:

 

Right @crazybirdy What do you think of his KextToPatch !

 

I think KextToPatch is not the issue.

 

Maybe decode is the problem.

How to decode prelinkedkernel to be kernel and kexts?

How to decode BootKernelExtensions.kc to be kernel and kexts?

 

After decode BootKernelExtensions.kc, it start to patch kexts and kernel.

 

But it's not my ability, we need ......Slice :yes::thumbsup_anim:

  • Like 3
6 hours ago, crazybirdy said:

After decode BootKernelExtensions.kc, it start to patch kexts and kernel.

 

But it's not my ability, we need ......Slice :yes::thumbsup_anim:

Maybe also need the genious @Zenith432 B)

  • Like 3
  • Thanks 1

Hi @Slice

 

I  build latest commit 32eba04: it's better I think. Thanks.

 

  • Can't boot on Big Sur Installer and Installed Big Sur: stuck this time at apfs_module

I see "couldn't load" kexts and "couldn't alloc" messages

 

 

debug.log

anyone have Sandy Bridge working config for high sierra 

 

Model: AH512

IntelÆ CoreTM i3 processor 2.2 GHz

2GB DDR3 SDRAM

hard drive 320GB

Graphics Coprocessor     Intel HD Graphics 3000

Screen Resolution     1366 x 768

Edited by ameenjuz
9 hours ago, ameenjuz said:

anyone have Sandy Bridge working config for high sierra 

 

Model: AH512

IntelÆ CoreTM i3 processor 2.2 GHz

2GB DDR3 SDRAM

hard drive 320GB

Graphics Coprocessor     Intel HD Graphics 3000

Screen Resolution     1366 x 768

You'd better to ask in specialized subforum Intel

 

4 minutes ago, mifjpn said:

Hello,Slice.

There was nothing wrong with what you were doing.
You are great! !!

I still can't believe it, but Big Sur Developer Beta 3 was bootable by 32eba04-bulid.

I built Kext myself using "Kexts Update.command" from "Olarila Big Sur Vanilla Image / USB Installation". I updated EFI with that Kext.

The assembly parts of my computer are probably lucky. It's not expensive

i7-8700,ASUS PRIME H370-A/CSM,RAM 16GB(8GB+8GB),MSI RX-570,Pionner BD-209(Pached)

I couldn't believe it, so I took an uncut boot-time movie. And I confirmed the upgrade of the Clover package to another EFI twice.
The web page is below.
surprise! BigSurBeta3 booted with Clover (32eba04-bulid).(include movie and EFI zipfile)

I am moving to BigSur.

  • Like 1
4 hours ago, mifjpn said:

Hello,Slice.

There was nothing wrong with what you were doing.
You are great! !!

I still can't believe it, but Big Sur Developer Beta 3 was bootable by 32eba04-bulid.

I built Kext myself using "Kexts Update.command" from "Olarila Big Sur Vanilla Image / USB Installation". I updated EFI with that Kext.

The assembly parts of my computer are probably lucky. It's not expensive

i7-8700,ASUS PRIME H370-A/CSM,RAM 16GB(8GB+8GB),MSI RX-570,Pionner BD-209(Pached)

I couldn't believe it, so I took an uncut boot-time movie. And I confirmed the upgrade of the Clover package to another EFI twice.
The web page is below.
surprise! BigSurBeta3 booted with Clover (32eba04-bulid).(include movie and EFI zipfile)

i've tried using your EFI, and combine my config.plist with your quirks setting

but unfortunately i am still unable to boot big sur beta 3, many "couldnt load kext" error, just like latest clover 5120 release...

  • Sad 1
20 minutes ago, aryaone said:

i've tried using your EFI, and combine my config.plist with your quirks setting

but unfortunately i am still unable to boot big sur beta 3, many "couldnt load kext" error, just like latest clover 5120 release...

In my Z77 hackintosh only previous modified 5119 can boot Big Sur beta2 & beta3 as well as Catalina, but failed for BS installer. That means old OcQuirks.efi (59KB) worked, but new one (43KB) failed !

Screen Shot 2020-07-26 at 5.42.18 PM.png

Edited by jsl2000
28 minutes ago, jsl2000 said:

In my Z77 hackintosh only previous modified 5119 can boot Big Sur beta2 & beta3 as well as Catalina, but failed for BS installer. That means old OcQuirks.efi (59KB) worked, but new one (43KB) failed !

 

 

@jsl2000 You're using mod Clover r5119  to boot BS Beta 2 or Beta 3. With official Clover, I don't believe that the size of OcQuirks matters: in both cases, impossible to boot from USB Installer or external Hard disk, or internal hard disk on my Z390 system. At this time, of course.

Hi @Slice thanks for your efforts.

 

I  build latest commit 15b65bd95 on Z390 system

 

Can't boot on Big Sur Installer and Installed Big Sur: stuck this time at apfs_module:2411 

 

Before, I see "couldn't load" kexts and "couldn't alloc" messages

 

 

  • Like 1
2 hours ago, Matgen84 said:

Hi @Slice thanks for your efforts.

 

I  build latest commit 15b65bd95 on Z390 system

 

Can't boot on Big Sur Installer and Installed Big Sur: stuck this time at apfs_module:2411 

 

Before, I see "couldn't load" kexts and "couldn't alloc" messages

 

@Slice

Same issue here, Clover commit 15b65bd, 7/26, FYI.

 

135896.thumb.jpg.1121c70beb0bde9e8e049b6d1d16257c.jpg

 

 

  • Like 1
  • Sad 1
6 hours ago, mifjpn said:

You can boot latest commit 15b65bd from existing installed BS Beta 3 on your Hard Disk or from USB pendrive! 

It seems don't work on others mobo, yet. :cry:

 

EDIT: The same issue for commit b291971: couldn't load kext, etc

 

Edited by Matgen84
  • Like 1
On 7/16/2020 at 7:00 PM, Slice said:

I use

gcc version 10.1.0 (GCC) 

OK, got it works either with GCC 10.2.0 under Ubuntu 20.04.1 LTS after 'cd ~/src/CloverBootloader && rm -R Build && make -C BaseTools clean && make -C BaseTools/Source/C && ./ebuild'.sh -fr'. Thanks.

Screenshot at 2020-07-27 21-25-26.jpg

  • Like 2

Hi @Slice

Maybe I made a mistake somewhere

I can't boot r5120 commit 0724be9 on Big Sur (works fine for Catalina)
 

  • Can't boot on Big Sur Installer and Installed Big Sur: stuck this time at apfs_module:2411 
  • Before, I see "couldn't load" kexts and "couldn't alloc" messages
Spoiler

1.thumb.jpg.c341415537677cbca30b6daa6e38bf70.jpg

 

debug.log

  • Like 2
47 minutes ago, Matgen84 said:

Hi @Slice

Maybe I made a mistake somewhere

I can't boot r5120 commit 0724be9 on Big Sur (works fine for Catalina)
 

  • Can't boot on Big Sur Installer and Installed Big Sur: stuck this time at apfs_module:2411 
  • Before, I see "couldn't load" kexts and "couldn't alloc" messages
  Hide contents

1.thumb.jpg.c341415537677cbca30b6daa6e38bf70.jpg

 

debug.log

Delete your debug.log from misc folder. Else it grown unrestricted.

And I see no debug messages in your log. 

See kernel_patcher.cpp line 26.

There should be 

#define KERNEL_DEBUG 1

if you want to help me to see your problems.

  • Like 1
  • Thanks 1

Still not able to use OcQuirks provided by Clover 5120. Always panics at boot. This is what I am currently using in Quirks section of Clover, which is exactly the same as I am using with OcQuirks.plist.

	<key>Quirks</key>
	<dict>
		<key>AvoidRuntimeDefrag</key>
		<true/>
		<key>DevirtualiseMmio</key>
		<true/>
		<key>DisableSingleUser</key>
		<false/>
		<key>DisableVariableWrite</key>
		<false/>
		<key>DiscardHibernateMap</key>
		<false/>
		<key>EnableSafeModeSlide</key>
		<true/>
		<key>EnableWriteUnprotector</key>
		<true/>
		<key>ForceExitBootServices</key>
		<false/>
		<key>MmioWhitelist</key>
		<array/>
		<key>ProtectMemoryRegions</key>
		<false/>
		<key>ProtectSecureBoot</key>
		<false/>
		<key>ProtectUefiServices</key>
		<true/>
		<key>ProvideConsoleGopEnable</key>
		<true/>
		<key>ProvideCustomSlide</key>
		<true/>
		<key>ProvideMaxSlide</key>
		<integer>0</integer>
		<key>RebuildAppleMemoryMap</key>
		<true/>
		<key>SetupVirtualMap</key>
		<false/>
		<key>SignalAppleOS</key>
		<false/>
		<key>SyncRuntimePermissions</key>
		<true/>
	</dict>

 

On 7/25/2020 at 1:09 AM, Matgen84 said:

 

You says that you want to copy the quirks into the Clover config.plist, it's exactly what I told you. Just have a look to Config sample.plist in Clover repo.

 

What do you means by "I have a fully working OcQuirks.plist" ?

I currently use an OcQuirks.plist that is separate from the Clover config.plist and is in the drivers folder along with OcQuirks.efi

 

What I assume is that you delete that plist because the new way is to include it within the Clover config.plist. Am I wrong.

  • Like 1
6 hours ago, pkdesign said:

Still not able to use OcQuirks provided by Clover 5120. Always panics at boot. This is what I am currently using in Quirks section of Clover, which is exactly the same as I am using with OcQuirks.plist.

 

I currently use an OcQuirks.plist that is separate from the Clover config.plist and is in the drivers folder along with OcQuirks.efi

 

What I assume is that you delete that plist because the new way is to include it within the Clover config.plist. Am I wrong.

 

You're right. The new way for Clover is to include Quirks parameters in config.plist. Do you update Clover 5120 to latest commit ? 

 

Try to make two changes (Dortania Guide for Coffee Lake):

 

SetupVirtualMap to YES

EnableWriteUnprotector to FALSE

 

25 minutes ago, yapan4 said:

I have little progress after Lilu, WEG, AppleALC kexts removal and re-cleaning NVRAM.
Now no stop on apfs_module_start:2411 but boot process has progressed very little.

Clover - yesterday's

 

Hi @yapan4 What do you mean by "after Lilu, WEG, AppleALC kexts removal" 

4 hours ago, Matgen84 said:

 

Hi @yapan4 What do you mean by "after Lilu, WEG, AppleALC kexts removal" 

As @Slice say, now Clover can inject kexts but can't load acidanthera kexts. So I delete all this kexts from /EFI/Clover/kexts/Others and try boot with FakeSMC only.

Now I have stop on 'still waiting for root device'

 

debug.log

Edited by yapan4
  • Like 2
On 7/26/2020 at 6:16 PM, Matgen84 said:

 

@jsl2000 You're using mod Clover r5119  to boot BS Beta 2 or Beta 3. With official Clover, I don't believe that the size of OcQuirks matters: in both cases, impossible to boot from USB Installer or external Hard disk, or internal hard disk on my Z390 system. At this time, of course.

Please check my EFI for Clover for your reference which worked for Big Sur beta3 and Catalina in AMD FX-6300 hackintosh, but not worked for USB installer yet.

EFI.zip

  • Thanks 1
22 hours ago, Slice said:

Delete your debug.log from misc folder. Else it grown unrestricted.

And I see no debug messages in your log. 

See kernel_patcher.cpp line 26.

There should be 

#define KERNEL_DEBUG 1

if you want to help me to see your problems.

 

Thanks @Slice kernel_patcher.cpp line 26 is already #define KERNEL_DEBUG 1 in my local repo. 

 

I upload a "clean" debug.log file r5120 commit 0724be9. If you can help me to boot Big Sur  (Z390 system)

 

EDIT: I test r5119 modified by kuckkuck and his KernelToPatch in config.plist, I can boot Big Sur Beta 3 on my Z390 Aorus Master system from USB disk

 

debug.log

Edited by Matgen84
×
×
  • Create New...