![]() ![]() ![]() Almost all of us here are users trying to help out other users. This is not an official VMware support forum. I'm not sure how much further we can take this issue here. This meant that some Mac models that were supported by macOS were not supported by Fusion because their CPUs lacked certain instructions. For example in a past release VMware added a CPU requirement. VMware is also known to modify Fusion to take advantage of the hardware. And Fusion uses those more than your garden variety application. Apple continues to refine things like Metal and Hypervisor Framework, and its very, very likely that those changes have dependencies on the underlying hardware for certain functionality. If that something doesn't work on a patched Mac, but does on a supported Mac, then you need to be contacting the Open Core community because they're the only ones that have the expertise on that frankenMac.įusion is quite different than the other applications that work with Open Core in that it's highly sensitive to hardware and software capabilities. But you have to go into that world with eyes wide open and realize that there may be things that will not work. All the software I usually use works, except VMWare.īut OpenCore is still modifying the operating system as released by Apple which makes it unsupportable by Apple. On my 2012 MBP for example, Monterey works better than Catalina, bluetooth in particular is better managed. T's a shame, because many people use Open Core with great satisfaction. 2014 Mac mini with integrated Intel graphics. If it worked under Big Sur and whatever version of Fusion you had, drop back to dittos here. It's possible that VMware addressing the issues for supported Macs/macOS may help you but that's a chance you would be taking. The error message is somewhat of a "catch-all" that can have many different causes. Just because you're seeing the same symptom doesn't mean you have the same underlying cause. While the symptoms you are seeing may be the same as some (but not all) are seeing, you won't get VMware to look at a configuration that they don't officially support. (probably because Oracle is not going to make the investments in a free product to transition the macOS version to using the Apple hypervisor frameworks like VMware and Parallels are doing). If you look at Oracle's documentation, VirtualBox is not supported on Big Sur or Monterey. VirtuaBox is a totally different implementation and continues to use legacy kernel extensions. Fusion uses the Apple Hypervisor framework. I might go back to the simpler open-source drivers.Virtual Box is not Fusion and does not have the same dependencies on macOS capabilities sets that Fusion does. Getting the Nvidia drivers running isn’t straight forward on this mac specific hardware - especially for someone like me who hasn’t explored this stuff before. I’m thinking I should just accept that this machine isn’t a hard-core gaming or 3D rendering machine. OpenGL: renderer: GeForce GT 650M/PCIe/SSE2 v: 4.6.0 NVIDIA 390.154 Loaded: modesetting,nvidia unloaded: nouveau gpu: i915,nvidia |=|ĭevice-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernelĭevice-2: NVIDIA GK107M driver: nvidiaĭevice-3: Apple FaceTime HD Camera (Built-in) type: USB driver: uvcvideoĭisplay: x11 server: X.Org v: 21.1.4 driver: X: | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. Then I reinstalled Plasma Manjaro and ran, pamac install nvidia-390xx-utils linux515-nvidia-390xx lib32-nvidia-390xx-utils libxnvctrl-390xxĭidn’t seem to have the desired affect, ~> nvidia-smi When I selected “Discrete”, it automatically switched back to “Dynamic”. gfxcardstatus version 2.2.1 wasn’t available as a packaged release, so I installed 2.3 (after manually allowing some certificates globally in Keychain). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |