trx40 [Discussion] - TRX40 Bare Metal - Vanilla Patches

[fabiosun]

 

All is working (Kernel patches are good again)

[valmeida]

I'm running out of ideas. I bought the Fenvi  T919 hoping  I can finally get Monterey working. It works flawlessly with Bigsur from wifi, Bluetooth , and even Airdrop. I can not get to load on Monterey and Ventura. I see it on the PCI list on Hakintool. Any ideas I do have the internal Bluetooth and wifi card disable.  

EFI.zip

[jsl2000]

9 hours ago, fabiosun said:

In order to get software update from Ventura beta 1 to beta 2 my Ryzen 1700X hackintosh must change SMBIOS from MP7, 1 to iMac19,2.

[fabiosun]

2 hours ago, jsl2000 said:

In order to get software update from Ventura beta 1 to beta 2 my Ryzen 1700X hackintosh must change SMBIOS from MP7, 1 to iMac19,2.

SecureBootModel was set to Default?

[iGPU]

11 hours ago, valmeida said:

I'm running out of ideas. I bought the Fenvi  T919 hoping  I can finally get Monterey working. It works flawlessly with Bigsur from wifi, Bluetooth , and even Airdrop. I can not get to load on Monterey and Ventura. I see it on the PCI list on Hakintool. Any ideas I do have the internal Bluetooth and wifi card disable.  

EFI.zip 4.11 MB · 0 downloads

 

Despite people saying these cards work OOB, I've never found that to be true. The Fenvi T919 works just fine in Mojave through Ventura, but you need different kext files based on the OS version. For Monterey and Ventura you need the following:

 

[fabiosun]

1 hour ago, iGPU said:

The Fenvi T919 works just fine in Mojave through Ventura, but you need different kext files based on the OS version. For Monterey and Ventura you need the following:

 

I am using this:

https://www.amazon.it/gp/product/B089Q86SJD

 

no kext needed here

Is it the same board you use?

Last login: Thu Jun 23 11:08:03 on console
fabio@Mac-Pro ~ % kextstat | grep -v com.apple
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
   54    3 0                  0x2f000    0x2f000    as.vit9696.Lilu (1.6.1) E4CEEFB2-3C86-3E06-BAF2-8CE8B8509794 <9 7 6 3 2 1>
   55    0 0                  0xd000     0xd000     as.vit9696.RestrictEvents (1.0.8) 62515DC0-83EF-3625-887D-48C7E37E7D93 <54 9 7 6 3 2 1>
   56    0 0                  0x20000    0x20000    wtf.spinach.AMDRyzenCPUPowerManagement (0.7) 10AE6854-47D8-3FE6-B1D3-66937EF615EF <54 17 13 9 7 6 3 2 1>
   65    0 0                  0x1a000    0x1a000    as.vit9696.VirtualSMC (1.3.0) 1A588100-2B4E-367C-A317-7D697730B3A3 <54 16 9 7 6 3 1>
fabio@Mac-Pro ~ %

 

 

Edited June 23, 2022 by fabiosun
pictures added

[iGPU]

9 hours ago, fabiosun said:

 

I am using this:

https://www.amazon.it/gp/product/B089Q86SJD

 

no kext needed here

Is it the same board you use?

Last login: Thu Jun 23 11:08:03 on console
fabio@Mac-Pro ~ % kextstat | grep -v com.apple
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
   54    3 0                  0x2f000    0x2f000    as.vit9696.Lilu (1.6.1) E4CEEFB2-3C86-3E06-BAF2-8CE8B8509794 <9 7 6 3 2 1>
   55    0 0                  0xd000     0xd000     as.vit9696.RestrictEvents (1.0.8) 62515DC0-83EF-3625-887D-48C7E37E7D93 <54 9 7 6 3 2 1>
   56    0 0                  0x20000    0x20000    wtf.spinach.AMDRyzenCPUPowerManagement (0.7) 10AE6854-47D8-3FE6-B1D3-66937EF615EF <54 17 13 9 7 6 3 2 1>
   65    0 0                  0x1a000    0x1a000    as.vit9696.VirtualSMC (1.3.0) 1A588100-2B4E-367C-A317-7D697730B3A3 <54 16 9 7 6 3 1>
fabio@Mac-Pro ~ %

 

 

 

I've used that AIC and the Fenvi T919, both in the TRX40 and Z690 builds, and each build seems to worksbest if I used extra kexts, esp to get AirDrop working.

 

[fabiosun]

@iGPUi use AirDrop feature only to copy files from my iPhone to my hack so I can’t say if it could have some problem in other tasks

 

if you have some thing to try to understand where bt fails without  additional kexts I will try it

 

thank you

@valmeidaptoblems seems a bit complicated

and I can’t say why it is not working at all for his system

[iGPU]

I've been having issues with USB-C drives not mounting (appearing) on the desktop under Ventura. There are zero problems with previous macOSes. 

 

See this post here and here for my initial comments. I posted on the InsanelyMac forum as I thought it was a Z690 issue but when testing on the TRX40, I had the same problem (again, only with Ventura).

 

As shown below in the Hackintool USB section, the USB stick does appear on the desktop, while the external USB-C drive, whether I use a USB-C to USB-C or USB-C to USB-3 cable, does not appear on the desktop. Since the USB-C drive is shown as active within Hackintool (and I get the ejection error if I un-plug it), macOS Ventura is aware of the drive, but yet oddly, the drive does not appear on the desktop.

 

