Jump to content
TheBloke

AMD GPU on 10.14 with no iGPU: many issues

Recommended Posts

[ref]MaLd0n[/ref], short answer: yes I can sleep & wake OK with new DSDT you provided.



Full results:

 

  1. First boot, one monitor connected (port DP1): Boot to login screen. Click sleep. Machine sleeps. Press power to wake, machine wakes OK.
    • Then I log in. I try sleep again. Machine sleeps. Press power to wake, machine powers on, but does not properly wake: no picture on monitor, machine cannot be pinged on network. I had to press reset button.
    • But I had this same problem one time earlier today as well, so this is probably not connected to new DSDT.

[*]Second boot (same one monitor), boot to login & sleep/wake OK.

  • Then sleep again, this time it wakes fine.

 

As you said, I could only wake with power button, not keyboard.


Note: I did one test booting with multiple monitors connected, and there was no change - black screen, could not sleep. Probably this is expected, I just mention to be complete.


Thanks again for all the work you are doing for me, it is really appreciated.

ONE: X299X: G.byte X299X Designare 10G, Intel i9-10980XE, 128GB DDR4 3600

GPU:  Gigabyte RX Vega 64 8GB OC

SMB: MacPro 7,1. OpenCore 0.6.3

 

TWO: X58: G'byte GA-X58A-UD3R, Xeon X5670, 48GB DDR3 1600

GPU: AMD R9 280X 3GB

SMB: iMacPro 1,1. Clover: R5118 Legacy

Link to comment
Share on other sites

[ref]MaLd0n[/ref],


here you go Madl0n.. I have prided myself in getting by hackintoshing over the year, reading, trying but I have been banging my head on this for over a month... and getting nowhere.


I would prefer to try the MP5,1 route first, since I have many expensive software packages tied to my MP serial number. but if we have to go the iMac Pro route .. well I will figure something out


clover must have made great strides over the last couple years..


as I commented above.. this is a very vanilla install using multishit, and its generic 5,1 def. I only added ethernet kext and fakesmc and got 4k60 on DP, HDMI audio on that DP, and it looks like my cpu was being power and step managed. adding lilu,WEG,ALC got me line out on the alc889 without having a single line in the DSDT or patches in clover..


sleep obviously doesn't work.. and in both 5,1 and iMac pro , I only have 1 monitor, if I try to plug in or boot with the second monitor at HDMI, black screen, no signal , green screen ..etc


I have included my previous DSDT for you to look at .. I don't use that airport card right now so it doesn't need to be in the final product.. this dsdt give me full sleep, wake with usb, graphics on gtx660, HDMI audio, alc889, it just works great.... with almost no patches in clover enabled..


I would like to get this 6 port sata card working though, I don't have it plugged in for this right now.. but it attaches at PEX1@1c1 and funny it took the ARPT label in ioreg when I booted into el cap with it installed. it has kept me from booting 10.14 though on this motherboard.. I can boot it on a different machine running Mojave just fine. .can even boot osx from it.,. so I know its compatible.. perhaps with a fully functioning DSDT and good interrupt handling it will be plug and play


thanks again for your assistance!!!


Added in 4 minutes 54 seconds:

[ref]TheBloke[/ref],


sounds like this might be un-fixable with current drivers post 10.14.5


I think perhaps we might want to consider either rolling back to that point release or figure out which kexts are offending and try and bring those forward into 10.14.6 ... I doubt we will see apple release any new meaningful updates to Mojave if history repeats.. this is now EOL for major updates... security fixes only probably

Send me localagentsiMac.lab.zip

DSDT mod.aml.zip

Link to comment
Share on other sites

  • Administrators

[ref]duece[/ref], DSDT.duece1.zip

DSDT.duece2.zip

test two files and let me know

-Donations-

PayPal HERE - Stripe HERE - Ko-Fi HERE - BuyMeaCoffee HERE - Mercado Livre HERE

Skrill danielnmaldonado@gmail.com - BTC 33HeGCuCSh4tUBqdYkQqKpSDa1E7WeAJQ3 - BNB 0x10D1d656eCa00bD521f9b4A43B83098B8142e115 - USDT BSC BEP20 0xb57cfdfa371fad1981910f0e8332409ab99f74d9 - USDT TRC20 TUR6Z9AVS4AYzqPnULoHrfFvppRbhXmNbZ - KASPA kaspa:qpxzufgfj8p6r0krg58yzvs0009h2mwqgvcawa0xc2pth7sgzpv56j4f6dtvk - PicPay @danielnmaldonado - PiX @danielnmaldonado@gmail.com

Premium Users HERE - Problems with Paypal HERE

xcd5u2Y.png

Sign up for a Bybit account and claim exclusive rewards HERE

New ways to earn money with Linkvertise HERE

Link to comment
Share on other sites

sounds like this might be un-fixable with current drivers post 10.14.5

 

What makes you say that? Have you read something to that effect?


All I know is that I've been living with the same general issue since 10.13, first starting with my my previous GPU the R9 280X, which is now installed in my second Hack, the H77. It's worse on the Vega in that I can only boot with one monitor connected, else I can't sleep and have to reboot. But the general principle of needing to sleep in order to see a picture on all monitors has existed for me since I first installed my R9 280X over a year ago, in 10.13.x. It changed a bit in 10.14.0 in that I also started to get errors in Console, and the kernel using high CPU until a sleep was done. But the fundamental issue has remained unchanged - and unsolvable by me, despite tens of hours of trying things like FB patching, SSDTs, and every possible permutation of WEG/Clover options. Or rather, trying the options I understood - which is certainly not all of them.


So based on my own experiences, I'm not seeing .6 being any different. It certainly hasn't affected my symptoms thus far.


All that said, I'm certainly willing to test in .5 if there's some reason to think it would make a difference. I can restore a network backup to my spare SSD; my most recent one is from June which should be 10.14.5. Worst case the backup will be 10.14.1, in which case I can upgrade to .5 via the standalone downloads on support.apple.com.

ONE: X299X: G.byte X299X Designare 10G, Intel i9-10980XE, 128GB DDR4 3600

GPU:  Gigabyte RX Vega 64 8GB OC

SMB: MacPro 7,1. OpenCore 0.6.3

 

TWO: X58: G'byte GA-X58A-UD3R, Xeon X5670, 48GB DDR3 1600

GPU: AMD R9 280X 3GB

SMB: iMacPro 1,1. Clover: R5118 Legacy

Link to comment
Share on other sites

[ref]MaLd0n[/ref],


