Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11334

  • Joined

  • Last visited

  • Days Won

    476

 Content Type 

Everything posted by Fiery

  1. Fiery
    Yes, that could happen when the polarity of charge rate reporting is reversed in the Android platform. We need to implement a workaround for each those devices -- very time consuming task But, if you can send a report of your Android devices from the About page, we can do it of course
  2. Fiery
    It's not supported yet. We've just ordered a unit, and we'll implement support for the Commander Pro protocol as soon as it arrives. I'll let you know in this topic once a new AIDA64 beta -- with the protocol implemented -- becomes available for download. It shouldn't take more than 2 weeks approx.
  3. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery
  4. Fiery
    I know The problem with such approach is that AIDA64 supports over 50 LCD protocols, and it's not the best idea to cherry-pick from them. And we don't want to implement 100 more separate hot-key options either, to cover enabling+disabling the 50 different LCD protocols
  5. Fiery
    ULPS has little to do with the current sleep or awake state of a certain GPU. Even when ULPS is enabled, and AIDA64 wakes the GPUs, it will still not query the non-primary GPU (or GPUs) for video BIOS readout. And that's because ULPS is very agressive: it can put the non-primary GPU to sleep anytime, even half-way reading the flash BIOS for example. And when that happens, a system lockup is likely to happen AIDA64 detects the marked information using ADL (AMD proprietary API) calls. http://developer.amd.com/display-library-adl-sdk/
  6. Fiery
    What motherboard do you have? Can you see the MESH voltage in the BIOS Setup among the other measured voltage readings? (e.g. PC Health Status or H/W Monitor page in the BIOS Setup)
  7. Fiery
    Thank you for the dump. Yes, we'll add it, but first, we need to find a way to detect the presence of the iCX MCU. So far we haven't found a reliable way of doing that, but we keep looking for a proper solution. Please give us a few more days to investigate this.
  8. Fiery
    Those are quite specific requests. #3 is the easiest one to implement, but it would have to come as an optional feature that you can toggle with a checkbox (in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / Crystalfontz). Separate sliders for LCD brightness and keypad brightness may come second. But the rest are deep customizations that may come useless to most users of AIDA64. We'll have to think about them. As for EVGA iCX, we'll soon implement those readings
  9. Fiery
    Disabling would be possible, but enabling it is not possible, since there's no single switch to enable "all LCD" modules. Disabling all LCD modules is easy, since usually you have only one enabled (in your case, Razer). But it would be quite overkill and risky to implement a global "enable all LCD" modules, due to the complexity and diversity of various LCD protocols...
  10. Fiery
    It's not possible to do that with AIDA64.
  11. Fiery
    2) AIDA64 saves a separate .ROM file for all GPUs in the system, as long as those GPUs support flash BIOS readout, and ULPS doesn't stand between AIDA64 and the flash BIOSes When no flash BIOS readout is possible, it will revert back to the classic video BIOS region dumping (into a .DMP file) 4) I suppose in this particular case ULPS may be the issue. IMHO there's no need to select the GPU, since AIDA64 would try to save all BIOSes for all GPUs, whenever it's possible. And when it's not possible, by selecting the GPU you wouldn't get the .ROM file anyway either.
  12. Fiery
    Due to an internal mistake, we almost posted incorrect benchmark results with the latest stable update (AIDA64 v5.92). Since discovering that came the last minute, the only thing we could do to avoid publishing inaccurate reference scores is to remove that line from the list. Sadly, we had no time to perform the benchmarks again. We'll do that soon and add Ryzen 7 1800X results in an upcoming beta build.
  13. Fiery
    Do you have RGB LED support enabled in AIDA64 / main menu / File / Preferences / Hardware Monitoring / RGB LED, or Razer LCD support enabled in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / Razer?
  14. Fiery
    1) The video BIOS dump is not an official feature of AIDA64. It's only a debug tool that we use to aid hunting and fixing bugs. 2) The video BIOS dump feature is supposed to enumerate all available GPUs. Whenever it can find a GPU with flash BIOS readout, it will save the flash BIOS content into a .ROM file. It may or may not work with multi-GPU systems as well as with mixed graphics systems though. Whenever the flash BIOS cannot be accessed, AIDA64 tries to read the classic video BIOS region (at C0000h memory address) and saves it to a .DMP file. 3) Saving flash BIOS for non-primary GPUs is disabled when ULPS is active. 4) Saving flash BIOS for chipset integrated GPUs is not possible, since their flash image is not available for 3rd party applications via classic GPU flash BIOS interrogation.
  15. Fiery
    It's normal, and it's because GDDR5 memory uses QDR (Quad Data Rate) architecture. So your video RAM is actually running at 2502 MHz, but its effective clock frequency is 4 times that, 10008 MHz. https://en.wikipedia.org/wiki/Quad_data_rate https://en.wikipedia.org/wiki/GDDR5_SDRAM
  16. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery
  17. Fiery
    It would definitely require either: 1) You develop a firmware/program for your microcontroller to suit one of the existing external LCD display protocols that AIDA64 supports. For example, you can choose the Pertelian or Matrix Orbital protocol. They're both widely used in 3rd party displays. One advantage of this path is that for test runs you can use either AIDA64 or LCD Smartie while you develop your protocol, and you don't necesserily need any input from us, neither you need to wait for us to alter AIDA64 to make sure it works with your display. 2) We (you + us) come up with a proprietary protocol, one that is the most suitable for your display. However, in order to do this, we may need to develop a device emulator or have a sample of the final version of the hardware that you're developing. This one is a much more difficult solution, since it requires a lot of efforts on both ends (you + us).
  18. Fiery
    Thank you for your feedback. I've sent you an email.
  19. Fiery
    Yes, but first we need to find out whether the register readout works on your video cards. Both of you, please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery
  20. Fiery
    Please submit a report from the About page of our app, and we'll take a look at it. You can also contact us directly in email in case you have a technical question about our app
  21. Fiery
    Thank you! In order to have a reference set of readings with 100% accuracy, can you please also post a screen shot of Gigabyte's own monitoring utility of the UEFI Setup (BIOS Setup) where the temperature, voltage and fan RPM values are shown?
  22. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  23. Fiery
    The mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works
  24. Fiery
    The mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works
  25. Fiery
    I'm sorry for the delays. Here it is: https://www.aida64.com/downloads/latesta64xebeta
×
×
  • Create New...