From owner-freebsd-usb@freebsd.org Fri Nov 2 08:46:09 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 476F510EDC3A for ; Fri, 2 Nov 2018 08:46:09 +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 DB93D7D429 for ; Fri, 2 Nov 2018 08:46:08 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [178.17.145.230]) (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 674F426019D; Fri, 2 Nov 2018 09:46:06 +0100 (CET) Subject: Re: umodem0, Cisco USB serial console, and quirks To: Mike Andrews , "Andrey V. Elsukov" Cc: freebsd-usb@freebsd.org References: <0c4022f3-bd21-49b5-cadd-daeb9f1f3081@selasky.org> <33f3a1f8-69d1-9240-6381-8a851beb97d0@yandex.ru> <18d57cbe-1235-aedf-45e6-e36b495ca1eb@bit0.com> From: Hans Petter Selasky Message-ID: <15cff2a5-021f-49e5-b287-37a14a9321b3@selasky.org> Date: Fri, 2 Nov 2018 09:45:35 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: <18d57cbe-1235-aedf-45e6-e36b495ca1eb@bit0.com> 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.29 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2018 08:46:09 -0000 On 11/2/18 1:01 AM, Mike Andrews wrote: > On 11/1/18 4:59 PM, Andrey V. Elsukov wrote: > >> On 27.09.2017 05:11, Mike Andrews wrote: >>>> This is the USB read transfer. The other side is not returning any >>>> data, so neither is "cu" printing anything. Maybe you can try to get a >>>> similar trace from the system where it works? >>>> >>>> Looks to me like some kind of protocol error, that the Cisco USB >>>> serial console needs some kind of activation. >>> Took me a few days to get around to getting usbmon going on Linux.  The >>> verbose dump is too large for the list, so: >>> >>>     https://www.bit0.com/tmp/usbmon-ciscoasa-verbose.txt >>>     https://www.bit0.com/tmp/usbmon-ciscoasa.txt >> Hi, >> >> did you find some solution? It seems this device still doesn't work with >> recent FreeBSD. >> I found how it should work on linux: >> https://community.cisco.com/t5/network-architecture-documents/cisco-console-connection-via-usb-serial/ta-p/3163540 >> >> >> And it seems in Linux it is handled by generic CDC ACM driver without >> any quirks. So, I think the problem is with our umodem(4) or ucom(4) >> driver. >> > No, I didn't. > > The usbmon dumps above are still there, and if someone can suggest > anything else I can do to help, lemme know. > Hi, Are there any errors printed in dmesg for this device? What does "usbconfig -d X.Y dump_device_desc dump_curr_config_desc" where X.Y are numbers after ugenX.Y, output? --HPS