Jump to content
8755 posts in this topic

Recommended Posts

Does anyone know if it is possible to set the macOS partition as the default boot selection in the boot picker on Z390 boards with borked firmware. On my rig the picker always defaults to the first listed volume. I have LegacyEnable set to YES and have nvram.plist loading correctly. Any help here would be much appreciated. Thanks.

Edited by dgsga
1 minute ago, dgsga said:

Does anyone know if it is possible to set the macOS partition as the default boot selection in the boot picker on Z390 boards with {censored} nvram implementation. On my rig the picker always defaults to the first listed volume. I have LegacyEnable set to YES and have nvram.plist loading correctly. Any help here would be much appreciated. Thanks.

system preferences startup select drive

I have something weird, the inject kext (USBPorts.kext, FakePCIID.kext, FakePCIID_Intel_GBx.kext) not load at all, but according to the opencore debug log, the kext loads succuessfully.

This blocks me switch from clover.

opencore log

02:310 00:005 OCB: Matching <> args on type 1 0
02:315 00:004 OCC: Configuring behaviour 2
02:320 00:004 OCC: Setting cc mode 1 -> 1
02:326 00:006 OCABC: Only 246/256 slide values are usable!
02:331 00:004 OCABC: Valid slides - 10-255
02:337 00:006 OCC: Setting cc mode 1 -> 0
02:351 00:013 Trying XNU hook on System\Library\PrelinkedKernels\prelinkedkernel
02:362 00:011 Kext reservation size 8572928
02:816 00:453 Result of XNU hook on System\Library\PrelinkedKernels\prelinkedkernel is Success
02:832 00:016 OC: Read kernel version 19.0.0 (190000)
02:838 00:005 OCAK: algrey - cpu_topology_sort -disable _x86_validate_topology replace count - 1
02:843 00:004 OC: Kernel patcher result 0 for kernel (algrey - cpu_topology_sort -disable _x86_validate_topology) - Success
02:868 00:024 OCAK: PanicKextDump replace count - 1
02:872 00:004 OCAK: Patch success kext dump
02:920 00:047 OC: Prelink injection Lilu.kext () - Success
02:938 00:017 OC: Prelink injection VirtualSMC.kext () - Success
02:956 00:018 OC: Prelink injection WhateverGreen.kext (Video card) - Success
02:970 00:014 OC: Prelink injection FakePCIID.kext () - Success
02:986 00:016 OC: Prelink injection AppleALC.kext (Sound) - Success
02:991 00:004 OC: Prelink injection MCEReporterDisabler.kext () - Success
02:996 00:004 OC: Prelink injection FakePCIID_Intel_GbX.kext () - Success
03:008 00:011 OC: Prelink injection NullCPUPowerManagement.kext () - Success
03:012 00:004 OC: Prelink injection AGPMInjector.kext () - Success
03:026 00:013 OC: Prelink injection SMCSuperIO.kext () - Success
03:039 00:013 OC: Prelink injection SMCProcessor.kext () - Success
03:044 00:004 OC: Prelink injection USBPorts.kext () - Success
03:069 00:025 OC: Prelink injection SmallTreeIntel8259x.kext () - Success
03:099 00:030 Prelinked status - Success
03:120 00:020 OC: OcAppleGenericInputTimerQuirkExit status - Success
04:156 01:036 OC: OcAppleGenericInputKeycodeExit status - Success

kextstat says there is no fakepciid.kext loaded:

image.thumb.png.6c4b8e102bbdb53e739e658777bfa7ce.png

I checked multiple times that the config is set correctlly.

image.thumb.png.0bc8254b8bc043e11a4c45f913333910.png

 

 

Attachment is my efi folder, please give some help to make it work fEFI.zipor me.

I'm running Catalina with OpenCore 0.51 on my Gene VIII.

 

This is my first time using OC and can anyone check my config.plist to be sure the settings are correct for my system?  I would like to keep the options to the minimum that works with my system.

 

Thanks.

config.plist

On 10/25/2019 at 3:08 AM, dgsga said:

Does anyone know if it is possible to set the macOS partition as the default boot selection in the boot picker on Z390 boards with borked firmware. On my rig the picker always defaults to the first listed volume. I have LegacyEnable set to YES and have nvram.plist loading correctly. Any help here would be much appreciated. Thanks.

 

you have to set ShowPicker=NO. 

@Leoyzen, it is strange, and I would suggest you use kernel logs for tracing the issue. Add some debug code to FakePCIID init/probe/start methods and see what happens. Also check whether there is anything in the kernel log early at start.

 

Side note: you may actually be ok with just injecting vendor-id/device-id through DeviceProperties.

Hello all. I didn't see anything related to this when I hit search so I hope this helps. I've been AMD Hackintoshing with OpenCore and Vanilla Patches and I was not able to boot Windows out of the box. I solved this by adding an entry here:

 

OpenCore version: 0.5.2
Misc > Entries

 

The sample.plist config has a nice template if you use that. Here it is again for reference:

 

