search for: usb_do_request

...blazer_usb NAMI "/dev/ugen0.2" 67611 blazer_usb RET open 5 67611 blazer_usb CALL ioctl(0x5,USB_GET_PLUGTIME,0x7fffffffcc2c) 67611 blazer_usb RET ioctl 0 67611 blazer_usb CALL ioctl(0x5,USB_FS_INIT,0x7fffffffcbb0) 67611 blazer_usb RET ioctl 0 67611 blazer_usb CALL ioctl(0x4,USB_DO_REQUEST,0x7fffffffcab0) 67611 blazer_usb RET ioctl 0 67611 blazer_usb CALL ioctl(0x4,USB_DO_REQUEST,0x7fffffffcab0) 67611 blazer_usb RET ioctl 0 67611 blazer_usb CALL ioctl(0x4,USB_DO_REQUEST,0x7fffffffcab0) 67611 blazer_usb RET ioctl 0 67611 blazer_usb CALL ioctl(0x4,USB_DO_REQUEST,0x7fffff...

...x7fffffffd2a0,0x35) > 67611 blazer_usb GIO fd 2 wrote 53 bytes > "read: (229.6 219.5 220.0 021 49.7 2.25 18.5 00000001 > " Here's the strange part: the driver successfully queried the UPS once, and got a valid string back. > 67611 blazer_usb CALL ioctl(0x4,USB_DO_REQUEST,0x7fffffffe030) > 67611 blazer_usb RET ioctl -1 errno 5 Input/output error However, this part indicates that there is a disconnect between the NUT driver (which printed "Permissions problem" due to an EPERM return code somewhere), and the kernel driver, which returned EIO. Sadly, a...