From owner-freebsd-bluetooth@FreeBSD.ORG Tue Jul 31 21:59:45 2007 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DECE216A41B for ; Tue, 31 Jul 2007 21:59:45 +0000 (UTC) (envelope-from mihai@duras.ro) Received: from mail.duras.ro (mail.duras.ro [86.105.56.133]) by mx1.freebsd.org (Postfix) with ESMTP id 6262C13C442 for ; Tue, 31 Jul 2007 21:59:45 +0000 (UTC) (envelope-from mihai@duras.ro) Received: from localhost (localhost [127.0.0.1]) by mail.duras.ro (Postfix) with ESMTP id 7A67D28CDF; Wed, 1 Aug 2007 00:59:43 +0300 (EEST) Received: from mail.duras.ro ([127.0.0.1]) by localhost (mail [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01164-06; Wed, 1 Aug 2007 00:59:38 +0300 (EEST) Received: from [86.105.56.194] (ma.plimb.cu.barca.prin.padure.ro [86.105.56.194]) by mail.duras.ro (Postfix) with ESMTP id 9F6739EF5; Wed, 1 Aug 2007 00:59:38 +0300 (EEST) Message-ID: <46AFB0D2.1010302@duras.ro> Date: Wed, 01 Aug 2007 00:59:46 +0300 From: Mihai Tanasescu User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: Maksim Yevmenkin References: <46AE717D.6030409@duras.ro> <46AE8C42.5030107@duras.ro> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (RedHat) at duras.ro Cc: freebsd-bluetooth@freebsd.org Subject: Re: Bluesoleil dongle problems X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jul 2007 21:59:46 -0000 Maksim Yevmenkin wrote: > On 7/30/07, Mihai Tanasescu wrote: > >> Maksim Yevmenkin wrote: >> >>> Hello, >>> >>> >>> >>>> I've just bought a Bluesoleil bluetooth dongle and I'm having problems >>>> with it right from the start. >>>> >>>> >>>> I kldload-ed ng-ubt.ko. >>>> >>>> After plugging the USB dongle in my computer it says: >>>> >>>> ubt0: vendor 0x1131 ISSCBTA, rev 1.10/3.73 addr 2 >>>> ubt0: vendor 0x1131 ISSCBTA, rev 1.10/3.73 addr 2 >>>> ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 >>>> ubt0: Interface1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; >>>> wMaxPacketSize=49; nframes=6, buffer size=294 >>>> ubt_request_complete2: ubt0 - Control request failed. STALLED (17) >>>> ubt_request_complete2: ubt0 - Control request failed. STALLED (17) >>>> ubt_request_complete2: ubt0 - Control request failed. STALLED (17) >>>> >>>> >>> well, this points to usb and/or device itself, not bluetooth. >>> basically the driver is trying to send control request to the device >>> and it stalled. try different usb port and/or try to disable ehci usb >>> and revert back to uhci (or ohci). >>> >>> >>> >>>> a couple of times and then everything stops and no bluetooth device >>>> appears in /dev. >>>> >>>> >>> there won't be any entires in /dev for bluetooth devices. only netgraph nodes. >>> >> I was using UHCI already. >> The error still appears...but I don't quite get it...if I issue: >> > > i see > > >> hccontrol -n ubt0hci inquiry >> >> (like the handbook says) >> >> I can very easily see my mobile phone and my keyboards' bluetooth hub. >> >> I can also use: >> hccontrol -n ubt0hci remote_name_request >> >> and it works..but the error appears 1 or 2 times for each command I issue. >> > > that tells me that bluetooth part works fine, *when* communication > between host (pc) and bluetooth dongle works > > >> What could be causing this ? >> Do I need to set(increase) some sort of a timeout ? >> > > all i can say at this point is that there is seems to be something > wrong with usb part. for whatever reason communication (via usb bus) > between host (pc) and bluetooth dongle is flaky. it is clearly not a > timeout issue, so you can not fix it by changing timeout. > > can you please send > > 1) uname -a > > 2) dmesg output > > 3) usbdevs -dv output with bluetooth dongle attached > > you can also try to use different usb port (if available). if you use > usb hub, try without it. if your dongle has extension usb cable, try > shorter (or no) extension cable. finally, if possible try another > dongle (preferably different brand). > > thanks, > max > Don't shoot but I had some errors in hcsecd.conf and that's why I was getting those control request failures. Now everything works fine and it connects with my phone. I've just spent a couple of hours getting gnokii to work with it, but after disabling the rfcomm option and specifying AT mode everything went on smoothly. Sorry for the trouble and thanks for the help.