- Nov 7, 2020
Yeah, I have given up for now but it’s not over…lolNot lucky, I have disabled CPUID detectection but still no luck...
Yep, me too (RAM detection is better).Yeah, I have given up for now but it’s not over…lol
On the plus side, I now prefer using restrictevents to map the memory properly and have switched off my custom map. No errors showing and it’s also displaying the memory slots correctly. I’m happy with that alone but I want the cpu rename to work too to polish it off. I need to ask one of the OC Devs about it.
It’s not the AMD kext no, I’ve tried that already, anything you can think of me or shaneee have tried. I thought It best to just forget about it for now and try again with a clear mind on it.Yep, me too (RAM detection is better).
What about cosmetics? Still working on it... As I said on the other post, AMD processor kext maybe guilty...
BTW, I also updated to last ethernet kext (Lucy)
@AudioGod It is better to wait for us now xDIt’s not the AMD kext no, I’ve tried that already, anything you can think of me or shaneee have tried. I thought It best to just forget about it for now and try again with a clear mind on it.
new Lucy kext is much better don’t you think?
Auto negotiation is working at 2.5 too.
Its up in the resources section for all to use.
V1.0.1 of RestrictEvents has troubles as you know, some people need the boot argument for it to work and some don't and for some like myself it won't work at all.@AudioGod It is better to wait for us now xD
In fact, I have both ethernet cables plugged in and no difference for me. I have a 1GB download/upload speed. However, it is good to know this component is working at full speed.
Why do you use revcpu=1? According to code, it is enabled by default.
Have you try to inject layout number 7 instead 15?
None of my SSDTs are from dortonia but are instead made up mostly manually with the exception of USBX.I like the layout of your thread! awesome work.
i am on an MSI X570 Edge Wifi board with ryzen 3600 and vega 56. i followed dortonia tutorial and osx worked for me, but no sleep and wake. dortonia says that SSDT-SBRG.aml is Intel only. why do you use it? i think you will have a reason for that.
any good tutorial out there providing enough info for what i need which ssdt on AMD systems and how to create them for my setup?
Correct XHC0 is fine.Hello ) I apologize if I ask this question in the wrong topic, but: what about the XHC0? I understand correctly - this controller does not need to be renamed if i using 1.1 SMbios? I also have PTXH and AS43 controllers.
Given that I have a different motherboard than Owl, with SSDT-XHC in the zip there is an SSDT-USBX; should that also be used?Correct XHC0 is fine.
Saying that if your using SMBios1,1 and your board is a x570 then your best off using SSDT-XHC anyway as it maps out all the ports very nicely.
Different motherboard, different problem and I have to point out again that this is off topic for this thread.Given that I have a different motherboard than Owl, with SSDT-XHC in the zip there is an SSDT-USBX; should that also be used?
I have an iMacPro1,1 SMBios and mapped using USBMap-master. I have mapped several times using SSDT-EC-USBX-DESKTOP and XhciPortLimit enabling them in various combinations.
However, I find a XHC1 controller that obviously USBMap-master does not modify.
The results, however ... are identical. Using SSDT-XHC (which maps everything and deletes XHC1) or the kext generated by USBMap-master I still have the slip and wake problem