Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Activate AMD hardware acceleration
- Thread starter h9826790
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Hello!
I got a strange behavior at start-up with my cMP 5.1. I use Martins OC 0.8 and has done that since ages. Always with a perfect result. I have Monterey on a NVMe drive crypted with FileVault. Works fine, BUT;
At start-up the OC kicks in and I can se the boot-screen. Monterey is preselected and if I instead of hitting enter, types in my password and hit enter, the computer goes to the password screen. I then I have to retype my password once again and then the computer restarts?? OC kicks in after jet another reboot sequence. I hit enter this time and once more the password screens turns up. Here where is starts to get strange. Then I get the "screen of death" that tells me in Chinese with the turn-on sign in the background, that something is wrong. If I hit enter a one more time, the system boots up without "Finder". I´m consider myself lucky that I use Quick Silver and have option to restart "Finder", with short-command. Very strange. Like glitch in the Matrix.
[Quick answer is not to type in your passord at OC select. I know.]
If I do an ordenary boot, without the password hick-up, my system starts as expected with finder. If I go from OSX to Windows or the other way around, there is no problem. I´m just a user.
Best regards
/Doc
I got a strange behavior at start-up with my cMP 5.1. I use Martins OC 0.8 and has done that since ages. Always with a perfect result. I have Monterey on a NVMe drive crypted with FileVault. Works fine, BUT;
At start-up the OC kicks in and I can se the boot-screen. Monterey is preselected and if I instead of hitting enter, types in my password and hit enter, the computer goes to the password screen. I then I have to retype my password once again and then the computer restarts?? OC kicks in after jet another reboot sequence. I hit enter this time and once more the password screens turns up. Here where is starts to get strange. Then I get the "screen of death" that tells me in Chinese with the turn-on sign in the background, that something is wrong. If I hit enter a one more time, the system boots up without "Finder". I´m consider myself lucky that I use Quick Silver and have option to restart "Finder", with short-command. Very strange. Like glitch in the Matrix.
[Quick answer is not to type in your passord at OC select. I know.]
If I do an ordenary boot, without the password hick-up, my system starts as expected with finder. If I go from OSX to Windows or the other way around, there is no problem. I´m just a user.
Best regards
/Doc
I made a go of a test with the usb and the drives would not boot. I had install Monterey on the usb and that one booted but my other drives just sat with the apple logo doing nothing. Maybe you have an idea what it is with this behavior?
I could edit plist to do the -v and maybe see an answer.... not sure. Perhaps doing the nvram reset? Held off to return to Refind. But not really big deal to hold down option key and reinstall refind.
Running the GTX 780, probably would cause issues if I try running Monterey without some extra editing....
Turned on -v not sure if you tell anything with pic. Further investigating shows that Mohave will boot but not catalina. Thats catalina with the panic screen.
Odd thing that happened, the boot that I am typing this on, my catalina i use now, is that I used the option key boot picker but it had characteristics of the OC. Black background and verbose, loading the boot args from the OC efi? So strange! Clearly was also boot picker too. I can tell the way it loads that its bootpicker and it booted the catalina.
New boot, now I realize when in Mohave I used the startup disk in system prefs that would account for the odd behavior.
The only question I can think of now is why the kernel panic on the 10.15? Will probably have to do nvram reset as it seems refind somehow has retained the information from the usb which was removed. Still get the verbose boot. Also appleALC is there loaded even though usb not mounted?
Wait .... ok never mind just got it. The system I use was already modified by DosDude! of course they are going to KP, had to look at that line where KP said Lilu: unsupported system beta enabled.. some such....
Attachments
Last edited:
You have to check all EFI partitions one by one. Dark mode startup screen, and AppleALC's existence, both suggest that you are still booting via OC.
Removing the USB drive won't necessary remove automatically. If there is any other copy of OC installed onto other EFI partition, the cMP can boot to that OC copy automatically.
Blessed the USB drive's EFI partition somehow can means "give it the priority".
Thanks for the help! I've been testing/working on it awhile now and its doing better. Had to remove a bunch of drives and left only the nvme and was still not getting it to reset the nvram. Kept coming back to OC. Now got it all back and almost everything is perfect and there was even an improvement on the Nvidia card. Used to be if the system went into sleep, it came back with the screen saver messed up. I like the gtx 780 so staying awhile with 11 because 12 does not get acceleration. Will swap it out some time maybe to use 12. Really hanging on to it cause I scored a good deal. Bought it thinking it was a regular pc card but had the boot screen on it when it arrived. Now I guess that doesnt matter too much but still seems pretty good card while it can still be used.
Whats not perfect is just that it seems a little less stable than 10.15 did but I think with some experience it will get worked out a little better.
Just redid the rig for the wifi pretty much. Using Airportbrcmfixup instead. Would have gone better having not forgot some major important things along the way. But even so I have spent much more time setting up a system in the past.
Whats not perfect is just that it seems a little less stable than 10.15 did but I think with some experience it will get worked out a little better.
Just redid the rig for the wifi pretty much. Using Airportbrcmfixup instead. Would have gone better having not forgot some major important things along the way. But even so I have spent much more time setting up a system in the past.
You should do this if you want to remove OC.
NVRAM reset won't stop the cMP booting from OC if you use my config. That's intentional. Otherwise, those rely on OC (e.g. Running Monterey with 5700XT on 5,1) can easily get into no boot condition by just doing a NVRAM reset (which many Mac users will perform without hesitation).
Pro Tools HD Driver update issue I'd appreciate any advice on:
Successfully running OS 12.4 on early 2009 MP 4,1 now 5,1 and with 0.8.0 (have not updated to the newest config.plist for 12.4 recently posted by h9826790...is this necessary and what does it do?). All is running great with no issues EXCEPT trying to update Pro Tools HD Driver (2022.5 or .6 from 2022.4) freezes on "Running Package Scripts". Of course, the computer is "not supported" by Avid, so they won't help troubleshoot. Actually runs great with newest PT Ultimate 2022.6 with 2022.4 HD Driver, but would like to update driver if possible. Is this anything to do with OC or does anyone have ideas?
Successfully running OS 12.4 on early 2009 MP 4,1 now 5,1 and with 0.8.0 (have not updated to the newest config.plist for 12.4 recently posted by h9826790...is this necessary and what does it do?). All is running great with no issues EXCEPT trying to update Pro Tools HD Driver (2022.5 or .6 from 2022.4) freezes on "Running Package Scripts". Of course, the computer is "not supported" by Avid, so they won't help troubleshoot. Actually runs great with newest PT Ultimate 2022.6 with 2022.4 HD Driver, but would like to update driver if possible. Is this anything to do with OC or does anyone have ideas?
One thing has got me confuzzled. I was messing around with DRM. The tv app did not work OOTB. In the process, I put in an rx580 and got the Drm to kick in only in Catalina but get this, the odd thing is that the Wifi configuration failed after putting in the newer card. After trying to see if I deleted some boot arg for wifi, I put back in my gtx 780 and now the wifi works again.
WT...
Another thing, did your documentation show a way to get a boot screen when OC comes up? Will have to look it up.
WT...
Another thing, did your documentation show a way to get a boot screen when OC comes up? Will have to look it up.
Hey everyone, I have a unique issue I can't seem to find an answer or resolution for. I was running Mojave through OC on my cMP 4.1/5,1 and ran into an issue where one of my DAW software was crashing at launch. So I thought to boot into safe boot by holding shift during startup, it bricked my computer. Now when I boot into the drive with Mojave, it just shows me the Apple logo and a progress bar that fills up and just gets stuck there. I tried to reinstall a Mojave again through the recovery partition but it didn't help. I also tried resetting the NVRAM 3 times and then disabling SIP. I have no clue how else to go about this. Thanks in advance!
I've been no way to fix the Bluetooth and Wifi availability issue on Mac Pro 5,1 once upgraded to MacOS 12.4 Monterey with using any versions from h9826790.
It has been bothering me for months with using any version of h9826790's build. And eventually the Opencore team did it successfully with just needed to press on one single button on OpenCore Legacy Patcher app.
SOB they did it for all old Mac people on earth!!!
On last night, I did it with OpenCore Legacy Patcher v0.4.7 where it fixed the issue on the oldest stock Broadcom chip BCM43XX which came with Mac Pro 2010. And it also fixed the stock Bluetooth 2.1 board actually. Now everything finally working flawlessly.It has been bothering me for months with using any version of h9826790's build. And eventually the Opencore team did it successfully with just needed to press on one single button on OpenCore Legacy Patcher app.
SOB they did it for all old Mac people on earth!!!
Attachments
Last edited:
Hey coming by to say thanks for pointing us in the right directions. On following your input on the matter of the rx580 not being able to get a bootscreen, I have flashed it to the later rom and now even in big sur, the HDCP issue is resolved and the Tv app works besides a boot screen with the refind plus. Hey hey been using catalina from Dosdude quite a while when you guys were on this!
Not sure why the other issue did not come up with the wifi going out with that card but since it was flashed it now is working.
Not sure why the other issue did not come up with the wifi going out with that card but since it was flashed it now is working.
One thing I'd mention for folk with Samsung 970 M.2 SSDs like me... personally, I don't rate swapping to something else very highly, at least based upon my experience with the WDS200T1XHE. The WD SSD runs a little cooler and boots a fair bit quicker than the 970 due to it not having to deal with TRIM during boot, but it also partially locks the machine up while completing its TRIM processes while I'm using it. I never had this with the Samsung.
Perhaps there's something wrong here that I'm not considering, but I'd rather the thing locked up during boot and then performed like a champion than cause drive access to go unresponsive for twenty seconds at a time, once per session.
Please chime in if you think I've got some deeper problem, by the way.
AFAIK, TRIM is an OS level function that perform from time to time (assume hardware support it).One thing I'd mention for folk with Samsung 970 M.2 SSDs like me... personally, I don't rate swapping to something else very highly, at least based upon my experience with the WDS200T1XHE. The WD SSD runs a little cooler and boots a fair bit quicker than the 970 due to it not having to deal with TRIM during boot, but it also partially locks the machine up while completing its TRIM processes while I'm using it. I never had this with the Samsung.
Perhaps there's something wrong here that I'm not considering, but I'd rather the thing locked up during boot and then performed like a champion than cause drive access to go unresponsive for twenty seconds at a time, once per session.
Please chime in if you think I've got some deeper problem, by the way.
MacOS perform a manual TRIM during boot. This turn all remaining empty space on the SSD into over provision effectively. Therefore, the SSD should able to perform as expected right after boot to desktop.
However, this is not enough. If you rarely reboot the machine (most Mac user only use sleep indeed), then those TRIMed empty space will still run out eventually.
And the OS will actually TRIM the SSD from time to time. Ideally, this only perform when the system is idle.
I rarely monitor TRIM activity. But one of my net friend did that a few months back. What he found is that MacOS seems only perform TRIM once every few days.
I don’t know if his data is 100% correct. Or if that result only applicable for his SSD, or even his setup. But if that’s true, then if we don’t perform TRIM during boot, macOS should still TRIM the SSD later on, but may need to wait for few days. And in between, the SSD may not perform as expected.
Back to your situation. I don’t know if the system will be locked during TRIM. As I said, it seems that only happen once every few days, and most likely when the system is at idle. Therefore, the user may never notice when TRIM happen.
So, unless every time after lock up, you can find the TRIM record. Then we may safely assume that lock up is TRIM related. Otherwise, that may because something else.
On the other hand, I am not surprised if the system is locked when waiting for storage IO return, that sounds very normal to me indeed.
So, why this lock up only happen on some SSD but not others? I think that may depends on how the controller determine “idle”.
Assume the Samsung SSD controller is very conservative, and only report “idle” (or more precise, “ready for TRIM”) when the disk is at long idle. Then most likely the user is not using the computer, and won’t notice the lock up.
But if the WD controller reports idle more aggressively. Then it may active TRIM inadvertently, which causing a system lock up when the user actually still using the computer.
Anyway, all these are just a theory, I have no prove for that. But this theory fit what I know so far.
Hello. I have a 2017 MacBook Pro A1707 with a specific issue. Loading is only possible with the -igfxvesa flag. With this method of booting, the computer is fully functional. The brightness of the screen is adjustable, the exit from sleep works. With GPU ID spoofing, there will be no brightness and no wake up from sleep. That's why this flag is so important to me. H.264 decoders work, H.265 doesn't at all. But I'm ready to put up with it. In macOS Ventura beta 3, this feature has been removed and no longer works. I have fears that this feature will be cut out everywhere. Is there another way to enable this flag? Thanks in advance.
Sorry, but I couldn't quite understand what's happening.
I know you want the igfxvesa flag, but why?
A1707 support Ventura natively, why you want WhateverGreen and igfxvesa? Why you want to spoof the GPU ID? What issue exactly you are facing? A faulty GPU?
It's not about the system, it's needed in any system. This is such a complex problem. The video works fine, you can play and watch videos in standard definition and H.264, but if HEIC or HEVC is encountered, it freezes or reboots. Service can not help, they can not understand the reason. Suggest to replace the motherboard. It is expensive and impractical, for he is already too old. However, it works well with the -igfxvesa flag, and decoders are used from a discrete video card. I don't want to take it apart. Sorry…
P.S. I'm not aiming for the latest OS, I didn't see anything interesting in Ventura for me. But I fear that these innovations will find me in Monterey. So I decided to ask experienced people if there is another way to use this property to extend the life of this thing.
Attachments
Last edited:
At this moment, I can't see why Monterey will suddenly follow Ventura beta's path. And once Ventura released officially, Monterey will only receive security update, but no more functional update. From that point, I don't think this behaviour will be changed.
Anyway, if you have this concern, you can report this to the WhateverGreen developer (of course, only mention -igfxvesa flag not supported in current Ventura beta. We shouldn't waste their time on some hypothetical potential issue in future Monterey), and see if they have any plan on dealing this issue. [P.S. please read though the WEG official page, make sure this issue hasn't been addressed yet]
However, it's been a little less than a month after upgrading OpenCore to 0.8.0 to get my 2010 5,1 to Monterey 12.4, and I've realized now these fans don't spin up at all. Even tried replacing Mac Fan Control with the old school SMC Fan Control to see if it would change anything. No matter the settings in the control software, no spin.
I used the 12.4 config.plist Martin posted (thanks as always!), also tried his "base" 0.8.0 config.plist. Tried different OS's (High Sierra, Big Sur, Monterey). I'm trying to rack my brain if the fans stopped working before that, with a different OC upgrade, but I just about never saw the CPUs go over 55C before, now I'm lucky if its below 70C at idle without the Boost fans kicking in.
EDIT: Resetting NVRAM about 10 times fixed 3rd party fans not working. Nothing to see here.
Last edited:
I have 12.4 installed by OCLP. 0.48. on my Mac Pro 5.1 BUT although the card is recognized, I have no hardware acceleration via my AMD RX580 in my Mac Pro 5.1. Per example the export from DXO is very very Slow, the graphics card is recognized but somehow there is no graphics acceleration. Is there possibly another driver or another config plist? Can I simply exchange them on the EFI partition?
Graphic acceleration is to "make the display smooth", without this, the screen in modern OS may not able to display at 60FPS, but looks like slide show. Are you saying this part doesn't work properly on your cMP?
The HWAccel in this thread is for video editing. Or more precise, for H264/HEVC video encoding/decoding. If I understand correctly, DXO is a photographic software, not video editing software. Are you using DXO to deal with H264/HEVC videos?
What you mentioned is more like you want the GPU compute to assist the export from DXO. I believe that part should be done by CPU normally. I am not sure if GPU can do anything, but you better check with DXO CS / developer to understand which process can utilise GPU compute.
Just a "quick" question on Davinci Resolve (v17)users: I was not able to use HEVC accelleration for encoding with a 6900XT card on my Hackintosh. There is no particular option for that, but the CPU usage and the renderspeed indicates that there is no GPU accelleraion.
My iMac with 5700XT is much faster and acts like it should. In VideoProc H264 and H265 are available (green), so I think this is not a driver/config issue. Maybe Resolve and the 6900XT are not yet activated for HEVC? I did not test H264 in Resolve.
My iMac with 5700XT is much faster and acts like it should. In VideoProc H264 and H265 are available (green), so I think this is not a driver/config issue. Maybe Resolve and the 6900XT are not yet activated for HEVC? I did not test H264 in Resolve.
Oh great ! a fellow sufferer. I have the same problem. But the issue with bluetooth is not better with the tips from MartinLo. Everything (HWACC) on rx580 works fine but a have no bluetooth. Bevor this spezial package from Martin Lo , I have work also with the "simple" OpenLeacy Patcher. At least with 0.4.9. and have 12.5. So what should I do ? How do you do this exactly? Is it only necessary to "Post Install Root patch". with the OCLP or what settings are important ? Do I have to change something other points in the config.plist ? I can not simple put on the OCLP 0.49 over the Package from Martin .
Yes you are right. This is the Foto Software. BUT: this was not the Reason. The solution was YOUR newest Package for my Hardwareacceleration RX580. This was the solution ! Yeah! Now DXO also works fine ! Great work THANKS a lot. BUT now I have NO bluetooth anymore ! You did a Solution per Youtubevideo. That's what I did . I change the 2 Places in the Cogig.plist. like you showed us in the video. BUT. : NO positive Result. No bluetooth. Can you help me ? Do you have an Idea what to do ? in your config .plist I have changed these 3 "false" in "Trues" BUT no Bluithtooth !