10.14.6


made no changes to the generic config.plist of the fresh install.. not my config.plist from my previous el cap


no sleep either one


your GFX0 implementation at PEG3 is a bit unusual ... perhaps not what you intended?


I don't think that the EGPU device is even being picked up being overshadowed or GFX0 being grabbed by whatever green.. as it was able to do with no DSDT edits at all...

Screen Shot.jpg.zip

Link to comment
Share on other sites

  • Administrators

[ref]duece[/ref], the device don't exist and pegp is createt weg kext rename to gfx0 on the fly


the best is create all missing devices


Added in 51 seconds:

EDIT


here, without gfx0 in tree

DSDT.aml.zip

-Donations-

PayPal HERE - Stripe HERE - Ko-Fi HERE - BuyMeaCoffee HERE - Mercado Livre HERE

Skrill danielnmaldonado@gmail.com - BTC 33HeGCuCSh4tUBqdYkQqKpSDa1E7WeAJQ3 - BNB 0x10D1d656eCa00bD521f9b4A43B83098B8142e115 - USDT BSC BEP20 0xb57cfdfa371fad1981910f0e8332409ab99f74d9 - USDT TRC20 TUR6Z9AVS4AYzqPnULoHrfFvppRbhXmNbZ - KASPA kaspa:qpxzufgfj8p6r0krg58yzvs0009h2mwqgvcawa0xc2pth7sgzpv56j4f6dtvk - PicPay @danielnmaldonado - PiX @danielnmaldonado@gmail.com

Premium Users HERE - Problems with Paypal HERE

xcd5u2Y.png

Sign up for a Bybit account and claim exclusive rewards HERE

New ways to earn money with Linkvertise HERE

Link to comment
Share on other sites

[ref]MaLd0n[/ref], FYI I noticed that with latest DSDT you provided, my processor is always at x12 multiplier, like this:


EDIT: Sorry, this is not related to new DSDT/config.plist. I have done more testing and same happens with old as well. It appears that before sleep, I only have x12 multiplier. After sleep & wake, I have full x22-x24, and this is same with both my original DSDT/config.plist, and the ones you have sent me.


I do not know for sure if this is new behaviour or not, as before I would always put my machine to sleep at login screen. So maybe this issue has always been there.

Edited by Guest

ONE: X299X: G.byte X299X Designare 10G, Intel i9-10980XE, 128GB DDR4 3600

GPU:  Gigabyte RX Vega 64 8GB OC

SMB: MacPro 7,1. OpenCore 0.6.3

 

TWO: X58: G'byte GA-X58A-UD3R, Xeon X5670, 48GB DDR3 1600

GPU: AMD R9 280X 3GB

SMB: iMacPro 1,1. Clover: R5118 Legacy

Link to comment
Share on other sites

[ref]MaLd0n[/ref],


[ref]MaLd0n[/ref],


I understand where you are going with it, but for example on PEG3 you had GFX0 and HDAU devices, then added PEGP in the same path also with GFX0 and HDAU and I think WEG latched on to the first instance. Graphics card was not showing up in you FABULOUS !! system profiler PCI listing man that is really nice!! So I was thinking that perhaps having multiple devices with the same name was throwing things off


I am not at the computer at the moment but will test out later. Looking at the DSDT though, did you do the edits and patches of the NEW raw DSDT that was in the run.me zip or add/remove patches from my already patched DSDT? Only reason I ask is that I see old Toleda method HDEF patches that are likely no longer required using LILU/ALC and that probably should have stayed AZAL? and you added / or kept APRT in at PEX, and I really don't have that installed now. I also can't remember if I deleted more devices but see PS2K/M and perhaps the big one, serial port .. and that one has a NOIRQ that is like 1,2,3,4,5,6,7,8,9,..... basically taking every irq..


Also, the my old patched DSDT was one bios revision down... I had to update bios for the new graphics card. from 5599 to 5600 IIRC.

the el cap install still seems to run fine with my old DSDT and clover config.


also, I think I had some lengthly edits in the USB devices... I might have to have them in there for sleep... again can't remember.


I notice at least one rename TMR to TIMR but left LCP instead of LCPB.. just wondering what kind of patching flags this DSDT is designed to run with ? should I be selecting Drop Unused for example? And do some renames on the fly?


also there is a warning for and external value \UMAP at the start of the DSDT.. is that a SSDT table or some other external I need to have in my ACPI folder?


muchas gracias senior ... really... sorry for the dumb questions.. trying to learn something as I go since you are far more skilled than I !!


Added in 3 minutes 24 seconds:

[ref]TheBloke[/ref],


Man I am jealous of you guys that run the gigabyte boards... I get very little sensor data from the intel boards because of my chipset... not mainstream enough for the community to include my values!!!


what does the clover boot.log say about your processor? it should recognize it.. and the x5670 was in real macs IIRC? perhaps you have selected something in clover configurator that is patching your processor and loosing native speed stepping ?

Link to comment
Share on other sites

Man I am jealous of you guys that run the gigabyte boards... I get very little sensor data from the intel boards because of my chipset... not mainstream enough for the community to include my values!!!

 

Ah yeah, the HWMonitor stuff is useful. I take it you've tried the various FakeSMC variations to confirm none offer more info? I re-did that comparison yesterday, comparing two:


RehabMan/Kozlek

vit9696's VirtualSMC


The former is the one I have used for a long time, and is the one I'm still using now. It provides the info you saw earlier, with its own bundled HWMonitor.app. The latter I tried in case it provided more GPU data on the Vega. It doesn't have a bundled HWMonitor, so I used HWMonitorSMC2, which looks a bit different to HWMonitor, and does have one useful feature - it has an option for reading GPU data from IOKit, meaning it can read all the utilisation/performance stats that GPUs like the Vega 64 now write there (and which is also accessible from command line using ioreg).


I ended up uninstalling vit9696's VirtualSMC and going back to RehabMan's, even though that's not been updated in a year or so. And because HWMonitor is the only one that shows the Frequency info, and HWMonitorSMC2 is the only one that shows the Vega 64 info, I now have both running :)


BSchUOGm.png

 

what does the clover boot.log say about your processor? it should recognize it.. and the x5670 was in real macs IIRC? perhaps you have selected something in clover configurator that is patching your processor and loosing native speed stepping ?

 

I've edited my previous post - turns out this issue existed also with my original DSDT and config.plist as well. It appears that this is yet another issue that requires a sleep & wake: before sleep, my CPU won't go above x12. After sleep, it's normal x12-x22, with x24 on turbo boosting cores.


