mirror of
https://github.com/hirschmann/nbfc.git
synced 2026-04-26 00:56:01 +03:00
[GH-ISSUE #1194] Config for Lenovo Ideapad Slim 3i #1023
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#1023
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 @Str4u55 on GitHub (Oct 29, 2021).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/1194
Can someone please add fan config for Ideapad Slim 3i? will be much appreciated.
@dumprop commented on GitHub (Nov 5, 2021):
Check out my config for Lenovo Yoga Slim7 https://github.com/UraniumDonut/nbfc-revive/pull/59
But I'm not sure that it compatible with Lenovo Ideapad Slim 3i
It's impossible create config without probing
@Str4u55 commented on GitHub (Nov 5, 2021):
Thank you very much for your reply. greatly appreciate it.
I've tried your config, but yet nbfc still unable to read the fan EC.
I know that you need probing first before creating the config, but i don't understand the instructions. If only there's someone who wants to create the tutorials in YouTube, maybe i can follow it.
But once again, thank you for your response..
@dumprop commented on GitHub (Nov 5, 2021):
I prefer that way: dump register with disabled fan, enabled slow speed and enabled high speed
For these purposes I use any benchmark tool (geek bench), it loads cpu (fan) very fast
And then diff them
Also you can try to provide these files for possible config generation (personally I created with one attempt, but I had near 10 samples of various states)
@github-actions[bot] commented on GitHub (May 6, 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