From owner-freebsd-questions@FreeBSD.ORG  Fri Apr  4 16:15:04 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 4624AB48
 for <freebsd-questions@FreeBSD.org>; Fri,  4 Apr 2014 16:15:04 +0000 (UTC)
Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 095ED19C
 for <freebsd-questions@FreeBSD.org>; Fri,  4 Apr 2014 16:15:03 +0000 (UTC)
Received: from r56.edvax.de (port-92-195-177-157.dynamic.qsc.de
 [92.195.177.157])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx02.qsc.de (Postfix) with ESMTPS id 03CD124727;
 Fri,  4 Apr 2014 18:15:01 +0200 (CEST)
Received: from r56.edvax.de (localhost [127.0.0.1])
 by r56.edvax.de (8.14.5/8.14.5) with SMTP id s34GE4tv025172;
 Fri, 4 Apr 2014 18:14:04 +0200 (CEST)
 (envelope-from freebsd@edvax.de)
Date: Fri, 4 Apr 2014 18:14:04 +0200
From: Polytropon <freebsd@edvax.de>
To: "Bailey, Jeremy" <jbailey@Munciepower.com>
Subject: Re: Understanding DMESG
Message-Id: <20140404181404.110c956d.freebsd@edvax.de>
In-Reply-To: <E7FC2BFF7DD48545B2D029459F7A9C7EB357AC@TUL-EXCH.mpp.local>
References: <E7FC2BFF7DD48545B2D029459F7A9C7EB357AC@TUL-EXCH.mpp.local>
Organization: EDVAX
X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: "freebsd-questions@FreeBSD.org" <freebsd-questions@FreeBSD.org>
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Polytropon <freebsd@edvax.de>
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Fri, 04 Apr 2014 16:15:04 -0000

On Tue, 1 Apr 2014 16:55:26 +0000, Bailey, Jeremy wrote:
> Hello,
> 
> I ran the DMESG in terminal and have examined the output.
> I have even been able to locate the device on the output.
> My problem comes in identifying just what the ugenX.y is.
> If you could help me with this that would be great.

A powerful resource of the FreeBSD OS is the immediately
available local documentation. If you find an entry in
dmesg, use "man <entry>" to find out more about it, for
example "man ugen", "man usb", "man kbd" or "man bge".

The ugen devices refer to "USB generic devices". Those
are usually picked up by the approproate driver which
may associate another device entry, for example ulpt
(USB printer), uscanner (USB scanner) or ums (USM mouse).

With the "usbconfig" program, you can identify the 
devices on the system. Use

	# usbconfig -u <unit> -a <addr> dump_device_desc

to find out what ugen<unit>.<addr> is. See "man usbconfig"
for further details.


-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...