I have no idea how long this issue has existed for, because for the last 1+ years I have always put the system to sleep as soon as I got to the login screen, due to my ongoing GPU issues. I know that I haven't had the issue always, because back in High Sierra there was a time when I used an NVidia GPU, and didn't have to sleep. I know my frequencies were right then.


So it could be the issue has come with 10.14.0 or a later update. Or it could be a result of switching to iMacPro 1.1. No idea. Right now it's moot, because I have to sleep & wake shortly after boot anyway. If I ever get that solved, I'll investigate it further.

ONE: X299X: G.byte X299X Designare 10G, Intel i9-10980XE, 128GB DDR4 3600

GPU:  Gigabyte RX Vega 64 8GB OC

SMB: MacPro 7,1. OpenCore 0.6.3

 

TWO: X58: G'byte GA-X58A-UD3R, Xeon X5670, 48GB DDR3 1600

GPU: AMD R9 280X 3GB

SMB: iMacPro 1,1. Clover: R5118 Legacy

Link to comment
Share on other sites

[ref]TheBloke[/ref],


in the 13-14 years I have been building these things I have never found one that gives me more than basic info on my intel boards.. gluten for punishment .. I have a badaxe 1 775, a badaxe2 775, and DX58so and they were all more difficult to hack than their gigabyte brethren .. I have a EP45 board and that one had pretty good sensor support..


if and when I do this again and abandon the DX58 which I really don't want to do because the W3680 is good enough for me... it will be a much more mainstream board with better support .. I am getting too old spending a month working 6 hours a night trying to get this ironed out


[ref]MaLd0n[/ref],


I have not been able to get sleep working on the fresh install, but went back to my previous attempt which was a fresh install to .5 or .6, used migration assistant to pull in my el cap drive, and was upgraded to .6u2 .. went back to just my basic DSDT from my old install, my old config.plist that has almost nothing turned on.. and I am back to having sleep.


if I use the same procedures as the bloke.. I can boot the 4k60 TV at DP1 > HDMI adapter and pretty reliable, sleep wake, etc


if I try and boot just the HDMI monitor, black screen with the system running behind it logging GPU.restarts in the console panic/spindump section


if I boot with 4k60 and plug HDMI in , crash to black screen, system running.. can ssh in ect.. but sudo shutdown -h now just sits there.. wont turn off although drive activity ceases so I give it a minute and hard reset


if I boot 4k60 with the other HDMI monitor plugged in but OFF, not sleeping, OFF, and get to the login screen, sleep the system THEN turn on the HDMI monitor and wake, I have both monitors and can continue to sleep and wake them as a pair.. testing short term only right now.. sleept it all night last night will update later


not using darkwake in boot args which is strange since it only worked in the past with no or =0 .. using dart (even though VT-d disabled), SHIKI-96 SHIKI with imac boardid -rad24 (fix 30 bit color)


been experimenting with ATI deinit in clover but inconclusive right now..


the epic fail on the reinstall and the old install might be clover above 5000.. I have read more than 1 thread now where some folks are having issues with it. I went back to 4932 and using aptiomemoryfix and booting UEFI, native nvram not using EMU and RC scripts, and for the moment it looks more promising but the VEGA monitor init issues are plaguing .. latest LILU/WEG/ALC although with my DSDT I get the VEGA video and HDMI audio without WEG. but can't turn on hardware encode decode with boot args without it.. would need to hex edit AGDP to get hardware support if I drop WEG


if I use the iMacpro SMBIOS I loose speedstep and my multipliers are locked at 12 instead of stepping to 26-27 under load


I will send you some of the GPU.restart dumps later.. and will send you a .dsl of what maciasl dumps from my running system.. perhaps you can dif merge with your patches and figure out where the sleep error lies.. at first I thought it was the USB method for _DSM .. mine uses store and yours uses return .. tried editing yours to store, didn't make a difference .. could be just the clover version.. doing more testing today if I can find the time


thanks again for the help!!

Link to comment
Share on other sites

I am using dart=0, and no darkwake line because mald0n's config didn't have it, and I never knew if it was doing anything anyway. I can sleep & wake fine, although sometimes it will sleep but then not wake up properly - the power light comes on, but displays never wake up, and the machine doesn't respond to ping. I imagine it's GPU related as it first started happening since I installed the Vega.


I tried RadeonDeinit a couple of times and didn't notice it making any difference. However Clover's InjectATI makes a very important difference for me. Specifically:

1. It changes my GPU name from "Radeon RX Vega 64" (WEG only) to "AMD Radeon RX Vega 64" (WEG + InjectATI)

2. It changes the System Info->Graphics/Displays Metal info from: "Metal: Supported, macOS GPUFamily 2 v1" (WEG only) to "Metal: Supported" (WEG + InjectATI)

3. My Geekbench 4 score increases from ~145k (WEG only) to ~200k (WEG + InjectATI)


I don't understand quite what InjectATI does, or why it makes this important difference, but clearly I need it for full GPU performance. It's possible literally all it is doing is changing the GPU name, in which case I could likely achieve the same thing with a WEG SSDT. But I haven't tested that.


My current situation:

1. Using iMacPro 1.1 SMBIOS + mald0n's config.plist + mald0n's DSDT.aml. Plus I have added Clover's InjectATI to config.plist, which I need for full GPU performance.

2. From boot, I do not have working CPU PM: CPUs are locked at x12 multiplier

3. After sleep & wake, power management works OK: CPU multipliers x12 - x24

4. I have working h264 + h265 HW encode/decode. However, trying to use h264 encode often results in GPU freezes. This may be related to OC settings, as I have also had occasional issues in Windows 10. But, it's much worse in macOS.

5. I cannot use MacPro 5.1 SMBIOS as my 4K@60 display (DisplayPort 1.2) will never connect at 4K@60. It either connects at 2084x1080, or 4K@30, but almost never at 4K@60.

6. With iMacPro 1.1 SMBIOS, my 4K display always connects at 4K@60. However, it often does not display a picture. After sleep&wake I often have to unplug/replug it multiple times until it shows a picture. And I need to disable Display Sleep, as if the display goes to sleep, it will again lose the picture on the 4K after the displays wake up.

7. In Console, I get occasional errors like these:

 

