You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
APC model BVK750M2 false indications of LB/RB #2942
Currently have an APC model BVK750M2 purchased earlier this year connected to TrueNAS Core 13.3 (FreeBSD 13.3-RELEASE-P4) and from reading, it appears to be the same issue as #2347 and was addressed in PR #2565 but unfortunately it didn't cover my model #.
I'm going to tweak the usbhid-ups.c on my end and rebuild to see if the fix will work (likely) and then I should create a new PR I suppose?
Also probably review that older PR to check what/where it changed, to bump the driver version, update mentions of "APC BXnnnMI/BXnnnnMI" with the newly handled pattern, and add a change note in NEWS.adoc (for planned v2.8.4 trail). Thanks!
Just a quick note that today, after having not occurred for a long time, the problem occurred again. I had the following settings used, as was recommended:
I have since added lbrb_log_delay_sec=2 to see if that alleviates the problem.
edit: disregard, the lbrb_log_delay_sec=2 setting wouldn't do anything since the driver automatically makes it 3 seconds when these models are detected. Hmm...
Activity
jimklimov commentedon May 7, 2025
Yes, at least if this is the same issue - I suppose extending these lines should help (and a PR would be welcome after testing):
Also probably review that older PR to check what/where it changed, to bump the driver version, update mentions of "APC BXnnnMI/BXnnnnMI" with the newly handled pattern, and add a change note in
NEWS.adoc(for planned v2.8.4 trail). Thanks!invario commentedon May 7, 2025
Got it, working on it, thanks!
invario commentedon May 7, 2025
Created PR #2944, hopefully I did things right, or at least mostly right. :)
invario commentedon May 9, 2025
Have been using new
usbhid-upsfrom PR #2944 and so far no more LB/RB messages!invario commentedon May 9, 2025
Thanks for the merge! Closing as addressed by #2944
invario commentedon May 27, 2025
Just a quick note that today, after having not occurred for a long time, the problem occurred again. I had the following settings used, as was recommended:
I have since added
lbrb_log_delay_sec=2to see if that alleviates the problem.edit: disregard, the
lbrb_log_delay_sec=2setting wouldn't do anything since the driver automatically makes it 3 seconds when these models are detected. Hmm...