Recent content by jarekd

  1. jarekd

    Gigabyte Z390 M Gaming build with working NVRAM

    I think the problem is those are Samsung. Heard bad things about it in connection with Macs / hMacs. Personally, I've choosen WD ones - works great.
  2. jarekd

    Gigabyte Z390 M Gaming build with working NVRAM

    Double chceked everything, and there is something more to this than just wrong HWMonitor reporting, I think... I've triple-run VRay Benchmark under macOS Catalina and Win10. Mac: (temps and power from HWMonitor) score: 10658-10696 temps: 94-99 deg C power usage: 155-170W Win: (temps and power...
  3. jarekd

    Gigabyte Z390 M Gaming build with working NVRAM

    @pastrychef just noticed some strage behaviour: under Win10, while rendering something, CPU temps reach max 75-80 deg C - and the CPU is running full speed (checked with CPUZ). When I render under MacOS - HWMonitor shows temps around 95-100 deg C... Is it possible that under MacOS CPU is clocked...
  4. jarekd

    Gigabyte Z390 M Gaming build with working NVRAM

    @pastrychef Installation went smooth :) Only one problem: on the BIOS screen, I'm getting this message: "OCS: Failed to parse data field as value with type mdata and <b42e994ea059> contents, context <ROM>!" b42e994ea059 is my MAC address
  5. jarekd

    Gigabyte Z390 M Gaming build with working NVRAM

    LOL - stupid me... opened config.plist of Clover install, and that's why I couldn't figure out where to pot those numbers... :D Thanks again :)
  6. jarekd

    Gigabyte Z390 M Gaming build with working NVRAM

    @pastrychef thanks. Will stick to it too, then :) One more thing: I'm creating fresh install now, and I want to test OpenCore (I was using Clover up to this point). Where in the config.plist should I enter serial, board serial, SmUUID and MAC numbers? (I'm using raw text editor, Sublime Text)...
  7. jarekd

    Gigabyte Z390 M Gaming build with working NVRAM

    @pastrychef I've just noticed there is new BIOS for our board - 9m verison. Have you tested that by any chance?
  8. jarekd

    Gigabyte Z390 M Gaming build with working NVRAM

    @pastrychef Hi. Got my Catalina hackintosh running on you older EFI folder (Clover) and instructions some time ago - THANK YOU! :) Recently wanted to upgrade kexts and Clover itself - but trying to install the latter given me some error (tried to google it - no results found). I've found that...
  9. jarekd

    Gigabyte Z390 M Gaming build with working NVRAM

    Thanks for confirming this. That means it's the problem with BIOS itself, not problem on my side (i. e. faulty update, etc).
  10. jarekd

    Gigabyte Z390 M Gaming build with working NVRAM

    @pastrychef: it's minor problem, I think, but really frustrating... after upgrading "our" mainboard to version 9G (I was at older version till this time, updated because you recommended that) BIOS it's switching ... to French language every time I shut down the computer :D Gigabyte support only...
  11. jarekd

    Bluetooth and WiFi - buying advice needed :)

    @theruck - been there, but there is only list with hardware. From reading the forums I know, that some of those listed there, have some problems.
  12. jarekd

    Bluetooth and WiFi - buying advice needed :)

    Hi. Right now I'm on Mojave, soon will be upgrading to Catalina. I'm using ASUS Bluetooth 4.0 dongle for my MagicMouse - but when connected directly to USB port on my computer, it lags and/or disconnects from time to time and I need to use USB extender cable for it. My questions: - Can you...
  13. jarekd

    Updating kexts and clover

    @jaymonkey thanks :) Just installed fresh copy of Catalina on new SSD, leaving Mojave on separate one. @bufferOverflow I've kept kext in /L/E - it's easy with Hackintool :)
  14. jarekd

    << Solved >> USB 2.0/3.0/3.1 Fix

    Strange... I have the same mobo. Works here. Do you want to try my DSDT file?
  15. jarekd

    Updating kexts and clover

    @jaymonkey, thanks for reply and warnings, but ... I was impatient and just backup everything and went with updates :D 1. As for the Clover, it correctly moved drivers from UEFI64 to new folder (drivers > UEFI) by itself, leaving old one in place. As it was suggested there, I removed all non...
Back
Top