Contribute
Register

get same issues on boot

Status
Not open for further replies.
on this line stuck boot same I finking maybe same more kext need kext/other or maybe patch for this Macbookpro 11.1 or maybe I'm wrong?
 

Attachments

  • DSC_0050-2.JPG
    DSC_0050-2.JPG
    756.3 KB · Views: 46
on this line stuck boot same I finking maybe same more kext need kext/other or maybe patch for this Macbookpro 11.1 or maybe I'm wrong?

Your ioreg indicates successful boot.
You will need to explain more clearly what you're doing.
 
I just changed clover to 11.1 from imac 14.1 I fink. And then I start get this issue
 
I just changed clover to 11.1 from imac 14.1 I fink. And then I start get this issue

The ioreg you attached shows MacBookPro11,1.
What is the issue?
 
issue is in photo were Mac OS boots stop working and then I restart and in clover start do without sorted order then boot normal but if I use sorted order I get this issue from foto post #21
 
issue is in photo were Mac OS boots stop working and then I restart and in clover start do without sorted order then boot normal but if I use sorted order I get this issue from foto post #21

Nonsense.
Your Clover bootlog, extracted from ioreg, shows SortedOrder being used:
Code:
11:635  0:000  Start: Processing Patched AML(s): Sorted
11:635  0:000  Inserting table[0]:SSDT.aml from EFI\CLOVER\ACPI\patched ... Success
11:636  0:001  Inserting table[1]:SSDT-0.aml from EFI\CLOVER\ACPI\patched ... Success
11:636  0:000  Inserting table[2]:SSDT-1.aml from EFI\CLOVER\ACPI\patched ... Success
11:636  0:000  Inserting table[3]:SSDT-2.aml from EFI\CLOVER\ACPI\patched ... Success
11:637  0:000  Inserting table[4]:SSDT-3.aml from EFI\CLOVER\ACPI\patched ... Success
11:637  0:000  Inserting table[5]:SSDT-4.aml from EFI\CLOVER\ACPI\patched ... Success
11:638  0:000  Inserting table[6]:SSDT-12.aml from EFI\CLOVER\ACPI\patched ... Success
11:638  0:000  Inserting table[7]:SSDT-13.aml from EFI\CLOVER\ACPI\patched ... Success
11:638  0:000  End: Processing Patched AML(s)
 
Nonsense.
Your Clover bootlog, extracted from ioreg, shows SortedOrder being used:
Code:
11:635  0:000  Start: Processing Patched AML(s): Sorted
11:635  0:000  Inserting table[0]:SSDT.aml from EFI\CLOVER\ACPI\patched ... Success
11:636  0:001  Inserting table[1]:SSDT-0.aml from EFI\CLOVER\ACPI\patched ... Success
11:636  0:000  Inserting table[2]:SSDT-1.aml from EFI\CLOVER\ACPI\patched ... Success
11:636  0:000  Inserting table[3]:SSDT-2.aml from EFI\CLOVER\ACPI\patched ... Success
11:637  0:000  Inserting table[4]:SSDT-3.aml from EFI\CLOVER\ACPI\patched ... Success
11:637  0:000  Inserting table[5]:SSDT-4.aml from EFI\CLOVER\ACPI\patched ... Success
11:638  0:000  Inserting table[6]:SSDT-12.aml from EFI\CLOVER\ACPI\patched ... Success
11:638  0:000  Inserting table[7]:SSDT-13.aml from EFI\CLOVER\ACPI\patched ... Success
11:638  0:000  End: Processing Patched AML(s)
so can you look in this video I need all time drop sorted order if u can see in this video. I just take of tick and then its booting
 
so can you look in this video I need all time drop sorted order if u can see in this video. I just take of tick and then its booting

DropOem should already be true (because you have patched SSDTs in ACPI/patched).
 
yes its should be but why is not? :(

Probably you're not modifying the config.plist that you're actually using.
Refer to your Clover bootlog to determine from where Clover is loading config.plist (it is the same volume that Clover itself boots from).
You can change something that has little effect in your config.plist to verify you're looking at the right file. For example, if you change the theme used, but it has no effect, then you know you're looking at the wrong file. Or you could add -v to config.plist/Boot/Arguments. If verbose boot doesn't default after making that change, then you're not editing the file you're actually using...

Note also that Clover r3974 is very old... No idea why you're using such an old revision of Clover with 10.12.2 (why 10.12.2?)
 
Status
Not open for further replies.
Back
Top