On 2/8/2017 2:20 PM, Hans Petter Selasky wrote:
> Hi,
>
> After your device receives the following control endpoint request it
> becomes unrecoverable:
>
>> 13:05:50.860195 usbus0.4
>> SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
>> frame[0] WRITE 8 bytes
>> A1 01 52 03 00 00 03 00
On 2/8/2017 3:09 PM, Hans Petter Selasky wrote:
>
> You can also try connecting the device w/ or w/o a USB HUB.
I tried with a HUB, but it does not make a difference.
---Mike
--
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Inter
On 02/08/17 21:05, Mike Tancsa wrote:
I can try. I dont have any contacts there, but I will bcc' one of the
developers of apcupsd to see what he thinks. I attached the output of
truss and the usbdump to see if that sheds any light on the issue and
why FreeBSD is crashing the device and not Lin
On 2/8/2017 2:20 PM, Hans Petter Selasky wrote:
>
> Hi,
>
> After your device receives the following control endpoint request it
> becomes unrecoverable:
>
>> 13:05:50.860195 usbus0.4
>> SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
>> frame[0] WRITE 8 bytes
>> A1 01 52 03 00 00 03
On 02/08/17 19:08, Mike Tancsa wrote:
On 2/8/2017 12:55 PM, Hans Petter Selasky wrote:
On 02/08/17 18:38, Mike Tancsa wrote:
Hi,
It works without issue on Linux.
What information from usbdump would be helpful from usbdump ?
Hi,
If there are any transaction errors, like non successful USB
On 2/8/2017 12:55 PM, Hans Petter Selasky wrote:
> On 02/08/17 18:38, Mike Tancsa wrote:
>> Hi,
>> It works without issue on Linux.
>> What information from usbdump would be helpful from usbdump ?
>
> Hi,
>
> If there are any transaction errors, like non successful USB transfers.
Hi,
This is
On 02/08/17 18:38, Mike Tancsa wrote:
Hi,
It works without issue on Linux.
What information from usbdump would be helpful from usbdump ?
Hi,
If there are any transaction errors, like non successful USB transfers.
--HPS
___
freebsd-usb@freebs
On 2/8/2017 12:33 PM, Hans Petter Selasky wrote:
> On 01/24/17 18:12, Mike Tancsa wrote:
>> The daemon does attach to it, and it sort of reads some of the info (as
>> before adding the quirk)
>
> Hi,
>
> Does this device work with apcaccess under Linux?
>
> Have you tried contacting the mainta
On 01/24/17 18:12, Mike Tancsa wrote:
The daemon does attach to it, and it sort of reads some of the info (as
before adding the quirk)
Hi,
Does this device work with apcaccess under Linux?
Have you tried contacting the maintainers about this?
usbdump'ing the traffic, from before you attach t
On 1/24/2017 12:03 PM, Hans Petter Selasky wrote:
> On 01/24/17 16:14, Mike Tancsa wrote:
>> Perhaps some sort of USB quirk needs to be added ? Any ideas on how to
>> get things working ? It fails on RELENG8, RELENG_10, and RELENG_11 in
>> the same way. usbconfig dump_device_desc fails as its not
On 01/24/17 16:14, Mike Tancsa wrote:
Perhaps some sort of USB quirk needs to be added ? Any ideas on how to
get things working ? It fails on RELENG8, RELENG_10, and RELENG_11 in
the same way. usbconfig dump_device_desc fails as its not able to get
all the info.
Hi,
Try setting the UQ_NO_STRI
11 matches
Mail list logo
