[please keep the list cc'd - thanks]
On Mar 22, 2015, at 6:20 AM, cinowell cinow...@gmail.com wrote:
I may use the 'mc' in terminal. But I am not sure how to find the exact bit
of FSD? I am totally newbie in this topic.
Could you please elaborate the hex editing of FSD bit?
I haven't used
On Mar 22, 2015, at 1:48 PM, cinowell cinow...@gmail.com wrote:
ups.status: ALARM OL OFF
Great! This was so easy than I expected.
UPS back to life again.
Thank you.
You're welcome. hyouko's 'ignoresab' fix should also get rid of the ALARM
status.
--
Charles Lepple
clepple@gmail
ups.status: ALARM OL OFF
Great! This was so easy than I expected.
UPS back to life again.
Thank you.
2015-03-22 14:22 GMT+02:00 Charles Lepple clep...@gmail.com:
[please keep the list cc'd - thanks]
On Mar 22, 2015, at 6:20 AM, cinowell cinow...@gmail.com wrote:
I may use the 'mc' in
2015-03-20 19:16 GMT+01:00 cinowell cinow...@gmail.com:
Hello,
I am attaching debug logs. Hopefully it helps to fix this issue.
Thank you.
Perfect, thanks!
Workaround committed and available in current git HEAD (with nutdrv_qx
driver, set 'ignoresab' flag): this should solve your problem.
2015-03-17 0:24 GMT+01:00 Charles Lepple clep...@gmail.com:
On Mar 16, 2015, at 12:26 PM, cinowell cinow...@gmail.com wrote:
I've done all the steps. However FSD indication did NOT disappear. So it
seems UPS always send the FSD flag.
One thing more.
Can you launch the driver with a debug
