From owner-freebsd-usb@FreeBSD.ORG Sun Dec 21 20:23:40 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5CF25D0 for ; Sun, 21 Dec 2014 20:23:40 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (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 1842F21CB for ; Sun, 21 Dec 2014 20:23:39 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (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 6F5DE1FE022; Sun, 21 Dec 2014 21:23:36 +0100 (CET) Message-ID: <54972C6E.2080906@selasky.org> Date: Sun, 21 Dec 2014 21:24:14 +0100 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Randall Fox , Anish Mistry Subject: Re: urndis and umodem device collision for ue device References: <1580934.Kkj0kKdA3z@bigguy.am-productions.biz> <1993304.2n7h1o4Guv@bigguy.am-productions.biz> <548EABCA.7090908@selasky.org> <2834715.Xnaz94KKIN@bigguy.am-productions.biz> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-usb@freebsd.org X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Dec 2014 20:23:40 -0000 On 12/21/14 21:21, Randall Fox wrote: >> Hi, >> >> The following patches should fix your problem: >> >> https://svnweb.freebsd.org/changeset/base/275790 >> https://svnweb.freebsd.org/changeset/base/275791 >> >> --HPS > > > I finally was able to apply this, and it did not work for me. I am still > getting the disconnect messages. It seems to have worked for someone else > with a different (but similar) Tripp Lite unit. He had the same issue as I > did, but this seemed to have fixed it. > > Were you able to get the ID values from my data? Or did you pull them from > another source? If it was another source, how can I get a trace so I can > get you the needed ID values? > > Thanks Hi, Did you update /etc/devd/usb.conf, install new kernel and reboot your system? --HPS