search for: f6c100

...that was the problem. My sincere apologies if this has gone through and I just haven't seen it (could someone mail me if they are aware of what my problem is). If I'm just being flat annoying, please let me know that too =) ------------------------------- I've been running a Belkin F6C100-UNV for a couple of years, and just recently saw that nut might work with it. I'll fully admit the following: 1) I'm not completely certain that my UPS is working properly (I think the batteries are failing [which is why I'd like this to work]) 2) I'm running debian Etch with Nut...

Greetings all; I pulled a Belkin F6C100-4 into the shop this afternoon, deader than a door nail. Out of service for about a year because (I'm assuming here) that the cooling fan stopped and cooked what little remaining life there may have been out of the batteries, which had swelled so badly I had to split its frame to get them...

I recently installed NUT 2.2.1 and set it up with a Belkin F6C100-UNV. I can monitor it via serial (belkinunv) or USB (usbhid-ups) cable, and both do seem to work fine, but I would prefer USB to avoid having to add a PCI serial card to the machine. I had to unplug something else to try it with a serial cable. Using 'belkinunv', there's a "-...

I want to propose to change the format of the entries in the data/driver.list file. Currently the format is (according to the header) # <manufacturer> <model name> <model extra> <driver> Of these fields, the <model extra> field is not very well defined now. For many devices, it contains information about the communication interface used (serial / USB / SNMP) while