Skip to content

Fix I801 resource lookup affecting memory temperature reads - #13

Open
chenx-dust wants to merge 1 commit into
Blacktempel:masterfrom
chenx-dust:fix/i801-controller-device-id
Open

chenx-dust wants to merge 1 commit into
Blacktempel:masterfrom
chenx-dust:fix/i801-controller-device-id

Conversation

@chenx-dust

@chenx-dust chenx-dust commented Sep 28, 2026 •

Copy link
Copy Markdown

This change addresses a memory temperature reading issue on my current machine when using the WMI-based I801 SMBus detection path.

Inside the controller enumeration loop, the resource lookup uses pnpSignedDriver[0]["DeviceID"] instead of the current controller's DeviceID. If the current Intel controller is not the first WMI result, this can select an unrelated I/O range or unnecessarily fall back to the fixed address, affecting subsequent memory temperature reads.

Use item["DeviceID"] so the resource lookup matches the controller passed to TryAddSMBus.

Assisted by GPT 6 Astra

@chenx-dust chenx-dust changed the title Use current controller DeviceID for I801 resource lookup Fix I801 resource lookup affecting memory temperature reads Sep 28, 2026
@Blacktempel

Copy link
Copy Markdown
Owner

Thank you for your PR.
Due to many upcoming changes all non-critical PRs for this repository will currently be put on hold.
Your change will be reviewed and considered for a patch version, when possible.

Note: the suggested change is for legacy support of an old unsafe driver.
If possible, please do not use WinRing0 anymore.

@Blacktempel Blacktempel added the on hold Waiting for something (e.g. user reply) label Sep 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

on hold Waiting for something (e.g. user reply)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants