Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8,887 posts in this topic

Recommended Posts

chris1111
chris1111
Posted
Posted
4 hours ago, LIMITANT said:

I don't use Windows.. I'm sorry .. this is the best result i got for my configuration... 

Let me test some other values and report back 

 

Try : 67843 or 71939

I tested both and they don't work, thank you for your effort very much appreciate.

Anyway it seems to be complicated to hide a simple EFI partition...

Link to comment
Share on other sites
Ellybz
Ellybz
Posted
Posted (edited)
23 hours ago, chris1111 said:

any one knows how to hide EFI partition in boot picker ?

Here's my method to find the proper ScanPolicy value:

 

1- Let’s say your config has Windows (NTFS) & MacOS (APFS + HFS ) on Satas & NVMe Drives, but you’d also like to scan your USB for OS Installation purpose.

1- Enter your Calculator in MacOS ( to enter Programmer mode press: CMD+3 )

this window will appear:

1958382772_ScreenShot2020-09-04at11_34_03.thumb.png.1ae6e2f5a6257516833c4ce77e662d33.png

 

2- Without entering any numeric values, click on the desired binary value ( in front of the arrow ) to switch it from 0 to 1 ( 0= False / 1=True )

By doing so the big Hex value will appear:

result.thumb.png.5dcf66838e5b0ac3cf85e2e1730255d2.png

Now we have:

FSL + DL+ APFS+HFS + NTFS+SATA+SAS/Mac NVMe +NVMe+USB. = 0x2B0B03

0 + 1 + 8 + 9+ 11 + 16 + 17 + 19 + 21 = 0x2B0B03

( Note that if the ESP Value = 0 ( Bit10 ) no EFIs will be scanned.)

 

3- Converting that HEX value to Decimal ( Any Hex Converter will do )

0x2B0B03 -> 2820867

 

Your New Scan Policy is now: 2820867

 

Done!

Edited by Ellybz
  • Like 3
  • Thanks 3
Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted
6 minutes ago, Ellybz said:

Here's my method to find the proper ScanPolicy value:

 

1- Let’s say your config has Windows (NTFS) & MacOS (APFS + HFS ) on Satas & NVMe Drives, but you’d also like to scan your USB for OS Installation purpose.

1- Enter your Calculator in MacOS ( to enter Programmer mode press: CMD+3 )

this window will appear:

1958382772_ScreenShot2020-09-04at11_34_03.thumb.png.1ae6e2f5a6257516833c4ce77e662d33.png

 

2- Without entering any numeric values, click on the desired binary value ( in front of the arrow ) to switch it from 0 to 1 ( 0= False / 1=True )

By doing so the big Hex value will appear:

result.thumb.png.5dcf66838e5b0ac3cf85e2e1730255d2.png

Now we have:

FSL + DL+ APFS+HFS + NTFS+SATA+SAS/Mac NVMe +NVMe+USB. = 0x2B0B03

0 + 1 + 8 + 9+ 11 + 16 + 17 + 19 + 21 = 0x2B0B03

( Note that if the ESP Value = 0 ( Bit10 ) no EFIs will be scanned.)

 

3- Converting that HEX value to Decimal ( Any Hex Converter will do )

0x2B0B03 -> 2820867

 

Your New Scan Policy is now: 2820867

 

Done!

Wow :w00t: I will test :moil: thank you

  • Like 2
Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted (edited)
3 hours ago, obus said:

I think this is what you are looking for:

ScanPolicy > 722179

Thanks @obus Try that EFI Partition is show again; windows is visible that's ok

@Ellybz 2820867 EFI is hide but also windows and USB installer

Edited by chris1111
Link to comment
Share on other sites
Ellybz
Ellybz
Posted
Posted (edited)
6 hours ago, chris1111 said:

Thanks @obus Try that EFI Partition is show again; windows is visible that's ok

@Ellybz 2820867 EFI is hide but also windows and USB installer

That is extremely odd. This is what I have with ScanPolicy 2820867. Everything works as intended. ( USB, Windows, etc..)

Have you tried with PickerMode "Builtin"? Maybe it's an Icon/OpenCanopy issue?

Are you using Windows OS in a separate drive or with Bootcamp?

I have windows in a separate drive.

If you're not using bootcamp, I highly suggest to add a custom entry for Windows.

272487499_ScreenShot2020-09-25at10_35_15.thumb.png.1056bd22034a9a3025e0cf84fdebbf08.png

25173901.thumb.png.cbfcc770bb00ab3bb38116798fd3d51d.png

PS: I forgot to fix that "Preboot" name entry, easy fix. In my system I also deleted the recovery partition from Mojave. Too many recovery entries IMO.

 

