Jump to content

mumak

Members
  • Posts

    23
  • Joined

  • Days Won

    1

Posts posted by mumak

  1. 36 minutes ago, pip_jones said:

    Hi, thanks for getting back to me.

    Upgrade done, still only 2 of 3 fans visible.

    Any ideas? 

     

    Dumps as requested.

     

    GPU

    ............

    Could you please provide 2 more SMBus dumps at different 3rd fan speeds and note what was the fan speed (%) at the time you created each of them? That should help to figure out how the 3rd fan can be read.

  2. Some older HP Envy series (based on Quanta ODM design) used to have fan speed at EC [0xB2-0xB3], [0xD2-0xD3] (FAN_FEEDLo / FAN_FEEDHi).

    Not sure if that might apply here, but it's rather unlikely as the above models were notebooks using ENE ECs.

    An Embedded Controller dump (with known high and low fan speeds) might shed some light... And maybe a DSDT dump too...

  3. It still might be a B3 chipset. There's a feature in Intel chipsets called Chipset Compatibility Revision ID. If this feature is activated by the BIOS, then the chipset reports a Compatible Revision ID (which is not the true hardware revision of the chip). On the 6-series chipsets this would cause all the identifiers on a B3 chipset to report a B2 value !

    Unfortunately in this case there is NO UNIVERSAL WAY how to determine the true Hardware Revision ID - the only possible method would be if the BIOS saves the original ID in some register, then activates this feature and offers the reading of this ID to its own tools (which might be the case of the Acer tool). When this issue came out some vendors have released BIOS updates which obviously do not enable this feature anymore and so allow a proper reading of the ID - the result was that machines with a B3 chipset have been reporting B2 in all tools unless the user performed such BIOS update.

  4. The question is whether they would be willing to release that info. If yes, an NDA would solve the confidentiality concern. It might be worth a try..

    Yes Fiery is right,we try before to implement in proper way with Everest (many posts on Lavalys forum is gone),even I personaly ask my friends in GB Taiwan to give code for DES,but unsuccessfully (confidential documents).

  5. Yeah, of course, I forgot this litte detail :(

    Other tools include AIDA64, of course :) But that feature generally requires a platform that supports such readout, and AFAIK LGA1366 platforms do not support that due to lack of hardware implementation in ICH10 south bridge.

  6. HWMonitor doesn't really monitor CPU Power Consumption, it just reports a rough estimatation basen on current P-State (voltage) and maximum TDP/TDC. And that's the reason it doesn't report the power consumption here, because this SKU doesn't specify max TDP/TDC (it's unlimited).

    There are other tools able to really monitor CPU power consumption on Nehalem and later CPUs based on Energy Counters (independant on Max TDP/TDC values, but requires platform enabling in PCH/BIOS).

×
×
  • Create New...