Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
I was able to change the video card name to 580 from 480:
1589647451749.png

By modifying IOKitPersonalities in the radeonBoost.kext's Info.plist by adding ATY,DeviceName and model:
1589647549422.png

I am wondering why I can't do that through "add device properties" in the OC configuration file?
 
DigitaLife: "I had Windows 10 installed via Legacy Mode in the dedicated SATA SSD, then I converted to UEFI in a few steps (without data loss) and now OC sees the Windows volume without problems!"

Please show your steps to convert Win 10 Legacy to Win 10 UEFI-(I am a real Newbie, I couldn't follow the multiple steps I read on this thread to do it!!??)
Any simplified help (without data loss) will be Greatly appreciated!!

PS-I also have Win 10 legacy using the actual Bootcamp separate SSD on Parallels, can it be done from VM??
 
startergo said:
I am wondering why I can't do that through "add device properties" in the OC configuration file?
Click to expand...

If the properties already exist, they will not be set unless they are "blocked" first (or "deleted" in the latest OpenCore version).
 
cdf said:
If the properties already exist, they will not be set unless they are "blocked" first (or "deleted" in the latest OpenCore version).
Click to expand...
the property exists under x4000 driver, but not in OC. So how can it be "deleted" first? I know Clover can do it in the device properties section by just adding the property. A kext with higher IOProbeScore will also override properties set by the original kext.
 
Last edited:
papadj3 said:
DigitaLife: "I had Windows 10 installed via Legacy Mode in the dedicated SATA SSD, then I converted to UEFI in a few steps (without data loss) and now OC sees the Windows volume without problems!"

Please show your steps to convert Win 10 Legacy to Win 10 UEFI-(I am a real Newbie, I couldn't follow the multiple steps I read on this thread to do it!!??)
Any simplified help (without data loss) will be Greatly appreciated!!

PS-I also have Win 10 legacy using the actual Bootcamp separate SSD on Parallels, can it be done from VM??
Click to expand...
I used this:
www.windowscentral.com

How to convert MBR to GPT drive to switch BIOS to UEFI on Windows 10

A PC with UEFI is more secure and faster than the legacy one using BIOS, and here's how to switch.
www.windowscentral.com www.windowscentral.com
 
startergo said:
the property exists under x4000 driver, but not in OC. So how can it be "deleted" first? I know Clover can do it.
Click to expand...

In the latest version of OpenCore, use
Code: 
key>Delete</key>
<dict>
...
</dict>
under DeviceProperties.
 
  • Like
Reactions: startergo
cdf said:
The disk identifier can change from one boot to the next. I suspect that you actually mounted the EFI volume of another disk.
Click to expand...
I deleted OC (the whole EFI folder) from the EFI partition, restarted, reset the NVRAM and disabled the SIP.
Then I restarted and tried to mount the EFI partition of the Catalina SSD disk (identified by both Terminal and Clover Configurator: disk0s1), but as you can see from the image, the EFI volume is empty! Yet I believe I have not misidentified!
Can you please help me solve this problem! Thanks in advance!
Schermata 2020-05-17 alle 17.03.10.pngSchermata 2020-05-17 alle 17.04.29.png

Schermata 2020-05-17 alle 17.05.22.png
 
DigitaLife said:
I deleted OC (the whole EFI folder) from the EFI partition, restarted, reset the NVRAM and disabled the SIP.
Then I restarted and tried to mount the EFI partition of the Catalina SSD disk (identified by both Terminal and Clover Configurator: disk0s1), but as you can see from the image, the EFI volume is empty!
Click to expand...

If you deleted the EFI folder, then the EFI volume should be empty.
 
  • Like
Reactions: tommy chen
cdf said:
If you deleted the EFI folder, then the EFI volume should be empty.
Click to expand...
Ok! Thank you!
[automerge]1589729883[/automerge]
papadj3 said:
DigitaLife: "I had Windows 10 installed via Legacy Mode in the dedicated SATA SSD, then I converted to UEFI in a few steps (without data loss) and now OC sees the Windows volume without problems!"

Please show your steps to convert Win 10 Legacy to Win 10 UEFI-(I am a real Newbie, I couldn't follow the multiple steps I read on this thread to do it!!??)
Any simplified help (without data loss) will be Greatly appreciated!!

PS-I also have Win 10 legacy using the actual Bootcamp separate SSD on Parallels, can it be done from VM??
Click to expand...
See thread "How to: Boot Camp without a Boot Screen!, Post #620 and #634!
But the most important thing, after conversion to UEFI, is to make sure that Windows doesn't try to boot without OpenCore!
 
Last edited:
Imho it should be in the 1st post to let users make a backup of the firmware.

Either with Dosdude's rom tool or with a linux thumb drive and flashrom.

If Windows starts in Uefi mode without protection there is no easy way back. Just with reconstruction of the nvram volume what can lead to mistakes and a brick.

With a rom backup without certificates one can flash the rom file back.
 
cdf said:
In the latest version of OpenCore, use
Code: 
key>Delete</key>
<dict>
...
</dict>
under DeviceProperties.
Click to expand...
Something like this?
Code: 
<dict>
            <key>PciRoot(0x0)/Pci(0x1b,0x0)</key>
            <dict>
                <key>Delete</key>
                <string>model layout-id</string>
                <key>layout-id</key>
                <data>
                AQAAAA==
                </data>
                <key>model</key>
                <data>
                UmFkZW9uIFJYIDU4MA==
                </data>
            </dict>
 
Last edited:
startergo said:
Something like this?
Code: 
<key>DeviceProperties</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)</key>
            <dict>
                <key>AAPL,slot-name</key>
                <data>SW50ZXJuYWxAMCwxLDAvMCwx</data>
                <key>Delete</key>
                <string>model hda-gfx layout-id AAPL,slot-name</string>
                <key>device_type</key>
                <data>QXVkaW8gZGV2aWNl</data>
                <key>hda-gfx</key>
                <data>b25ib2FyZC0y</data>
                <key>layout-id</key>
                <data>AQAAAA==</data>
                <key>model</key>
                <data>UlggNTgwIEhETUkgQXVkaW8=</data>
            </dict>
        </dict>
        <key>Block</key>
        <dict/>
Click to expand...
I don't know if your code is correct or not, never use this Delete function. However, use <string> should be easier. e.g.
Code: 
<key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)</key>
            <dict>
                <key>AAPL,slot-name</key>
                <string>Internal@0,1,0,0,1</string>
                <key>Delete</key>
                <string>model hda-gfx layout-id AAPL,slot-name</string>
                <key>device_type</key>
                <string>Audio device</string>
                <key>hda-gfx</key>
                <string>onboard-2</string>
                <key>layout-id</key>
                <data>AQAAAA==</data>
                <key>model</key>
                <string>RX 580 HDMI Audio</string>
            </dict>

For your reference, this is the code I use on my Hackintosh
Code: 
<key>PciRoot(0x0)/Pci(0x1f,0x3)</key>
            <dict>
                <key>AAPL,slot-name</key>
                <string>Internal@0,31,3</string>
                <key>device_type</key>
                <string>Audio device</string>
                <key>hda-gfx</key>
                <string>onboard-2</string>
                <key>layout-id</key>
                <data>AgAAAA==</data>
                <key>model</key>
                <string>200 Series PCH HD Audio</string>
            </dict>
 
Question,
My hard drive with Mojave is formated in GUID APFS, it looks like 3 layers.
The Disk itself, a Container and inside the container the Volume,
The Volume has a name but open core is not seeing the name, just the untitled container so in OC boot menu instead of the Volume name all I see is untitled how do I get around this.
Thanks
 
cdf said:
No. At the bottom of your code you have "Block." That's where you include the device properties that you want to override. In the latest version of OpenCore, "Block" is replaced by "Delete."
Click to expand...
h9826790 said:
I don't know if your code is correct or not, never use this Delete function. However, use <string> should be easier. e.g.
Code: 
<key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)</key>
            <dict>
                <key>AAPL,slot-name</key>
                <string>Internal@0,1,0,0,1</string>
                <key>Delete</key>
                <string>model hda-gfx layout-id AAPL,slot-name</string>
                <key>device_type</key>
                <string>Audio device</string>
                <key>hda-gfx</key>
                <string>onboard-2</string>
                <key>layout-id</key>
                <data>AQAAAA==</data>
                <key>model</key>
                <string>RX 580 HDMI Audio</string>
            </dict>

