From owner-freebsd-questions@FreeBSD.ORG  Wed Jan 14 09:54:34 2004
Return-Path: <owner-freebsd-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 9608216A4CE
	for <freebsd-questions@freebsd.org>;
	Wed, 14 Jan 2004 09:54:34 -0800 (PST)
Received: from web11503.mail.yahoo.com (web11503.mail.yahoo.com
	[216.136.172.35])
	by mx1.FreeBSD.org (Postfix) with SMTP id 2984E43D69
	for <freebsd-questions@freebsd.org>;
	Wed, 14 Jan 2004 09:54:33 -0800 (PST)
	(envelope-from bjjbuckley@yahoo.com)
Message-ID: <20040114175433.73435.qmail@web11503.mail.yahoo.com>
Received: from [62.17.145.97] by web11503.mail.yahoo.com via HTTP;
	Wed, 14 Jan 2004 17:54:33 GMT
Date: Wed, 14 Jan 2004 17:54:33 +0000 (GMT)
From: =?iso-8859-1?q?Bryan=20JJ=20Buckley?= <bjjbuckley@yahoo.com>
To: FreeBSD Questions <freebsd-questions@freebsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Subject: Why is a USB modem not a USB modem?
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jan 2004 17:54:34 -0000

Hi,
How do I tell FreeBSD 5.1-RELEASE to recognise my
STMicroelectronics USB Communicator as a umodem, and
not as a ugen? Yes, I do have umodem and ucom both
loaded. I have scoured the umodem(4) and ucom(4) man
pages (which are pretty short) as well as the usb(4)
man page, ugen(4), usbd(4) and usbdevs(4). Actually,
running usbdevs -v just confirmed that the FreeBSD had
apparantly all the information it needed (vendor ID,
product ID, device class, description, etc.) - but it
is still not attaching the right driver!
I've seen this question asked before, but never
answered. Here's hoping...
JJ

________________________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping" 
your friends today! Download Messenger Now 
http://uk.messenger.yahoo.com/download/index.html