Jump to content

joedm ru

Members
  • Content Count

    53
  • Joined

  • Last visited

About joedm ru

  • Rank
    InsanelyMac Protégé

Recent Profile Visitors

888 profile views
  1. joedm ru

    HWSensors3

    Make sure that it doesn't escape your experiments. GPU must be working only as a support for IQSV, this is how real Macs work. And that's how the majority of hackintosh community use it on desktop systems. I.e., IGPU works on "0 connector" framebuffer and doesn't appear in "About this Mac - Graphics/Monitors". But in this case IGPU would be visible in yours HWMonitorSMC2 app and IOReg.
  2. Avoid to use it! It has critical misunderstandings about how APTIO works. According to the description on Asus web-site, it has Meltdown/Spectre fix only.
  3. Does anybody know a link to 10.13.4 RecoveryHD.pkg for iMacPro?
  4. Hmm... strictly speaking this is not a KP, but boot.efi got stuck for some reason. OK, so far I'm out of ideas, sorry.
  5. Try to drop this table and remove fake cpuid. You don't need any cpu tables for HWP enabled mode. If there is a KP, capture it by your phone or any other camera.
  6. Could you please also provide original ACPI tables? Press F4 when Clover bootloader in on your screen. Then find the tables in Clover/ACPI/origin folder. I've got an idea how to get rid of FakeCPUID for you. If the forum doesn't allow you to attach it, please use any file share service like MediaFire or Dropbox.
  7. This is really weird. I suspect that the patches.txt file you use either incomplete or invalid. Indeed, try to contact ASUS support and ask them to provide firmware with unlocked 0xE2.
  8. Thanks for pointing this! Unfortunately, I used my hardcopy motherboard manual and it doesn't contain this information.
  9. When you contact ASUS please ask them to provide such fixes not only for Prime Deluxe motherboard, but for all their LGA2066-based motherboards. Thanks.
  10. @obus, I also still don't get why you need FakeCPUID. Your Xeon has the CPUID exactly the same as my Core i9 has, and I never used FakeCPUID. Could you please attach your current EFI folder?
  11. The first thing you need to know is what name the file with bios firmware should have, since the file name is always special to motherboard. If you just put the file with firmware as it is - it won't be flashed. And "BIOS Flashback" is the only way to write modified firmware into you bios chip. Also please note that I'm not responsible for any damage/data loss/whatever. You do it all on your own risk. So you need to do: Contact ASUS support and ask them about firmware file name to use with BIOS Flashback. Or try to find it by yourself, but as for me, I wans't succesful and asked ASUS support. Download the latest firmware for your motherboard. Use latest UEFIPatch with patches.txt from KGP's guide to patch your firmware. These patches unlock MSR 0xE2 and disable writes to TSR, so you won't need Pike's patch and TSCAdjust. Grab a USB flash drive which should not be larger than 8 GB. Format it to FAT32 and put a file with patched firmware to flash drive root. Make sure it has the proper name from p.1. I'd also suggest to prepare two flash drives where the second should contain unmodified firmware in order to be able to restore the original firmware if something goes wrong. Shut down your rig. Plug the flash drive from p.4 with patched firmware into a special BIOS Flashback USB slot. Refer to your motherboard manual to find it out. DO NOT POWER UP you rig. Press and hold BIOS Flashback button until a blue LED starts flashing. Wait until the LED goes off (3-5 min). Unplug your rig from wall and wait for 1 min. Then open your rig case and press 'CLR_CMOS' button on your motherboard. Refer to your motherboard manual to find out the button and clear bios settings. Power on your rig and you are done. I don't think you actually have this installed.
  12. @yapan4, if so, could it be solved with FakeID for LAN set to 1533? Or 'legacy' kext which we usually did for USB? I'd not recommend to make changes to anything in /S/L/E unless there are no other possible solutions exist.
  13. @yapan4, his Intel I210 Ethernet controller should work out-of-the-box using native support by vanilla AppleIntelI210Ethernet.kext If it does not, then it's weird. My board has the same controller and it works fine without any effort.
  14. That's weird. Please drop me your EFI folder you have after you did this.
×