Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

  • Days Won


TpwUK last won the day on June 1 2017

TpwUK had the most liked content!


About TpwUK

  • Rank
    Junior Member
  • Birthday 10/14/1964

Contact Methods

  • Jabber

Profile Information

  • Location:
    United Kingdom
  • Gender
  • Interests
    3D Modelling and Rendering, Garden Design, Reading and Cooking

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Are you using ATi/AMD Radeon R7 or R9, if so you need the Intel Graphics enabled, but you wont need a screen attached to it. Sadly though the last version of OSX that supported Radeons was Yosemite, so your mileage may vary. Martin
  2. If your using Clover Boot, there is an option in the Boot Args section for -xcpm, click that for it to be added at boot. Under Kernel there is KernelPM. If you are not using a CPU officially supported by Apple then you will need to add the option forces the kernel to recognise the CPU. You might also need to create a custom SSDT using ssdtPRGen script. Martin
  3. Excellent moderator who know how to explain with proper details. More moderators like this pls. 

  4. As far as i am aware you will not get full power management with Sierra and IvyBridge v2 Xeons. Kernel based power management for those CPU's was purely experimental with El-Capitan and has been officially withdrawn with Sierra, so if you want full power management you will need to roll back to 10.11.x then you can use -xcpm and kernel PM with your Xeon v2 CPU Martin
  5. Which OS version are you trying with ? Are you using Clover ? Martin
  6. I had issues with it too on my old IvyBridge build ... see if this kext helps ... I am not certain the kext will work with Sierra. To get power management working i had to use -xcpm boot argument with Clover EFI boot. Martin HackPlatformPlugin.kext.zip
  7. It's not drastically serious but it's serious enough to warrant concern. Test your builds serial number with Apples coverage web page. If that says it is an unrecognised serial you need to change it. You need that web page to show that the coverage has expired, then you know you have a good serial. If you see a result that shows it's covered by Apple, then you need another serial otherwise you will be competing for logins with the true serial owner, only uncovered serials are good. If you need to rebuild from scratch then you also need to remove any EFI partitions on your non removable drives as Apple now seems to make backups to non booting drives but uses them to compare settings. I use Linux to remove those extra EFI partitions that using GUID partitioning creates. You will also need to clear your UEFI Bios Settings. If you can't delete them via the BIOS on your motherboard then you will need to downflash your BIOS to an older version, then flash back up to the latest one. The smBIOS and serial used to install now has to be copied to your boot drive from your USB installation stick, you can not create a new one as you used to be able to! If you get a partially blocked AppleID such as myself, it's no biggie if you have true Apple products, you can still use those to do your Syncing, I can still login to my AppleID, iCloud etc, but i can't use FaceTime or Messenger. I can not backup my iPhone to my now deleted Hackintosh build, and it would only do updates to the OS. No AppStore login, and no access to my legitimate AppStore purchases so no updates for those either. For these reasons I flattened my workstation and have now installed Windows 10 pro on it. I used to use the smBIOS settings from my dead MacPro3,1 the only thing i couldn't change was the networks MAC addresses and that seems to have been enough to block that computer for AppStore access. It's my own fault, I built this workstation and tried several smBIOS versions for iMac 14,1.. 17,1 along with MacPro 3,5 and 6, all of which would no longer work after 10.12.2 updates to what was by then running as a MP5,1, so i reverted back to my 3,1 specs and dropped to 10.11.6 and then that's when i discovered it was partially blocked. I phoned Apple support and came clean that i was using a Hackintosh because their current 6,1 was not powerful enough and was too expensive for the performance level it has. I explained that I have two other Apple computers and an iPhone that i need to use with my AppleID and they said that "they should still work and have full access to all Apple Services" and indeed they do. However the iPhone no longer shows as a device when connecting to any of my computers so something has been effected there too. I test software for companies and this is a major area of concern for me now and depending on what the new 2018 Mac Pro will deliver on bang for buck has to be seen before i decide if i will retire all my Apple products and shift to Android and Windows, and trust me, i hate Windows with a passion. The simple answer is to not keep using the same PC as a Hackintosh platform, get it right and working to your satisfaction with zero online access until you are sure it's good to go, then and only then activate your AppleID with it, but then, don't be surprised if it gets blocked because of having no legitimate Apple MAC Address for your network interface. Martin
  8. With my partially blocked appleID i can not make purchases or get access to the Apple App Store any more from my Hackintosh, so i now have to download my apps using a real Apple and network them over... It's OK to use the same computer as long as you keep using the same smBIOS and run-time variable details across each build, but if you experiment to see which is best for your machine then you are better off not signing in at all with your ID. I am not sure how strict they have gotten on mac addresses either, if more people start seeing that message it can only be two things. They have recorded and blocked you mac address, or they are blanket blocking since all Apple products i have ever used have mac addresses that start with 00:. The latter would not be wise as there are plenty of Apple servers out there using NIC's so then the smBIOS would have to come into play too to decide if you are a true Apple computer. Once you're happy and certain you have a stable build and you're going to stick with it then start using your AppleID. Make sure to pick as close as you can get to a real mac serial number. If using clover or chameleon generated ones, check it on everymac for validity and then check the serial with apples coverage website. You can have 5 goes per day. If it says the number is invalid it is, so create a new one. If it shows as having active coverage, then generate another number. Martin
  9. You can set this in system preferences but be warned, if you are using your main apple-ID and have used your machine with several builds and different smbios versions Apple are getting more strict and are blocking by network mac addresses now. It is also much harder to get your iPhone to interact with your non apple products too. Martin
  10. Look into the settings of the -Debug boot argument ... Also Sierra from 12.3 requires that all kexts be injected (at least when booting with uefi mode) Martin
  11. Reading the rehabman git tells you where to download from ... https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek/downloads/ It should come with all the sensor kexts and then you need HWinfo.app I think it was called to display the results. If using Clover copy the unpacked kexts to Clover/kexts/other Martin
  12. If you are booting with Clover have you tried setting the GUI section to a specific resolution ? From my understanding OS X uses VESA tables for the installation process, whatever you set in Clover is supposed to carry over on to the installer. If nothing has been set at boot then the installer will go for max resolution and will centre the install screen and not scale it to suit your actual resolution. Martin
  13. HWSensors kexts that you can get from the FakeSMC github https://github.com/kozlek/HWSensors or from rehabman's branch here https://github.com/RehabMan/OS-X-FakeSMC-kozlek Martin
  14. I could never get Sandy Bridge CPU's to work so can't offer any help there. NullCPUPM will disable speed stepping. You will need to enable the Asus Power Management fix in Clover along with KernelPM and KernelCPU recognition, you might need AppleRTC fixing too Boot arguments should be -v npci=0x2000 xcpm_ipi SMBIOS to use either iMac14,2 will get the graphics working with no patching needed SMBIOS MacPro6,1 will need an SSDT for the 660ti but it was for use with El-Cap and not Sierra so might no longer work Do not use Clover Configurator's Use Nvidia Web Drivers it's broken (or was the last time I used it) use Clovers boot Options/Graphics section to set the Use Web Drivers but only after you have installed them. So you are right to boot with NV_Disable=1 (depending on your smbios) it will be slow because it's using VESA mode, but it will enable you to download and install the Nvidia web drivers. Please note the iMac14,2 requires no web drivers to get full function of the 660ti Martin
  15. There are a number of hardware differences between the CPU capabilities that could cause issues. I recommend a fresh new install. Martin
  • 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.