From: David Ford <david+cert@blue-labs.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
apcupsd-devel@apcupsd.org
Subject: APC USB ups, Back-UPS ES series, 2.5.68
Date: Fri, 02 May 2003 23:04:21 -0400 [thread overview]
Message-ID: <3EB331B5.4080306@blue-labs.org> (raw)
(Please cc: me on reply)
I'm wanting to get this new toy up and running. I've installed apcupsd,
but it doesn't want to work well with my kernel (2.5.68) or somewhat.
When apcupsd tries to open the hiddev, open() gets an ENODEV. Is
apcupsd doing something wrong or is 2.5.68 doing something wrong?
~# dmesg
hub 1-0:0: debounce: port 1: delay 100ms stable 4 status 0x301
hub 1-0:0: new USB device on port 1, assigned address 4
usb 1-1: new device strings: Mfr=3, Product=1, SerialNumber=2
usb 1-1: Product: Back-UPS ES 350 FW:800.e3.D USB FW:e3
usb 1-1: Manufacturer: APC
usb 1-1: SerialNumber: AB0238241677
usb 1-1: usb_new_device - registering interface 1-1:0
hid 1-1:0: usb_device_probe
hid 1-1:0: usb_device_probe - got id
drivers/usb/core/file.c: asking for 1 minors, starting at 96
drivers/usb/core/file.c: found a minor chunk free, starting at 96
hiddev96: USB HID v1.10 Device [APC Back-UPS ES 350 FW:800.e3.D USB
FW:e3] on usb-00:07.2-1
~# ls -l /dev/usb/hid
total 0
crw-r--r-- 1 root root 180, 192 Dec 31 1969 hiddev96
crw-r--r-- 1 root root 180, 193 Dec 31 1969 hiddev97
~# strace -f apcupsd (trimmed)
[...]
open("/dev/usb/hid/hiddev95", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("/dev/usb/hid/hiddev96", O_RDONLY) = -1 ENODEV (No such device)
open("/dev/usb/hid/hiddev97", O_RDONLY) = -1 ENODEV (No such device)
open("/dev/usb/hid/hiddev98", O_RDONLY) = -1 ENOENT (No such file or
directory)
write(2, "Couldn\'t find UPS device or no p"..., 43Couldn't find UPS
device or no permission.
) = 43
_exit(1) = ?
ref: http://www.sibbald.com/apcupsd/manual/usb.html
apcupsd version: 3.10.5
Linux kernel: 2.5.68
David
p.s. apcupsd needs patched to handle hiddev from 96 on (minor allocated by kernel)
next reply other threads:[~2003-05-03 2:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-03 3:04 David Ford [this message]
2003-05-03 6:36 ` APC USB ups, Back-UPS ES series, 2.5.68 Greg KH
2003-05-03 10:05 ` David Ford
2003-05-06 1:42 ` David Ford
2003-05-06 4:25 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EB331B5.4080306@blue-labs.org \
--to=david+cert@blue-labs.org \
--cc=apcupsd-devel@apcupsd.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).