OpenCore General Discussion

[chris1111]

Something was wrong with OC O.6.1 

0.6.1 / 3 august 2020 boot Mojave but latest 0.6.1 not boot, I can not provide any log because its an instant ShutDown

Catalina and Big Sur no issue with latest OC

 

EDIT*** Fix with

<key>SecureBootModel</key>

<string>Disabled</string>

 

Edited August 12, 2020 by chris1111

[Cyberdevs]

Hi guys,

I don't know it it has been discussed or not but I couldn't find anything regarding this matter so my question is: Is there any way to patch DoNotSeal option in Big Sur installation on the fly with OpenCore? Is that even possible to do it without having to edit the UpdateOptions.plist to prevent macOS to seal APFS Volume during installation?

[MacNB]

8 hours ago, CappeXXIII said:

Thanks you very much. Now i can run in recovery without nv_disable and without any glitch, so i reinstalled macos for removing all clover junk. It reboots and without any problem it finished the second part of installation but at the third (and last reboot) i get black screen with working mouse and when I press a key the screen flashes. I leave in the attachment a gif to explain it better.

 

Try different video output connector. 

Looks like default login port is on another connector.

 

Before you try to reinstall macOS, did the existing macOS boot correctly and provide video output ?

 

BTW, there was no reason to reinstall macOS just to remove Clover.

You can remove Clover by just following these instructions.

 

[CappeXXIII]

Just now, MacNB said:

Try different video output connector. 

I tried HDMI and VGA, now i will try also DVI.

 

Just now, MacNB said:

Looks like default login port is on another connector.

This is most likely because if I move the mouse cursor to the right disappears, as if in fact there was another display.

 

Just now, MacNB said:

Before you try to reinstall macOS, did the existing macOS boot correctly and provide video output ?

Same things, for that I reinstalled.

[pitrysha]

33 minutes ago, 5T33Z0 said:

Yesterday, I upated OpenCore to the latest build (0.6.1 Nightly) which has a new Security option called "SecureBootModel" which is set to "Default". In my case I had to disable it otherwise the system wouldn't boot. Normally it should not interfere the boot process if apple secureboot is disabled but in my case it did. Just in case, somebody else is facing issues after updating.

From the "Differences" PDF:

 

 

The system boots with the latest build.
Kernel patches are no longer loaded.

[Kevin...]

Can anyone pls share OC 0.6.1 KabyLake efi folder...bcu I made and tried so many time my Efi folder but every time I’m stucked on different karnel panic, apfs module start, don’t show macOS partition in 3 stage and my other problems...so I can’t find any way to...so pls if some have successfully boot with OC 0.6.1 Big Sur beta 4 kabylake pls share your efi folder 

[MacNB]

12 hours ago, xKaoSx said:

My full Efi folder in link

 

 

 

I replied to you in that separate thread to Inject Nvidia. Try it.

2 hours ago, CappeXXIII said:

I tried HDMI and VGA, now i will try also DVI.

 

This is most likely because if I move the mouse cursor to the right disappears, as if in fact there was another display.

 

Same things, for that I reinstalled.

 

It's a shame you reinstalled as your original OS had booted and you could have logged in remotely from another system to get the new IOREG.

[CappeXXIII]

Just now, MacNB said:

It's a shame you reinstalled as your original OS had booted and you could have logged in remotely from another system to get the new IOREG.

I know, it's my mistake. I configurated new macOS using nv_disable=1, enabled Remote Screen and removed nv_disable. So i rebooted and connected using VNC but i can see the same thing: a black screen with working pointer.

Edited August 12, 2020 by CappeXXIII

[OneLife2000]

hi guys

how to fix this issue related to ocvalidate utilitie

how to appendite it to config.plist

[SavageAUS]

hi guys
how to fix this issue related to ocvalidate utilitie
how to appendite it to config.plist

I told you how in a different thread.
Please don’t double post.
Drag and drop ocvalidate into terminal then drag and drop your config.plist from finder into terminal window and press enter.


Sent from my iPhone using Tapatalk

[OneLife2000]

thanks man

[MacNB]

1 hour ago, CappeXXIII said:

I know, it's my mistake. I configurated new macOS using nv_disable=1, enabled Remote Screen and removed nv_disable. So i rebooted and connected using VNC but i can see the same thing: a black screen with working pointer.

 

Try the attached SSDT.

I changed the boot-display to @0,AAPL,boot-display.

SSDT-GFX0.aml

 

Also, post your IOREG once you have booted with nv_disable=1.

Edited August 12, 2020 by MacNB

[CappeXXIII]

15 minutes ago, MacNB said:

 

Try the attached SSDT.

I changed the boot-display to @0,AAPL,boot-display.

SSDT-GFX0.aml

 

Also, post your IOREG once you have booted with nv_disable=1.

I don't know how to thank you! Now it works very well. Thanks again.

[MacNB]

