From owner-freebsd-questions@FreeBSD.ORG Sat Sep 3 23:42:39 2005 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FDA616A41F for ; Sat, 3 Sep 2005 23:42:39 +0000 (GMT) (envelope-from wmoran@potentialtech.com) Received: from internet.potentialtech.com (internet.potentialtech.com [66.167.251.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA2EE43D45 for ; Sat, 3 Sep 2005 23:42:38 +0000 (GMT) (envelope-from wmoran@potentialtech.com) Received: from localhost (24-53-250-148.pittpa.adelphia.net [24.53.250.148]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by internet.potentialtech.com (Postfix) with ESMTP id 2440169A4C for ; Sat, 3 Sep 2005 19:42:38 -0400 (EDT) Date: Sat, 3 Sep 2005 19:42:36 -0400 From: Bill Moran To: questions@freebsd.org Message-Id: <20050903194236.7da253ba.wmoran@potentialtech.com> Organization: Potential Technologies X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: USB-RS232 adapter in FreeBSD 5? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2005 23:42:39 -0000 I've got a USB -> RS232 adapter I'm trying to get working on 5.3-RELEASE. I've seen a lot of comments about these kind of things that seem to indicate that they can be used (I occasionally have needs to use this lappy as a serial console, and I'd like to use it to demonstrate a serial barcode scanner that we have - normally, tip would work great for this, but the laptop doesn't have a native RS-232 port). Anyway, I get the impression that I'm missing some early, basic steps to get this working. dmesg shows: ugen0: Prolific Technology Inc. USB-Serial Controller, rev 1.10/3.00, addr 2 But neither tip nor cu seems to talk to ugen0 very well. Other posts I've seen seem to indicate that I need to be talking to a ucom0 device, but I see nothing like that in /dev. Is there something missing from my kernel? I haven't been able to find any reference to ucom in the GENERIC or NOTES files. Any advice/pointers is welcome. TIA. -- Bill Moran Potential Technologies http://www.potentialtech.com