2019-09-21 12:05:27.467141+0100  localhost kernel[0]: (IOAcceleratorFamily2) <IOAcceleratorFamily2`IOAccelEventMachine2::waitForStamp(int, unsigned int, unsigned int*)> virtual IOReturn IOAccelEventMachine2::waitForStamp(int32_t, stamp_t, stamp_t *): initial wait for 1 second expired. Continue wait for 4 seconds. stamp 1 (gpu_stamp=0)
2019-09-21 12:05:31.467235+0100  localhost kernel[0]: (IOAcceleratorFamily2) <IOAcceleratorFamily2`IOAccelEventMachine2::waitForStamp(int, unsigned int, unsigned int*)> virtual IOReturn IOAccelEventMachine2::waitForStamp(int32_t, stamp_t, stamp_t *): timeout waiting for AMDRadeonAccelerator stamp 1 (gpu_stamp=0)
2019-09-21 12:10:03.491975+0100  localhost kernel[0]: (IOAcceleratorFamily2) <IOAcceleratorFamily2`IOAccelFenceMachine::fence_timeout(IOTimerEventSource*)> void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt
2019-09-21 12:10:03.601648+0100  localhost kernel[0]: (IOAcceleratorFamily2) <IOAcceleratorFamily2`IOAccelFenceMachine::fence_timeout(IOTimerEventSource*)> void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt
2019-09-21 13:22:36.958127+0100  localhost kernel[0]: (IOAcceleratorFamily2) <IOAcceleratorFamily2`IOAccelDisplayPipe2::event_interrupt_gated()> AMDRadeonAccelerator [0]: transaction ID (165047) generated error (0xe00002d5). dirtyBits=0x1, options=0x1
2019-09-21 14:22:32.075500+0100  localhost kernel[0]: (IOAcceleratorFamily2) <IOAcceleratorFamily2`IOAccelDisplayPipe2::event_interrupt_gated()> AMDRadeonAccelerator [0]: transaction ID (184995) generated error (0xe00002d5). dirtyBits=0x1, options=0x1

 

All those errors are since my last boot, 2.5 hours ago. They are not terminal, but maybe result in slowdowns or something, I am not sure. However if I do extended h264 encoding, I will sometimes get a bunch of the blockFenceInterrupt errors, plus errors about GPURestart, and then all displays crash, and the system has to be rebooted.


[ref]MaLd0n[/ref], do you think there is any further improvement that can be made to my system? I know you have done a lot of work on it already. I'd be grateful if you could let me know if you think anything more can be done.


I am planning to buy a new PC sometime soon - my first 'new' PC in 9 years (new to me, though I will buy it used.) I am thinking maybe an HP Z840 workstation, as I need more PCIe lanes than modern CPUs have, eg for 10Gbe ethernet. But even if/when I get a new PC, I will still hope to use this one as a secondary system with a modern AMD GPU, eg RX 580.

ONE: X299X: G.byte X299X Designare 10G, Intel i9-10980XE, 128GB DDR4 3600

GPU:  Gigabyte RX Vega 64 8GB OC

SMB: MacPro 7,1. OpenCore 0.6.3

 

TWO: X58: G'byte GA-X58A-UD3R, Xeon X5670, 48GB DDR3 1600

GPU: AMD R9 280X 3GB

SMB: iMacPro 1,1. Clover: R5118 Legacy

Link to comment
Share on other sites

eleratorFamily2) AMDRadeonAccelerator [0]: transaction ID (184995) generated error (0xe00002d5). dirtyBits=0x1, options=0x1

 

I noticed I think in your files you sent up that you have other cards installed in this machine .. not just the vega..


I found while testing that my machine didn't like some cards... without a specific edit in DSDT .. most times installing supported card would break sleep.. but for example.. now that mojave completely breaks support for SIL3132 based sata cards.. I went out an bought a support card that uses Marvel and ASM controllers... I can't boot fine with it installed into el capitan with the gtx660 installed .. but the same machine, same DSDT and config.. wont boot mojave.. black screen... BUT the system is running .. BIGGER BUT.. the card is working and the 3 drive apple raid hanging on it is WORKING.. the files are there but had to ssh in to see that .. no video...


the VEGA is a very strange cat.. and SLICE was saying that there are known issues with later AMD cards and older chipsets.. likely no UEFI for you and a poor and old UEFI implementation for me.. because the same card installed in a $90 HP6300sff running mojave that took 15minutes to install mojave on .. .works just fine and doesn't block video from the installed gx710 .. I can even BOOT mojave off the $40 sata add in card.. it has 6 ports and its the only time I have ever seen an add in sata card boot OS X ... so the card is very compatible .. but on these old boards.. I think that most modern hardware is looking for UEFI support


I know that with the DX58.. when I added the vega I was running bios 5599 from a long time ago.. like say 2012.. no video.. at all not even post if I recall.. updated to 5600 which was intel last bios from say 2013.. so still very old .. but obviously they updated the UEFI option rom for graphics cards because now I have video at post...


in the old days apples hardware and COTS hardware were more similar and the OS X codebase was a bit more generically written.. today with the advent of allot of apple only tech like biometrics, T2, customized chipsets and integrated video and custom drivers and frameworks that arent used on the PC side.. hackintoshing has thinner margins for working hardware.. and 'working' is different .. lots of tradeoffs..


for example your woes with imacpro .. some of the hardware encoding that is done with that model lean HEAVILY on that T2 according to bearfeat, .. I think a lot of hardware offloading in macs is very difficult to get right in the hack because the frameworks send the work to chips we don't have .. on a pc the hardware encode would be VEGA only and the driver would send it all to the VCE stack.. in apple its drivers definitely don't work that way ..


something else to consider.. since out bioses are years behind.. is that intel has been constantly releasing updated patches for their CPUs last few years as part of the security patches ongoing from heart bleed, and others that have not even been publicly released.. well apple pushes out these firmware updates with the releases and say for macpro5,1 which hadn't had many new firmwares has had like 4 in the last year... so if apples kernel is optimized for these new microcodes and we are not getting these microcode patches in firmware . the instruction sets don't match up... BOOM


Added in 39 minutes 2 seconds:

[ref]TheBloke[/ref],


update


my machine not liking the INJECT ATI with deinit


when booted same way single monitor.. GPU fan full up, power bar on the card pulsates and I am using 200W at the wall instead of 120~

so clearly with macpro5,1 SMBIOS .. injecting is messing with GPU power management AND my luxmark scores are LOWER.. which makes no sense

Link to comment
Share on other sites

  • Administrators

[ref]duece[/ref], for solve problems with hardware accel, systeem freezes and other problems after high sierra, the best is use IntelQuickSync