For your reference, this is the code I use on my Hackintosh
Code: 
<key>PciRoot(0x0)/Pci(0x1f,0x3)</key>
            <dict>
                <key>AAPL,slot-name</key>
                <string>Internal@0,31,3</string>
                <key>device_type</key>
                <string>Audio device</string>
                <key>hda-gfx</key>
                <string>onboard-2</string>
                <key>layout-id</key>
                <data>AgAAAA==</data>
                <key>model</key>
                <string>200 Series PCH HD Audio</string>
            </dict>
Click to expand...
Yeah, just read the log, they just rename Block to Delete.

Which means it should look something like this
Code: 
<key>DeviceProperties</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)</key>
            <dict>
                <key>AAPL,slot-name</key>
                <string>Internal@0,1,0,0,1</string>
                <key>device_type</key>
                <string>Audio device</string>
                <key>hda-gfx</key>
                <string>onboard-2</string>
                <key>layout-id</key>
                <data>AQAAAA==</data>
                <key>model</key>
                <string>RX 580 HDMI Audio</string>
            </dict>
        </dict>
        <key>Delete</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)</key>
            <array>
                <string>model</string>
                <string>hda-gfx</string>
                <string>layout-id</string>
                <string>AAPL,slot-name</string>
            </array>
        </dict>
    </dict>
 
  • Like
