has your motherboard two intel ethernet (I225)?
if so use only this attached kext (add it in your config plist) and use also this bootarg
e1000=0
I have read you reached User configuration in OSX with some EFI (maybe i am wrong)
Beiträge von fabiosun
-
-
Could you post a config.plist only where your system reaches USer configuration step in OSX Ventura?
-
fabiosun das ware total nett wenn du dich so gut auskennst wie andere berichten, ich habe es nochmal probiert auch wieder freeze
your latest EFI is pretty good (i cant judge USB mapping but other part is almost good)
try attached config in your EFI
I have enabled Dummypowermanagement and disabled two patches not useful and not well documented for AMD desktop system
>Let see if it works and then you can optimize GPU performance
it seems also you have i225 ethernet card so this is another problem to solve in your EFI
and it could creates for now a reboot in initial user configuration steps (reboot or freeze)
-
macos Sequoia beta 7
-
SchmockLord your XTXH has a device id not supported by osx AMD gpu driver
So you have to spoof it to a supported one by this driver
6950 xt is not supported in any osx
So we have to spoof to a supported device id from a supported 6900 xt (different but similar to a 6950 xt)
Luckily it works
I can use also NootRX but i prefer to spoof and use whatevergreen kext
DevFelixJava user has a pci acpi path in his ioreg i cant understand for my limited acpi knoledge and also his pciroot address seems doesnt work. It is weird so for now he had success using NootRX and overall Shaneee kernel fix patch to boost opencl/gl performance -
let see it solves EFI problem?
EFI i mounted well (i use hackcheck for this)
-
I remembered that MacPro7,1 caused some issues and that only my current smbios worked properly. The IOREG is definitely with NRX disabled. (As you said, just one monitor and no hardware acceleration)
i do not know if NOOTRX needs to use ImacPro 1.1 Smbios
For your CPU is more appropriate to use MacPro 7.1 Smbios
i would try to use in this way if possible
Happy you solved initial problem but i think is it possible to improve your system configuration
-
DevFelixJava it seems not disabled here
if you can use MacPro7.1 SMBIOS and redo an ioreg log both with NootRX and without it (without it only a monitor on shold be present and obviusly no GPU acceleration)
-
i did what i am saying from my initial post here
disabled a patch used the other
I woluld like to say you should understand why ACPI method does not work
if you can send an IOREG log without using NootRX (i know no acceleration there)
i see some bridges i do not underst (i am not an ACPI expert so it is my fault)
-
first try
do a GeekBench GPU test and save the results (metal/Opengl/CL)
then use this config.plist (overwriting your after backupping it) an do the same and please post the result
I am preparing your ssdt to not use NootRX kext and see if we had acceleration as all we have
-
I think I give up at this point. Using the new Shaneee fix didn't help either.
Guess im dual booting windows to play some Minecraftif you like to do latest try, post your actual EFI and execute this app (or one you have like this)
https://github.com/vulgo/IOReg…xplorer/releases/tag/v2.1
post the results (save as a file (it is your system OSX registry)
i would try (if you want) to do a SSDT for you
-
Still no Hardware-Acceleration.
the only problem could be your <GPU acpi address
others parameters are the same for all people who use to spoof their GPU
EDIT
i see you have acceleration using NootRX kext but only low performance
try to recreate that condition and only to disable to that config algrey fix pat and enable Shaneee fix pat
you would see a great improvment in performance
-
Niloc your EFI is too much old (some kext does not work anymore like Smaltree)
As said patches are also too old and the main problemo for a good experience is that your GPU (GTX 1080) is not supported in OSX from HighSierra
RX 480 i see in your left profile is good also with latest OS (Sonoma)
-
mmmh it is the one i use i cant say if it needs some permission
however i see you are using Algrey fix pat patch
to improve performance in OpenCL/GL you can disable it and use the Shanees one
for now if you cant do good resuòt with DP or with SSDT you can try also with NootRX kext and see the differences
in Opencl your system should have a result greater than 100000 as you see in my picture above
i have tried to modify your config.plist
use also the kext attached (backup yours first)
in this config i use DP properties with your path
removed pikera from bootarg
used Shanee fix patch
-
Well I already removed NootRX completely im just on whatevergreen. device properties are fine if Hackintool isn't wrong with the path. my only option now is to get the .aml running or accept my fate in not be able to play games
Post your config plist without smbios data and serial (if you like)
Dp works well for all our 6950xt so we have to do also for your
attached hackcheck (if you like to try and put acpi path from there
-
I do not follow dortania guide for this (i use and like their product like OCLP but not their guide for AMD)
Default patch used is algrey one
it is much slower than Shanees one
i would suggest to try it and if you do not have additional problem i would use Shanee patch
I would also check better Device properties and use it togheter whatevergreen kext (disable NootRX kext)
you have to use ioregistry explore app and search for GFx0, you will find your path and you have to change in my SSDT here
-
Can't open .amls with this program. Just nothing happens.
.dsls work thoughhttps://github.com/acidanthera/MaciASL
i use this
EDIT2
DevFelixJava i see you are on AMD as me
Which AMD Kernel patches do you use for FIX pat? algrey or Shanees's ones?
Second one is faster in benchmarking gpu
-
you have to open and edit with maciasl app
and find yours here:
-
i use hack check, but if you like you can also try to use a SSDT like this
You have to check in IOREG your path and change them accordly
EDIT
With DP it should work so i think some errors i cant see by now (sorry)
-
Didnt work but I mentioned the pikera in the boot arg and deviceproperty. gonna remove it and try again
Explain what happens?
If it doesnt work maybe your PCI address is wrong
