Jump to content

vector sigma

Developers
  • Content Count

    1,678
  • Joined

  • Last visited

  • Days Won

    56

vector sigma last won the day on February 12

vector sigma had the most liked content!

2 Followers

About vector sigma

  • Rank
    InsanelyMac Deity

Profile Information

  • Gender
    Male

Recent Profile Visitors

4,006 profile views
  1. vector sigma

    Clover.app testing

    I think I can
  2. vector sigma

    Clover.app testing

    please retry to redownload it... but before opening it try with: sudo spctl --master-disable let me know
  3. vector sigma

    Clover.app testing

    Thanks!
  4. vector sigma

    HWSensors3

    Thanks to had taken the time to ensure fans connectors are right. The file is identical on what it's already on Github..
  5. vector sigma

    Clover.app testing

    Not sure why this always happens to Slice while mine it's ok. I'll ensure (in buildme) zip is the Apple one by hard coding its path. Wait. Resource forks are added when the file is not on a hfs/apfs volume . May be Slice has Clover in to a DOS partition??
  6. vector sigma

    HWSensors3

    As a magician I can compare fans with this: as the default.plist comes from ...but if @MacNB want ensure it..
  7. vector sigma

    HWSensors3

    done .. I'm a fortune teller
  8. vector sigma

    HWSensors3

    No it should display: Z77X-UP5-TH, ITE IT8728F instead of Main Logic Board, ITE IT8728F We are OT for this here, but only recently OpenCore added OEM informations. Clover has this for a long time. Otherwise the app doesn't know that has to read the Z77X-UP5-TH.plist
  9. vector sigma

    HWSensors3

    You have to take the max limit otherwise the risk is to not show fans because FANINLIMIT is not the number of the fans you have, but the number of the fans the LPC chip can handle. If some of it doesn't show up is because has an incredible value. Create a file to your desktop: touch ~/Desktop/HWBadSensors and restart the app. The formula is: valueFromChip + ((valueFromChip - VRef) * Ri) / Rf no need to say that Rf must not be 0. All the values are integers because kexts can read only integers from a plist so the the calculation should be: valueFromChip = 0,504 volts (assuming this is the +5V) VRef = 0 Ri = 10 Rf = 1 valueFromChip + ((valueFromChip - VRef) * Ri) / Rf = 5,04 Volts You have to ask to the Motherboard vendor, or compare with other software in Windows. 3. Create firstly an empty dictionary with the motherboard name (exactly) to see raw values reported by the chip, and start modifying VRef, Ri and Rf. 4. nothing, different projects, it's for Lilu/VirtualSMC plugins (so not for FakeSMC plugins). Anyway it is just the same, "multi" is a multiplier that already take into account the above formula.
  10. vector sigma

    HWSensors3

    I think you should trust more Intel who made the software and your CPU, you don't think? What make you think "architectural cores" (logical part) are not physical? The difference is that each one of them (in pairs) share the processor execution resource part. All that to say that Intel apparently put sensors on each logical core, which is expected for a correct measurement.... and the library just read them. Here there is a distinguish. IntelPowerGadget.framework 3.7.0 carries 3 headers, first two are marked as deprecated (the framework print a clear message about this), the third one (which I using) was introduced this or last month, the newer iStat is from October 19... Care to update your bootloader as is not showing the motherboard name? Say that because without OEM informations the configuration will not be automatically detected.
  11. vector sigma

    HWSensors3

    Hi, I had pinned it somewhere, but then I forgot about it. Did you figure it out?
  12. vector sigma

    VirtualSMC — SMC Emulator

    if you turn off the power saving mode in your BIOS (C1E/EIST), if that is the case, you should see this value going to the max.
  13. vector sigma

    VirtualSMC — SMC Emulator

    Vcore is the limit of the voltage the CPU can use while the VID is the voltage the CPU uses at any particular moment depending by its frequency range. The CPU communicate the VID to the VRM (Voltage Regulator Module) which send the correct Vcore to use. (large use of google ) VID --> VRM --> Vcore Basically VID is it a request, VRM allow or disallow and regulate the request, and Vcore is the final the CPU uses.
  14. vector sigma

    HWSensors3

    One interesting thing, Hyper-Threading: some part of the core are duplicated, not entirely, but it physically doubles the cores which runs at different frequency and different temperatures. Hyper-threading works by duplicating certain sections of the processor—those that store the architectural state—but not duplicating the main execution resources. This allows a hyper-threading processor to appear as two "logical" processors to the host operating system, If i increase by one the core count manually it show 0 for both frequency and temperature of the fake core I added... all this is correct because that means that there are also sensors that monitoring all this for true. Conclusion: HWMonitorSMC2 and Intel Power Gadget are right, iStat is wrong (or incomplete, maybe read SMC keys).
  15. vector sigma

    HWSensors3

    this is the function that returns the core count in Intel Power Gadget: /*@function PG_GetNumCores * @abstract Gets the number of CPU cores on the specified package. * @param iPackage Index of Intel processor package to query. Must be less than the value from PG_GetNumPackages. * @param numCores Pointer that will be updated with the number of CPU cores on this system. * @result True on success, false on failure. */ bool PG_GetNumCores(int iPackage, int* numCores); ..and there is no mention that numCores must divided by two, so I guess it is at least a bug in Intel Power Gadget (see next post). Don't be surprised, HWMonitorSMC2.app uses the latest availabe library while I have doubt iStat already implemented this, otherwise will have the same readings. This depend by developers. In the first place you have something wrong because the motherboard name didn't show up. So the LPC configuration (assuming one for your motherboard exists) is not applied. iStat decide that Fans reporting 0 rpm are invalid and not shown (this should depend if PWM can turn off the fans otherwise they must be display even with 0 RPM, I guess). In HWMonitorSMC2 this is configurable, as well for the fan/voltages name.
×