- Joined
- Oct 7, 2020
- Messages
- 28
- Motherboard
- Gigabyte designare z390
- CPU
- I7 9700K
- Graphics
- rx580
- Mac
- Mobile Phone
can you tell me which chip on the designare z390 to flash, can you take a picture of me so i can see for thunderbold ports. thank you
If you are using the USB-C to HDMI cable, then it's not just plug-and-play. In my previous reply I mentioned that it's necessary to change Platform ID to 0x3E9B0007.Hi @CaseySJ, it's been a very long time since I visited this forum, so I'm sure you already forgot the issue I had. Basically, at one point my hackintosh stopped being to able to wake from sleep (even though it worked seamlessly for about 6 months). Among your numerous suggestions, you proposed to try USB C to HDMI cable (I was using HDMI to HDMI) but I didn't have it. I finally got two of those, but unfortunately, monitors don't seem to be connected when I simply connect any of my monitors (the monitor indicators just keep on blinking). So my question might sound really dumb, but do I need to do anything else apart from just connecting the monitor (HDMI) to the video card (USB C)? I was under the impression that it's just plug and play.
By the way, it doesn't work on Windows too, which is installed on a separate SSD, meaning when I turn on the machine from a completely shut down state, nothing appears on the screen(s). Does that mean my Radeon RX580 is busted or something is configured incorrectly in BIOS?
Hello,
I've disconnected every usb device in my system, besides the mouse and the keyboard, including the Fenvi Card and the Corsair H115i, and the problem is reproduced at every reboot...
- Are you using a WiFi/BT card such as Fenvi FV-T919? Yes, the FV-HB1200
- Are there any other PCIe cards in the system? No
- Are there any Thunderbolt devices connected? No
- Is the Corsair H115i connected to the internal F_USB header? Yes
- are you using a Thunderbolt monitor or a standard HDMI/DisplayPort monitor? 2 4K DisplayPort monitors
It seems weird that I'm the only one having this problem, with two motherboards!
It's worth mentioning that this problem wasn't happening every time at the beginning, but now it is!
I have not seen this myself. In fact I just attempted a fresh Catalina 10.15.7 installation ten minutes ago and did not encounter this. A quick Google search found this, which you're welcome to try (or just format the new disk as MacOS Extended (Journaled)).@CaseySJ - so I built a new Install USB, config.plist and trying to install Catalina 10.15.7 on to an external drive. I get OC to boot, get to MacOS installer, format drive as GUID / APFS - but then when I get to Select the Disk for install all drives are greyed out and I get a message -
"Your mac needs a firmware update to install on this volume. Please select a Mac OS Extended (Journaled) volume instead."
View attachment 492745
Have you seen this before?
Have you looked at Quick Reference spoiler, section 8, as previously mentioned? Please take a look at the name of each entry in section 8.can you tell me which chip on the designare z390 to flash, can you take a picture of me so i can see for thunderbold ports. thank you
<key>Properties</key>
<dict>
<key>PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)/Pci(0x1,0x0)</key>
<dict>
<key>AAPL,slot-name</key>
<string>Internal@0,28,4/0,0/1,0</string>
<key>device_type</key>
<string>PCI bridge</string>
<key>model</key>
<string>JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016]</string>
</dict>
<key>PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>AAPL,slot-name</key>
<string>Internal@0,28,4/0,0/0,0</string>
<key>device_type</key>
<string>PCI bridge</string>
<key>model</key>
<string>JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016]</string>
</dict>
<key>PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>AAPL,slot-name</key>
<string>Internal@0,28,4/0,0/0,0/0,0</string>
<key>device_type</key>
<string>System peripheral</string>
<key>model</key>
<string>JHL6540 Thunderbolt 3 NHI (C step) [Alpine Ridge 4C 2016]</string>
</dict>
<key>PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)/Pci(0x4,0x0)</key>
<dict>
<key>AAPL,slot-name</key>
<string>Internal@0,28,4/0,0/4,0</string>
<key>device_type</key>
<string>PCI bridge</string>
<key>model</key>
<string>JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016]</string>
</dict>
<key>PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)/Pci(0x2,0x0)</key>
<dict>
<key>AAPL,slot-name</key>
<string>Internal@0,28,4/0,0/2,0</string>
<key>device_type</key>
<string>PCI bridge</string>
<key>model</key>
<string>JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016]</string>
</dict>
Thanks for your reply! Do I need to do the other steps you outlined or just changing the platform ID will suffice?If you are using the USB-C to HDMI cable, then it's not just plug-and-play. In my previous reply I mentioned that it's necessary to change Platform ID to 0x3E9B0007.
Another option is to install Mojave or Catalina from scratch on a spare SATA SSD (just a cheap 128GB or 256GB will work) and see if the sleep/wake problem occurs on a fresh installation.
I followed your process, handoff and Continuity Camera are working great, but when I try to activate the Unlock with Apple Watch, it said that the Mac couldn't communicate with the WatchPlease describe the problem(s) again in some detail. If the clock in BIOS does not change, how does that affect macOS?
In BIOS we can capture screenshots like this:
Insert FAT32 USB flash diskPress F12 to capture screenshot; it will be saved directly on FAT32 flash disk in BMP formatUse a photo editor like Pixelmator (or free Gimp) to convert BMP to JPEG and post the JPEG imageSo you could do something like this:
Update: I see that switching to OpenCore fixes this. For Apple Watch and Sidecar issues, please see Quick Reference spoiler:
Capture a screenshot of BIOS where the current time is displayedWait 5 minutes.Capture another screenshot of the same screen so we can see the new time
View attachment 492769
If you use a USB-C to HDMI cable or even a USB-C to DisplayPort cable then changing Platform ID to 0x3E9B0007 is sufficient. The on-board HDMI port will not work unless we apply framebuffer patches, but if you use USB-C ports instead of HDMI port (on the rear IO panel) then you can safely ignore the framebuffer patches and just avoid using the on-board HDMI port.Thanks for your reply! Do I need to do the other steps you outlined or just changing the platform ID will suffice?