Source: https://raw.githubusercontent.com/acidanthera/OpenCorePkg/cd8a046ce9920e5246a427e347f64ffe1ab63e2d/Docs/SampleFull.plist

		<array>
			<dict>
				<key>Arguments</key>
				<string></string>
				<key>Name</key>
				<string>CustomOS</string>
				<key>Comment</key>
				<string>Not signed for security reasons</string>
				<key>Enabled</key>
				<false/>
				<key>Path</key>
				<string>PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,11-22-33-44-55-66-77-88)/HD(1,GPT,00000000-0000-0000-0000-000000000000,0x800,0x64000)/\EFI\BOOT\BOOTX64.EFI</string>
			</dict>
		</array>

Here is what I have modified:

<key>Entries</key>
        <array>
            <dict>
                <key>Arguments</key>
                <string></string>
                <key>Name</key>
                <string>Windows 10</string>
                <key>Comment</key>
                <string>Not signed for security reasons</string>
                <key>Enabled</key>
                <true/>
                <key>Path</key>
                <string>IDENTIFIER/\EFI\Microsoft\Boot\bootmgfw.efi</string>
            </dict>
        </array>

Here is what the identifer looks like for my machine:

<string>PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,16-7D-50-71-53-38-25-00)/HD(1,GPT,094B0907-C4B8-48B1-8010-8BA5BF105D0E,0x28,0x64000)/\EFI\Microsoft\Boot\bootmgfw.efi</string>

You can use gfxutil to grab this path, but the way I did it was to boot EFI shell and run the following command:

*BOOT EFI SHELL*

Shell> fs0:
fs0:\> map > maps.txt

I then mounted my ESP partition and was able to copy and paste the info into the plist file:

 

image.thumb.png.a724dbc35353f8f75c502a3d4943fc8f.png

 

I hope this helps somebody. Took me a bit of tries to get it working.

  • Like 1
  • Thanks 2
15 hours ago, DaGr8Gatzby said:

Hello all. I didn't see anything related to this when I hit search so I hope this helps. I've been AMD Hackintoshing with OpenCore and Vanilla Patches and I was not able to boot Windows out of the box. I solved this by adding an entry here:

 


OpenCore version: 0.5.2
Misc > Entries

 

The sample.plist config has a nice template if you use that. Here it is again for reference:

 

Source: https://raw.githubusercontent.com/acidanthera/OpenCorePkg/cd8a046ce9920e5246a427e347f64ffe1ab63e2d/Docs/SampleFull.plist


		<array>
			<dict>
				<key>Arguments</key>
				<string></string>
				<key>Name</key>
				<string>CustomOS</string>
				<key>Comment</key>
				<string>Not signed for security reasons</string>
				<key>Enabled</key>
				<false/>
				<key>Path</key>
				<string>PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,11-22-33-44-55-66-77-88)/HD(1,GPT,00000000-0000-0000-0000-000000000000,0x800,0x64000)/\EFI\BOOT\BOOTX64.EFI</string>
			</dict>
		</array>

Here is what I have modified:


<key>Entries</key>
        <array>
            <dict>
                <key>Arguments</key>
                <string></string>
                <key>Name</key>
                <string>Windows 10</string>
                <key>Comment</key>
                <string>Not signed for security reasons</string>
                <key>Enabled</key>
                <true/>
                <key>Path</key>
                <string>IDENTIFIER/\EFI\Microsoft\Boot\bootmgfw.efi</string>
            </dict>
        </array>

Here is what the identifer looks like for my machine:


<string>PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,16-7D-50-71-53-38-25-00)/HD(1,GPT,094B0907-C4B8-48B1-8010-8BA5BF105D0E,0x28,0x64000)/\EFI\Microsoft\Boot\bootmgfw.efi</string>

You can use gfxutil to grab this path, but the way I did it was to boot EFI shell and run the following command:


*BOOT EFI SHELL*

Shell> fs0:
fs0:\> map > maps.txt

I then mounted my ESP partition and was able to copy and paste the info into the plist file:

 

image.thumb.png.a724dbc35353f8f75c502a3d4943fc8f.png

 

I hope this helps somebody. Took me a bit of tries to get it working.

 

It becomes simply with BlessOverride.

  • Like 4
On 10/21/2019 at 7:31 PM, moozuki said:

1. Holdover from Clover, sorry

2. My hardware NVRAM works just fine

3. SSDT-PLUG.aml was adjusted for my board

4. no way in BIOS

5. All my drives are SATA.

 

Had to make USB installer and re-install Catalina to get it to boot again, not the best solution.

It seems everytime I update kexts or OC , it gets the unable to load kernel cache error.

 

Solved the problem! Had a bad copy of VirtualSMC.

2 hours ago, Andrey1970 said:

 

It becomes simply with BlessOverride.

 

This did not work for me. I just tested it. I'm booting Windows and Catalina off of the same drive and I already tried setting HideSelf to False. The only way I was able to get boot working is with this entry, which is why I posted it.

 

Good suggestion though!

12 minutes ago, DaGr8Gatzby said:

 

This did not work for me. I just tested it. I'm booting Windows and Catalina off of the same drive and I already tried setting HideSelf to False. The only way I was able to get boot working is with this entry, which is why I posted it.

 

