Jump to content

Jaidy

Members
 View Profile  See their activity

  • Posts

    237

  • Joined

  • Last visited

 Content Type 

Everything posted by Jaidy

  1. Jaidy
    there still doesn't seem to be a working driver for these GPUs in Big Sur, so we could wait. Though the way things have been going, it seems there'd be a shortage till sometime Q1 2021
  2. Jaidy
    Would you please follow the ritual of uploading your EFI? 🙂
  3. Jaidy
    thanks 🙂
  4. Jaidy
    will upgrading to OC 0.6.4 possible with the existing config.plist for OC 0.6.3 you generously provided?
  5. Jaidy
    Is there someone who uses Julia? On my MacBook Pro, the Julia libraries install and test successfully, while on the hackintosh, there are a lotta problems. Even if it’s not Julia, it is similar a case for Python too - but those were forced to compile with openBLAS (previously they assumed MKL). I suspect it’s the same problem here. I Googled to try forcing Julia and any libraries to use openBLAS but there still are problems..
  6. Jaidy
    I would like to thank everyone for their awesome effort in bringing macOS to TRX40 platform, especially @fabiosun @Ploddles @iGPU. Regarding the EFI, I shamelessly use @Ploddles as they are (our systems are virtually identical)..
  7. Jaidy
    So while I don’t think I would be able to source a RX 6800 XT or RX 6900 XT in three weeks, but is there a driver for these GPUs in Big Sur?
  8. Jaidy
    @Ploddles @fabiosun the latest EFI folder did the trick. Thanks a ton 🙂
  9. Jaidy
    I just checked the config.plist on my EFI folder, and the setting of SecurebootModel is indeed Disabled, still the onboard WiFi isn't working. Is there any other setting for that?
  10. Jaidy
    @Ploddles what is the setting to enable the WiFi built into the Gigabyte's motherboard to work in Big Sur in your config.plist? Sorry I forgot..
  11. Jaidy
    Looking at the presentation today, Apple claims that Big Sir is supposed to be significantly faster (at launching apps, switching between them, performance wise etc.) than Catalina. Have you observed this on your hack/MBP? P.S. when the update to Big Sur arrives, it should go through seamlessly using your EFI, right?
  12. Jaidy
    I looked at it before posting here. MKL won't install at all. The installer just fades away when clicked on. I think the DUBUG mode was discontinued in the previous builds (probably due to this notoriety?)..
  13. Jaidy
    is there any one here who uses products that on the backend use Intel's MKL, like numpy, MATLAB etc.? If so, can you please tell me how did you manage to get them to work, as I can not install Intel's MKL library yet - and openBLAS while works perfectly fine, is there a way to configure numpy etc. to use openBLAS instead of MKL? Of course if MKL works, then no need to openBLAS..
  14. Jaidy
    oh boy, the Zen 3 reviews are damn good! Give the Threadripper 5xxx already!!!
  15. Jaidy
    Yeah I just used your EFI and the error vanished! Thanks
  16. Jaidy
    Thanks @meina222 @fabiosun @Ploddles. It works now after setting the PlatformInfo -> Automatic to No 🙂 There is a crazy thing though, as noted previously by @Ploddles too, that Kext Updater, and Hackintool both still detect the version of OC to be 0.6.1, but that is fine by me. The files really have been updated to 0.6.3.
  17. Jaidy
    @Ploddles @meina222 this is the message it gives at boot. It was giving this message when I did exactly what @meina222 said about the upgrading procedure - simply updating the files from the OC 0.6.3. @Ploddles this error still comes up after replacing my EFI with yours.. config.plist.zip
  18. Jaidy
    I have leeched on @Ploddles so much that I feel shy asking for any more EFIs. I tried updating, but it gives me some error message at startup. Will you please share your config.plist file for 0.6.3?
  19. Jaidy
    I’m looking forward to Big Sur due to the rumors of it carrying drivers for AMD’s 6x00 series.
  20. Jaidy
    You are correct to the point that CUDA is closed source, and leverages nVidia's specific hardware. Though OpenCL can do much of what CUDA does, in the sense of freeing us from the worries of allocating and de-allocating memory manually, and also moving data between VRAM and system RAM. I am a Ph.D. student in computer science, and I do numerical linear algebra, and its applications in machine learning. I need to perform computations with huge matrices. They can be parallelized in openCL too, just that the CUDA wrappers are way too sweet. If someone writes similar wrappers for AMD GPUs using openCL (I am not sure about Vulkan if that is another API?), AMD has had higher theoretical TFLOPs till last generation! And Apple and Nvidia need to grow up. Besides Apple too likes to keep things proprietary (just look at the lightening connector). Anyway, the Navi 2 series is awesome, and I am so looking forward to getting my hands on one of these! 🙂
  21. Jaidy
    you know @fabiosun, now I won't be asking if Nvidia cards are compatible with macOS any more 😛. I hope AMD (or someone else) writes a counterpart of CUDA for AMD GPUs which would make my life so much better!
  22. Jaidy
    I heard these cards should be compatible with macOS OOB already. Is this true?
  23. Jaidy
    Just like when using system audio over DP/HDMI, the volume can not be controlled using the macOS controls. I just got a DAC (connected via USB), and I think previously I was able to use the macOS controls with a USB DAC, but this time around, the volume controls are disabled.. I would like the EFI too 😛
  24. Jaidy
    @Rox67er do you have an app that allows for volume controlling from within the macOS using its controls when you use your DAC?
  25. Jaidy
    Hello everyone, I tried upgrading to OpenCore 0.6.2, but I am getting random kernel panics leading to system being restarted. It has to do something with power management, but that's all my (lack of any) expertise tells me. EFI The message for the panics is the following: panic(cpu 0 caller 0xffffff7fa05a6f3d): CPU 63 has no HPET assigned to it Backtrace (CPU 0), Frame : Return Address 0xffffff93dec43c90 : 0xffffff801d11a65d 0xffffff93dec43ce0 : 0xffffff801d254a75 0xffffff93dec43d20 : 0xffffff801d2465fe 0xffffff93dec43d70 : 0xffffff801d0c0a40 0xffffff93dec43d90 : 0xffffff801d119d27 0xffffff93dec43e90 : 0xffffff801d11a117 0xffffff93dec43ee0 : 0xffffff801d8c1a6c 0xffffff93dec43f50 : 0xffffff7fa05a6f3d 0xffffff93dec43f60 : 0xffffff7fa0591882 0xffffff93dec43fa0 : 0xffffff801d0c013e Kernel Extensions in backtrace: com.apple.driver.AppleIntelCPUPowerManagement(222.0)[C5BB0AFD-CB31-3FD1-BF3B-773B2919A970]@0xffffff7fa058b000->0xffffff7fa05b4fff BSD process name corresponding to current thread: kernel_task Boot args: -v -wegbeta -no_compat_check amfi_get_out_of_my_way=1 Mac OS version: 19H2 Kernel version: Darwin Kernel Version 19.6.0: Mon Aug 31 22:12:52 PDT 2020; root:xnu-6153.141.2~1/RELEASE_X86_64 Kernel UUID: 05D51A3D-3A87-3FF0-98C3-9CF3827A3EDD Kernel slide: 0x000000001ce00000 Kernel text base: 0xffffff801d000000 __HIB text base: 0xffffff801cf00000 System model name: MacPro7,1 (Mac-27AD2F918AE68F61) System shutdown begun: NO Panic diags file available: YES (0x0) System uptime in nanoseconds: 91267996860
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.