Boot catalina

laurent

Member
AMD OS X Member
Joined
Oct 30, 2020
Messages
109
I did something stupid, I deactivated an option in opencore that prevents me from seeing the Catalina Installer
at installation
do you have an idea
THANKS
 

Edhawk

Guru
Guru
Joined
May 2, 2020
Messages
2,691
Usually this is the UEFI > APFS > MinDate and MinVersion entries in the config.plist. These need to be edited to match the oldest version of macOS you are running, back to High Sierra. These entries have no impact on Sierra and older releases of macOS.

UEFI-APFS-MinDate+MinVersion.png Use of '-1' is not recommended.
 

laurent

Member
AMD OS X Member
Joined
Oct 30, 2020
Messages
109
Usually this is the UEFI > APFS > MinDate and MinVersion entries in the config.plist. These need to be edited to match the oldest version of macOS you are running, back to High Sierra. These entries have no impact on Sierra and older releases of macOS.

View attachment 13002 Use of '-1' is not recommended.
THANKS
now there is a weird thing about processor name recognition
it should be amd ryzen 5 3600
do you have an idea
 

Attachments

  • Capture d’écran 2023-12-30 à 22.02.40.png
    Capture d’écran 2023-12-30 à 22.02.40.png
    192.5 KB · Views: 12
  • Capture d’écran 2023-12-30 à 22.10.48.png
    Capture d’écran 2023-12-30 à 22.10.48.png
    356.7 KB · Views: 5

Edhawk

Guru
Guru
Joined
May 2, 2020
Messages
2,691
You can set the CPU name in 'About this Mac' using RestrictEvents.kext and by adding three entries in the NVRAM > Add, and three new entries in the NVRAM > Delete sections of your config.plist.

This is how mine is shown in Sonoma.

Screenshot 2023-12-30 at 21.44.20.png Processor name shown as set in the config.plist.

This is a screenshot showing the contents of the NVRAM > Add and NVRAM > Delete sections in my config.plist.

Screenshot 2023-12-30 at 21.47.31.png Viewed in ProperTree Plist editor

As you can see I have created three (3) additional entries in both of the '4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102' sections.

If you create the same entries, with the same String/number entries in your config.plist, obviously changing the CPU name to 'Ryzen 5 3600 3.6GHz' or similar, this process should work the same for you.
 

Edhawk

Guru
Guru
Joined
May 2, 2020
Messages
2,691
Here is a link to the RestrictEvents Github page, it contains details of the 'rev' (RestrictEVents) boot argument and NVRAM options.


You can also download the latest release, if you don't already have a copy of the latest kext.
 

laurent

Member
AMD OS X Member
Joined
Oct 30, 2020
Messages
109
Here is a link to the RestrictEvents Github page, it contains details of the 'rev' (RestrictEVents) boot argument and NVRAM options.


You can also download the latest release, if you don't already have a copy of the latest kext.
I don't think I'm wrong but it doesn't work, there must be something I'm not doing correctly
opencore 0.7.0
 

Attachments

  • Capture d’écran 2023-12-30 à 23.31.25.png
    Capture d’écran 2023-12-30 à 23.31.25.png
    817 KB · Views: 4
Last edited:

Edhawk

Guru
Guru
Joined
May 2, 2020
Messages
2,691
Which SMBIOS are you using, MacPro6,1 or MacPro7,1?

Do you have the 'ProcessorType' entry in the PlatformInfo > Generic section of your config.plist set with (0x0601) '1537' instead of the default entry '0'?

Screenshot 2023-12-30 at 22.45.17.png PlatformInfo > Generic > ProcessorType

1537 is used for a 6-core or lower CPU.
I use 3841 (0x0F01) as my CPU has 12-cores.

Did you use the ResetNvramEntry from the OC boot screen to clear the old NVRAM entries in your system?
 

laurent

Member
AMD OS X Member
Joined
Oct 30, 2020
Messages
109
Which SMBIOS are you using, MacPro6,1 or MacPro7,1?

