- Joined
- Jun 9, 2011
- Messages
- 18
- Motherboard
- Gigabyte Z490 Vision D
- CPU
- i5-10600K
- Graphics
- RX 5500 XT
- Mac
- Mobile Phone
Because it did not work for me, computer shutsoff at the apple logo
Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580
- Thread starter CaseySJ
- Start date
Feartech
Moderator
- Joined
- Aug 3, 2013
- Messages
- 32,503
- Motherboard
- Asus N752VX-OpenCore
- CPU
- i7-6700HQ / HM170
- Graphics
- HD 530 1920 x 1080
- Mac
- Mobile Phone
you posting in a Golden Build thread and using a a EFI not from this site....
- Joined
- Jun 9, 2011
- Messages
- 18
- Motherboard
- Gigabyte Z490 Vision D
- CPU
- i5-10600K
- Graphics
- RX 5500 XT
- Mac
- Mobile Phone
Ok this is the EFI i used from this build, and this is where it stops. My BIOS is set up and all. I get further along with the other EFI.
BIOS version F2
Attachments
Last edited:
trs96
Moderator
- Joined
- Jul 30, 2012
- Messages
- 25,559
- Motherboard
- Gigabyte B460M Aorus Pro
- CPU
- i5-10500
- Graphics
- RX 570
- Mac
- Mobile Phone
Upgrade to the same BIOS/UEFI that CaseySJ used.
Also check that the settings in the BIOS are all changed in the same manner.
Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580
CaseySJ's Comet Lake-S in BeQuiet! Pure Base 500DX: Gigabyte Z490 Vision-D - i5-10400 - UHD 630 - AMD RX 580 (Please do not quote this guide in its entirety. Post a link instead.) (See this post for how to refer to a Guide or Mini-Guide.) Refer to the Z390 Designare thread for answers to a...
www.tonymacx86.com
Casey's guide has been thoroughly tested and proven to work. Follow everything in the guide.
- Joined
- Jun 9, 2011
- Messages
- 18
- Motherboard
- Gigabyte Z490 Vision D
- CPU
- i5-10600K
- Graphics
- RX 5500 XT
- Mac
- Mobile Phone
I understand, I have a working Catalina on this BIOS version at the moment, I will try F5.Upgrade to the same BIOS/UEFI that CaseySJ used.
Also check that the settings in the BIOS are all changed in the same manner.
Also make note of step 7.Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580
CaseySJ's Comet Lake-S in BeQuiet! Pure Base 500DX: Gigabyte Z490 Vision-D - i5-10400 - UHD 630 - AMD RX 580 (Please do not quote this guide in its entirety. Post a link instead.) (See this post for how to refer to a Guide or Mini-Guide.) Refer to the Z390 Designare thread for answers to a...
Casey's guide has been thoroughly tested and proven to work. Follow everything in the guide.
- Joined
- Jun 9, 2011
- Messages
- 18
- Motherboard
- Gigabyte Z490 Vision D
- CPU
- i5-10600K
- Graphics
- RX 5500 XT
- Mac
- Mobile Phone
Updated my BIOS, Ventura is running. I cannot change CPU name nor can I log into Apple Music. iMessage works and my audio interface drivers work.
Edit: Apple Music Works
Edit: Apple Music Works
Last edited:
- Joined
- Oct 24, 2012
- Messages
- 56
- Motherboard
- Gigabyte Z490 VISION D
- CPU
- i7-10700K
- Graphics
- RX 5700 XT
- Mac
- Mobile Phone
Hi everyone,
I tried to figure out the problem by myself but my yet again disappointing brain miserably failed to come out with a bright solution.
All I can say is that my build (the one exhaustively documented and greatly supported by @CaseySJ here) has always worked until now, update after update, while at the same time maintaining my OpenCore up-to-date with the quite recent HackingDROM tool.
The system hangs a very long time at boot time but eventually reaches the log screen with no apparent graphical issue. The problem is that I can no more see my internal/external hard drives (even in disk utility) and my USB devices do not seem to be correctly detected either (e.g. my Logitech mouse can move the pointer but is no longer recognized by the Logitech driver).
I've attached a picture of the boot log in verbose mode. There is a lot of error messages but I am not even sure which is the one related to my issue. I have these ones:
AppleKeyStore:7633:162: unexpected session uid -1 requested by: AirPlayXPCHelper (162)
AppleKeyStore:12139:162: operation failed (sel: 7 ret: e00002c2, -1)
AppleKeyStore:12139:162: operation failed (sel: 7 ret: e00002f0, -1)
or this one:
AMFI: Launch Constraint Violation (not enforcing), error info: c[6]p[2]m[3]e[255] ...
or this one maybe (?):
connectx() - failed necp_set_socket_domain_attibutesAppleUSBTopCaseHIDDriver:0x100000587 open by IOHIDLibUserClient:0x1000007ec
My system was perfectly stable before that happens. I did not do any update. The thing is that I actually wanted to make the update to 14.4, so I first backed up my system on an external hard drive. Then the system became unresponsive when I ejected it (which happens very rarely), so I did a hard reset of the computer. This might have caused the issue.
Something different also came to my mind as the "AppleUSBTopCaseHIDDriver" identifier appears multiple times in the log: I played around with an online app named VIA (usevia.app) on Chrome, which is able to reconfigure the keys of (compatible) keyboards. I have installed Chrome especially for that occasion - Chromium based browsers are the only ones supporting that HID Driver thing feature. It worked out very well... but I am wondering if it could not have messed up with my drivers and conflict with my OC configuration.
Booting with my external backup drive (and using the external drive EFI OC) shows the same issue, which is not that surprising as resetting my computer was the very next thing I did after the successful backup operation - which btw might exclude that the issue was caused by the hard reset itself... but I am sure of nothing at this point.
I've also attached the EFI containing my OpenCore configuration... hope this helps.
Any help will be warmly and highly appreciated!
Thank you all in advance!
Little edit: The hard drives eventually show up in Finder (but not in disk utility) after a HUUGE time
(about 30 minutes).
I tried to figure out the problem by myself but my yet again disappointing brain miserably failed to come out with a bright solution.
All I can say is that my build (the one exhaustively documented and greatly supported by @CaseySJ here) has always worked until now, update after update, while at the same time maintaining my OpenCore up-to-date with the quite recent HackingDROM tool.
The system hangs a very long time at boot time but eventually reaches the log screen with no apparent graphical issue. The problem is that I can no more see my internal/external hard drives (even in disk utility) and my USB devices do not seem to be correctly detected either (e.g. my Logitech mouse can move the pointer but is no longer recognized by the Logitech driver).
I've attached a picture of the boot log in verbose mode. There is a lot of error messages but I am not even sure which is the one related to my issue. I have these ones:
AppleKeyStore:7633:162: unexpected session uid -1 requested by: AirPlayXPCHelper (162)
AppleKeyStore:12139:162: operation failed (sel: 7 ret: e00002c2, -1)
AppleKeyStore:12139:162: operation failed (sel: 7 ret: e00002f0, -1)
or this one:
AMFI: Launch Constraint Violation (not enforcing), error info: c[6]p[2]m[3]e[255] ...
or this one maybe (?):
connectx() - failed necp_set_socket_domain_attibutesAppleUSBTopCaseHIDDriver:0x100000587 open by IOHIDLibUserClient:0x1000007ec
My system was perfectly stable before that happens. I did not do any update. The thing is that I actually wanted to make the update to 14.4, so I first backed up my system on an external hard drive. Then the system became unresponsive when I ejected it (which happens very rarely), so I did a hard reset of the computer. This might have caused the issue.
Something different also came to my mind as the "AppleUSBTopCaseHIDDriver" identifier appears multiple times in the log: I played around with an online app named VIA (usevia.app) on Chrome, which is able to reconfigure the keys of (compatible) keyboards. I have installed Chrome especially for that occasion - Chromium based browsers are the only ones supporting that HID Driver thing feature. It worked out very well... but I am wondering if it could not have messed up with my drivers and conflict with my OC configuration.
Booting with my external backup drive (and using the external drive EFI OC) shows the same issue, which is not that surprising as resetting my computer was the very next thing I did after the successful backup operation - which btw might exclude that the issue was caused by the hard reset itself... but I am sure of nothing at this point.
I've also attached the EFI containing my OpenCore configuration... hope this helps.
Any help will be warmly and highly appreciated!
Thank you all in advance!
Little edit: The hard drives eventually show up in Finder (but not in disk utility) after a HUUGE time
(about 30 minutes).
Last edited:
CaseySJ
Moderator
- Joined
- Nov 11, 2018
- Messages
- 22,224
- Motherboard
- Asus ProArt Z690-Creator
- CPU
- i7-12700K
- Graphics
- RX 6800 XT
- Mac
- Classic Mac
- Mobile Phone
@maeluse,
Which version of macOS are you running at this time? You indicated an interest in upgrading to 14.4, but did not mention which version is currently in use.
I am experiencing the same or similar issue with 14.4 on my Z390 Designare in that the boot process begins normally with the Apple logo and progress bar, but the bar pauses midway for what seems like 30-60 seconds, then continues normally and completes successfully.
I haven’t noticed any issues with internally installed SSDs being recognized or recognized after a few minutes. All internal drives are mounted right away, but the boot delay is there.
I will troubleshoot the boot delay and see if any solution I find on my Designare might apply to the Z490 Vision D.
Which version of macOS are you running at this time? You indicated an interest in upgrading to 14.4, but did not mention which version is currently in use.
I am experiencing the same or similar issue with 14.4 on my Z390 Designare in that the boot process begins normally with the Apple logo and progress bar, but the bar pauses midway for what seems like 30-60 seconds, then continues normally and completes successfully.
I haven’t noticed any issues with internally installed SSDs being recognized or recognized after a few minutes. All internal drives are mounted right away, but the boot delay is there.
I will troubleshoot the boot delay and see if any solution I find on my Designare might apply to the Z490 Vision D.
Last edited:
- Joined
- Oct 24, 2012
- Messages
- 56
- Motherboard
- Gigabyte Z490 VISION D
- CPU
- i7-10700K
- Graphics
- RX 5700 XT
- Mac
- Mobile Phone
Sonoma 14.3.1. The latest official macOS release before 14.4 if I'm not mistaken.
As I mentioned, I am wondering what caused the issue, as after I have updated to 14.3.1 back then everything went well. My OC configuration hasn't changed either as far as I can remember.
My issue looks strangely like this one, however disabling all kext related to Bluetooth/WIFI did not help in my case. I need to double check that though.
Last edited:
- Joined
- Oct 24, 2012
- Messages
- 56
- Motherboard
- Gigabyte Z490 VISION D
- CPU
- i7-10700K
- Graphics
- RX 5700 XT
- Mac
- Mobile Phone
@CaseySJ,
I've found the source of the problem... and that's kinda insane: below the photo of the "murder weapon".
How did I figure it out? by chance... I was searching for some clues in Hackintool, whether some device id names may match the ones in my boot log. Then I thought that the hexa device id of my USB Hub plugged to one of my USB3 ports had a match, but there was probably nothing related. Anyway, I restarted my computer without the USB Hub et voilà: problem fixed!
I just felt so stupid not to have first disconnected any external USB devices thus filtering out that kind of incompatibilities before starting to play around with OC. The error messages were so misleading though, that the fact a USB stick could cause that problem did not even cross my mind... especially as that USB stick was already plugged in and was operational before the issue occurred.
I found out that the stick was responsible because it was the only device from my hub, which did not show up when I hot plugged the hub again. Then I tried on my MacBook: same issue. Something interesting occurred on my Windows when I tried to plug it: I got the "new device detected" window popping up every second and looping for ever... I guess that a similar phenomenon occurred in the macOS boot sequence.
The stick sit just beside the external hard drive I used for the backup (the one I did not eject properly). My guess is that the improper unplug of the hard drive potentially created an electric charge, which affected the stick on the next port... that's just a vague assumption though, anyway...
Don't buy that stick!
I've found the source of the problem... and that's kinda insane: below the photo of the "murder weapon".
How did I figure it out? by chance... I was searching for some clues in Hackintool, whether some device id names may match the ones in my boot log. Then I thought that the hexa device id of my USB Hub plugged to one of my USB3 ports had a match, but there was probably nothing related. Anyway, I restarted my computer without the USB Hub et voilà: problem fixed!
I just felt so stupid not to have first disconnected any external USB devices thus filtering out that kind of incompatibilities before starting to play around with OC. The error messages were so misleading though, that the fact a USB stick could cause that problem did not even cross my mind... especially as that USB stick was already plugged in and was operational before the issue occurred.
I found out that the stick was responsible because it was the only device from my hub, which did not show up when I hot plugged the hub again. Then I tried on my MacBook: same issue. Something interesting occurred on my Windows when I tried to plug it: I got the "new device detected" window popping up every second and looping for ever... I guess that a similar phenomenon occurred in the macOS boot sequence.
The stick sit just beside the external hard drive I used for the backup (the one I did not eject properly). My guess is that the improper unplug of the hard drive potentially created an electric charge, which affected the stick on the next port... that's just a vague assumption though, anyway...
Don't buy that stick!
Last edited: