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

[Lensjocky]

CaseySJ & Friends,

My Hackintosh has started ejecting drives by itself since I updated to Monterey. I've updated my OC from .074 to .075 last week hoping that would help, but no the problem persists. It's pretty odd as a reboot usually solves the issue for a while. Not sure if it's a Software or Hardware issue, but it only started since MacOS 12.0.1

Any thoughts on troubleshooting anyone?

 

[wifinity]

*** Repository of Patched Thunderbolt Firmware Files ***
Please do not quote this post in its entirety. Post a link instead.​

...

HI CaseySJ,

I've flashed My Lenovo X1C6 Thunderbolt Winbond SPI-ROM using your "Lenovo-X1-Carbon-NVM-43-MOD-1-CaseySJ.bin" file.

My Laptop had the Thunderbolt SPI-ROM updated using the last Thunderbolt Firmware update from the Lenovo support site from April 2021 (n23th07w.exe file). This update has PD Firmware 6.31 and NVM 46, and your file has PD Firmware 6.15 and NVM 43.

Checking the Lenovo Version information:

VERSION INFORMATION

The following versions have been released to date.

Build ID Update tool Firmware Build NVM PD Firmware Rev. Issue Date
---------- ------------ -------------- --- ------------ ---- ----------
n23th07w 17.0.0.18 N23TF23W 46 F407.06.31 01 2021/03/17
n23th06w 17.0.0.12 N23TF22W 45 F407.06.29 01 2020/06/02
n23th05w 17.0.0.12 N23TF20W 43 F407.06.27 01 2020/04/06
n23th04w 17.0.0.10 N23TF20W 43 F407.06.27 01 2020/03/18
n23th03w 17.0.0.8 N23TF18W 43 F407.06.15 02 2020/01/22
n23th03w 17.0.0.8 N23TF18W 43 F407.06.15 01 2020/01/17
n23th02w 17.0.0.3 N23TF18W 43 F407.06.15 02 2019/07/05
n23th02w 17.0.0.3 N23TF18W 43 F407.06.15 01 2019/06/24
n23tf16w 17.0.0.1 N23TF14W 40 F407.06.12 01 2019/02/21
n23tf15w 1.0.12.0 N23TF13W 40 F407.06.12 02 2018/11/16
n23tf15w 1.0.12.0 N23TF13W 40 F407.06.12 01 2018/11/08
n23tf14w 1.0.10.0 N23TF12W 33 F407.06.12 01 2018/07/20
n23tf13w 1.0.7.0 N23TF12W 33 F407.06.12 01 2018/06/27
n23tf12w 1.0.3.0 N23TF12W 33 F407.06.12 01 2018/03/05

I suppose you used the N23TF18W firmware build as base file for creating your Lenovo-X1-Carbon-NVM-43-MOD-1-CaseySJ.bin mod file.

Looking for the Firmware version in the Thunderbolt/USB4 OSX System Info, after flashing SIP-ROM with your firmware mod file I can see this info:

Firmware version: 150043.0

And before flashing, it was:

Firmware version: 310046.0

The question is... maybe will be possible you create a new X1 Gen 6 Thunderbolt firmware moded based in the last N23TF23W Firmware Build.

You can download the Lenovo X1 G6 Thunderbolt firmware update file from Lenovo Support Site here: n23th07w.exe

Or you can download my Lenovo-X1-Carbon-NVM-46-PD-6.31.bin file reader directly from my SPI-ROM before flashing attached in this message.

Thank you very much for your help!

King regards,

David

PD: I'm using some custom SSDT you can download here. Maybe its not necessary patch thunderbolt firmware using this SSDT, and its better reflash again with the original NVM 46 firmware? I can see the Thunderbolt Bus always in System information, with original firmware or with your moded firmware.

My problem is I'm using a TB3 to TB2 Apple adapter -> TB2 to Fireware 800 Apple Adapter -> ECLER EVO5 Fireware Sound Card (using Core Audio because there no drivers from the Ecler manufacturer), and the audio play correctly, but in a few seconds, the audio is crappy, and I don't know how solve this. I was trying change clock to MAC instead DEVICE in the Apple Audio MIDI Settings application, but the system freeze if I change to MAC clock.

Actually I'm using MAC OS Monterey 12.0.1, but with Big Sur had the same issues.

 

[wifinity]

Hi again @CaseySJ,

