Search results

You're already using CaseySJ's patches for PCI enumeration. Your config plist shows property injection for a 5080 GPU which is not supported, and apparently not disabled. Where is the RX 6600 XT? Do you need AMDCPUSupport.kext in the first place?

Browsing through your configuration (keep in mind I'm no expert…) I wonder what the GPRW and PWDE patches are doing, as there's no SSDT which use the renamed functions. Based on the comments, the USB map appears to feature logical HS ports with type 0 and SS ports with type 3 for the same...

OK. At least, I infer that it still boots with my patches. And this has provided two more motherboards to my records, which has eventually prompted me to write a better explanation. Do the patches affect USB behaviour, or other devices? (@Jumper981 reported that he had to modify the RTL812x...

In a further twist, AsRock B650E Steel Legend and X670E PG Lightning have been found to fit the patterns for MSI boards, while AsRock X870E Taichi Lite fits the "general" patterns … which are not so general, and just looking at the manufacturer may not be good enough. Which leaves my "Universal...

You're welcome. So I see you are not using motherboard-specific patches for the conditional device declarations, so you may try my almost-generic patches above ("MSI" version). I don't know if that alone will fix the ghost reboot issue, but it should improve how macOS sees the USB controllers...

@errevi You have posted the ACPI tables but not the EFI folder you're using. In the spirit of the International Journal of Negative Results, even failed SSDTs could be interesting to analyse. Are you using custom ACPI patches, such as those provided on request by CorpGhost? If not, you may try...

Which post? Are you referring to MY patches? :oops: If so, you may try the MSI version from this post (and below) on your AsRock X670E motherboard (patches #1a and #3a looking for the ACPI condition with a mask of three bytes) as an alternative to your set of "AM5 translate" patches, if I...

The problem is that, from reading your document, you're already at "guru" level of technical skills yourself… I notice you first posted in another thread by @errevi involving an AsRock B650E motherboard. Has the issue been reported from other manufacturers? If not, it might not be an AGESA...

Nothing I've seen or read on LiquidGlass has convinced me to try and dip any toe on the 26 family of OS in any Mac, Hack or iDevice… Your bst bet is to reach out to Thunderbolt Master @CaseySJ . But I suspect an IOMMU issue without a solution on AMD.

IORegistryExplorer would show where devices are. If it worked with previous releases, the configuration is fine and it must be that Tahoe has removed non-virtualised access over Thunderbolt. If so the only solutions are (1) revert to Sonoma, (2) make an Intel hack, or (3) get a real Mac.

Assuming that the TitanRidge is at _SB.PCI0.RP21 and everything is correctly configured, your issue could be that macOS wants to address the Thunderbolt device through AppleVTd… which is not available on Ryzentoshes. Was the Octo correctly detected on previous releases of macOS?

Are you merely inquiring or looking for help with your GC-TitanRidge v2? In the latter case you need to explain your issues and describe your setting, including Thunderbolt-related SSDT.

Having the RX580 hanging from the chipset rather than the CPU is not optimal. I'm afraid that a dual or triple boot with alternative GPUs will be difficult, unless you can find a motherboard with a pair of x8/x8 bifurcated PCIe slots from the CPU. I know none of your SSDs, and have no idea...

I fully understand that you are wary to tinker with a working system. I'm sharing my experience with Xeons, which suggests that the need for this "Above 4G+npci=0x2000" setting comes from device conflicts in the PCIe bus. I haven't experienced bad effects from the npci boot arg, which is...

I have no hands-on experience with AMD systems (just hanging around here to learn…), but using BOTH "Above 4G Decoding" and npci=0x2000 is a typical setting with Xeon W-2000 and Xeon Scalable systems—against what Dortania advises for Core systems. I have eventually found out that doing IRQ...

Not quite: This is the direct PCIe root to the CPU and your AMD GPU hangs from the chipset, which is not a satisfactory setting for a main GPU. Two separate builds looks like the most sensible option, even if it implies two sets of RAM. If you absolutely want to have a single build, I'd...

An AMD laptop is quite ambitious for a first. All the best for the work ahead, USB and others!

What is this? The on-board i211? Or do you mean the add-on 10G card? Specifications are abysmal…

(Context here.) Yes, you have an Asus board, I took a quick look at the DSDT, and saw the same patterns as any other Asus/Gigabyte/non-MSI board so far so the patches should work and get you a step closer. These won't correct the ACPI errors from G02F and G027 but I don't think that these are...

I'm obviously not as reputable as CorpGhost, but the standard G002 issues are dealt with by the (non-MSI) generic patches in this post. The G02F and G027 errors are new to me. G02F is only invoked to create a PWRB (Power Button) device, and there's an Else clause which creates a purposedly...