[Slackbuilds-users] apcupsd (3.14.10) Slackware 14.1 64-bit Won't Start

Thomas Ronayne ronayne.thomas at gmail.com
Sat Dec 7 13:34:26 UTC 2013

Well, it gets stranger.

I looked back though dmesg and did find this:

    [    8.681393] usb 4-1: New USB device found, idVendor=051d,
    [    8.682711] usb 4-1: New USB device strings: Mfr=1, Product=2,
    [    8.683967] usb 4-1: Product: Back-UPS RS 1000G FW:869.L3 .D USB
    [    8.685217] usb 4-1: Manufacturer: American Power Conversion
    [    8.686468] usb 4-1: SerialNumber: 3B1235X07353
    [    8.751187] hidraw: raw HID events driver (C) Jiri Kosina
    [    8.773466] usbcore: registered new interface driver usbhid
    [    8.774819] usbhid: USB HID core driver

Don't know if that makes any sense, but that's all that is there.

I'm going to shut down the server, hook up a laptop and shut down the 
UPS (don't want to do that on a running system). and see if kick 
starting the UPS makes a difference. Pulling the USB cable and plugging 
it back in a different slot didn't do anything; I don't really know if 
unplugging and plugging back it ought to kick a dmesg or not.

Anyway, a little experimenting seems to be in order and I'll let you know.


On 12/06/2013 08:26 PM, Robby Workman wrote:

> Okay, weird.
> I agree that the config file looks correct, and is (in the places
> that matter) identical to mine on Slackware 14.1 x86_64.
> For whatever reason, apcupsd is trying to use /dev/ttyS0 for the
> device node *and* it thinks it's a usb device.  I suspect some
> bad logic in apcupsd somewhere, but I won't swear to it.
> In the meantime, when you plug in the UPS, what do you see in dmesg?
> Here's what I have:
> usb 2-2: new full-speed USB device number 7 using uhci_hcd
> usb 2-2: New USB device found, idVendor=051d, idProduct=0002
> usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> usb 2-2: Product: Back-UPS RS 1000G FW:868.L3 .D USB FW:L3
> usb 2-2: Manufacturer: American Power Conversion
> usb 2-2: SerialNumber: 3B1225X20592
> hid-generic 0003:051D:0002.0005: hiddev0,hidraw0: USB HID v1.00 Device [American Power Conversion Back-UPS RS 1000G FW:868.L3 .D USB FW:L3 ] on usb-0000:00:1d.0-2/input0
> Assuming you only have one UPS, and you see something similar to me,
> you can possibly specify /dev/hidraw0 as the DEVICE parameter in
> apcupsd.conf to make it work.  Before I was aware of the autodetection
> capability (or perhaps it didn't exist yet?), I recall having put
> /dev/hiddev0 in my config file (no idea why hiddev0 doesn't exist now
> though).
> All that said, this is perhaps worth mailing the apcupsd list
> <http://lists.sourceforge.net/lists/listinfo/apcupsd-users>
> and see if anyone has any ideas.  Go ahead and attach dmesg output
> from when it's plugged in and your config file.
> CC me too if you don't mind.
> -RW

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20131207/c418da0e/attachment.html>

More information about the SlackBuilds-users mailing list