It does not seem to matter which port I put the USB-C into, it does not appear on the desktop, while the USB3 stick does appear, when using the same port.

 

While one response I got from someone on the InsanelyMac forum thought it was a USBMap kext problem, I tried different approaches and had the same result. Furthermore, no USBMap kext are even used on my TRX40 build as no USB device natively has more than 15 ports (therefore none are required).

 

 

 

Adding the following Quirks did not help.

 

 

[fabiosun]

 

Senza titolo is connected to USB c back in my motherboard it is a SSD 240 Gb..it seems I can't see it in Hackintool if I am not wrong or I need of an Oftalmic Specialist!

🙂

 

 

 

[fabiosun]

 

and this is a 64 USBc pen

[iGPU]

 

The USB-C mounting just got more confusing. I have a couple other USB-C drives, all by different companies and each with different macOSes on them. My initial tests were performed with the SSK Media drive that contains Monterey.

 

It turns out that the different drives all behave differently between Big Sur and Ventura. The differences are summarized in the table below. There are differences between Big Sur vs Ventura but fortunately the Z690 and TRX40 mobos behave the same.

 

 

So there are some differences with Ventura, as shown in red box above. The ASMedia drive is the odd one, since it won't mount on either platform in either OS (I now don't recall when I formatted it and installed Big Sur; maybe it was on a Z390 build).

 

Based on these findings, I don't know which is affecting the mounting: a manufacturer's problem or the macOS on the drive problem. It seems that I'll need to format the bottom 2 drives (ASMedia and SSK) to see if, as empty drives, they will mount in Big Sur and Ventura. If they do mount then the macOS is affecting the mounting.

 

BTW, all 3 drives mount on my real Mac laptop that is running Big Sur without any problems. The screen shots in Spoiler below were taken on the laptop.

 

*****

 

Spoiler: drive manufacturer and macOS:

Spoiler

 

The JMicron Tech drive contains Mojave:

 

 

The ASMedia (ASMT) contains Big Sur:

 

 

and the SSK Media contains Monterey:

 

 

 

 

 

 

 

[fabiosun]

https://www.macos86.it/applications/core/interface/file/attachment.php?id=40594

 

added in OP a working EFI with macOS Ventura 13.0 (B1 and B2)

Thanks @jsl2000and @carlo_67for some hints!

 

I do not advise to use Clover in latest its release (5145/5146) it could corrupt your working NVRAM till you reset Cmos

 

[valmeida]

I tried moving the Fenvi t919 to every PCIE slot and even when as far as buying another similar wireless card with and NVME adapter to see if it will work on Monterey and no luck . Works great in all the enclosures and pcie slots with Big Sur but can seem to get it working in Monterey 🤬🤬🤬🤬🤬  

[valmeida]

On 6/26/2022 at 12:57 PM, fabiosun said:

https://www.macos86.it/applications/core/interface/file/attachment.php?id=40594 2.93 MB · 10 downloads

 

added in OP a working EFI with macOS Ventura 13.0 (B1 and B2)

Thanks @jsl2000and @carlo_67for some hints!

 

I do not advise to use Clover in latest its release (5145/5146) it could corrupt your working NVRAM till you reset Cmos

 

I'm going to try the clover bootloader to see if fixes my ethernet issues. 

 

[fabiosun]

34 minutes ago, valmeida said:

I'm going to try the clover bootloader to see if fixes my ethernet issues. 

no nnot use it it is not fixable with only a bootloader chngement

[valmeida]

1 hour ago, fabiosun said:

no nnot use it it is not fixable with only a bootloader chngement

So I should not use Clover 🍀 . Ok

 

[valmeida]

Im open to suggestions .

[valmeida]

 

Can someone help me force my USB ethernet adapter to show as built in device properties. This will help me greatly until I can figure out why I can't get Aquantia and Fenvi card to work in Monterey 

Victor’s IOREG Mac Pro.zip EFI.zip

[fabiosun]

13 hours ago, valmeida said:

Can someone help me force my USB ethernet adapter to show as built in device properties

i think this is not possible

For others problem if you have to use newer OSXs, i think you have to change your motherboard (crying only to think this but i cant see another solution)

 

[fabiosun]

@iGPUdo you remember when you studied motherboard bios related to not working USBC on thunderbolt?which differences between Designare trx40 and our MSI boards?

I remember you discovered something in the past about this subject

 

thank you

 

 

[iGPU]

4 hours ago, fabiosun said:

@iGPUdo you remember when you studied motherboard bios related to not working USBC on thunderbolt?which differences between Designare trx40 and our MSI boards?

I remember you discovered something in the past about this subject

 

thank you

 

 

 

As I recall it had to do with the original DSDT files for each mono being a little different. The mobos with internal TB had that device declared in the DSDT and I tried to add similar declarations to out mobos but it didn't work.

 

On another topic, when items are defined for RestrictEvents in the NVRAM section, the same items need to be Deleted. I'd over-looked that step and recently caught the resulting error. See image below. RestrictEvents works better when set up this way, deleting all items that were added.

 

 

[fabiosun]

macOS 13 beta 3 (22A5295h)

[fabiosun]

PS do not update 🙂

 

[fabiosun]

KernelCollections is changed

We all have a boot loop in early stage

Dev says is not a simple fix

They are working on it!