anyone try the 11.3 developer beta just released?
Lets hope something new is there... also AMD drivers for Apple Silicon would be great so we can use eGPU on new Macs while we wait for M1X which probably will render eGPU useless in most scenarios.anyone try the 11.3 developer beta just released?
how about the 6800 (non-XT) in a 5,1 - think that might work without any mods?I don't think a 5,1 will have the PSU to power a 6900XT, MAYBE a 6800XT with a Pixlas mod, but that would involve getting it up to Big Sur or Bootcamping via OpenCore. Apple depreciated Open CL, which Blender uses to do GPU rendering on macOS, so currently there is no way to do GPU rendering in Cycles on macOS and Blender. They are moving Blender to Vulkan and hopefully will port that to Metal via MoltenVK, but that is a ways out. If you want to do GPU rendering in Blender, a PC with an Nvidia card is unfortunately your best bet right now.
That's not exactly true.Apparently Apple removed the 6000 drivers from the latest Beta...
There is still remnants of AMDRadeonX6000_AmdRadeonControllerNavi21 in the new binary of X6000Framebuffer.kext, but it looks like they have refactored a ton and moved all the Navi 10, 12 and 14 code to go off a new Controller named AMDRadeonX6000_AmdRadeonControllerNavi instead. Maybe next beta I guess.
The WindowServer fails to load, unlike 11.2. But this can be a bug. Seems that there's some conflict with PerfPowerService and Radeon6000FrameBuffer and the WindowServer.
The fact that the kext still loads and that there's still mention of Navi21 in the binary does mean support is not gone completely. Based on findings of them refactoring Navi10 to a new controller it seems likely they're in the middle of refactoring the code to separate out RDNA1 and RDNA2 hardware. It always seemed slightly odd to me that they'd add RDNA2 to the same controller as RDNA1, and maybe that was just a quick temporary measure to provide the basic non-accelerated output that they put in 11.1.
I'm still not quite sure why they bothered adding the device IDs so early if they had no intention of providing the full drivers for a while longer. Perhaps they were using their telemetry data to log how many users were trying Big Sur with 6000-series cards so as to decide how important it was to support them quickly.
Which forum was this?That's not exactly true.
Here are some quotes from another forum:
Not even at MacRumors, and I wouldn't like to mention this Apple-ish related website. I think you can find it on Google.Which forum was this?
LOL, what's wrong with Hackintoshes?Not even at MacRumors, and I wouldn't like to mention this Apple-ish related website. I think you can find it on Google.
I am going to do the bootcampdrivers.com route today to see how that goes.
I am now at 1909. It was difficult to get there because Windows told me it would update to 1909, but it jumped to 202H instead (frustrating). IMHO 1909 works. 202H is NOT good with the AMD drivers yet, at least I was experiencing "driver hangs" and other nasty stuff. I had no such issues on Win 1803 or 1909.
Just to check, are you saying we could use fusion to boot into a UEFI win 10 install in macos? That's great if it works, as I've got fusion player installed on my MBP for my bootcsmp there but didn't realise it would work with the Mac Pro UEFI install.-Fusion: If you need to be in mac OS and working on something else in windows boot camp, fusion is great for allowing that and the latest version supports directx11 with its virtual drivers. Caveat: DONT use fusion to install the AMD drivers or do any operations related to AMD drivers with the exception of UNINSTALL using DDU or AMD's uninstall utility (which is inside their software install; it is also in bootcamp). The new Fusion is Free for some use cases. I paid so I am not 100% sure it will support boot camp. It's worth the money though.
Just to check, are you saying we could use fusion to boot into a UEFI win 10 install in macos? That's great if it works, as I've got fusion player installed on my MBP for my bootcsmp there but didn't realise it would work with the Mac Pro UEFI install.
Thanks for the info. I'll have to play around with this, after i make a clone of my win 10 system. Fusion player with my MBP was pretty good for getting Win 10 updates done while I'm in MacOS, except the fan was on full blast.Adding to the above comment, VMWare has supported UEFI boot for a while. Not only can it boot off UEFI OS installs from physical drives, but also from virtual drives.
It’s just a toggle in the settings to enable VMWare’s UEFI implementation. It’s actually required to boot EFI only systems like macOS in VMWare.
Thanks! Will try it out.Yes- the bootcamp trick has been up VMware's sleeve for a while. VMware workstation and fusion have always had the ability to operate directly on a drive partition instead of a vmdk "file" (virtual machine disk). I now have 3 macs doing this.
By the way a bit more information on windows. I have gotten pro versions based on some advice here and elsewhere. However, every time I upgrade my win 10 1909 image to pro, the AMD card starts getting those nasty timeouts and often I get kernel panics. So stick with Win 10 home unless you have something better. I may try upgrading first, and then doing the bootcampdrivers.com install at some point when I'm bored. Waste of an expensive windows license so far.
100% Agreed.These GPUs were released 3 months ago. Apple and AMD would have had time to put drivers into Mac OS long before that as well.
They don't give a ****, not their priority...How does a 2 trillion dollar company fail so hard at this?
As annoying as it might be for anyone looking to beef up performance via generic PC components, I feel you rant misses the mark a bit. As pure 'venting' it's fine enough, but Apple only coordinates releases of hardware/software with their own products.This is insulting to everyone in this thread, other pro mac user and embarrassing for Apple now. These GPUs were released 3 months ago.
No.I am 100% sure that the drivers will be ready when the next modules launch.
No.
These same GPUs have been functioning for 3 months for people on Windows. There's NO EXCUSE.
You don’t get drivers for GPU until Apple ships a product with that architecture. This isn’t news. They have to test the GPU with their own system first and they can’t provide tech support for people having bugs with a new GPU until they themselves are shipping the same.
Apple develops, integrates, and supports macOS GPU drivers to ensure there are consistent GPU capabilities across all Mac products, including rich APIs like Metal, Core Animation, Core Image, and Core ML. In order to deliver the best possible customer experience, GPU drivers need to be engineered, integrated, tested, and delivered with each version of macOS. Aftermarket GPU drivers delivered by third parties are not compatible with macOS.
The GPU drivers delivered with macOS are also designed to enable a high quality, high performance experience when using an eGPU, as described in the list of recommended eGPU chassis and graphics card configurations below. Because of this deep system integration, only graphics cards that use the same GPU architecture as those built into Mac products are supported in macOS.