Contribute
Register

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

Hey Casey,

Its stated in post Repository of Thunderbolt Bus Activation SSDTs that we can activate the GPIO Force Power with grubshell, it would be cool if that "How to" is also linked to that post, no?

The option without flashing to modded Bios F22i that is.

Thanks!
The preferred option is to install the modified firmware that provides GPIO Force Power option and CFG-Lock option:
 
ok, really need some guidance. after installing Big Sur (external usb drive) I removed it to see if everything would be like pre install. I.E. open core booting to Catalina and windows 10. I was able to see Catalina in the menu but 10 was gone. after a couple of reboots I cleared the nvram. this made a huge mess somehow.

now, not only do I only see the Catalina install, it doesn't even work. looking in the bios, I no longer see my UEFI versions of my evo drives. Well I do see 1 but not sure which it is. opencore is listed in the boot menu as well? not sure that this is correct.

also, I did try to to a fresh install just to see if I can get to a point to see my drives. All installers stop at the apple screen (no progress bar)

I reset bios to optimize defaults, but still nothing. anyway not sure what happened, but something low level occurred and before I take the last option of clearing cmos, im wondering if there's any other steps. As I said I would really like to keep my windows drive functioning.
Please try two things one by one:
  1. Shutdown the system and flip power switch on PSU to OFF for 10 seconds. Then restart and see if your Catalina and Windows 10 drive options reappear.
  2. If they do not, then perform a CMOS Reset.
    • It will be necessary to reconfigure BIOS parameters, starting with Save & Exit --> Load Optimized Defaults
    • It will also be necessary to unlock MSR 0xE2 unless you're running BIOS F9g or F9h
 
Just a quick side note:
AppleTV app is now available on many 2018 and newer LG OLED and LG NanoCell TVs. It's a TV-focused app as it should be; hence no apps and games. The interface is quite well done -- very close to a real AppleTV.

IMG_1966-sm.jpg IMG_1967-sm.jpg IMG_1970-sm.jpg IMG_1971-sm.jpg IMG_1969-sm.jpg
 
Last edited:
Hello,@CaseySJ

Can you find the original firmware of the ASUS Thunderbolt 3 card NVM26? I plan to compare it with the Mod version, because the built-in Thunderbolt main controller on my motherboard is DSL6540, which is the same as the ASUS Thunderbolt 3 card. You helped me before The modified firmware, I looked at it is based on the modified bytes of JHL6540.

Thanks!
 
Hello,@CaseySJ

Can you find the original firmware of the ASUS Thunderbolt 3 card NVM26? I plan to compare it with the Mod version, because the built-in Thunderbolt main controller on my motherboard is DSL6540, which is the same as the ASUS Thunderbolt 3 card. You helped me before The modified firmware, I looked at it is based on the modified bytes of JHL6540.

Thanks!
Sure, attached is the original NVM 26 from ASUS ThunderboltEX-3. (Credit: @NorthAmTransAm)
 

Attachments

  • OEM-ASUS-TBEX3-NVM26.bin.zip
    147.3 KB · Views: 55
Finally got around to testing something I assumed would work and be more native than a patch.

Instead of setting ThirdPartyDrives to true, we can set EnableTRIM=0x01 in NVRAM. This is what running trimforce enable does and I believe I saw some OC guide/documentation recommending that.

I like this because it's more native than a patch (I doubt the patch adds any bugs), and setting it in OC means clearing NVRAM won't require rerunning trimforce again (which forces an immediate reboot).

This makes my Samsung 860 Evo SATA drives get TRIM support (I excluded the other entries here).

Code:
            <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
            <dict>
                <key>EnableTRIM</key>
                <data>AQ==</data>
            </dict>
 
Hey @CaseySJ ,

Not sure if you remember my situation, but I was having major power issues with my Z390 Designare build. Process of elimination kept pointing to the Fenvi but I still swapped a bunch of components over the last few months to test. Turns out it did end up being the Fenvi cards afterall (tried multiple t919s and an HB1200). Just swapped in the YOUBO yesterday and it is now powering on/running flawlessly.

Wanted to just add another voice here saying that it is solving strange power issues where the other cards failed.

Many thanks to you and the others who discovered this card!
 
Hey @CaseySJ ,

Not sure if you remember my situation, but I was having major power issues with my Z390 Designare build. Process of elimination kept pointing to the Fenvi but I still swapped a bunch of components over the last few months to test. Turns out it did end up being the Fenvi cards afterall (tried multiple t919s and an HB1200). Just swapped in the YOUBO yesterday and it is now powering on/running flawlessly.

Wanted to just add another voice here saying that it is solving strange power issues where the other cards failed.

Many thanks to you and the others who discovered this card!
Glad to hear it and I must admit the rate of issues on other cards is alarming. I've already added a note at the top of the Z490 Vision D thread, and will do the same for this thread momentarily.
 
@CaseySJ Well odds are good the freezes are due to bad RAM. Hundreds of errors in about 45 minutes of MemTest86.

I remember the Corsair Vengeance LPX had a lot of people at once here get bad RAM, though mine did a full test without a single error. This though is bad within 6 months. Going to try to get it replaced now.
G.SKILL Ripjaws V Series 128GB (4 x 32GB) F4-3200C16Q-128GVK
 
@CaseySJ Well odds are good the freezes are due to bad RAM. Hundreds of errors in about 45 minutes of MemTest86.

I remember the Corsair Vengeance LPX had a lot of people at once here get bad RAM, though mine did a full test without a single error. This though is bad within 6 months. Going to try to get it replaced now.
G.SKILL Ripjaws V Series 128GB (4 x 32GB) F4-3200C16Q-128GVK
Looks like certain Fenvi WiFi cards and Corsair Vengeance LPX DIMMs are exhibiting unusually high number of issues, although all six of my Fenvi cards have never failed. And although I primarily use G.Skill, Silicon Power, and Team Force DIMMs, I do have a couple pairs of Corsair Vengeance LPX modules that have been just as reliable. Alas, failures do occur and the laws of statistics guarantee that failures will continue to occur on just about every product. Failures can be due both to manufacturing issues and operational issues.
 
Back
Top