[Nut-upsuser] UPS Atlantis OnePower - VT12094S
Hi, i have the ups in the subject. It is connected with usb cable. With nut 2.4.3 it was working quite good with megatec-usb driver. Now i just upgraded to nut 2.6 on my gentoo system and switching to blazer_usb is not working. Copying old megatec_usb driver from 2.4.6 and using it, everything returns to function. 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 drivers! [ !! ] * ERROR: upsdrv failed to start with megatec_usb: * Service upsdrv starting Network UPS Tools - UPS driver controller 2.6.0 Network UPS Tools - Megatec protocol driver 1.6 (2.4.3) Serial-over-USB transport layer 0.10 Megatec protocol UPS detected [ VT12094S]. * Service upsdrv started What can I do to use the new, still supported and developed blazer driver? Many thanks Andrea ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] UPS Atlantis OnePower - VT12094S
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 drivers! [ !! ] * ERROR: upsdrv failed to start Start the driver again, now with debugging enabled: /path/to/blazer_usb -DDD -a upsname Assuming the detection will fail, just post the full output from the above command here. Just to be sure, post the output of lsusb -v as well. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] UPS Atlantis OnePower - VT12094S
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 0.207981 - Serial Number: unknown 0.207983 - Bus: 008 0.207986 Trying to match device 0.207990 Device does not match - skipping 0.207995 Checking device (1D6B/0001) (008/001) 0.208006 - VendorID: 1d6b 0.208009 - ProductID: 0001 0.208012 - Manufacturer: unknown 0.208014 - Product: unknown 0.208017 - Serial Number: unknown 0.208020 - Bus: 008 0.208022 Trying to match device 0.208025 Device does not match - skipping 0.208030 Checking device (046D/0819) (002/004) 0.208039 - VendorID: 046d 0.208043 - ProductID: 0819 0.208045 - Manufacturer: unknown 0.208048 - Product: unknown 0.208050 - Serial Number: unknown 0.208053 - Bus: 002 0.208056 Trying to match device 0.208059 Device does not match - skipping 0.208062 Checking device (0BB4/0FF9) (002/002) 0.208073 - VendorID: 0bb4 0.208076 - ProductID: 0ff9 0.208078 - Manufacturer: unknown 0.208081 - Product: unknown 0.208084 - Serial Number: unknown 0.208086 - Bus: 002 0.208089 Trying to match device 0.208092 Device does not match - skipping 0.208096 Checking device (1D6B/0002) (002/001) 0.208105 - VendorID: 1d6b 0.208108 - ProductID: 0002 0.208111 - Manufacturer: unknown 0.208114 - Product: unknown 0.208116 - Serial Number: unknown 0.208119 - Bus: 002 0.208121 Trying to match device 0.208124 Device does not match - skipping 0.208128 Checking device (1D6B/0001) (007/001) 0.208139 - VendorID: 1d6b 0.208142 - ProductID: 0001 0.208145 - Manufacturer: unknown 0.208147 - Product: unknown 0.208150 - Serial Number: unknown 0.208152 - Bus: 007 0.208155 Trying to match device 0.208158 Device does not match - skipping 0.208162 Checking device (1D6B/0001) (006/001) 0.208173 - VendorID: 1d6b 0.208176 - ProductID: 0001 0.208179 - Manufacturer: unknown 0.208181 - Product: unknown 0.208184 - Serial Number: unknown 0.208187 - Bus: 006 0.208189 Trying to match device 0.208192 Device does not match - skipping 0.208196 Checking device (1D6B/0002) (001/001) 0.208206 - VendorID: 1d6b 0.208209 - ProductID: 0002 0.208212 - Manufacturer: unknown 0.208215 - Product: unknown 0.208217 - Serial Number: unknown 0.208220 - Bus: 001 0.208222 Trying to match device 0.208225 Device does not match - skipping 0.208229 Checking device (1D6B/0001) (004/001) 0.208240 - VendorID: 1d6b 0.208243 - ProductID: 0001 0.208245 - Manufacturer: unknown 0.208248 - Product: unknown 0.208251 - Serial Number: unknown 0.208253 - Bus: 004 0.208256 Trying to match device 0.208259 Device does not match - skipping 0.208263 Checking device (0A5C/2101) (003/002) 0.208273 - VendorID: 0a5c 0.208276 - ProductID: 2101 0.208278 - Manufacturer: unknown 0.208281 - Product: unknown 0.208284 - Serial Number: unknown 0.208286 - Bus: 003 0.208289 Trying to match device 0.208292 Device does not match - skipping 0.208296 Checking device (1D6B/0001) (003/001) 0.208306 - VendorID: 1d6b 0.208309 - ProductID: 0001 0.208311 - Manufacturer: unknown 0.208314 - Product: unknown 0.208317 - Serial Number: unknown 0.208319 - Bus: 003 0.208322 Trying to match device 0.208325 Device does not match - skipping 0.208328 Checking device (/) (005/004) 0.251866 - VendorID: 0.251883 - ProductID: 0.251889 - Manufacturer: 0.251894 - Product: 010937 0.251899 - Serial Number: 0.251904 - Bus: 005 0.251908 Trying to match device 0.251915 Device matches 0.251927 failed to claim USB device: could not claim interface 0: Device or resource busy 0.251953 detached kernel driver from USB device... 0.257887 Trying megatec protocol... 0.257901 send: Q1 0.506931 blazer_status: short reply 0.506950 Status read 1 failed 0.506954 send: Q1 0.754910 blazer_status: short reply 0.754930 Status read 2 failed 0.754938 send: Q1 1.003957 blazer_status: short reply 1.003976 Status read 3 failed 1.003982 Trying mustek protocol... 1.003987 send: QS 1.003992 read: QS 1.003997 blazer_status: short reply 1.004002 Status read 1 failed 1.004007 send: QS
