- Joined
- Sep 21, 2010
- Messages
- 13,411
- Motherboard
- HP 17" 17-by3053cl
- CPU
- i5-1035G1
- Graphics
- Intel UHD Graphics, 1920x1080
- Mac
- Classic Mac
- Mobile Phone
Stork's MyHero II Build: ASUS ROG MAXIMUS Z370 HERO X - i7-8700K - AMD RX 580 - Thunderbolt 3
- Thread starter Stork
- Start date
- Joined
- Jan 23, 2019
- Messages
- 186
- Motherboard
- Asus ROG MAXIMUS Z370 HERO X
- CPU
- i9-9900K
- Graphics
- Radeon VII
- Joined
- Jan 23, 2019
- Messages
- 186
- Motherboard
- Asus ROG MAXIMUS Z370 HERO X
- CPU
- i9-9900K
- Graphics
- Radeon VII
Information that can be useful for those who use this configuration:
updated to 10.15.6, after backing up and updating Clover (5119) and basic kext (ALC, Lilu, WEG) to the latest versions.
Everything as if it were an original Mac, from the request for an update on the system preferences to the return to the updated system, without any necessary intervention.
At a first check everything seems to be working properly and also my personal problem with the USB-C port with a hub attached that crashed the system on waking up from sleep seems to have gone away (I have tried only one sleep and wake, for now).
No problem with video ports (the DP cable was attached and remained where it was).
I hope it will be encouraging to go to the final version for those like me who were a little intimidated by the problems read on .5 and wanted to stop at .4, waiting for better and reassuring news (thanks again @Stork!).
edit:
Unfortunately, at the second wake after sleep, the usual crash arrived.
So ,I have to infer that it's not a .4 bug problem like Chimiel had suggested, but it's related to something else.
I'll have to look for why this hub makes me this joke.
The first step I will take is to connect it to a USB-A port, as soon as I find an adapter ...
updated to 10.15.6, after backing up and updating Clover (5119) and basic kext (ALC, Lilu, WEG) to the latest versions.
Everything as if it were an original Mac, from the request for an update on the system preferences to the return to the updated system, without any necessary intervention.
At a first check everything seems to be working properly and also my personal problem with the USB-C port with a hub attached that crashed the system on waking up from sleep seems to have gone away (I have tried only one sleep and wake, for now).
No problem with video ports (the DP cable was attached and remained where it was).
I hope it will be encouraging to go to the final version for those like me who were a little intimidated by the problems read on .5 and wanted to stop at .4, waiting for better and reassuring news (thanks again @Stork!).
edit:
Unfortunately, at the second wake after sleep, the usual crash arrived.
So ,I have to infer that it's not a .4 bug problem like Chimiel had suggested, but it's related to something else.
I'll have to look for why this hub makes me this joke.
The first step I will take is to connect it to a USB-A port, as soon as I find an adapter ...
Last edited:
- Joined
- Jan 23, 2019
- Messages
- 186
- Motherboard
- Asus ROG MAXIMUS Z370 HERO X
- CPU
- i9-9900K
- Graphics
- Radeon VII
With the use of a USB-c to USB-a adapter it seems that I managed to understand that the problem of the crash on waking is due to the use of one of the two ports related to the external controller (which is seen as such) of our moterboard (red USB-a port and USB-c port).
The first thing I tried was to connect the panic USB-c hub to the red USB-a port (right through the adapter) and I got the exact same behavior, then I connected the hub to one of the USB-a blue (the internal ones in the list of 15 declared with USBPorts.kext) and the problem seems to have disappeared. I tried to do several sleeps and wakes, but it is stable and functional.
It seems as if that controller (or at least as it has been managed in MacOX since 10.15.4, because before it had no problems), don't like a hub that activates both the HS and the SS function in the same port, because the first connection (empty hub) had only activated the function HS and did not give problems, then I tried to attack a USB3.0 stick that also activated the SS function (all seen with Hackintool and with the system info) and upon awakening the crash occurred.
Once activated the SS function from the hub remains active even if the USBDisk is disconnected and the refresh is done.
I ask @UtterDisbelief, which I greet and thank, if by chance reading this, from the behavior, he manages to deduce something.
However it seems that thanks to a small USB-c/USB-a adapter I have returned to full functionality in comfort, without having to disconnect and reattach the cable (or disable sleep), every time I need to read an SDcard.
I'd like to know if anyone else using the HERO X has encountered the same problem or something similar, now that the behavior is a little more defined.
Greetings to all
The first thing I tried was to connect the panic USB-c hub to the red USB-a port (right through the adapter) and I got the exact same behavior, then I connected the hub to one of the USB-a blue (the internal ones in the list of 15 declared with USBPorts.kext) and the problem seems to have disappeared. I tried to do several sleeps and wakes, but it is stable and functional.
It seems as if that controller (or at least as it has been managed in MacOX since 10.15.4, because before it had no problems), don't like a hub that activates both the HS and the SS function in the same port, because the first connection (empty hub) had only activated the function HS and did not give problems, then I tried to attack a USB3.0 stick that also activated the SS function (all seen with Hackintool and with the system info) and upon awakening the crash occurred.
Once activated the SS function from the hub remains active even if the USBDisk is disconnected and the refresh is done.
I ask @UtterDisbelief, which I greet and thank, if by chance reading this, from the behavior, he manages to deduce something.
However it seems that thanks to a small USB-c/USB-a adapter I have returned to full functionality in comfort, without having to disconnect and reattach the cable (or disable sleep), every time I need to read an SDcard.
I'd like to know if anyone else using the HERO X has encountered the same problem or something similar, now that the behavior is a little more defined.
Greetings to all
- Joined
- Jan 20, 2018
- Messages
- 162
- Motherboard
- ASUS ROG MAXIMUS X HERO Z370
- CPU
- i7-8086K
- Graphics
- Vega 56
- Mac
- Mobile Phone
@Stork What Bios version do you use the days on the Hero X?
(BTW I switched to OpenCore with the help of @pastrychef, it runs smooth)
(BTW I switched to OpenCore with the help of @pastrychef, it runs smooth)
- Joined
- Sep 21, 2010
- Messages
- 13,411
- Motherboard
- HP 17" 17-by3053cl
- CPU
- i5-1035G1
- Graphics
- Intel UHD Graphics, 1920x1080
- Mac
- Classic Mac
- Mobile Phone
I'm still on 1801. I forgot to look lately to update the BIOS. I'll update to 2402 within the next couple of days.
- Joined
- Jul 7, 2010
- Messages
- 130
- Motherboard
- ASUS ROG MAXIMUS HERO X Z370
- CPU
- i9-9900KS
- Graphics
- RX 580
- Mac
- Classic Mac
- Mobile Phone
Any chance of sharing your OpenCore EFI for this board?
- Joined
- Nov 12, 2018
- Messages
- 53
- Motherboard
- Asus ROG Maximus X Hero Gaming Z370
- CPU
- i7-8700K
- Graphics
- RX 570
- Mac
- Mobile Phone
I'm also interested. Or is the help you mentioned somewhere accessible?
My Hackintosh runs great, but I'm interested in switch to OpenCore (prepare for Big Sur).
- Joined
- Jan 20, 2018
- Messages
- 162
- Motherboard
- ASUS ROG MAXIMUS X HERO Z370
- CPU
- i7-8086K
- Graphics
- Vega 56
- Mac
- Mobile Phone
Well, it's not my OpenCore EFI, it's @pastrychef!
link
You have to fill some stuff and make a new USBport.kext.
Good luck!
link
You have to fill some stuff and make a new USBport.kext.
Good luck!
- Joined
- Jan 23, 2019
- Messages
- 186
- Motherboard
- Asus ROG MAXIMUS Z370 HERO X
- CPU
- i9-9900K
- Graphics
- Radeon VII
I'm also interested. Or is the help you mentioned somewhere accessible?
This is an EFI created for this configuration (or rather for my configuration, which in any case is totally compatible with that of this thread, from which it originates and then has been updated)
In the EFI there are minimum interventions (I'm learning ... Radeonboost is missing for example) and it was created to be able to update Catalina 10.15.6 to Big Sur Beta and has also granted updates to even more advanced beta.
I don't use Big Sur as my main system, so I didn't dig into much, but on initial inspection it seemed to me that everything was working fine.
I would be grateful to those who use it if (in full spirit of this forum) in finding possible or necessary changes or improvements, they would also inform me and the others here, in order to make the configuration of this thread created so well by Stork, valid and performing for a long time to go.
It is still in verbose mode ...
For my needs (related to the video card) I used the FakeSMC and related to then add the kext related to the GPU that tells me the temperature of the VII, I say this for those who want to go back to virtualSMC.
There are to enter the data relating to the serial etc .. and the SMBIOS is 1.1.
Being on Catalina, as the main system, I am continuing to use Clover's EFI, but this one from OC loads faster, both Catalina and Big Sur, but until I decide to work on it and study it a little more I feel more comfortable with Clover.
Share problems/success and changes/improvements, thank you ...
greetings to all