[Nut-upsdev] Tripplite OMNI1000LCD Watchdog

Arjen de Korte nut+devel at de-korte.org
Wed Dec 12 10:33:48 UTC 2007


> When I do this same thing with 2.2.0 it works perfectly with no errors.

Indeed. We now try to reconnect if we received an unexpected error and
this is something that leads to termination of the driver during the
initialization phase. I suspect that the report descriptor (see my
previous message) might help us find out where this error originates from.
I suspect that the report descriptor in the UPS is lying to us and
mentions a variable that really isn't available.

> I saw this same error referenced on the list archives, but it didn't seem
> to match my situation, and it wasn't for a Tripp Lite UPS. I tried to look
> through the libhid stuff to figure out if a buffer had changed size since
> 2.2.0, but gave up. What's your thoughts?

If you want to try a quick fix, in 'drivers/usbhid-ups.c' change line 1283

1280	default:
1281		/* Don't know what happened, try again later... */
1282		upslog_with_errno(LOG_DEBUG, "HIDGetDataValue");
1283		return FALSE;
1283		continue;
1284	}

This will make the driver continue as usual for this unexpected error, in
the hope that it will go away eventually. If not, it will keep logging
this error every 30 seconds, so that will probably nag people enough to
complain to the mailinglist and we can fix it.

Best regards, Arjen
Eindhoven - The Netherlands
Key fingerprint - 66 4E 03 2C 9D B5 CB 9B  7A FE 7E C1 EE 88 BC 57

More information about the Nut-upsdev mailing list