From owner-freebsd-usb@freebsd.org Mon Sep 3 14:15:08 2018 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EC1A0FEB208 for ; Mon, 3 Sep 2018 14:15:07 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7F324865D7 for ; Mon, 3 Sep 2018 14:15:07 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 16354260104; Mon, 3 Sep 2018 16:15:00 +0200 (CEST) Subject: Re: nut/apc values sparse after update to 11.2 To: =?UTF-8?Q?Gerrit_K=c3=bchn?= Cc: freebsd-usb@FreeBSD.org References: <20180903150854.6bd6052d5c1a8c02e539509d@aei.mpg.de> <20180903160517.e443ef89ce9564c0fec5122d@aei.mpg.de> From: Hans Petter Selasky Message-ID: Date: Mon, 3 Sep 2018 16:14:34 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <20180903160517.e443ef89ce9564c0fec5122d@aei.mpg.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Sep 2018 14:15:08 -0000 On 9/3/18 4:05 PM, Gerrit Kühn wrote: > On Mon, 3 Sep 2018 15:37:18 +0200 Hans Petter Selasky > wrote about Re: nut/apc values sparse after update to 11.2: > >> Did you check the permissions for the USB device? > > Yes, they should be fine: > > --- > # ll /dev/uhid0 > crw-r----- 1 uucp uucp 0xde Sep 3 15:40 /dev/uhid0 > --- > >> Did you try to re-attach the USB device? > > Yes, doesn't change anything: > > --- > # dmesg|grep uhid0 > uhid0 on uhub3 > uhid0: 0/0, rev 2.00/1.06, addr 3> on usbus1 > uhid0: detached > uhid0 on uhub3 > uhid0: 0/0, rev 2.00/1.06, addr 3> on usbus1 > uhid0: detached > uhid0 on uhub3 > uhid0: 0/0, rev 2.00/1.06, addr 3> on usbus1 > --- > >> What does usbconfig output? Does it detect your device? > > Yes, it does (otherwise it wouldn't work at all, I guess?): > > --- > # usbconfig|grep American > ugen1.3: at > usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (2mA) > --- > >> Did you try a 11-stable kernel? > Hi, > No, should I? Running -stable on that machine would be tedious. What does uname -a tell about your current kernel? Some debug options for you: 1) ktrace nut/apc 2) usbdump -i usbus1 -f 3 -s 65536 -vvv --- any ERR= non-zero lines? 3) Have you tried sysutils/apcupsd ? 4) Try booting an 11-stable kernel. --HPS