NootedRed isn't accelerating graphics

G

GarvitPlayz

Member
AMD OS X Member
Mar 23, 2022
38
1
3
8
CPU:
AMD RYZEN 4600H
Hola People! I just successfully installed Ventura a while ago, but it seems like NootedRed isn't working? No Graphical Acceleration, Very Laggy and iGPU shows with 7MB Vram.

System Specs:
CPU : Ryzen 5 4600h with AMD Radeon Graphics
dGPU : NVIDIA GTX 1650ti

I also noticed that even though I have used an SSDT to disable the dGPU as well as used the bootarg (EFI LINKED BELOW) in System Report both the gpus are present and show no kext is attached(something like that)

PS : Opencore MOD EFI from Orialla with some SSDTs and Kexts added (It was the only one that even booted up the installer for me)
 

Attachments

Last edited:
Sort by date Sort by votes
Which commit have you downloaded when obtaining the NootedRed.kext?

There is a 'Nightly Build' link on the page below, download the NootedRed version from the build dated 4 Dec 2024.

NootedRed

The AMD iGPU kernel extension.
chefkissinc.github.io chefkissinc.github.io


Are you sure the SSDT contains the correct ACPI path for your dGPU? As your SSDT has the ACPI path for the example shown in the Optimus method, in the page linked below.
Did you check/confirm the Bios device name for your dGPU in Windows?


You can use the Bumblebee method to create the SSDT to disable your GTX 1650 TI, it should also help reduce the power used by the dGPU. This uses the SSDT-NoHybGfx.aml table.
 
Upvote 0 Downvote
Edhawk said:
Which commit have you downloaded when obtaining the NootedRed.kext?

There is a 'Nightly Build' link on the page below, download the NootedRed version from the build dated 4 Dec 2024.

NootedRed

The AMD iGPU kernel extension.
chefkissinc.github.io chefkissinc.github.io


Are you sure the SSDT contains the correct ACPI path for your dGPU? As your SSDT has the ACPI path for the example shown in the Optimus method, in the page linked below.
Did you check/confirm the Bios device name for your dGPU in Windows?


You can use the Bumblebee method to create the SSDT to disable your GTX 1650 TI, it should also help reduce the power used by the dGPU. This uses the SSDT-NoHybGfx.aml table.
Click to expand...
Hey! Thanks for taking time to help me! I downloaded the latest commit - https://github.com/ChefKissInc/NootedRed/actions/runs/12166048812
I am pretty sure I did set the correct ACPI path from my Device Manager, but I'll recheck once again.

I'll download the nightly build and get back to you!
 
Upvote 0 Downvote
tbf I don't really mind if the Nvidia GPU isn't completely disabled, just getting graphical acceleration with my igpu would be enough for now
 
Last edited:
Upvote 0 Downvote
The SSDT-dGPU-Off.aml table is correct. But you may still need to use the Bumblebee method. As the battery life of your laptop will be rubbish if you don't disable/reduce the dGPU's power consumption.

The NootedRed.kext commit you downloaded has the same date/time stamp as the last Nightly Build, so you definitely have the latest release.

You need to remove the DeviceProperties > Add entry from your config.plist. Using DeviceProperties with NootedRed.kext is known to cause issues. It may prevent NootedRed.kext from loading in macOS, which in turn would prevent any graphics acceleration.

Screenshot 2025-01-04 at 15.38.35.png Remove DeviceProperties entry

If what your are setting as 'compatible' by using the DeviceProperties entry is essential to your laptop working, then look at an option to create an SSDT that does the same task. But definitely remove/delete the DeviceProperties entry.

You might want to look at updating the version of OpenCore you are using and the latest release for your Kexts, as some of them are a few releases old, compared to current kexts.

Same goes for the AMD Kernel Patches, these are not the latest and should be updated.

github.com

GitHub - AMD-OSX/AMD_Vanilla: Native AMD macOS via OpenCore

Native AMD macOS via OpenCore. Contribute to AMD-OSX/AMD_Vanilla development by creating an account on GitHub.
github.com github.com
Boot Arguments:
Screenshot 2025-01-04 at 15.53.45.png Your current boot arguments

You may want to remove the -wegnoegpu boot argument, as well as a few of the others, as they aren't required for an AMD system.
Does your laptop have an Intel I225-V Ethernet controller/port, as if not then the dk.e1000=0 and e1000=0 boot arguments can be removed.
The -igfxvesa boot argument is an Intel IGPU fix, but if it is working this will force your system to run in VESA mode, i.e. with no graphics acceleration. It should be removed.

Screenshot 2025-01-04 at 15.58.01.png Proposed boot arguments

See if changing the boot arguments and removing the DeviceProperties entry helps.
 
