apcupsd usb problem [CLOSED]

Message

whiskeypriest · Post by **whiskeypriest** » Thu Oct 28, 2004 4:21 pm

A couple thoughts

First, which version of apcupsd are you using?

Second, it looks like youve got two USB hubs: one using the UHCI controller (an onboard Intel, I gather) and one using the OHCI controller (a PCI card, if Im not mistaken). Which one is the UPS connected to? Have you tried reversing the connection (i.e. plugging into the PCI card if it was connected directly before, or vice-versa)?

Finally, what does your apcupsd.conf file look like? It looks like there might be a problem with device allocation; you can try commenting out the DEVICE line in your configuration file (see here for the reason why).

Like you, I answered no to all the new USB options in gentoo-dev-sources-2.6.9-r1, but my system is functioning as expected.

Finally, since this thread is actually about bumpert trying to get an Energizer UPS working with NUT, we might wish to move this discussion over to the Troubleshooting apcupsd with USB thread.

bluesea · Post by **bluesea** » Fri Oct 29, 2004 3:54 am

Thanks for the input. Before trying all those things, I had a thought based on your comment about saying "No" to all the new USB kernel options. It occurred to me that there was one _new_ USB-related item which I did _not_ say "no" to: CONFIG_BLK_DEV_UB. The help message for this item claims that it helps with USB memory sticks/keys. Since I use those (with no problem until 2.6.9-r1

) I figured it couldn't hurt to say "yes". My new rule for new kernels: if it's not broken... etc, etc..

anyway - recompiled the kernel withOUT CONFIG_BLK_DEV_UB, and everything's fine again.

apcupsd is working again, as is my USB memory stick (which had also stopped working).

For some reason CONFIG_BLK_DEV_UB prevented the creation of /dev/usb/hid/hiddev0 (among other things). Note that I'm not using udev yet (if it's not broken.... and yes, I know someday I'll have to convert).

Anyway - bottom line, got rid of CONFIG_BLK_DEV_UB and my /dev/usb/ came back and the devices could all be found.

Thanks for your input.

whiskeypriest · Post by **whiskeypriest** » Fri Oct 29, 2004 2:20 pm

Happy to be of service (whether directly or not)and good catch on CONFIG_BLK_DEV_UB. Since I didnt see it in your diff output, I forgot all about saying no to it. Glad its all sorted.

We now return you to your regularly scheduled thread, already in progress

bumpert · Post by **bumpert** » Sun Nov 21, 2004 6:15 pm

is someone able to download the package offered into this link: http://www.vttoth.com/ER-OF800.htm

i'm not able

thx

bumpert · Post by **bumpert** » Sun Dec 05, 2004 3:22 am

nobody? it could be the solution i need

thx

bumpert · Post by **bumpert** » Mon Jan 03, 2005 2:46 am

i was finally able to download it, so when i'll have some spare time i'll try to make it work, and give you feedback

thx

bumpert · Post by **bumpert** » Mon Jan 03, 2005 3:22 am

maybe you could help, i was trying to use this package. I do all the step in the installation guide, but i had problem with the step 5, i did the step 6, and come back to step 5 without success. It didn't seems to find my UPS

thx

bumpert · Post by **bumpert** » Sun Jan 23, 2005 12:48 pm

nobody?

bumpert · Post by **bumpert** » Wed Mar 30, 2005 12:36 am

saghi · Post by **saghi** » Wed Oct 05, 2005 5:07 am

Hi,
I emerged Nut 2.0.0-r1 which, according to Viktor Toth, includes the driver for the Energizer ER-OF800 UPS.
Well, I don't see it in there at all! In the driver's directory (/usr/lib/nut) there's nothing which comes close to the Energizer. Here's a list:

apcsmart
belkin
belkinunv
bestuferrups
bestups
blazer
cyberpower
cyberpower1100
esupssmart
etapro
everups
fentonups
genericups
ippon
isbmex
liebert
masterguard
mge-shut
mge-utalk
oneac
powercom
safenet
sms
tripplite
tripplitesu
upsdrvctl
victronups

Shouldn't I be seeing an "Energizer Family" driver? Everything up to this step has worked wonderfully for me, the "qups /dev/usb/hid/hiddev0 I" works, it reports the presence of my UPS, I just have no idea what to set my "driver" to in the /etc/nut/ups.conf.
Any help would be appreciated.
Thanks!
Oh yeah, I compiled all the USB specific stuff in the kernel itself and not as modules, would that be a problem?

bumpert · Post by **bumpert** » Wed Oct 05, 2005 2:05 pm

I hope you'll get help. For my part, i stop searching for this, cause my UPS is now dead

thx for all who tried to help me. Good luck saghi...

saghi · Post by **saghi** » Wed Oct 05, 2005 4:25 pm

Thanks, I hope so too.
Actually, Vikto just wrote me back and confirmed what I was kind of afraid of - that I'd have to compile the source code as it's not built into the Nut suite. Normally I have no trouble compiling anything, but I've not had to compile a suite or segment of a suite since I embraced Gentoo, since I just use emerge. No big deal I guess, I just need to take my time and make sure I do everything right. I'm pretty sure I'm going to have to rewrite some of the paths of the include's.
Did you go throught that? Having to compile "energizerups.c"?

josh · Post by **josh** » Sun Feb 19, 2006 5:37 am

Sorry to rehash this.

saghi: If you add "usb" to your USE flags for nut then it will compile energizerups (which is the driver you need).

I'm trying to get my ER-OF800 UPS working with linux. Everything seems kosher but it just doesn't create the device or I just don't know where it is. When I plug it in it shows up in /proc/bus/usb/devices as it should. But it says this in /var/log/messages

Code: Select all

Feb 18 22:13:49 lotuseaters HID device not claimed by input or hiddev

How could I make one of them take responsibility? I'm thinking that I"m missing a usb kernel option Or I have one too many. I've been over the kernel Options about a billion times. I have CONFIG_BLK_DEV_UB unset and I also have CONFIG_INPUT_HIDINPUT unset but I have the rest of the appropriate usb options as per the website. In fact, that is all I have since this is the only usb device I use. Have you gotten anywhere with this saghi?

josh · Post by **josh** » Sun Feb 19, 2006 3:33 pm

Duh. Forgot to enable /dev/hiddev support. Now the device shows up as /dev/usb/hiddev0 But it still complains that it can't 'talk' to it. If I use the qups tool from V Toth's website then it will seemingly "work" but I get no output. But there is no error either. Example:

Code: Select all

lotuseaters eups # ./qups /dev/usb/hiddev0 I

lotuseaters eups # ./qups /dev/psaux I
Error in SUSAGE

apcupsd usb problem [CLOSED]

SOLVED (for me, anyway)

I'm almost there, but...

Thanks