Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8,887 posts in this topic

Recommended Posts

uglyJoe
uglyJoe
Posted
Posted

@Proxary

 

Try FwRuntimeServices.efi with  

	<key>Booter</key>
	<dict>
		<key>Quirks</key>
		<dict>
			<key>AvoidRuntimeDefrag</key>
			<true/>
			<key>DisableVariableWrite</key>
			<false/>
			<key>DiscardHibernateMap</key>
			<false/>
			<key>EnableSafeModeSlide</key>
			<false/>
			<key>EnableWriteUnprotector</key>
			<true/>
			<key>ForceExitBootServices</key>
			<false/>
			<key>ProtectCsmRegion</key>
			<false/>
			<key>ProvideCustomSlide</key>
			<false/>
			<key>SetupVirtualMap</key>
			<true/>
			<key>ShrinkMemoryMap</key>
			<false/>
		</dict>
	</dict>

And to get the apple back, set ProvideConsoleGop=TRUE

Link to comment
Share on other sites
uglyJoe
uglyJoe
Posted
Posted (edited)

Hi, I am trying to boot linux 

		<key>Entries</key>
		<array>
			<dict>
				<key>Name</key>
				<string>LibreElec</string>
				<key>Comment</key>
				<string>VDR Media Client</string>
				<key>Enabled</key>
				<true/>
				<key>Path</key>
				<string>PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0x1,0x0)/HD(1,GPT,886ea49d-fb01-4685-ada6-842ce476367f,0x2000,0x100000)/\EFI\BOOT\syslinux.efi</string>
			</dict>
		</array>

or refind 

		<key>Entries</key>
		<array>
			<dict>
				<key>Name</key>
				<string>Refind</string>
				<key>Comment</key>
				<string>Not signed for security reasons</string>
				<key>Enabled</key>
				<true/>
				<key>Path</key>
				<string>PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0x0,0x0)/HD(1,GPT,df9f014d-e07b-4cae-a8b2-0b80f9f06600,0x28,0x64000)/\EFI\Refind\refind.efi</string>
			</dict>
		</array>

I am working with to two different hacks and on both I added the efi files via bcfg boot... to get the Path. Both are working from bios boot menu but from OpenCore I get: 

04:500 00:741 Should boot from Refind (W:0|R:0|F:0)
04:503 00:002 OCB: Perform boot Refind to dp PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(1,GPT,DF9F014D-E07B-4CAE-A8B2-0B80F9F06600,0x28,0x64000)/\EFI\Refind\refind.efi (0/0)
04:505 00:002 OCB: LoadImage failed - Not Found

What's wrong?

Edited by uglyJoe
Link to comment
Share on other sites
uglyJoe
uglyJoe
Posted
Posted
50 minutes ago, Download-Fritz said:

@uglyJoe idk whether your Shell is borked or whatever, but SATA has three operands, it should be SATA(0x0,0xFFFF,0x0)

 

I fixed the path like you said and it works.

syslinux/LibreElec and refind are loading correctly (and I can start macOS from refind).

Thanks a lot!

 

But my shell is not borked because I tried different versions with two pc's and all gives me the path like I used it before.

bcfg simply does not add the 0xFFFF to the path and the firmware does not need it for booting.
  

UEFI Interactive Shell v2.2
EDK II
UEFI v2.31 (American Megatrends, 0x0004028D)

Option: 00. Variable: Boot0080   
  Desc    - Mac OS X
  DevPath - PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,0e24b55c-ac2b-4cbf-aadf-3a13409a3ddd,0x64028,0x1d161920)/VenMedia(be74fcf7-0b7c-49f3-9147-01f4042e6842,b4e5b22b3b8ed24cb3d6c832ed0ae1c8)/\141E13A7-2343-30EF-A414-4E40632F276A\System\Library\CoreServices\boot.efi
  Optional- N
Option: 01. Variable: Boot0001   
  Desc    - UEFI OS
  DevPath - HD(1,GPT,df9f014d-e07b-4cae-a8b2-0b80f9f06600,0x28,0x64000)/\EFI\BOOT\BOOTX64.EFI
  Optional- N
