Contribute
Register

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

One last question. In the BIOS what difference does setting Windows 8/10 Features to Windows 8/10 do versus Other OS?
I can boot and use the computer apparently in the same way with both on OC 0.6.0.
 
ndrik said:
One last question. In the BIOS what difference does setting Windows 8/10 Features to Windows 8/10 do versus Other OS?
I can boot and use the computer apparently in the same way with both on OC 0.6.0.
Click to expand...
Dortania and others are now recommending Windows 8/10 when using OpenCore. This is good for dual boot systems. Also, all of the SSDTs now contain:
Code: 
if (_OSI("Darwin"))
{
   // then do stuff for Mac
}
else
{
  // do stuff for other OS's
}
... which better supports multiple operating systems.
 
ndrik said:
I tripled checked, followed your guide and the NVRAM one, checked the /etc/ folder, but had nothing there.
It took me 2 days, and my system now boots on OC 0.6.0 and works as it did before, flawlessly with TB and I can hot swap my Apollo 8P with no issue.

For those coming after me, read EVERY single one of the steps and never assume because you've done it before it'll be easy.

Thank you for your help and sharing your knowledge.
Click to expand...
Before starting to build a Hackintosh I read this thread for a month, so 2 days is okay haha
 
CaseySJ said:
*** Micro-Guide: Installing Catalina using OpenCore ***
Please do not quote this guide in its entirety. Post a link instead.​
...
Click to expand...
@casey: first of all, thanks for a detail guide.
I am still in Download Catalina step, I've spent last 4 hrs with this and haven't finished. It's extremely slow, I had to kill few times and restarted. As you said the wait is about 15-20 mins, I waited for 40 mins, the most files downloaded are 9 out of 11. Wondering if you know any other download methods beside this. Thanks!
 
PTuser said:
Hi @c0c0p0ps - Im also on clover - I checked both our ssdts yesterday and found a few lines on yours that weren't in mine (ethernet wake string) - copied them into mine - theres a definite improvement on boot now - it did fail to sort up once but three boots in a row with no issues - so thanks - getting there - may not need to re flash...
Click to expand...
Glad it was some help to you although all credit goes solely to the Casey and the other clever folks who put together that SSDT.

I reckon it is still worth flashing your card with the Elias64 NVM23 even if you don’t want to go for the Designare NVM33. After all DSM2 himself started sharing and posting the Elias version as an ‘updated’ release of his original so obviously recognised there were improvements.
 
Pro Tools | Titan Ridge | 9900KS | Z370
ROG MAXIMUS X HERO |  i9 Other |  RX 580 Pulse 8GB
CaseySJ said:
Some comments / questions:
  • The screenshot shows 10 lighting channels.
  • Were all lighting channels turned on when the capture was taken? All channels can be set to Static or Fixed color while WireShark is capturing traffic. But if all channels were on, then no need to re-capture. Nevermind: I see that SYNC was enabled, hence all channels driven!
  • If all channels were on, I'm seeing the following Channel Addresses:
    • 0x20 0xFF
    • 0x20 0x00
    • 0x20 0x01
    • 0x21 0x02
    • 0x22 0x04
    • 0x23 0x08
    • 0x24 0x10
    • 0x25 0x20
    • 0x26 0x40
    • 0x27 0x80
  • The two channels in red are the ones missing from the RGB Fusion driver.
I've modified the rgb_fusion2 driver (attached) by adding led9 and led10. To test this, please backup the existing rgb_fusion2.py from the following directory (if you installed via Homebrew) and replace with attached version. Replace "1.4.1" with the actual version you're using.
Code: 
/usr/local/Cellar/liquidctl/1.4.1/libexec/lib/python3.8/site-packages/liquidctl/driver
Then try running:
Code: 
liquidctl -m Gigabyte set led9 color fixed FF0000
liquidctl -m Gigabyte set led10 color fixed 00FF00
Are you able to set all of the lighting channels now?
Click to expand...

Hi Casey,

Thanks a million for putting this together :)

It appears to be working for the most part, a few odd observations however.

