Hello. I recently upgraded from Ubuntu Maverick to Natty and hence upgraded nut from 2.4.3-1ubuntu5 to 2.6.0-1ubuntu3. My Sven PowerPro+ 1000 UPS ( http://en.sven.ru/catalog/ups/power_pro_plus_1000.htm ) worked fine with the previous version, using megatec_usb driver, but doesn't work with the current version, since megatec_usb is no longer available. Here is the output from blazer_usb. sudo /lib/nut/blazer_usb -a sven1 -DDD Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.4.3) 0.000000 debug level is '3' 0.251050 Checking device (FFFF/0000) (009/002) 0.295442 - VendorID: ffff 0.295451 - ProductID: 0000 0.295456 - Manufacturer: 0.295460 - Product: 010937 0.295464 - Serial Number: 0.295468 - Bus: 009 0.295472 Trying to match device 0.295477 Device matches 0.295493 failed to claim USB device: could not claim interface 0: Device or resource busy 0.295505 detached kernel driver from USB device... 0.301458 Trying megatec protocol... 0.301466 send: Q1 0.549441 blazer_status: short reply 0.549453 Status read 1 failed 0.549458 send: Q1 1.042431 blazer_status: short reply 1.042444 Status read 2 failed 1.042449 send: Q1 1.291425 blazer_status: short reply 1.291435 Status read 3 failed 1.291440 Trying mustek protocol... 1.291445 send: QS 1.291449 read: QS 1.291453 blazer_status: short reply 1.291457 Status read 1 failed 1.291460 send: QS 1.291464 read: QS 1.291467 blazer_status: short reply 1.291470 Status read 2 failed 1.291473 send: QS 1.291476 read: QS 1.291479 blazer_status: short reply 1.291482 Status read 3 failed 1.291486 Trying megatec/old protocol... 1.291489 send: D 1.291492 read: D 1.291495 blazer_status: short reply 1.291498 Status read 1 failed 1.291502 send: D 1.291505 read: D 1.291508 blazer_status: short reply 1.291511 Status read 2 failed 1.291514 send: D 1.291517 read: D 1.291520 blazer_status: short reply 1.291524 Status read 3 failed 1.291527 No supported UPS detected I downgraded back to 2.4.3, configured nut to use megatec_usb again, and it started working again. However, it seems strange that I cannot use the latest version. -- Vlad -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20110626/1b42699f/attachment-0001.html>
On Sat, Jun 25, 2011 at 8:13 PM, Vlad <nut at wolf.umail.net> wrote:> Hello. > > I recently upgraded from Ubuntu Maverick to Natty and hence upgraded nut > from 2.4.3-1ubuntu5 to 2.6.0-1ubuntu3. > My Sven PowerPro+ 1000 UPS ( > http://en.sven.ru/catalog/ups/power_pro_plus_1000.htm) worked fine with > the previous version, using megatec_usb driver, but doesn't work with the > current version, since megatec_usb is no longer available. > > Here is the output from blazer_usb. > > sudo /lib/nut/blazer_usb -a sven1 -DDD > Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.4.3) > 0.000000 debug level is '3' > 0.251050 Checking device (FFFF/0000) (009/002) > 0.295442 - VendorID: ffff > 0.295451 - ProductID: 0000 > 0.295456 - Manufacturer: > 0.295460 - Product: 010937 > 0.295464 - Serial Number: > 0.295468 - Bus: 009 > 0.295472 Trying to match device > 0.295477 Device matches > 0.295493 failed to claim USB device: could not claim interface 0: > Device or resource busy > 0.295505 detached kernel driver from USB device... > 0.301458 Trying megatec protocol... > 0.301466 send: Q1 > 0.549441 blazer_status: short reply > 0.549453 Status read 1 failed > 0.549458 send: Q1 > 1.042431 blazer_status: short reply > 1.042444 Status read 2 failed > 1.042449 send: Q1 > 1.291425 blazer_status: short reply > 1.291435 Status read 3 failed > 1.291440 Trying mustek protocol... > 1.291445 send: QS > 1.291449 read: QS > 1.291453 blazer_status: short reply > 1.291457 Status read 1 failed > 1.291460 send: QS > 1.291464 read: QS > 1.291467 blazer_status: short reply > 1.291470 Status read 2 failed > 1.291473 send: QS > 1.291476 read: QS > 1.291479 blazer_status: short reply > 1.291482 Status read 3 failed > 1.291486 Trying megatec/old protocol... > 1.291489 send: D > 1.291492 read: D > 1.291495 blazer_status: short reply > 1.291498 Status read 1 failed > 1.291502 send: D > 1.291505 read: D > 1.291508 blazer_status: short reply > 1.291511 Status read 2 failed > 1.291514 send: D > 1.291517 read: D > 1.291520 blazer_status: short reply > 1.291524 Status read 3 failed > 1.291527 No supported UPS detected > > I downgraded back to 2.4.3, configured nut to use megatec_usb again, and it > started working again. > However, it seems strange that I cannot use the latest version. > > -- > Vlad > > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser >Vlad, This seems very similar to the trouble I have with a Belkin UPS (USB) with Natty (64 bit). Martin -- Martin Ewing Branford, Connecticut martin.s.ewing at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20110626/3a514e17/attachment.html>
Citeren Martin Ewing <martin.s.ewing at gmail.com>:> This seems very similar to the trouble I have with a Belkin UPS (USB) with > Natty (64 bit).Not at all. You seem to be suffering from a permissions problem, where Vlad is not (most likely, there is a problem in the protocol handling). These are totally unrelated issues. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected)
Citeren Vlad <nut at wolf.umail.net>:> I downgraded back to 2.4.3, configured nut to use megatec_usb again, > and it started working again. > However, it seems strange that I cannot use the latest version.This is not strange at all. We have reworked this driver core and could not find people with access to these device and willing to test this. Note that blazer_usb has been in the stable version since 2.4.0 was released and have urged people to switch over to this one. We have had no reports that the subdriver that is used by this series of UPS devices was broken. In that case, there is nothing more we can do than to switch to the new driver and see what happens. We've had some changes after 2.6.0 was released in this driver, so you could try if upgrading to that helps. There are some more changes underway, but due to the lack of help we're getting from the userbase, this is put on the back burner (without people volunteering to test changes, there is no point in putting effort in it). You could help us here by running the development version for this driver and report back your results, since we will need testing from as many different flavors of the krauler series of devices as possible (USB ID's 0001:0000 and FFFF:0000). Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected)
Hi, Arjen. Sorry for the late reply and lack of quoting - I occasionally messed up my subscription settings and didn't get your message. I'll try to install dev version and see whether it works. What kind of diagnostic info would you need? USB ID of my device is FFFF:0000. -- Vlad