<IMGUR id="4YO0fZx"><a href=https://i.imgur.com/4YO0fZx.png' alt='IMGUR>'>

<IMGUR id="d8U0kof"><a href=https://i.imgur.com/d8U0kof.png' alt='IMGUR>'>

<IMGUR id="dhBKFmb"><a href=https://i.imgur.com/dhBKFmb.png' alt='IMGUR>'>


after it system don't crash more, encoder/decoder is very very fast


check one real mac apple dump

<IMGUR id="oagmaQZ"><a href=https://i.imgur.com/oagmaQZ.png' alt='IMGUR>'> :guitar


in this case just a iMacPro1,1 smbios for check if solve, i think

-Donations-

PayPal HERE - Stripe HERE - Ko-Fi HERE - BuyMeaCoffee HERE - Mercado Livre HERE

Skrill danielnmaldonado@gmail.com - BTC 33HeGCuCSh4tUBqdYkQqKpSDa1E7WeAJQ3 - BNB 0x10D1d656eCa00bD521f9b4A43B83098B8142e115 - USDT BSC BEP20 0xb57cfdfa371fad1981910f0e8332409ab99f74d9 - USDT TRC20 TUR6Z9AVS4AYzqPnULoHrfFvppRbhXmNbZ - KASPA kaspa:qpxzufgfj8p6r0krg58yzvs0009h2mwqgvcawa0xc2pth7sgzpv56j4f6dtvk - PicPay @danielnmaldonado - PiX @danielnmaldonado@gmail.com

Premium Users HERE - Problems with Paypal HERE

xcd5u2Y.png

Sign up for a Bybit account and claim exclusive rewards HERE

New ways to earn money with Linkvertise HERE

Link to comment
Share on other sites

[ref]MaLd0n[/ref],


i agree... intel quick sync would be an answer.. if I had a motherboard chipset or CPU that supported it


I am on a x58 platform (socket 1366) and a Westmere W3680 processor .. hence .. no intel quick sync due to no CPU embedded GPU .. hence all my questions as to why your DSDT has multiple GFX0 > PEGP > GFX0 etc conversions...


only have one dGPU at PEG3 ... I define it as GFXO to give WEG the place to latch on


have not tested your third DSDT yet but the previous 2 have no sleep and make no improvements over my already edited DSDT as far as VEGA booting multiple monitors


perhaps you ran the wrong autopach against it thinking I had sandy bridge or something

Link to comment
Share on other sites