Option: 02. Variable: Boot0000   
  Desc    - Windows Boot Manager
  DevPath - HD(1,GPT,f9933d89-0bd2-4a3a-85ea-4395d6cf0ce8,0x800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi
  Optional- Y
Option: 03. Variable: Boot0003   
  Desc    - UEFI: KINGSTON SA400S37120G
  DevPath - PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0x4,0x0)/HD(1,GPT,ce93fbb9-5aad-4897-ba61-7c9cdee187fd,0x28,0x64000)
  Optional- Y
Option: 04. Variable: Boot0004   
  Desc    - UEFI: ST1000LM024 HN-M101MBB
  DevPath - PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0x5,0x0)/HD(1,GPT,e4409a95-a817-4d06-b9ea-e0b7c60c9e8d,0x28,0x64000)
  Optional- Y
Option: 05. Variable: Boot0005   
  Desc    - UEFI: ST1000LM024 HN-M101MBB
  DevPath - PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0x5,0x0)/HD(4,GPT,73612ed4-ef49-4981-8d6d-7f8ad35e694a,0x745ac548,0x15a840)
  Optional- Y
Option: 06. Variable: Boot0002   
  Desc    - Refind
  DevPath - PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0x0,0x0)/HD(1,GPT,df9f014d-e07b-4cae-a8b2-0b80f9f06600,0x28,0x64000)/\EFI\OpenCore\refind.efi
  Optional- N

  

EFI Specification Revision : 2.31
EFI Vendor                 : American Megatrends
EFI Revision               : 4.653
EFI Build Version          : HermitCrabs-Lab-20151103

The boot option list is:
01. PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,0e24b55c-ac2b-4cbf-aadf-3a13409a3ddd,0x64028,0x1d161920)/VenMedia(be74fcf7-0b7c-49f3-9147-01f4042e6842,b4e5b22b3b8ed24cb3d6c832ed0ae1c8)/\141E13A7-2343-30EF-A414-4E40632F276A\System\Library\CoreServices\boot.efi "Mac OS X"
02. HD(1,GPT,df9f014d-e07b-4cae-a8b2-0b80f9f06600,0x28,0x64000)/\EFI\BOOT\BOOTX64.EFI "UEFI OS"
03. HD(1,GPT,f9933d89-0bd2-4a3a-85ea-4395d6cf0ce8,0x800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi "Windows Boot Manager" OPT
04. PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0x4,0x0)/HD(1,GPT,ce93fbb9-5aad-4897-ba61-7c9cdee187fd,0x28,0x64000) "UEFI: KINGSTON SA400S37120G" OPT
05. PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0x5,0x0)/HD(1,GPT,e4409a95-a817-4d06-b9ea-e0b7c60c9e8d,0x28,0x64000) "UEFI: ST1000LM024 HN-M101MBB" OPT
06. PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0x5,0x0)/HD(4,GPT,73612ed4-ef49-4981-8d6d-7f8ad35e694a,0x745ac548,0x15a840) "UEFI: ST1000LM024 HN-M101MBB" OPT
07. PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0x0,0x0)/HD(1,GPT,df9f014d-e07b-4cae-a8b2-0b80f9f06600,0x28,0x64000)/\EFI\Refind\refind.efi "Refind"

 

Link to comment
Share on other sites
mhaeuser
mhaeuser
Posted
Posted (edited)
19 minutes ago, uglyJoe said:

bcfg simply does not add the 0xFFFF to the path and the firmware does not need it for booting.

DPs are not stored in text format, they are converted. Lack of 0xFFFF means the conversion is screwed, not that the value is "not needed". Which Shell are you using? The only I can recommend is OpenCoreShell, though even it needs more refinement.

 

EDIT: Ah, you use HermitShell... don't

Edited by Download-Fritz
  • Like 1
Link to comment
Share on other sites
rusty-bits
rusty-bits
Posted
Posted (edited)

Here is another tool for building OpenCore from the command line that I'm working on if anyone wants to try it out

 

https://github.com/rusty-bits/OC-tool

 

It updates required packages, builds the files, and copies them into an EFI directory

It also makes the required vault files if you have the RequireVault option set in your config.plist

 

