VRAM Problem with Vega 8! - Lenovo Thinkcenter m75q-1 AMD serie 3000

AdoniS4U

AdoniS4U

New member
AMD OS X Member
Feb 9, 2026
9
3
3
Italy
www.adonisgagliardi.com
CPU:
Ryzen 3 with Vega 8
Hello everyone! I'm writing to you because I'm going crazy. Let me explain...

At first I tried to install Monterey on my Think center m75q-1 model with AMD RYZEN 3000 with integrated Vega 8 graphics.

Ok I managed to build myself a compatible and bootable EFI with Quirks set, Ketxt updated etc etc and therefore all the settings necessary to start at least the installation. That after several trials and attempts I succeeded! I also managed to get to the Desktop but without graphics acceleration having 6MB of video memory from system info. Ok so far so good.
Then I tried to enable Nootedred to enable the graphics driver, but nothing to do! I've been doing endless tests for 6 days between arg boots, PCI changes for the video card and much more. But nothing. I freeze just before it should initialize the login screen (i.e. it crashes and logically it's for VRAM).

I tell you this because my damn think enter, from the BIOS, as far as the UMA BUFFER is concerned, has the maximum imposed threshold of 256MB, no more. I was also logically advised to use Smooker for the BIOS to "unlock" the famous GB of VRAM hidden by lenovo (which is often 90% happening) but there is no entry where I can change this entry. There is not!

I tried to search in all the menus and sub menus and trying triks but nothing to do! I can't! It seems as if blocked by the BIOS irreversibly and I don't know how to start this blessed accelerated graphics of which the Mac is so unusable.

Ah I conclude by saying also, that at the beginning I had tried to install the Mac OS Sonoma operating system, but obviously it was the same problem. Then I was advised to switch to Monterey because it had to be less squeaky as it manages VRAM graphics but it seems the same to me. That is, the question does not change!

I know I've been quite verbose, but it was just to make you understand that I've been trying for days, hours and hours, but without results, and I've seen that here you are real aces in terms of configurations for Hackintos and especially on the AMD front. I hope. Helping you 🙏🙏🙏 Thank you very much and have a good evening everyone!
 
Sort by date Sort by votes
Do you mean you tried to use Smokeless_UMAF to increase the VRAM in the Bios, but were unable to find the hidden UMA setting?

github.com

GitHub - DavidS95/Smokeless_UMAF

Contribute to DavidS95/Smokeless_UMAF development by creating an account on GitHub.
github.com github.com

Are you using any DeviceProperties in your config.plist? As doing this can cause issues with NootedRed.kext.
 
  • Like
Reactions: AdoniS4U
Upvote 0 Downvote
Edhawk said:
Do you mean you tried to use Smokeless_UMAF to increase the VRAM in the Bios, but were unable to find the hidden UMA setting?

github.com

GitHub - DavidS95/Smokeless_UMAF

Contribute to DavidS95/Smokeless_UMAF development by creating an account on GitHub.
github.com github.com

Are you using any DeviceProperties in your config.plist? As doing this can cause issues with NootedRed.kext.
Click to expand...
Yes exactly, I tried Smokeless_UMAF but to no avail. I can't seem to unlock this entry they say it's hidden in the Bios. I tried days and days to search, do tricks and stuff like that but nothing. There is none.

Yes I tried to use it with DeviceProperties and also no, but same. It crashes as soon as with Nootedred active, try to enable graphics acceleration. I have seen that in the Bios settings but everything is fine as they recommend etc etc. But nothing to do. Tried to see even with the Quirks but nothing there either. As said installation part, I have installed, and if I don't use NootedRed.kext logically the Mac OS starts and works.

The problem is that even installing Monterey instead of Sonoma is the same thing. Nothing changes.

I am really sorry and bitter. I can't get out of it.
 
