- Joined
- Feb 4, 2011
- Messages
- 71
- Motherboard
- Gigabyte GA-Z170N-WiFi
- CPU
- i7-6700K
- Graphics
- GT 640
- Mac
- Mobile Phone
I'm sorry I think I didn't select properly verbose mode during that test.Have you toggled Verbose on? In the screenshot, Verbose is still unchecked.
Clover Configurator (and OpenCore Configurator and several other apps) get confused when we mount two or more EFI partitions at the same time:I'm sorry I think I didn't select properly verbose mode during that test.
Anyway good news (I hope)!
Now everything works as it supposed to work.
-Both Mojave and Catalina boot properly.
-Mojave boots with and without Catalina SSD attached, during the clover boot Mojave shows 10.14.6 version.
-Clover finally load the Mojave "Default boot disk" which was set on the config.plist (before it was loading always the Catalina one, no matter what I had selected on Clover Configurator)
-Catalina boots with and without Mojave SSD attached (that was true also before.)
I also found what created all this mess. I'm not sure if it's me that I do something wrong but any time I open the confing.plist using clover configurator version 5.16.0.0, even only to referencing something (so I don't change anything on config.plist file) that operation mess up with the Mac OSX version on clover boot.
Sometimes is 10.14.6 on Catalina end 10.15.7 on Mojave, sometimes is 10.15.7 on both (Mojave and Catalina).
Sometimes is 10.14.6 on both.
At the moment they are correct:
Mojave boot = 10.14.6
Catalina boot = 10.15.7
My question is, how can I make sure I don't mess up with that when I need to edit or even only open one of the config.plist? Should I change Clover configurator version? What do you recommend?
Hello all
I have ASUS UX550GE TB3 dump. Can anyone help me with patching it ? Much appreciated.
Best regards and thanks in advance
@CaseySJ Also,I'm sorry I think I didn't select properly verbose mode during that test.
Anyway good news (I hope)!
Now everything works as it supposed to work.
-Both Mojave and Catalina boot properly.
-Mojave boots with and without Catalina SSD attached, during the clover boot Mojave shows 10.14.6 version.
-Clover finally load the Mojave "Default boot disk" which was set on the config.plist (before it was loading always the Catalina one, no matter what I had selected on Clover Configurator)
-Catalina boots with and without Mojave SSD attached (that was true also before.)
I also found what created all this mess. I'm not sure if it's me that I do something wrong but any time I open the confing.plist using clover configurator version 5.16.0.0, even only to reference something (so I don't change anything on config.plist file) that operation mess up with the Mac OSX version on clover boot.
Sometimes is 10.14.6 on Catalina end 10.15.7 on Mojave, sometimes is 10.15.7 on both (Mojave and Catalina).
Sometimes is 10.14.6 on both.
At the moment they are correct:
Mojave boot = 10.14.6
Catalina boot = 10.15.7
My question is, how can I make sure I don't mess up with that when I need to edit or even only open one of the config.plist? Should I change Clover configurator version? What do you recommend?
Good job in extracting the Thunderbolt firmware. This seems to be an Alpine Ridge chip. Please try the attached modified firmware.Hello all
I have ASUS UX550GE TB3 dump. Can anyone help me with patching it ? Much appreciated.
Best regards and thanks in advance
Seems to be Alpine Ridge.
It seems harmless, but technically should not be there. Please try the following:@CaseySJ Also,
There is a strange name in the Bios Boot for the Catalina Mojave SSD:
- Clover Start boot.efi at CATALINA (P5: Samsung SSD 850 EVO 250GB)
Is that normal?
Ok, that's good to know.Clover Configurator (and OpenCore Configurator and several other apps) get confused when we mount two or more EFI partitions at the same time:
If open config.plist from Disk A, it could get written to Disk B, and vice-versa. Therefore, whenever using Clover Configurator or OpenCore Configurator always check that only one EFI partition is mounted.
- EFI (from Disk A)
- EFI (from Disk B)
That screenshot looks good. Let's check some more things:
- Which version of WhateverGreen are you using?
- Which cable are you using? Do you have a product link?
- In BIOS, is Internal Graphics enabled?
- Please run IORegistryExplorer, select File --> Save As..., and post the saved file. This will show us the iGPU configuration.
Using the iGPU to drive a display monitor is not recommended, but it is okay for temporarily use (generally for debugging a problem with AMD GPU or while waiting for AMD GPU order to be delivered).
Because you are trying to debug the issue of blank screen after wake-from-sleep with the AMD GPU, I don't think it makes too much sense to activate iGPU video. However, this still makes sense if you subsequently remove the AMD GPU and test sleep/wake behavior using only the on-board video ports.
- Are you running Mojave or Catalina?
- What is the make/model of the AMD GPU?