I can't check if the new firmware solves the sound artifacts with my ECLER EVO5 SOUNDCARD because I don't have the device here for testing, (I've will check the next week), but I was compairing the original @contemporarygary Lenovo X1 Carbon 2018 Alpine Ridge.rom file with the Lenovo-X1-Carbon-NVM-43-PD-6.15.MOD-1-CaseySJ.bin file you sent him, I found this changes:

Offset 0x82035 Original = 2727 Mod file = 3737
Offset 0x82081 Original = A0 Mod file = 20

I've done this same changes in the original Lenovo-X1-Carbon-NVM-46-PD-6.31.bin file I sent you in same offsets (file attached).

I've flashed the file but with my moded file the drivers don't load, maybe the byte in 0x82081 offset is some checksum and the 20 value is wrong??.

Can you explain how can I mod the new firmware file correctly, and which is the purpose of this bytes changes in order to understand the magic?

Thanks very much to @CaseySJ and @Elias64Fr for your hard work looking solutions with the Thunderbolt firmwares!!

And another question for all tonymacx86 community, anybody have found any solution for solving the same sound artifacts problem with soundcard using Apple Core Audio?

I'm using this Evo 5 without any drivers, (only the Apple Core Audio) with no problems in some Hackintoshes and real macs.

I have only this Audio problem in my Lenovo X1 Carbon Gen 6 connecting like this:

Apple Thunderbolt 3 to 2 adapter -> Apple Thunderbolt 2 to Firewire 800 adapter -> Ecler Evo5 device

I'm not sure if the problem can be in the Thunderbolt Hack implementation, or simply for using this two adapters for having the firewire 800 I needed to connect to the soundcard.

Any help is welcome, Thanks to everybody!!

 

[CaseySJ]

On my backup machine (Z390 Aorus Pro) I had been using a PCI-e adapter card with a BCM943224 WiFi module, which no longer works in Monterey. Is there any OpenCore setting or workaround? I see that the OC legacy patcher has a fix but if I understand correctly that patcher is for use on older "real" Macs.
Thanks.

Although I’m not familiar with the OC legacy patcher, it’s certainly worth trying. The alternative of course would be a BCM94360 module such as Fenvi FV-T919.

 

[CaseySJ]

Hi @CaseySJ

Since upgrading to latest OC (0.7.4) and Monterey, PC will never sleep. When I hit sleep now, screen goes blank and then comes back a few seconds later. Per activity monitor, nothing is preventing sleep. Even if I log out and try sleeping, it will not work. I have also reverted OC to 0.7.3 and still have issues so I am thinking it is related to Monterey... I did not have these issues before upgrading, and everything is still the same as far as kexts, etc.

Is anyone else having similar issues? - could this be stemming from the SSDT-USBW.aml file?

sleep log shows these constant lines



@Inqnuam
It also looks like HackinDROM is removing and unable to see my custom USB kext even when it's in the EFI/Kext folder. But even after manually adding it via OpenCore Configurator and enabling, it still has same wakeup problem, so I do not believe that to be related, but still something that I noticed with HackinDROM.

It’s okay to uncheck both USBWakeFixup.kext and SSDT-USBW.aml (they work together), reboot, and check sleep behavior again. Sleep issues often require ‘process of elimination’ to identify the culprit. We should uncheck “Wake for network access” in System Preferences —> Energy Saver.

 

[wifinity]

Hi again @CaseySJ,

I can't check if the new firmware solves the sound artifacts with my ECLER EVO5 SOUNDCARD because I don't have the device here for testing, (I've will check the next week), but I was compairing the original @contemporarygary Lenovo X1 Carbon 2018 Alpine Ridge.rom file with the Lenovo-X1-Carbon-NVM-43-PD-6.15.MOD-1-CaseySJ.bin file you sent him, I found this changes:

Offset 0x82035 Original = 2727 Mod file = 3737
Offset 0x82081 Original = A0 Mod file = 20

I've done this same changes in the original Lenovo-X1-Carbon-NVM-46-PD-6.31.bin file I sent you in same offsets (file attached).

I've flashed the file but with my moded file the drivers don't load, maybe the byte in 0x82081 offset is some checksum and the 20 value is wrong??.

Can you explain how can I mod the new firmware file correctly, and which is the purpose of this bytes changes in order to understand the magic?

Thank you very much for your hard work looking solutions with the Thunderbolt firmwares!!

And another question for all tonymacx86 community, anybody have found any solution for solving the same sound artifacts problem with soundcard using Apple Core Audio?

I'm using this Evo 5 without any drivers, (only the Apple Core Audio) with no problems in some Hackintoshes and real macs.

I have only this Audio problem in my Lenovo X1 Carbon Gen 6 connecting like this:

Apple Thunderbolt 3 to 2 adapter -> Apple Thunderbolt 2 to Firewire 800 adapter -> Ecler Evo5 device

I'm not sure if the problem can be in the Thunderbolt Hack implementation, or simply for using this two adapters for having the firewire 800 I needed to connect to the soundcard.

Any help is welcome, Thanks to everybody!!

Finally checking your TitanRidgeNVM43-Elias64Fr-Mod.bin mod file I found in this case the bytes changes in offsets 0x4035 and 0x4081 instead 0x82035 and 0x82081. I can see the byte was 0x20 in 0x4081 like your x1 mod, so I've moded the bytes in the new offsets and now the drivers are loaded again:

Offset 0x4035 Original = 2727 Mod file = 3737
Offset 0x4081 Original = A0 Mod file = 20

This is the thunderbolt screenshots:

The PCI:

And the firewire working:

I've uploaded the new NVM 46 modded file in order to check if now the mod its ok.

Thanks again @CaseySJ!

Edit:

The Hotplug only is working with Assist mode Disabled.

This is my BIOS mod settings:

- Config - Thunderbolt (TM) 3 - Thunderbolt BIOS Assit Mode Disabled
- Config - Thunderbolt (TM) 3 - Security Level Not Security
- Config - Thunderbolt (TM) 3 - Support in Pre Boot Environment Pre-Boot ACL
- Advanced - Intel Advanced Menu - Firmware Configuration Test
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - Thunderbolt (TM) Support Enabled
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - Thunderbolt USB Support Disabled
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - Thunderbolt Boot Support Pre-Boot A
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - Titan Ridge Workaround for OSUP Disabled
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - Thunderbolt Detachable Graphics Support Disabled
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - AIC Support Enabled
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - AR AIC Support Enabled
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - Wake form Thunderbolt Devices X
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - GPIO3 Force Pwr X
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - GPIO3 Force Pwr for RP05 X
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - Skip PCI enumeration Enabled
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - Skip PCI OptiomRom Disabled
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - Skip PCI Interrupt Assignment Enabled
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - ACPI Removal Object Support Disabled
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - Security Level Not Security
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - Call pre boot SMI handler Disabled
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - SW SMI on TBT hot-plug Disabled
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - GPIO filter Disabled
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - ACPI Notify on TBT Hot-plug Enabled
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - MSI Enabled in FADT Enabled
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - Enable CLK Req Enabled
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - Enable ASPM Disabled
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - Enable LTR Disabled
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - TBT Port Root Selector AUTO
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - TBT Host Router Two port
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - Reserved I/O 0
- Advanced - Intel Advanced Menu - Thunderbolt (TM) Configuration - Thundetbolt (TM) OS Select - Enable + RTD3

Maybe, can I change some of this settings in order to get Hot-plug with Assist mode Enabled to get less power consumption?, or alway must be Assist mode Disabled?

Thanks again

 

[phrfpeixoto]

yes it does, it is on all systems

Indeed, I had looked in the wrong library folder.

Regardless,

...

The only differences I can see from one-another are:
- The new account was not an Admin
- My account has its home folder mapped to another Volume (Another APFS partition on the same disk)

I'll try to copy my data back to the system disk and undo that volume, and see if that makes any difference.

That last item seemingly did the trick: After a major hassle to switch my account's home folder back to /Users/peixoto, the computer now sleeps properly.

I find this VERY odd. The previous path was a volume within the system's container disk, named as Home (home dir was /Volumes/Home).
I originally did this move right before the BigSur upgrade - For the case I needed a clean install (that partition wouldn't be touched)

@CaseySJ Have you ever seen macOS installations/accounts with a different home folder? If so, did that cause any unwanted behavior?

I'll try and find some time to do the same on my real MacBook Pro running BigSur, and see what happens.

 

[Lukey1979]

Hi @CaseySJ I finally updated to OC 0.7.5 using the old manual method. Booted in Monterey OK however, both Ethernet ports on my Aorus Xtreme are not working. WiFI works OK and Bluetooth appears to be working fine. I'm wondering if I have missed something. ALL of my settings have been copied across to the new EFI this includes my ACPI folder. I haven't copied across the EFI to my main drive as yet as I wanted to make sure it was all working first. Has anyone else with the same MB experienced this?

 

[rondark]

Hi @CaseySJ
I am suffering from the Samsung 970 EVO (1 Tb) problem in Monterey. I bought a WD recommended SN 750 I TB to replace it.
I have searched and can't seem to find the proper method to clone the Samsung to the WD. I cloned using CCC - Samsung to WD. I then placed the EFI (OC .75) in the WD EFI partition. The WD is seen as uefi in the BIOS but it doesn't show up in the OC picker. However the old Samsung boot disc which I placed in a Sabrent Thunderbolt enclosure boots fine.
I also am not sure the Sabrent is connecting properly to Thunderbolt as I have previously only used the Thunderbolt ports for USB.

I have , again, probably done something stupid.

How should I proceed?

Thanks

 

[cylsfar]

Please post your config.plist with serial numbers removed from PlatformInfo section.

It's

i boot only with internal cpu graphics and it block