Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8755 posts in this topic

Recommended Posts

obus
obus
Posted
Posted (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 by obus
UefiBooter
UefiBooter
Posted
Posted (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 by UefiBooter
obus
obus
Posted
Posted

 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?

UefiBooter
UefiBooter
Posted
Posted

        <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.

 

obus
obus
Posted
Posted (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 by obus
UefiBooter
UefiBooter
Posted
Posted (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 by UefiBooter
Spelling mistakes :P
  • Like 1
obus
obus
Posted
Posted
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?

UefiBooter
UefiBooter
Posted
Posted (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 by UefiBooter
obus
obus
Posted
Posted (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 by obus
Andres ZeroCross
Andres ZeroCross
Posted
Posted
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

obus
obus
Posted
Posted
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.

aben
aben
Posted
Posted

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 

Pavo
Pavo
Posted
Posted
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

  • Like 1
aben
aben
Posted
Posted (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 by aben
Allan
Allan
Posted
Posted
2 hours ago, aben said:

 

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.

Hey can you share your OpenCore folder?

 

Thanks

obus
obus
Posted
Posted
14 hours 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

Tested with the Release version 0.5.1 with "FailSafe empty Arguments string" and got the same result as previous test, stuck at boot menu.

OpenCore is loading but can't find any APFS/recovery volume  to boot on. If I put in my USB recovery pen drive I use for my other two (fully working) rigs when I want to do a recovery, the RecoveryImage.dmg pops up in boot menu and start loading but fail before boot into recovery.

 

Is this a problem with my firmware in my HP laptop or with my config.plist, or could it be a problem with OC or maybe a bug in OC?

I feel Iv'e get no serious response in this matter. People just more and less telling me that this is a "noob" problem with my config.plist (read the manual and so on.) It might be a part of the problem but even if I should have some problem with my configuration my rig should at least boot up and then crash. I'm not an expert but I'm not a noob neither. I have two fully working rigs with OpenCore but I never had experienced a problem like this. Clover is working flawlessly on this laptop and I'm quite sure that that should be the case with OpenCore too, if I can solve this boot problem.

 

I attach the last log with Debug version and my used config.plist.

 

Is there any of you devs how could try to shed some lights over my problem?

config.plist

opencore-2019-10-15-155211.txt

mhaeuser
mhaeuser
Posted
Posted (edited)

@obus I'm not spending much time to read user reports right now because I want to use my time off on the OC crypto stack

"FailSafe empty Arguments string", what is this supposed to be? it must *not* be empty in DEBUG, currently

Try with non-empty "Arguments" and current DEBUG, or leave the field alone and compile master DEBUG (bug fixed there)

Edited by Download-Fritz
  • Like 1
obus
obus
Posted
Posted (edited)
5 hours ago, Download-Fritz said:

@obus I'm not spending much time to read user reports right now because I want to use my time off on the OC crypto stack

"FailSafe empty Arguments string", what is this supposed to be? it must *not* be empty in DEBUG, currently

Try with non-empty "Arguments" and current DEBUG, or leave the field alone and compile master DEBUG (bug fixed there)

8.6 Entry Properties

  1. Arguments
    Type: plist string
    Failsafe: Empty string
    Description: Arbitrary ASCII string used as boot arguments (load options) of the specified entry.

This is what I mean with "FailSafe empty Arguments string".

Try to read what I men instead of treat me like an idiot!

 

Secondely above is not my problem. The problem is that I can't boot with OpenCore if you care to read what I've wrote previously . 

Edited by obus
mhaeuser
mhaeuser
Posted
Posted

@obus Let me clarify. You are asking me for help, and I am on limited time to dedicate for this kind of request, so I will read, think and respond as long or short as I see fit to suit my available resources, not more and not less. I have explained the bug, you have not avoided the bug with obvious and explained ways, but instead re-provide the same kind of useless log in every post. Yet, I had been patient, I told you the possible ways again, and yet I do not see the log in the fashion it had been requested. I'm not sure what you are expecting from me, but whatever it is, you are not going to get it. I will not dedicate a single second more to this until we have an actually useful log.

  • Like 2
  • Haha 1
UefiBooter
UefiBooter
Posted
Posted

@obus, the configuration document is correct, but there is a bug in 0.5.1-DEBUG release.

 

to work around the bug either add some dummy value into each of your <Arguments> entries such as "Bypass" as this will prevent the ASSERT stop you are seeing.

 

or you can build the source from the repo as the bug has been fixed.

 

easiest for you is to add dummy values into each of the Argument entries as indicated above.

 Share
Go to topic listing
×
×
  • Create New...