Jump to content
8755 posts in this topic

Recommended Posts

For the heck of it, i tried to load/boot up OC on my Lenovo T420 (sandy bridge) - which has been working on clover for about 8 years now.

 

- but after OC inits.  i get a black screen??? and not not see any boot options etc.

i used the Ivy Bridge profile. so in essense never even got to fun part of making it work.

 

anyone have an full EFI repo with config.plist for Sandy Bridge I can try to see where I went wrong. the Sanity Checker for the config.plist came back all green? 

 

 

22 hours ago, Pene said:

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!

Hi @Pene, I can confirm that neither combination works on my rig. Should I open a new issue in bug tracker or just append my log files to the old (closed) issue?

 

Edited by dgsga

@Download-Fritz Man, you are clear (I also deleted all posts) but you guys released early preview today? Am I missing something? I thought if you released today, we can ask something? Then you must be much clear, like this: "Even we released do not ask anything about OpenCanopy"?

Edited by telepati

@telepati That is more or less what I did:

 

17 hours ago, Download-Fritz said:

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.

 

From the docs of this release:

 

Quote

WARNING: OpenCanopy is currently considered experimental and is not recommended for everyday use.

 

This is software is not only months away from being stable, it also is at the very bottom of the priority list. Ask whatever you feel like asking, but stop pinging, especially vit deserves to not be bothered for a single day after the last few weeks.

  • Like 5
39 minutes ago, dgsga said:

Hi @Pene, I can confirm that neither combination works on my rig. Should I open a new issue in bug tracker or just append my log files to the old (closed) issue?

Too bad, closed one should be fine. No reason to open a new one.

  • Like 1
2 hours ago, telepati said:

@Download-Fritz OK. I understood what you mean and I apologize to both of you. :blush:

 

In any case .. i had similar issue .. Used OC Builder pull and compile latest versions of all that it pulls and compiles and OpenCanopy works just fine ... Not sure what difference this made for me between compiling this way and copying the OCBinaryData over to the release version...  Didn't spend that much time looking into it to be fair.

41 minutes ago, Cass67 said:

 

In any case .. i had similar issue .. Used OC Builder pull and compile latest versions of all that it pulls and compiles and OpenCanopy works just fine ... Not sure what difference this made for me between compiling this way and copying the OCBinaryData over to the release version...  Didn't spend that much time looking into it to be fair.

OCBuilder has been updated to reflect their new folder structure. Check for updates in the app.

it seems someone was listening at opencore and made some positive for a while I was impressed the scripts almost succeded in make a full blown mac it was actually parsing each and every attempt to parse and regroup based upon an ouput of a fallen ssdt driver wow that a major improvement or something but it still stopped short of a full blown success here is a pic please let me know where it failed I was so far impresed with my russian friends who borrowed every english word in computer jargon gave it a russian ending and talk in it like it is there own one should see them go talk in some sort of english speak sudo jargon it was russian yet it wasnt  I just visited their website 

IMG-1269.jpg

10 hours ago, markl18 said:

can some kind sole explain this error because I cant get out of it openruntime v3 not 10 

I had this error today right after updated to 0.5.7. In my case, I replaced "FwRuntimeServices.efi" with "OpenRuntime.efi" in my "Drivers" folder, and finally use Propertree's SnapShot to update config.plist. After this, I can boot into the system without the openruntime error. BTW, 0.5.7 boot a lot faster than 0.5.6 on my desktop. 

Edited by Andrew1263
×
×
  • Create New...