From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 27 09:28:12 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 6E66D16A4CF for ; Thu, 27 Jan 2005 09:28:12 +0000 (GMT) Received: from natpreptil.rzone.de (natpreptil.rzone.de [81.169.145.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8D4543D46 for ; Thu, 27 Jan 2005 09:28:11 +0000 (GMT) (envelope-from rainer@jabbe.de) Received: from [192.168.1.16] (80-219-4-14.dclient.hispeed.ch [80.219.4.14]) by post.webmailer.de (8.13.1/8.13.1) with ESMTP id j0R9S9pL023879; Thu, 27 Jan 2005 10:28:09 +0100 (MET) Message-ID: <41F8B429.8010504@jabbe.de> Date: Thu, 27 Jan 2005 10:28:09 +0100 From: Rainer Goellner Organization: Arctopile User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050126 X-Accept-Language: de-de, de-ch, de, en MIME-Version: 1.0 To: freebsd-bluetooth@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: 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 09:28:12 -0000 Hi there, 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 ;-) Any hints? Rainer 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 From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 27 12:23:33 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 B8E9316A4CE for ; Thu, 27 Jan 2005 12:23:33 +0000 (GMT) Received: from natsmtp00.rzone.de (natsmtp00.rzone.de [81.169.145.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15A0243D54 for ; Thu, 27 Jan 2005 12:23:31 +0000 (GMT) (envelope-from rainer@jabbe.de) Received: from [192.168.1.16] (80-219-4-14.dclient.hispeed.ch [80.219.4.14]) by post.webmailer.de (8.13.1/8.13.1) with ESMTP id j0RCNS83018417; Thu, 27 Jan 2005 13:23:28 +0100 (MET) Message-ID: <41F8DD3F.9020209@jabbe.de> Date: Thu, 27 Jan 2005 13:23:27 +0100 From: Rainer Goellner Organization: Arctopile User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050126 X-Accept-Language: de-de, de-ch, de, en MIME-Version: 1.0 To: Marcel Holtmann References: <41F8B429.8010504@jabbe.de> <1106821788.28444.68.camel@pegasus> In-Reply-To: <1106821788.28444.68.camel@pegasus> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 12:23:33 -0000 Marcel Holtmann wrote: > >>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. >> > ... > 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. > Could you give me any hint where to look and where to add the ids? BTW, I almost forgot that I had changed USB_MATH(ubt) in sys/netgraph/bluetooth/drivers/utb/ng_ubt.c like this very early during my awkward attempts: ... Static struct usb_devno const ubt_ignored_devices[] = { { 0x057c, 0x3800, 0, 0 } /* This should be the last item in the list */ }; ... Static struct usb_devno const ubt_broken_devices[] = { { 0x057c, 0x3800, 0, 0 } /* This should be the last item in the list */ }; ... AFAIK 0x057c is the vendor id, 0x3800 the device id. Hope that's not what you meant... Rainer From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 27 12:48:36 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 D004816A4CE for ; Thu, 27 Jan 2005 12:48:36 +0000 (GMT) Received: from mail.holtmann.net (coyote.holtmann.net [217.160.111.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49E7143D5D for ; Thu, 27 Jan 2005 12:48:35 +0000 (GMT) (envelope-from marcel@holtmann.org) Received: from pegasus (pD9FF959F.dip.t-dialin.net [217.255.149.159]) j0RCnOLM018528 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Thu, 27 Jan 2005 13:49:25 +0100 From: Marcel Holtmann To: Rainer Goellner In-Reply-To: <41F8DD3F.9020209@jabbe.de> References: <41F8B429.8010504@jabbe.de> <1106821788.28444.68.camel@pegasus> <41F8DD3F.9020209@jabbe.de> Content-Type: text/plain Date: Thu, 27 Jan 2005 13:48:30 +0100 Message-Id: <1106830110.3998.4.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 12:48:36 -0000 Hi Rainer, > > 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. > > > Could you give me any hint where to look and where > to add the ids? > > BTW, I almost forgot that I had changed USB_MATH(ubt) in > sys/netgraph/bluetooth/drivers/utb/ng_ubt.c like this > very early during my awkward attempts: > ... > Static struct usb_devno const ubt_ignored_devices[] = { > { 0x057c, 0x3800, > 0, 0 } /* This should be the last item in the list */ > }; > ... > Static struct usb_devno const ubt_broken_devices[] = { > { 0x057c, 0x3800, > 0, 0 } /* This should be the last item in the list */ > }; > ... > AFAIK 0x057c is the vendor id, 0x3800 the device id. > > Hope that's not what you meant... ask somebody who knows something about FreeBSD ;) Regards Marcel From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 27 13:41:49 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 1EB8516A4CE for ; Thu, 27 Jan 2005 13:41:49 +0000 (GMT) Received: from natsmtp00.rzone.de (natsmtp00.rzone.de [81.169.145.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id 218F443D60 for ; Thu, 27 Jan 2005 13:41:48 +0000 (GMT) (envelope-from rainer@jabbe.de) Received: from [192.168.1.16] (80-219-4-14.dclient.hispeed.ch [80.219.4.14]) by post.webmailer.de (8.13.1/8.13.1) with ESMTP id j0RDfjY4000284; Thu, 27 Jan 2005 14:41:46 +0100 (MET) Message-ID: <41F8EF99.4090200@jabbe.de> Date: Thu, 27 Jan 2005 14:41:45 +0100 From: Rainer Goellner Organization: Arctopile User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050126 X-Accept-Language: de-de, de-ch, de, en MIME-Version: 1.0 To: Marcel Holtmann References: <41F8B429.8010504@jabbe.de> <1106821788.28444.68.camel@pegasus> <41F8DD3F.9020209@jabbe.de> <1106830110.3998.4.camel@pegasus> In-Reply-To: <1106830110.3998.4.camel@pegasus> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 13:41:49 -0000 Marcel Holtmann wrote: > Hi Rainer, > > >>>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. >>> >> >>Could you give me any hint where to look and where >>to add the ids? >> > ... > ask somebody who knows something about FreeBSD ;) > So that's for the FreeBSD part. But what about Linux? Thanks, Rainer From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 27 17:37: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 1488E16A4CF for ; Thu, 27 Jan 2005 17:37:55 +0000 (GMT) Received: from smtp.rol.ru (smtp.rol.ru [194.67.1.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FBE643D41 for ; Thu, 27 Jan 2005 17:37:54 +0000 (GMT) (envelope-from peterp@online.ru) Received: from ts11-a132.Spb.dial.rol.ru ([212.46.200.132]:44036 "EHLO [212.46.200.132]" smtp-auth: "peterp@online.ru" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by gnome10.net.rol.ru with ESMTPSA id S27576AbVA0Rhu (ORCPT ); Thu, 27 Jan 2005 20:37:50 +0300 Message-ID: <41F9273C.8020401@online.ru> Date: Thu, 27 Jan 2005 20:39:08 +0300 From: Petr Panteleyev User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: ru-ru, ru MIME-Version: 1.0 To: freebsd-bluetooth@freebsd.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Subject: LAN over rfcomm_pppd failure with 5.3-STABLE 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 17:37:55 -0000 I'm trying to connect WinXP with 5.3-STABLE via Bluetooth using USB dongles. Specifically, BSD box has dongle that is recognized by the ng_ubt with the following trace: ubt0: SiW SiW, rev 1.10/15.00, addr 2 ubt0: SiW SiW, rev 1.10/15.00, addr 2 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, buffer size=294 I followed Handbook, set up and started rc.bluetooth, hcsecd, sdpd and rfcomm_pppd. My dongle is recognized, pairing from WinXP side goes well. Connection from WinXP to FreeBSD can be always established but when I'm trying to send any data over this connection, it drops very soon with the following diagnostics: Jan 22 21:34:49 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x4, len=124. Queue full Jan 22 21:34:49 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x4, len=13. Queue full Jan 22 21:34:49 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x4, len=124. Queue full Jan 22 21:34:49 elrond last message repeated 3 times Jan 22 21:34:49 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x4, len=13. Queue full Jan 22 21:47:37 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x6, len=124. Queue full Jan 22 21:47:37 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x6, len=13. Queue full Jan 22 21:47:37 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x6, len=124. Queue full Jan 22 21:47:37 elrond last message repeated 2 times Jan 22 21:47:37 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x6, len=13. Queue full Jan 22 21:47:46 elrond kernel: ng_btsocket_rfcomm_session_send: Could not send data to L2CAP socket, error=40 Jan 22 21:47:46 elrond kernel: ng_l2cap_l2ca_receive: ubt0l2cap - unexpected L2CAP data packet. Invalid channel state, cid=75, state=5 I tried to reduce MTU and MRU for ppp down to 512. It helped a bit - connection was alive a bit longer. Then again, connection dropped with the above diagnostics. Just have no idea where to dig further. Regards, Petr