Do you have the 'ProcessorType' entry in the PlatformInfo > Generic section of your config.plist set with (0x0601) '1537' instead of the default entry '0'?

View attachment 13011 PlatformInfo > Generic > ProcessorType

1537 is used for a 6-core or lower CPU.
I use 3841 (0x0F01) as my CPU has 12-cores.

Did you use the ResetNvramEntry from the OC boot screen to clear the old NVRAM entries in your system?
 

laurent

Member
AMD OS X Member
Joined
Oct 30, 2020
Messages
109
thank you I just didn't do a nvram reset
 

Attachments

  • Capture d’écran 2023-12-31 à 00.11.15.png
    Capture d’écran 2023-12-31 à 00.11.15.png
    179.3 KB · Views: 10

laurent

Member
AMD OS X Member
Joined
Oct 30, 2020
Messages
109
Good morning
I attach the opencore error report
if anyone can help me
everything seems to work apart from the burner which is recognized every other time and I find that it takes a long time to start up
I find that there are quite a few errors
it's a catalina 10.15.7 installation
on an asus roguestrix b550 A gaming motherboard
ryzen 5 3600
 

Attachments

  • opencore-2024-01-05-153247.txt
    256 KB · Views: 7
  • Capture d’écran 2024-01-05 à 18.15.55.png
    Capture d’écran 2024-01-05 à 18.15.55.png
    575.6 KB · Views: 7
Last edited:

laurent

Member
AMD OS X Member
Joined
Oct 30, 2020
Messages
109
another weird thing
 

Attachments

  • Résultat de Terminal.pdf
    21.5 KB · Views: 1

Edhawk

Guru
Guru
Joined
May 2, 2020
Messages
2,691
That Terminal output is not weird. It is normal when you are trying to install macOS. It shows the following:

Disk0 = EFI and APFS Container, normal split for macOS drive.
Disk1 = 2GB HFS+ Disk image, probably the USB you are using to install macOS, containing a recovery partition not a full installer.
Disk2 = Synthesised APFS Volumes contained in the Disk0 Container, again normal for macOS APFS drive.
Disk3 - Disk Image = Installation Partitions, all 21!

So the Terminal output is nothing to worry about, if you are seeing it as part of the macOS Installation.

The Disk Image entries should all disappear once you have macOS installed and have removed the Installer (USB?).
 

laurent

Member
AMD OS X Member
Joined
Oct 30, 2020
Messages
109
Cette sortie du terminal n’est pas bizarre. C'est normal lorsque vous essayez d'installer macOS. Il montre ce qui suit :

Disk0 = Conteneur EFI et APFS, division normale pour le lecteur macOS.
Disk1 = 2 Go HFS+ Image disque, probablement la clé USB que vous utilisez pour installer macOS, contenant une partition de récupération et non un programme d'installation complet.
Disk2 = Volumes APFS synthétisés contenus dans le conteneur Disk0, encore une fois normal pour le lecteur macOS APFS.
Disk3 - Image disque = Partitions d'installation, toutes les 21 !

Il n’y a donc pas lieu de s’inquiéter de la sortie du terminal si vous la voyez dans le cadre de l’installation de macOS.

Les entrées de l'image disque devraient toutes disparaître une fois que macOS est installé et que vous avez supprimé le programme d'installation (USB ?).
catalina is already installed I ran the command in the terminal from recovery mode
there must be a trace somewhere
 
Last edited:

Edhawk

Guru
Guru
Joined
May 2, 2020
Messages
2,691
If you boot in to Recovery, then part of the recovery process is creating the 21 x installation partitions/disks. So you can select a clean Install of macOS Catalina from the 2nd phase of the Wizard, i.e. in case you need to Erase your current macOS drive in Disk Utility. The 2.1GB disk is probably containing the recovery data etc.

The APFS Container and Volumes are all fine and as expected.

I am not sure what you are worried or concerned about.

Examining the setup in Recovery mode is always going to be different from undertaking the same examination when booting Catalina or any other version of macOS.
 
Back
Top Bottom
  AdBlock Detected
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.