Edited by Ellybz
  • Like 4
Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted
2 hours ago, Ellybz said:

That is extremely odd. This is what I have with ScanPolicy 2820867. Everything works as intended. ( USB, Windows, etc..)

Have you tried with PickerMode "Builtin"? Maybe it's an Icon/OpenCanopy issue?

Are you using Windows OS in a separate drive or with Bootcamp?

I have windows in a separate drive.

If you're not using bootcamp, I highly suggest to add a custom entry for Windows.

 

 

PS: I forgot to fix that "Preboot" name entry, easy fix. In my system I also deleted the recovery partition from Mojave. Too many recovery entries IMO.

 

Thank you

I don't use bootcamp my windows 10 is installed in UEFI on a 250 g SSD separate

I will do another more in-depth test but I find it very complicated to simply hide or see partitions :angel_not:

Link to comment
Share on other sites
Ellybz
Ellybz
Posted
Posted
25 minutes ago, chris1111 said:

Thank you

I don't use bootcamp my windows 10 is installed in UEFI on a 250 g SSD separate

I will do another more in-depth test but I find it very complicated to simply hide or see partitions :angel_not:

I sent you a PM.

Link to comment
Share on other sites
droples
droples
Posted
Posted (edited)
1 hour ago, luky35 said:

I have installed Catalina 10.15.7.

The Efi OC start menu only shows me the Macintosh SSD boot disk icon.
No Recovery and no Tools icons?

 

  Reveal hidden contents

imageproxy.php?img=&key=c17464ef1b1b51c71400194600_CatalinaOC.thumb.png.b555cfb57b9cb07efa4466017899955e.png

These are not OC issues. See your config. Maybe you should press the magic key2.png.9096c225c4bca538e799db8a966526c8.png

 

Edited by droples
  • Like 2
Link to comment
Share on other sites
Thegn
Thegn
Posted
Posted (edited)

**** Edit ****

**** I just removed the entries under UEFI/ReservedMemory, and got rid of the error. ****

 

Hi,

I've just updated from OC 6.1 (an August build), to tonights build of 6.2. I'm getting the following fault message before the disk icons show when booting OC:

"OCS: No schema for Type at 1 index, context <ReservedMemory>

OCS: No schema for Type at 1 index, context <ReservedMemory>

 

There are two default items in the example config under the UEFI/ReservedMemory section, HD3000 memory errata and a fix for black screen on Lenovo Thinkpad, but those are not Enabled.

 

Does anyone her have an idea what the issue is and can help me?

 

I can boot with this error, but I would like to fix it. My config with 6.2 is the same as for 6.1 with the new stuff from 6.2 added with it's default settings.

 

Cheers,

Edited by Thegn
Link to comment
Share on other sites
Emanuele-1998
Emanuele-1998
Posted
Posted
On 7/6/2020 at 9:59 AM, ghost8282 said:

Greetings to all!

I'm seeing that things are moving faster with kernel collection and kext injection, after spending the whole day yesterday trying to install (install, not restore) big sur on qemu without success, I tried again today, since I saw that the work is still in development (as always) and some commits were added, to lilu too.

Kernel patching and kext injection seem to work, apart from manually pointing the boot picker after the first and second reboot I'm able to have the installation screen to show and proceed.

I'm stuck after the second reboot, when you choose to boot from "Preboot", with "No port micro restart (we don't support SMC on this platform)": after this it reboots and loops.

 

IMG_20200706_091543.thumb.jpg.3fcd6ddcece4e0641f281015bcc1034b.jpg

 

I will follow the progress on github, I don't know if you are already aware of the issue and/or if you have a solution or not, just to report my trials.

On another chinese forum a user said he solved the issue by pointing oc to clover, pointing to mac os (???????????) --> I don't like it at all. (edited, as it's a non sense..)

 

Thanks for your hard work, you are the best!

 

 

I have the same error as the post, with the new build of Lilu 1.4.6+ and VirtualSMC 1.1.5+ the bootargs vmscgen = 1, no longer needed. I'm upgrading to Big Sur beta 8 @Andrey1970

  • Like 1
Link to comment
Share on other sites
obus
obus
Posted
Posted (edited)

Could anybody out there tell me if it's possible to boot macOS from a connected thunderbolt drive with OpenCore? Has two GC-TITAN RIDGE card with flashed @DSM2 firmware (https://forums.macrumors.com/threads/testing-tb3-aic-with-mp-5-1.2143042/page-37?post=28291766#post-28291766 )

Booting from the same external thunderbolt disk is working perfect on my MacBookPro.

Spoiler