Yeah, the whole problem we have is we have no iGPU, so no way to use any Intel acceleration :(


Added in 1 minute 11 seconds:

my machine not liking the INJECT ATI with deinit


when booted same way single monitor.. GPU fan full up, power bar on the card pulsates and I am using 200W at the wall instead of 120~

so clearly with macpro5,1 SMBIOS .. injecting is messing with GPU power management AND my luxmark scores are LOWER.. which makes no sense

 

And what about without deinit?


I get the fan spinning up also only with InjectATI, but I take that as a good sign - because that was a known issue with the Vega 64 card, and possibly still is, at least with my Gigabyte OC which I have heard has its own fan controller.


Though in my case it is just the fan spinning up - not also an increase in power usage, at least not according to the stats put into IOKit, as read by HWMonitorSMC2. It's common for me to see 2600RPM fan, with 0% utilisation and ~20W power usage.


Ironically, the way to get the fan to stop spinning at full speed - at least for a time - is to put some load on the GPU, ie start playing a video. This is again a common experience from what I've read of other Vega 64 users, both Hack and real Mac Pro users. Though it was meant to be resolved in 10.14.5. So I am assuming the reason it is not resolved for me is my specific choice of Vega 64, as I found at least one site that mentioned the Gigabyte OC Vega 64s were an exception to the general fixes for fan spin, due to their proprietary fan controller.


Without InjectATI I get 25% lower GeekBench 4 scores, and one time I actually had the system freeze when I tried to run the Heaven UniEngine benchmark, which didn't happen with InjectATI


All I am setting is InjectATI - I don't set any of the other options in the same area. Which I believe means (though I may be wrong), that all InjectATI is doing is injecting the GPU name that Clover detects, which is "AMD Radeon RX Vega 64", versus the "Radeon RX Vega 64" that WEG puts in. Other settings, eg FBName, are all blank in my config.


If I'm correct about that, then that would mean that some part of the Apple drivers is looking for a particular GPU name and being affected by it? You'd think it would be based off the Vendor ID / Card ID. So maybe there's more to it than that.


I've never properly tried RadeonDeInit, so I don't really know what that does. I only tested it briefly, days ago, when I was seeing if there was any way to get rid of the need to sleep&wake. I had the impression it was an old param intended for much older cards/older versions of macOS/Clover, but who knows

ONE: X299X: G.byte X299X Designare 10G, Intel i9-10980XE, 128GB DDR4 3600

GPU:  Gigabyte RX Vega 64 8GB OC

SMB: MacPro 7,1. OpenCore 0.6.3

 

TWO: X58: G'byte GA-X58A-UD3R, Xeon X5670, 48GB DDR3 1600

GPU: AMD R9 280X 3GB

SMB: iMacPro 1,1. Clover: R5118 Legacy

Link to comment
Share on other sites

I've effectively given up for now.


Latest results:


I mentioned earlier that I had a theory that my h264 encoding freezes might be related to OCing, on the basis that earlier in the week had a BSOD in Windows 10 when doing h264 encoding on the Vega, and that after I lowered the OC a bit, it didn't return.


So earlier today I tried completely removing the OC on my X58, reverting to stock speeds with everything on AUTO.


Initial results were positive: for the first time ever I got a Premiere Pro export to work with HW accel, successfully exporting a 5 minute video with no errors in Console. So then I tried a much longer project, and within 10 minutes Console was flooded with errors and all displays froze.


Next I put the Vega 64 into my second Hack, the H77. This is my UEFI machine, not overclocked. I installed my second, backup SSD in the H77 so it was running the same software as my X58, including my exact Premiere Pro/After Effects install. (Everything the same except the EFI partition, which I booted from USB so as to use my H77 DSDT + config)


The Vega behaved exactly the same in the H77 as it did in the X58, in all respects: from boot, a single DP works, but plugging in a second display will cause all monitors to go black, and force a restart. After sleep & wake, all ports worked. InjectATI was required to get full Geekbench 4 performance.


Just about the only difference noticeable on the H77 was that using the iMacPro 1.1 SMBIOS on the H77 did not affect Speedstep.


As for HW accel: same shit. After about 10 minutes of exporting the same Premiere Pro project, the Console filled with all the same errors and the machine was dead.


So I basically give up for now. The irony is I never planned to buy a new GPU yet, I was going to wait until I was ready to buy a better workstation. But I was doing a lot of Premiere Pro and After Effects work, and I thought getting a new GPU now might speed things up. Ha! I've lost about 4 days from fucking around trying to get it to work, and now I'm back where I started.


Well, not completely. The Vega 64 is still in my second machine, booted into Windows 10, and maybe it will provide some benefit there. Though not much, as Premiere Pro/After Effects can't use AMD encode acceleration in Windows, only Intel.


I may even return the Vega. I bought it from Amazon, so I still have 3 weeks in which I can return it. Maybe the Vega 64 is just a bad card. I'd really like to get the VII Pro, as not only is it much more powerful and has 16GB, but it's also a card that's used in a real Mac - or will be when the 2019 Pro comes out. Of course it's stupidly expensive, so I doubt I'll be able to.


I've seriously thought about whether I should buy a real Mac for my 'new' computer. If the 2013 Mac Pro wasn't so shit I probably would do. But it can't be expanded, and I really need 10 Gbe internet and a modern GPU, and I can't afford a new workstation plus Thunderbolt enclosures and the like. And buying the classic Mac Pro just seems silly; spending upwards of £1000 on a system that's of exactly the same generation as the one I already have.


The easiest and safest thing to do would be to buy a system with a recent Intel consumer CPU, with Intel HD, like mald0n was saying. But then I will be very limited in PCIe lanes, and probably limited in RAM as well, and I wouldn't be able to go dual CPU,


I'm really tempted by something like the HP Z840, which can give me 16+ cores over 2 CPUs, 64, 96GB or even 128GB of RAM, and all the PCIe slots I could ever need. But that wouldn't have an iGPU, so maybe I'd end up stuck with all the same problems.


If only Apple weren't being such c***s about NVidia. Having the NVidia web drivers available would open a huge range of new cards and likely solve all these problems. I suppose I could go back to High Sierra, but I really don't like running an OS that's too old. That just introduces more problems over time. I'll already not be updating to Catalina for a while because of the stupid removal of 32bit support; being two OS' old just seems like too much.


Geez, what a mess.

ONE: X299X: G.byte X299X Designare 10G, Intel i9-10980XE, 128GB DDR4 3600

GPU:  Gigabyte RX Vega 64 8GB OC

SMB: MacPro 7,1. OpenCore 0.6.3

 

TWO: X58: G'byte GA-X58A-UD3R, Xeon X5670, 48GB DDR3 1600

GPU: AMD R9 280X 3GB

SMB: iMacPro 1,1. Clover: R5118 Legacy

Link to comment
Share on other sites

  • Administrators

[ref]duece[/ref], in this case i think don't have other solution, only iMacPro1,1 smbios

but this smbios inject other properties like usb etc


the patches is for lga 1366, ich10 properties


the problem in legacy mobos with new amd cards is: don't have csm option and csm driver clover is very strange and dangerous

-Donations-

PayPal HERE - Stripe HERE - Ko-Fi HERE - BuyMeaCoffee HERE - Mercado Livre HERE

Skrill danielnmaldonado@gmail.com - BTC 33HeGCuCSh4tUBqdYkQqKpSDa1E7WeAJQ3 - BNB 0x10D1d656eCa00bD521f9b4A43B83098B8142e115 - USDT BSC BEP20 0xb57cfdfa371fad1981910f0e8332409ab99f74d9 - USDT TRC20 TUR6Z9AVS4AYzqPnULoHrfFvppRbhXmNbZ - KASPA kaspa:qpxzufgfj8p6r0krg58yzvs0009h2mwqgvcawa0xc2pth7sgzpv56j4f6dtvk - PicPay @danielnmaldonado - PiX @danielnmaldonado@gmail.com

Premium Users HERE - Problems with Paypal HERE

xcd5u2Y.png

Sign up for a Bybit account and claim exclusive rewards HERE

New ways to earn money with Linkvertise HERE

Link to comment
Share on other sites

the problem in legacy mobos with new amd cards is: don't have csm option and csm driver clover is very strange and dangerous

 

But I have the same issues with Vega 64 in my H77 which has UEFI and CSM. So I think there is more to it than this :(

ONE: X299X: G.byte X299X Designare 10G, Intel i9-10980XE, 128GB DDR4 3600

GPU:  Gigabyte RX Vega 64 8GB OC

SMB: MacPro 7,1. OpenCore 0.6.3

 

TWO: X58: G'byte GA-X58A-UD3R, Xeon X5670, 48GB DDR3 1600

GPU: AMD R9 280X 3GB

SMB: iMacPro 1,1. Clover: R5118 Legacy

Link to comment
Share on other sites

Errr OMG


I just got the Vega 64 to boot on my H77 with two monitors connected, one HDMI.


I did it by setting CSM to Disabled in BIOS. I've literally never tried that before...


More testing starting now...

ONE: X299X: G.byte X299X Designare 10G, Intel i9-10980XE, 128GB DDR4 3600

GPU:  Gigabyte RX Vega 64 8GB OC

SMB: MacPro 7,1. OpenCore 0.6.3

 

TWO: X58: G'byte GA-X58A-UD3R, Xeon X5670, 48GB DDR3 1600

GPU: AMD R9 280X 3GB

SMB: iMacPro 1,1. Clover: R5118 Legacy

Link to comment
Share on other sites

  • Administrators

[ref]TheBloke[/ref], AMD = CSM disable / NVIDIA = CSM Enable :mrgreen:

-Donations-

PayPal HERE - Stripe HERE - Ko-Fi HERE - BuyMeaCoffee HERE - Mercado Livre HERE

Skrill danielnmaldonado@gmail.com - BTC 33HeGCuCSh4tUBqdYkQqKpSDa1E7WeAJQ3 - BNB 0x10D1d656eCa00bD521f9b4A43B83098B8142e115 - USDT BSC BEP20 0xb57cfdfa371fad1981910f0e8332409ab99f74d9 - USDT TRC20 TUR6Z9AVS4AYzqPnULoHrfFvppRbhXmNbZ - KASPA kaspa:qpxzufgfj8p6r0krg58yzvs0009h2mwqgvcawa0xc2pth7sgzpv56j4f6dtvk - PicPay @danielnmaldonado - PiX @danielnmaldonado@gmail.com

Premium Users HERE - Problems with Paypal HERE

xcd5u2Y.png

Sign up for a Bybit account and claim exclusive rewards HERE

New ways to earn money with Linkvertise HERE

Link to comment
Share on other sites

I've been testing for several hours and it's late and I'm too tired - and still disillusioned - to do a full report. I'll do one tomorrow.


The TLDR is:

1. With CSM disabled on the H77, the multi-display issue appears completely gone. I can boot with multiple monitors connected, no need to sleep.

2. HW accel encode appeared fixed at first; I was able to export my larger Premiere Pro project, which took 30+ minutes.

3. But it's not fixed fully. Using a screen recording app called Screenflick, recording a full screen game at 1080p 60 FPS, the GPU will crash within 1 - 5 minutes of the recording starting. The usual long list of IOAccel errors in Console, with all displays freezing. The system remains accessible via SSH, but a shutdown doesn't complete, so the only option is a hardware reboot or shutdown via power switch.

4. Tested with both iMacPro 1.1, and with my original SMBIOS for that machine, iMac 14.2 with the shikivga=96 ... config line. Identical results with both.


This may end up being a usable config at least for Premiere Pro encoding, if it proves that it never crashes in that config - which I don't think is guaranteed by any means. But it's clearly not 'fixed'.


At this point I have no idea if this is specific to the Vega 64 or not. It could even be specific to *this* Vega 64, although I doubt it.


What this has told me - belatedly - is that there's very likely no chance of getting this working on my X58, or any system without a proper UEFI CSM. Don't know what that means for your system, dueces, but I'd presume it's the same as mine; if you had a CSM option to disable that would fix it, I imagine you'd have found it by now.


I'll write a bit more tomorrow.

ONE: X299X: G.byte X299X Designare 10G, Intel i9-10980XE, 128GB DDR4 3600

GPU:  Gigabyte RX Vega 64 8GB OC

SMB: MacPro 7,1. OpenCore 0.6.3

 

TWO: X58: G'byte GA-X58A-UD3R, Xeon X5670, 48GB DDR3 1600

GPU: AMD R9 280X 3GB

SMB: iMacPro 1,1. Clover: R5118 Legacy

Link to comment
Share on other sites

[ref]MaLd0n[/ref], yeah. Intel shitty UEFI on this board. No CSM disable and I have to assume there is one since this board was mainstream what more than 6 years ago it would need it for windows.


Only thing left would be a complete legacy boot to see if that improves. Or perhaps figure out how to dump the cards bios and have clover load it


On the fresh test install that was put on a intel sata drive can’t get it to sleep period. Same OS X version same dsdt same config file etc as the one from last month and that one is sleeping. Mojave want me to tear my hair out.

Link to comment
Share on other sites

A couple more bits of info, FWIW:


Once I got the Vega 64 booting reliably in the H77 with CSM disabled, I experimented with InjectATI on and off.


InjectATI off: Fans work normally. GPU detected as "Radeon RX Vega 64". Metal support listed as "Supported, GPUFamily 2v1". IOKit performance statistics/info messages are fully accurate. Geekbench score: 145k. Heaven uniEngine Benchmark result: 99-101 FPS.


InjectATI on: Fans mostly at 100%. GPU detected as "AMD Radeon RX Vega 64". Metal support listed as "Supported". IOKit performance statistics/info messages are often inaccurate, eg showing Power Usage at 650W (impossible), Core Clock never going above 750Mhz even at 100% utilisation, and often VRAM Free/Used does not add up to the correct amount. Geekbench score: 200k. Heaven uniEngine Benchmark: 100-102 FPS.


So nearly everything is better with InjectATI off. It's just that Geekbench 4 benchmark, consistent across both Metal and OpenCL benchmarks. But then the Heaven benchmark was the same in both modes.


The end result is I am not using InjectATI, because it definitely introduces problems, and while one benchmark shows it to be faster, another shows no difference.


On the HW h264 encode issue: I today booted into Windows 10 and recorded 25 minutes of a game at 60 FPS, high quality, no issues. So I am almost certain the card itself is fine. It's definitely some macOS/Hack issue.


I get the h264 encode crashes both with iMacPro 1.1 and with iMac 14.2 with shikivga=96.


I tried doing a sleep & wake, even though it's no longer needed for multi-monitor support, but that made no difference; h264 encode still freezes the GPU even after a sleep.


So I am out of ideas on that one. I have a mostly working Vega 64 in the H77, but one of the main reasons I bought the card was to get h264 encode, and if that's not reliable then I think I will be forced to stay in Windows for now.


So frustrating.


For the record, here are the errors I get when the GPU freezes during h264 encode:

 

kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt
kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt
kernel[0]: (IOAcceleratorFamily2) AMDRadeonAccelerator: IOAccelDisplayPipeTransaction time out after 300ms. framebufferIndex=5
kernel[0]: (IOAcceleratorFamily2)     framebufferIndex=5, wsaa=17
kernel[0]: (IOAcceleratorFamily2)     eventInterruptEnabled=0, transactionInterruptEnabled=1, vblInterruptEnabled=0
kernel[0]: (IOAcceleratorFamily2)     powerOff=0, pipeTerminated=0, acceleratorEnabled=1, fWSAA=17
kernel[0]: (IOAcceleratorFamily2)     lastIOGraphicsMessageEvent=93, fbIndex=5
kernel[0]: (IOAcceleratorFamily2)     transactionQueueReadCount=12055, transactionQueueWriteCount=12056
kernel[0]: (IOAcceleratorFamily2) lastCompletedTransaction: ID=12054 dirtyBits=0x1 options=0x1
kernel[0]: (IOAcceleratorFamily2)     pendingTransaction ID=12055, isTransactionComplete()=0, dirtyBits=0x1, options=0x1, errorCode=0x0, submittedReturn=0xe0014042
kernel[0]: (IOAcceleratorFamily2)     readTransaction ID=12056, dirtyBits=0x1, options=0x1, errorCode=0x0, submittedReturn=0xe0014042, event hasn't finished
kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt
<last message repeated many times>
kernel[0]: (IOAcceleratorFamily2) virtual IOReturn IOAccelEventMachine2::waitForStamp(int32_t, stamp_t, stamp_t *): initial wait for 1 second expired. Continue wait for 4 seconds. stamp 15313 (gpu_stamp=15312)
kernel[0]: (IOAcceleratorFamily2) virtual IOReturn IOAccelEventMachine2::waitForStamp(int32_t, stamp_t, stamp_t *): initial wait for 1 second expired. Continue wait for 4 seconds. stamp 9557 (gpu_stamp=9556)
kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt
<last message repeated many times>
kernel[0]: (IOAcceleratorFamily2) virtual IOReturn IOAccelEventMachine2::waitForStamp(int32_t, stamp_t, stamp_t *): timeout waiting for AMDRadeonAccelerator stamp 15313 (gpu_stamp=15312)
kernel[0]: (IOAcceleratorFamily2) virtual IOReturn IOAccelEventMachine2::waitForStamp(int32_t, stamp_t, stamp_t *): timeout waiting for AMDRadeonAccelerator stamp 9557 (gpu_stamp=9556)
kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt

<last message repeated many times>

kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 0..
kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=0 type=2
kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 2..
kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartSignaled stampIdx=2 type=2 prevType=0 numStamps=22
kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=2 type=2
kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 5..
kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartSignaled stampIdx=5 type=2 prevType=0 numStamps=22
kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=5 type=2
kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 6..
kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartSignaled stampIdx=6 type=2 prevType=0 numStamps=22
kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=6 type=2
kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 12..
kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartSignaled stampIdx=12 type=2 prevType=0 numStamps=22
kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=12 type=2
kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 17..
kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartSignaled stampIdx=17 type=2 prevType=0 numStamps=22
kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=17 type=2
kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 18..
kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartSignaled stampIdx=18 type=2 prevType=0 numStamps=22
kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=18 type=2
kernel[0]: (IOAcceleratorFamily2) virtual void IOAccelEventMachineFast2::checkGPUProgress() - Signaling hardware error on channel 19..
kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartSignaled stampIdx=19 type=2 prevType=0 numStamps=22
kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::signalHardwareError(eRestartRequest, int32_t): GPURestartEnqueued stampIdx=19 type=2
kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::hardwareErrorEvent(): setting restart type to 2 (channel 0)
kernel[0]: (IOAcceleratorFamily2) void IOAccelEventMachine2::hardwareErrorEvent(): GPURestartDequeued stampIdx=0 type=2
kernel[0]: (AMDRadeonX5000) [3:0:0]: channel 0 event timeout
kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt
kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt
kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt
kernel[0]: (IOAcceleratorFamily2) virtual IOReturn IOAccelEventMachine2::waitForStamp(int32_t, stamp_t, stamp_t *): a graphics error occurred, exitting..
kernel[0]: (IOAcceleratorFamily2) virtual IOReturn IOAccelEventMachine2::waitForStamp(int32_t, stamp_t, stamp_t *): a graphics error occurred, exitting..
kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt
kernel[0]: (AMDRadeonX5000) [3:0:0]: channel 0 GFX is hung! (lastReadTimestamp=0x0001212a) channelResetMask 0x00000000
kernel[0]: (AMDRadeonX5000HWLibs) AMD Cail: [3:0:0] GPU HangState 0x00000040, HangFlags 0x00000005: IndividualEngineHang 1, NonEngineBlockHang 0, FenceNotRetired 1, PerEngineReset 1, FullAsicReset 0
kernel[0]: (AMDRadeonX5000HWLibs) [3:0:0] GPU HangState 0x00000040, HangFlags 0x00000005: IndividualEngineHang 1, NonEngineBlockHang 0, FenceNotRetired 1, PerEngineReset 1, FullAsicReset 0
kernel[0]: (IOAcceleratorFamily2) virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
kernel[0]: (IOAcceleratorFamily2) virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
kernel[0]: (IOAcceleratorFamily2) virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
kernel[0]: (IOAcceleratorFamily2) virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
kernel[0]: (IOAcceleratorFamily2) virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
kernel[0]: (IOAcceleratorFamily2) virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
kernel[0]: (IOAcceleratorFamily2) virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
kernel[0]: (IOAcceleratorFamily2) virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
kernel[0]: (IOAcceleratorFamily2) virtual sIOAccelEvent *IOAccelFIFOChannel2::getFirstPendingEvent(): All are finished
kernel[0]: (IOAcceleratorFamily2) void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt
kernel[0]: (AMDRadeonX5000) [3:0:0] ** AMDRadeonX5000_AMDVega10GraphicsAccelerator Device in slot: SLOT--1 **
kernel[0]: (IOAcceleratorFamily2) Trying to restart GPU (Radeon RX Vega 64)...
kernel[0]: (AMDSupport) AMD Recovery Display.
kernel[0]: (Sandbox) Sandbox: tailspin(1751) deny(1) sysctl-write kern.procname

ONE: X299X: G.byte X299X Designare 10G, Intel i9-10980XE, 128GB DDR4 3600

GPU:  Gigabyte RX Vega 64 8GB OC

SMB: MacPro 7,1. OpenCore 0.6.3

 

TWO: X58: G'byte GA-X58A-UD3R, Xeon X5670, 48GB DDR3 1600

GPU: AMD R9 280X 3GB

SMB: iMacPro 1,1. Clover: R5118 Legacy

Link to comment
Share on other sites

[ref]TheBloke[/ref],


if you are intent on using the imacpro1,1 smbios then perhaps you need to continue investigating whether shikiGVA values are even needed... since the vega is natively supported in that SMBIOS you probably should run without WEG at all.. should not need it to turn on functionality


again.. in windows .. the drives just point all encodode/decode at ATIs drivers .. simple


in the Mac the fruit company uses many different video handling frameworks... and in systems with shared dGPU and intel, quick sync takes the load in the iMacpro, where they could simply throw it at the ATI, the T2 chip gets involved ..


I doubt that ATI will bite the hand that feeds it, so I don't expect to see ATI release purpose drivers ... the only open architecture machine that apple officially/ unofficially support is the macpro5,1 .. that that special relationship is over now that the new machine is due for release... apple realized with the trashcan the professionals used pci-e cards and wanted/needed open hardware architecture .. so as to no loose the entire professional user base, many of which didn't upgrade to the trashcan.. they gave them just enough to drag them to this point but they are intentionally not providing hardware encoding for 265 which the card is more than capable of in hope of pushing new hardware .. plain and simple.. and I doubt that will change.. at the start of Catalina beta.. the 5,1 was going to be an approved machine, but when the new pro was announced and marketing starts making the calls, 5,1 is now dropped ...


until someone hacks the video processing framework or writes a program that goes around the framework calls and deals with the card directly ... perhaps we will see something in the future but most devs don't deviate from apple frameworks...

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.





×
  • Create New...