Jump to content

Scan Policy Not Doing It's Job on 0.9.4 DEV OpenCore-MOD No ACPI


5 posts in this topic

Recommended Posts

 "Scanpolicy has avdverse effects" is not a very helpful problem description.

 

There's an online app for calculating ScanPolicy: https://oc-scanpolicy.vercel.app/

 

If this doesn't work, the fix is getting your SSDT tables in order so that they are acpi-compliant and will work with both macOS and Windows! Because then you don't need modded 3rd party versions of OpenCore!

@eSaF

 

thanks, don't know why this happens.

 

but, my scan policy was set to only show the drives I boot with custom entries:  Windows 11 Pro and Windows 10 Pro so I know which Windows is being selected for boot at the GUI Boot Menu.

 

A few days ago, this broke and the GUI shows 4 entries:  Windows, Windows, Windows 11 Pro, Windows 10 Pro.

Then when selecting "Windows 11 Pro", no boot.  Selecting "Windows" booted.

 

Map in Shell of all the drives copy to Entries, reboot. No luck.

 

Scan Policy set to 0 every Icon booted from GUI. 

 

Something is borked here.  Fix please.

 

 

@eSaF

 

2687747 < this fixed it.

 

Thanks! ;)

1 hour ago, cankiulascmnfye said:

 "Scanpolicy has avdverse effects" is not a very helpful problem description.

 

There's an online app for calculating ScanPolicy: https://oc-scanpolicy.vercel.app/

 

If this doesn't work, the fix is getting your SSDT tables in order so that they are acpi-compliant and will work with both macOS and Windows! Because then you don't need modded 3rd party versions of OpenCore!

 

@cankiulascmnfye

 

Thanks.  Done that. 

The fix is the Scan Policy and it somehow stopped working, whereas it was working.

 

So with the NEW Version of OC-MOD which has the ability to bypass ACPI tables that aren't complaint --NOTE this is a Hacky-- hence means patching and none are really compliant,

so we resort to this thing called "Scan Policy".  Which was as I mentioned afore, working just fine.  Thus it is a great possibility that in the NEW version something changed in the package.

Which it did. Thus no boot.

 

Had to use UEFI Shell to boot. 

 

Thanks to @eSaF who is very astute and intelligent knew what the deal was. So we fixed with his kind help.

 

 

 

 

39 minutes ago, makk said:

So with the NEW Version of OC-MOD which has the ability to bypass ACPI tables that aren't complaint --NOTE this is a Hacky-- hence means patching and none are really compliant,so we resort to this thing called "Scan Policy".  Which was as I mentioned afore, working just fine.  Thus it is a great possibility that in the NEW version something changed in the package.

Which it did. Thus no boot.

 

You just completely misinterpreted my comment. Let me break down my train of though so you can follow it:

 

1. If your ScanPolicy value is correct…

2. …but doesn't work…

3. …then there's something wrong with this modded version of OpenCore or with your Configuration in  general

4. So therefore you should fix your config and/or switch to the official OpenCore version…

5. …which requires properly written ACPI tables.

 

Finally, an d most importantly: ScanPolicy is unrelated to ACPI tables and boot paramters. It seems to me that you completely over-rate the relvance of ScanPolicy for booting. It does nothing more than limit the listed device types and file systems shown in the BootPicker . It doesn't fix boot if it's broken. If you want to show all possible boot devices, set it to 0.

×
×
  • Create New...