2009/5/26 Arjen de Korte <[email protected] <nut%[email protected]>>
> Citeren Daniel O'Connor <[email protected]>: > > Note that I still have trouble starting mge-shut - 50+% of the time it >> says "Unable to get Report Descriptor" >> > > Have you also tried the newmge-ups driver? Being based on the same core as > the usbhid-ups (USB) driver, it may be a little more forgiving in case of > timeouts (although I'm not very familiar with it's predecessor, mge-shut). > CAUTION: newmge-shut has still a major issue I haven't yet solved (which explains why it has not yet superseded): a loss of synchronization tends to happen. The SHUT protocol is *very* verbose and uses a slow 2400 baud link, so you > want to give it lots of time before giving up (reading a 1500+ bytes report > descriptor will take more than 10 seconds). You may want to increase MAXAGE > in upsd.conf to at least double that, to prevent PINGing the driver to > death. > I still have a point in my TODO list which is the baudrate negotiation. newer units supports it. there are also rooms for improvement on the startup sequence. Daniel: I'm interested in debug trace of these startup failure. just to see how it fails, and what should be done. cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/
_______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