Good suggestion though!

 

ScanPolicy 

(bit 10) — OC_SCAN_ALLOW_FS_ESP, allows scanning of EFI System Partition file system.
  • Like 2
33 minutes ago, Andrey1970 said:

 

ScanPolicy 

(bit 10) — OC_SCAN_ALLOW_FS_ESP, allows scanning of EFI System Partition file system.

Custom Entries are the way to get your particular boot entry to show up, changing ScanPolicy to allow Scanning ESP is not a good idea, there's are potentially my drives and multiple EFI partitions from a system, it will pollute the boot menu with multiple additional unwanted entries.

  • Like 1
39 minutes ago, n.d.k said:

Custom Entries are the way to get your particular boot entry to show up, changing ScanPolicy to allow Scanning ESP is not a good idea, there's are potentially my drives and multiple EFI partitions from a system, it will pollute the boot menu with multiple additional unwanted entries.

 

If you have booter files on others ESP, means they to you are necessary. Otherwise why they there.)

3 hours ago, DaGr8Gatzby said:

 

This did not work for me. I just tested it. I'm booting Windows and Catalina off of the same drive and I already tried setting HideSelf to False. The only way I was able to get boot working is with this entry, which is why I posted it.

 

Good suggestion though!

Try this: ScanPolicy 722179 HideSelf -> NO.

Works for me.

 

4 hours ago, Andrey1970 said:

 

ScanPolicy 

(bit 10) — OC_SCAN_ALLOW_FS_ESP, allows scanning of EFI System Partition file system.

My ScanPolicy is currently set to 0. I was under the impression this enables all volumes. Is this no longer the case?

4 hours ago, n.d.k said:

According to your logic, i should put every app in my computer on the Dock, I am not sure if it's even possible...:)

It seems OpenCore 0.5.2 worked for your hackintosh. Would you share your config.plist for me because I always got reboot or freeze before login desktop in my Z77 hackintosh, but no problem booted by Clover.

17 minutes ago, jsl2000 said:

It seems OpenCore 0.5.2 worked for your hackintosh. Would you share your config.plist for me because I always got reboot or freeze before login desktop in my Z77 hackintosh, but no problem booted by Clover.

I am using my own DSDT.aml and SSDT.aml and don't use any ACPI patches from OC

You need to change the 3 private fields below to match your system:

PlatformInfo->Generic->MLB

PlatformInfo->Generic->SystemSerialNumber

PlatformInfo->Generic->SystemUUID

 

Here's my error free config.plist for my signature system.

config.plist

  • Like 1
35 minutes ago, n.d.k said:

I am using my own DSDT.aml and SSDT.aml and don't use any ACPI patches from OC

You need to change the 3 private fields below to match your system:

PlatformInfo->Generic->MLB

PlatformInfo->Generic->SystemSerialNumber

PlatformInfo->Generic->SystemUUID

 

Here's my error free config.plist for my signature system.

config.plist

Thanks for your prompt reply and help.

I'll test it ASAP.

Quote

 

04:781 00:032 OC: OcMiscLateInit...
04:807 00:025 OC: LoadHandle is 76378A18 - Success
04:834 00:026 OC: Requested resolution is 0x0@0 (max: 1) from Max
04:863 00:029 OCC: Missing GOP on console - Unsupported
04:888 00:024 OC: Changed resolution to 0x0@0 (max: 1) from Max - Unsupported
04:914 00:026 OC: Requested console mode is 0x0 (max: 1) from Max
04:945 00:030 OCC: Requesting 0x0 (max: 1) console mode, curr 3, max 4
04:971 00:026 OCC: Mode 0 - 80x25
04:997 00:026 OCC: Mode 1 - 80x50
05:023 00:026 OCC: Mode 2 - 100x31
05:054 00:030 OCC: Mode 3 - 128x40
05:080 00:026 OCC: Current console mode matches desired mode 3, forcing update
05:111 00:030 OCC: Setting mode 3 (prev 3) with 128x40 console mode
05:143 00:032 OCC: Changed console mode to 3
05:168 00:025 OC: Changed console mode to 0x0 (max: 1) from Max - Success
05:194 00:026 OC: Translated HibernateMode None to 0
05:220 00:026 OC: Hibernation detection status is Not Found

05:247 00:026 OC: OcLoadKernelSupport...
05:273 00:026 OC: OpenCore is loaded, showing boot menu...
05:302 00:029 OC: Handing off to external boot controller
05:327 00:024 OC: Missing external GUI protocol - Not Found
05:354 00:026 BS: Failed to start OpenCore image...

 

 

Is this "Missing external GUI protocol" a driver I'm missing? Or do I have to add anything else about my system to the config.plist?

17 minutes ago, n.d.k said:

Set to YES on your UEFI->Quirks->ProvideConsoleGop

Well, it allows higher resolutions, but fails with the same "Missing external GUI protocol" message...

 

I have all UEFI Protocols enabled as I have drivers on my Clover - which is what I'm trying to mimic on OC config.

Edited by Alex HQuest
×
×
  • Create New...