OpenCore General Discussion

[MacNB]

7 hours ago, CappeXXIII said:

iMac di Gabriele.ioreg

 

But now i realized that when i am connected with the vga it sees another monitor on the right. how can i disable it? I need only VGA, DVI and HDMI can be disabled

iMac di Gabriele.ioreg

 

This is now becoming off-topic as it's no longer related to OpenCore in this thread.

But I'll answer.

GeForce 2xx series GPU's only really supported two outputs.

The VGA output is a mirror of either the HDMI or the DVI depending on the manufacturer.

So it appears as if the VGA connector is working.

 

Regarding your issue, I do not understand what you mean by "it sees another monitor on the right" if you only have ONE screen attached.

I suggest you continue this discussion in the other thread where you have been replying and I sent you a new SSDT as it's no longer related to OpenCore.

[MacPete]

Hi everyone,

I'm new to Hackintoshs but am doing my best to get things running on my box.  I've add my machine specs to my profile so hopefully they'll show up below this post.

After following the guide (https://dortania.github.io/OpenCore-Install-Guide/) to create a bootable USB my machine is crashing immediately after selecting "macOS Base System (External)"

 

The error says:

Quote

 

ACPI: 12 ACPI AML tables successfully acquired and loaded

panic(cpu 8 caller 8xfffffff8818f8776f): Kernel trap at 8xffffff881dda12ee, type 14=page fault, registers:

 

I've attached a copy of my EFI directory and a photo of the error I see.

 

I've looked at the trouble shooting page (https://dortania.github.io/OpenCore-Install-Guide/troubleshooting/troubleshooting.html) and found the section (https://dortania.github.io/OpenCore-Install-Guide/troubleshooting/troubleshooting.html#kernel-panic-on-invalid-frame-pointer)

 

For me, changing DevirtualiseMmi, EnableWriteUnprotector, RebuildAppleMemoryMap and SyncRuntimePermissions had no effect.  Changing SetupVirtualMap to false resulted in me getting stuck on EndRandomSeed (https://dortania.github.io/OpenCore-Install-Guide/troubleshooting/troubleshooting.html#stuck-on-endrandomseed).

 

The troubleshooter for this problem suggests changing the same properties as for the 'invalid frame pointer' issue.  Changing anything except SetupVirtualMap has no effect and I continue to get stuck.

 

I'd greatly appreciate any tips people can give me on what to try next.

 

Regards,

Peter

 

EFI.zip

[fuzzylogic]

I would like to ask the dev regarding sealed snapshots, since Big Sur does not boot of a "live", vol

how does this impact:-

updating of OpenCore, since we have a sealed snapshot?

updating of Kernel Extensions, again since we do not boot off a live vol ?

 

 

When I try to boot into recovery I have only the option of disc util and or

re install mac os big sur

currently using Opencore 061

Current Os big sur Beta4

Edited August 13, 2020 by fuzzylogic

[kapian]

On 4/5/2020 at 11:01 AM, thientruongdx said:

I use OpenCore on

Motherboard Chipset Intel Kaby Point Q270, Intel Kaby Lake-S
CPU i5-7600T

 

 

 

 

 

 

 

进bios，关闭兼容模式即可

[polkaholga]

19 hours ago, fuzzylogic said:

I would like to ask the dev regarding sealed snapshots, since Big Sur does not boot of a "live", vol

how does this impact:-

updating of OpenCore, since we have a sealed snapshot?

updating of Kernel Extensions, again since we do not boot off a live vol ?

 

 

When I try to boot into recovery I have only the option of disc util and or

re install mac os big sur

currently using Opencore 061

Current Os big sur Beta4

 

To update opencore and/or kexts you just need to mount the appropriate EFI partition, where your OpenCore EFI resides

 

For editing /S/L/E or user/L/E kexts read fusion71au's post here.... 

 

Edited August 14, 2020 by polkaholga

[Matgen84]

Hi Guys

 

Sorry for my stupid question  : my BIOS (Z390 mobo) show up 'OpenCore' instead of 'UEFI:KingSton...' (my USB stick). After several Reset NVRAM, the OpenCore mention disappears.

How to avoid 'Opencore' in BIOS Boot list ? Thanks for helping me.

[Matgen84]

10 minutes ago, eSaF said:

I don't think it matters that much, whether the named disk shows up or Opencore as long as you can boot the disk or if multi-booting, any other other OS, but if you don't like the name Opencore, you will need to make the change in the BIOS and enable the name disk and disable the name Opencore from the boot list. This is not permanent though. because when ever you clean the NVRAM, the name Opencore will appear in the boot list again. If there is a fix to permanently to remove the name OC I don't know and quite frankly, I don't think it is a problem one should concern them selves with, the mere ability to boot BS should be sufficient especially how much the OS has changed from the previous ones before it.

 

@eSaF

I work (test) with several bootloader on my USB key: this is the reason why 'Opencore' show up in BIOS, is annoying for me  (I don't want to use multi-boot because I've got 3 separated disk)

[DocXavier]

2 hours ago, Matgen84 said:

Hi Guys

 

Sorry for my stupid question  : my BIOS (Z390 mobo) show up 'OpenCore' instead of 'UEFI:KingSton...' (my USB stick). After several Reset NVRAM, the OpenCore mention disappears.

How to avoid 'Opencore' in BIOS Boot list ? Thanks for helping me.

Probably you have Misc -> Security -> BootProtect -> Bootstrap in your config. For me was even worst because I had Opencore in the list and blocked bios access... I changed it to Misc -> Security -> BootProtect -> None and OC disappeared from list.

 

I hope this can help you¡¡¡

Edited August 14, 2020 by DocXavier

[jimbojingle]

Hi,

 

I am running OpenCore 0.6.0 on a Gigabyte Z490 Vision D with a Radeon RX 5700XT Graphics Card.

 

I have a weird problem that I am unable to solve so would be grateful for any tips.

 

I accidentally renamed my Catalina NVMe Disk as ‘parallels’ and when I noticed the Catalina NVMe Disk showed up as ‘parallels’ on the OpenCore GUI Boot Screen, I changed its name back to ‘Catalina’.

 

However, even after several NVRAM resets and a load BIOS Defaults and a Clear CMOS, it’s still showing up as ‘parallels’ on the Boot Screen GUI.

 

Also, Big Sur Disk, shows up in OpenCore Boot GUI as 'Preboot'.

 

Where are these 'strange' names coming from in the GUI when the actual Disk names are different?

 

Any ideas how I can rectify this ‘cosmetic’ problem as I can not boot Catalina automatically even though the Startup Disk is set to Catalina.

 

Thanks in advance.

Edited August 15, 2020 by jimbojingle

[kjp4756]

I have a fat32 formatted usb flash drive with BaseSystem.dmg and BaseSystem.chunklist in a folder called com.apple.recovery.boot.  When I have a scanpolicy of 0 I can boot from it.  With a scanpolicy of 19857667 opencore doesn't see the recovery dmg.  19857667 is the default with the addition of USB.  What else do I need for it to work?  There isn't an option for fat32.

[fuzzylogic]

11 hours ago, Matgen84 said:

Hi Guys

 

Sorry for my stupid question  : my BIOS (Z390 mobo) show up 'OpenCore' instead of 'UEFI:KingSton...' (my USB stick). After several Reset NVRAM, the OpenCore mention disappears.

How to avoid 'Opencore' in BIOS Boot list ? Thanks for helping me.

https://dortania.github.io/OpenCore-Install-Guide/config.plist/coffee-lake.html#acpi

protect UefiServices= YES under booter

ProtectUefiServices

YES

Needed on Z390 system

 

 

[fuzzylogic]

14 hours ago, polkaholga said:

 

To update opencore and/or kexts you just need to mount the appropriate EFI partition, where your OpenCore EFI resides

 

For editing /S/L/E or user/L/E kexts read fusion71au's post here.... 

 

Thanks for your kind help

[Matgen84]

7 hours ago, fuzzylogic said:

https://dortania.github.io/OpenCore-Install-Guide/config.plist/coffee-lake.html#acpi

protect UefiServices= YES under booter

ProtectUefiServices

YES

Needed on Z390 system

 

 

 

Thanks. I've already this values in my config.plist. ASAP, I test with BootProtect set to NO as @DocXavier says.

[d5aqoep]

Kinda noob question... Is there a way to unseal Big Sur after it has been sealed by the initial installation?

[iCanaro]

1 hour ago, mifjpn said:

Dear Acidanthera members
This is a serious problem.
Does OpenCore pass the data such as ACPI, etc. as the original BIOS when selecting another OS?
On my computer, when I booted Windows from OpenCore, I could never see the BIOS screen again.
My friend's Windows also shuts down in a few hours when booting from OpenCore.
OpenCore is a great program.
However, with the current movement of OpenCore, it seems as if every OS in the world had to be macOS.
And we can practically only choose Open Core to run Big Sur.
Therefore, I feel very sad that the wonderful OPEN CORE is in an oligopoly.
To all the members of the team, we sincerely request that OpenCore will be great.

 

better to refrain from starting windows with OC
even at best when it starts it correctly, it still passes values that many motherboard builders utilities do not function properly, not recognizing the system
Start windows with function keys or with Clover and use OC to start macOS only
my 2 cents

[iCanaro]

I've been testing OC since the first beta and on several hacks... apart from the first beta that regularly started windows, since then I still have to figure out what it takes to start windows without any acidathera injection or bootcamp. So I decided not to waste more time to figure it out, until the first release stable to study, or the advent of a fork type NDK that you can use alternatively.

[kocoman]

any fast way to boot between igfxframe=0x12345678 vs no igfxframe?

[MacNB]

5 hours ago, mifjpn said:

Thank you for your warm and keen opinions and comments.

What I mean is that OpenCore is both a boot loader and a boot selector. So, although it is very good as a boot loader for macOS, it does not have a basic function as a boot selector.

I think that means changing the way of thinking. Not everyone wants the OZMOSIS-like movement.

Great deveropers and coders are doing their best in their day-to-day efforts.

All I want is just the usual behavior as a boot selector.

Currently I mainly use Catalina so I use Clover as the main boot loader.

If there is a problem with Open Core、We can install GRUB2 from Windows, so I　select it by chainloading at.

Try using GRUB as a boot manager

 

I'm sorry I have to disagree with you.

OC has a fairly good boot selector. 

It has a simple text based builtin boot selector and it has an API to add an external boot selector.

And there's an example of an External boot selector called OpenCanopy that was added by the OC team.

Yes OpenCanopy is still in-developent and will improve further when it's complete.

That boot selector works almost like a native Mac boot selector.

You can even use Mac like hot keys e.g. OPT key during boot to display the boot picker - just like a real Mac

 

Here's what OpenCanopy displays on my system (Hack 4):

 

 

I have not had a problem booting Windows from OC. My Windows version is Retail and was fully activated BEFORE OC was ever installed.

It is still activated after booting it via OC. On that system, I don't even have a DSDT and Windows boots fine.

 

Here's another system I have that is LEGACY system that does NOT even have UEFI but with OC's Duet Legacy boot, I can still use OpenCanopy and boot Windows 10 (Hack 2):
 

 

OK, on this legacy system I could NOT initially boot Windows because it would fail with the ACPI_BIOS_ERROR blue screen of death.

That's because the DSDT that I had which was being injected to Windows by OC did not allow for Windows booting (e.g. _OSI checks).

I have completely modified that DSDT with liberal use of _OSI guarding and I can now boot Windows 10 without any issues and no problem with Activation. That version of Windows has OEM (DELL) Licensing.

I'll get around writing a guide on how I modified that DSDT to enable Windows booting via OC hopefully.

 

I can even use macOS's Start-up Disk selector from System Preferences to select an OS to boot and OC takes care of booting that OS (both on UEFI & Legacy BIOS systems).

 

So I am failing to understand your issue is with OC's boot selection.

 

EDIT: If you have an issue with booting Windows, then it has nothing to do with the Boot Selector but with the core function of OC - which was by design. That design choice the Devs made to boot macOS just like a Mac and allow other OS's to boot the way a Mac does.

Edited August 15, 2020 by MacNB

[Sniki]

Hi guys,

 

Dell Optiplex 9020:

i7-4790

 

When attempting to boot, get's stuck at this screen:

 

Could this be related to KASLR (Slide value) or RTC ?

 

Default Booter Quirks from sample.plist (as they work like that on 90% of hacks we tried so far).

[XLNC]

9 minutes ago, Антико said:

Dear experts. Please help me solve the problem with installing Big Sur. I haven't been able to install it on a separate disk partition for several weeks. Catalina with this config is started, I try to start installation of Big Sur-panic. Where am I wrong? Perhaps you could show me the right way - I would be very grateful!

config.plist

opencore-2020-08-16-100220.txt

Enable IncreasePciBarSize in kernel -> quirks

[ainsleyclark]

Hi there.

 

Did a fresh install for big sur. I’m aware that they are playing around with the naming of the ‘preboot volume’ name but I have two disks showing up in opencore for one boot drive.

 

One named preboot, which boots into Mac fine, the other macOS (the big sur drive name) doesn’t boot, just hangs at x86 architecture or something.

 

This didn’t happen when I upgraded but just a fresh install. Anyone know of a fix?

my scan policy is set to 0.

 

Thanks.

[Tiem]

On 8/15/2020 at 6:12 AM, eSaF said:

Getting into the BIOS from Windows is also mentioned, I can't see the significance of this, does it really matter which OS allows you to get into the BIOS as long as you can get in there and are we talking about a Legacy or UEFI system?

No. The BIOS is the BIOS. It supersedes any OS. The BIOS is at the lowest level.

What people are complaining about is booting into an OS using OC. OC is a chain loader (or boot loader depending on your verbiage). It will pass information to the OS before booting. These can include manufacturer name and other details that help whatever OS you're loading, be it Windows or Linux or macOS to run. Because OC is made for macOS, passing critical info such as ACPI patches, manufacturer name and other low level details to other OSes, like Windows, can cause problems. Windows expects to boot from it's boot loader or on a real Mac, from Bootcamp, which is set up by Apple to provide a nice clean compartment for it to run smoothly. Even then, you lose some functionality with Bootcamp, such as the low level safe mode services that end up spinning on a loop.

 

The NDK fork works around this by passing any critical patches (DSDT, etc.) only to macOS, leaving the booting of other OSes like Windows relatively clean. So far, the native OC project does not provide this functionality.

 

This does also depend on how you're hack is set up. The more patches and hacks you used, the more they may adversely affect Windows from loading properly.

 

If you want to load Windows clean, just hold F12 and load it directly from your board's boot loader, which precedes other loaders like OC or grub or whatever.

[ltooz_audis]

Ok, I finally fixed the dreaded HP Post Error RTC Bios mismatched due to OpenCore boot loader, actually someone emailed me reminding me about this problem. OK it's fixed and a simple one too.

Cheers,

Louis

 

Ch

[ainsleyclark]

Anyone know of a fix fo NVMe kernel panics?

Tried pretty much everything including the NVMefix.kext, not sure if it's big sur related?

[polkaholga]

On 8/15/2020 at 11:23 AM, d5aqoep said:

Kinda noob question... Is there a way to unseal Big Sur after it has been sealed by the initial installation?

 

i've posted a link to fusion71au's post in another forum about snapshots, etc... around a dozen posts above your question

read it and the answers will jump at you..

 

once more the link

https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/?page=27&tab=comments#comment-2729935