Jump to content
8755 posts in this topic

Recommended Posts

38 minutes ago, Morpheus NS said:

 

OK, I've now tested every possible scenario (I think)...

 

 

1. Your HfsPlus.efi and VBoxHfs.efi give me exactly the same results:

a) no FakeCPUID - boot picker - choice of partition - kernel panic from the picture below

b) with ANY FakeCPUID (most of the time 0x0306A0 and 0x0106E0 (which is the only one that ever worked for me), but others too) - boot picker - choice of partition - black screen no matter how much time I wait

 

2. HfsPlus.efi that I was using previously (from OCBuilder, much larger in size):

a) with OR without FakeCPUID it gives me my motherboard logo on a dark background and nothing else, no picker

 

This is the kernel panic I get with your HfsPlus.efi and VBoxfs.efi without FakeCPUID:

151582818_Screenshot2020-04-05at15_02_55.thumb.png.b676a261e9ec9f13621c85afcc6181b4.png

 

I've included bootstrap and AVX patch from the link you provided, tested with and without them but nothing changes. This is the current version of my config.plist, I switched to OpenCore 0.5.7: config.plist (I enable/disable patches depending on whether I use FakeCPUID or not, but I tried othe combinations as well).

 

Everything works with Clover, even Power Management is fine without FakeCPUID

 

1628784496_Screenshot2020-04-05at15_15_45.thumb.png.b262cc9fc7f84e765697e4312f1ca4a3.png

hi you have to use ssdttime to produce oc.plist which you have to add to your regular plist to get some of those ism files to work properly also when you get there you will find out that  you python is not setup prperly so good luck with that

Has anyone else had any problems with Windows drive detection with recent commits of Opencore? With commit eceb36f (OcBootManagementLib: Rename BOOTCAMP Windows to Windows, on 13th March) everything works fine but if I upgrade to the latest commit and then select the Windows drive I get the blue recovery screen with a message saying 'the PC needs to be repaired, an unexpected error has occurred'. If I boot the same drive direct from the bios boot selector the system loads fine. I have windows 10 installed on a separate drive so it doesn't pollute the Mac side of things. Reverting back to the old OC version corrects this issue. Any ideas?

Edited by dgsga

Unfortunately, it didn't help. I've tried using debug version of OpenCore and every time it halts at the same place:

 

73:704 00:099 OCSMC: SmcReadValue Key 4D535463 Size 1
73:795 00:090 OCSMC: SmcReadValue Key 4D534163 Size 2

 

From Google search, it seams to have something to do with KASLR, so I tried adding slide=0 (should be the correct value) to my boot arguments, it didn't help either.

 

I am too stubborn to give up, but I am running out of ideas... thank you for your help so far. :)

My Opencore boot into macos very well but it will panic when I boot into recovery partition and any bootable installer for macOS. What should I do to fix this?
I tried changing between hfsplus.efi and VBoxHfs.efi (from AppleSupportPkg) but it still didn't work out.
My OC folder here: https://www.dropbox.com/s/vdjubjpgbrpls8p/OC.zip?dl=0
914081092_IMG_20200405_212503(1).thumb.jpg.68a930aca1156d65027d1ff41f0204d0.jpg

@vit9696 I have been following bugtracker #491 to try to solve my Windows 10 boot failure and have found that if I revert commit f963012 (the 4K section alignment in Open Runtime) it fixes the failure on my rig. I did try the latest commit with the latest version of mtoc (949.0.1) but couldn't get past the BSOD with any combination of booter quirks. Am I missing something here?

Edited by dgsga
21 minutes ago, dgsga said:

but couldn't get past the BSOD with any combination of booter quirks. Am I missing something here?

If you are compiling as of now, after the check for correct mtoc has been enforced, and are still experiencing issues with Windows booting, please confirm this, and if it is the same case, follow vit's debug instructions for this problem and post the resulting files in the GitHub issue. Thanks!

Edited by Pene
  • Like 2

Why would you guys bloat this thread with OpenCore 0.5.7 issues "of work in progress stuff" when you all "crystal" clearly see that commits are being added constantly during the day like in minutes and they are working on that  ?

 

They have been working hard most of the day as i followed the commits, Let them do their valuable work that they do for free for all of us, show them some respect.

 

No offence but it's really getting hard to also see valuable posts/solution to real problems, having to scroll pages and pages everyday for such repeated things over and over again.

  • Like 8
14 hours ago, Matgen84 said:

 

Take a look to  configuration.pdf

I took a look and it says to edit the contentDetails file for the boot entries. Unfortunately still doesn't tell me where to look for it or as another user said to create it but I dont' know where this should be put in after it's created nor is there a sample somewhere I think.

@telepati Look I/we get pinged on several channels several times a day. And the more of those are disposable things like "bug reports" about explicitly development branches literally during active development (talking about minutes, not even hours or days), the more appealing it is to not react to pings of any sort at all. I do not want to hear any more "bug reports" about OpenCanopy, especially not of its development branch, until it's mature for daily use.

7 minutes ago, Download-Fritz said:

@telepati Look I/we get pinged on several channels several times a day. And the more of those are disposable things like "bug reports" about explicitly development branches literally during active development (talking about minutes, not even hours or days), the more appealing it is to not react to pings of any sort at all. I do not want to hear any more "bug reports" about OpenCanopy, especially not of its development branch, until it's mature for daily use.

Well Said, its very frustrating!

It changes all the time now, wait for the final version of 0.5.7 or use OCBuilder to get the currently available version of OpenCore with its drivers including OpenRuntime.efi. Just choose Release (without kexts) and the folder you want your files to be saved - click Build and wait. :) Or just use 0.5.6 with FwRuntimeServices instead, there aren't many visible changes, they work the same.

Edited by Morpheus NS

Opencore stops at this error

Motherboard Chipset Intel Kaby Point Q270, Intel Kaby Lake-S
CPU i5-7600T
Ram 2x8gb buss 2400

My OC 0.5.6

https://drive.google.com/file/d/1OyvND1UjT-2tlC3fN_bi6kiK0Gr5HFty/view?usp=sharing

Pls help me

nILG51E.jpg

Edited by thientruongdx
6 minutes ago, thientruongdx said:

 

Please. If you want users to help you, put your config detailed in your signature (CPU, MB, RAM, Graphics, etc.) Oc Version, macOS version used

Edited by Matgen84
×
×
  • Create New...