Jump to content

OpenCore General Discussion


dgsga
8,888 posts in this topic

Recommended Posts

1856306056_ScreenShot2020-04-26at10_02_04PM.thumb.png.6a500f6219517810beaa3509abe18c16.png

when i added BootProtect to None i lost my windows 10 partition from boot menu i readed many times Differences.pdf i couldn't understand clearly

nobody answered me clearly about bootProtect

where i put \EFI\OC\Bootstrap\Bootstrap.efi into config

config.plist

Link to comment
Share on other sites

38 minutes ago, anmool said:

1856306056_ScreenShot2020-04-26at10_02_04PM.thumb.png.6a500f6219517810beaa3509abe18c16.png

when i added BootProtect to None i lost my windows 10 partition from boot menu i readed many times Differences.pdf i couldn't understand clearly

nobody answered me clearly about bootProtect

imageproxy.php?img=&key=c17464ef1b1b51c7where i put \EFI\OC\Bootstrap\Bootstrap.efi into config

config.plist

 

Why don't you just delete Misc->Security->BootProtect entry in the config.plist.

Also while you are at it, delete :

Misc->Entries->1 (there's nothing the Configuration.pdf that tells you to put an Entry like that)

 

Link to comment
Share on other sites

44 minutes ago, MacNB said:

 

Why don't you just delete Misc->Security->BootProtect entry in the config.plist.

Also while you are at it, delete :

Misc->Entries->1 (there's nothing the Configuration.pdf that tells you to put an Entry like that)

 

just i deleted BootProtect=None and custom entries

no luck same behavier windows partition disappeared

but with old compiled windows partition appeared before BootProtect

Edited by anmool
Link to comment
Share on other sites

hi I got this message

this version of mac os x is not supported on this platform

reason yoga 2

 

is that finale there is no recourse help

I stuck the old smbios and it went through 

 

Edited by markl18
Link to comment
Share on other sites

bool SMCSuperIO::start(IOService *provider) {
  SYSLOG("ssio", "starting up SuperIO sensors");
   
  if (!IOService::start(provider)) {
  SYSLOG("ssio", "failed to start the parent");
  return false;
  }
   
  auto ioreg = OSDynamicCast(IORegistryEntry, this);
   
  dataSource = detectDevice();
  if (!dataSource) {
  SYSLOG("ssio", "failed to detect supported SuperIO chip");
  return false;
  }

 

whoever wrote this code can you help me get through it I get stuck right here unsupported cpu unsupported pch

Link to comment
Share on other sites

1 hour ago, Kynyo said:

OCS: no schema for protocols at 5 index!

 

System from signature. It boots perfectly but this error its spawned for 1 second. OC sanity checker says that config.plist its setup correctly.


They changed the name. The new updated name is in the manual under Docs.

 

To Mark that happened to me once turning on the AppleMemoryRemap quirk. Though could be anything. 

  • Like 1
Link to comment
Share on other sites

52 minutes ago, davidm71 said:


They changed the name. The new updated name is in the manual under Docs.

 

To Mark that happened to me once turning on the AppleMemoryRemap quirk. Though could be anything. 

no it didnt work but I got this file I dont know why

OP #1 of total 2, console - Success
Current mode 0, max mode 7, FB: A0000000, FBS: 15F9000
Current: 3200 x 1800, pixel 1 (0 0 0 0), scan: 3200
0: 3200 x 1800, pixel 1 (0 0 0 0), scan: 3200
1: 640 x 480, pixel 1 (0 0 0 0), scan: 640
2: 800 x 600, pixel 1 (0 0 0 0), scan: 800
3: 1024 x 768, pixel 1 (0 0 0 0), scan: 1024
4: 1280 x 1024, pixel 1 (0 0 0 0), scan: 1280
5: 1600 x 1200, pixel 1 (0 0 0 0), scan: 1600
6: 1920 x 1440, pixel 1 (0 0 0 0), scan: 1920
New 0 <-> 0: max mode 7, FB: A0000000, FBS: 15F9000 - Success
New 0 <-> 0: 3200 x 1800, pixel 1 (0 0 0 0), scan: 3200


GOP #2 of total 2, auxiliary - Success
Current mode 0, max mode 7, FB: A0000000, FBS: 15F9000
Current: 3200 x 1800, pixel 1 (0 0 0 0), scan: 3200
0: 3200 x 1800, pixel 1 (0 0 0 0), scan: 3200
1: 640 x 480, pixel 1 (0 0 0 0), scan: 640
2: 800 x 600, pixel 1 (0 0 0 0), scan: 800
3: 1024 x 768, pixel 1 (0 0 0 0), scan: 1024
4: 1280 x 1024, pixel 1 (0 0 0 0), scan: 1280
5: 1600 x 1200, pixel 1 (0 0 0 0), scan: 1600
6: 1920 x 1440, pixel 1 (0 0 0 0), scan: 1920

 

maybe someone can explain what is this supposed to be
New 0 <-> 0: max mode 7, FB: A0000000, FBS: 15F9000 - Success
New 0 <-> 0: 3200 x 1800, pixel 1 (0 0 0 0), scan: 3200

Link to comment
Share on other sites

On 4/26/2020 at 9:22 PM, davidm71 said:

 

Ok Will do. Thanks.

 


only this word -flto caused  windows to boot and disappear
i removed this word -flto from OpenCorePkg.dsc and compiled worked
i solved my problem removing this word -flto
windows icon appearing and booting worked fine like before
close this conversation
mark solved

Link to comment
Share on other sites

4 minutes ago, anmool said:


only this word -flto caused  windows to boot and disappear
i removed this word -flto from OpenCorePkg.dsc and compiled worked
i solved my problem removing this word -flto
windows icon appearing and booting worked fine like before
close this conversation
mark solved

 

Good for you. Well done.

 

That flag (-flto) is a compiler flag. What made you choose to delete that one ? 

What was your theory ?

You should not close the conversation because if you know that this is a build BUG then it should be reported to the Devs on the Bugtracker.

  • Like 1
Link to comment
Share on other sites

17 minutes ago, MacNB said:

 

Good for you. Well done.

 

That flag (-flto) is a compiler flag. What made you choose to delete that one ? 

What was your theory ?

You should not close the conversation because if you know that this is a build BUG then it should be reported to the Devs on the Bugtracker.


Deleting -oz for me trouble occurred for starting windows
Deleting -flto for me, no trouble occurred for starting windows
i have no issue deleting this word -flto
i double checked worked fine

test it yourself

Link to comment
Share on other sites

4 minutes ago, anmool said:


Deleting -oz for me trouble occurred for starting windows
Deleting -flto for me, no trouble occurred for starting windows
i have no issue deleting this word -flto
i double checked worked fine

test it yourself

 

I think you misunderstand me.

Did just randomly go around deleting flags until you found something that worked ????

Do you know what that flag does ???

 

There was a reason that the developers put that flag (-flto) there.

Fixing it for yourself is not a solution since that flag will ALWAYS be there.

Then, next time you wish to build another version of OC, you will have to remember to delete it...everytime !

The only way to make that fix permanent for you is to Fork your own Branch of OC and in your own branch you delete it.

The other (proper) way is to report the problem (NOT here because it will not necessarily get fixed).

That way, if it is a problem, it will be fixed for everyone.

 

Link to comment
Share on other sites

1 hour ago, ameenjuz said:

orry guys 

my username is ameenjuz in github account

in insanelymac my name is anmool

sorry engilsh is not my native english therefore  i couldn't fully answered of them

 

my username is zijun_he in github account.

Recommend the https://github.com/daliansky/OC-little project of our community to you, it may be helpful for you to check the ACPI patch. Although these may cause great difficulties for you to read ...

Edited by lanzaozijun
Link to comment
Share on other sites

1 hour ago, lanzaozijun said:

my username is zijun_he in github account.

Recommend the https://github.com/daliansky/OC-little project of our community to you, it may be helpful for you to check the ACPI patch. Although these may cause great difficulties for you to read ...

thanks i will read but this is chinse language

how to read

  • Like 1
Link to comment
Share on other sites

Link to comment
Share on other sites

×
×
  • Create New...