Contribute
Register

Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

@bricknewer Please replace your SSDT-DMAR.aml with the one I attached here and then try booting Windows via OC again.
 

Attachments

  • SSDT-DMAR.aml
    80 bytes · Views: 30
Anyone else seeing strange disk read access since updating to 12.5? I have a Windows SSD, and, while booted in OSX, I see sustained reads on my NTFS RO volume of about 45min (100MB/s) every 3-4 hours. I have since unmounted the NTFS drive while operating OSX. Besides this everything works great.
 

** Mini-Guide: Change Disk Label Shown in OpenCore Picker **
Please do not quote this guide in its entirety. Post a link instead.

...
I upgraded to OC 0.8.3 and Monterey 12.5
Then I would change the label name but I had this error when I want to edit .disk_label.contentDetails.
E1187: Failed to source defaults.vim

Nota Bene : my system is in French.
 
I upgraded to OC 0.8.3 and Monterey 12.5
Then I would change the label name but I had this error when I want to edit .disk_label.contentDetails.
E1187: Failed to source defaults.vim

Nota Bene : my system is in French.
Are you using vi or vim? Please try vi first.
 
Or use nano, and spare yourself the pain of dealing with vi commands to edit a single line…
 
Are you using vi or vim? Please try vi first.

I used vi

I just tested this. You’re right that we get this error:
Code:
E1187: Failed to source defaults.vim

But right after that we see this:
Code:
Press ENTER or type command to continue

Just press Enter and the vi editor will start normally. It’s okay if defaults.vim cannot be found and read.
 
** OpenCore Configurator 2.62.0.0 has been released **
Open the "Preferences" dialog and set it to 0.8.3 Release Configuration as shown​

If you're using OpenCore 0.8.3 and seeing OCS Schema: LegacyEnable warnings during boot, simply open your config.plist in OpenCore Configurator 2.62.0.0, ensure that the application is set to "0.8.3 Release Configuration", then click through each of the main headings on the left side without making any changes :

  • ACPI
  • Booter
  • DeviceProperties
  • Kernel
  • ...
Then save the file (CMD-S). On reboot, the LegacyEnable warning will disappear.
Screenshot 2022-08-10 at 1.00.31 PM.png
 
Last edited:
Or use nano, and spare yourself the pain of dealing with vi commands to edit a single line…
nano is not in the default path when we boot into Recovery. The default path points to a few directories, among them /usr/bin in which we have both vi and vim, but not nano.

nano is available, but we need to qualify the path ourselves:
Code:
/Volumes/[name-of-macOS-volume]/usr/bin/nano
 
I just tested this. You’re right that we get this error:
Code:
E1187: Failed to source defaults.vim

But right after that we see this:
Code:
Press ENTER or type command to continue

Just press Enter and the vi editor will start normally. It’s okay if defaults.vim cannot be found and read.
I pressed Enter but it was very difficult to edit the content.
When I type characters, I got a strange behaviour from the editor.
Lines were added and I could not delete them afterwards.
I switched my keyboard to US format but I had even more problems then I came back to French and still had as much difficulty to write Monterey instead of Big Sur.

I restarted, got a text line boot instead of icons.
I tried to edit .disk_label.contentDetails again and finally by some miracle I managed to write Monterey on the first line but the file now contains 10 lines.

Since then everything works and I don't dare touch anything.
 
Back
Top