Edited by rusty-bits
remove unnecessary matter from general discussion
  • Like 4
Link to comment
Share on other sites
Erroruser
Erroruser
Posted
Posted
1 hour ago, rusty-bits said:

Here is another tool for building OpenCore from the command line that I'm working on if anyone wants to try it out

 

https://github.com/rusty-bits/OC-tool

 

It updates required packages, builds the files, and copies them into an EFI directory

It also makes the required vault files if you have the RequireVault option set in your config.plist

 

  Reveal hidden contents

 

 

i think i rather stick with this one https://github.com/Pavo-IM/ocbuilder

 

Link to comment
Share on other sites
rusty-bits
rusty-bits
Posted
Posted (edited)
On 8/24/2019 at 2:48 PM, errorexists said:
On 8/24/2019 at 1:38 PM, rusty-bits said:

Here is another tool for building OpenCore from the command line that I'm working on if anyone wants to try it out

 

https://github.com/rusty-bits/OC-tool

 

It updates required packages, builds the files, and copies them into an EFI directory

It also makes the required vault files if you have the RequireVault option set in your config.plist

 

i think i rather stick with this one https://github.com/Pavo-IM/ocbuilder

 

I tried that one, but I didn't like it much

-It wants administrator privileges, but I'm not sure why

-It pulls and builds everything, whether you are using it in your EFI or not, makes it a bit slow

-It builds Release, NoOpt, and Debug every time, whether you want them all or not, also makes it a bit slow

-It doesn't make the vault files, I like the RequireVault option, has saved me a couple of times

-It doesn't seem to make a logfile anywhere, but I may have missed that

-It doesn't make an EFI folder that I can just drop in my EFI partition and reboot to try it out

 

Anyways, that's some of the reasons why I wanted to make a simple command line tool that grabs only what you tell it and builds it into a bootable EFI directory

I still need to add on ACPI file handling, not a priority for me yet since I don't use them, but it might be nice to have

And a NoOpt option as well, right now I just have a release and debug option

Also I need to include the Tools folder as well, it's nice to be able to boot into OpenCoreShell

That's next on my agenda

Edited by rusty-bits
strikeout incorrect comments
Link to comment
Share on other sites
Proxary
Proxary
Posted
Posted

Hello guys I have successfully  updated my opencore and my settings and now I can boot Without osxfixdrv2.efi them I have removed it but I have only VirtualSMC.efi and all the files from applesupportpkg but when I try to boot I have a panic error but i don’t know from what I hope the are Can fix the problem here a picture as appendix 

image.jpg

Link to comment
Share on other sites
Erroruser
Erroruser
Posted
Posted
24 minutes ago, rusty-bits said:

I tried that one, but I didn't like it much

-It wants administrator privileges, but I'm not sure why

-It pulls and builds everything, whether you are using it in your EFI or not, makes it a bit slow

-It builds Release, NoOpt, and Debug every time, whether you want them all or not, also makes it a bit slow

-It doesn't make the vault files, I like the RequireVault option, has saved me a couple of times

-It doesn't seem to make a logfile anywhere, but I may have missed that

-It doesn't make an EFI folder that I can just drop in my EFI partition and reboot to try it out

 

Anyways, that's some of the reasons why I wanted to make a simple command line tool that grabs only what you tell it and builds it into a bootable EFI directory

I still need to add on ACPI file handling, not a priority for me yet since I don't use them, but it might be nice to have

And a NoOpt option as well, right now I just have a release and debug option

Also I need to include the Tools folder as well, it's nice to be able to boot into OpenCoreShell

That's next on my agenda

i think @Pavo would explain that better when he gets the chance

Link to comment
Share on other sites
Sniki
Sniki
Posted
Posted (edited)

How to solve the problem with Haswell MSR Lock on Laptops so i can boot with OC ?

 

Is there a kernel patch or quirk like there is on clover for this aside from having to mod the bios and remove it ?

 

@vit9696 @PMheart any suggestions ?

Edited by "Sniki"
Link to comment
Share on other sites
Pavo
Pavo
Posted
Posted
16 hours ago, rusty-bits said:

-It wants administrator privileges, but I'm not sure why

