Citeren Andrea krog...@gmail.com:
Exactly what benefit can i have using the new driver with this hack?
If nothing changes i can wait for nut 2.6.1 ;-)
It would help to confirm that this is indeed the problem so that
nut-2.6.1 will work out-of-the box for you (and all others using this
* Service upsdrv starting
Network UPS Tools - UPS driver controller 2.6.0
Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.6.0)
Can't claim USB device [:]: could not detach kernel driver
from interface 0: Operation not permitted
Driver failed to start (exit status=1)
Failed to
Citeren Andrea krog...@gmail.com:
* Service upsdrv starting
Network UPS Tools - UPS driver controller 2.6.0
Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.6.0)
Can't claim USB device [:]: could not detach kernel driver
from interface 0: Operation not permitted
Driver failed
Citeren Andrea krog...@gmail.com:
0.257887 Trying megatec protocol...
0.257901 send: Q1
0.506931 blazer_status: short reply
0.506950 Status read 1 failed
Sadly there is a small flaw in the krauler subdriver here and it
doesn't output the data it has read from the
Exactly what benefit can i have using the new driver with this hack?
If nothing changes i can wait for nut 2.6.1 ;-)
But thinking about all the people with this ups and the same
problem... can you write some note on the compatibility list page?
Many thanks for your job.
If you need to test future
Citeren Andrea krog...@gmail.com:
Some output with blazer_usb:
* Service upsdrv starting
Network UPS Tools - UPS driver controller 2.6.0
Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.6.0)
No supported UPS detected
Driver failed to start (exit status=1)
Failed to start UPS
Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.6.0)
0.00 debug level is '3'
0.207935 Checking device (046D/C517) (008/002)
0.207969 - VendorID: 046d
0.207973 - ProductID: c517
0.207975 - Manufacturer: unknown
0.207978 - Product: unknown
7 matches
Mail list logo
