Ryzen 7000 Testing

mariettosun said:
yep I misunderstood from a link given on AMD discord (I meant about the genesis of that boot arg)
github.com

IOPCIFamily/IOKit/pci/IOPCIConfigurator.h at IOPCIFamily-583.40.1 · apple-oss-distributions/IOPCIFamily

Contribute to apple-oss-distributions/IOPCIFamily development by creating an account on GitHub.
github.com github.com
Click to expand...
We described all of those boot args here:

Ryzen 7000 Testing

@ExtremeXT Unfortunately pci-msi-limit did not make a difference with either 0 or 1000.
forum.amd-osx.com forum.amd-osx.com

kIOPCIConfiguratorDefaultETF is the second one from the end of the list.
 
  • Like
Reactions: fabiosun
ExtremeXT said:
Shaneee merged it, can you do one final test to make sure it works fine?
Click to expand...
It is 2:50am — just sipping my morning coffee in front of the fireplace. My Zen moment before the world around me wakes up. :)

Will retest soon.
 
  • Like
Reactions: ExtremeXT
  • Like
Reactions: ExtremeXT
@CaseySJ @ExtremeXT

some users using clover boot loader and MSI board could benefit of your work
1668510595625.png

if you have no objection I would like to put the patch in the Clover AMD Vanilla patches repo
Patch also works fine in Clover boot loader

Code: 
17:514  0:001  OC: Prelinked patch [1] com.apple.iokit.IOPCIFamily (CaseySJ - probeBusGated Disable 10 bit tags - 12.0/13.0)
17:516  0:001  Replace E6117206 by E6117306 at ofs:7289
17:532  0:015  OCAK: 64-bit com.apple.iokit.IOPCIFamily (CaseySJ - probeBusGated Disable 10 bit tags - 12.0/13.0) replace count - 1
17:533  0:001  OC: Prelinked patcher result 1 for com.apple.iokit.IOPCIFamily (com.apple.iokit.IOPCIFamily (CaseySJ - probeBusGated Disable 10 bit tags - 12.0/13.0)) - Success

thanks
 
mariettosun said:
@CaseySJ @ExtremeXT

some users using clover boot loader and MSI board could benefit of your work
View attachment 8291

if you have no objection I would like to put the patch in the Clover AMD Vanilla patches repo
Patch also works fine in Clover boot loader

Code: 
17:514  0:001  OC: Prelinked patch [1] com.apple.iokit.IOPCIFamily (CaseySJ - probeBusGated Disable 10 bit tags - 12.0/13.0)
17:516  0:001  Replace E6117206 by E6117306 at ofs:7289
17:532  0:015  OCAK: 64-bit com.apple.iokit.IOPCIFamily (CaseySJ - probeBusGated Disable 10 bit tags - 12.0/13.0) replace count - 1
17:533  0:001  OC: Prelinked patcher result 1 for com.apple.iokit.IOPCIFamily (com.apple.iokit.IOPCIFamily (CaseySJ - probeBusGated Disable 10 bit tags - 12.0/13.0)) - Success

thanks
Click to expand...
I have no problem, if Casey agrees you can PR it to the repo, don't forget to edit the README as well.
 
ExtremeXT said:
It shouldn't be needed for the 4 byte patch.
Click to expand...
There’s a higher chance of conflict with future macOS updates as the number of “Find” bytes decreases. Adding ‘base’ reduces those chances. It also allows OpenCore to jump quickly to the base function (via symbol map in binary file), hence faster.
 
  • Like
Reactions: etorix
mariettosun said:
@CaseySJ @ExtremeXT

some users using clover boot loader and MSI board could benefit of your work
View attachment 8291

if you have no objection I would like to put the patch in the Clover AMD Vanilla patches repo
Patch also works fine in Clover boot loader