47 minutes ago, CappeXXIII said:

I don't know how to thank you! Now it works very well. Thanks again.

 

You are welcome.

 

Please post your IOREG.

[obus]

Hi Guys.

After upgrading OC from 0.5.9 to 0.6.0 I've got this weird boot problem. With OC 0.5.9 and 0.6.0 beta everything works flawlessly. Have I missed something. 

Can't figure out what is wrong. Is there anybody out there having any clue?

Attached is my config.plist

 

config.plist

[Deanor30]

Hi Folks,

   I am trying to get Macos running on a Toshiba Satellite L50-C-22l using opencore 0.6. I have been able to get Catalina & BigSur public Beta running on a Dell 3020 with a I5 Haswell CPU and GT710 gpu and everything is working without issue with overall performance and boot time improving when switching from Clover to Opencore. So as a secondary project I though I would try to get same running on the Toshiba Satellite L50-C-22l using Dorthania's laptop guide for Broadwell and I am getting no panics. I created the SSDT's using SSDTtime and double checked the config.plist using the sanity checker. As you can see from the image below I am getting to the installer screen in BigSur but it is very distorted. I am getting the same when booting to Catalina. I have looked at a lot of forums on here and other Hachintosh sources and while this seems very common relating to the HD 5500 from Yosemite to Catalina, Nobody has posted an actual fix.

 

I have tried:

Applying framebuffer patches in the config.plist.

Changing UEFI -> Resolution in the config.plist.

All kexts & Drivers are the latest versions.

 

I cannot enable the legacy or CSM boot mode on this laptop as otherwise the USB will not boot.

There are no settings in bios to assign memory to GPU.

 

Someone posted that putting the laptop to sleep and then waking the system can fix this issue  but it has not worked for me and it seems a poor fix even if it did work. I have attached my EFI so any fixes or suggestions would be welcome.

 

EFI.zip

 

[Matgen84]

20 minutes ago, obus said:

Hi Guys.

After upgrading OC from 0.5.9 to 0.6.0 I've got this weird boot problem. With OC 0.5.9 and 0.6.0 beta everything works flawlessly. Have I missed something. 

Can't figure out what is wrong. Is there anybody out there having any clue?

Attached is my config.plist

config.plist

 

Hi
 

Do you update your kexts to the latest version! You can check your config.plist via  Dortania Guide for Skylake

[obus]

8 minutes ago, Matgen84 said:

 

Hi
 

Do you update your kexts to the latest version! You can check your config.plist via  Dortania Guide for Skylake

 

Kext updated and config.plist checked and updated according to Dortania guide/Skylake X/W. 

Any other ideas?

[Matgen84]

11 minutes ago, obus said:

 

Kext updated and config.plist checked and updated according to Dortania guide/Skylake X/W. 

Any other ideas?

 

Sorry, no ideas   PlatformInfo section is not correct (I think) : for Generic, use GemSMBIOS (Dortania Guide) to complete values. Imac17,1 is recommended for your CPU.

Edited August 12, 2020 by Matgen84

[CappeXXIII]

2 hours ago, MacNB said:

 

You are welcome.

 

Please post your IOREG.

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

[obus]

14 minutes ago, 5T33Z0 said:

OCConfigCompare says you are missing a Key in your Config. I don't know if it matters, though. You can copy it over from the sample.plis

 

That missing key isn't the problem (could be deleted according to Dortania Guide).

Thank's anyway.

[feartech]

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

VGA has not been used on mac's for a very long time, over 10 years..

[CappeXXIII]

1 minute ago, feartech said:

VGA has not been used on mac's for a very long time, over 10 years..

Yeah I know  but it's working fine, I only need to disable DVI and HDMI

[obus]

2 hours ago, obus said:

Hi Guys.

After upgrading OC from 0.5.9 to 0.6.0 I've got this weird boot problem. With OC 0.5.9 and 0.6.0 beta everything works flawlessly. Have I missed something. 

Can't figure out what is wrong. Is there anybody out there having any clue?

Attached is my config.plist

 

Problems solved. Deleted NVMeFix.kext from config.plist and kext folder. Now booting as it should.

Edited August 12, 2020 by obus

[Tiem]

10 hours ago, 5T33Z0 said:

Yesterday, I upated OpenCore to the latest build (0.6.1 Nightly) which has a new Security option called "SecureBootModel" which is set to "Default". In my case I had to disable it otherwise the system wouldn't boot. Normally it should not interfere the boot process if apple secureboot is disabled but in my case it did. Just in case, somebody else is facing issues after updating.

From the "Differences" PDF:

Try setting the value for Misc/Security/SecureBootModel to your SMBIOS. For example, if you're running MacPro7,1, set it to j160.

 

As was said earlier, the new secure boot features are in a state of flux. If you have debug logs, please provide them so bugs can be crushed. If not, hang tight till the devs expand on the feature. It is currently not complete.