From: David Niklas <Hgntkwis@vfemail.net>
To: linux-usb@vger.kernel.org
Cc: stern@rowland.harvard.edu, linux-input@vger.kernel.org,
<linux-kernel@vger.kernel.org>
Subject: Re: I need advice with UPS connection. (ping)
Date: Sun, 14 Nov 2021 22:02:22 -0500 [thread overview]
Message-ID: <20211114220222.31755871@Zen-II-x12.niklas.com> (raw)
In-Reply-To: <20211114211435.GA87082@rowland.harvard.edu>
[-- Attachment #1: Type: text/plain, Size: 3570 bytes --]
On Sun, 14 Nov 2021 16:14:35 -0500
stern@rowland.harvard.edu wrote:
> On Sun, Nov 14, 2021 at 02:48:42PM -0500, David Niklas wrote:
> > Hello,
> >
> > Almost 1 year ago to the date I posted a question regarding
> > connecting my UPS to my PC (look for the same subject -ping). The
> > input subsystem maintainers, Jiri Kosina or Ben Tissoires were asked
> > to get back to me. No one ever did though.
> >
> > Now my UPS is *not* working correctly, and I'd really really like to
> > be able to speak to it with my PC so I can (hopefully) figure out
> > what's wrong with it.
> >
> > I'm running Linux Kernel 5.15.X on a Devuan (Debian) system. I
> > connected my UPS (OPTI-UPS Thunder Shield TS2250B) via USB cable and
> > got (almost the same as last time...):
> > [ 4236.165138] usb 3-2: new low-speed USB device number 2 using
> > xhci_hcd [ 4236.325178] usb 3-2: New USB device found, idVendor=0d9f,
> > idProduct=0004, bcdDevice= 0.02 [ 4236.325183] usb 3-2: New USB
> > device strings: Mfr=3, Product=1, SerialNumber=2 [ 4236.325185] usb
> > 3-2: Product: HID UPS Battery [ 4236.325187] usb 3-2: Manufacturer:
> > POWERCOM Co.,LTD [ 4236.325188] usb 3-2: SerialNumber: 004-0D9F-000
> > [ 4236.423210] hid-generic 0003:0D9F:0004.000B: hiddev3,hidraw8: USB
> > HID v1.00 Device [POWERCOM Co.,LTD HID UPS Battery] on
> > usb-0000:11:00.3-2/input0 [ 4239.842223] usb 3-2: USB disconnect,
> > device number 2 [ 4242.485126] usb 3-2: new low-speed USB device
> > number 3 using xhci_hcd [ 4242.645075] usb 3-2: New USB device found,
> > idVendor=0d9f, idProduct=0004, bcdDevice= 0.02 [ 4242.645080] usb
> > 3-2: New USB device strings: Mfr=3, Product=1, SerialNumber=2
> > [ 4242.645082] usb 3-2: Product: HID UPS Battery [ 4242.645084] usb
> > 3-2: Manufacturer: POWERCOM Co.,LTD [ 4242.645085] usb 3-2:
> > SerialNumber: 004-0D9F-000 [ 4242.727148] hid-generic
> > 0003:0D9F:0004.000C: hiddev3,hidraw8: USB HID v1.00 Device [POWERCOM
> > Co.,LTD HID UPS Battery] on usb-0000:11:00.3-2/input0 [ 4246.135926]
> > usb 3-2: USB disconnect, device number 3 [ 4248.781839] usb 3-2: new
> > low-speed USB device number 4 using xhci_hcd [ 4248.942099] usb 3-2:
> > New USB device found, idVendor=0d9f, idProduct=0004, bcdDevice= 0.02
> > [ 4248.942104] usb 3-2: New USB device strings: Mfr=3, Product=1,
> > SerialNumber=2 [ 4248.942106] usb 3-2: Product: HID UPS Battery
> > [ 4248.942108] usb 3-2: Manufacturer: POWERCOM Co.,LTD [ 4248.942109]
> > usb 3-2: SerialNumber: 004-0D9F-000 [ 4249.031166] hid-generic
> > 0003:0D9F:0004.000D: hiddev3,hidraw8: USB HID v1.00 Device [POWERCOM
> > Co.,LTD HID UPS Battery] on usb-0000:11:00.3-2/input0 [ 4252.511996]
> > usb 3-2: USB disconnect, device number 4 ...
> >
> > I'd appreciate any advice trying to get my UPS to stay connected and
> > not spam the kernel log. I'd like to have nut or apcupsd talk to it.
>
> It would help to see the details of the communication between the
> computer and the UPS. You can collect a usbmon trace by running (as
> superuser):
>
> cat /sys/kernel/debug/usb/usbmon/3u >mon.txt
>
> before plugging in the UPS cable. (The 3 comes from the bus number of
> the USB port in the log above.) Kill the process after the cable has
> been plugged in long enough for a couple of these disconnect messages
> to appear, and post the output file to the mailing list.
>
> Alan Stern
>
Attached is the info.
In case someone doesn't realize, I'm subscribed to the linux-kernel ML,
but not input or usb. Please CC me if you don't want to spam the LKML.
Thanks for the timely response,
David
[-- Attachment #2: mon.txt.bz2 --]
[-- Type: application/x-bzip, Size: 1990 bytes --]
next prev parent reply other threads:[~2021-11-15 3:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 3:00 I need advice with UPS connection David Niklas
2020-11-10 21:55 ` Alan Stern
2020-11-11 1:17 ` Hgntkwis
2020-11-11 15:42 ` Alan Stern
2021-11-14 19:48 ` I need advice with UPS connection. (ping) David Niklas
2021-11-14 21:14 ` Alan Stern
2021-11-15 3:02 ` David Niklas [this message]
2021-11-15 16:09 ` Alan Stern
2021-11-15 22:08 ` David Niklas
2021-11-17 5:23 ` David Niklas
2021-11-17 17:08 ` Alan Stern
2021-11-19 22:19 ` David Niklas
2021-11-21 2:54 ` Alan Stern
2021-11-22 16:25 ` David Niklas
2021-11-22 20:13 ` Alan Stern
2021-11-22 21:29 ` Filipe Laíns
2021-11-23 16:33 ` Benjamin Tissoires
2021-11-24 3:12 ` David Niklas
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=20211114220222.31755871@Zen-II-x12.niklas.com \
--to=hgntkwis@vfemail.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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