Date: Thu, 1 Nov 2018 23:59:46 +0300 From: "Andrey V. Elsukov" <bu7cher@yandex.ru> To: Mike Andrews <mandrews@bit0.com>, Hans Petter Selasky <hps@selasky.org> Cc: freebsd-usb@freebsd.org Subject: Re: umodem0, Cisco USB serial console, and quirks Message-ID: <33f3a1f8-69d1-9240-6381-8a851beb97d0@yandex.ru> In-Reply-To: <alpine.BSF.2.21.1709262210180.33243@beast.int.bit0.com> References: <alpine.BSF.2.21.1709191021260.34953@beast.int.bit0.com> <d9dbef0b-c22e-c7ea-34a2-f36e9e768745@selasky.org> <alpine.BSF.2.21.1709191205280.1218@beast.int.bit0.com> <0c4022f3-bd21-49b5-cadd-daeb9f1f3081@selasky.org> <alpine.BSF.2.21.1709262210180.33243@beast.int.bit0.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --H98m3bURjF1BEcLhZT7wk4LbICgINUQS9 Content-Type: multipart/mixed; boundary="ZvvDEN1zlTUeIxFPQD0hRvcRRp9V6Nq6e"; protected-headers="v1" From: "Andrey V. Elsukov" <bu7cher@yandex.ru> To: Mike Andrews <mandrews@bit0.com>, Hans Petter Selasky <hps@selasky.org> Cc: freebsd-usb@freebsd.org Message-ID: <33f3a1f8-69d1-9240-6381-8a851beb97d0@yandex.ru> Subject: Re: umodem0, Cisco USB serial console, and quirks References: <alpine.BSF.2.21.1709191021260.34953@beast.int.bit0.com> <d9dbef0b-c22e-c7ea-34a2-f36e9e768745@selasky.org> <alpine.BSF.2.21.1709191205280.1218@beast.int.bit0.com> <0c4022f3-bd21-49b5-cadd-daeb9f1f3081@selasky.org> <alpine.BSF.2.21.1709262210180.33243@beast.int.bit0.com> In-Reply-To: <alpine.BSF.2.21.1709262210180.33243@beast.int.bit0.com> --ZvvDEN1zlTUeIxFPQD0hRvcRRp9V6Nq6e Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable 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. >=20 > Took me a few days to get around to getting usbmon going on Linux.=C2=A0= The > verbose dump is too large for the list, so: >=20 > =C2=A0=C2=A0 https://www.bit0.com/tmp/usbmon-ciscoasa-verbose.txt > =C2=A0=C2=A0 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-conso= le-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. --=20 WBR, Andrey V. Elsukov --ZvvDEN1zlTUeIxFPQD0hRvcRRp9V6Nq6e-- --H98m3bURjF1BEcLhZT7wk4LbICgINUQS9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlvbaUIACgkQAcXqBBDI oXrVdgf/SWqNx9nlw9Eqh7gNdlw27xOKdJKb05aIgMHq/963CLkgnDv01ak0jG2j xdw+hVvm7CVJpFKvm9b/6Yfz77a7ef97N3RtBZi9TG2JJDzvf3Mz1g0uyS1tWTlX +pZ8f04y4GDrmBFO2O2Rx98Snq683wGFoI6DFgxXz/TeDZ0IuK9RvhOC3rknVz8Y GT4NEeFr8dORSURNuwiThevyQ2pBfGdvI+wUVFGJUMZNYRyaZRk2pyKwpjGRuz1s Mjpu0xO6dzHx3l8WhlBxmgElRuHNobr8b/5wwBlSU7YkUP2EJux7hJYdPU2Q3qEs eJXfnGH9ySnkncou4PcStbjK8uk5wQ== =YGVO -----END PGP SIGNATURE----- --H98m3bURjF1BEcLhZT7wk4LbICgINUQS9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?33f3a1f8-69d1-9240-6381-8a851beb97d0>