From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 12:19:16 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF0FB16A4CE for ; Tue, 18 Jan 2005 12:19:16 +0000 (GMT) Received: from bsd.dino.sk (bsd.dino.sk [213.215.72.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB15543D3F for ; Tue, 18 Jan 2005 12:19:15 +0000 (GMT) (envelope-from bsd@dino.sk) Received: from [213.215.72.59] ([213.215.72.59]) by bsd.dino.sk with esmtp; Tue, 18 Jan 2005 13:19:10 +0100 id 000000F4.41ECFEBF.00000E0F From: Milan Obuch To: freebsd-current@freebsd.org Date: Tue, 18 Jan 2005 13:18:54 +0100 User-Agent: KMail/1.7.2 References: <200501181306.49120.emanuel.strobl@gmx.net> In-Reply-To: <200501181306.49120.emanuel.strobl@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501181318.57177.bsd@dino.sk> Subject: Re: strange ucom (uplcom) error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 12:19:17 -0000 On Tuesday 18 January 2005 13:06, Emanuel Strobl wrote: > Dear experts, > > I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working the > other one not (I hate to say it but both are working under win). > > The not working (more expensive) one gets recognized as ucom0 and I have > ucom0, also I can receive signal but not transmit. > > When I connect the (more expensive) adopter to a serial console (FreeBSD > comconsole) I can see all kernel messages but I can't type any charecter > when I see the login. If I change to the cheaper adopter everything is > working fine. I compared 'stty -a -f /dev/ucom0' and both adaptors show the > same settings. > > I'm using tip (ucom0:dv=/dev/ucom0:br#115200:pa=none:) on RELENG_5 (from > this weekend) > Hi, I am by no means an expert here, just couple of my observations. I have two Prolific2303 adapters and they exhibit both some peculiarity. I use minicom for serial communication. With my pl2303 based adapters, I must first start minicom, change something (toggle harware flow control as an example) and after that, I can use the adapter. Without this, no characters are seen, however, what I type is send to the other side. There is something incorrect in USB stack maybe, but with this workaround I can live with this. I have no possibility to investigate further, if someone, however, makes a path to be tested, I can do it. Regards, Milan