mirror of
https://github.com/hirschmann/nbfc.git
synced 2026-04-27 01:25:59 +03:00
[GH-ISSUE #628] Can control only 1 fan out of 2 on Acer aspire VN7 592G #562
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#562
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 @feresberbeche on GitHub (Jan 28, 2019).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/628
Describe the bug
Can't read the value or change the speed of one of the fans on the Acer Aspire VN7-591G V15 Nitro BE using preloaded config. the other fan works perfectly (read and write)
To Reproduce
Open NBFC, select VN7-591G V15 Nitro BE
Expected behavior
Read the fan speed and control it
System information
Acer Aspire VN7-591G
time;level;message;exception;callsite;stacktrace 2019-01-21 02:01:47.9934;Info;App start;;NbfcClient.App..ctor;App.Main => App..ctor 2019-01-21 02:46:08.6978;Info;App exit;;System.Windows.ExitEventHandler.Invoke;Dispatcher.LegacyInvokeImpl => ExceptionWrapper.TryCatchWhen => ExceptionWrapper.InternalRealCall => HwndSubclass.DispatcherCallbackOperation => HwndWrapper.WndProc => Dispatcher.WndProcHook => Dispatcher.ProcessQueue => DispatcherOperation.Invoke => CulturePreservingExecutionContext.Run => ExecutionContext.Run => ExecutionContext.Run => ExecutionContext.RunInternal => DispatcherOperation.InvokeImpl => ExceptionWrapper.TryCatchWhen => ExceptionWrapper.InternalRealCall => Application.ShutdownCallback => Application.ShutdownImpl => Application.DoShutdown => Application.OnExit => ExitEventHandler.Invoke 2019-01-22 00:39:06.2483;Info;App start;;NbfcClient.App..ctor;App.Main => App..ctor 2019-01-22 01:56:12.2263;Info;App start;;NbfcClient.App..ctor;App.Main => App..ctor 2019-01-22 01:56:25.3385;Info;App exit;;System.Windows.ExitEventHandler.Invoke;Dispatcher.LegacyInvokeImpl => ExceptionWrapper.TryCatchWhen => ExceptionWrapper.InternalRealCall => HwndSubclass.DispatcherCallbackOperation => HwndWrapper.WndProc => Dispatcher.WndProcHook => Dispatcher.ProcessQueue => DispatcherOperation.Invoke => CulturePreservingExecutionContext.Run => ExecutionContext.Run => ExecutionContext.Run => ExecutionContext.RunInternal => DispatcherOperation.InvokeImpl => ExceptionWrapper.TryCatchWhen => ExceptionWrapper.InternalRealCall => Application.ShutdownCallback => Application.ShutdownImpl => Application.DoShutdown => Application.OnExit => ExitEventHandler.InvokeAdditional context
Both of the fans used to work before with that exact configuration, I have updated windows and the gpu drivers, maybe they have some influence.
@github-actions[bot] commented on GitHub (Nov 19, 2019):
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
@feresberbeche commented on GitHub (Nov 19, 2019):
yes it's not a software problem, I checked the fan that was not turning and I tried manually turning the blades using a pin I stuck between the openings and something came out I think that what stopping the from turning