search for: usbmon

...n (not that I know of any such users of course) and starts by adding "RUN_AS_USER = nutmon" and then creates this user. Later he discovers that the rpm package already has created a "nut" user and therefore deletes the nutmon user but forgets to update upsmon.conf. In this case usbmon will fail silently to start up, without any clues why. Please add some code to usbmon to output a descriptive error message in this case. BR H?kon L?vdal

Hi Alan, sorry for the journalctl output. I have now done the following:L * boot into 3.17-rc7 * mount the usb stick (recovery completed) * unmount, mount, unmount - just to be sure all is fine * started usbmon capturing on bus 3 * mount the usb stick * suspend to ram * wake up now the stick is "officially" mounted (/proc/mounts) * umount error messages pop up * try to mount more error messages * capture dmesg output * stip usbmon The two files are available here: http://www.preining.info/...

...0.294589 Can't retrieve Report 03: Operation not permitted 0.294601 Path: UPS.BELKINConfig.BELKINConfigApparentPower, Type: Feature, ReportID: 0x03, Offset: 0, Size: 16 0.299576 libusb_get_report: No error .. The change in SVN r2098 triggers the problem. By looking at the usbmon output I see that this device fails to respond to the get_report requests when the request size is 512 bytes. The requests worked correctly when they were using the sizes reported by the device: usbmon get_report() requests from nut-2.4.1 The length of each request matches the response from the de...

Hi Alan, thanks for your answer. > I do not recognize this problem based on your description. Please post > the dmesg log. Here cleaned output of journalctl, removed mainly networkmanager stuff. This is about a wake up after sleep, where before the stick was ok. More details necessary, let me know. Thanks Norbert

...manager stuff. I would have preferred to see the output from dmesg, as I requested. But never mind, there probably isn't enough information in either log. > This is about a wake up after sleep, where before the stick was ok. > > More details necessary, let me know. Please collect a usbmon trace for that bus (bus 3), starting before the suspend and ending after the resume. Alan Stern

...for linux 03. It has 3 candidates for linux, linux-upsilon.tar.gz, centos-upsilon.tar.gz, linux.Z 04. Uncompress & diff & manual installations & tests 05. linux.Z does not have usb support 06. centos is upsilon 2.1.x 08. linux-upsilon is uspilon 3.0 - ok let's go with that 09. Setup usbmon 10. configure upsilon to use usb instead /dev/ttyS1. Not trivial. No documentation, I had to use ltrace to see that it strcmp the device name from the config file with "hid". So "hid" is the USB hurray 11. Collect the usbmon log. Please find it attached. Keep in mind that I brok...

Hello, the appended patch converts the reason of transfer to be human readable. How about adding this variable to the usbmon message when it detects being on battery? Michael ---------------------------------------------------------------------- --- ./drivers/apcsmart.h.orig 2009-12-09 16:52:56.000000000 +0100 +++ ./drivers/apcsmart.h 2009-12-09 16:54:34.000000000 +0100 @@ -98,6 +98,7 @@ #define APC_F_SECONDS 0x100000...

...duct id and vendor id and the very scarce info NUT cannot properly support this UPS. However, in hope that maybe it's a known protocol or it's helpfull anyway, I made usb captures of the windows software that comes with the ups for windows. I did two captures: one with the proc interface to usbmon and one with with wireshark. I have no experience writing drivers, but I can try experimental drivers to help. Kind regards. -------------- next part -------------- A non-text attachment was scrubbed... Name: ups.log Type: text/x-log Size: 6835 bytes Desc: not available URL: <http://lists.aliot...

[please use reply-all when responding - the list does not mangle reply-to headers. thanks!] On Jun 22, 2016, at 4:06 AM, Andr? H?nsel wrote: > > On Mittwoch, 22. Juni 2016 09:21 Andr? wrote: > >> Hi list, >> >> (I think) I understand that in upsmon.conf, the MONITOR line ends with >> "master" or "slave". Basically if it's master it will

On Mon, 29 Sep 2014, Norbert Preining wrote: > Hi Alan, > > sorry for the journalctl output. I have now done the following:L > > * boot into 3.17-rc7 > * mount the usb stick (recovery completed) > * unmount, mount, unmount - just to be sure all is fine > * started usbmon capturing on bus 3 > * mount the usb stick > * suspend to ram > * wake up > now the stick is "officially" mounted (/proc/mounts) > * umount > error messages pop up > * try to mount > more error messages > * capture dmesg output > * stip usbmon > >...

> You could also try adding "-x usb_set_altinterface" to the command line > (or adding it to ups.conf). The lsusb output implies that the only valid > setting is 0 (bAlternateSetting), but it might need to be set explicitly. I checked with -x usb_set_altinterface and it says nut_usb_set_altinterface: usb_set_altinterface() should not be necessary - please email the

