Date: Fri, 4 Apr 2014 18:14:04 +0200 From: Polytropon <freebsd@edvax.de> To: "Bailey, Jeremy" <jbailey@Munciepower.com> Cc: "freebsd-questions@FreeBSD.org" <freebsd-questions@FreeBSD.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140404181404.110c956d.freebsd>