Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump to LibreHardwareMonitor 0.9.3 #433

Merged
merged 3 commits into from
Jan 29, 2024
Merged

Bump to LibreHardwareMonitor 0.9.3 #433

merged 3 commits into from
Jan 29, 2024

Conversation

nickbabcock
Copy link
Owner

@nickbabcock nickbabcock commented Jan 2, 2024

There's a breaking change in LHW with the introduction of the index of superIO identifier:

Before:

/lpc/nct6792d/control/0 "Fan #1"

After:

/lpc/nct6792d/0/control/0 "Fan #1"

I'm open to discussion on what the right course of action should be:

  1. Preserve the breaking change and just note it in the changelog
  2. Introduce logic to keep the same sensor IDs (but what to do with new users with systems that eventually see the motherboard hardware split in two, which would experience duplicate sensor IDs or a breaking change in IDs if we only introduced indices if multiple exist).
  3. Introduce a config in OhmGraphite so the user can choose between 1 and 2 (and default to 2)

Option "2" was chosen as it allows us to punt the decision down the road in a "wait and see" scenario.

Another user visible change is that there is a new metric for storage metrics: "Read Activity" which is analogous to the already present Total and Write Activity sensors but for reading.

  • Add read activity to storage
  • Add support for MSI MPG X570 GAMING PLUS (MS-7C37)
  • Add support for ASUS ROG STRIX X670E-F GAMING WIFI
  • Add support Asus ROG MAXIMUS XI FORMULA

There's a breaking change in LHW with the [introduction of the index of superIO identifier][0]:

Before:

```
/lpc/nct6792d/control/0 "Fan #1"
```

After:

```
/lpc/nct6792d/0/control/0 "Fan #1"
```

I'm open to discussion on what the right course of action should be:

1. Preserve the breaking change and just note it in the changelog
2. Introduce logic to keep the same sensor IDs (but what to do with new
   users with systems that eventually see the motherboard hardware split
   in two, which would experience duplicate sensor IDs or a breaking
   change in IDs if we only introduced indices if multiple exist).
3. Introduce a config in OhmGraphite so the user can choose between 1
   and 2 (and default to 2)

Another use visible change is that there is a new metric for storage
metrics: "Read Activity" which is analogous to the already present
Total and Write Activity sensors but for reading.

[0]: LibreHardwareMonitor/LibreHardwareMonitor#1183
@nickbabcock nickbabcock marked this pull request as ready for review January 28, 2024 21:18
@nickbabcock nickbabcock merged commit dda9fc5 into master Jan 29, 2024
3 checks passed
@nickbabcock nickbabcock deleted the bump-libre branch January 29, 2024 12:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant