From owner-freebsd-bluetooth@FreeBSD.ORG Tue Jan 4 21:54:50 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 A8DD716A4CE for ; Tue, 4 Jan 2005 21:54:50 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 418D343D46 for ; Tue, 4 Jan 2005 21:54:50 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45])j04LshLk001868; Tue, 4 Jan 2005 15:54:43 -0600 Received: from s228130hz1ew17.apptix-01.savvis.net ([10.146.4.29]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Tue, 4 Jan 2005 15:54:34 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew17.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Tue, 4 Jan 2005 15:54:12 -0600 Message-ID: <41DB1084.2090405@savvis.net> Date: Tue, 04 Jan 2005 13:54:12 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Arne Schwabe , Vladimir Grebenschikov , Yann Berthier References: <1100552998.1098.5.camel@localhost> <419B8353.7040908@savvis.net> <419B9EF8.2090401@savvis.net> <1103269957.974.7.camel@localhost> <41C32471.2050805@savvis.net> <866530fusa.fsf@kamino.rfc1149.org> In-Reply-To: <866530fusa.fsf@kamino.rfc1149.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 04 Jan 2005 21:54:13.0051 (UTC) FILETIME=[ED7478B0:01C4F2A7] X-ECS-MailScanner: No virus is found cc: bluetooth@freebsd.org Subject: Re: Bluetooth mouse 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: Tue, 04 Jan 2005 21:54:50 -0000 Hi Guys, sorry for the delay :) i've trying to troubleshoot the problem with Logitech MX900 bluetooth mouse (invalid psm for hid-interrupt channel) and have been looking at all dumps you guys sent to me. here is what i found so far. 1) according to the dumps the mouse advertises correct psm, i.e. 0x13 2) bthidcontrol(8) _should_ work just fine, but it _does_not_. for whatever reason it gets wrong psm (0x25). let me just ask one more question: did you guys set any gcc optimization flags? anything that is *not* default? bottom line: the problem can be either in bthidcontrol(8) or sdp(3) library. i can not reproduce the problem here, so would anyone consider giving me remote access to your box and mouse for a few hours/days? thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Jan 5 11:01:56 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 1987116A4CE for ; Wed, 5 Jan 2005 11:01:56 +0000 (GMT) Received: from psismtp5.vodafone.es (back.vodafone.es [212.73.32.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 174F443D46 for ; Wed, 5 Jan 2005 11:01:55 +0000 (GMT) (envelope-from jjess@freebsd.polarhome.com) Received: from 212-166-158-3.red-acceso.airtel.net ([212.166.158.3]) by psismtp5.vodafone.es (ESMTP service) with ESMTP id I9UBZ400.CX3 for ; Wed, 5 Jan 2005 12:01:52 +0100 From: Jes To: freebsd-bluetooth@freebsd.org User-Agent: KMail/1.7 MIME-Version: 1.0 Content-Disposition: inline Date: Wed, 5 Jan 2005 12:01:22 +0100 Message-Id: <200501051201.23222.jjess@freebsd.polarhome.com> Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Subject: obexapp-1.4.2 and motorola E1000 X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jjess@freebsd.polarhome.com List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jan 2005 11:01:56 -0000 Hello: I have problems to browse the file system in a Motorola E1000. I've just updated obexapp to 1.4.2 but the problem remains. No problems to do OPUSH and connect with PPP but when I do: obexapp -a e1000_address -f -C FTRN I get connected but I when type 'ls' I get any response and I have to type 'CTRL+C' to quit. If I type 'cd' obexapp answer for the remote directory but what directory ? A capture from an xterm: ======================================= bash-2.05b$ obexapp -a e1000 -f -C FTRN obex> ls ^C bash-2.05b$ obexapp -a e1000 -f -C FTRN obex> help CApability, CD, DElete, DIsconnect, Empty, GET, GETDefault, Ls, Mkdir, Put? obex> ca ^C bash-2.05b$ obexapp -a e1000 -f -C FTRN bash-2.05b$ obexapp -a e1000 -f -C FTRN obex> cd cd: remote directory> MMC ^C bash-2.05b$ obexapp -a e1000 -f -C FTRN obex> cd cd: remote directory> MMC(Removable) ======================================= One friend of mine can connect with Linux Slackware 10 using Konqueror pointed to: obex://[e1000_address]:9 and he can navigate .... Nevertheless I can navigate without any problems with a Sony-Ericsson Z600 ... Any idea ? Again, everything ok with OPUSH and PPP (rfcomm_pppd -c -a e1000 -C 1 -l e1000). Thanks Jes From owner-freebsd-bluetooth@FreeBSD.ORG Wed Jan 5 15:22:41 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 5224916A4D9 for ; Wed, 5 Jan 2005 15:22:41 +0000 (GMT) Received: from mx.dada.it (mail2.dada.it [195.110.100.2]) by mx1.FreeBSD.org (Postfix) with SMTP id E336D43D5A for ; Wed, 5 Jan 2005 15:22:39 +0000 (GMT) (envelope-from mad@madpilot.net) Received: (qmail 21351 invoked from network); 5 Jan 2005 15:22:35 -0000 Received: from unknown (HELO madpilot.net) (195.110.114.197) by mail.dada.it with SMTP; 5 Jan 2005 15:22:35 -0000 Received: (qmail 57490 invoked from network); 5 Jan 2005 15:22:37 -0000 Received: from wedge.madpilot.net (192.168.13.11) by 0 with SMTP; 5 Jan 2005 15:22:37 -0000 Received: from wedge.madpilot.net (localhost.madpilot.net [127.0.0.1]) by wedge.madpilot.net (8.13.1/8.12.11) with ESMTP id j05FMbMp083923 for ; Wed, 5 Jan 2005 16:22:37 +0100 (CET) (envelope-from mad@wedge.madpilot.net) Received: (from mad@localhost) by wedge.madpilot.net (8.13.1/8.12.11/Submit) id j05FMbPT083922 for freebsd-bluetooth@freebsd.org; Wed, 5 Jan 2005 16:22:37 +0100 (CET) (envelope-from mad) Date: Wed, 5 Jan 2005 16:22:37 +0100 From: Guido Falsi To: freebsd-bluetooth@freebsd.org Message-ID: <20050105152237.GA83878@wedge.madpilot.net> References: <200501051201.23222.jjess@freebsd.polarhome.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200501051201.23222.jjess@freebsd.polarhome.com> X-Operating-System: FreeBSD 5.3-STABLE X-PGP-Key: http://www.madpilot.net/~mad/PGP-public-key.asc User-Agent: Mutt/1.5.6i Subject: Re: obexapp-1.4.2 and motorola E1000 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: Wed, 05 Jan 2005 15:22:41 -0000 On Wed, Jan 05, 2005 at 12:01:22PM +0100, Jes wrote: > Hello: > > I have problems to browse the file system in a Motorola E1000. I've just > updated obexapp to 1.4.2 but the problem remains. No problems to do OPUSH and > connect with PPP but when I do: > > obexapp -a e1000_address -f -C FTRN > > I get connected but I when type 'ls' I get any response and I have to type > 'CTRL+C' to quit. If I type 'cd' obexapp answer for the remote directory but > what directory ? There's version 1.4.4, but can't be committed right now(there's a ports freeze in force). You could try updating your port using the patch in the PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=75732 -- Guido Falsi From owner-freebsd-bluetooth@FreeBSD.ORG Wed Jan 5 17:59: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 0C5C316A4CE for ; Wed, 5 Jan 2005 17:59:36 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88F2543D1D for ; Wed, 5 Jan 2005 17:59:35 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44])j05Hx76Z029862; Wed, 5 Jan 2005 11:59:07 -0600 Received: from s228130hz1ew03.apptix-01.savvis.net ([10.146.4.28]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 5 Jan 2005 11:59:02 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew03.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 5 Jan 2005 11:58:52 -0600 Message-ID: <41DC2ADA.3060500@savvis.net> Date: Wed, 05 Jan 2005 09:58:50 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Guido Falsi , Jes References: <200501051201.23222.jjess@freebsd.polarhome.com> <20050105152237.GA83878@wedge.madpilot.net> In-Reply-To: <20050105152237.GA83878@wedge.madpilot.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 05 Jan 2005 17:58:52.0544 (UTC) FILETIME=[3763D800:01C4F350] X-ECS-MailScanner: No virus is found cc: freebsd-bluetooth@freebsd.org Subject: Re: obexapp-1.4.2 and motorola E1000 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: Wed, 05 Jan 2005 17:59:36 -0000 Hello, >> I have problems to browse the file system in a Motorola E1000. I've >> just updated obexapp to 1.4.2 but the problem remains. No problems >> to do OPUSH and connect with PPP but when I do: >> >> obexapp -a e1000_address -f -C FTRN >> >> I get connected but I when type 'ls' I get any response and I have >> to type 'CTRL+C' to quit. If I type 'cd' obexapp answer for the >> remote directory but what directory ? i assume you have paired your phone and pc *and* hcsecd(8) is running, right? could you please send me the hcidump(1) binary dump (produced with -w option)? note: hcidump(1) is available at http://www.geocities.com/m_evmenkin/hcidump-1.5.1.tar.gz > There's version 1.4.4, but can't be committed right now(there's a > ports freeze in force). You could try updating your port using the > patch in the PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=75732 just so you know the patch in the pr is *reversed* :) 1.4.4 version has a fix for 'obex connection id' header problem. this version has been tested with motorola v551 phone and known to work. max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Jan 5 20:22: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 9628416A4CE for ; Wed, 5 Jan 2005 20:22:12 +0000 (GMT) Received: from psismtp9.vodafone.es (back.vodafone.es [212.73.32.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9634843D58 for ; Wed, 5 Jan 2005 20:22:11 +0000 (GMT) (envelope-from jjess@freebsd.polarhome.com) Received: from 212-166-255-2.red-acceso.airtel.net ([212.166.255.2]) by psismtp9.vodafone.es (ESMTP service) with ESMTP id I9V1WY00.0EZ for ; Wed, 5 Jan 2005 21:22:10 +0100 From: Jes To: freebsd-bluetooth@freebsd.org Date: Wed, 5 Jan 2005 21:21:51 +0100 User-Agent: KMail/1.7 References: <200501051201.23222.jjess@freebsd.polarhome.com> <20050105151913.GA83113@wedge.madpilot.net> In-Reply-To: <20050105151913.GA83113@wedge.madpilot.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501052121.52011.jjess@freebsd.polarhome.com> Subject: Re: obexapp-1.4.2 and motorola E1000 X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jjess@freebsd.polarhome.com List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jan 2005 20:22:12 -0000 On Wednesday 05 January 2005 16:19, Guido Falsi wrote: > On Wed, Jan 05, 2005 at 12:01:22PM +0100, Jes wrote: > > Hello: > > > > I have problems to browse the file system in a Motorola E1000. I've just > > updated obexapp to 1.4.2 but the problem remains. No problems to do OPUSH > > and connect with PPP but when I do: > > > > obexapp -a e1000_address -f -C FTRN > > > > I get connected but I when type 'ls' I get any response and I have to > > type 'CTRL+C' to quit. If I type 'cd' obexapp answer for the remote > > directory but what directory ? > > There's version 1.4.4, but can't be committed right now(there's a ports > freeze in force). You could try updating your port using the patch in > the PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=75732 Ok, everything is ok with motorola e1000 phone using obexapp 1.4.4. Thanks a lot Guido. If any developer needs some kind of test with this phone or any other feel free to send me a message. Ciao :) Jes From owner-freebsd-bluetooth@FreeBSD.ORG Wed Jan 5 20:30:13 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 AC35716A4CE for ; Wed, 5 Jan 2005 20:30:13 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17E4343D2F for ; Wed, 5 Jan 2005 20:30:11 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44])j05KTwoj008819; Wed, 5 Jan 2005 14:29:58 -0600 Received: from s228130hz1ew03.apptix-01.savvis.net ([10.146.4.28]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 5 Jan 2005 14:29:54 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew03.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 5 Jan 2005 14:29:29 -0600 Message-ID: <41DC4E21.9060100@savvis.net> Date: Wed, 05 Jan 2005 12:29:21 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: jjess@freebsd.polarhome.com References: <200501051201.23222.jjess@freebsd.polarhome.com> <20050105151913.GA83113@wedge.madpilot.net> <200501052121.52011.jjess@freebsd.polarhome.com> In-Reply-To: <200501052121.52011.jjess@freebsd.polarhome.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 05 Jan 2005 20:29:29.0432 (UTC) FILETIME=[41CB8580:01C4F365] X-ECS-MailScanner: No virus is found cc: freebsd-bluetooth@freebsd.org Subject: Re: obexapp-1.4.2 and motorola E1000 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: Wed, 05 Jan 2005 20:30:13 -0000 Jes, >>> I have problems to browse the file system in a Motorola E1000. >>> I've just updated obexapp to 1.4.2 but the problem remains. No >>> problems to do OPUSH and connect with PPP but when I do: >>> >>> obexapp -a e1000_address -f -C FTRN >>> >>> I get connected but I when type 'ls' I get any response and I >>> have to type 'CTRL+C' to quit. If I type 'cd' obexapp answer for >>> the remote directory but what directory ? >> >> There's version 1.4.4, but can't be committed right now(there's a >> ports freeze in force). You could try updating your port using the >> patch in the PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=75732 > > Ok, everything is ok with motorola e1000 phone using obexapp 1.4.4. > > Thanks a lot Guido. > > If any developer needs some kind of test with this phone or any other > feel free to send me a message. do you have access to the phone book via obex ftrn? that is can you *pull entire* phone book out of your phone with obexapp/ftrn? does special 'telecom/' pathnames work for you? could you please send 'sdpcontrol -a e1000_address browse' output? thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Jan 5 20:41: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 F007E16A4CE for ; Wed, 5 Jan 2005 20:41:32 +0000 (GMT) Received: from psismtp7.vodafone.es (back.vodafone.es [212.73.32.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0057743D39 for ; Wed, 5 Jan 2005 20:41:32 +0000 (GMT) (envelope-from jjess@freebsd.polarhome.com) Received: from 212-166-255-2.red-acceso.airtel.net ([212.166.255.2]) by psismtp7.vodafone.es (ESMTP service) with ESMTP id I9V2T401.VAX; Wed, 5 Jan 2005 21:41:28 +0100 From: Jes To: Maksim Yevmenkin Date: Wed, 5 Jan 2005 21:41:14 +0100 User-Agent: KMail/1.7 References: <200501051201.23222.jjess@freebsd.polarhome.com> <200501052121.52011.jjess@freebsd.polarhome.com> <41DC4E21.9060100@savvis.net> In-Reply-To: <41DC4E21.9060100@savvis.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501052141.15375.jjess@freebsd.polarhome.com> cc: freebsd-bluetooth@freebsd.org Subject: Re: obexapp-1.4.2 and motorola E1000 X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jjess@freebsd.polarhome.com List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jan 2005 20:41:33 -0000 On Wednesday 05 January 2005 21:29, Maksim Yevmenkin wrote: > Jes, > > >>> I have problems to browse the file system in a Motorola E1000. > >>> I've just updated obexapp to 1.4.2 but the problem remains. No > >>> problems to do OPUSH and connect with PPP but when I do: > >>> > >>> obexapp -a e1000_address -f -C FTRN > >>> > >>> I get connected but I when type 'ls' I get any response and I > >>> have to type 'CTRL+C' to quit. If I type 'cd' obexapp answer for > >>> the remote directory but what directory ? > >> > >> There's version 1.4.4, but can't be committed right now(there's a > >> ports freeze in force). You could try updating your port using the > >> patch in the PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=75732 > > > > Ok, everything is ok with motorola e1000 phone using obexapp 1.4.4. > > > > Thanks a lot Guido. > > > > If any developer needs some kind of test with this phone or any other > > feel free to send me a message. > > do you have access to the phone book via obex ftrn? that is can you > *pull entire* phone book out of your phone with obexapp/ftrn? does > special 'telecom/' pathnames work for you? could you please send > 'sdpcontrol -a e1000_address browse' output? > > thanks, > max No, my phone is suited for Vodafone so it's ... uhmmmm which is the english word? not full featured maybe ? ... some features are disabled like access to phonebook, send pictures/audio/java applications to another phones or pcs via bluetooth. The only way to "export" files is via ftrn iniated from a pc. Then I only can browse files. The file structure is: /picture /video /audio /MMC(Removable) <-this is the compact flash (optional) /picture /video /audio I think of there is a toolset from Motorola but it costs around 40$ or so.... and I guess it's for windows :( The services: sdpcontrol -a e1000 browse Record Handle: 00000000 Service Class ID List: Service Discovery Server (0x1000) Protocol Descriptor List: L2CAP (0x0100) SDP (0x0001) Bluetooth Profile Descriptor List: Service Discovery Server (0x1000) ver. 1.0 Record Handle: 0x00010001 Service Class ID List: Dial-Up Networking (0x1103) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 1 Bluetooth Profile Descriptor List: Dial-Up Networking (0x1103) ver. 1.0 Record Handle: 0x00010003 Service Class ID List: Headset Audio Gateway (0x1112) Generic Audio (0x1203) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 3 Bluetooth Profile Descriptor List: Headset (0x1108) ver. 1.0 Record Handle: 0x00010007 Service Class ID List: Handsfree Audio Gateway (0x111f) Generic Audio (0x1203) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 7 Bluetooth Profile Descriptor List: Handsfree (0x111e) ver. 1.1 Record Handle: 0x00010008 Service Class ID List: OBEX Object Push (0x1105) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 8 OBEX (0x0008) Bluetooth Profile Descriptor List: OBEX Object Push (0x1105) ver. 1.0 Record Handle: 0x00010009 Service Class ID List: OBEX File Transfer (0x1106) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 9 OBEX (0x0008) Bluetooth Profile Descriptor List: OBEX File Transfer (0x1106) ver. 1.0 Bye Jes From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 6 03:08:15 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 0A40D16A4CE for ; Thu, 6 Jan 2005 03:08:15 +0000 (GMT) Received: from out005.verizon.net (out005pub.verizon.net [206.46.170.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7352843D55 for ; Thu, 6 Jan 2005 03:08:14 +0000 (GMT) (envelope-from Alex.Kovalenko@verizon.net) Received: from RabbitsDen ([70.21.161.195]) by out005.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20050106030813.NHJG28362.out005.verizon.net@RabbitsDen>; Wed, 5 Jan 2005 21:08:13 -0600 From: "Alexandre \"Sunny\" Kovalenko" To: Maksim Yevmenkin In-Reply-To: <41DC2ADA.3060500@savvis.net> References: <200501051201.23222.jjess@freebsd.polarhome.com> <41DC2ADA.3060500@savvis.net> Content-Type: text/plain; charset=iso-8859-5 Date: Wed, 05 Jan 2005 22:07:33 -0500 Message-Id: <1104980853.1050.5.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit X-Authentication-Info: Submitted using SMTP AUTH at out005.verizon.net from [70.21.161.195] at Wed, 5 Jan 2005 21:08:13 -0600 cc: freebsd-bluetooth@freebsd.org Subject: Re: obexapp-1.4.2 and motorola E1000 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, 06 Jan 2005 03:08:15 -0000 On Wed, 2005-01-05 at 09:58 -0800, Maksim Yevmenkin wrote: > just so you know the patch in the pr is *reversed* :) 1.4.4 version has > a fix for 'obex connection id' header problem. this version has been > tested with motorola v551 phone and known to work. > > max Just wanted to confirm that obexapp 1.4.4 works with Motorola V505. No telecom/ stuff, no capabilities object, no default object -- forbidden, but file transfer is OK. obexapp 1.4.2 used to exit without giving me 'obex>' prompt. -- Alexandre "Sunny" Kovalenko (Олександр Коваленко) From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 6 14:06:27 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 0287516A4CE for ; Thu, 6 Jan 2005 14:06:27 +0000 (GMT) Received: from smtp14.wxs.nl (smtp14.wxs.nl [195.121.6.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75E8543D3F for ; Thu, 6 Jan 2005 14:06:26 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from ronald.echteman.nl (ip51cdc5d2.speed.planet.nl [81.205.197.210])2004))freebsd-bluetooth@freebsd.org; Thu, 06 Jan 2005 15:06:25 +0100 (CET) Received: (qmail 9651 invoked from network); Thu, 06 Jan 2005 14:06:23 +0000 Received: from unknown (HELO laptop.thuis.klop.ws) (192.168.1.4) by ronald.echteman.nl with SMTP; Thu, 06 Jan 2005 14:06:23 +0000 Received: (qmail 1366 invoked from network); Thu, 06 Jan 2005 14:06:23 +0000 Received: from localhost.thuis.klop.ws (HELO smtp.local) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; Thu, 06 Jan 2005 14:06:23 +0000 Date: Thu, 06 Jan 2005 15:06:20 +0100 From: Ronald Klop In-reply-to: To: freebsd-bluetooth@freebsd.org Message-id: MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_U4TtL1uBOl/kJOoxcD4r+Q)" User-Agent: Opera M2/7.54u1 (FreeBSD, build 892) References: Subject: Fwd: ng_ubt with Broadcom BCM92035DGL 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, 06 Jan 2005 14:06:27 -0000 --Boundary_(ID_U4TtL1uBOl/kJOoxcD4r+Q) Content-type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 Content-transfer-encoding: 7BIT Sorry, for the cross post, but I just found out about this list. ------- Forwarded message ------- From: "Ronald Klop" To: freebsd-stable@freebsd.org Subject: ng_ubt with Broadcom BCM92035DGL Date: Thu, 06 Jan 2005 12:27:36 +0100 Hello, I have a USB Bluetooth adapter which probes fine as ubt0, but I get errors when trying to use bluetooth. Attached is my verbose dmesg output. I've read the handbook about bluetooth and searched the internet for it. The errors I get are these. # /etc/rc.bluetooth start ubt0 Status: Command disallowed [0xc] # /etc/rc.bluetooth start ubt0 Could not execute command "reset". Operation timed out What information can I provide to resolve this. Or is there a better mailinglist for this? The usb-adapter is the shop-brand of the MyCom shops in The Netherlands. Ronald. -- Ronald Klop, Amsterdam, The Netherlands --Boundary_(ID_U4TtL1uBOl/kJOoxcD4r+Q) Content-type: text/plain; name=dmesg.txt Content-transfer-encoding: 7BIT Content-disposition: attachment; filename=dmesg.txt Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #62: Tue Jan 4 00:33:21 CET 2005 root@guido.thuis.klop.ws:/usr/obj/usr/src/sys/LAPTOP Preloaded elf kernel "/boot/kernel/kernel" at 0xc06dd000. Preloaded elf module "/boot/kernel/linprocfs.ko" at 0xc06dd1a4. Preloaded elf module "/boot/kernel/linux.ko" at 0xc06dd254. Preloaded elf module "/boot/kernel/g_md.ko" at 0xc06dd300. Preloaded elf module "/boot/kernel/if_tun.ko" at 0xc06dd3ac. Preloaded elf module "/boot/kernel/if_ep.ko" at 0xc06dd458. Preloaded elf module "/boot/kernel/elink.ko" at 0xc06dd504. Preloaded elf module "/boot/kernel/snd_ess.ko" at 0xc06dd5b0. Preloaded elf module "/boot/kernel/sound.ko" at 0xc06dd65c. Preloaded elf module "/boot/kernel/snd_sbc.ko" at 0xc06dd708. Preloaded elf module "/boot/kernel/mem.ko" at 0xc06dd7b4. Preloaded elf module "/boot/kernel/io.ko" at 0xc06dd85c. Calibrating clock(s) ... i8254 clock: 1193310 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 266677167 Hz CPU: Pentium II/Pentium II Xeon/Celeron (266.68-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 100622336 (95 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000000826000 - 0x0000000005e15fff, 90112000 bytes (22000 pages) avail memory = 93024256 (88 MB) bios32: Found BIOS32 Service Directory header at 0xc00fa000 bios32: Entry = 0xf0000 (c00f0000) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0x474 pnpbios: Found PnP BIOS data at 0xc00fe2d0 pnpbios: Entry = f0000:4ef2 Rev = 1.0 pnpbios: Event flag at fe2f6 pnpbios: OEM ID b9b0110e Other BIOS signatures found: random: null: mem: Pentium Pro MTRR support enabled io: npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x80000060 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=ae6c0e11) pcibios: BIOS version 2.10 Found $PIR table, 7 entries at 0xc00f0990 PCI-Only Interrupts: 11 Location Bus Device Pin Link IRQs embedded 0 0 A 0x0d 9 10 11 embedded 0 12 A 0x0c 9 10 11 embedded 0 14 A 0x01 9 10 11 embedded 0 16 A 0x19 9 10 11 embedded 0 16 B 0x19 9 10 11 embedded 0 10 A 0x18 9 10 11 slot 11 0 9 A 0x15 9 10 11 slot 11 0 9 B 0x14 9 10 11 slot 11 0 9 C 0x15 9 10 11 slot 11 0 9 D 0x14 9 10 11 slot 12 0 8 A 0x17 9 10 11 slot 12 0 8 B 0x16 9 10 11 slot 12 0 8 C 0x17 9 10 11 slot 12 0 8 D 0x16 9 10 11 apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 pcib0: pcibus 0 on motherboard pir0: on motherboard $PIR: Links after initial probe: Link IRQ Rtd Ref IRQs 0xd 255 N 1 9 10 11 0xc 255 N 1 9 10 11 0x1 255 N 1 9 10 11 0x19 255 N 2 9 10 11 0x18 255 N 1 9 10 11 0x15 255 N 2 9 10 11 0x14 255 N 2 9 10 11 0x17 255 N 2 9 10 11 0x16 255 N 2 9 10 11 $PIR: Found matching pin for 0.12.INTA at func 0: 11 $PIR: Found matching pin for 0.14.INTA at func 1: 255 $PIR: Found matching pin for 0.14.INTA at func 2: 11 $PIR: Links after initial IRQ discovery: Link IRQ Rtd Ref IRQs 0xd 255 N 1 9 10 11 0xc 11 Y 1 9 10 11 0x1 11 Y 1 9 10 11 0x19 255 N 2 9 10 11 0x18 255 N 1 9 10 11 0x15 255 N 2 9 10 11 0x14 255 N 2 9 10 11 0x17 255 N 2 9 10 11 0x16 255 N 2 9 10 11 $PIR: IRQs used by BIOS: 11 $PIR: Interrupt Weights: [ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ] [ 0 0 0 0 0 0 0 0 0 0 0 2 0 0 0 0 ] pci0: on pcib0 pci0: physical bus=0 map[10]: type 3, range 32, base 50000000, size 28, enabled map[14]: type 1, range 32, base 44000000, size 12, enabled found-> vendor=0x0e11, dev=0xae6c, revid=0x01 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x2280, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x0e11, dev=0xae6c, revid=0x01 bus=0, slot=0, func=1 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0003, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) map[10]: type 1, range 32, base 7fffe000, size 12, enabled $PIR: 0:12 INTA routed to irq 11 found-> vendor=0x104c, dev=0xac16, revid=0x02 bus=0, slot=12, func=0 class=06-07-00, hdrtype=0x02, mfdev=1 cmdreg=0x0003, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x42 (1980 ns), mingnt=0xc0 (48000 ns), maxlat=0x03 (750 ns) intpin=a, irq=11 powerspec 1 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base 7ffff000, size 12, enabled $PIR: 0:12 INTA routed to irq 11 found-> vendor=0x104c, dev=0xac16, revid=0x02 bus=0, slot=12, func=1 class=06-07-00, hdrtype=0x02, mfdev=1 cmdreg=0x0003, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x42 (1980 ns), mingnt=0xc0 (48000 ns), maxlat=0x03 (750 ns) intpin=a, irq=11 powerspec 1 supports D0 D1 D2 D3 current D0 found-> vendor=0x0e11, dev=0xae69, revid=0x03 bus=0, slot=14, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0047, statreg=0x2480, cachelnsz=8 (dwords) lattimer=0x42 (1980 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[20]: type 4, range 32, base 00001000, size 4, enabled found-> vendor=0x0e11, dev=0xae33, revid=0x01 bus=0, slot=14, func=1 class=01-01-ea, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 powerspec 1 supports D0 D3 current D0 map[10]: type 1, range 32, base 44080000, size 12, enabled $PIR: 0:14 INTA routed to irq 11 found-> vendor=0x0e11, dev=0xa0f8, revid=0x11 bus=0, slot=14, func=2 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 1 supports D0 D3 current D0 pcib1: at device 0.1 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xf000-0xfff pcib1: memory decode 0x40000000-0x43ffffff pcib1: prefetched decode 0xfff00000-0xfffff pci1: on pcib1 pci1: physical bus=1 map[10]: type 1, range 32, base 40000000, size 26, enabled pcib1: device (null) requested decoded memory range 0x40000000-0x43ffffff found-> vendor=0x5333, dev=0x8c01, revid=0x06 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0003, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x04 (1000 ns), maxlat=0xff (63750 ns) pci1: at device 0.0 (no driver attached) cbb0: mem 0x7fffe000-0x7fffefff irq 11 at device 12.0 on pci0 cbb0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0x7fffe000 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb0: [MPSAFE] cbb0: PCI Configuration space: 0x00: 0xac16104c 0x02100007 0x06070002 0x00824208 0x10: 0x7fffe000 0x020000a0 0x20020200 0xfffff000 0x20: 0x00000000 0xfffff000 0x00000000 0x0000fffc 0x30: 0x00000000 0x0000fffc 0x00000000 0x0740010b 0x40: 0xb0480e11 0x00000001 0x00000000 0x00000000 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 0x80: 0x2044b060 0x00000000 0x09898181 0x00000000 0x90: 0x60640280 0x00000000 0x00000000 0x00000000 0xa0: 0x7e210001 0x00800000 0x00000000 0x00000000 0xb0: 0x00000000 0x00000000 0x00000000 0x00000000 0xc0: 0x00000000 0x00000000 0x00000000 0x00000000 0xd0: 0x00000000 0x00000000 0x00000000 0x00000000 0xe0: 0x00000000 0x00000000 0x00000000 0x00000000 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 cbb1: mem 0x7ffff000-0x7fffffff irq 11 at device 12.1 on pci0 cbb1: Reserved 0x1000 bytes for rid 0x10 type 3 at 0x7ffff000 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 cbb1: [MPSAFE] cbb1: PCI Configuration space: 0x00: 0xac16104c 0x02100007 0x06070002 0x00824208 0x10: 0x7ffff000 0x020000a0 0x20030300 0xfffff000 0x20: 0x00000000 0xfffff000 0x00000000 0x0000fffc 0x30: 0x00000000 0x0000fffc 0x00000000 0x0740010b 0x40: 0xb0480e11 0x00000001 0x00000000 0x00000000 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 0x80: 0x20449060 0x00000000 0x09898181 0x00000000 0x90: 0x60640280 0x00000000 0x00000000 0x00000000 0xa0: 0x7e210001 0x00800000 0x00000000 0x00000000 0xb0: 0x00000000 0x00000000 0x00000000 0x00000000 0xc0: 0x00000000 0x00000000 0x00000000 0x00000000 0xd0: 0x00000000 0x00000000 0x00000000 0x00000000 0xe0: 0x00000000 0x00000000 0x00000000 0x00000000 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 isab0: at device 14.0 on pci0 isa0: on isab0 atapci0: port 0x1000-0x100f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 14.1 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0x1000 ata0: channel #0 on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=01 ostat0=50 ostat1=ff ata0-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=00 devices=0x1 ata0: [MPSAFE] ata1: channel #1 on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=00 ostat0=ff ostat1=ff ata1: [MPSAFE] pci0: at device 14.2 (no driver attached) cpu0 on motherboard pnpbios: 18 devices, largest 250 bytes PNP0c04: adding io range 0xf0-0xff, size=0x10, align=0 PNP0c04: adding irq mask 0x2000 pnpbios: handle 1 device ID PNP0c04 (040cd041) PNP0c01: adding fixed memory32 range 0-0x9ffff, size=0xa0000 PNP0c01: adding fixed memory32 range 0xf0000-0xfffff, size=0x10000 PNP0c01: adding fixed memory32 range 0x100000-0x5ffffff, size=0x5f00000 pnpbios: handle 2 device ID PNP0c01 (010cd041) PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0 pnpbios: handle 3 device ID PNP0a03 (030ad041) PNP0200: adding io range 0-0xf, size=0x10, align=0 PNP0200: adding io range 0x80-0x8f, size=0x10, align=0 PNP0200: adding io range 0xc0-0xdf, size=0x20, align=0 PNP0200: adding dma mask 0x10 pnpbios: handle 5 device ID PNP0200 (0002d041) PNP0100: adding io range 0x40-0x43, size=0x4, align=0 PNP0100: adding irq mask 0x1 pnpbios: handle 6 device ID PNP0100 (0001d041) PNP0800: adding io range 0x61-0x61, size=0x1, align=0 pnpbios: handle 7 device ID PNP0800 (0008d041) PNP0b00: adding io range 0x70-0x71, size=0x2, align=0 PNP0b00: adding io range 0x74-0x74, size=0x1, align=0 PNP0b00: adding io range 0x76-0x76, size=0x1, align=0 PNP0b00: adding irq mask 0x100 pnpbios: handle 8 device ID PNP0b00 (000bd041) PNP0303: adding io range 0x60-0x60, size=0x1, align=0 PNP0303: adding io range 0x64-0x64, size=0x1, align=0 PNP0303: adding irq mask 0x2 pnpbios: handle 9 device ID PNP0303 (0303d041) PNP0f13: adding irq mask 0x1000 pnpbios: handle 10 device ID PNP0f13 (130fd041) PNP0700: adding irq mask 0x40 PNP0700: adding dma mask 0x4 PNP0700: adding io range 0x3f0-0x3f5, size=0x6, align=0 pnpbios: handle 11 device ID PNP0700 (0007d041) PNP0401: adding irq mask 0x80 PNP0401: adding dma mask 0x8 PNP0401: adding io range 0x378-0x37f, size=0x8, align=0 PNP0401: adding io range 0x778-0x77a, size=0x3, align=0 pnpbios: handle 12 device ID PNP0401 (0104d041) PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0 PNP0501: adding irq mask 0x10 pnpbios: handle 13 device ID PNP0501 (0105d041) pnpbios: handle 14 device ID SMCf010 (10f0a34d) PNP0e03: adding io range 0x3e0-0x3e1, size=0x2, align=0 pnpbios: handle 15 device ID PNP0e03 (030ed041) ESS0009: adding io range 0x250-0x257, size=0x8, align=0 pnpbios: handle 16 device ID ESS0009 (09007316) ESS1879: adding io range 0x220-0x22f, size=0x10, align=0 ESS1879: adding io range 0x388-0x38b, size=0x4, align=0 ESS1879: adding io range 0x330-0x331, size=0x2, align=0 ESS1879: adding irq mask 0x20 ESS1879: adding dma mask 0x2 ESS1879: adding dma mask 0x1 pnpbios: handle 17 device ID ESS1879 (79187316) PNP0c02: adding fixed memory32 range 0xfffc0000-0xffffffff, size=0x40000 PNP0c02: adding fixed memory32 range 0xcc000-0xcffff, size=0x4000 PNP0c02: adding io range 0x10-0x1f, size=0x10, align=0 PNP0c02: adding io range 0x44-0x47, size=0x4, align=0 PNP0c02: adding io range 0x92-0x92, size=0x1, align=0 PNP0c02: adding io range 0xe0-0xef, size=0x10, align=0 PNP0c02: adding io range 0xbc-0xbf, size=0x4, align=0 PNP0c02: adding io range 0x130-0x131, size=0x2, align=0 PNP0c02: adding io range 0x134-0x137, size=0x4, align=0 PNP0c02: adding io range 0x270-0x271, size=0x2, align=0 PNP0c02: adding io range 0x260-0x261, size=0x2, align=0 PNP0c02: adding io range 0x2a0-0x2a0, size=0x1, align=0 PNP0c02: adding io range 0x370-0x371, size=0x2, align=0 PNP0c02: adding io range 0x374-0x374, size=0x1, align=0 PNP0c02: adding io range 0x400-0x47f, size=0x80, align=0 PNP0c02: adding io range 0x480-0x4ff, size=0x80, align=0 PNP0c02: adding io range 0xcf7-0xcf7, size=0x1, align=0 PNP0c02: adding io range 0xc48-0xc48, size=0x1, align=0 PNP0c02: adding io range 0xc4a-0xc4a, size=0x1, align=0 PNP0c02: adding io range 0xc6c-0xc6d, size=0x2, align=0 PNP0c02: adding io range 0x800-0x87f, size=0x80, align=0 PNP0c02: adding io range 0xc1f-0xc20, size=0x2, align=0 PNP0c02: adding io range 0xc80-0xc9f, size=0x20, align=0 pnpbios: handle 19 device ID PNP0c02 (020cd041) ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices pmtimer0 on isa0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff adv0: not probed (disabled) aha0: not probed (disabled) aic0: not probed (disabled) atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 atkbd0: [GIANT-LOCKED] psm0: current command byte:0065 psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3-00, 3 buttons psm0: config:00000000, flags:00000008, packet size:4 psm0: syncmask:08, syncbits:00 bt0: not probed (disabled) cs0: not probed (disabled) ed0: not probed (disabled) fdc0: ic_type 90 part_id 80 fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: ic_type 90 part_id 80 fdc0: [MPSAFE] fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 fe0: not probed (disabled) ie0: not probed (disabled) lnc0: not probed (disabled) pcic0 failed to probe at port 0x3e0 iomem 0xd0000 on isa0 pcic1: not probed (disabled) ppc0: parallel port found at 0x378 ppc0: using extended I/O port range ppc0: EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: irq maps: 0x1 0x1 0x1 0x1 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) sn0: not probed (disabled) vt0: not probed (disabled) isa_probe_children: probing PnP devices unknown: failed to probe at port 0x61 on isa0 unknown: can't assign resources (port) unknown: at port 0x60 on isa0 unknown: can't assign resources (irq) unknown: at irq 12 on isa0 unknown: can't assign resources (port) unknown: at port 0x3f0-0x3f5 on isa0 unknown: can't assign resources (port) unknown: at port 0x378-0x37f on isa0 unknown: can't assign resources (port) unknown: at port 0x3f8-0x3ff on isa0 unknown: failed to probe on isa0 unknown: failed to probe at port 0x3e0-0x3e1 on isa0 unknown: failed to probe at port 0x250-0x257 on isa0 sbc0: at port 0x330-0x331,0x388-0x38b,0x220-0x22f irq 5 drq 0,1 on isa0 sbc0: [GIANT-LOCKED] pcm0: on sbc0 pcm0: ESS1879 detected, newspeed pcm0: [GIANT-LOCKED] pcm0: sndbuf_setmap ff4000, 1000; 0xc699c000 -> ff4000 pcm0: sndbuf_setmap ff3000, 1000; 0xc699d000 -> ff3000 Device configuration finished. procfs registered linprocfs registered TSC timecounter disabled: APM enabled. Timecounter "TSC" frequency 266677167 Hz quality -1000 Timecounters tick every 4.000 msec Linux ELF exec handler installed lo0: bpf attached ipfw2 initialized, divert enabled, rule-based forwarding disabled, default to deny, logging unlimited ata0-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin ad0: ATA-5 disk at ata0-master ad0: 9590MB (19640880 sectors), 19485 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, PIO4 pccard0: CIS version PC Card Standard 5.0 pccard0: CIS info: , IEEE 802.11 Wireless LAN/PC Card, pccard0: Manufacturer code 0xd601, product 0x2 pccard0: function 0: network adapter, ccr addr 3e0 mask 1 pccard0: function 0, config table entry 1: I/O card; irq mask ffff; iomask 6, iospace 0-3f; io16 irqpulse irqlevel pccard0: (manufacturer=0xd601, product=0x0002) at function 0 pccard0: CIS info: , IEEE 802.11 Wireless LAN/PC Card, GEOM: new disk ad0 [0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/15/63 s:63 l:19640817 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure ad0s1, start 32256 length 10056098304 end 10056130559 GEOM: Configure ad0s1a, start 0 length 268435456 end 268435455 GEOM: Configure ad0s1b, start 268435456 length 185606144 end 454041599 GEOM: Configure ad0s1c, start 0 length 10056098304 end 10056098303 GEOM: Configure ad0s1d, start 454041600 length 268435456 end 722477055 GEOM: Configure ad0s1e, start 722477056 length 268435456 end 990912511 GEOM: Configure ad0s1f, start 990912512 length 9065185792 end 10056098303 Mounting root from ufs:/dev/ad0s1a start_init: trying /sbin/init wlan: <802.11 Link Layer> wi0: < IEEE 802.11 Wireless LAN/PC Card> at port 0x180-0x1bf irq 11 function 0 config 1 on pccard0 wi0: [MPSAFE] wi0: using RF:PRISM2 MAC:HFA3841 CARD:HWB3163 rev.A wi0: Intersil Firmware: Primary (0.3.0), Station (0.8.3) wi0: bpf attached wi0: Ethernet address: 00:60:b3:71:86:1c wi0: bpf attached wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps wi0: bpf attached pci0: driver added found-> vendor=0x0e11, dev=0xa0f8, revid=0x11 bus=0, slot=14, func=2 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 1 supports D0 D3 current D0 pci0:14:2: reprobing on driver added pci0:14:2: Transition from D0 to D3 pci1: driver added found-> vendor=0x5333, dev=0x8c01, revid=0x06 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0003, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x04 (1000 ns), maxlat=0xff (63750 ns) pci1:0:0: reprobing on driver added tun1: bpf attached pci0: driver added found-> vendor=0x0e11, dev=0xa0f8, revid=0x11 bus=0, slot=14, func=2 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 1 supports D0 D3 current D3 pci0:14:2: reprobing on driver added pci0:14:2: Transition from D3 to D0 pci0:14:2: Transition from D0 to D3 pci1: driver added found-> vendor=0x5333, dev=0x8c01, revid=0x06 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0003, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x04 (1000 ns), maxlat=0xff (63750 ns) pci1:0:0: reprobing on driver added pci0: driver added found-> vendor=0x0e11, dev=0xa0f8, revid=0x11 bus=0, slot=14, func=2 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 1 supports D0 D3 current D3 pci0:14:2: reprobing on driver added pci0:14:2: Transition from D3 to D0 ohci0: mem 0x44080000-0x44080fff irq 11 at device 14.2 on pci0 ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0x44080000 ohci0: (New OHCI DeviceId=0xa0f80e11) ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0 usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x0e11) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci1: driver added found-> vendor=0x5333, dev=0x8c01, revid=0x06 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0003, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x04 (1000 ns), maxlat=0xff (63750 ns) pci1:0:0: reprobing on driver added pci0: driver added pci1: driver added found-> vendor=0x5333, dev=0x8c01, revid=0x06 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0003, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x04 (1000 ns), maxlat=0xff (63750 ns) pci1:0:0: reprobing on driver added uhub1: Broadcom product 0x3535, class 9/0, rev 2.00/1.00, addr 2 uhub1: 3 ports with 0 removable, bus powered ubt0: Broadcom BCM92035DGL, rev 1.10/1.00, addr 3 ubt0: Broadcom BCM92035DGL, rev 1.10/1.00, addr 3 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 --Boundary_(ID_U4TtL1uBOl/kJOoxcD4r+Q)-- From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 6 18:27:15 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 19A9516A4E4 for ; Thu, 6 Jan 2005 18:27:11 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9919043D54 for ; Thu, 6 Jan 2005 18:27:10 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45])j06IQiTt014235; Thu, 6 Jan 2005 12:26:44 -0600 Received: from s228130hz1ew17.apptix-01.savvis.net ([10.146.4.29]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 6 Jan 2005 12:26:36 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew17.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 6 Jan 2005 12:26:19 -0600 Message-ID: <41DD82CE.5080502@savvis.net> Date: Thu, 06 Jan 2005 10:26:22 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ronald Klop References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 06 Jan 2005 18:26:20.0040 (UTC) FILETIME=[37C98880:01C4F41D] X-ECS-MailScanner: No virus is found cc: freebsd-bluetooth@freebsd.org Subject: Re: ng_ubt with Broadcom BCM92035DGL 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, 06 Jan 2005 18:27:15 -0000 Ronald, > I have a USB Bluetooth adapter which probes fine as ubt0, but I get errors > when trying to use bluetooth. > Attached is my verbose dmesg output. I've read the handbook about > bluetooth and searched the internet for it. > The errors I get are these. > > # /etc/rc.bluetooth start ubt0 > Status: Command disallowed [0xc] > > # /etc/rc.bluetooth start ubt0 > Could not execute command "reset". Operation timed out > > What information can I provide to resolve this. Or is there a better > mailinglist for this? for starters can you tell which command your dongle disallowed. rc.bluetooth is a shell script, so 1) unplug the dongle 2) plug the dongle 3) # sh -x /etc/rc.bluetooth start ubt0 4) send me the output then try to comment out the disallowed command and repeat the steps above. > The usb-adapter is the shop-brand of the MyCom shops in The Netherlands. ok, do you know if i can get similar adapter in US? > uhub1: Broadcom product 0x3535, class 9/0, rev 2.00/1.00, addr 2 > uhub1: 3 ports with 0 removable, bus powered > ubt0: Broadcom BCM92035DGL, rev 1.10/1.00, addr 3 > ubt0: Broadcom BCM92035DGL, rev 1.10/1.00, addr 3 > ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 > ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 this looks fine to me. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 6 18:51:32 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 72E2816A4CE for ; Thu, 6 Jan 2005 18:51:32 +0000 (GMT) Received: from smtp17.wxs.nl (smtp17.wxs.nl [195.121.6.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E55843D5D for ; Thu, 6 Jan 2005 18:51:32 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from ronald.echteman.nl (ip51cdc5d2.speed.planet.nl [81.205.197.210])2004))freebsd-bluetooth@freebsd.org; Thu, 06 Jan 2005 19:51:31 +0100 (CET) Received: (qmail 11456 invoked from network); Thu, 06 Jan 2005 18:51:30 +0000 Received: from unknown (HELO laptop.thuis.klop.ws) (192.168.1.4) by ronald.echteman.nl with SMTP; Thu, 06 Jan 2005 18:51:30 +0000 Received: (qmail 2832 invoked from network); Thu, 06 Jan 2005 18:51:28 +0000 Received: from localhost.thuis.klop.ws (HELO smtp.local) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; Thu, 06 Jan 2005 18:51:28 +0000 Date: Thu, 06 Jan 2005 19:51:24 +0100 From: Ronald Klop In-reply-to: <41DD82CE.5080502@savvis.net> To: Maksim Yevmenkin Message-id: MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_7E/5UKxifNzHjf3gIoMsxw)" User-Agent: Opera M2/7.54u1 (FreeBSD, build 892) References: <41DD82CE.5080502@savvis.net> cc: freebsd-bluetooth@freebsd.org Subject: Re: ng_ubt with Broadcom BCM92035DGL 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, 06 Jan 2005 18:51:32 -0000 --Boundary_(ID_7E/5UKxifNzHjf3gIoMsxw) Content-type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 Content-transfer-encoding: 7BIT On Thu, 06 Jan 2005 10:26:22 -0800, Maksim Yevmenkin wrote: > Ronald, > > for starters can you tell which command your dongle disallowed. > rc.bluetooth is a shell script, so > > 1) unplug the dongle > > 2) plug the dongle > > 3) # sh -x /etc/rc.bluetooth start ubt0 > > 4) send me the output > > then try to comment out the disallowed command and repeat the steps > above. > >> The usb-adapter is the shop-brand of the MyCom shops in The Netherlands. > > ok, do you know if i can get similar adapter in US? Hi, Thanks for your reply. Attached is the output from the 'sh -x ...' as you requested. I also attached the usbdevs -v output for the device id's. Searching with google for bmc92035dgl gives one result. http://sourceforge.net/mailarchive/forum.php?thread_id=6218036&forum_id=1883 This site mentions a 'IOgear GBU311' usb adapter. I didn't know the sh -x trick. (Even after years I still learn something new about the wonderful Unix tools.) In a few moments I will send my results when I uncomment the disallowed command. Ronald. -- Ronald Klop, Amsterdam, The Netherlands --Boundary_(ID_7E/5UKxifNzHjf3gIoMsxw) Content-type: text/plain; name=typescript.txt Content-transfer-encoding: 7BIT Content-disposition: attachment; filename=typescript.txt Script started on Thu Jan 6 19:40:56 2005 # root@laptop [~] portaudit -aFdaF sh -x /etc/rc.bluetooth start ubt0 + logger=/usr/bin/logger -i -s -p user.err + kldstat=/sbin/kldstat + kldload=/sbin/kldload + sysctl=/sbin/sysctl + ngctl=/usr/sbin/ngctl + hcseriald=/usr/sbin/hcseriald + hccontrol=/usr/sbin/hccontrol + hci_debug_level=3 + l2cap_debug_level=3 + [ 2 -lt 2 ] + startstop=start + shift + dev=ubt0 + shift + load_module ng_bluetooth + module=ng_bluetooth + shift + /sbin/kldstat -n ng_bluetooth + [ 0 -ne 0 ] + load_module ng_hci + module=ng_hci + shift + /sbin/kldstat -n ng_hci + [ 0 -ne 0 ] + load_module ng_l2cap + module=ng_l2cap + shift + /sbin/kldstat -n ng_l2cap + [ 0 -ne 0 ] + load_module ng_btsocket + module=ng_btsocket + shift + /sbin/kldstat -n ng_btsocket + [ 0 -ne 0 ] + /etc/rc.bluetooth stop ubt0 + hook=hook + expr ubt0 : ubt\([0-9]\{1,\}\) + unit=0 + [ -z 0 ] + setup_stack ubt0 hook + dev=ubt0 + shift + hook=hook + shift + /usr/sbin/ngctl mkpeer ubt0: hci hook drv + /usr/sbin/ngctl name ubt0:hook ubt0hci + /usr/sbin/ngctl msg ubt0hci: set_debug 3 + /usr/sbin/ngctl mkpeer ubt0hci: l2cap acl hci + /usr/sbin/ngctl name ubt0hci:acl ubt0l2cap + /usr/sbin/ngctl msg ubt0l2cap: set_debug 3 + /usr/sbin/ngctl connect ubt0hci: btsock_hci_raw: raw ubt0raw + /usr/sbin/ngctl connect ubt0l2cap: btsock_l2c_raw: ctl ubt0ctl + /usr/sbin/ngctl connect ubt0l2cap: btsock_l2c: l2c ubt0l2c + /usr/sbin/hccontrol -n ubt0hci reset Status: Command disallowed [0xc] + exit 1 # root@laptop [~] exit Script done on Thu Jan 6 19:42:51 2005 --Boundary_(ID_7E/5UKxifNzHjf3gIoMsxw) Content-type: text/plain; name=usbdevs.txt Content-transfer-encoding: 7BIT Content-disposition: attachment; filename=usbdevs.txt Controller /dev/usb0: addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), (0x0e11)(0x0000), rev 1.00 port 1 addr 2: full speed, power 100 mA, config 1, product 0x3535(0x3535), Broadcom(0x0a5c), rev 1.00 port 1 addr 3: full speed, self powered, config 1, BCM92035DGL(0x2009), Broadcom(0x0a5c), rev 1.00 port 2 addr 4: full speed, self powered, config 1, product 0x3502(0x3502), Broadcom(0x0a5c), rev 1.00 port 3 addr 5: full speed, self powered, config 1, product 0x3503(0x3503), Broadcom(0x0a5c), rev 1.00 port 2 powered --Boundary_(ID_7E/5UKxifNzHjf3gIoMsxw)-- From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 6 19:04:03 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 56DF516A4CE for ; Thu, 6 Jan 2005 19:04:03 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BA8B43D49 for ; Thu, 6 Jan 2005 19:04:03 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45])j06IvcU1016910; Thu, 6 Jan 2005 12:57:47 -0600 Received: from s228130hz1ew17.apptix-01.savvis.net ([10.146.4.29]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 6 Jan 2005 12:57:35 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew17.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 6 Jan 2005 12:57:16 -0600 Message-ID: <41DD8A10.5080104@savvis.net> Date: Thu, 06 Jan 2005 10:57:20 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ronald Klop References: <41DD82CE.5080502@savvis.net> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 06 Jan 2005 18:57:16.0782 (UTC) FILETIME=[8A7DE0E0:01C4F421] X-ECS-MailScanner: No virus is found cc: freebsd-bluetooth@freebsd.org Subject: Re: ng_ubt with Broadcom BCM92035DGL 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, 06 Jan 2005 19:04:03 -0000 Ronald, >> for starters can you tell which command your dongle disallowed. >> rc.bluetooth is a shell script, so >> >> 1) unplug the dongle >> >> 2) plug the dongle >> >> 3) # sh -x /etc/rc.bluetooth start ubt0 >> >> 4) send me the output >> >> then try to comment out the disallowed command and repeat the steps >> above. >> >>> The usb-adapter is the shop-brand of the MyCom shops in The Netherlands. >> >> >> ok, do you know if i can get similar adapter in US? > > > Searching with google for bmc92035dgl gives one result. > http://sourceforge.net/mailarchive/forum.php?thread_id=6218036&forum_id=1883 yes, i've seen it too. > This site mentions a 'IOgear GBU311' usb adapter. yes, and it costs ~$50 :( will wait until it gets into $10-$15 range :) > I didn't know the sh -x trick. (Even after years I still learn > something new about the wonderful Unix tools.) > In a few moments I will send my results when I uncomment the disallowed > command. [...] > + /usr/sbin/hccontrol -n ubt0hci reset > Status: Command disallowed [0xc] > + exit 1 i kinda suspected it would be 'reset'. try commenting it out and re-run rc.bluetooth. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 6 19:07:52 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 A2C3216A4CE for ; Thu, 6 Jan 2005 19:07:52 +0000 (GMT) Received: from smtp15.wxs.nl (smtp15.wxs.nl [195.121.6.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 586CB43D4C for ; Thu, 6 Jan 2005 19:07:52 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from ronald.echteman.nl (ip51cdc5d2.speed.planet.nl [81.205.197.210])2004))freebsd-bluetooth@freebsd.org; Thu, 06 Jan 2005 20:07:51 +0100 (CET) Received: (qmail 11569 invoked from network); Thu, 06 Jan 2005 19:07:50 +0000 Received: from unknown (HELO laptop.thuis.klop.ws) (192.168.1.4) by ronald.echteman.nl with SMTP; Thu, 06 Jan 2005 19:07:50 +0000 Received: (qmail 3038 invoked from network); Thu, 06 Jan 2005 19:07:49 +0000 Received: from localhost.thuis.klop.ws (HELO smtp.local) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; Thu, 06 Jan 2005 19:07:49 +0000 Date: Thu, 06 Jan 2005 20:07:47 +0100 From: Ronald Klop In-reply-to: To: Maksim Yevmenkin Message-id: MIME-version: 1.0 Content-type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 Content-transfer-encoding: 7BIT User-Agent: Opera M2/7.54u1 (FreeBSD, build 892) References: <41DD82CE.5080502@savvis.net> cc: freebsd-bluetooth@freebsd.org Subject: Re: ng_ubt with Broadcom BCM92035DGL 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, 06 Jan 2005 19:07:52 -0000 On Thu, 06 Jan 2005 19:51:24 +0100, Ronald Klop wrote: > On Thu, 06 Jan 2005 10:26:22 -0800, Maksim Yevmenkin > wrote: > >> Ronald, >> >> for starters can you tell which command your dongle disallowed. >> rc.bluetooth is a shell script, so >> >> 1) unplug the dongle >> >> 2) plug the dongle >> >> 3) # sh -x /etc/rc.bluetooth start ubt0 >> >> 4) send me the output >> >> then try to comment out the disallowed command and repeat the steps >> above. I commented out this list of hci-commands one by one and they all give the same error. (Status: Command disallowed [0xc]) reset write_scan_enable 3 write_class_of_device change_local_name After commenting all this rc.bluetooth ends without errors. The output is this. + /usr/sbin/ngctl mkpeer ubt0: hci hook drv + /usr/sbin/ngctl name ubt0:hook ubt0hci + /usr/sbin/ngctl msg ubt0hci: set_debug 3 + /usr/sbin/ngctl mkpeer ubt0hci: l2cap acl hci + /usr/sbin/ngctl name ubt0hci:acl ubt0l2cap + /usr/sbin/ngctl msg ubt0l2cap: set_debug 3 + /usr/sbin/ngctl connect ubt0hci: btsock_hci_raw: raw ubt0raw + /usr/sbin/ngctl connect ubt0l2cap: btsock_l2c_raw: ctl ubt0ctl + /usr/sbin/ngctl connect ubt0l2cap: btsock_l2c: l2c ubt0l2c + /usr/sbin/hccontrol -n ubt0hci read_bd_addr BD_ADDR: 00:02:72:c0:23:12 + /usr/sbin/hccontrol -n ubt0hci read_local_supported_features Features: 0xff 0xff 0xd 0x38 0x8 0x8 00 00 <3-Slot> <5-Slot> + /usr/sbin/hccontrol -n ubt0hci read_buffer_size Max. ACL packet size: 377 bytes Number of ACL packets: 10 Max. SCO packet size: 16 bytes Number of SCO packets: 0 + /usr/sbin/hccontrol -n ubt0hci initialize I then tried 'hccontrol -n ubt0hci inquiry', but it returns nothing. (I'm trying to connect to my mobile phone.) Any thoughts? Ronald. -- Ronald Klop, Amsterdam, The Netherlands From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 6 19:25: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 67DAA16A4CE for ; Thu, 6 Jan 2005 19:25:49 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1827343D60 for ; Thu, 6 Jan 2005 19:25:49 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45])j06JPfTt020066; Thu, 6 Jan 2005 13:25:41 -0600 Received: from s228130hz1ew03.apptix-01.savvis.net ([10.146.4.28]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 6 Jan 2005 13:25:32 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew03.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 6 Jan 2005 13:24:55 -0600 Message-ID: <41DD9095.6010409@savvis.net> Date: Thu, 06 Jan 2005 11:25:09 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ronald Klop References: <41DD82CE.5080502@savvis.net> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 06 Jan 2005 19:24:55.0379 (UTC) FILETIME=[6717B230:01C4F425] X-ECS-MailScanner: No virus is found cc: freebsd-bluetooth@freebsd.org Subject: Re: ng_ubt with Broadcom BCM92035DGL 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, 06 Jan 2005 19:25:49 -0000 Ronald Klop wrote: [...] > I commented out this list of hci-commands one by one and they all give > the same error. (Status: Command disallowed [0xc]) > > reset > write_scan_enable 3 > write_class_of_device > change_local_name none of the commands above is strictly required. well, maybe with exception of 'write_scan_enable 3' command. this command supposed to make bluetooth device answer inquiry from the remote devices, i.e. it makes bluetooth device 'visible' to other devices. what is the output of % hccontrol -n ubt0hci read_node_state % hccontrol -n ubt0hci read_scan_enable % hccontrol -n ubt0hci read_class_of_device % hccontrol -n ubt0hci read_local_name commands? > After commenting all this rc.bluetooth ends without errors. The output > is this. > + /usr/sbin/ngctl mkpeer ubt0: hci hook drv > + /usr/sbin/ngctl name ubt0:hook ubt0hci > + /usr/sbin/ngctl msg ubt0hci: set_debug 3 > + /usr/sbin/ngctl mkpeer ubt0hci: l2cap acl hci > + /usr/sbin/ngctl name ubt0hci:acl ubt0l2cap > + /usr/sbin/ngctl msg ubt0l2cap: set_debug 3 > + /usr/sbin/ngctl connect ubt0hci: btsock_hci_raw: raw ubt0raw > + /usr/sbin/ngctl connect ubt0l2cap: btsock_l2c_raw: ctl ubt0ctl > + /usr/sbin/ngctl connect ubt0l2cap: btsock_l2c: l2c ubt0l2c > + /usr/sbin/hccontrol -n ubt0hci read_bd_addr > BD_ADDR: 00:02:72:c0:23:12 > + /usr/sbin/hccontrol -n ubt0hci read_local_supported_features > Features: 0xff 0xff 0xd 0x38 0x8 0x8 00 00 > <3-Slot> <5-Slot> > > > > > + /usr/sbin/hccontrol -n ubt0hci read_buffer_size > Max. ACL packet size: 377 bytes > Number of ACL packets: 10 > Max. SCO packet size: 16 bytes > Number of SCO packets: 0 > + /usr/sbin/hccontrol -n ubt0hci initialize > > I then tried 'hccontrol -n ubt0hci inquiry', but it returns nothing. > (I'm trying to connect to my mobile phone.) > > Any thoughts? the output above looks fine, so i'd say it should work. - did you enable bluetooth on your phone? - did you make your phone 'visible' to other bluetooth devices (look somewhere under bluetooth security settings) - what is your phone make and model? max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 6 19:40: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 C5E2C16A4E3 for ; Thu, 6 Jan 2005 19:40:33 +0000 (GMT) Received: from smtp16.wxs.nl (smtp16.wxs.nl [195.121.6.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5114943D64 for ; Thu, 6 Jan 2005 19:40:26 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from ronald.echteman.nl (ip51cdc5d2.speed.planet.nl [81.205.197.210])2004))freebsd-bluetooth@freebsd.org; Thu, 06 Jan 2005 20:40:25 +0100 (CET) Received: (qmail 11817 invoked from network); Thu, 06 Jan 2005 19:40:24 +0000 Received: from unknown (HELO laptop.thuis.klop.ws) (192.168.1.4) by ronald.echteman.nl with SMTP; Thu, 06 Jan 2005 19:40:24 +0000 Received: (qmail 14486 invoked from network); Thu, 06 Jan 2005 19:40:22 +0000 Received: from localhost.thuis.klop.ws (HELO smtp.local) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; Thu, 06 Jan 2005 19:40:22 +0000 Date: Thu, 06 Jan 2005 20:40:14 +0100 From: Ronald Klop In-reply-to: <41DD9095.6010409@savvis.net> To: Maksim Yevmenkin Message-id: MIME-version: 1.0 Content-type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 Content-transfer-encoding: 7BIT User-Agent: Opera M2/7.54u1 (FreeBSD, build 892) References: <41DD82CE.5080502@savvis.net> <41DD9095.6010409@savvis.net> cc: freebsd-bluetooth@freebsd.org Subject: Re: ng_ubt with Broadcom BCM92035DGL 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, 06 Jan 2005 19:40:34 -0000 On Thu, 06 Jan 2005 11:25:09 -0800, Maksim Yevmenkin wrote: > Ronald Klop wrote: > > [...] > >> I commented out this list of hci-commands one by one and they all give >> the same error. (Status: Command disallowed [0xc]) >> reset >> write_scan_enable 3 >> write_class_of_device >> change_local_name > > none of the commands above is strictly required. well, maybe with > exception of 'write_scan_enable 3' command. this command supposed to > make bluetooth device answer inquiry from the remote devices, i.e. it > makes bluetooth device 'visible' to other devices. > > what is the output of > > % hccontrol -n ubt0hci read_node_state State: 0x3 > % hccontrol -n ubt0hci read_scan_enable Status: Command disallowed [0xc] > % hccontrol -n ubt0hci read_class_of_device Status: Command disallowed [0xc] > % hccontrol -n ubt0hci read_local_name Status: Command disallowed [0xc] > the output above looks fine, so i'd say it should work. > > - did you enable bluetooth on your phone? Yes, I did. Would be a nice mistake. :-) > - did you make your phone 'visible' to other bluetooth devices (look > somewhere under bluetooth security settings) Yes, I did. > - what is your phone make and model? Sony Ericsson K700i I do not have other bluetooth devices to test with. And if I ask my phone to search for bluetooth devices it doesn't find anything. I already read quite a lot about it and I think the not working write_scan_enable is not good. Can you tell me what 'Status: Command disallowed [0xc]' means? Is this my bluetooth adapter telling I can't issue the command, is it usb? Or is it in the software (driver)? Or do you have any other clue about it? Ronald. -- Ronald Klop, Amsterdam, The Netherlands From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 6 20:04:08 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 EF11E16A4CE for ; Thu, 6 Jan 2005 20:04:07 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7439B43D1F for ; Thu, 6 Jan 2005 20:04:07 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44])j06K3YTt023186; Thu, 6 Jan 2005 14:03:34 -0600 Received: from s228130hz1ew17.apptix-01.savvis.net ([10.146.4.29]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 6 Jan 2005 14:03:25 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew17.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 6 Jan 2005 14:03:10 -0600 Message-ID: <41DD997C.90605@savvis.net> Date: Thu, 06 Jan 2005 12:03:08 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ronald Klop References: <41DD82CE.5080502@savvis.net> <41DD9095.6010409@savvis.net> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 06 Jan 2005 20:03:11.0028 (UTC) FILETIME=[BF67EF40:01C4F42A] X-ECS-MailScanner: No virus is found cc: freebsd-bluetooth@freebsd.org Subject: Re: ng_ubt with Broadcom BCM92035DGL 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, 06 Jan 2005 20:04:08 -0000 Ronald, >>> I commented out this list of hci-commands one by one and they all >>> give the same error. (Status: Command disallowed [0xc]) >>> reset >>> write_scan_enable 3 >>> write_class_of_device >>> change_local_name >> >> none of the commands above is strictly required. well, maybe with >> exception of 'write_scan_enable 3' command. this command supposed to >> make bluetooth device answer inquiry from the remote devices, i.e. it >> makes bluetooth device 'visible' to other devices. >> >> what is the output of >> >> % hccontrol -n ubt0hci read_node_state > > State: 0x3 ok, hci node is initialized >> % hccontrol -n ubt0hci read_scan_enable > > Status: Command disallowed [0xc] bummer :( >> % hccontrol -n ubt0hci read_class_of_device > > Status: Command disallowed [0xc] double bummer :( >> % hccontrol -n ubt0hci read_local_name > > Status: Command disallowed [0xc] triple bummer :( >> the output above looks fine, so i'd say it should work. >> >> - did you enable bluetooth on your phone? > > Yes, I did. Would be a nice mistake. :-) good. >> - did you make your phone 'visible' to other bluetooth devices (look >> somewhere under bluetooth security settings) > > Yes, I did. fine, just checking :) >> - what is your phone make and model? > > Sony Ericsson K700i that phone should work just fine. > I do not have other bluetooth devices to test with. > > And if I ask my phone to search for bluetooth devices it doesn't find > anything. yes, most (all) devices will not answer inquiry by default. that is what write_scan_enable command does. > I already read quite a lot about it and I think the not working > write_scan_enable is not good. correct. > Can you tell me what 'Status: Command disallowed [0xc]' means? i've never seen this before. but my guess would be it means exactly what it says: device has received command and decided that it does not want to execute it. > Is this my bluetooth adapter telling I can't issue the command, is it usb? its adapter. after the command is received the adapter will send hci event back. one of the fields is a status byte. non-zero status means something is wrong. > Or is it in the software (driver)? no, its adapter. > Or do you have any other clue about it? the spec on the web says this adapter is a bluetooth v1.2 adapter. i do not think it matters (there were no big changes since v1.1 - not in the hci commands/events at least). will look anyway. unless i get this specimen into my lab for dissection there is not much i can do. sorry :( max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 6 20:32:16 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 AA60D16A4CE for ; Thu, 6 Jan 2005 20:32:16 +0000 (GMT) Received: from smtp19.wxs.nl (smtp19.wxs.nl [195.121.6.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 653BA43D3F for ; Thu, 6 Jan 2005 20:32:16 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from ronald.echteman.nl (ip51cdc5d2.speed.planet.nl [81.205.197.210])2004))freebsd-bluetooth@freebsd.org; Thu, 06 Jan 2005 21:32:15 +0100 (CET) Received: (qmail 12791 invoked from network); Thu, 06 Jan 2005 20:32:14 +0000 Received: from unknown (HELO laptop.thuis.klop.ws) (192.168.1.4) by ronald.echteman.nl with SMTP; Thu, 06 Jan 2005 20:32:13 +0000 Received: (qmail 53275 invoked from network); Thu, 06 Jan 2005 20:32:09 +0000 Received: from localhost.thuis.klop.ws (HELO smtp.local) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; Thu, 06 Jan 2005 20:32:09 +0000 Date: Thu, 06 Jan 2005 21:31:56 +0100 From: Ronald Klop In-reply-to: <41DD997C.90605@savvis.net> To: Maksim Yevmenkin Message-id: MIME-version: 1.0 Content-type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 Content-transfer-encoding: 7BIT User-Agent: Opera M2/7.54u1 (FreeBSD, build 892) References: <41DD82CE.5080502@savvis.net> <41DD9095.6010409@savvis.net> <41DD997C.90605@savvis.net> cc: freebsd-bluetooth@freebsd.org Subject: Re: ng_ubt with Broadcom BCM92035DGL 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, 06 Jan 2005 20:32:16 -0000 On Thu, 06 Jan 2005 12:03:08 -0800, Maksim Yevmenkin wrote: > Ronald, > >> Or do you have any other clue about it? > > the spec on the web says this adapter is a bluetooth v1.2 adapter. i do > not think it matters (there were no big changes since v1.1 - not in the > hci commands/events at least). will look anyway. > > unless i get this specimen into my lab for dissection there is not much > i can do. sorry :( > > max I understand. I think the costs of shipping you one from Europe to the US is more than the price of the USB adapter. I will look for another one and return this one to the store. Thanks a lot for your time. Ronald. -- Ronald Klop, Amsterdam, The Netherlands From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 6 21:28:06 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 1C84F16A4CE for ; Thu, 6 Jan 2005 21:28:06 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FB0B43D1D for ; Thu, 6 Jan 2005 21:28:05 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45])j06LRiTt029295; Thu, 6 Jan 2005 15:27:44 -0600 Received: from s228130hz1ew17.apptix-01.savvis.net ([10.146.4.29]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 6 Jan 2005 15:27:42 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew17.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 6 Jan 2005 15:27:34 -0600 Message-ID: <41DDAD45.2070807@savvis.net> Date: Thu, 06 Jan 2005 13:27:33 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ronald Klop References: <41DD82CE.5080502@savvis.net> <41DD9095.6010409@savvis.net> <41DD997C.90605@savvis.net> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 06 Jan 2005 21:27:34.0985 (UTC) FILETIME=[89C27390:01C4F436] X-ECS-MailScanner: No virus is found cc: freebsd-bluetooth@freebsd.org Subject: Re: ng_ubt with Broadcom BCM92035DGL 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, 06 Jan 2005 21:28:06 -0000 Ronald Klop wrote: > On Thu, 06 Jan 2005 12:03:08 -0800, Maksim Yevmenkin > wrote: > >> Ronald, >> >>> Or do you have any other clue about it? >> >> >> the spec on the web says this adapter is a bluetooth v1.2 adapter. i >> do not think it matters (there were no big changes since v1.1 - not >> in the hci commands/events at least). will look anyway. >> >> unless i get this specimen into my lab for dissection there is not >> much i can do. sorry :( >> >> max > > > I understand. I think the costs of shipping you one from Europe to the > US is more than the price of the USB adapter. I will look for another > one and return this one to the store. use this page for reference. if driver column says 'hci_usb' then device will most likely to work http://www.holtmann.org/linux/bluetooth/devices.html > Thanks a lot for your time. sure. sorry, couldn't help you. max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 6 22:37:43 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 520DC16A4CE for ; Thu, 6 Jan 2005 22:37:43 +0000 (GMT) Received: from smtp17.wxs.nl (smtp17.wxs.nl [195.121.6.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CFFF43D46 for ; Thu, 6 Jan 2005 22:37:43 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from ronald.echteman.nl (ip51cdc5d2.speed.planet.nl [81.205.197.210])2004))freebsd-bluetooth@freebsd.org; Thu, 06 Jan 2005 23:37:41 +0100 (CET) Received: (qmail 14075 invoked from network); Thu, 06 Jan 2005 22:37:41 +0000 Received: from unknown (HELO laptop.thuis.klop.ws) (192.168.1.4) by ronald.echteman.nl with SMTP; Thu, 06 Jan 2005 22:37:41 +0000 Received: (qmail 768 invoked from network); Thu, 06 Jan 2005 22:37:35 +0000 Received: from localhost.thuis.klop.ws (HELO smtp.local) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; Thu, 06 Jan 2005 22:37:35 +0000 Date: Thu, 06 Jan 2005 23:37:33 +0100 From: Ronald Klop In-reply-to: <41DDAD45.2070807@savvis.net> To: Maksim Yevmenkin Message-id: MIME-version: 1.0 Content-type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 Content-transfer-encoding: 7BIT User-Agent: Opera M2/7.54u1 (FreeBSD, build 892) References: <41DD82CE.5080502@savvis.net> <41DD9095.6010409@savvis.net> <41DD997C.90605@savvis.net> <41DDAD45.2070807@savvis.net> cc: freebsd-bluetooth@freebsd.org Subject: Re: ng_ubt with Broadcom BCM92035DGL 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, 06 Jan 2005 22:37:43 -0000 On Thu, 06 Jan 2005 13:27:33 -0800, Maksim Yevmenkin wrote: > use this page for reference. if driver column says 'hci_usb' then device > will most likely to work > > http://www.holtmann.org/linux/bluetooth/devices.html > >> Thanks a lot for your time. > > sure. sorry, couldn't help you. That's the risk of running a free OS. :-) I just found these in my /var/log/messages. ng_hci_process_command_complete: ubt0hci - HCI command failed, OGF=0x3, OCF=0x1a, status=0xc ng_hci_process_command_complete: ubt0hci - HCI command failed, OGF=0x3, OCF=0x3, status=0xc The first is about a 'write_scan_enable 3' and the last is a 'reset'. Maybe it is valuable info. Cheers, Ronald. -- Ronald Klop, Amsterdam, The Netherlands From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 6 23:14:44 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 F17E116A4CE for ; Thu, 6 Jan 2005 23:14:44 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7CAE443D5D for ; Thu, 6 Jan 2005 23:14:44 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45])j06NEfTt004535; Thu, 6 Jan 2005 17:14:41 -0600 Received: from s228130hz1ew03.apptix-01.savvis.net ([10.146.4.28]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 6 Jan 2005 17:14:28 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew03.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 6 Jan 2005 17:14:24 -0600 Message-ID: <41DDC64F.7000904@savvis.net> Date: Thu, 06 Jan 2005 15:14:23 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ronald Klop References: <41DD82CE.5080502@savvis.net> <41DD9095.6010409@savvis.net> <41DD997C.90605@savvis.net> <41DDAD45.2070807@savvis.net> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 06 Jan 2005 23:14:24.0286 (UTC) FILETIME=[76002BE0:01C4F445] X-ECS-MailScanner: No virus is found cc: freebsd-bluetooth@freebsd.org Subject: Re: ng_ubt with Broadcom BCM92035DGL 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, 06 Jan 2005 23:14:45 -0000 Ronald Klop wrote: > On Thu, 06 Jan 2005 13:27:33 -0800, Maksim Yevmenkin > wrote: > >> use this page for reference. if driver column says 'hci_usb' then >> device will most likely to work >> >> http://www.holtmann.org/linux/bluetooth/devices.html >> >>> Thanks a lot for your time. >> >> >> sure. sorry, couldn't help you. > > That's the risk of running a free OS. :-) does not meant it does not have to work :) > I just found these in my /var/log/messages. > ng_hci_process_command_complete: ubt0hci - HCI command failed, OGF=0x3, > OCF=0x1a, status=0xc > ng_hci_process_command_complete: ubt0hci - HCI command failed, OGF=0x3, > OCF=0x3, status=0xc > > The first is about a 'write_scan_enable 3' and the last is a 'reset'. > Maybe it is valuable info. well, these are exactly what we saw already. command complete hci event has status code 0xc - command disallowed. nothing new. one last question: device work in windows, right? can you look at windows install and see if there are files that look like firmware? i.e. something like BCM*.{hex|bin}? if there are such files and you are fill like hacking then perhaps you could add device id to the ubtbcmfw(4), recompile and load it. and then use bcmfw(8) to upload windows firmware files into the device. i have no idea if this will work. it could even damage the device, so its up to you :) max From owner-freebsd-bluetooth@FreeBSD.ORG Fri Jan 7 15:37:31 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 4811116A4CE for ; Fri, 7 Jan 2005 15:37:31 +0000 (GMT) Received: from psismtp9.vodafone.es (back.vodafone.es [212.73.32.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B61443D45 for ; Fri, 7 Jan 2005 15:37:28 +0000 (GMT) (envelope-from jjess@freebsd.polarhome.com) Received: from zurich.homeunix.com ([212.166.158.93]) by psismtp9.vodafone.es (ESMTP service) with ESMTP id I9YE2A01.43G for ; Fri, 7 Jan 2005 16:37:22 +0100 Date: Fri, 7 Jan 2005 16:37:05 +0100 From: Jes To: freebsd-bluetooth@freebsd.org Message-ID: <20050107163705.616cbe5f@zurich.homeunix.com> X-Mailer: Sylpheed-Claws 0.9.13 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Motorola E1000 and obexapp 1.4.4 in server mode 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: Fri, 07 Jan 2005 15:37:31 -0000 Hello all: I've just found motorola e1000 suited for vodafone maybe can send files via bluetooth (sort of more or less hidden menu option). Ok, obexapp in client mode works fine (1.4.4) but in server mode i get errors (/var/log/messages). I launch obexapp in server mode : > obexapp -d -s -C 10 then I send the file from phone, my phone finds my computer and try to send ... and remains trying until I cancel. In /var/log/messages two entries : Jan 7 16:34:10 zurich kernel: ng_l2cap_l2ca_receive: ubt0l2cap - invalid L2CAP data packet. Packet too big, length=671, imtu=132, cid=77 Jan 7 16:34:10 zurich kernel: ng_l2cap_l2ca_receive: ubt0l2cap - invalid L2CAP data packet. Packet too big, length=363, imtu=132, cid=77 I can't find information about this... any idea ? Thanks Jes -- Be different: conform. From owner-freebsd-bluetooth@FreeBSD.ORG Fri Jan 7 18:02:32 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 399BF16A4CF for ; Fri, 7 Jan 2005 18:02:32 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9324B43D49 for ; Fri, 7 Jan 2005 18:02:31 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44])j07I2PGF024058; Fri, 7 Jan 2005 12:02:25 -0600 Received: from s228130hz1ew17.apptix-01.savvis.net ([10.146.4.29]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Fri, 7 Jan 2005 12:02:20 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew17.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Fri, 7 Jan 2005 12:02:13 -0600 Message-ID: <41DECEA3.5080500@savvis.net> Date: Fri, 07 Jan 2005 10:02:11 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jes References: <20050107163705.616cbe5f@zurich.homeunix.com> In-Reply-To: <20050107163705.616cbe5f@zurich.homeunix.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 07 Jan 2005 18:02:13.0412 (UTC) FILETIME=[03F15E40:01C4F4E3] X-ECS-MailScanner: No virus is found cc: freebsd-bluetooth@freebsd.org Subject: Re: Motorola E1000 and obexapp 1.4.4 in server mode 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: Fri, 07 Jan 2005 18:02:32 -0000 Jes, > I've just found motorola e1000 suited for vodafone maybe can send files > via bluetooth (sort of more or less hidden menu option). Ok, obexapp in > client mode works fine (1.4.4) but in server mode i get errors > (/var/log/messages). > > I launch obexapp in server mode : > >>obexapp -d -s -C 10 > > then I send the file from phone, my phone finds my computer and try to > send ... and remains trying until I cancel. In /var/log/messages two > entries : > > Jan 7 16:34:10 zurich kernel: ng_l2cap_l2ca_receive: ubt0l2cap - > invalid L2CAP data packet. Packet too big, length=671, imtu=132, cid=77 > Jan 7 16:34:10 zurich kernel: ng_l2cap_l2ca_receive: ubt0l2cap - > invalid L2CAP data packet. Packet too big, length=363, imtu=132, cid=77 hmmm... strange. it appears that phone sends over sized l2cap packets. rfcomm layer sets default mtu of 132 bytes, but remote side (phone) keeps sending much bigger packets, so the stack drops them. > I can't find information about this... any idea ? as usual, i need binary hcidump (produced with -w option). without it i can not tell what is going on. just by looking at two error messages below i'd guess that both sides (phone and pc) seems to disagree on mtu. max From owner-freebsd-bluetooth@FreeBSD.ORG Fri Jan 7 18:54:31 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 2D49916A4CE for ; Fri, 7 Jan 2005 18:54:31 +0000 (GMT) Received: from psismtp8.vodafone.es (back.vodafone.es [212.73.32.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13D7E43D1D for ; Fri, 7 Jan 2005 18:54:30 +0000 (GMT) (envelope-from jjess@homeunix.com) Received: from zurich.homeunix.com ([212.166.158.93]) by psismtp8.vodafone.es (ESMTP service) with ESMTP id I9YN6M02.2AL for ; Fri, 7 Jan 2005 19:54:22 +0100 Received: from jjess by zurich.homeunix.com with local (Exim 4.42 (FreeBSD)) id 1CmzFO-0000dH-M8; Fri, 07 Jan 2005 19:54:06 +0100 Date: Fri, 7 Jan 2005 19:54:06 +0100 From: Jes To: Maksim Yevmenkin Message-ID: <20050107195406.0c76f42e@zurich.homeunix.com> In-Reply-To: <41DECEA3.5080500@savvis.net> References: <20050107163705.616cbe5f@zurich.homeunix.com> <41DECEA3.5080500@savvis.net> X-Mailer: Sylpheed-Claws 0.9.13 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Multipart_Fri__7_Jan_2005_19_54_06_+0100_e2O5Xp/fpP0UEDXb" Sender: Jes cc: freebsd-bluetooth@freebsd.org Subject: Re: Motorola E1000 and obexapp 1.4.4 in server mode 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: Fri, 07 Jan 2005 18:54:31 -0000 --Multipart_Fri__7_Jan_2005_19_54_06_+0100_e2O5Xp/fpP0UEDXb Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline Thanks for replying so fast :) hcidump.bin attached. Bye Jes On Fri, 07 Jan 2005 10:02:11 -0800 Maksim Yevmenkin wrote: > Jes, > > > I've just found motorola e1000 suited for vodafone maybe can send files > > via bluetooth (sort of more or less hidden menu option). Ok, obexapp in > > client mode works fine (1.4.4) but in server mode i get errors > > (/var/log/messages). > > > > I launch obexapp in server mode : > > > >>obexapp -d -s -C 10 > > > > then I send the file from phone, my phone finds my computer and try to > > send ... and remains trying until I cancel. In /var/log/messages two > > entries : > > > > Jan 7 16:34:10 zurich kernel: ng_l2cap_l2ca_receive: ubt0l2cap - > > invalid L2CAP data packet. Packet too big, length=671, imtu=132, cid=77 > > Jan 7 16:34:10 zurich kernel: ng_l2cap_l2ca_receive: ubt0l2cap - > > invalid L2CAP data packet. Packet too big, length=363, imtu=132, cid=77 > > hmmm... strange. it appears that phone sends over sized l2cap packets. > rfcomm layer sets default mtu of 132 bytes, but remote side (phone) > keeps sending much bigger packets, so the stack drops them. > > > I can't find information about this... any idea ? > > as usual, i need binary hcidump (produced with -w option). without it i > can not tell what is going on. just by looking at two error messages > below i'd guess that both sides (phone and pc) seems to disagree on mtu. > > max -- Good day to let down old friends who need help. --Multipart_Fri__7_Jan_2005_19_54_06_+0100_e2O5Xp/fpP0UEDXb Content-Type: application/octet-stream; name=hcidump.bin Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=hcidump.bin DQABAMfY3kFdYQEABAQKLEujihIADAH/AQsAAADH2N5Bb2EBAAEJBAcsS6OKEgAABwABAMfY3kFH dAEABA8EAAEJBA4AAQDH2N5BVNACAAQDCwApACxLo4oSAAEACAAAAMfY3kFm0AIAAQ0IBCkADwAK AAEAx9jeQZjXAgAEIAcsS6OKEgABBgABAMfY3kG53wIABBsDKQAFEQABAMfY3kHE3wIAAikgDAAI AAEAAj0EAAEAQAAVAAAAx9jeQSbgAgACKSAQAAwAAQADPQgASABAAAAAAAAJAAEAx9jeQVrnAgAE DgYBDQgAKQAIAAEAx9jeQcr2AgAEEwUBKQABABUAAQDH2N5B0CEDAAIpIBAADAABAAQ+CABIAAAA AQIABBMAAADH2N5BOCIDAAIpIA4ACgABAAU+BgBAAAAAAAARAAAAx9jeQUAiAwACKSAMAAgAAQAE AQQAQAAAAAgAAQDH2N5BfD0DAAQTBQEpAAEACAABAMfY3kHoRAMABBMFASkAAQATAAEAx9jeQcNQ AwACKSAOAAoAAQAFAQYASAAAAAAAJwABAMfY3kF3XAMAAikgIgAeAEgABgABABk1AxkRBQCANQ8J AAAJAAEJAAIJAAYJAAkAQgAAAMfY3kFbXQMAAikgPQA5AEAABwABADQAMTYALjYAKwkAAAoAAAAC CQABNQMZEQUJAAY1CQllbgkAagkBAAkACTUINQYZEQUJAQAAGgABAMfY3kGs3QMAAikgFQARAEgA BABnAAwAAAACAIA1AwkBAAAIAAEAx9jeQbrdAwAEEwUBKQABACkAAADH2N5Bo94DAAIpICQAIABA AAUAZwAbABg2ABUJAQAlEE9CRVggT2JqZWN0IFB1c2gACAABAMfY3kHRUgQABBMFASkAAQAaAAEA x9jeQcvuBAACKSAVABEASAAEAGkADAAAAAIAgDUDCQAEACoAAADH2N5BtO8EAAIpICUAIQBAAAUA aQAcABk2ABYJAAQ1ETUDGQEANQUZAAMIATUDGQAIABEAAQDH2N5BNWwFAAIpIAwACAABAAI/BAAD AEEACAABAMfY3kFEbAUABBMFASkAAQAVAAAAx9jeQahsBQACKSAQAAwAAQADPwgASQBBAAAAAAAI AAEAx9jeQV+yBQAEEwUBKQABABUAAQDH2N5B0rkFAAIpIBAADAABAARACABJAAAAAQIFCBMAAADH 2N5BS7oFAAIpIA4ACgABAAVABgBBAAAAAAAVAAAAx9jeQVO6BQACKSAQAAwAAQAEAggAQQAAAAEC hAAIAAEAx9jeQQXVBQAEEwUBKQABAAgAAQDH2N5B2dwFAAQTBQEpAAEAFwABAMfY3kGS9AUAAikg EgAOAAEABQIKAEkAAAAAAAEChAANAAEAx9jeQT38BQACKSAIAAQASQADPwEcDQAAAMfY3kGw/AUA AikgCAAEAEEAA3MB1wgAAQDH2N5BY3UGAAQTBQEpAAEAFwABAMfY3kEHfQYAAikgEgAOAEkAA+8V gxEC8AAAmwIAAHAXAAAAx9jeQX19BgACKSASAA4AQQAB7xWBEQLgAACbAgAHqggAAQDH2N5BV5wG AAQTBQEpAAEADQABAMfY3kEKpAYAAikgCAAEAEkACz8BWQ0AAADH2N5BZqQGAAIpIAgABABBAAtz AZIRAAAAx9jeQZqkBgACKSAMAAgAQQAB7wnjBQuMqggAAQDH2N5B2L8GAAQTBQEpAAEACAABAMfY 3kFCxwYABBMFASkAAQASAAEAx9jeQRDPBgACKSANAAkASQAD7wvjBwsMA3ASAAAAx9jeQZLPBgAC KSANAAkAQQAB7wvhBwsMA6oRAAEAx9jeQejWBgACKSAMAAgASQAD7wnhBQuMcAgAAQDH2N5B3TgH AAQTBQEpAAEADgABAMfY3kFVQAcAAikgCQAFAEkAC/8BAYYUAAEAx9jeQfUkCQACKSAPAAsASQAL 7w+AAAcQABQGmg4AAADH2N5BgCUJAAIpIAkABQBBAAn/ASJcFAAAAMfY3kHRKQkAAikgDwALAEEA Ce8PoAAHEQAEAEAIAAEAx9jeQbWCCQAEEwUBKQABAAgAAQDH2N5BF4oJAAQTBQEpAAEADgABAMfY 3kH3kQkAAikgCQAFAEkAC/8BAYY3AAEAytjeQc0/AQACKSAyAC4ASQAL71UCACpCAAUwAAEAHQBp AG0AZwAwADEAcABvAHAALgBqAHAAZwAAwwAA/86aEAAAAMrY3kEdQgEAAikgCwAHAEEACe8HkAAD QAgAAQDK2N5BHH4BAAQTBQEpAAEADgABAMrY3kG6hQEAAikgCQAFAEkAC/8BAYZYAQEAytjeQS6l AQACKSBTAZ8CSQAL7zQFAgQASAP9/9j/4AAQSkZJRgABAgAAZABkAAD/7AARRHVja3kAAQAEAAAA OwAA/+4ADkFkb2JlAGTAAAAAAf/bAIQABwUFBQUFBwUFBwkGBQYJCwgHBwgLDQoKCwoKDRAMDAwM DAwQDA4PEA8ODBQUFRUUFB0cHBwdICAgICAgICAgIAEHBwcNDA0ZEBAZGxYSFhsgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg/8AAEQgBwgJYAwERAAIRAQMR Af/EAMoAAAEFAQEBAQAAAAAAAAAAAAEAAgMEBQYHCAkBAAIDAQEBAAAAAAAAAAAAAAABAgMEBQYH EAABAwMBAwgECgUICAUFAQEBAgMEABEFEiExBkFRYXGBIhMHkaEyFLFCUnKCkqIjMxXB0WI0COHC Q1OTJFUBAQDK2N5BhbcBAAIpEFABNRbw8bJjc4NEJdKjZDYXs1R0hEVVNxEAAgECAwQGBwYGAQME AwAAAAECEQMhMQRBURIFYXGRoTITgbHB0SJCBvDhUnIzFGKCkqIjFfGywtLiUzQW8kNj/9oADAMB AAIRAxEAPwDDv8FecqfXxA0wD20CHA2oAN6ADqO4ddFRUDqvTCgb8nrpgLV10gDe26ioBCuagTDc 0woOCqKhQcFU6kaBBNOoUHBXTQKgQqmIcD6aBBueWioUCFWpioSoWaCLROldOpW0HV07qKkaDtVM KDtWynUVBwUKdRBCrUBQcDUqioOBtvoCgQaYgg8lCYh1z206ioOB7KBUCFXPRQJodc3pioK9AUHB XJ6qCNBwNAqDr366BUFfl5KYqBF70CoOCrbKBEjbhSRY2I200xSjU6GFK94YudjrQ2/MHL9H4L1c nU5V63wvoZWzMFL7XvCaWAEBAMrY3kEV8wMAAikgUwFrAUkAC+/MAtjbt1dCv5aVyNUXaS9wujOW WClVlb6ynYQgrk5KAaHhQpoQ4KpiaDqFMVB2ugVA6vTQKgtdAUCDQFBaundQKgdXqoqKgdVMQdXT QKgb0AK9OoUDqNAg6hTqFAhXN20VCgb89OpGgdXPyUBQIVtpioEKoqKgb0CoLVTCgtRoqFBwULba ZGgQrnoEOCjuFABGom1jQJjhcb7D1UyLPKwq4HSBXGPX0De9MKBv6qAoG9ABvQAr8lAqDr0woIGg QdV6ADegKBvs20CDemA64oAINAg39FMVBwNAUCD006ioOv8A6qKioEGgKB1UxUHBXKKdRMmSv00y LRIFdtBAcDagVBwVTFQcDamJoeDu5b06kQ6qKioOCummA4GmIIJpioG9ADgaYg3NAgg89MQ69Ahw NFRMeD20xBvQKgiaBUHA0CHA0VIsde27fsoAuQYhAAEAytjeQQb7AwACKRAcAFqjupcSSLbanCVC i9a4kdIktLbCxtYdASpPyZoRAAEAytjeQX1iBQACKSAMAAgAAQAGQQQASABAABEAAADK2N5BjWIF AAIpIAwACAABAAdBBABIAEAACAABAMrY3kE9sAUABBMFASkAAQANAAEA6tjeQaz5AwACKSAIAAQA SQALUwG4DQAAAOrY3kFO+gMAAikgCAAEAEEAC3MBkggAAQDq2N5BlSgEAAQTBQEpAAEAEQABAOrY 3kEvMAQAAikgDAAIAAEABkIEAEkAQQARAAAA6tjeQTswBAACKSAMAAgAAQAHQgQASQBBAAgAAQDq 2N5BQ0sEAAQTBQEpAAEABwABAOrY3kE/aw0ABAUEACkAEw== --Multipart_Fri__7_Jan_2005_19_54_06_+0100_e2O5Xp/fpP0UEDXb-- From owner-freebsd-bluetooth@FreeBSD.ORG Fri Jan 7 19:56:29 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 60BDF16A4CE for ; Fri, 7 Jan 2005 19:56:29 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9A4043D45 for ; Fri, 7 Jan 2005 19:56:28 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45])j07JuNGF032127; Fri, 7 Jan 2005 13:56:23 -0600 Received: from s228130hz1ew17.apptix-01.savvis.net ([10.146.4.29]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Fri, 7 Jan 2005 13:56:19 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew17.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Fri, 7 Jan 2005 13:56:09 -0600 Message-ID: <41DEE958.70403@savvis.net> Date: Fri, 07 Jan 2005 11:56:08 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jes References: <20050107163705.616cbe5f@zurich.homeunix.com> <41DECEA3.5080500@savvis.net> <20050107195406.0c76f42e@zurich.homeunix.com> In-Reply-To: <20050107195406.0c76f42e@zurich.homeunix.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 07 Jan 2005 19:56:09.0842 (UTC) FILETIME=[EEC5CD20:01C4F4F2] X-ECS-MailScanner: No virus is found cc: freebsd-bluetooth@freebsd.org Subject: Re: Motorola E1000 and obexapp 1.4.4 in server mode 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: Fri, 07 Jan 2005 19:56:29 -0000 Jes, thanks for the dump. here is what i have found: 1) l2cap channel was successfully created between the phone and pc. both sides have configured mtu's: here phone tells it can accept up to 2053 bytes in single l2cap packet and pc confirms it 1105123527.375250 > ACL data: handle 0x0029 flags 0x02 dlen 16 L2CAP(s): Config req: dcid 0x0049 flags 0x0000 clen 4 MTU 2053 1105123527.375371 < ACL data: handle 0x0029 flags 0x02 dlen 14 L2CAP(s): Config rsp: scid 0x0041 flags 0x0000 result 0 clen 0 here pc tells phone that we can accept up to 132 bytes in single packet and phone confirms it 1105123527.375379 < ACL data: handle 0x0029 flags 0x02 dlen 16 L2CAP(s): Config req: dcid 0x0041 flags 0x0000 clen 4 MTU 132 1105123527.390290 > ACL data: handle 0x0029 flags 0x02 dlen 18 L2CAP(s): Config rsp: scid 0x0049 flags 0x0000 result 0 clen 4 MTU 132 it is my understanding that after this the phone should send all l2cap data on this channel in 132 (or less) bytes chunks. now move to rfcomm channel (which uses l2cap channel as transport) 1105123527.425223 > ACL data: handle 0x0029 flags 0x02 dlen 18 L2CAP(d): cid 0x0049 len 14 [psm 3] RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8 dlci 2 frame_type 0 credit_flow 15 pri 0 ack_timer 0 frame_size 667 max_retrans 0 credits 0 1105123527.425341 < ACL data: handle 0x0029 flags 0x02 dlen 18 L2CAP(d): cid 0x0041 len 14 [psm 3] RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8 dlci 2 frame_type 0 credit_flow 14 pri 0 ack_timer 0 frame_size 667 max_retrans 0 credits 7 here we see the phone telling that it wants to use rfcomm frames of 667 bytes in size (frame_size 667). and the pc confirms that its fine. now, first notice that rfcomm frame_size of 667 bytes is bigger then l2cap mtu of 132 bytes. so, it is *my* understanding of the spec that, in this case, each rfcomm frame of 667 bytes should be transmitted as series of l2cap packets and each l2cap packet should not exceed 132 bytes in size. rfcomm layer must re-assemble entire 667 bytes (or less) frame out of 132 bytes chunks and then process it. what happens next is you are trying to push 'img01pop.jpg' file which is 65486 bytes in size, we i see 1105123530.107822 > ACL data: handle 0x0029 flags 0x02 dlen 339 1105123530.112517 > ACL data: handle 0x0029 flags 0x01 dlen 336 L2CAP(d): cid 0x0049 len 671 [psm 3] RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 666 fcs 0x9a OBEX: Put cmd(c): len 1024 (continue) Body (0x48) = Sequence length 1018 [ .... ] first we see two l2cap chunks of 339 and 336 bytes in size respectively (they were segmented at baseband level). the weird thing is that original l2cap packet was 671 bytes in size! remember we previously configured l2cap channel to *not* accept l2cap packets bigger then 132 bytes and phone has accepted it. at this point i'm not sure who is at fault here. after reading the spec i was not sure if *entire* rfcomm frame must fit into l2cap mtu, or segmentation is allowed. i need to re-read the spec and look at more dumps from different bluetooth devices. it seems to me that if l2cap channel was configured to use 132 bytes mtu then device should not send larger packets, so my first impression is that the phone has a bug. as workaround you might want to try this: 1) edit /sys/netgraph/bluetooth/include/ng_btsocket_rfcomm.h file and change RFCOMM_DEFAULT_MTU from 127 to 667. 2) re-compile ng_btsocket module, i.e. # cd /sys/modules/netgraph/bluetooth/socket/ # make depend # make # make install 3) reboot and try again thanks, max Jes wrote: > Thanks for replying so fast :) > > hcidump.bin attached. > > Bye > > Jes > > > On Fri, 07 Jan 2005 10:02:11 -0800 > Maksim Yevmenkin wrote: > > >>Jes, >> >> >>>I've just found motorola e1000 suited for vodafone maybe can send > > files > >>>via bluetooth (sort of more or less hidden menu option). Ok, obexapp > > in > >>>client mode works fine (1.4.4) but in server mode i get errors >>>(/var/log/messages). >>> >>>I launch obexapp in server mode : >>> >>> >>>>obexapp -d -s -C 10 >>> >>>then I send the file from phone, my phone finds my computer and try > > to > >>>send ... and remains trying until I cancel. In /var/log/messages two >>>entries : >>> >>>Jan 7 16:34:10 zurich kernel: ng_l2cap_l2ca_receive: ubt0l2cap - >>>invalid L2CAP data packet. Packet too big, length=671, imtu=132, > > cid=77 > >>>Jan 7 16:34:10 zurich kernel: ng_l2cap_l2ca_receive: ubt0l2cap - >>>invalid L2CAP data packet. Packet too big, length=363, imtu=132, > > cid=77 > >>hmmm... strange. it appears that phone sends over sized l2cap packets. > > >>rfcomm layer sets default mtu of 132 bytes, but remote side (phone) >>keeps sending much bigger packets, so the stack drops them. >> >> >>>I can't find information about this... any idea ? >> >>as usual, i need binary hcidump (produced with -w option). without it > > i > >>can not tell what is going on. just by looking at two error messages >>below i'd guess that both sides (phone and pc) seems to disagree on > > mtu. > >>max > > > From owner-freebsd-bluetooth@FreeBSD.ORG Fri Jan 7 21:37:42 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 B8AE816A4CE for ; Fri, 7 Jan 2005 21:37:42 +0000 (GMT) Received: from psismtp7.vodafone.es (back.vodafone.es [212.73.32.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8F1E43D58 for ; Fri, 7 Jan 2005 21:37:39 +0000 (GMT) (envelope-from jjess@homeunix.com) Received: from zurich.homeunix.com ([212.166.255.67]) by psismtp7.vodafone.es (ESMTP service) with ESMTP id I9YUQQ00.LDU for ; Fri, 7 Jan 2005 22:37:38 +0100 Received: from jjess by zurich.homeunix.com with local (Exim 4.42 (FreeBSD)) id 1Cn1nR-000ET9-TZ; Fri, 07 Jan 2005 22:37:25 +0100 Date: Fri, 7 Jan 2005 22:37:25 +0100 From: Jes To: Maksim Yevmenkin Message-ID: <20050107223725.15a4554d@zurich.homeunix.com> In-Reply-To: <41DEE958.70403@savvis.net> References: <20050107163705.616cbe5f@zurich.homeunix.com> <41DECEA3.5080500@savvis.net> <20050107195406.0c76f42e@zurich.homeunix.com> <41DEE958.70403@savvis.net> X-Mailer: Sylpheed-Claws 0.9.13 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: Jes cc: freebsd-bluetooth@freebsd.org Subject: Re: [spam] Re: Motorola E1000 and obexapp 1.4.4 in server mode 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: Fri, 07 Jan 2005 21:37:42 -0000 > at this point i'm not sure who is at fault here. after reading the spec > i was not sure if *entire* rfcomm frame must fit into l2cap mtu, or > segmentation is allowed. i need to re-read the spec and look at more > dumps from different bluetooth devices. it seems to me that if l2cap > channel was configured to use 132 bytes mtu then device should not send > larger packets, so my first impression is that the phone has a bug. > > as workaround you might want to try this: > > 1) edit /sys/netgraph/bluetooth/include/ng_btsocket_rfcomm.h file and > change RFCOMM_DEFAULT_MTU from 127 to 667. > > 2) re-compile ng_btsocket module, i.e. > > # cd /sys/modules/netgraph/bluetooth/socket/ > # make depend > # make > # make install > > 3) reboot and try again > No, it doesn't work nor obexapp in client mode with that change. It really doesn't matter because of I can retrieve files from pc in client mode... Thanks in deed Max Jes -- If only God would give me some clear sign! Like making a large deposit in my name at a Swiss bank. -- Woody Allen, "Without Feathers" From owner-freebsd-bluetooth@FreeBSD.ORG Fri Jan 7 23:03:18 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 E895616A4CE; Fri, 7 Jan 2005 23:03:18 +0000 (GMT) Received: from vbook.fbsd.ru (user164.hovrino.net [82.179.232.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E93E43D3F; Fri, 7 Jan 2005 23:03:18 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.43 (FreeBSD)) id 1Cn38N-0000Nb-PT; Sat, 08 Jan 2005 02:03:07 +0300 From: Vladimir Grebenschikov To: Julian Elischer In-Reply-To: <41D67753.60202@elischer.org> References: <20041228010938.GA39686@freebsd3.cimlogic.com.au> <20041230.111631.13597845.imp@bsdimp.com> <1104542138.3084.9.camel@localhost> <41D67753.60202@elischer.org> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Sat, 08 Jan 2005 02:03:07 +0300 Message-Id: <1105138987.1401.5.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.0FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov cc: Randy Bush cc: bluetooth cc: FreeBSD Current cc: "M. Warner Losh" Subject: Re: USB problems X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: vova@fbsd.ru List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jan 2005 23:03:19 -0000 =F7 =D3=C2, 01/01/2005 =D7 02:11 -0800, Julian Elischer =D0=C9=DB=C5=D4: > Vladimir Grebenschikov wrote: > > =F7 =D0=D4, 31/12/2004 =D7 05:05 -1000, Randy Bush =D0=C9=DB=C5=D4: > >=20 > >>possibly related? > >> > >>just so you know, on a thinkpad t41 with any current in the last > >>few weeks, i kernel panic on boot if a usb device is not plugged > >>in. turning off acpi also allows boot. see > >> > >> > >> > >>i can help debug if anyone is on the trail > >=20 > >=20 > > I have also problems with USB on recent current (previous was few weeks > > old). > >=20 >=20 > the most salient thiing you could do is find the date of the problem by c= hecking=20 > out sys/dev/usb on dec 9 and seeing if that fixes it (you said dec 9 was= ok) > and if so, gradually moving it forward using a binary search and narrowin= g in on=20 > the commit that broke it. So far I tracked it: it works on -D '2004-12-08 12:00' and does not works with -D '2004-12-09 00:00' I guess time is by MSK timezone (my local time). There are a lot of changes between these dates. > Is it an ohci or uhci (or ehci) usb inerface? I think both. It strikes when only ehci umass device attached or when uhci mouse or bluetooth dongle connected. usb0: on uhci0 usb0: USB revision 1.0 usb1: on uhci1 usb1: USB revision 1.0 usb2: on uhci2 usb2: USB revision 1.0 ehci_pci_attach: companion usb0 ehci_pci_attach: companion usb1 ehci_pci_attach: companion usb2 usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 Looks like it is not USB-only problem, I have revert only USB code and it does not helps. So I suppose it is some kind of locking problem. --=20 Vladimir B. Grebenchikov vova@fbsd.ru