Upvote 0 Downvote
Edhawk said:
The SSDT-dGPU-Off.aml table is correct. But you may still need to use the Bumblebee method. As the battery life of your laptop will be rubbish if you don't disable/reduce the dGPU's power consumption.

The NootedRed.kext commit you downloaded has the same date/time stamp as the last Nightly Build, so you definitely have the latest release.

You need to remove the DeviceProperties > Add entry from your config.plist. Using DeviceProperties with NootedRed.kext is known to cause issues. It may prevent NootedRed.kext from loading in macOS, which in turn would prevent any graphics acceleration.

View attachment 16016 Remove DeviceProperties entry

If what your are setting as 'compatible' by using the DeviceProperties entry is essential to your laptop working, then look at an option to create an SSDT that does the same task. But definitely remove/delete the DeviceProperties entry.

You might want to look at updating the version of OpenCore you are using and the latest release for your Kexts, as some of them are a few releases old, compared to current kexts.

Same goes for the AMD Kernel Patches, these are not the latest and should be updated.

github.com

GitHub - AMD-OSX/AMD_Vanilla: Native AMD macOS via OpenCore

Native AMD macOS via OpenCore. Contribute to AMD-OSX/AMD_Vanilla development by creating an account on GitHub.
github.com github.com
Boot Arguments:
View attachment 16017 Your current boot arguments

You may want to remove the -wegnoegpu boot argument, as well as a few of the others, as they aren't required for an AMD system.
Does your laptop have an Intel I225-V Ethernet controller/port, as if not then the dk.e1000=0 and e1000=0 boot arguments can be removed.
The -igfxvesa boot argument is an Intel IGPU fix, but if it is working this will force your system to run in VESA mode, i.e. with no graphics acceleration. It should be removed.

View attachment 16018 Proposed boot arguments

See if changing the boot arguments and removing the DeviceProperties entry helps.
Click to expand...
Yup, that did absolutely nothing 😔 I also noticed another thing. When I used an older version of NootedRed, the screen went black after booting into the OS. Could this be something?

EDIT : With the black screen, MacOS is running tho, I can hear some sounds
 
Last edited:
Upvote 0 Downvote
The system will be running in the background, with a black screen. This can usually be tested by screen sharing to the Hack from another Hack or a real Mac. Assuming you have setup the hack to screen share.

Try the version of NootedRed.kext attached below from a commit I downloaded back in November 2024. It worked on both my AMD IGPU only systems.
 

Attachments

Upvote 0 Downvote
Edhawk said:
The system will be running in the background, with a black screen. This can usually be tested by screen sharing to the Hack from another Hack or a real Mac. Assuming you have setup the hack to screen share.

Try the version of NootedRed.kext attached below from a commit I downloaded back in November 2024. It worked on both my AMD IGPU only systems.
Click to expand...
Sure, I'll try it out and get back to you in 5 mins, please be online
 
Upvote 0 Downvote
Two older versions of the kext are attached. I used both at some point. Try them see if one works.
 

Attachments

  • Like
Reactions: GarvitPlayz
Upvote 0 Downvote
Solution
Dude. Just hear me out. You are a boon to mankind. Thanks for your invaluable help! The Dec 2023 version worked for me! Believe me, if I could've, I would've hugged you as tightly as possible! THANKS DUDE!! The only thing not working now is Bluetooth. Rest Everything works flawlessly!
 
  • Like
Reactions: Edhawk
Upvote 0 Downvote
Which Bluetooth module are you using?
 
Upvote 0 Downvote
Yeah, that helps.

That means you need to add these kexts to your OC Kexts folder and config.plist.
  1. IntelBluetoothFirmware.kext
  2. IntelBTPatcher.kext
  3. BlueToolFixup.kext
You will also need these NVRAM > Add & Delete entries, if running Sequoia.
Screenshot 2025-01-04 at 21.58.56.png contained in config-Intel-BT.plist attached below
 

Attachments

Upvote 0 Downvote
Edhawk said:
Yeah, that helps.

That means you need to add these kexts to your OC Kexts folder and config.plist.
  1. IntelBluetoothFirmware.kext
  2. IntelBTPatcher.kext
  3. BlueToolFixup.kext
You will also need these NVRAM > Add & Delete entries, if running Sequoia.
View attachment 16033 contained in config-Intel-BT.plist attached below
Click to expand...
I've already done all of this, including the NVRAM entries, you can check my EFI folder
 
Upvote 0 Downvote
Another problem......It seems like Battery isn't charging at all or smthing. The charge % doesn't go up. It seems like Windows has been affected by this as well
 
Upvote 0 Downvote
GarvitPlayz said:
Another problem......It seems like Battery isn't charging at all or smthing. The charge % doesn't go up. It seems like Windows has been affected by this as well
Click to expand...
Ok, I fixed this temporarily by force shutting down the laptop, but it's back again
 
Last edited:
Upvote 0 Downvote
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.