673873350_Screenshot2020-09-27at21_23_08.thumb.png.7569aa0244c3d37877324f4aa9a8e534.png1371612995_Screenshot2020-09-27at21_14_45.thumb.png.90286771fc3a4e3e6209d537f7edb6a6.png1688990594_Screenshot2020-09-27at21_14_03.thumb.png.c187fd0a083f1af28fd61f2c73ff16c5.png

 

OpenCore does not detect the disk in BootPicker. Drivers are loaded according to system preferences and the disk is showing up in "Startup disk" as a bootable disk. Is it something with ScanPolicy settings or could it be a driver problem?

Any ideas?

 

 

Edited by obus
  • Like 1
Link to comment
Share on other sites
obus
obus
Posted
Posted (edited)
8 hours ago, meaganmargaret said:

I guess you could say maybe I'm booting via USB, but the drive is directly connected via an Apple TB cable to a TB port on the Titan Ridge, and it, and other drives connected this way boot just fine.

Is your boot disk listed here? If soo you are booting trough USB 3.1.

Spoiler

1292280547_Screenshot2020-09-28at10_06_24.thumb.png.bc94ad7b05fd850c56d5e177fa9cc829.png

 

Edited by obus
Link to comment
Share on other sites
joevt
joevt
Posted
Posted
20 hours ago, obus said:

Could anybody out there tell me if it's possible to boot macOS from a connected thunderbolt drive with OpenCore? Has two GC-TITAN RIDGE card with flashed @DSM2 firmware (https://forums.macrumors.com/threads/testing-tb3-aic-with-mp-5-1.2143042/page-37?post=28291766#post-28291766 )

Booting from the same external thunderbolt disk is working perfect on my MacBookPro.

  Reveal hidden contents

673873350_Screenshot2020-09-27at21_23_08.thumb.png.7569aa0244c3d37877324f4aa9a8e534.png1371612995_Screenshot2020-09-27at21_14_45.thumb.png.90286771fc3a4e3e6209d537f7edb6a6.png1688990594_Screenshot2020-09-27at21_14_03.thumb.png.c187fd0a083f1af28fd61f2c73ff16c5.png

 

OpenCore does not detect the disk in BootPicker. Drivers are loaded according to system preferences and the disk is showing up in "Startup disk" as a bootable disk. Is it something with ScanPolicy settings or could it be a driver problem?

Any ideas?

In the EFI Shell, does the NVMe or SATA or whatever controller that is in the Thunderbolt drive exist in the list of PCI devices? If not, then you need some different BIOS settings or a new EFI Thunderbolt driver that someone would have to create. It's possible the flashed ROM that makes it work better for macOS stops it from working with EFI or Windows.

 

15 hours ago, meaganmargaret said:

 Hmm......maybe I'm not understanding, but I can boot macOS from my TB Titan Ridge with OC - the drive is in a 10G USB adapter and connected directly to a TB port on the Titan Ridge. 

 

Just as an aside, I tried flashing my TR card, but didn't like the result so I flashed it back to factory.  So, my TB card is not flashed, and it's been at factory for quite a while now.

 

I do have some settings set in the Asus bios to make sure the Thunderbolt Titan Ridge can boot external drives.

 

I guess you could say maybe I'm booting via USB, but the drive is directly connected via an Apple TB cable to a TB port on the Titan Ridge, and it, and other drives connected this way boot just fine. 

 

I boot this way all the time - this is the way I boot into my Big Sur install, for instance.

You are talking about USB. The USB controller of an unflashed Thunderbolt controller usually works fine. Booting from a Thunderbolt drive requires PCI enumeration of the connected Thunderbolt devices while in EFI which may require some new EFI code.

 

 

  • Like 1
Link to comment
Share on other sites
nmano
nmano
Posted
Posted (edited)

I Fix build Lilu.kext Errors

 

Before

399712772_ScreenShot2020-09-30at3_31_36AM.thumb.png.c9c5f9f6e572b375178e7d5ddb4ef8df.png

 

PLEASE DOWNLOAD

https://github.com/acidanthera/MacKernelSDK

You have to setting KERNEL_FRAMEWORK_HEADERS

600607778_ScreenShot2020-09-30at3_56_04AM.thumb.png.8880705b4c757bc352f38a9fbb9848e4.png

 

I appreciate Lilu Team.

Edited by nmano
Link to comment
Share on other sites
obus
obus
Posted
Posted (edited)
13 hours ago, Emanuele-1998 said:

Hi, I have already installed Big Sur beta 3 but can't upgrade to beta 8

You need to enable SIP (System Integrity Protection) to download update for macOS Big Sur 11 beta.

Boot into Recovery --> terminal--> command: csrutil enable

Edited by obus
Changing Disable to Enable
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...