Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


Local Moderators
  • Content count

  • Joined

  • Last visited

  • Days Won


Slice last won the day on January 17

Slice had the most liked content!

1 Follower

Profile Information

  • Gender
  • Location

Recent Profile Visitors

48,378 profile views
  1. HWSensors3

    But the package does not contain HWMonitor2
  2. HWSensors3

    I cam compile. It fine! iMac-2:hwsensors3 slice$ make pkg ** Building HWSensor's extensions r112 ** ..using the sdk: macosx10.11 ** Building HWMonitorSMC.app v1 ** ** Building HWMonitorSMC.app v2 ** ** Building HWSensors-3_r112.pkg ** [partutil] [seticon] [Pre] [HWMonitorSMC] [kextsToSLE] [FakeSMC] [IntelCPUMonitor] [AmdCPUMonitor] [GeforceSensor] [NVClockX] [RadeonMonitor] [X3100] [F718x] [ITEIT87x] [PC8739x] [W836x] [ACPIMonitor] [VoodooBatterySMC] [kextsToESP] [Post] Package name: HWSensors-3_r112.pkg iMac-2:hwsensors3 slice$
  3. HWSensors3

    I tested HWMonitor2 on MacBookPro 2012 with Apple SSD 128Gb. All works except SSD life = 0%. It means dead?
  4. HWSensors3

    I have python installed with macport needed for another projects iMac-2:hwsensors3 slice$ which python /opt/local/bin/python iMac-2:hwsensors3 slice$ Python 2.7.13 (default, Apr 25 2017, 11:00:18) And Xcode 9.2, although I have also Xcode8.3.3 on second partition.
  5. HWSensors3

    @vector sigma My compilation log ended with Traceback (most recent call last): File "/Volumes/HighHD/Users/Slice/Projects/hwsensors3/package/seticon.py", line 2, in <module> import Cocoa ImportError: No module named Cocoa The package is created but with HWMonitor v1. Why not v2?
  6. HWSensors3

    But it is HWSensors3:RadeonMonitor who has support for all new Radeons. Not kozlek.
  7. SLIC.aml is not being inserted

    Works for BIOS only as well.
  8. SLIC.aml is not being inserted

    Should work. It is very simple procedure and it's tested. I don't know where there may be a mistake.
  9. SLIC.aml is not being inserted

    You have to drop old SLIC.
  10. HWSensors3

    This is open-source project if ((vendor_id==0x1002) && (class_id == 0x030000)) { InfoLog("found Radeon chip id=%x ", (unsigned int)device_id); VCard = device; ret = 1; //TODO - count a number of cards break; }
  11. Update or not to update Clover...

    New package contains updated AptioMemoryFix which prevents OS crashes is some rare cases. There may be your case. About Clover revisions you may see what was changed in the history https://sourceforge.net/p/cloverefiboot/code/4415/log/?path= There are changes in package, in build rules, in hibernation, in private data - nothing significant.
  12. Clover General discussion

    This is version of the specification [Defines] INF_VERSION = 0x00010005 BASE_NAME = AtaAtapiPassThruDxe MODULE_UNI_FILE = AtaAtapiPassThruDxe.uni FILE_GUID = 5E523CB4-D397-4986-87BD-A6DD8B22F455 MODULE_TYPE = UEFI_DRIVER VERSION_STRING = 1.0 ENTRY_POINT = InitializeAtaAtapiPassThru
  13. HWSensors3

    Already done.
  14. FileVault 2

    Press F10 and show us what clover is not showing. As well preboot.log is very informative file. To get it press F2.
  15. Clover General discussion

    They have no version string. There are only two versions new and bad. If you somehow want to keep old drivers then you may copy drivers64UEFi folder to drivers64UEFI_rev4415 and keep it proposing all newer version will be wrong. It is not true.