Reactions: startergo and cdf
I often use use OpenCore Configurator not for file saving as it is almost always behind the development, but for EFI mounting. Now there is a very useful feature:
1589741155243.png

If you change string to data it will do automatic conversion:
1589741243835.png

Then just click on Synchronize in the bottom left corner.
 
  • Like
Reactions: h9826790
Hello All,
well I managed to fix the issue by uninstalling everything and starting from scratch, so now the name on the hard drive shows up instead of the untitlled container created from the APFS system.
I did however install a copy of Windows 7 on a separate drive OpenCore doesn't seem to have recognized it when I did the reset of the SMC, Is there a line of code in the config file that would help OC find the Windows drive?
Thanks in Advance
Ralph
 
Curtisrb said:
Hello All,
well I managed to fix the issue by uninstalling everything and starting from scratch, so now the name on the hard drive shows up instead of the untitlled container created from the APFS system.
I did however install a copy of Windows 7 on a separate drive OpenCore doesn't seem to have recognized it when I did the reset of the SMC, Is there a line of code in the config file that would help OC find the Windows drive?
Thanks in Advance
Ralph
Click to expand...
Windows 7 is most probably installed in Legacy/MBR mode, which OC does not support.
 
startergo said:
Windows 7 is most probably installed in Legacy/MBR mode, which OC does not support.
Click to expand...
I don't know if Windows changed the format of the disk but I installed it via Bootcamp on my High Sierra drive as a 50/50 partition. the drive is GUID the OS volume is OS Extended Journeled, the Windows volume is NTFS
this is what Disk Utility is telling me right now?
 
Curtisrb said:
I don't know if Windows changed the format of the disk but I installed it via Bootcamp on my High Sierra drive as a 50/50 partition. the drive is GUID the OS volume is OS Extended Journeled, the Windows volume is NTFS
this is what Disk Utility is telling me right now?
Click to expand...
BOOTCAMP assistant repartitions the drive in hybrid MBR/GPT manner, so even though it is a GPT drive it appears to Windows as a MBR partitioned drive and WIndows can not see the EFI/ESP partition, therefore can not boot in UEFI mode. This hybrid MBR/GPT is not supported by OC. OC will only boot Windows loading the boot drivers and the BCD store from its ESP/EFI partition.
 
  • Like
Reactions: octoviaa
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back