mirror of
https://github.com/hirschmann/nbfc.git
synced 2026-04-26 00:56:01 +03:00
[GH-ISSUE #1180] ec-probe.exe dump and RWEverything show all EC values in 00 #1006
Labels
No labels
Stale
bug
config
discussion
duplicate
enhancement
experimental
feature
help-wanted
info
invalid
invalid
pull-request
question
up-for-grabs
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nbfc-hirschmann#1006
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JuanMiguelPR on GitHub (Sep 18, 2021).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/1180
Hi! I have been trying to create a config file for my Asus UX534FT, but have had trouble since the begining.
I opened my laptop and could not find the EC anywhere, looked for the models of the chips I saw, but none of them where the EC.
I proceeded then to try the DSDT editor, but got the error Could not parse ACPI tables, AE_ALREADY_EXISTS.
With RWEverything I'm able to get the DSDT, but then comes the strange part for me: When I run ec-probe.exe dump or use RWEverything to see the EC values, all result in 00 and when trying to use the monitor feature of ec-probe I don't recieve any result and I'm also not able to save a report text file.
Resulting in being unable to get any clues of the registers controlling the fans speeds, even though I have a way of making them spin by loading the cpu of gpu.
Any help or idea of what can be wrong?
Thanks!
@cRoCx commented on GitHub (Nov 21, 2021):
I encounter the same problem with my Asus ZenBook Duo 14 UX482.
This issue is a duplicate of #1034 btw.
@github-actions[bot] commented on GitHub (May 22, 2022):
This issue is stale because it has been open more than 180 days with no activity. If nobody comments within 7 days, this issue will be closed
@cRoCx commented on GitHub (May 22, 2022):
Similar issues occur also in the NBFC Revive project (https://github.com/UraniumDonut/nbfc-revive/) here: https://github.com/UraniumDonut/nbfc-revive/issues/72 and here https://github.com/UraniumDonut/nbfc-revive/issues/46 .