Search results

Loading Google Results...
  1. obus

    [SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

    Could be that I mixed my different IOReg. Attached is a new one and system logs with the correct thunderbolt SSDT for bios 3406.
  2. obus

    [SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

    Hi @Elias64Fr Thank's for your support. Systemlog as requested. The New feature "Support Resize BAR function (SAM)" is probably Not the cause because I have had this problem with 90% of all the old bios. There is only two bios working for may rig (1202 and 3003). Both of them is more than one...
  3. obus

    [SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

    Hi @CaseySJ and/or @Elias64Fr. Sorry if this might be the wrong forum for my problem but I need some help with my two Thunderbolt 3 TitanRidge cards flashed with @Elias64Fr:s DESIGNARE-Z390-NVM33-Elias64Fr firmware. Both my two cards are working flawlessly on my rig with two out of maybe ten...
  4. obus

    11.4 Update Caused OpenCore patch for Intel I225-V 2.5GBe Controller Stopped Working

    oli.matihieu said: Can you disable one of the two NIC from the BIOS ? Yes I can disable both. If I disable only booth booting vent fine but you just needs to disconnect the two cables for booting. Check my thread here https://www.insanelymac.com/forum/topic/348114-cant-update-big-sur-113-to-114/
  5. obus

    11.4 Update Caused OpenCore patch for Intel I225-V 2.5GBe Controller Stopped Working

    Hi @oli.mathieu I have more or less the same problem as you. My two intel i210 ethernet ports are giving me KP when booting into Big Sur 11.4. Obviousely a problem with how OC 0.7.0 (in my case) are injecting AppleIntelI210Ethernet.kext. Everything is working in Clover. Remove Alcid=1 from boot...
  6. obus

    [SOLVED] Help with installing HighSierra on Xeon W-2175 and Asus WS C422 mobo

    Never use Clover driver in OC. You can make any further comments on my thread here: https://www.insanelymac.com/forum/topic/335193-help-installing-mojave-on-xeon-w-2175-and-asus-ws-c422-mobo/?page=15
  7. obus

    [SOLVED] Help with installing HighSierra on Xeon W-2175 and Asus WS C422 mobo

    And this EFI you can use with bios v.3003 Bios 3003 has locked MSR0xE2 register but with OC this is not a problem. Upgrade your bios and test this EFI. It should work for you but don't forget to put in MLB,ROM,SystemsSerialNumber and SystemUUID in config.plist. My C422-XHCI.kext for the USB 15...
  8. obus

    [SOLVED] Help with installing HighSierra on Xeon W-2175 and Asus WS C422 mobo

    My bad. Test this config.plist It should work like a treat. Don't forget to fill in MLB,ROM,SystemsSerialNumber and SystemUUID. This EFI will only work on bios 1202. NOT 3003 (the latest).
  9. obus

    [SOLVED] Help with installing HighSierra on Xeon W-2175 and Asus WS C422 mobo

    Hi @cwbm I'am on OpenCore but if that is no problem you could test this complete EFI. Just edit Platforminfo in config.plist. You need to put in your own MLB, ROM, SystemsSerialNumber and SystemUUID under Platforminfo --> Generic. No other changes. Keep me posted if it works.
  10. obus

    Asus X299 - Catalina Support

    The Memory tab was not showing up in 0.5.3 The memory warning is there for both OC versions.
  11. obus

    Asus X299 - Catalina Support

    Thank's @Loloflatsix Forgot to say that I was on OpenCore (OC) Release 0.5.3 and if you chose Generic setup for the SMBIOS in Platforminfo there is not even a tab for PlatformFeature. This is solved in OC 0.5.4 Master release so the memory tab is now showing up as it should in About This Mac.
  12. obus

    Asus X299 - Catalina Support

    Nice to see that memory is showing up in System Preferences on your installation. I have a ASUS C422 board and tried the MacPro7,1 SMBIOs but can't see anything about memory in System Preferences at all on Catalina 10.15.2. Don't even have the Memory tab showing up. Any clue?
  13. obus

    Successfully patched Z170X-UD5 TH CFG Lock (MSR Ex02)

    Offset is now set to 0x00 with your suggested command but when checking with VerifyMSRE2.efi the register is still locked and stuck at boot. All this is with the new 3003 bios. With the old bios,1202 everything is working and the register is unlocked. Can you have any info from my old firmware...
  14. obus

    Successfully patched Z170X-UD5 TH CFG Lock (MSR Ex02)

    Funny still locked with value 0x00?
  15. obus

    Successfully patched Z170X-UD5 TH CFG Lock (MSR Ex02)

    Yep. I see that now. I will run VerifyMSRE2 once again. Hang on!
  16. obus

    Successfully patched Z170X-UD5 TH CFG Lock (MSR Ex02)

    Cheers. I can change if you want but it will take some minutes.
  17. obus

    Successfully patched Z170X-UD5 TH CFG Lock (MSR Ex02)

    The command is working. "setup_var_3 0x537" didn't give what you expected "0x1 (or 0x01) is locked, 0x0 (or 0x00) is unlocked". It gave the same message as the first one Iv'e tried see attached picture:
  18. obus

    Successfully patched Z170X-UD5 TH CFG Lock (MSR Ex02)

    Ok command "setup_var_3 0x537 0x00" in grub unfortunately didn't work. Still Locked.
  19. obus

    Successfully patched Z170X-UD5 TH CFG Lock (MSR Ex02)

    Thank's I will test that immediately. Will report back in a while.
Top