From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 27 10:29:55 2005 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCA1E16A4CE for ; Thu, 27 Jan 2005 10:29:55 +0000 (GMT) Received: from mail.holtmann.net (coyote.holtmann.net [217.160.111.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 738FF43D54 for ; Thu, 27 Jan 2005 10:29:54 +0000 (GMT) (envelope-from marcel@holtmann.org) Received: from pegasus (pD9FF959F.dip.t-dialin.net [217.255.149.159]) j0RAUhLM017330 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Thu, 27 Jan 2005 11:30:44 +0100 From: Marcel Holtmann To: Rainer Goellner In-Reply-To: <41F8B429.8010504@jabbe.de> References: <41F8B429.8010504@jabbe.de> Content-Type: text/plain Date: Thu, 27 Jan 2005 11:29:48 +0100 Message-Id: <1106821788.28444.68.camel@pegasus> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on coyote.holtmann.net X-Virus-Scanned: ClamAV 0.80/631/Wed Dec 15 15:01:14 2004 clamav-milter version 0.80j on coyote.holtmann.net X-Virus-Status: Clean cc: freebsd-bluetooth@freebsd.org Subject: Re: BlueFRITZ! USB v2.0 is not recognized X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jan 2005 10:29:56 -0000 Hi Rainer, > I'm failing to get my new AVM BlueFRITZ! v2.0 Bluetooth > dongle recognized on a fresh FreeBSD 5.3 installation. > This version of the BlueFRITZ! should be H:2 compliant, > but all I get is a ugen, no ubt. > > USB stuff is built into the kernel; ng_ubt and various > combinations of modules are loaded. A kernel with built > in netgraph doesn't help either. It seems to me anyway, > that the problem lies in a somewhat deeper layer, because > the device class is reported as 0xff. > > Probably this is really a USB question, but I think people > in this group have played around with different types of > Bluetooth dongles rather extensivly ;-) the BlueFRITZ! USB v2.0 is a H:2 device, but it doesn't present itself with the Bluetooth device class. I suggest you add the vendor and product id to the driver like it is done for Linux. Regards Marcel