Code: 
17:514  0:001  OC: Prelinked patch [1] com.apple.iokit.IOPCIFamily (CaseySJ - probeBusGated Disable 10 bit tags - 12.0/13.0)
17:516  0:001  Replace E6117206 by E6117306 at ofs:7289
17:532  0:015  OCAK: 64-bit com.apple.iokit.IOPCIFamily (CaseySJ - probeBusGated Disable 10 bit tags - 12.0/13.0) replace count - 1
17:533  0:001  OC: Prelinked patcher result 1 for com.apple.iokit.IOPCIFamily (com.apple.iokit.IOPCIFamily (CaseySJ - probeBusGated Disable 10 bit tags - 12.0/13.0)) - Success

thanks
Click to expand...
No objection from me either.
 
CaseySJ said:
There’s a higher chance of conflict with future macOS updates as the number of “Find” bytes decreases. Adding ‘base’ reduces those chances. It also allows OpenCore to jump quickly to the base function (via symbol map in binary file), hence faster.
Click to expand...
PR that to the repo and ping Shaneee.
 
  • Like
Reactions: backinblackx86
smashing
 
  • Like
Reactions: ExtremeXT
CaseySJ said:
Has anyone been able to inject this in Ventura? I'm still trying, but no success so far.
Click to expand...
Yes, it should work by just injecting it with OpenCore.
 
  • Like
Reactions: CaseySJ
ExtremeXT said:
Yes, it should work by just injecting it with OpenCore.
Click to expand...
The I225 device got disabled when I tried this yesterday. Will give it another go shortly.
 
  • Like
Reactions: ExtremeXT
The Gigabyte AM5 user whom I posted the screenshot a few pages back has an ALC897 codec instead of ALC4080 (USB audio) and their audio is 99% perfect with Speedkeeper, I wonder if it's related to the USB audio.
 
CaseySJ said:
The I225 device got disabled when I tried this yesterday. Will give it another go shortly.
Click to expand...
Unfortunately no success with AppleIntelI210Ethernet in Ventura. I've tried:
  • Raising Probe Score to 4000 (DriverKit-AppleEthernetE2000 is 3000)
  • Using e1000=0
  • Using device-id = 0xF3158680
 
ExtremeXT said:
The Gigabyte AM5 user whom I posted the screenshot a few pages back has an ALC897 codec instead of ALC4080 (USB audio) and their audio is 99% perfect with Speedkeeper, I wonder if it's related to the USB audio.
Click to expand...
It's 99% perfect with SpeedKeeper on this system as well. That's what I mean when I say audio from all sources is virtually perfect when SpeedKeeper is enabled.
 
  • Like
Reactions: ExtremeXT
CaseySJ said:
It's 99% perfect with SpeedKeeper on this system as well. That's what I mean when I say audio from all sources is virtually perfect when SpeedKeeper is enabled.
Click to expand...
Could you record a sample coming from the internal audio with and without Speedkeeper?
 
ExtremeXT said:
About audio, I found this in an old custom kernel for High Sierra (Screenshot 1). My idea would be to either:
1. Make a kext that calculates the TSC and FSB Frequency values
2. Find an easy way to get these values from the OS and make a script that calculates them. With the proper values, the user can manually input these values into the InitialTSC and FSBFrequency fields in the config.plist
I am positive that it would work if done properly, since it seems to be the same problem as on AMD APUs.
...
Click to expand...

With PCI issues resolved, now seems like a good time to reopen the audio discussion.

Let's consider various strategies for tackling this problem before we embark on any particular strategy.

If we agree that obtaining correct FSB and TSC frequencies is the key, then the first few questions are:
  • Should we discount or ignore the frequencies reported by sysctl -a | grep tsc and sysctl -a | grep freq ?
  • Should we discount or ignore the frequencies reported in OpenCore boot log?
  • If we cannot trust the values from both sysctl and OpenCore, how can we still get reliable or usable values from the OS?
  • What parameters would we need to obtain from the OS that will allow us to calculate TSC and FSB frequencies?
 
  • Like
Reactions: craighazan and ExtremeXT
You must log in or register to reply here.
Top Bottom
✖
  AdBlock Detected
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.