led10: this is working and controls the edge lighting on the mb.
led9: I do not notice any change and I suspect that this channel controls any RGB device connected to one of the RGB headers on the MB. Currently the (led5) channel is connected to the LED_C1 header on my MB. I will see if I can plug in a device to the LED_C2, D_LED1 & 2 to see if the led9 channel affects these.

Another observation:

currently I use led1 to control the lighting on the IO panel, any changes made using led1 only affect the lighting on the IO Panel whereas using the newly created led10, any changes made to led10 not only change the MB edge lighting but also change the lighting on the IO Panel.

Here is a better list of what I am injecting and what it controls now with the new experimental driver:

# Led1 is the lighting around the io panel
liquidctl -m Gigabyte set led1 color fixed 01cdfe

# Led2 is the lighting of the XMP logo - top right of MB (I have amended this to be the lighting behind the XMP logo and not actually the MB edge lighting as previously stated, it only appeared to be the start of the edge lighting as it had some light bleed through to that section)
liquidctl -m Gigabyte set led2 color fixed be29ec

# Led3 is the Aorus Logo Top Right
liquidctl -m Gigabyte set led3 color fixed be29ec

# Led4 is the ESS Sabre HIFI Logo
liquidctl -m Gigabyte set led4 color fixed be29ec

# Led5 is the LED_C1 Onbaord RGB Header (Power Supply)
liquidctl -m Gigabyte set led5 color fixed 01cdfe

# Led7 is the NVME SSD Covers
liquidctl -m Gigabyte set led7 color fixed 01cdfe

# Led9 (At this stage I cannot see what it is affecting, more investigation needed)

# Led10 is the MB edge lighting (controls the entire lighting strip that runs along the RHS edge of the MB) However, any changes made here also change the IO panel lighting (Led1) at the same time although changes made to Led1 do not affect Led10
 
Lukey1979 said:
...
Here is a better list of what I am injecting and what it controls now with the new experimental driver:

# Led1 is the lighting around the io panel
liquidctl -m Gigabyte set led1 color fixed 01cdfe

# Led2 is the lighting of the XMP logo - top right of MB (I have amended this to be the lighting behind the XMP logo and not actually the MB edge lighting as previously stated, it only appeared to be the start of the edge lighting as it had some light bleed through to that section)
liquidctl -m Gigabyte set led2 color fixed be29ec

# Led3 is the Aorus Logo Top Right
liquidctl -m Gigabyte set led3 color fixed be29ec

# Led4 is the ESS Sabre HIFI Logo
liquidctl -m Gigabyte set led4 color fixed be29ec

# Led5 is the LED_C1 Onbaord RGB Header (Power Supply)
liquidctl -m Gigabyte set led5 color fixed 01cdfe

# Led7 is the NVME SSD Covers
liquidctl -m Gigabyte set led7 color fixed 01cdfe

# Led9 (At this stage I cannot see what it is affecting, more investigation needed)

# Led10 is the MB edge lighting (controls the entire lighting strip that runs along the RHS edge of the MB) However, any changes made here also change the IO panel lighting (Led1) at the same time although changes made to Led1 do not affect Led10
Click to expand...
Thank you for the detailed map. Some questions/suggestions:
  • Are any motherboard LEDs not being addressed by one of the channels now? (It seems we got them all despite the issue with LED10.)
  • To troubleshoot LED10 it would be helpful to do the following in Windows:
    1. Run the Gigabyte RGB Fusion app but do not run WireShark.
    2. Turn off all lighting channels.
    3. Now run WireShark and begin capture.
    4. Turn on the motherboard edge lighting only -- simply set it to Static color (without using the sync channel)
    5. Then turn off the motherboard edge lighting.
    6. Then turn it on again (same static color).
    7. Stop WireShark capture and upload the capture file.
 
tern said:
@casey: first of all, thanks for a detail guide.
I am still in Download Catalina step, I've spent last 4 hrs with this and haven't finished. It's extremely slow, I had to kill few times and restarted. As you said the wait is about 15-20 mins, I waited for 40 mins, the most files downloaded are 9 out of 11. Wondering if you know any other download methods beside this. Thanks!
Click to expand...
The total byte count is almost 8GB so it may take some time depending on your download speeds, your region, and the load on Apple's servers.
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top