obus Posted October 15, 2019 Share Posted October 15, 2019 (edited) 24 minutes ago, UefiBooter said: ok try booting with just the basic drivers and kexts ie just Lilu, VirtualSMC, WhateverGreen and AppleALC. remove AudiioDxe.efi and BootChimeDxe.efi see how far you get oh and use DEBUG versions until you get it sorted Here's the result. This must be something with my HP firmware. config.plist opencore-2019-10-15-093230.txt Edited October 15, 2019 by obus Link to comment Share on other sites More sharing options...
UefiBooter Posted October 15, 2019 Share Posted October 15, 2019 very weird, can you check if your loading anything with bcfg open shell and type bcfg driver dump (this will show any drivers that the firmware will try to load) otherwise uploaded your EFI folder. and do you really need all those ACPI patches, crazyness. Link to comment Share on other sites More sharing options...
obus Posted October 15, 2019 Share Posted October 15, 2019 (edited) 22 minutes ago, UefiBooter said: very weird, can you check if your loading anything with bcfg open shell and type bcfg driver dump (this will show any drivers that the firmware will try to load) otherwise uploaded your EFI folder. and do you really need all those ACPI patches, crazyness. bcfg driver dump = No options found. Can't boot from shell from boot menu. need to ls to correct directory and then start shell. I know it's a lot of crazy stuff in my config but that's the same I have in my working Clover. For laptops we need more of this patches than in a desktop. In my other two rigs I have nothing, only one or two SSDT for PM and EC. But this is not the big problem for the moment. Now Iv'e just wan't Oc to load my starting image. EFI.zip Edited October 15, 2019 by obus Link to comment Share on other sites More sharing options...
UefiBooter Posted October 15, 2019 Share Posted October 15, 2019 Just now, obus said: bcfg driver dump = No options found. Can't boot from shell from boot menu. need to ls to correct directory and then start shell. I know it's a lot of crazy stuff in my config but that's the same I have in my working Clover. For laptops we need more of this patches than in a desktop. In my other two rigs I have nothing, only one or two SSDT for PM and EC. But this is not the big problem for the moment. Now Iv'e just wan't to at least load my starting image. ok my skylake laptop doesnt need any of those renames its not the right way to achieve it anyway, but lets concentrate on getting the kernel to start first so remove all that. Set ProvideConsoleGop = YES Link to comment Share on other sites More sharing options...
obus Posted October 15, 2019 Share Posted October 15, 2019 (edited) 15 minutes ago, UefiBooter said: ok my skylake laptop doesnt need any of those renames its not the right way to achieve it anyway, but lets concentrate on getting the kernel to start first so remove all that. Set ProvideConsoleGop = YES Config ACPI patches cleaned. Set ProvideConsoleGop = YES No go. config.plist opencore-2019-10-15-101333.txt Edited October 15, 2019 by obus Link to comment Share on other sites More sharing options...
UefiBooter Posted October 15, 2019 Share Posted October 15, 2019 (edited) are you using DEBUG versions of OpenCore.efi and its companion BootX64.efi ? how are you loading OpenCore too ? Edited October 15, 2019 by UefiBooter Link to comment Share on other sites More sharing options...
obus Posted October 15, 2019 Share Posted October 15, 2019 (edited) 39 minutes ago, UefiBooter said: are you using DEBUG versions of OpenCore.efi and its companion BootX64.efi ? I presume that but I will download and test again with debug version. 39 minutes ago, UefiBooter said: are you using DEBUG versions of OpenCore.efi and its companion BootX64.efi ? how are you loading OpenCore too ? Sorry my bad. I was using the release version. This is with 100% debug drivers. opencore-2019-10-15-102810.txt Edited October 15, 2019 by obus Link to comment Share on other sites More sharing options...
obus Posted October 15, 2019 Share Posted October 15, 2019 28 minutes ago, UefiBooter said: how are you loading OpenCore too ? What do you mean. I don't get what you mean? Link to comment Share on other sites More sharing options...
UefiBooter Posted October 15, 2019 Share Posted October 15, 2019 do you have it on a usb stick and your choosing to boot that ? Link to comment Share on other sites More sharing options...
obus Posted October 15, 2019 Share Posted October 15, 2019 (edited) 7 minutes ago, UefiBooter said: do you have it on a usb stick and your choosing to boot that ? On harddisk. Clover on USB Edited October 15, 2019 by obus Link to comment Share on other sites More sharing options...
UefiBooter Posted October 15, 2019 Share Posted October 15, 2019 (edited) ok. need to find an easy way to work around the broken DEBUG binary release. you could try the 5.0 DEBUG release i guess. Edited October 15, 2019 by UefiBooter Link to comment Share on other sites More sharing options...
UefiBooter Posted October 15, 2019 Share Posted October 15, 2019 (edited) ok, right you need to add the missing elements that 0.5.1 version now requires specifically Arguments option to Tool items and if you have any items in the Entries both in the Misc section. That will let you proceed a bit further ie it bypasses the ASSERT Edited October 15, 2019 by UefiBooter Link to comment Share on other sites More sharing options...
obus Posted October 15, 2019 Share Posted October 15, 2019 Seems that a bunch of stuff is missing. Could this be firmware related? 00:965 00:002 OCBP: APFS Volume Info is missing 00:967 00:002 OCBP: Blessed file is missing 00:970 00:002 OCBP: Blessed folder is missing 00:972 00:002 OCBP: Predefined <nil> \System\Library\CoreServices\boot.efi is missing - Not Found 00:975 00:002 OCBP: Predefined <nil> \EFI\APPLE\X64\BOOT.EFI is missing - Not Found 00:977 00:002 OCBP: Predefined <nil> \EFI\BOOT\BOOTX64.EFI was found 00:980 00:002 OCB: Filesystem 0 (B2170518) named EFI (Success) has 1 entries 00:985 00:005 OCB: Adding entry 0, external - 0, skip recovery - 0 00:987 00:002 DevicePath - PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(1,GPT,9F4B1F10-9F1E-4ED4-8293-9AA8317A89EE,0x28,0x64000)/\EFI\BOOT\BOOTX64.EFI 00:990 00:002 OCBP: APFS recovery volume handle missing - \EFI\BOOT\ 00:992 00:002 OCB: Adding entry 0 recovery (<null>) - Not Found 00:995 00:002 Scanning got 1 entries 00:997 00:002 Trying to get label from \EFI\BOOT\.contentDetails 01:000 00:002 Trying to get label from \EFI\BOOT\.disk_label.contentDetails 01:002 00:002 Trying to detect Microsoft BCD 01:004 00:002 Entry 0 is EFI at \EFI\BOOT\ (T:0|F:0) 01:007 00:002 Entry 0 is EFI at dp PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(1,GPT,9F4B1F10-9F1E-4ED4-8293-9AA8317A89EE,0x28,0x64000)/\EFI\BOOT\BOOTX64.EFI 01:010 00:002 OCB: Performing OcShowSimpleBootMenu... 0 01:012 00:002 OCB: BootNext has not been found 01:014 00:002 OCB: BootOrder is unavailable - Not Found 01:017 00:002 OCB: Initial default is 0, fallback 06:062 05:044 OCB: Should boot from EFI (T:0|F:0) 06:066 00:003 OCB: Perform boot EFI to dp PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(1,GPT,9F4B1F10-9F1E-4ED4-8293-9AA8317A89EE,0x28,0x64000)/\EFI\BOOT\BOOTX64.EFI (0/0) 06:068 00:002 OCB: Matching <> args on type 0 0 06:071 00:002 ASSERT [OpenCore] /Users/travis/build/acidanthera/OpenCorePkg/UDK/MdePkg/Library/BaseLib/String.c(1076): 3 minutes ago, UefiBooter said: ok, right you need to add the missing elements that 0.5.1 version now requires specifically Arguments option to Tool items and if you have any items in the Entries both in the Misc section. I don't really now if I can follow what you mean Can you elaborate a little bit further please? Link to comment Share on other sites More sharing options...
UefiBooter Posted October 15, 2019 Share Posted October 15, 2019 <key>Tools</key> <array> <dict> <key>Comment</key> <string>BootChimeCfg</string> <key>Enabled</key> <true/> <key>Name</key> <string>BootChimeCfg</string> <key>Path</key> <string>BootChimeCfg.efi</string> </dict> is missing the following <key>Arguments</key> <string></string> add that to each of the 'Tool' options you've added and double check the Changes.pdf each new version of OpenCore as it details the changes one needs to make. Link to comment Share on other sites More sharing options...
obus Posted October 15, 2019 Share Posted October 15, 2019 (edited) 15 minutes ago, UefiBooter said: ok, right you need to add the missing elements that 0.5.1 version now requires specifically Arguments option to Tool items and if you have any items in the Entries both in the Misc section. That will let you proceed a bit further ie it bypasses the ASSERT OK. Done. Argument is in config.plist Tool. 5 minutes ago, UefiBooter said: <key>Tools</key> <array> <dict> <key>Comment</key> <string>BootChimeCfg</string> <key>Enabled</key> <true/> <key>Name</key> <string>BootChimeCfg</string> <key>Path</key> <string>BootChimeCfg.efi</string> </dict> is missing the following <key>Arguments</key> <string></string> add that to each of the 'Tool' options you've added and double check the Changes.pdf each new version of OpenCore as it details the changes one needs to make. Arguments Type: plist string Failsafe: Empty string Description: Arbitrary ASCII string used as boot arguments (load options) of the specified entry. I have added Argument to all my 5 entries but I don't know what to fill the argument with? See attached config. config.plist Edited October 15, 2019 by obus Link to comment Share on other sites More sharing options...
UefiBooter Posted October 15, 2019 Share Posted October 15, 2019 (edited) 7 minutes ago, obus said: OK. Done. Argument is in config.plist Tool. Arguments Type: plist string Failsafe: Empty string Description: Arbitrary ASCII string used as boot arguments (load options) of the specified entry. I have added Argument to all my 5 entries but I don't what to fill the argument with? See attached config. config.plist leave it empty for now , its used for passing arguments to the tools that run ie pass -nomap -nostartup options to Shell.efi. umm Failsafe means if your unsure of the value to set use the Failsafe value. Edited October 15, 2019 by UefiBooter Spelling mistakes :P 1 Link to comment Share on other sites More sharing options...
obus Posted October 15, 2019 Share Posted October 15, 2019 1 hour ago, UefiBooter said: leave it empty for now , its used for passing arguments to the tools that run ie pass -nomap -nostartup options to Shell.efi. umm Failsafe means if your unsure of the value to set use the Failsafe value. do you want me to test again with the new Argument (FailSafe = none) values? Link to comment Share on other sites More sharing options...
UefiBooter Posted October 15, 2019 Share Posted October 15, 2019 (edited) 1 hour ago, obus said: do you want me to test again with the new Argument (FailSafe = none) values? Well you need to follow the instructions and make your config.plist compatible with OpenCore 0.5.1 otherwise how would one expect to make any progress ? Good Luck. Edited October 15, 2019 by UefiBooter Link to comment Share on other sites More sharing options...
obus Posted October 15, 2019 Share Posted October 15, 2019 (edited) 2 hours ago, UefiBooter said: Well you need to follow the instructions and make your config.plist compatible with OpenCore 0.5.1 otherwise how would one expect to make any progress ? Good Luck. Attached and tested config.plist is 100% compatible with OpenCore 0.5.1 and have just the basics drivers and kext enabled for booting. no ACPI patch at all and still no go. Stuck att boot menu with message: ASSERT [OpenCore] /Users/travis/build/acidanthera/OpenCorePkg/UDK/MdePkg/Library/BaseLib/String.c(1076): String != ((void *) 0) Anybody? Any input that could guide me in the right direction is appreciated: opencore-2019-10-15-155211.txt config.plist Edited October 15, 2019 by obus Link to comment Share on other sites More sharing options...
mhaeuser Posted October 15, 2019 Share Posted October 15, 2019 @obus It is a bug in the current DEBUG build documented in the Changelog, this error happens when an "Arguments" field is empty. It does not affect RELEASE or master DEBUG builds 1 Link to comment Share on other sites More sharing options...
Andres ZeroCross Posted October 15, 2019 Share Posted October 15, 2019 28 minutes ago, obus said: Attached and tested config.plist is 100% compatible with OpenCore 0.5.1 and have just the basics drivers and kext enabled for booting. no ACPI patch at all and still no go. Stuck att boot menu with message: ASSERT [OpenCore] /Users/travis/build/acidanthera/OpenCorePkg/UDK/MdePkg/Library/BaseLib/String.c(1076): String != ((void *) 0) Anybody? Any input that could guide me in the right direction is appreciated: opencore-2019-10-15-155211.txt config.plist Try this.. Post the result config.plist Link to comment Share on other sites More sharing options...
obus Posted October 15, 2019 Share Posted October 15, 2019 56 minutes ago, Download-Fritz said: @obus It is a bug in the current DEBUG build documented in the Changelog, this error happens when an "Arguments" field is empty. It does not affect RELEASE or master DEBUG builds Ok so I have to use the release version to test? or should I fill the "arguments" field with something and use my current debug version? Could you please elaborate little more because I need the logs. 44 minutes ago, Andres ZeroCross said: Try this.. Post the result config.plist Thank's for your help. I tested but with the same result. Link to comment Share on other sites More sharing options...
aben Posted October 15, 2019 Share Posted October 15, 2019 Hi OpenCore testers, Unable to get XCPM and X86PlatformPlugin to work with plugin-type, how does one patch KernelXCPM like Clover on OC for i5 Ivy-Bridge, should I be using FakeCPUID and xcpm_bootstrap patches from @PMheart ? Where can I find these kernel patches Link to comment Share on other sites More sharing options...
Pavo Posted October 15, 2019 Share Posted October 15, 2019 5 minutes ago, aben said: Hi OpenCore testers, Unable to get XCPM and X86PlatformPlugin to work with plugin-type, how does one patch KernelXCPM like Clover on OC for i5 Ivy-Bridge, should I be using FakeCPUID and xcpm_bootstrap patches from @PMheart ? Where can I find these kernel patches Ivy-Bridge doesn't support XCPM 1 Link to comment Share on other sites More sharing options...
aben Posted October 15, 2019 Share Posted October 15, 2019 (edited) 2 hours ago, Pavo said: Ivy-Bridge doesn't support XCPM Sorry I mean't XCPM patches for Ivy-Bridge to get X86PlatformPlugin and PM to work on 10.13.6 using OC. I hope @PMheart can help me find Ivy bootstrap patches for 10.13.6 since Clover spoiled me with KernelXCPM auto patches Edit: Finally fixed XCPM kernel panic by using @PMheart's AppleX86PlatformPluginInjector with patched MAC-BoardID, Ivy-Bridge now running flawless on OC 0.5.1 with full Power Management. Thanks to all developers and OpenCore Team for this amazing bootloader. Goodbye Clover, you were good to me. Cant wait to experience the future OpenCore development in action. Edited October 15, 2019 by aben Link to comment Share on other sites More sharing options...
Recommended Posts