-It pulls and builds everything, whether you are using it in your EFI or not, makes it a bit slow

-It builds Release, NoOpt, and Debug every time, whether you want them all or not, also makes it a bit slow

-It doesn't make the vault files, I like the RequireVault option, has saved me a couple of times

-It doesn't seem to make a logfile anywhere, but I may have missed that

-It doesn't make an EFI folder that I can just drop in my EFI partition and reboot to try it out

 

I still need to add on ACPI file handling, not a priority for me yet since I don't use them, but it might be nice to have

Also I need to include the Tools folder as well, it's nice to be able to boot into OpenCoreShell

- It needs administrative privileges, because it checks to see if you have the build tools such as nasm and mtoc are installed and if not, it uses those privileges to install them for you automatically.

- It pulls only the drivers, kexts repos that are commonly used.

- It builds only Release versions.

- It adds all the Utility files that you would need if you need to make vault files. Which is done separately yes. 

- A log file is only made if there is any errors. No reason to make a log file if there is no errors.

- It makes a complete EFI folder that can be dropped into your ESP upon build complete. All you have to do is make your config.plist file.

- All the ACPI files are included in the completed build folder.

- It also includes the ClearNVRAM, MSRCheck and OpenCoreShell in the Tools folder inside the EFI folder upon completing the build.

  • Like 1
Link to comment
Share on other sites
rusty-bits
rusty-bits
Posted
Posted
4 hours ago, Pavo said:

- It needs administrative privileges, because it checks to see if you have the build tools such as nasm and mtoc are installed and if not, it uses those privileges to install them for you automatically.

[snip]

- All the ACPI files are included in the completed build folder.

- It also includes the ClearNVRAM, MSRCheck and OpenCoreShell in the Tools folder inside the EFI folder upon completing the build.

Hey @Pavo

Thanks for the reply. Sorry for appearing critical of ocBuilder, the point I was making to @errorexists is that ocBuilder isn't the tool for me. I pretty much live in the terminal even when I'm not remoted in. I wouldn't know the first thing about creating a GUI app.

Your app was one of the inspirations I had for trying to create my own command line tool to build an EFI which is currently a work in progress. I'd love your critique of it if you have time.

 

I tend to shy away from things than need admin privileges. I try to put binaries into /usr/local/bin when possible to avoid the need for admin. As for ACPI and the Tools folder, I'm well aware that ocBuilder takes care of those, the point was that my tool doesn't yet.

 

My tool definitely won't be for everyone. Some people don't like the command line or don't know how to install build tools. That's not a feature I'm ever going to add.

I thought it would be a fun challenge to see if I could make a command line tool that will read the config.plist and then build a complete EFI folder based on it.

 

Anyways, thanks again for the reply, and thanks for all your work! :thanks_speechbubble:

  • Like 2
Link to comment
Share on other sites
STLVNUB
STLVNUB
Posted
Posted
22 minutes ago, rusty-bits said:

I thought it would be a fun challenge to see if I could make a command line tool that will read the config.plist and then build a complete EFI folder based on it.

 

 

good job 

  • Thanks 1
Link to comment
Share on other sites
Sniki
Sniki
Posted
Posted (edited)
1 hour ago, NorthAmTrans said:

@sniki you should add your hardware to your signature.

Thanks for pointing that out, added my hardware.

 

But im more concerned about my current issue, i read the Configuration.pdf but can't seem to find a reason why i have a kernel panic related to my CPU.

 

Managed to fix everything recently into all my other hardware, it's just this kernel panic that i cannot figure out why it is happening.

Edited by Snikii
Link to comment
Share on other sites
NorthAmTrans
NorthAmTrans
Posted
Posted

@Snikii of course! 

 

A couple things. Rename patches are frowned on with OC. Someone here with a more articulate answer can fill in the blanks here but the short of it all is that they cause problems and should be avoided. I would go through and figure out which ones are actually necessary and then find some help here about how to make or find a patch for them. 

 

I don't know much about laptops here but for pure lucks sake try setting LegacyEnable to YES.

 

You should join the InsanelHack Discord. There is a channel there for OpenCore Laptops. Best of luck to ya. Report back with some progress!

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...