Jump to content

fabiosun

Recommended Posts

DRIFTWOOD’S CURRENT USBTOOLBOX LAYOUT OF ASROCK TRX40 USB PORTS
FILE: ASROCK TRX40 CREATOR USB MAP - DRIFTWOOD.zip

 

AMD USB 3.10 extensible Host Controller 1.10 (Microsoft) | USB 3.0 (XHCI) | 4/4 ports

(WHERE: BACK MIDDLE - 2 TYPE A PORTS)

[#] 1. Port 1 | USB 2.0 | Type 0| Companion to 3.

[#] 2. Port 2 | USB 2.0 | Type 0| Companion to 4

[#] 3. Port 3 | USB 3.0 | Type 3 | Companion to 1

- Unknown Device operating at USB 1.1

[#] 4. Port 4 | USB 3.0 | Type 3| Companion to 2 

 
AMD USB 3.10 extensible Host Controller 1.18 (Microsoft) | USB 3.0 (XHCI) | 4/4 ports

(WHERE: BACK TOP - 2 TYPE A Ports)

[#] 5. Port 1 | USB 2.0 | Type 0 | Companion to 7 

[#] 6. Port 2 | USB 2.0 | Type 0 | Companion to 8

[#] 7. Port 3 | USB 3.0 | Type  3| Companion to 5

[#] 8. Port 4 | USB 3.0 | Type 3| Companion to 6


ASMedia USB 3.20 extensible Host Controller 1.10 (Microsoft) | USB 3.0 (XHCI) | 2/2 ports

(WHERE: BACK ASMEDIA USB-C PORT)

[#] 9. Port 1 | USB 3.0 (USB-C)| Type 10  | Companion to 10

Example  - USB DISK 3.1 operating at USB 3.1 Gen 2

[#] 10. Port 2 | USB 2.0 | Type 10  | Companion to 9


AMD USB 3.18 extensible Host Controller 1.18 (Microsoft) | USB 3.0 (XHCI) | 10/10 ports

(WHERE: FRONT PORTS - type A & USB-C)
[#] 11. Port 1 | USB 2.0 | Type 0

[#] 12. Port 2 | USB 2.0 | Type 0 

[#] 13. Port 3 | USB 2.0 | Type 0 

[#] 14. Port 4 | USB 2.0 | Type 0 

[#] 15. Port 5 | USB 2.0 | Type 255 / but maybe type 0| Companion to 17 

-USB Audio operating at USB 2.0 

[#] 16. Port 6 | USB 2.0 | Type 255 but maybe type 0| Companion to 19

[#] 17. Port 7 USB 3 / USB C | Type 10 / maybe type 3| Companion to 15
Example  - DISK 3.1 operating at USB 3.1 Gen 2 

[#] 18. Port 8 | USB 3.0 | Type 10 / maybe type 3 | Companion to 15

Example   - USB DISK 3.1 operating at USB 3.1 Gen 2

- Unknown Device operating at USB 1.1 

[#] 19. Port 9 | USB 3.0 | Type 3 | Companion to 16 FRONT TOP

[#] 20. Port 10 | USB 3.0 | Type 3 | Companion to 16  

 

AMD USB 3.10 extensible Host Controller 1.10 (Microsoft) USB 3.0 (XHCI) | 9/10 ports

(WHERE: BACK Bottom 2 USB PORTS)
[#] 21. Port 1 | USB 2.0 | Type 0 | Companion to 30

[#] 22. Port 2 | USB 2.0 | Type 0| Companion to 29

[ ] 23. Port 3 | USB 2.0 | Type 0| Companion to 28  TURN OFF - unused

[ ] 24. Port 4 | USB 2.0 | Type 0| Companion to 27 TURN OFF - unused

[ ] 25. Port 5 | USB 2.0 | Type 255 POSSIBLY LEAVE ON, CURRENTLY TURNED OFF

- LED Controller operating at USB 1.1

[#] 26. Port 6 | USB 2.0 | Type 255

 - BRCM20702 Hub operating at USB 1.1

- USB Input Device operating at USB 1.1

- USB Input Device operating at USB 1.1

- Unknown Device operating at USB 1.1

[ ] 27. Port 7 | USB 3.0 | Type 3 | Companion to 24 TURN OFF - unused

[ ] 28. Port 8 USB 3.0 | Type 3 | Companion to 23 TURN OFF - unused

[#] 29. Port 9 | USB 3.0 | Type 3 | Companion to 22

[#] 30. Port 10 | USB 3.0 | Type 3 | Companion to 21

  

 

Edited by Driftwood
Link to comment
Share on other sites

On 9/29/2021 at 11:22 PM, Driftwood said:

HOW TO INSTALL MONTEREY BETA 8 ON THREADRIPPER TRX40s

 

 

As you may have seen on OSX Discord server... last nights install of Monterey beta 8 didn't go to plan. It downloaded fine with j160 reboot, then when SBM=Disabled and Nvram reset, it wouldn't install beta 8 despite three re-download attempts too.

I didn't want to go the iMac17,1 way so I thought I would wait until a solution cropped up. Today, it did.

 

The new version of RestrictEvents Kext together with the latest Release candidate of OC 0.74 now works - and it won't upset your memory configuration (as set out by iGPU)

 

Here's the RestrictEvents kext, & download OC0.74: RestrictEvents.zip

Source: https://github.com/acidanthera/RestrictEvents/commit/2430ed06c15a9f3dd94634ab68e208c8b762e11d

 

This will negate the need to do anything like change your SMBIOS to iMac17,1 OR SBM=j160 🙂

 

Just install OC0.74, include the restrictEvents kext in your kext folder, then Propertree snapshot it into your config/EFI.

 

Reboot, it sees the update, installs, reboots just fine!

 

 

54135382_OC0.74LatestRelease.thumb.png.5783bffe96d0adc6f307be1ff378ab73.pngrestrictevents.png.a0e13f9cef5c553871112c1324efbe1a.png

1172817510_Downloadingbeta8.thumb.png.021ee14a74c1a0b07b49cecef5b36ea8.png1095291912_Screenshot2021-09-29at22_21_54.thumb.png.832a07e10b52377c9f36f6ca322ae19a.png

 

Job done.

 

 

I confirm the driftwood method with OpenCore 0.7.4 and RestrictEvents.Kext allows upgrading to Monterey Beta 8 without modifying the SMBIOS.

 

As I do not support the RestrictEvents memory layout information window, I used the boot argument: revnopatch = mempci to find the one for a 2019 Mac Pro.

After all I have a Mac Pro 2021🤪

1458868065_Capturedecran2021-10-02a19_28_39.thumb.png.750129bfe1f20bb25bcd135837b668fb.png

  • Like 2
Link to comment
Share on other sites

1 hour ago, Arrakis said:

I confirm the driftwood method with OpenCore 0.7.4 and RestrictEvents.Kext allows upgrading to Monterey Beta 8 without modifying the SMBIOS.

 

As I do not support the RestrictEvents memory layout information window, I used the boot argument: revnopatch = mempci to find the one for a 2019 Mac Pro.

After all I have a Mac Pro 2021🤪

1458868065_Capturedecran2021-10-02a19_28_39.thumb.png.750129bfe1f20bb25bcd135837b668fb.png

Yeah you're not forced to use RestrictEvents permanently. You can just use it to grab the updates/then disable the kext and then iGPU's 'MemoryDevices' method comes back... and do what you have done very elegantly!

Edited by Driftwood
Link to comment
Share on other sites

  • Supervisor

I do not use RestrictEvents.kext because it could create randomly some problem during booting stage,

I have it in the folder's kext because it helps to update from Monterey beta 7 to 8 without changing SMBIOS or Secure Boot Model parameter

I will see in the next beta if here will be the same

However my system is stable without it 100% so I do not use RE.kext

 

  • Like 2
Link to comment
Share on other sites

So the Titan Ridge Card v.2.0 finally arrived. I popped it in an in the PCI section of hardware I can already find it. Thunderbolt is empty.

 

I suppose it will not work without flashing the chips?

 

Also one question about iMessage: it worked for a few days now but now I cannot login anymore. Is this a known problem?

Edited by gosi
Link to comment
Share on other sites

  • Moderators
3 hours ago, gosi said:

So the Titan Ridge Card v.2.0 finally arrived. I popped it in an in the PCI section of hardware I can already find it. Thunderbolt is empty.

 

I suppose it will not work without flashing the chips?

 

Also one question about iMessage: it worked for a few days now but now I cannot login anymore. Is this a known problem?

 

Correct, you need to flash _a_ chip.

 

iMessage requires proper log in to iCloud with your Apple ID. Sometimes signing in and out of App Store or Music app helps. Also, you need to have (one) internet connection assigned "en0".

 

318057541_ScreenShot2021-10-06at8_27_53PM.thumb.png.43048bdb3c9a52f97025f587223b9543.png

 

How to re-set to "en0" has been discussed before, but in case you've forgotten:

 

Spoiler

Re-set “en0” ethernet configuration from Terminal, then re-boot computer:

 

sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist

 

Link to comment
Share on other sites

  • Supervisor

Every now and then, since Monterey beta 6, this happens on my system with a percentage of 1 boot not working with 10 working

it would appear to be tied to the network card after the attached color screen, which appears in my monitor connected in hdmi

both monitors go to black screen with signal

I can't say it with extreme certainty but before beta 6 it didn't happen and the same didn't happen with Big Sur

Maybe it will be a SIP problem?

 

2082699249_Screenshot2021-10-07at08_34_03.thumb.png.482ee4c508e5d24633c04b183b6883c5.png

mmmmm

BYS4 should be intel Ethernet I think..and it is not connected (also no kext installed for it)

Link to comment
Share on other sites

  • Moderators
25 minutes ago, fabiosun said:

Every now and then, since Monterey beta 6, this happens on my system with a percentage of 1 boot not working with 10 working

it would appear to be tied to the network card after the attached color screen, which appears in my monitor connected in hdmi

both monitors go to black screen with signal

I can't say it with extreme certainty but before beta 6 it didn't happen and the same didn't happen with Big Sur

Maybe it will be a SIP problem?

 

2082699249_Screenshot2021-10-07at08_34_03.thumb.png.482ee4c508e5d24633c04b183b6883c5.png

mmmmm

BYS4 should be intel Ethernet I think..and it is not connected (also no kext installed for it)

 

BYS4 is the location of my internal AX200 card, which can appear as an ethernet access. (I use a section of a USB port SSDT file to cancel this card.) 

 

But I thought your mobo has no Wifi card.

 

Are you using an SSDT, DevProp, or kext file (with its Info.plist file containing a definition) with BYS4?

 

Link to comment
Share on other sites

  • Supervisor

by now I have disabled them from Bios

I will test for some days in this condition, today I have had no problem in this condition

Will see if it is enough

if it works I will test re enabling them in bios and using Smaltree kext

 

thank you

 

  • +1 1
Link to comment
Share on other sites

  • Moderators
5 hours ago, fabiosun said:

@iGPUand @all 6900xt owners..

take a look to this thread (hackintosh-forum.de)

I have lowered my max GPU temps of about 10 degrees only loosing a bit of performances in my task (thanks to Aluveitie and his SoftPowerPlay for device properties)

 

PowerPlayTable thread

 

 

 

@fabiosun 

 

I did similar DevProp for Vega56, Vega64 and Radeon VIIs.

 

I don't see the actual PPTable data; where are did you get it (or can you post the code in a spoiler on this thread)? Thanks.

 

[I don't have Windows working; I tried installing Win 11 today and despite carefully only installing on drive 0, Win 11 decided during the install formatted drive 0 and drive 1 (my Monterey drive), and then to make matters worse, failed to install. I'm so annoyed with MS... So the rest of my free time today, I'm re-installing Monterey on drive 1 and copying things from drive 2, which thankfully Win 11 did not also re-format.]

 

Link to comment
Share on other sites

  • Supervisor

I asked to aluveitie to post his data here

https://www.hackintosh-forum.de/forum/thread/54924-radeon-gpu-temperatur-mit-virtualsmc/?postID=720620&highlight=Gadget#post720620

 

about windows 11

i have had many problems , different from yours

the only way for me to instal it was starting from another pc the installation or update an existent windows in my rig

painfull

  • Thanks 1
Link to comment
Share on other sites

I don't think I need to remind you that this is specific to my chip and yours might do better or worse with it :D

The new cards behave quite differently than the Vegas, AMD pumped a lot of unnecessary voltage through the VII and you could safe a lot of power without sacrificing performance on it.

 

The 6900 XT came far better tuned, there was almost no room to undervolt without limiting the maximum frequency with my chip.

My SPPT is on the more aggressive side since mine is in an ITX case with just 3 120mm rads and a SFX PSU. If I remember correctly the max frequency is 2200 MHz which results in a 5-7% performance hit but reduces the power draw to around 220-250W. At those settings the card is very efficient, still slightly faster than a 6800 XT but I rarely see the GPU hitting 55 C under load.

  • Like 1
  • +1 1
Link to comment
Share on other sites

On 10/7/2021 at 1:46 PM, Driftwood said:

Big Sur Updated: 11.6.1 easily with latest OC 0.74 (SecureBootMethod=Default) As simply as Monterey Beta 9. Thats all.

 

1909394479_Screenshot2021-10-07at21_42_55.thumb.png.94cfcabbe0f3032f48571f78891f5d4a.png

 

Any chance you'd be willing to share your latest EFI? I can't seem to get past;

EB|#LOG:EXITBS:START


Which is the first time I run into this issue, having basically figured out all MMIO stuff and so forth prior. Not sure if I messed it up when going from 0.7.2 to 0.7.4, but doesn't work at all to downgrade either now.

Don't remember Hackintosh being this complicated back in the day. 😉

 

Edit: Out of embarrassment I won't share how, but I Managed to boot, but would still love to compare configs. 😅

 

@fabiosun I remember you mentioned a potential workaround to boot with 64 cores multithreaded, any chance you could elaborate? I seem to have a solid and stable system at the moment, just need to figure out bluetooth and some minor stuff.

Edited by 23d1
Link to comment
Share on other sites

  • Supervisor
24 minutes ago, 23d1 said:

 

Here it is

config.zip 5.28 kB · 1 download

 

Ps. Got sound working, Bluetooth mostly working (lots of weird bugs tho).

Have you tried with this config to boot with all cores enabled?

if it is not working as I think you can try to use an Xcode app (instruments) and limit there cpu core to 32

it could be possible also to try a boot arg (cpu or cpus =32) and see

 

but no illusion about it because also some important lib should be capped to work

 

only some tries to do!

Link to comment
Share on other sites

  • fabiosun changed the title to [Discussion] - TRX40 Bare Metal - Vanilla Patches

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • There are no registered users currently online
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.