[Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression
Martin Ewing
martin.s.ewing at gmail.com
Wed Jul 13 13:55:42 UTC 2011
Arnaud,
Thanks for the reply! I imagine you are correct. I ran the command you
suggested (below). Apparently nut knows the device it should connect to,
but that device is "busy". And running as root doesn't overcome the
problem... (And I don't know why I should have to make /var/run/nut,
either.)
I am not well versed in Ubuntu bug reporting. Do you think I need to submit
this separately? Or should I just wait until the next release? (The lazy
way out.)
Thanks again,
Martin
martin at gimli:~$ sudo /lib/nut/usbhid-ups -u root -DDDD -a mybelkin
[sudo] password for martin:
Network UPS Tools - Generic HID driver 0.35 (2.6.0)
USB communication driver 0.31
0.000000 debug level is '4'
0.000580 Can't chdir to /var/run/nut: No such file or directory
martin at gimli:~$ sudo mkdir /var/run/nut
martin at gimli:~$ sudo /lib/nut/usbhid-ups -u root -DDDD -a mybelkin
Network UPS Tools - Generic HID driver 0.35 (2.6.0)
USB communication driver 0.31
0.000000 debug level is '4'
0.000546 upsdrv_initups...
0.106579 Checking device (03F0/0317) (008/002)
0.118917 - VendorID: 03f0
0.118930 - ProductID: 0317
0.118937 - Manufacturer: HewLett Packard
0.118943 - Product: HP LaserJet 1200
0.118948 - Serial Number: 00CNDL017843
0.118953 - Bus: 008
0.118958 Trying to match device
0.118984 Device does not match - skipping
0.118997 Checking device (1D6B/0001) (008/001)
0.119031 - VendorID: 1d6b
0.119038 - ProductID: 0001
0.119043 - Manufacturer: Linux 2.6.38-8-generic uhci_hcd
0.119048 - Product: UHCI Host Controller
0.119053 - Serial Number: 0000:00:1d.2
0.119059 - Bus: 008
0.119063 Trying to match device
0.119069 Device does not match - skipping
0.119078 Checking device (0403/6001) (007/002)
0.134688 - VendorID: 0403
0.134702 - ProductID: 6001
0.134709 - Manufacturer: ftdi
0.134715 - Product: usb serial converter
0.134721 - Serial Number: ftDWECKP
0.134726 - Bus: 007
0.134731 Trying to match device
0.134738 Device does not match - skipping
0.134748 Checking device (1D6B/0001) (007/001)
0.134782 - VendorID: 1d6b
0.134789 - ProductID: 0001
0.134794 - Manufacturer: Linux 2.6.38-8-generic uhci_hcd
0.134799 - Product: UHCI Host Controller
0.134804 - Serial Number: 0000:00:1d.1
0.134809 - Bus: 007
0.134814 Trying to match device
0.134820 Device does not match - skipping
0.134828 Checking device (050D/1100) (006/002)
0.160503 - VendorID: 050d
0.160517 - ProductID: 1100
0.160524 - Manufacturer: Belkin
0.160530 - Product: Belkin UPS
0.160536 - Serial Number: unknown
0.160541 - Bus: 006
0.160545 Trying to match device
0.160553 Device matches
0.160579 failed to claim USB device: could not claim interface 0:
Device or resource busy
0.162665 detached kernel driver from USB device...
0.173501 HID descriptor, method 1: (9 bytes) => 09 21 11 01 21 01 22
f2 01
0.173518 i=0, extra[i]=09, extra[i+1]=21
0.173528 HID descriptor, method 2: (9 bytes) => 09 21 11 01 21 01 22
f2 01
0.173535 HID descriptor length 498
0.243508 Report Descriptor size = 498
0.243528 Report Descriptor: (498 bytes) => 05 84 09 04 a1 01 05 86 09
26 a1 02 85 01
0.243541 75 08 95 01 15 00 26 ff 00 09 40 b1 02 85 02 09 42 b1 02 85
03 75 10 27 ff
0.243553 ff 00 00 09 43 b1 02 85 04 09 44 b1 02 c0 05 86 09 29 a1 02
26 ff 00 85 0d
0.243564 09 75 b1 02 85 0e 09 76 b1 02 85 0f 09 7c b1 02 c0 05 86 09
27 a1 02 85 10
0.243575 75 08 95 01 26 ff 00 09 58 b1 02 85 11 09 5a b1 02 85 15 75
10 95 01 27 ff
0.243586 ff 00 00 09 57 b1 02 85 16 09 56 b1 02 c0 05 86 09 2a a1 02
09 1a a1 02 85
0.243597 18 75 10 95 01 27 ff ff 00 00 09 30 b1 02 85 19 09 32 b1 02
c0 09 1c a1 02
0.243608 85 1b 75 10 95 01 27 ff ff 00 00 09 30 b1 02 85 1c 09 32 b1
02 85 1e 75 08
0.243619 95 01 26 ff 00 09 35 b1 02 c0 c0 05 86 09 10 a1 02 05 86 85
20 75 10 95 01
0.243630 27 ff ff 00 00 09 30 b1 02 85 21 75 08 95 01 26 ff 00 09 39
b1 02 c0 05 86
0.243641 09 28 a1 02 85 22 75 10 95 01 27 ff ff 00 00 09 21 b1 02 85
23 75 08 95 01
0.243652 26 ff 00 09 22 b1 02 c0 05 84 09 24 a1 00 85 28 09 fe 75 08
95 01 26 ff 00
0.243663 b1 02 85 29 09 ff b1 02 05 85 85 2a 09 89 b1 02 85 2b 09 8f
b1 02 85 2c 09
0.243674 8b b1 02 85 2d 09 44 75 08 95 01 81 82 09 44 b1 82 85 2e 09
45 81 82 09 45
0.243685 b1 82 05 84 85 30 09 40 75 10 95 01 27 fe ff 00 00 b1 02 85
31 09 30 b1 02
0.243696 85 32 09 31 75 08 95 01 26 ff 00 b1 02 05 85 85 33 09 2c 75
08 95 01 26 ff
0.243707 00 b1 02 85 34 09 66 81 82 09 66 b1 82 85 35 09 68 75 10 95
01 27 ff ff 00
0.243718 00 81 82 09 68 b1 82 85 36 26 ff 00 75 08 95 01 09 83 b1 02
85 37 09 67 b1
0.243729 02 85 38 09 8c b1 02 85 39 09 8e b1 02 85 3a 09 29 b1 82 85
3b 09 8d b1 02
0.243740 85 3c 09 d0 b1 82 09 d0 81 82 85 3d 09 42 81 82 09 42 b1 82
85 3e 05 84 09
0.243748 69 81 82 09 69 b1 82 c0 c0
0.243825 Using subdriver: Belkin HID 0.12
0.243836 Entering libusb_get_report
0.248503 libusb_get_report: could not claim interface 0: Device or
resource busy
0.248526 Can't retrieve Report 01: Device or resource busy
0.248546 Path: UPS.BELKINConfig.BELKINConfigVoltage, Type: Feature,
ReportID: 0x01, Offset: 0, Size: 8
0.248554 Entering libusb_get_report
0.254471 libusb_get_report: could not claim interface 0: Device or
resource busy
0.254489 Can't retrieve Report 02: Device or resource busy
0.254501 Path: UPS.BELKINConfig.BELKINConfigFrequency, Type: Feature,
ReportID: 0x02, Offset: 0, Size: 8
0.254508 Entering libusb_get_report
0.259523 libusb_get_report: could not claim interface 0: Device or
resource busy
0.259542 Can't retrieve Report 03: Device or resource busy
0.259554 Path: UPS.BELKINConfig.BELKINConfigApparentPower, Type:
Feature, ReportID: 0x03, Offset: 0, Size: 16
0.259561 Entering libusb_get_report
0.264524 libusb_get_report: could not claim interface 0: Device or
resource busy
0.264543 Can't retrieve Report 04: Device or resource busy
0.264555 Path: UPS.BELKINConfig.BELKINConfigBatteryVoltage, Type:
Feature, ReportID: 0x04, Offset: 0, Size: 16
0.264562 Entering libusb_get_report
0.269500 libusb_get_report: could not claim interface 0: Device or
resource busy
0.269519 Can't retrieve Report 0d: Device or resource busy
0.269531 Path: UPS.BELKINDevice.BELKINModelString, Type: Feature,
ReportID: 0x0d, Offset: 0, Size: 16
0.269538 Entering libusb_get_report
0.274495 libusb_get_report: could not claim interface 0: Device or
resource busy
0.274514 Can't retrieve Report 0e: Device or resource busy
0.274526 Path: UPS.BELKINDevice.BELKINModelStringOffset, Type:
Feature, ReportID: 0x0e, Offset: 0, Size: 16
0.274533 Entering libusb_get_report
0.279521 libusb_get_report: could not claim interface 0: Device or
resource busy
0.279541 Can't retrieve Report 0f: Device or resource busy
0.279616 Path: UPS.BELKINDevice.BELKINUPSType, Type: Feature,
ReportID: 0x0f, Offset: 0, Size: 16
0.279623 Entering libusb_get_report
0.284523 libusb_get_report: could not claim interface 0: Device or
resource busy
0.284541 Can't retrieve Report 10: Device or resource busy
0.284552 Path: UPS.BELKINControls.BELKINTest, Type: Feature, ReportID:
0x10, Offset: 0, Size: 8
0.284559 Entering libusb_get_report
0.289503 libusb_get_report: could not claim interface 0: Device or
resource busy
0.289522 Can't retrieve Report 11: Device or resource busy
0.289534 Path: UPS.BELKINControls.BELKINAudibleAlarmControl, Type:
Feature, ReportID: 0x11, Offset: 0, Size: 8
0.289541 Entering libusb_get_report
0.294499 libusb_get_report: could not claim interface 0: Device or
resource busy
0.294517 Can't retrieve Report 15: Device or resource busy
0.294529 Path: UPS.BELKINControls.BELKINDelayBeforeShutdown, Type:
Feature, ReportID: 0x15, Offset: 0, Size: 16
0.294536 Entering libusb_get_report
0.298501 libusb_get_report: could not claim interface 0: Device or
resource busy
0.298519 Can't retrieve Report 16: Device or resource busy
0.298531 Path: UPS.BELKINControls.BELKINDelayBeforeStartup, Type:
Feature, ReportID: 0x16, Offset: 0, Size: 16
0.298538 Entering libusb_get_report
0.304535 libusb_get_report: could not claim interface 0: Device or
resource busy
0.304551 Can't retrieve Report 18: Device or resource busy
0.304561 Path: UPS.BELKINPowerState.BELKINInput.BELKINVoltage, Type:
Feature, ReportID: 0x18, Offset: 0, Size: 16
0.304567 Entering libusb_get_report
0.309538 libusb_get_report: could not claim interface 0: Device or
resource busy
0.309555 Can't retrieve Report 19: Device or resource busy
0.309565 Path: UPS.BELKINPowerState.BELKINInput.BELKINFrequency, Type:
Feature, ReportID: 0x19, Offset: 0, Size: 16
0.309571 Entering libusb_get_report
0.314488 libusb_get_report: could not claim interface 0: Device or
resource busy
0.314504 Can't retrieve Report 1b: Device or resource busy
0.314514 Path: UPS.BELKINPowerState.BELKINOutput.BELKINVoltage, Type:
Feature, ReportID: 0x1b, Offset: 0, Size: 16
0.314521 Entering libusb_get_report
0.320521 libusb_get_report: could not claim interface 0: Device or
resource busy
0.320540 Can't retrieve Report 1c: Device or resource busy
0.320551 Path: UPS.BELKINPowerState.BELKINOutput.BELKINFrequency,
Type: Feature, ReportID: 0x1c, Offset: 0, Size: 16
0.320559 Entering libusb_get_report
0.325471 libusb_get_report: could not claim interface 0: Device or
resource busy
0.325489 Can't retrieve Report 1e: Device or resource busy
0.325501 Path: UPS.BELKINPowerState.BELKINOutput.BELKINPercentLoad,
Type: Feature, ReportID: 0x1e, Offset: 0, Size: 8
0.325509 Entering libusb_get_report
0.330499 libusb_get_report: could not claim interface 0: Device or
resource busy
0.330518 Can't retrieve Report 20: Device or resource busy
0.330530 Path: UPS.BELKINBatterySystem.BELKINVoltage, Type: Feature,
ReportID: 0x20, Offset: 0, Size: 16
0.330537 Entering libusb_get_report
0.335477 libusb_get_report: could not claim interface 0: Device or
resource busy
0.335495 Can't retrieve Report 21: Device or resource busy
0.335506 Path: UPS.BELKINBatterySystem.BELKINCharge, Type: Feature,
ReportID: 0x21, Offset: 0, Size: 8
0.335514 Entering libusb_get_report
0.340561 libusb_get_report: could not claim interface 0: Device or
resource busy
0.340578 Can't retrieve Report 22: Device or resource busy
0.340589 Path: UPS.BELKINStatus.BELKINPowerStatus, Type: Feature,
ReportID: 0x22, Offset: 0, Size: 16
0.340596 Entering libusb_get_report
0.345491 libusb_get_report: could not claim interface 0: Device or
resource busy
0.345510 Can't retrieve Report 23: Device or resource busy
0.345521 Path: UPS.BELKINStatus.BELKINBatteryStatus, Type: Feature,
ReportID: 0x23, Offset: 0, Size: 8
0.345528 Entering libusb_get_report
0.349524 libusb_get_report: could not claim interface 0: Device or
resource busy
0.349543 Can't retrieve Report 28: Device or resource busy
0.349555 Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID:
0x28, Offset: 0, Size: 8
0.349561 Entering libusb_get_report
0.355476 libusb_get_report: could not claim interface 0: Device or
resource busy
0.355494 Can't retrieve Report 29: Device or resource busy
0.355505 Path: UPS.PowerSummary.iSerialNumber, Type: Feature,
ReportID: 0x29, Offset: 0, Size: 8
0.355513 Entering libusb_get_report
0.360501 libusb_get_report: could not claim interface 0: Device or
resource busy
0.360520 Can't retrieve Report 2a: Device or resource busy
0.360532 Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature,
ReportID: 0x2a, Offset: 0, Size: 8
0.360539 Entering libusb_get_report
0.365473 libusb_get_report: could not claim interface 0: Device or
resource busy
0.365491 Can't retrieve Report 2b: Device or resource busy
0.365503 Path: UPS.PowerSummary.iOEMInformation, Type: Feature,
ReportID: 0x2b, Offset: 0, Size: 8
0.365510 Entering libusb_get_report
0.371498 libusb_get_report: could not claim interface 0: Device or
resource busy
0.371580 Can't retrieve Report 2c: Device or resource busy
0.371591 Path: UPS.PowerSummary.Rechargeable, Type: Feature, ReportID:
0x2c, Offset: 0, Size: 8
0.371598 Entering libusb_get_report
0.375489 libusb_get_report: could not claim interface 0: Device or
resource busy
0.375508 Can't retrieve Report 2d: Device or resource busy
0.375526 Path: UPS.PowerSummary.Charging, Type: Input, ReportID: 0x2d,
Offset: 0, Size: 8
0.375534 Entering libusb_get_report
0.380528 libusb_get_report: could not claim interface 0: Device or
resource busy
0.380547 Can't retrieve Report 2d: Device or resource busy
0.380559 Path: UPS.PowerSummary.Charging, Type: Feature, ReportID:
0x2d, Offset: 0, Size: 8
0.380566 Entering libusb_get_report
0.385477 libusb_get_report: could not claim interface 0: Device or
resource busy
0.385495 Can't retrieve Report 2e: Device or resource busy
0.385507 Path: UPS.PowerSummary.Discharging, Type: Input, ReportID:
0x2e, Offset: 0, Size: 8
0.385514 Entering libusb_get_report
0.390501 libusb_get_report: could not claim interface 0: Device or
resource busy
0.390520 Can't retrieve Report 2e: Device or resource busy
0.390532 Path: UPS.PowerSummary.Discharging, Type: Feature, ReportID:
0x2e, Offset: 0, Size: 8
0.390539 Entering libusb_get_report
0.395471 libusb_get_report: could not claim interface 0: Device or
resource busy
0.395488 Can't retrieve Report 30: Device or resource busy
0.395500 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature,
ReportID: 0x30, Offset: 0, Size: 16
0.395508 Entering libusb_get_report
0.400499 libusb_get_report: could not claim interface 0: Device or
resource busy
0.400518 Can't retrieve Report 31: Device or resource busy
0.400530 Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID:
0x31, Offset: 0, Size: 16
0.400537 Entering libusb_get_report
0.405497 libusb_get_report: could not claim interface 0: Device or
resource busy
0.405516 Can't retrieve Report 32: Device or resource busy
0.405528 Path: UPS.PowerSummary.Current, Type: Feature, ReportID:
0x32, Offset: 0, Size: 8
0.405535 Entering libusb_get_report
0.410523 libusb_get_report: could not claim interface 0: Device or
resource busy
0.410542 Can't retrieve Report 33: Device or resource busy
0.410553 Path: UPS.PowerSummary.CapacityMode, Type: Feature, ReportID:
0x33, Offset: 0, Size: 8
0.410560 Entering libusb_get_report
0.415474 libusb_get_report: could not claim interface 0: Device or
resource busy
0.415492 Can't retrieve Report 34: Device or resource busy
0.415504 Path: UPS.PowerSummary.RemainingCapacity, Type: Input,
ReportID: 0x34, Offset: 0, Size: 8
0.415512 Entering libusb_get_report
0.422500 libusb_get_report: could not claim interface 0: Device or
resource busy
0.422519 Can't retrieve Report 34: Device or resource busy
0.422531 Path: UPS.PowerSummary.RemainingCapacity, Type: Feature,
ReportID: 0x34, Offset: 0, Size: 8
0.422538 Entering libusb_get_report
0.427474 libusb_get_report: could not claim interface 0: Device or
resource busy
0.427492 Can't retrieve Report 35: Device or resource busy
0.427505 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, ReportID:
0x35, Offset: 0, Size: 16
0.427512 Entering libusb_get_report
0.432497 libusb_get_report: could not claim interface 0: Device or
resource busy
0.432515 Can't retrieve Report 35: Device or resource busy
0.432527 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature,
ReportID: 0x35, Offset: 0, Size: 16
0.432534 Entering libusb_get_report
0.437492 libusb_get_report: could not claim interface 0: Device or
resource busy
0.437508 Can't retrieve Report 36: Device or resource busy
0.437520 Path: UPS.PowerSummary.DesignCapacity, Type: Feature,
ReportID: 0x36, Offset: 0, Size: 8
0.437526 Entering libusb_get_report
0.442526 libusb_get_report: could not claim interface 0: Device or
resource busy
0.442544 Can't retrieve Report 37: Device or resource busy
0.442556 Path: UPS.PowerSummary.FullChargeCapacity, Type: Feature,
ReportID: 0x37, Offset: 0, Size: 8
0.442563 Entering libusb_get_report
0.447503 libusb_get_report: could not claim interface 0: Device or
resource busy
0.447520 Can't retrieve Report 38: Device or resource busy
0.447530 Path: UPS.PowerSummary.WarningCapacityLimit, Type: Feature,
ReportID: 0x38, Offset: 0, Size: 8
0.447536 Entering libusb_get_report
0.452499 libusb_get_report: could not claim interface 0: Device or
resource busy
0.452518 Can't retrieve Report 39: Device or resource busy
0.452529 Path: UPS.PowerSummary.CapacityGranularity2, Type: Feature,
ReportID: 0x39, Offset: 0, Size: 8
0.452537 Entering libusb_get_report
0.457501 libusb_get_report: could not claim interface 0: Device or
resource busy
0.457520 Can't retrieve Report 3a: Device or resource busy
0.457532 Path: UPS.PowerSummary.RemainingCapacityLimit, Type: Feature,
ReportID: 0x3a, Offset: 0, Size: 8
0.457539 Entering libusb_get_report
0.462503 libusb_get_report: could not claim interface 0: Device or
resource busy
0.462521 Can't retrieve Report 3b: Device or resource busy
0.462533 Path: UPS.PowerSummary.CapacityGranularity1, Type: Feature,
ReportID: 0x3b, Offset: 0, Size: 8
0.462540 Entering libusb_get_report
0.467522 libusb_get_report: could not claim interface 0: Device or
resource busy
0.467541 Can't retrieve Report 3c: Device or resource busy
0.467553 Path: UPS.PowerSummary.ACPresent, Type: Feature, ReportID:
0x3c, Offset: 0, Size: 8
0.467560 Entering libusb_get_report
0.472522 libusb_get_report: could not claim interface 0: Device or
resource busy
0.472540 Can't retrieve Report 3c: Device or resource busy
0.472552 Path: UPS.PowerSummary.ACPresent, Type: Input, ReportID:
0x3c, Offset: 0, Size: 8
0.472559 Entering libusb_get_report
0.477502 libusb_get_report: could not claim interface 0: Device or
resource busy
0.477521 Can't retrieve Report 3d: Device or resource busy
0.477533 Path: UPS.PowerSummary.BelowRemainingCapacityLimit, Type:
Input, ReportID: 0x3d, Offset: 0, Size: 8
0.477540 Entering libusb_get_report
0.482497 libusb_get_report: could not claim interface 0: Device or
resource busy
0.482515 Can't retrieve Report 3d: Device or resource busy
0.482527 Path: UPS.PowerSummary.BelowRemainingCapacityLimit, Type:
Feature, ReportID: 0x3d, Offset: 0, Size: 8
0.482535 Entering libusb_get_report
0.488500 libusb_get_report: could not claim interface 0: Device or
resource busy
0.488519 Can't retrieve Report 3e: Device or resource busy
0.488531 Path: UPS.PowerSummary.ShutdownImminent, Type: Input,
ReportID: 0x3e, Offset: 0, Size: 8
0.488537 Entering libusb_get_report
0.493496 libusb_get_report: could not claim interface 0: Device or
resource busy
0.493514 Can't retrieve Report 3e: Device or resource busy
0.493526 Path: UPS.PowerSummary.ShutdownImminent, Type: Feature,
ReportID: 0x3e, Offset: 0, Size: 8
0.493549 string_to_path: depth = 3
0.493557 Entering libusb_get_report
0.498492 libusb_get_report: could not claim interface 0: Device or
resource busy
0.498511 Can't retrieve Report 29: Device or resource busy
0.498529 Report descriptor retrieved (Reportlen = 498)
0.498536 Found HID device
0.498542 Detected a UPS: Belkin /Belkin UPS
0.498553 string_to_path: depth = 3
0.498568 Entering libusb_get_report
0.502533 libusb_get_report: could not claim interface 0: Device or
resource busy
0.502552 Can't retrieve Report 21: Device or resource busy
0.502561 Got disconnected by another driver: Device or resource busy
0.502568 Can't initialize data from HID UPS
On Wed, Jul 13, 2011 at 3:17 AM, Arnaud Quette <aquette.dev at gmail.com>wrote:
> Hi Martin,
>
> 2011/6/27 Martin Ewing <martin.s.ewing at gmail.com>
>
> > I have a very similar situation with my Belkin UPS on Natty (worked on
> > previous release).
> >
> > See
> >
> > $ lsb_release -rd
> > Description: Ubuntu 11.04
> > Release: 11.04
> >
> > martin at gimli:~$ aptitude show nut
> > Package: nut
> > State: installed
> > Automatically installed: no
> > Version: 2.6.0-1ubuntu3
> > ...
> >
> > sudo /lib/nut/usbhid-ups -DDDD -a mybelkin
> > Network UPS Tools - Generic HID driver 0.35 (2.6.0)
> > USB communication driver 0.31
> > 0.000000 debug level is '4'
> > 0.000583 upsdrv_initups...
> > 0.266176 Checking device (1D6B/0001) (008/001)
> > 0.266219 - VendorID: 1d6b
> > 0.266226 - ProductID: 0001
> > 0.266232 - Manufacturer: unknown
> > 0.266237 - Product: unknown
> > 0.266242 - Serial Number: unknown
> > 0.266247 - Bus: 008
> > 0.266252 Trying to match device
> > 0.266275 Device does not match - skipping
> > 0.266285 Checking device (1D6B/0001) (007/001)
> > 0.266303 - VendorID: 1d6b
> > 0.266309 - ProductID: 0001
> > 0.266315 - Manufacturer: unknown
> > 0.266320 - Product: unknown
> > 0.266325 - Serial Number: unknown
> > 0.266330 - Bus: 007
> > 0.266335 Trying to match device
> > 0.266341 Device does not match - skipping
> > 0.266349 Checking device (050D/1100) (006/002)
> > 0.291945 - VendorID: 050d
> > 0.291959 - ProductID: 1100
> > 0.291966 - Manufacturer: Belkin
> > 0.291972 - Product: Belkin UPS
> > 0.291977 - Serial Number: unknown
> > 0.291982 - Bus: 006
> > 0.291987 Trying to match device
> > 0.291995 Device matches
> > (...)
>
> 0.383981 Entering libusb_get_report
> > 0.388933 libusb_get_report: error sending control message:
> Operation
> > not permitted
> > ...
> >
> > Is this the same bug?
>
>
> I don't think so.
> the issue reported here was related to a code change, that resulted in a
> regression.
>
> yours seem to be with privileges.
> to validate this, try launching the driver with root privs (note the "-u
> root"):
> $ sudo /lib/nut/usbhid-ups -u root -DDDD -a mybelkin
>
> Is there a fix
>
>
> it's related to udev, and since there seems to be quite some similar
> issues,
> I'm wondering if there is a race condition between udev (started through
> upstart native scripts) and nut (started through upstart sysV compat
> script).
>
> cheers,
> Arnaud
> --
> Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
> Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
> Debian Developer - http://www.debian.org
> Free Software Developer - http://arnaud.quette.free.fr/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/779512
>
> Title:
> nut-2.6.0-1ubuntu3 behavior regression
>
> Status in “nut” package in Ubuntu:
> Triaged
>
> Bug description:
> Binary package hint: nut
>
> Prior to upgrading to Natty, I had the nut-2.4.3-1ubuntu5 package and
> it was working correctly.
>
> After upgrading to Natty, I have the nut-2.6.0-1ubuntu3 package and it
> is not working correctly. Here's my release info:
>
> •[x4linux:~] mmusgrove $ lsb_release -rd
> Description: Ubuntu 11.04
> Release: 11.04
>
> The symptom is that it can't initialize data from HID UPS and so the
> driver fails to start.
>
> •[x4linux:~] mmusgrove $ sudo upsdrvctl start
> Network UPS Tools - UPS driver controller 2.6.0
> Network UPS Tools - Generic HID driver 0.35 (2.6.0)
> USB communication driver 0.31
> Using subdriver: CyberPower HID 0.3
> libusb_get_report: No error
> Can't initialize data from HID UPS
> Driver failed to start (exit status=1)
>
> This appears to be the old behavior from 2.4.x prior to 2.4.3.
>
> This was reported for Debian months ago:
>
> http://www.google.com/search?source=ig&hl=en&q=nut+2.6.0-1+libusb_get_report%3A+No+error+Can%27t+initialize+data+from+HID+UPS
>
> Possible related to Bug #701182 (although that is for 2.4.3-2)
> https://bugs.launchpad.net/ubuntu/+source/nut/+bug/701182
>
> ProblemType: Bug
> DistroRelease: Ubuntu 11.04
> Package: nut 2.6.0-1ubuntu3
> ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
> Uname: Linux 2.6.38-8-generic x86_64
> NonfreeKernelModules: fglrx
> Architecture: amd64
> Date: Sun May 8 09:37:55 2011
> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64
> (20101007)
> KernelVersion: Linux x4linux 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11
> 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
> ProcEnviron:
> LANGUAGE=en_US:en
> PATH=(custom, user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: nut
> UpgradeStatus: Upgraded to natty on 2011-05-06 (2 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+subscriptions
>
--
Martin Ewing
Branford, Connecticut
martin.s.ewing at gmail.com
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/779512
Title:
nut-2.6.0-1ubuntu3 behavior regression
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+subscriptions
More information about the Ubuntu-server-bugs
mailing list