Upvote 0 Downvote
The only useful alternative would be for nootedred to see at least 512Mb of VRAM memory allocated as a minimum, but I don't know how to get out of it. This damn Thinkcenter m75q-1 has a shitty Bios. It doesn't let me go beyond 256mb of UMA. :-(
 
Upvote 0 Downvote
Yeah, most Lenovo & HP systems tend to have a non-standard bios implemented. Hiding or limiting features seems to be a common issue.

Have you had a look on the Lenovo Forums to see if a fix has been found for this UMA issue? As I am sure you are not the first person to have this IGPU VRAM issue.

Bios Mods might also be worth a look, to see if a Hack’d Bios is available for your Mini PC.
 
Upvote 0 Downvote
Upvote 0 Downvote
I found an Optimisation post over on Reddit for your Lenovo m75q-1, which has details on how to use Smokeless_UMAF to increase the RAM speed and the UMA VRAM.

https://www.reddit.com/r/MiniPCs/comments/1g29za0/lenovo_m715q_optimization_guide

Relevant post by user StrawberryNervous637 has been copied and pasted below.

Download Smokeless_UMAF tool from GitHub site, extract to an fat32 formatted usb stick,

boot from it.

in new bios menu, go to:

For RAM Setup:
----------------------
  1. -Device Manager
  2. -AMD CBS
  3. -UMC Common Options
  4. -DDR4 Common Options
  5. -DRAM Timing Configuration
  6. -Accept Warning Disclaimer
  7. -Memory Clock Speed (Set RAM Module Speed, e.g. 1600MHz for DDR4-3200 Modules)
For GFX Memory Setup:
---------------------------------
  1. -Go back to AMD CBS Menu
  2. -NBIO Common Options
  3. -GFX Configuration
  4. -UMA Frame Buffer Size
Setup here your GFX VRAM, e.g. 2GB or 4GB, options go up to 16G (if you had enough RAM Installed)

Hope this helps.
 
Upvote 0 Downvote
Edhawk said:
I found an Optimisation post over on Reddit for your Lenovo m75q-1, which has details on how to use Smokeless_UMAF to increase the RAM speed and the UMA VRAM.

https://www.reddit.com/r/MiniPCs/comments/1g29za0/lenovo_m715q_optimization_guide

Relevant post by user StrawberryNervous637 has been copied and pasted below.

Download Smokeless_UMAF tool from GitHub site, extract to an fat32 formatted usb stick,

boot from it.

in new bios menu, go to:

For RAM Setup:
----------------------
  1. -Device Manager
  2. -AMD CBS
  3. -UMC Common Options
  4. -DDR4 Common Options
  5. -DRAM Timing Configuration
  6. -Accept Warning Disclaimer
  7. -Memory Clock Speed (Set RAM Module Speed, e.g. 1600MHz for DDR4-3200 Modules)
For GFX Memory Setup:
---------------------------------
  1. -Go back to AMD CBS Menu
  2. -NBIO Common Options
  3. -GFX Configuration
  4. -UMA Frame Buffer Size
Setup here your GFX VRAM, e.g. 2GB or 4GB, options go up to 16G (if you had enough RAM Installed)

Hope this helps.
Click to expand...
Thank you very much for the solution

But as I had already written, I had used Smokeless_UMAF and also BETA version but in no way did that damn GFX menu appear to set the UMA BUFFER more than 256Mb. I was helped by a user from another forum who provided me with a USB solution (called SREP) that loads BIOS entries even if they are blocked. Et woila, the option came out and I managed to put 2GB of VRAM. PERFECT. I really have to thank this person because he unblocked what was blocking me for weeks.

Anyway, thank you also for your commitment to finding alternative solutions, anyway, really thank you.
 
Upvote 0 Downvote
But now I have another dilemma.

I have now updated the system to Sonoma (which updated me to the latest build 14.8.4) and everything seems to work.
The only thing that when I went to set up the network card well (with the built-in and so on) with the ketx Itlwm.kext (Because obviously the ketx AirportItlwm doesn't work with my configuration with my WiFi card, in Sonoma, in Monterey it did) but as soon as I enter my APPLE account and the synchronization starts everything stops. It freezes. I can no longer move mouse and nothing. I have to restart. After restarting, everything works but if I go to the apple account tab, it does it again.

It practically freezes, and the fans start at a thousand.

Then for a test, if I disable NootedRed, everything works normally. So it probably conflicts with the video card or too much GPU/CPU load, like, I don't know.
 
Upvote 0 Downvote
Intel WiFi cards using Airportitlwm.kext require different versions of the kext for the different macOS Releases. See this Github page.

github.com

Release v2.3.0 stable · OpenIntelWireless/itlwm

Support macOS Sonoma Users from macOS 14.0 to macOS 14.3 should use a separate kext due to an API change in 14.4+ iMessage and related services will not work OOB with AirportItlwm.kext, use itlwm....
github.com github.com

As you will see, Sonoma has 2 x versions of the kext available each depending on the release package version. You would need to download and use the following kext for 14.8.4:


Using this kext should enable any supported Intel WiFi card to work in the latest release of Sonoma.

Graphics/Freezing issue:
Do you have any DeviceProperties in your config.plist?

I ask this because NootedRed.kext is known to have issues when users add DeviceProperties to their setup.

If possible it is best to use a boot argument or custom SSDT instead of adding DeviceProperties to your config.plist.
 
  • Like
Reactions: AdoniS4U
Upvote 0 Downvote
Edhawk said:
Intel WiFi cards using Airportitlwm.kext require different versions of the kext for the different macOS Releases. See this Github page.

github.com

Release v2.3.0 stable · OpenIntelWireless/itlwm

Support macOS Sonoma Users from macOS 14.0 to macOS 14.3 should use a separate kext due to an API change in 14.4+ iMessage and related services will not work OOB with AirportItlwm.kext, use itlwm....
github.com github.com

As you will see, Sonoma has 2 x versions of the kext available each depending on the release package version. You would need to download and use the following kext for 14.8.4:


Using this kext should enable any supported Intel WiFi card to work in the latest release of Sonoma.

Graphics/Freezing issue:
Do you have any DeviceProperties in your config.plist?

I ask this because NootedRed.kext is known to have issues when users add DeviceProperties to their setup.

If possible it is best to use a boot argument or custom SSDT instead of adding DeviceProperties to your config.plist.
Click to expand...
Yes I see this. But with this release of Sonoma 14.8.4 AirportItlwm.kext does not work. At least it doesn't work for me. Then I don't know if there is any way to make it work.

Now I'm reinstalling and trying to put Ventura (even if I would have preferred Sonoma) because I read on the internet that it's less "*******" than Sonoma and AirportItlwm.kext should work without problem.

As for the EFI or the config.plist tomorrow I post here so you can check in case. I used various versions and did test after test, but without results.

In DeviceProperties it seems to me that I had set the network card to be set built-in as en0 I think having the ketx itlwm..
 
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.