...tus=1) $ sudo /usr/sbin/upsdrvctl -DDD start myups Network UPS Tools - UPS driver controller 2.4.1 Starting UPS: myups exec: /lib/nut/usbhid-ups -a myups Network UPS Tools - Generic HID driver 0.34 (2.4.1) USB communication driver 0.31 Using subdriver: EXPLORE HID 0.1 This is all I could get from usbmon, with explore. This is just turning on the driver. I don't know how to cause the UPS to send any more info. $ sudo usbmon -i 6 265b7600 0.695954 S Ci:6:002:0 s 80 06 0300 0000 00ff 255 < 265b7600 0.700413 C Ci:6:002:0 0 4 = 04030904 265b7600 0.700431 S Ci:6:002:0 s 80 06 0301 0409 00ff 255...

...d and the > very scarce info NUT cannot properly support this UPS. However, in hope > that maybe it's a known protocol or it's helpfull anyway, I made usb > captures of the windows software that comes with the ups for windows. I > did two captures: one with the proc interface to usbmon and one with > with wireshark. > I have no experience writing drivers, but I can try experimental drivers > to help. Maybe Dan, the maintainer of the nutdrv_qx driver, has better insight on this, but my uneducated guess is that I don't think it is Megatec/Qx. The logs don't show...

...blkif_init: reqs=64, pages=704, mmap_vstart=0xdf800000 netfront: Initialising virtual ethernet driver. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx Registering block device major 8 ide-floppy driver 0.99.newide usbmon: debugfs is not available usbcore: registered new driver libusual mice: PS/2 mouse device common for all mice NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP established hash table entries: 131072 (order: 8, 1048576 bytes) TCP bind hash table...

...lients from connecting. Can you provide more details about the system? If this is a distributor-provided package, did they link against TCP-wrappers (using /etc/hosts.deny)? It's the Debian (Raspbian) jessie package. Anyway, I'm sorry, I just saw that I had it set to "master" in usbmon.conf. Only then the user has to have "upsmon master" set. However, that made me curious: Is there any situation where I would add a remote (not @localhost) UPS in my upsmon.conf with "master" instead of "slave"?

...?? EOF (3) I did some tests with /lib/nut/usbhid-ups, lsusb and usbhid-dump It doesn't work out of the box. After some investigation, it seems that the GXT3 usb device is a bit susceptible and "crash" after some USB requests. I used wireshark to check at the protocol level (modprobe usbmon before launching wireshark). Here is what i can say : ?- after usb cable plugin, issue an 'lsusb -v' -> after the GET DESCRIPTOR Request DEBUG, the device sends Malformed responses. ?- after usb cable plugin, issue an 'usbhid-ups ... ' -> after the SET INTERFACE Request that s...

Hello all! I've been trying to get my UPS working with my OpenBSD stable box and I haven't had any luck yet. dmesg shows that I have something from Powerware usb0 at uhci0: USB revision 1.0 uhub0 at usb0 "Intel UHCI root hub" rev 1.00/1.00 addr 1 biomask f5fd netmask fffd ttymask ffff ugen0 at uhub0 port 1 "Powerware Powerware UPS" rev 0.20/0.50 addr 2 nut version

...UPS, this is useless but hey, with a upsc MyUPS at localhost. I get the full telemetry dump, in this dump I note that my offdelay and ondelay are not being sent to the UPS. The default values are still there. Pull the plug. Within the poll time, I get the system on battery message. Execute a usbmon -c fsd, to force the shutdown command. After the system has announced it is entering shutdown, I replug in the mains. Now the strangeness begins. I get a USB disconnect message for the USB subsystem, immediately followed by a reconnect message with the same USB port vendor id you name it....

...0 00 00 9.397801 reply[0] = 0x01 -> OB 11.406018 read: (8 bytes) => 01 00 00 00 00 00 00 00 11.406062 reply[0] = 0x01 -> OB 13.406318 read: (8 bytes) => 01 00 00 00 00 -------------- next part -------------- A non-text attachment was scrubbed... Name: 2014-01-12-usbmon-short-timeout.pcapng.gz Type: application/gzip Size: 4346 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140112/97ff5929/attachment.bin>

...ry little about the status of the UPS. This time, I added another capture point, a software running inside the vm (usbsniff), in case for some reason commands sent to the ups where missing. Here are the results (the list would hold large messages): http://www.ariwainer.com.ar/varios/ups/2013-12-21-usbmon-fullcycle.log http://www.ariwainer.com.ar/varios/ups/2013-12-21-usbsniff-fullcycle.log http://www.ariwainer.com.ar/varios/ups/2013-12-21-wireshark-fullcycle.pcapng > Also important are the settings in the UPS monitoring software, such as timeouts, or behavior options for when the power returns....