From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 14 10:37:28 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 02E4816A41F; Mon, 14 Nov 2005 10:37:28 +0000 (GMT) (envelope-from past@ebs.gr) Received: from fly.ebs.gr (fly.ebs.gr [62.103.84.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AD6443D45; Mon, 14 Nov 2005 10:37:26 +0000 (GMT) (envelope-from past@ebs.gr) Received: from ebs.gr (root@hal.ebs.gr [10.1.1.2]) by fly.ebs.gr (8.12.9p1/8.12.9) with ESMTP id jAEAb79V058295; Mon, 14 Nov 2005 12:37:07 +0200 (EET) (envelope-from past@ebs.gr) Received: from [10.1.1.158] (pc158.ebs.gr [10.1.1.158]) by ebs.gr (8.13.3/8.12.11) with ESMTP id jAEAbE69048965; Mon, 14 Nov 2005 12:37:18 +0200 (EET) (envelope-from past@ebs.gr) Message-ID: <437868C8.10508@ebs.gr> Date: Mon, 14 Nov 2005 12:36:56 +0200 From: Panagiotis Astithas Organization: EBS Ltd. User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051106) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Maksim Yevmenkin References: <43519460.1090605@ebs.gr> <1129491219.1616.18.camel@localhost> <4375246E.3050303@savvis.net> <20051111.165103.110975378.imp@bsdimp.com> <20051112000929.GB10648@odin.ac.hmc.edu> <4375681B.6030808@savvis.net> <20051112175541.GA18302@odin.ac.hmc.edu> <437667D4.5030205@savvis.net> In-Reply-To: <437667D4.5030205@savvis.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Brooks Davis , freebsd-bluetooth@freebsd.org, freebsd-rc@freebsd.org, "M. Warner Losh" Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 10:37:28 -0000 Maksim Yevmenkin wrote: > Brooks, > > [...] > >> Instead, I would suggest creating a port that installs the firmware >> and a /usr/local/etc/devd/ script simliar to the iwi-firmware port. > > > ok. that sounds fine to me. does anyone have experience with this like > this? i mean do i have to contact 3com and broadcom and obtain some sort > of permission for this? how does this work? > > linux bluez has rpm that contains firmware. it seems like they have > contacted broadcom, because they have firmware files in their cvs > > http://cvs.sourceforge.net/viewcvs.py/bluez/firmware/broadcom/ > > can i legally get those files and include them into freebsd port's > collection? if this is going to lead to too much corporate brouhaha then > perhaps i should leave it as it is. bcmfw(8) and bt3cfw(8) man pages > already tell users where they can get the firmware. You could just have the port fetch the files from sourceforge and avoid including any copyrighted material in the ports repository. Regards, Panagiotis From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 14 14:15:56 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 D840416A41F for ; Mon, 14 Nov 2005 14:15:56 +0000 (GMT) (envelope-from barner@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 1B03143D45 for ; Mon, 14 Nov 2005 14:15:55 +0000 (GMT) (envelope-from barner@gmx.de) Received: (qmail invoked by alias); 14 Nov 2005 14:15:54 -0000 Received: from unknown (EHLO zi025.glhnet.mhn.de) [129.187.19.157] by mail.gmx.net (mp031) with SMTP; 14 Nov 2005 15:15:54 +0100 X-Authenticated: #147403 Received: by zi025.glhnet.mhn.de (Postfix, from userid 1000) id C2EACC160; Mon, 14 Nov 2005 15:15:52 +0100 (CET) Date: Mon, 14 Nov 2005 15:15:52 +0100 From: Simon Barner To: Maksim Yevmenkin Message-ID: <20051114141552.GA2031@zi025.glhnet.mhn.de> References: <43519460.1090605@ebs.gr> <1129491219.1616.18.camel@localhost> <4375246E.3050303@savvis.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FL5UXtIhxfXey3p5" Content-Disposition: inline In-Reply-To: <4375246E.3050303@savvis.net> User-Agent: Mutt/1.5.10i X-Y-GMX-Trusted: 0 Cc: freebsd-bluetooth@freebsd.org Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 14:15:57 -0000 --FL5UXtIhxfXey3p5 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Maksim Yevmenkin wrote: > All, >=20 > does anyone have any objections to the /etc/devd.conf patch located at >=20 > http://people.freebsd.org/~emax/devd.conf.diff.txt >=20 > this patch will add support for a usb bluetooth dongles to devd(8). Great! This + http://people.freebsd.org/~emax/bluetooth-rc-4.diff.txt makes my usb bt dongle "just work" (on RELENG_6). FYI, it's a "Level One MDU-0001USB": ubt0: vendor 0x0a12 product 0x0001, rev 1.10/11.20, addr 2 ubt0: Interface 0 endpoints: interrupt=3D0x81, bulk-in=3D0x82, bulk-out=3D0= x2 ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=3D0x83, isoc-out=3D0x3;= wMaxPacketSize=3D49; nframes=3D6, buffer size=3D294 Mobile (Siemens S65) to PC file transfer works just fine with the following /etc/rc.local (I proably should have them launched by devd, but the dongle is always plugged in anyway). /usr/sbin/hcsecd=20 /usr/sbin/sdpd=20 /usr/local/bin/obexapp -C 1 -r /var/spool/obex -s -S Now looking for a convenient way to sync contacts... --=20 Best regards / Viele Gr=FC=DFe, barner@FreeBSD.= org Simon Barner barner@gmx.de --FL5UXtIhxfXey3p5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDeJwYCkn+/eutqCoRAvgKAJ9J9puLepH6asvsu3BBQbVyF/oS1gCdFICU m2NUfi+58Jz/3l5BG8Z+RKo= =SrA3 -----END PGP SIGNATURE----- --FL5UXtIhxfXey3p5-- From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 14 17:18:07 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 C74BB16A420; Mon, 14 Nov 2005 17:18:07 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 326E043D46; Mon, 14 Nov 2005 17:18:07 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id jAEHI1Hk005487; Mon, 14 Nov 2005 09:18:01 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id jAEHI0Of005486; Mon, 14 Nov 2005 09:18:00 -0800 Date: Mon, 14 Nov 2005 09:18:00 -0800 From: Brooks Davis To: Panagiotis Astithas Message-ID: <20051114171800.GA1928@odin.ac.hmc.edu> References: <43519460.1090605@ebs.gr> <1129491219.1616.18.camel@localhost> <4375246E.3050303@savvis.net> <20051111.165103.110975378.imp@bsdimp.com> <20051112000929.GB10648@odin.ac.hmc.edu> <4375681B.6030808@savvis.net> <20051112175541.GA18302@odin.ac.hmc.edu> <437667D4.5030205@savvis.net> <437868C8.10508@ebs.gr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline In-Reply-To: <437868C8.10508@ebs.gr> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: Brooks Davis , freebsd-bluetooth@freebsd.org, freebsd-rc@freebsd.org, "M. Warner Losh" Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 17:18:07 -0000 --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 14, 2005 at 12:36:56PM +0200, Panagiotis Astithas wrote: > Maksim Yevmenkin wrote: > >Brooks, > > > >[...] > > > >>Instead, I would suggest creating a port that installs the firmware > >>and a /usr/local/etc/devd/ script simliar to the iwi-firmware port. > > > > > >ok. that sounds fine to me. does anyone have experience with this like= =20 > >this? i mean do i have to contact 3com and broadcom and obtain some sort= =20 > >of permission for this? how does this work? > > > >linux bluez has rpm that contains firmware. it seems like they have=20 > >contacted broadcom, because they have firmware files in their cvs > > > >http://cvs.sourceforge.net/viewcvs.py/bluez/firmware/broadcom/ > > > >can i legally get those files and include them into freebsd port's=20 > >collection? if this is going to lead to too much corporate brouhaha then= =20 > >perhaps i should leave it as it is. bcmfw(8) and bt3cfw(8) man pages=20 > >already tell users where they can get the firmware. >=20 > You could just have the port fetch the files from sourceforge and avoid= =20 > including any copyrighted material in the ports repository. Yes. Just make sure to set the RESTRICTED variable to cause the distfiles and packages to not be distributed. I'd suggest starting with the net/ipw-firmware port (it's a little overly complex as it's the master port for net/iwi-firmware, but it's got the basics.) -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDeMbHXY6L6fI4GtQRAqlxAJ0dqYkSpwbwp3RKzj52c/1mkixWagCgg0wM 0HfW8FcwIOgWIELWE1TTsZk= =xnXP -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm-- From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 15 00:08:21 2005 Return-Path: X-Original-To: freebsd-bluetooth@FreeBSD.org 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 3FCBE16A41F; Tue, 15 Nov 2005 00:08:21 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id C37DC43D49; Tue, 15 Nov 2005 00:08:20 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jAF08JJ30902; Mon, 14 Nov 2005 19:08:19 -0500 Message-ID: <437926F2.9000709@savvis.net> Date: Mon, 14 Nov 2005 16:08:18 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Simon Barner References: <43519460.1090605@ebs.gr> <1129491219.1616.18.camel@localhost> <4375246E.3050303@savvis.net> <20051114141552.GA2031@zi025.glhnet.mhn.de> In-Reply-To: <20051114141552.GA2031@zi025.glhnet.mhn.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@FreeBSD.org Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 00:08:21 -0000 Simon, >>does anyone have any objections to the /etc/devd.conf patch located at >> >>http://people.freebsd.org/~emax/devd.conf.diff.txt >> >>this patch will add support for a usb bluetooth dongles to devd(8). > > Great! This + http://people.freebsd.org/~emax/bluetooth-rc-4.diff.txt > makes my usb bt dongle "just work" (on RELENG_6). great. thanks for the information > FYI, it's a "Level One MDU-0001USB": > > ubt0: vendor 0x0a12 product 0x0001, rev 1.10/11.20, addr 2 > ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 > ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, buffer size=294 ok > Mobile (Siemens S65) to PC file transfer works just fine with the > following /etc/rc.local (I proably should have them launched by devd, > but the dongle is always plugged in anyway). > > /usr/sbin/hcsecd > /usr/sbin/sdpd > /usr/local/bin/obexapp -C 1 -r /var/spool/obex -s -S in -current /usr/sbin/hcsecd and /usr/sbin/sdpd should be started by separate scripts /etc/rc.d/hcsecd and /etc/rc.d/sdpd. all you need to do is to put hcsecd_enable="YES" sdpd_enable="YES" into your /etc/rc.conf and you should be done. please do not forget to kldload ng_btsocket(4) module (from loader.conf) or else these will not start. there is no reason to start/stop hcsecd(8) and sdpd(8) when device is attached/detached. if you plan on using bluetooth you just may have run these all the time. both daemons listen on wildcard addresses, so they should not be affected attach/detach events. > Now looking for a convenient way to sync contacts... http://lists.freebsd.org/pipermail/freebsd-bluetooth/2005-September/000422.html there is a mobile_backup.sh script that you might find useful. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 15 16:23:04 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 C094616A41F for ; Tue, 15 Nov 2005 16:23:04 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E3DC43D58 for ; Tue, 15 Nov 2005 16:23:01 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id jAFGN095073726; Tue, 15 Nov 2005 10:23:01 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <437A0B5D.1000205@centtech.com> Date: Tue, 15 Nov 2005 10:22:53 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051021 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Maksim Yevmenkin References: <431F388E.2010204@centtech.com> <43217D56.3050508@centtech.com> <4321D6C4.6050300@savvis.net> <432AC7E9.5060206@centtech.com> <433F4B50.1050108@centtech.com> <433F62F7.3060607@centtech.com> <43427296.6090404@centtech.com> <4342BC20.8000001@savvis.net> <4342CEEB.5010501@centtech.com> <4342F41A.1050706@savvis.net> In-Reply-To: <4342F41A.1050706@savvis.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1173/Tue Nov 15 06:43:30 2005 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-bluetooth@freebsd.org Subject: Re: Bluetooth mouse breaks on -current X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 16:23:05 -0000 Maksim Yevmenkin wrote: > Eric, > > [...] > >>> this looks like the mouse is loosing the connection and trying to >>> re-connect. >> >> >> Correct - the mouse would just stop working while I was using it, and >> this particular mouse needs a button click to tell it to re-connect >> (as if it was in power save mode). The reconnects you see, are me >> clicking buttons to get it to come back alive. > > > fine > >>>>>> [died completely at that vkbd message] >>>>>> >>>>>> Oct 1 21:01:16 neutrino su: anderson to root on /dev/ttyp2 >>>>>> Oct 1 21:06:22 neutrino kernel: ng_hci_process_command_timeout: >>>>>> ubt0hci - unable to complete HCI command OGF=0x1, OCF=0x1. Timeout >>>>>> Oct 1 21:06:22 neutrino kernel: ubt_request_complete2: ubt0 - >>>>>> Control request failed. TIMEOUT (15) >>>>>> Oct 1 21:07:39 neutrino kernel: ng_hci_process_command_timeout: >>>>>> ubt0hci - unable to complete HCI command OGF=0x3, OCF=0x3. Timeout >>>>>> Oct 1 21:07:39 neutrino kernel: ubt_request_complete2: ubt0 - >>>>>> Control request failed. TIMEOUT (15) >>> >>> >>> this is bad. something screwed up at usb level. basically we are >>> trying to send commands to the local device (not mouse) and it does >>> not respond. >> >> >> I agree - almost seems as though it's a faulty usb bluetooth adapter. > > > well, may be. may be not. since the load is high during buildworld i > wonder if this has something to do with interrupt latency. > >>> what is the model/make of the local bluetooth device (not mouse)? >> >> >> It's a built-in bluetooth adapter in my Sony laptop: >> >> ubt0: ALPS UGX, rev 1.10/11.68, addr 3 >> ubt0: ALPS UGX, rev 1.10/11.68, addr 3 >> ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 >> ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, >> isoc-out=0x3; wMaxPacketSize=49; nframes=6, buffer size=294 > > > thanks > >>> was buildworld still running? >> >> >> Yes >> >>> if buildworld was running can you tell what the load was? >> >> >> I can't recall what the load was at the time, but the CPU was close to >> 100% utilized. > > > hmm... > >>> what scheduler are you using BSD or ULE? >> >> >> ULE > > > can you please try BSD? just to see if it makes any difference. also try > to disable PREEMPTION (with both ULE and BSD). > >>> are you running with WITNESS enabled? >> >> >> No. > > > good > >>> also how fast is the cpu on your machine? >> >> >> 1500MHZ. > > > hmm... 1.5ghz, i wonder why your cpu is close to 100% during buildworld. > it would be nice to know how much time system spends in "sys" etc. you > have pretty fast cpu, so its kinda strange. > >> Full dmesg, and other info here: >> >> http://www.googlebit.com/freebsd/ >> >> Look for the most recent date. > > > thanks > >>>>>> Oct 1 21:09:33 neutrino kernel: ubt0: detached >>> >>> >>> ok, this is really bad. usb device should not just detach by itself >>> (unless you pull it out). >> >> >> Actually, that was me flipping the switch (enable/disable wireless, >> including bluetooth) on the laptop. > > > ah, i see. For what it's worth, I've been using a new Logitech Bluetooth mouse now for a month, with absolutely no problems. I think it was the mouse causing all my troubles. Thanks again for the great work (and also the recent rc.d commits!) Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 16 09:46:07 2005 Return-Path: X-Original-To: freebsd-bluetooth@FreeBSD.org 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 927E816A41F for ; Wed, 16 Nov 2005 09:46:07 +0000 (GMT) (envelope-from barner@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id C411143D46 for ; Wed, 16 Nov 2005 09:46:06 +0000 (GMT) (envelope-from barner@gmx.de) Received: (qmail invoked by alias); 16 Nov 2005 09:46:05 -0000 Received: from unknown (EHLO zi025.glhnet.mhn.de) [129.187.19.157] by mail.gmx.net (mp033) with SMTP; 16 Nov 2005 10:46:05 +0100 X-Authenticated: #147403 Received: by zi025.glhnet.mhn.de (Postfix, from userid 1000) id 98284C13A; Wed, 16 Nov 2005 10:46:04 +0100 (CET) Date: Wed, 16 Nov 2005 10:46:04 +0100 From: Simon Barner To: Maksim Yevmenkin Message-ID: <20051116094604.GB6251@zi025.glhnet.mhn.de> References: <43519460.1090605@ebs.gr> <1129491219.1616.18.camel@localhost> <4375246E.3050303@savvis.net> <20051114141552.GA2031@zi025.glhnet.mhn.de> <437926F2.9000709@savvis.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9amGYk9869ThD9tj" Content-Disposition: inline In-Reply-To: <437926F2.9000709@savvis.net> User-Agent: Mutt/1.5.10i X-Y-GMX-Trusted: 0 Cc: freebsd-bluetooth@FreeBSD.org Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 09:46:07 -0000 --9amGYk9869ThD9tj Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > in -current /usr/sbin/hcsecd and /usr/sbin/sdpd should be started by=20 > separate scripts /etc/rc.d/hcsecd and /etc/rc.d/sdpd. all you need to do= =20 > is to put >=20 > hcsecd_enable=3D"YES" > sdpd_enable=3D"YES" Oh yes, I totally forgot about them. They also work as exspected on RELENG_6. >=20 > into your /etc/rc.conf and you should be done. please do not forget to=20 > kldload ng_btsocket(4) module (from loader.conf) or else these will not= =20 > start. I also needed to manually pre-load ng_btsocket.ko for the bluetooth rc script, so it has already been in my loader.conf. >=20 > there is no reason to start/stop hcsecd(8) and sdpd(8) when device is=20 > attached/detached. if you plan on using bluetooth you just may have run= =20 > these all the time. >=20 > both daemons listen on wildcard addresses, so they should not be=20 > affected attach/detach events. Thanks, good to know. >=20 > >Now looking for a convenient way to sync contacts... >=20 > http://lists.freebsd.org/pipermail/freebsd-bluetooth/2005-September/00042= 2.html >=20 > there is a mobile_backup.sh script that you might find useful. Great, it worked just fine :-) --=20 Best regards / Viele Gr=FC=DFe, barner@FreeBSD.= org Simon Barner barner@gmx.de --9amGYk9869ThD9tj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDev/cCkn+/eutqCoRAlzuAJ4+3mKSZWeDEvnKRb/cxpDmFWoZJgCgxtql R0l13ux5TUDvRvoegUuVKF0= =ZrD6 -----END PGP SIGNATURE----- --9amGYk9869ThD9tj-- From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 16 13:04:34 2005 Return-Path: X-Original-To: bluetooth@freebsd.org 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 4292216A434 for ; Wed, 16 Nov 2005 13:04:34 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4BEA43D46 for ; Wed, 16 Nov 2005 13:04:33 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id jAGD4W5I094101 for ; Wed, 16 Nov 2005 07:04:32 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <437B2E58.50709@centtech.com> Date: Wed, 16 Nov 2005 07:04:24 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051021 X-Accept-Language: en-us, en MIME-Version: 1.0 To: bluetooth Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1176/Tue Nov 15 14:47:39 2005 on mh2.centtech.com X-Virus-Status: Clean Cc: Subject: No route to host for bluetooth devices X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 13:04:34 -0000 Well, I've recently updated to the latest current, and while yesterday everything seemed to be working fine, this morning after booting up (no changes were made anywhere, except rebooting), I cannot use bluetooth devices. Here's some quick info: snippets from /var/log/messages: Nov 16 06:30:58 neutrino kernel: ubt0: ALPS UGX, rev 1.10/11.68, addr 3 Nov 16 06:30:58 neutrino kernel: ubt0: ALPS UGX, rev 1.10/11.68, addr 3 Nov 16 06:30:58 neutrino kernel: ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 Nov 16 06:30:58 neutrino kernel: ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, buffer size=294 Nov 16 06:31:08 neutrino kernel: ng_hci_process_command_timeout: ubt0hci - unable to complete HCI command OGF=0x3, OCF=0x3. Timeout Nov 16 06:31:10 neutrino kernel: kbd: new array size 4 Nov 16 06:31:10 neutrino kernel: kbd1 at vkbd0 Id Refs Address Size Name 1 36 0xc0400000 767fbc kernel 2 1 0xc0b68000 5750 vesa.ko 3 2 0xc0b6e000 1c714 linux.ko 4 1 0xc0b8b000 5ecc snd_ich.ko 5 2 0xc0b91000 269b0 sound.ko 6 5 0xc0bb8000 232e8 usb.ko 7 1 0xc0bdc000 5e08 ugen.ko 8 1 0xc0be2000 40a8 ums.ko 9 1 0xc0be7000 7408 umass.ko 10 1 0xc0bef000 550c acpi_video.ko 11 1 0xc0bf5000 1e55c radeon.ko 12 2 0xc0c14000 10f18 drm.ko 13 1 0xc0c25000 2730 acpi_sony.ko 14 1 0xc0c28000 2e98 wlan_wep.ko 15 1 0xc0c2b000 9454 cpufreq.ko 16 6 0xc0c35000 d478 netgraph.ko 17 1 0xc0c43000 8550 ng_ubt.ko 18 1 0xc0c4c000 68f8 vkbd.ko 19 1 0xc53be000 6000 linprocfs.ko 20 3 0xc5f7e000 2000 ng_bluetooth.ko 21 1 0xc5f80000 d000 ng_hci.ko 22 1 0xc5fb8000 10000 ng_l2cap.ko 23 1 0xc5fc8000 1b000 ng_btsocket.ko 24 1 0xc5fe3000 4000 ng_socket.ko # bthidcontrol -a logimouse query Could not perform SDP query on the device 00:07:61:31:27:15. No route to host (65) in /etc/rc.conf: hcsecd_enable="YES" sdpd_enable="YES" and in /etc/rc.local: /usr/sbin/bthidd and just now I did: /etc/rc.d/bluetooth stop ubt0 /etc/rc.d/bluetooth start ubt0 and it started working, so I think my message is bogus, except for one question: am I supposed to have a bluetooth_enable="YES" in /etc/rc.conf? I think that's the problem.. I'm still sending this message for the archives. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 16 15:40:52 2005 Return-Path: X-Original-To: bluetooth@freebsd.org 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 EE88716A41F for ; Wed, 16 Nov 2005 15:40:52 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C2FA43D78 for ; Wed, 16 Nov 2005 15:40:47 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [192.168.1.254] (really [70.32.199.60]) by mta9.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051116154047.UFIF17844.mta9.adelphia.net@[192.168.1.254]>; Wed, 16 Nov 2005 10:40:47 -0500 Message-ID: <437B52FF.9040407@savvis.net> Date: Wed, 16 Nov 2005 07:40:47 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <437B2E58.50709@centtech.com> In-Reply-To: <437B2E58.50709@centtech.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: bluetooth Subject: Re: No route to host for bluetooth devices X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 15:40:53 -0000 Eric, > Well, I've recently updated to the latest current, and while yesterday > everything seemed to be working fine, this morning after booting up (no > changes were made anywhere, except rebooting), I cannot use bluetooth > devices. Here's some quick info: > > snippets from /var/log/messages: > Nov 16 06:30:58 neutrino kernel: ubt0: ALPS UGX, rev 1.10/11.68, addr 3 > Nov 16 06:30:58 neutrino kernel: ubt0: ALPS UGX, rev 1.10/11.68, addr 3 > Nov 16 06:30:58 neutrino kernel: ubt0: Interface 0 endpoints: > interrupt=0x81, bulk-in=0x82, bulk-out=0x2 > Nov 16 06:30:58 neutrino kernel: ubt0: Interface 1 (alt.config 5) > endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, > buffer size=294 > Nov 16 06:31:08 neutrino kernel: ng_hci_process_command_timeout: ubt0hci > - unable to complete HCI command OGF=0x3, OCF=0x3. Timeout device initialization failed. reset command has timed out. there should be message like "Unable to setup Bluetooth stack for device" somewhere in your logs. > # bthidcontrol -a logimouse query > Could not perform SDP query on the device 00:07:61:31:27:15. No route to > host (65) yes, and this is because stack was not set properly and as far as system concerns you do not have active bluetooth devices. its kinda like using the network without network card. > and just now I did: > /etc/rc.d/bluetooth stop ubt0 > /etc/rc.d/bluetooth start ubt0 > > and it started working, so I think my message is bogus, except for one ok. you basically restart the device and now it works. are you getting "ng_hci_process_command_timeout" error when you boot with device attached? > question: am I supposed to have a bluetooth_enable="YES" in > /etc/rc.conf? I think that's the problem.. no, that is not your problem. the fact that you got the error means that /etc/rc.d/bluetooth was called and tried to setup the stack. like i said, your problem is that device did not respond to "reset" command for the very first time. i will cvsup to -current today and try to reproduce it. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 16 16:23:07 2005 Return-Path: X-Original-To: bluetooth@freebsd.org 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 899BA16A41F for ; Wed, 16 Nov 2005 16:23:07 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33DA843D45 for ; Wed, 16 Nov 2005 16:23:06 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id jAGGN6Hb097449; Wed, 16 Nov 2005 10:23:06 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <437B5CE2.5000601@centtech.com> Date: Wed, 16 Nov 2005 10:22:58 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051021 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Maksim Yevmenkin References: <437B2E58.50709@centtech.com> <437B52FF.9040407@savvis.net> In-Reply-To: <437B52FF.9040407@savvis.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1176/Tue Nov 15 14:47:39 2005 on mh2.centtech.com X-Virus-Status: Clean Cc: bluetooth Subject: Re: No route to host for bluetooth devices X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 16:23:07 -0000 Maksim Yevmenkin wrote: > Eric, > >> Well, I've recently updated to the latest current, and while yesterday >> everything seemed to be working fine, this morning after booting up >> (no changes were made anywhere, except rebooting), I cannot use >> bluetooth devices. Here's some quick info: >> >> snippets from /var/log/messages: >> Nov 16 06:30:58 neutrino kernel: ubt0: ALPS UGX, rev 1.10/11.68, addr 3 >> Nov 16 06:30:58 neutrino kernel: ubt0: ALPS UGX, rev 1.10/11.68, addr 3 >> Nov 16 06:30:58 neutrino kernel: ubt0: Interface 0 endpoints: >> interrupt=0x81, bulk-in=0x82, bulk-out=0x2 >> Nov 16 06:30:58 neutrino kernel: ubt0: Interface 1 (alt.config 5) >> endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, >> buffer size=294 >> Nov 16 06:31:08 neutrino kernel: ng_hci_process_command_timeout: >> ubt0hci - unable to complete HCI command OGF=0x3, OCF=0x3. Timeout > > > device initialization failed. reset command has timed out. there should > be message like > > "Unable to setup Bluetooth stack for device" > > somewhere in your logs. I could not find that message anywhere (dmesg, or /var/log/messages). Only thing I saw was: WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() which I believe is harmless. >> # bthidcontrol -a logimouse query >> Could not perform SDP query on the device 00:07:61:31:27:15. No route >> to host (65) > > > yes, and this is because stack was not set properly and as far as system > concerns you do not have active bluetooth devices. its kinda like using > the network without network card. > >> and just now I did: >> /etc/rc.d/bluetooth stop ubt0 >> /etc/rc.d/bluetooth start ubt0 >> >> and it started working, so I think my message is bogus, except for one > > > ok. you basically restart the device and now it works. are you getting > "ng_hci_process_command_timeout" error when you boot with device attached? Yes - see the log message output above. >> question: am I supposed to have a bluetooth_enable="YES" in >> /etc/rc.conf? I think that's the problem.. > > > no, that is not your problem. the fact that you got the error means that > /etc/rc.d/bluetooth was called and tried to setup the stack. like i > said, your problem is that device did not respond to "reset" command for > the very first time. > > i will cvsup to -current today and try to reproduce it. Ok, thanks. This is a laptop, with an internal bluetooth adapter. I can reboot again and see if it does the same thing a second time. It could be a timing issue. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 16 20:17:24 2005 Return-Path: X-Original-To: bluetooth@freebsd.org 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 6C12316A41F for ; Wed, 16 Nov 2005 20:17:24 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 042D643D45 for ; Wed, 16 Nov 2005 20:17:23 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jAGKHLJ21304; Wed, 16 Nov 2005 15:17:22 -0500 Message-ID: <437B93CF.4000403@savvis.net> Date: Wed, 16 Nov 2005 12:17:19 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <437B2E58.50709@centtech.com> <437B52FF.9040407@savvis.net> <437B5CE2.5000601@centtech.com> In-Reply-To: <437B5CE2.5000601@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: bluetooth Subject: Re: No route to host for bluetooth devices X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 20:17:24 -0000 Eric, >>> Well, I've recently updated to the latest current, and while >>> yesterday everything seemed to be working fine, this morning after >>> booting up (no changes were made anywhere, except rebooting), I >>> cannot use bluetooth devices. Here's some quick info: >>> >>> snippets from /var/log/messages: >>> Nov 16 06:30:58 neutrino kernel: ubt0: ALPS UGX, rev 1.10/11.68, addr 3 >>> Nov 16 06:30:58 neutrino kernel: ubt0: ALPS UGX, rev 1.10/11.68, addr 3 >>> Nov 16 06:30:58 neutrino kernel: ubt0: Interface 0 endpoints: >>> interrupt=0x81, bulk-in=0x82, bulk-out=0x2 >>> Nov 16 06:30:58 neutrino kernel: ubt0: Interface 1 (alt.config 5) >>> endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, >>> buffer size=294 >>> Nov 16 06:31:08 neutrino kernel: ng_hci_process_command_timeout: >>> ubt0hci - unable to complete HCI command OGF=0x3, OCF=0x3. Timeout >> >> device initialization failed. reset command has timed out. there >> should be message like >> >> "Unable to setup Bluetooth stack for device" >> >> somewhere in your logs. > > I could not find that message anywhere (dmesg, or /var/log/messages). > Only thing I saw was: > WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() > which I believe is harmless. /etc/rc.d/bluetooth uses err() and warn() from /etc/rc.subr to complain about errors. both err() and warn() use /usr/bin/logger to send messages. according to the logger(1) man page it uses default user.notice priority. could you please try to run as root # logger foo and then check your /var/log/messages to see if you got "foo" line in there. if you dont, then verify syslogd(8) is runnig and check your /etc/syslog.conf to see where do you redirect *.notice messages (or more specifically user.notice). i will double check if there is an ordering issue, i.e. devd(8) is started before syslogd(8) and thus error messages are not logged. >>> # bthidcontrol -a logimouse query >>> Could not perform SDP query on the device 00:07:61:31:27:15. No route >>> to host (65) >> >> yes, and this is because stack was not set properly and as far as >> system concerns you do not have active bluetooth devices. its kinda >> like using the network without network card. >> >>> and just now I did: >>> /etc/rc.d/bluetooth stop ubt0 >>> /etc/rc.d/bluetooth start ubt0 >>> >>> and it started working, so I think my message is bogus, except for one >> >> ok. you basically restart the device and now it works. are you getting >> "ng_hci_process_command_timeout" error when you boot with device >> attached? > > Yes - see the log message output above. ok >>> question: am I supposed to have a bluetooth_enable="YES" in >>> /etc/rc.conf? I think that's the problem.. >> >> no, that is not your problem. the fact that you got the error means >> that /etc/rc.d/bluetooth was called and tried to setup the stack. like >> i said, your problem is that device did not respond to "reset" command >> for the very first time. >> >> i will cvsup to -current today and try to reproduce it. > > Ok, thanks. This is a laptop, with an internal bluetooth adapter. I > can reboot again and see if it does the same thing a second time. It > could be a timing issue. i have updated my system to the most recent -current, and booted with bluetooth usb dongle (3com) attached. no problem here. so i guess there is something about your internal bluetooth adapter that makes it bad. do you have, like, bluetooth on/off button on you laptop? what laptop do you have? thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 16 21:29:02 2005 Return-Path: X-Original-To: bluetooth@freebsd.org 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 1C91116A41F for ; Wed, 16 Nov 2005 21:29:02 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2599043D58 for ; Wed, 16 Nov 2005 21:28:57 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id jAGLSuaq015781; Wed, 16 Nov 2005 15:28:56 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <437BA490.1010704@centtech.com> Date: Wed, 16 Nov 2005 15:28:48 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051021 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Maksim Yevmenkin References: <437B2E58.50709@centtech.com> <437B52FF.9040407@savvis.net> <437B5CE2.5000601@centtech.com> <437B93CF.4000403@savvis.net> In-Reply-To: <437B93CF.4000403@savvis.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1176/Tue Nov 15 14:47:39 2005 on mh1.centtech.com X-Virus-Status: Clean Cc: bluetooth Subject: Re: No route to host for bluetooth devices X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 21:29:02 -0000 Maksim Yevmenkin wrote: > Eric, > >>>> Well, I've recently updated to the latest current, and while >>>> yesterday everything seemed to be working fine, this morning after >>>> booting up (no changes were made anywhere, except rebooting), I >>>> cannot use bluetooth devices. Here's some quick info: >>>> >>>> snippets from /var/log/messages: >>>> Nov 16 06:30:58 neutrino kernel: ubt0: ALPS UGX, rev 1.10/11.68, addr 3 >>>> Nov 16 06:30:58 neutrino kernel: ubt0: ALPS UGX, rev 1.10/11.68, addr 3 >>>> Nov 16 06:30:58 neutrino kernel: ubt0: Interface 0 endpoints: >>>> interrupt=0x81, bulk-in=0x82, bulk-out=0x2 >>>> Nov 16 06:30:58 neutrino kernel: ubt0: Interface 1 (alt.config 5) >>>> endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, >>>> buffer size=294 >>>> Nov 16 06:31:08 neutrino kernel: ng_hci_process_command_timeout: >>>> ubt0hci - unable to complete HCI command OGF=0x3, OCF=0x3. Timeout >>> >>> >>> device initialization failed. reset command has timed out. there >>> should be message like >>> >>> "Unable to setup Bluetooth stack for device" >>> >>> somewhere in your logs. >> >> >> I could not find that message anywhere (dmesg, or /var/log/messages). >> Only thing I saw was: >> WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() >> which I believe is harmless. > > > /etc/rc.d/bluetooth uses err() and warn() from /etc/rc.subr to complain > about errors. both err() and warn() use /usr/bin/logger to send > messages. according to the logger(1) man page it uses default > user.notice priority. > > could you please try to run as root > > # logger foo > > and then check your /var/log/messages to see if you got "foo" line in > there. As root or regular user, I see the foo message in /var/log/messages. > > if you dont, then verify syslogd(8) is runnig and check your > /etc/syslog.conf to see where do you redirect *.notice messages (or more > specifically user.notice). > > i will double check if there is an ordering issue, i.e. devd(8) is > started before syslogd(8) and thus error messages are not logged. Here's my syslog.conf: # $FreeBSD: src/etc/syslog.conf,v 1.28 2005/03/12 12:31:16 glebius Exp $ # # Spaces ARE valid field separators in this file. However, # other *nix-like systems still insist on using tabs as field # separators. If you are sharing this file between systems, you # may want to use only tabs as field separators here. # Consult the syslog.conf(5) manpage. *.err;kern.warning;auth.notice;mail.crit /dev/console *.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages security.* /var/log/security auth.info;authpriv.info /var/log/auth.log mail.info /var/log/maillog lpr.info /var/log/lpd-errs ftp.info /var/log/xferlog cron.* /var/log/cron *.=debug /var/log/debug.log *.emerg * # uncomment this to log all writes to /dev/console to /var/log/console.log #console.info /var/log/console.log # uncomment this to enable logging of all log messages to /var/log/all.log # touch /var/log/all.log and chmod it to mode 600 before it will work #*.* /var/log/all.log # uncomment this to enable logging to a remote loghost named loghost #*.* @loghost # uncomment these if you're running inn # news.crit /var/log/news/news.crit # news.err /var/log/news/news.err # news.notice /var/log/news/news.notice !startslip *.* /var/log/slip.log !ppp *.* /var/log/ppp.log !mpd *.* /var/log/mpd.log > >>>> # bthidcontrol -a logimouse query >>>> Could not perform SDP query on the device 00:07:61:31:27:15. No >>>> route to host (65) >>> >>> >>> yes, and this is because stack was not set properly and as far as >>> system concerns you do not have active bluetooth devices. its kinda >>> like using the network without network card. >>> >>>> and just now I did: >>>> /etc/rc.d/bluetooth stop ubt0 >>>> /etc/rc.d/bluetooth start ubt0 >>>> >>>> and it started working, so I think my message is bogus, except for one >>> >>> >>> ok. you basically restart the device and now it works. are you >>> getting "ng_hci_process_command_timeout" error when you boot with >>> device attached? >> >> >> Yes - see the log message output above. > > > ok > >>>> question: am I supposed to have a bluetooth_enable="YES" in >>>> /etc/rc.conf? I think that's the problem.. >>> >>> >>> no, that is not your problem. the fact that you got the error means >>> that /etc/rc.d/bluetooth was called and tried to setup the stack. >>> like i said, your problem is that device did not respond to "reset" >>> command for the very first time. >>> >>> i will cvsup to -current today and try to reproduce it. >> >> >> Ok, thanks. This is a laptop, with an internal bluetooth adapter. I >> can reboot again and see if it does the same thing a second time. It >> could be a timing issue. > > > i have updated my system to the most recent -current, and booted with > bluetooth usb dongle (3com) attached. no problem here. so i guess there > is something about your internal bluetooth adapter that makes it bad. do > you have, like, bluetooth on/off button on you laptop? what laptop do > you have? I have a Sony VGN-A170P laptop, which does indeed include a switch. I verified that the switch was on, and the blue light that indicates the bluetooth is running was lit. The switch also controls the wireless card, which was working fine at the time. I also tried switching it off, waiting until the blue light went away, and then switching it back on, with no change. Only running the bluetooth script helped. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 16 22:14:15 2005 Return-Path: X-Original-To: bluetooth@freebsd.org 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 54B6016A420 for ; Wed, 16 Nov 2005 22:14:15 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC36743D46 for ; Wed, 16 Nov 2005 22:14:14 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jAGMEDJ24380; Wed, 16 Nov 2005 17:14:13 -0500 Message-ID: <437BAF32.5030502@savvis.net> Date: Wed, 16 Nov 2005 14:14:10 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <437B2E58.50709@centtech.com> <437B52FF.9040407@savvis.net> <437B5CE2.5000601@centtech.com> <437B93CF.4000403@savvis.net> <437BA490.1010704@centtech.com> In-Reply-To: <437BA490.1010704@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: bluetooth Subject: Re: No route to host for bluetooth devices X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 22:14:15 -0000 Eric, >>>>> Well, I've recently updated to the latest current, and while >>>>> yesterday everything seemed to be working fine, this morning after >>>>> booting up (no changes were made anywhere, except rebooting), I >>>>> cannot use bluetooth devices. Here's some quick info: >>>>> >>>>> snippets from /var/log/messages: >>>>> Nov 16 06:30:58 neutrino kernel: ubt0: ALPS UGX, rev 1.10/11.68, >>>>> addr 3 >>>>> Nov 16 06:30:58 neutrino kernel: ubt0: ALPS UGX, rev 1.10/11.68, >>>>> addr 3 >>>>> Nov 16 06:30:58 neutrino kernel: ubt0: Interface 0 endpoints: >>>>> interrupt=0x81, bulk-in=0x82, bulk-out=0x2 >>>>> Nov 16 06:30:58 neutrino kernel: ubt0: Interface 1 (alt.config 5) >>>>> endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; >>>>> nframes=6, buffer size=294 >>>>> Nov 16 06:31:08 neutrino kernel: ng_hci_process_command_timeout: >>>>> ubt0hci - unable to complete HCI command OGF=0x3, OCF=0x3. Timeout >>>> >>>> device initialization failed. reset command has timed out. there >>>> should be message like >>>> >>>> "Unable to setup Bluetooth stack for device" >>>> >>>> somewhere in your logs. >>> >>> I could not find that message anywhere (dmesg, or /var/log/messages). >>> Only thing I saw was: >>> WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() >>> which I believe is harmless. >> >> /etc/rc.d/bluetooth uses err() and warn() from /etc/rc.subr to >> complain about errors. both err() and warn() use /usr/bin/logger to >> send messages. according to the logger(1) man page it uses default >> user.notice priority. >> >> could you please try to run as root >> >> # logger foo >> >> and then check your /var/log/messages to see if you got "foo" line in >> there. > > As root or regular user, I see the foo message in /var/log/messages. thats good. >> if you dont, then verify syslogd(8) is runnig and check your >> /etc/syslog.conf to see where do you redirect *.notice messages (or >> more specifically user.notice). >> >> i will double check if there is an ordering issue, i.e. devd(8) is >> started before syslogd(8) and thus error messages are not logged. > > > Here's my syslog.conf: [...] > *.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err *.notice should go into /var/log/messages. so you should have seen the error message from /etc/rc.d/bluetooth there. did you check messages.{1,2,...} files? may be it was rotated? i'm pretty sure that on my system syslogd(8) starts before devd(8). so at this point i do not know why you did not get error message from /etc/rc.d/bluetooth. i will try to simulate the error on boot to see what is going on. [...] >>>> i will cvsup to -current today and try to reproduce it. >>> >>> Ok, thanks. This is a laptop, with an internal bluetooth adapter. I >>> can reboot again and see if it does the same thing a second time. It >>> could be a timing issue. >> >> i have updated my system to the most recent -current, and booted with >> bluetooth usb dongle (3com) attached. no problem here. so i guess >> there is something about your internal bluetooth adapter that makes it >> bad. do you have, like, bluetooth on/off button on you laptop? what >> laptop do you have? > > I have a Sony VGN-A170P laptop, which does indeed include a switch. I > verified that the switch was on, and the blue light that indicates the > bluetooth is running was lit. The switch also controls the wireless > card, which was working fine at the time. I also tried switching it > off, waiting until the blue light went away, and then switching it back > on, with no change. Only running the bluetooth script helped. hmm... i'm surprised that switch did not help. on some laptops bluetooth button/switch usually makes internal device to disconnect/connect. in this case devd(8) will get detach/attach event which will trigger 'bluetooth stop/start'. perhaps the switch only controls the light? or may be the radio part of the device, i.e. device will always stay attached, but the radio is powered off? did you try to turn switch off and then bluetooth stop/start? does it give you the same timeout error? thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Nov 17 02:27:43 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 7056B16A41F for ; Thu, 17 Nov 2005 02:27:43 +0000 (GMT) (envelope-from bohra@dragon.rutgers.edu) Received: from dragon.rutgers.edu (dragon.rutgers.edu [128.6.25.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1291343D49 for ; Thu, 17 Nov 2005 02:27:42 +0000 (GMT) (envelope-from bohra@dragon.rutgers.edu) X-Virus-Scanned: by dragon-cgpav-clamav-v1.3b Received: by dragon.rutgers.edu (CommuniGate Pro PIPE 5.0) with PIPE id 35211506; Wed, 16 Nov 2005 21:27:42 -0500 Received: from [70.192.56.96] (account bohra@dragon.rutgers.edu) by dragon.rutgers.edu (CommuniGate Pro WebUser 5.0) with HTTP id 35211501 for freebsd-bluetooth@freebsd.org; Wed, 16 Nov 2005 21:27:33 -0500 From: "Aniruddha Bohra" To: freebsd-bluetooth@freebsd.org X-Mailer: CommuniGate Pro WebUser v5.0 Date: Wed, 16 Nov 2005 21:27:33 -0500 Message-ID: X-Priority: 1 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on spamfilter.rutgers.edu X-Spam-Level: X-Spam-Status: No, score=-0.2 required=5.0 tests=BAYES_00,J_CHICKENPOX_33, MSGID_FROM_MTA_ID,TW_HC autolearn=disabled version=3.0.4 Subject: Cannot pair with Audiovox SMT5600 Bluetooth X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 02:27:43 -0000 Hi, I have been trying to get the bluetooth pairing between the above cellphone and my FreeBSD 6.0-Release host. I followed the instructions in the handbook and created the entry for the phone in /etc/bluetooth/hcsecd.conf as follows : evice { bdaddr 00:09:2d:1b:15:a3; name "Audiovox"; key nokey; pin "1234"; } On starting rfcomm_pppd from the host, I get : hcsecd[1107]: Got PIN_Code_Request event from 'ubt0hci', remote bdaddr 00:09:2d:1b:15:a3 hcsecd[1107]: Found matching entry, remote bdaddr 00:09:2d:1b:15:a3, name 'Audiovox', PIN code exists hcsecd[1107]: Sending PIN_Code_Reply to 'ubt0hci' for remote bdaddr 00:09:2d:1b:15:a3 hcsecd[1107]: Got Link_Key_Notification event from 'ubt0hci', remote bdaddr 00:09:2d:1b:15:a3 hcsecd[1107]: Updating link key for the entry, remote bdaddr 00:09:2d:1b:15:a3, name 'Audiovox', link key exists Any ideas what might be going wrong and how to debug this ? BTW, I tried with both : hccontrol -n ubt0hci write_node_role_switch 0 and without it with the same result. The phone gives an error saying the phone did not connect. Any help is appreciated. Thanks Aniruddha From owner-freebsd-bluetooth@FreeBSD.ORG Thu Nov 17 13:27:54 2005 Return-Path: X-Original-To: bluetooth@freebsd.org 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 3A0C016A421 for ; Thu, 17 Nov 2005 13:27:54 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33D3543D60 for ; Thu, 17 Nov 2005 13:27:46 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id jAHDRheL017849; Thu, 17 Nov 2005 07:27:44 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <437C8547.3060708@centtech.com> Date: Thu, 17 Nov 2005 07:27:35 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051021 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Maksim Yevmenkin References: <437B2E58.50709@centtech.com> <437B52FF.9040407@savvis.net> <437B5CE2.5000601@centtech.com> <437B93CF.4000403@savvis.net> <437BA490.1010704@centtech.com> <437BAF32.5030502@savvis.net> In-Reply-To: <437BAF32.5030502@savvis.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1177/Thu Nov 17 02:35:37 2005 on mh2.centtech.com X-Virus-Status: Clean Cc: bluetooth Subject: Re: No route to host for bluetooth devices X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 13:27:54 -0000 Maksim Yevmenkin wrote: > Eric, > >>>>>> Well, I've recently updated to the latest current, and while >>>>>> yesterday everything seemed to be working fine, this morning after >>>>>> booting up (no changes were made anywhere, except rebooting), I >>>>>> cannot use bluetooth devices. Here's some quick info: >>>>>> >>>>>> snippets from /var/log/messages: >>>>>> Nov 16 06:30:58 neutrino kernel: ubt0: ALPS UGX, rev 1.10/11.68, >>>>>> addr 3 >>>>>> Nov 16 06:30:58 neutrino kernel: ubt0: ALPS UGX, rev 1.10/11.68, >>>>>> addr 3 >>>>>> Nov 16 06:30:58 neutrino kernel: ubt0: Interface 0 endpoints: >>>>>> interrupt=0x81, bulk-in=0x82, bulk-out=0x2 >>>>>> Nov 16 06:30:58 neutrino kernel: ubt0: Interface 1 (alt.config 5) >>>>>> endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; >>>>>> nframes=6, buffer size=294 >>>>>> Nov 16 06:31:08 neutrino kernel: ng_hci_process_command_timeout: >>>>>> ubt0hci - unable to complete HCI command OGF=0x3, OCF=0x3. Timeout >>>>> >>>>> >>>>> device initialization failed. reset command has timed out. there >>>>> should be message like >>>>> >>>>> "Unable to setup Bluetooth stack for device" >>>>> >>>>> somewhere in your logs. >>>> >>>> >>>> I could not find that message anywhere (dmesg, or >>>> /var/log/messages). Only thing I saw was: >>>> WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() >>>> which I believe is harmless. >>> >>> >>> /etc/rc.d/bluetooth uses err() and warn() from /etc/rc.subr to >>> complain about errors. both err() and warn() use /usr/bin/logger to >>> send messages. according to the logger(1) man page it uses default >>> user.notice priority. >>> >>> could you please try to run as root >>> >>> # logger foo >>> >>> and then check your /var/log/messages to see if you got "foo" line in >>> there. >> >> >> As root or regular user, I see the foo message in /var/log/messages. > > > thats good. > >>> if you dont, then verify syslogd(8) is runnig and check your >>> /etc/syslog.conf to see where do you redirect *.notice messages (or >>> more specifically user.notice). >>> >>> i will double check if there is an ordering issue, i.e. devd(8) is >>> started before syslogd(8) and thus error messages are not logged. >> >> >> >> Here's my syslog.conf: > > > [...] > >> *.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err > > > *.notice should go into /var/log/messages. so you should have seen the > error message from /etc/rc.d/bluetooth there. did you check > messages.{1,2,...} files? may be it was rotated? > > i'm pretty sure that on my system syslogd(8) starts before devd(8). so > at this point i do not know why you did not get error message from > /etc/rc.d/bluetooth. i will try to simulate the error on boot to see > what is going on. > > [...] > >>>>> i will cvsup to -current today and try to reproduce it. >>>> >>>> >>>> Ok, thanks. This is a laptop, with an internal bluetooth adapter. >>>> I can reboot again and see if it does the same thing a second time. >>>> It could be a timing issue. >>> >>> >>> i have updated my system to the most recent -current, and booted with >>> bluetooth usb dongle (3com) attached. no problem here. so i guess >>> there is something about your internal bluetooth adapter that makes >>> it bad. do you have, like, bluetooth on/off button on you laptop? >>> what laptop do you have? >> >> >> I have a Sony VGN-A170P laptop, which does indeed include a switch. I >> verified that the switch was on, and the blue light that indicates the >> bluetooth is running was lit. The switch also controls the wireless >> card, which was working fine at the time. I also tried switching it >> off, waiting until the blue light went away, and then switching it >> back on, with no change. Only running the bluetooth script helped. > > > hmm... i'm surprised that switch did not help. on some laptops bluetooth > button/switch usually makes internal device to disconnect/connect. in > this case devd(8) will get detach/attach event which will trigger > 'bluetooth stop/start'. perhaps the switch only controls the light? or > may be the radio part of the device, i.e. device will always stay > attached, but the radio is powered off? did you try to turn switch off > and then bluetooth stop/start? does it give you the same timeout error? Well, here's more information. First, it's reproducable every time I boot up. Doing: /etc/rc.d/bluetooth start ubt0 does not fix it by itself, but doing: /etc/rc.d/bluetooth stop ubt0 /etc/rc.d/bluetooth start ubt0 does. I also tried a fresh boot, then switching the bluetooth off, waiting about 20 seconds, and flipping it back on, which *did* in fact work. I may not have waited long enough the previous time that failed. Oddly enough, I never had a problem before now. I previously started the bluetooth stuff from rc.local. The only things I have changed are: updated to latest -current, removed inet6 from kernel, rebuilt world/kernel, switched to new rc.d bluetooth scripts. I can try anything you like. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-bluetooth@FreeBSD.ORG Thu Nov 17 17:38:04 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 9F7E516A420 for ; Thu, 17 Nov 2005 17:38:04 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 372AB43D49 for ; Thu, 17 Nov 2005 17:38:03 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jAHHc2J21943; Thu, 17 Nov 2005 12:38:02 -0500 Message-ID: <437CBFF8.7070709@savvis.net> Date: Thu, 17 Nov 2005 09:38:00 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vijay Kiran References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD_Bluetooth Subject: Re: Bluetooth on Laptop X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 17:38:04 -0000 Hello, > I've a Laptop with integrated bluetooth. I've loaded the ng_ubt kernel > module and the dmesg | grep ubt shows the following: > > ubt0: vendor 0x0a12 product 0x0001, rev 2.00/15.93, addr 2 > ubt0: vendor 0x0a12 product 0x0001, rev 2.00/15.93, addr 2 > ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 > ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; > wMaxPacketSize=49; nframes=6, buffer size=294 looks fine to me > This is similar to the example shown in the Handbook. But when I try > /etc/rc.bluetooth start ubt0 it gives error like: > > bash-2.05b# /etc/rc.bluetooth start ubt0 > ngctl: send msg: No such file or directory strange... could you please provide the output of the following commands 1) uname -a 2) kldstat -v 3) ngctl li (as root) and finally try to run (as root) # sh -x /etc/rc.bluetooth start ubt0 > Did I miss something? Do I need to create the device nodes like on Linux? no, you do not need to create device nodes. thanks, max p.s. i've redirected your question to freebsd-bluetooth@ which is more appropriate. From owner-freebsd-bluetooth@FreeBSD.ORG Thu Nov 17 17:45:21 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 5418C16A433 for ; Thu, 17 Nov 2005 17:45:21 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1710443D5D for ; Thu, 17 Nov 2005 17:45:17 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jAHHiiJ22106; Thu, 17 Nov 2005 12:44:44 -0500 Message-ID: <437CC18A.5040804@savvis.net> Date: Thu, 17 Nov 2005 09:44:42 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Aniruddha Bohra References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: Cannot pair with Audiovox SMT5600 Bluetooth X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 17:45:21 -0000 Hello, > I have been trying to get the bluetooth pairing between the above > cellphone and my FreeBSD 6.0-Release host. > > I followed the instructions in the handbook and created the entry > for the phone in /etc/bluetooth/hcsecd.conf as follows : > > evice { > bdaddr 00:09:2d:1b:15:a3; > name "Audiovox"; > key nokey; > pin "1234"; > } > > On starting rfcomm_pppd from the host, I get : > > hcsecd[1107]: Got PIN_Code_Request event from 'ubt0hci', remote bdaddr > 00:09:2d:1b:15:a3 > hcsecd[1107]: Found matching entry, remote bdaddr 00:09:2d:1b:15:a3, > name 'Audiovox', PIN code exists > hcsecd[1107]: Sending PIN_Code_Reply to 'ubt0hci' for remote bdaddr > 00:09:2d:1b:15:a3 > hcsecd[1107]: Got Link_Key_Notification event from 'ubt0hci', remote > bdaddr 00:09:2d:1b:15:a3 > hcsecd[1107]: Updating link key for the entry, remote bdaddr > 00:09:2d:1b:15:a3, name 'Audiovox', link key exists > > Any ideas what might be going wrong and how to debug this ? well, from what i can see everything is working as expected. your phone requests pin code and we send it back. the next event shows that link key is generated and stored. so, "pairing" procedure is completed. > BTW, I tried with both : > hccontrol -n ubt0hci write_node_role_switch 0 > and without it with the same result. no, that is not your problem. most likely the phone is trying to do something else after it has opened baseband connection. > The phone gives an error saying the phone did not connect. please install hcidump port from comms/hcidump and run as root # hcidump -w dump.file this will block. then try one more time. after you got the error, interrupt hcidump with ctrl+c and send me the dump.file thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Nov 17 18:00:42 2005 Return-Path: X-Original-To: bluetooth@freebsd.org 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 C729616A41F for ; Thu, 17 Nov 2005 18:00:42 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6331143D45 for ; Thu, 17 Nov 2005 18:00:42 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jAHI0cJ22553; Thu, 17 Nov 2005 13:00:39 -0500 Message-ID: <437CC544.6080509@savvis.net> Date: Thu, 17 Nov 2005 10:00:36 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <437B2E58.50709@centtech.com> <437B52FF.9040407@savvis.net> <437B5CE2.5000601@centtech.com> <437B93CF.4000403@savvis.net> <437BA490.1010704@centtech.com> <437BAF32.5030502@savvis.net> <437C8547.3060708@centtech.com> In-Reply-To: <437C8547.3060708@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: bluetooth Subject: Re: No route to host for bluetooth devices X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 18:00:42 -0000 Eric, [...] >>> I have a Sony VGN-A170P laptop, which does indeed include a switch. >>> I verified that the switch was on, and the blue light that indicates >>> the bluetooth is running was lit. The switch also controls the >>> wireless card, which was working fine at the time. I also tried >>> switching it off, waiting until the blue light went away, and then >>> switching it back on, with no change. Only running the bluetooth >>> script helped. >> >> hmm... i'm surprised that switch did not help. on some laptops >> bluetooth button/switch usually makes internal device to >> disconnect/connect. in this case devd(8) will get detach/attach event >> which will trigger 'bluetooth stop/start'. perhaps the switch only >> controls the light? or may be the radio part of the device, i.e. >> device will always stay attached, but the radio is powered off? did >> you try to turn switch off and then bluetooth stop/start? does it give >> you the same timeout error? > > Well, here's more information. First, it's reproducable every time I > boot up. Doing: > /etc/rc.d/bluetooth start ubt0 > does not fix it by itself, but doing: > /etc/rc.d/bluetooth stop ubt0 > /etc/rc.d/bluetooth start ubt0 > does. now, i really puzzled. because device fails on to start at boot time, /etc/rc.d/bluetooth should have backed out and removed all netgraph nodes it tried to create (except device node and socket nodes). so i do not understand why do you need to do 'stop' before 'start'. 'stop' should really be a noop in this case. could you please do the following 1) do a fresh boot with bluetooth device turned on 2) after system boots (and bluetooth device failed to start) please run as root # ngctl li > I also tried a fresh boot, then switching the bluetooth off, waiting > about 20 seconds, and flipping it back on, which *did* in fact work. I > may not have waited long enough the previous time that failed. ah, ok. could you please check the /var/log/messages file to see if you get a message saying ubt0 is detached/attached? > Oddly enough, I never had a problem before now. I previously started > the bluetooth stuff from rc.local. The only things I have changed are: > updated to latest -current, removed inet6 from kernel, rebuilt > world/kernel, switched to new rc.d bluetooth scripts. I can try > anything you like. one thing you could try to do is to comment out ubt0 section in /etc/devd.conf and go back to old style rc.bluetooth script to see if you have the same problem. if you do - then its not bluetooth related, if you dont - then its related to new bluetooth rc.d scripts. thanks, max > > Eric > > > From owner-freebsd-bluetooth@FreeBSD.ORG Thu Nov 17 19:09:05 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 8B76516A41F for ; Thu, 17 Nov 2005 19:09:05 +0000 (GMT) (envelope-from bohra@dragon.rutgers.edu) Received: from dragon.rutgers.edu (dragon.rutgers.edu [128.6.25.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1BBB43D73 for ; Thu, 17 Nov 2005 19:08:46 +0000 (GMT) (envelope-from bohra@dragon.rutgers.edu) X-Virus-Scanned: by dragon-cgpav-clamav-v1.3b Received: by dragon.rutgers.edu (CommuniGate Pro PIPE 5.0) with PIPE id 35232285; Thu, 17 Nov 2005 14:08:44 -0500 Received: from [66.209.15.234] (account bohra@dragon.rutgers.edu) by dragon.rutgers.edu (CommuniGate Pro WebUser 5.0) with HTTP id 35232286; Thu, 17 Nov 2005 14:08:26 -0500 From: "Aniruddha Bohra" To: Maksim Yevmenkin X-Mailer: CommuniGate Pro WebUser v5.0 Date: Thu, 17 Nov 2005 14:08:26 -0500 Message-ID: In-Reply-To: <437CC18A.5040804@savvis.net> References: <437CC18A.5040804@savvis.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_===35232286====dragon.rutgers.edu===_" X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on spamfilter.rutgers.edu X-Spam-Level: ** X-Spam-Status: No, score=2.6 required=5.0 tests=BAYES_05,J_CHICKENPOX_33, J_CHICKENPOX_44,MSGID_FROM_MTA_ID,TW_HC autolearn=disabled version=3.0.4 Cc: freebsd-bluetooth@freebsd.org Subject: Re: Cannot pair with Audiovox SMT5600 Bluetooth X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 19:09:05 -0000 This is a multi-part MIME message --_===35232286====dragon.rutgers.edu===_ Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit > > I have been trying to get the bluetooth pairing between the above > > cellphone and my FreeBSD 6.0-Release host. > > > > On starting rfcomm_pppd from the host, I get : > > > > hcsecd[1107]: Got PIN_Code_Request event from 'ubt0hci', remote > bdaddr > > 00:09:2d:1b:15:a3 > > hcsecd[1107]: Found matching entry, remote bdaddr > 00:09:2d:1b:15:a3, > > name 'Audiovox', PIN code exists > > hcsecd[1107]: Sending PIN_Code_Reply to 'ubt0hci' for remote bdaddr > > 00:09:2d:1b:15:a3 > > hcsecd[1107]: Got Link_Key_Notification event from 'ubt0hci', > remote > > bdaddr 00:09:2d:1b:15:a3 > > hcsecd[1107]: Updating link key for the entry, remote bdaddr > > 00:09:2d:1b:15:a3, name 'Audiovox', link key exists > > > well, from what i can see everything is working as expected. your > phone requests pin code and we send it back. the next event shows > that link key is generated and stored. so, "pairing" procedure is > completed. > > > BTW, I tried with both : > > hccontrol -n ubt0hci write_node_role_switch 0 > > and without it with the same result. > > no, that is not your problem. most likely the phone is trying to do > something else after it has opened baseband connection. > > please install hcidump port from comms/hcidump and run as root > > # hcidump -w dump.file > The file is attached. Actually the problem is only with pairing I feel. The GPRS connection (through DUN) goes through, even if the phone says there was an error. Thanks Aniruddha --_===35232286====dragon.rutgers.edu===_ Content-Type: application/octet-stream Content-Disposition: attachment; filename="dump.file" Content-Transfer-Encoding: base64 DQABABbhfENDUQsABAQKoxUbLQkADAJQAQsAAAAW4XxDSFELAAEJBAejFRstCQAABwABABbh fENYcAsABA8EAAEJBAsAAQAW4XxDei8OAAQSCACjFRstCQAADgABABbhfEO1eQ4ABAMLACkA oxUbLQkAAQAIAAAAFuF8Q7h5DgABDQgEKQAPAAoAAQAW4XxDfoEOAAQgB6MVGy0JAAEJAAEA FuF8Q0+JDgAEDgYBDQgAKQAGAAEAFuF8Qxe8DgAEGwMpAAUJAAEAF+F8Qzq3BwAEFgajFRst CQAbAAAAF+F8Q6q3BwABDQQXoxUbLQkABDEyMzQAAAAAAAAAAAAAAAANAAEAF+F8QzHiBwAE DgoBDQQAoxUbLQkAGgABABfhfENSJAoABBgXoxUbLQkADHgI0v2UaxhQwu6hh+z2gwAHAAEA GOF8Q4NNCQAEBQQAKQATDQABABnhfEO6SwgABAQKoxUbLQkADAJQAQsAAAAZ4XxDvksIAAEJ BAejFRstCQAABwABABnhfEPnaggABA8EAAEJBAsAAQAZ4XxD8i0LAAQSCACjFRstCQAADgAB ABnhfEMVfAsABAMLACoAoxUbLQkAAQAIAAAAGeF8Qxh8CwABDQgEKgAPAAoAAQAZ4XxD3oML AAQgB6MVGy0JAAEJAAEAGeF8Q6+LCwAEDgYBDQgAKgARAAEAGeF8Q+quCwACKiAMAAgAAQAC wwQAAQB8ABUAAAAZ4XxDAK8LAAIqIBAADAABAAPDCAB4AHwAAgAAAAYAAQAZ4XxDRsYLAAQb AyoABQgAAQAZ4XxDFs4LAAQTBQEqAAEAEQABABrhfEMrpgQAAiogDAAIAAEAAsQEAAEAfQAV AAAAGuF8Qz2mBAACKiAQAAwAAQADxAgAeQB9AAIAAAAIAAEAGuF8Q2nBBAAEEwUBKgABABEA AQAb4XxDmA8FAAIqIAwACAABAALFBAABAH4AFQAAABvhfEOpDwUAAiogEAAMAAEAA8UIAHoA fgACAAAACAABABvhfEP5JgUABBMFASoAAQA= --_===35232286====dragon.rutgers.edu===_-- From owner-freebsd-bluetooth@FreeBSD.ORG Thu Nov 17 19:36:18 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 C518816A426 for ; Thu, 17 Nov 2005 19:36:18 +0000 (GMT) (envelope-from vijaykiran.duvvuri@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50D1C43D72 for ; Thu, 17 Nov 2005 19:36:13 +0000 (GMT) (envelope-from vijaykiran.duvvuri@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so5107nzo for ; Thu, 17 Nov 2005 11:36:12 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:to:subject:references:message-id:date:from:organization:content-type:mime-version:in-reply-to:user-agent; b=I0Nll9FdrIG2+pW3k1iausvXr6o5n90a2NOc2tOAJK5YmjBDElzutY63iuYsrdXHtkai4hYRI2RVY3k57eYUa4zT4RiJxCficFXsNEnkSDIdI+O8dsYVrp/1lfO+VNHiHLnMAWCPWAlunFeHiKde/TyVItCJBMRkcNKvpfvIRp4= Received: by 10.37.15.74 with SMTP id s74mr7851749nzi; Thu, 17 Nov 2005 11:36:12 -0800 (PST) Received: from localhost.vijaykiran.com ( [203.187.240.144]) by mx.gmail.com with ESMTP id c12sm9073nzc.2005.11.17.11.36.07; Thu, 17 Nov 2005 11:36:12 -0800 (PST) To: FreeBSD_Bluetooth References: <437CBFF8.7070709@savvis.net> Message-ID: Date: Fri, 18 Nov 2005 01:05:59 +0530 From: "Vijay Kiran" Organization: www.VijayKiran.com Content-Type: multipart/mixed; boundary=----------y7qxwHqhwhwjgtEVmzYtm5 MIME-Version: 1.0 In-Reply-To: <437CBFF8.7070709@savvis.net> User-Agent: Opera M2/8.50 (FreeBSD, build 1358) Subject: Re: Bluetooth on Laptop X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 19:36:19 -0000 ------------y7qxwHqhwhwjgtEVmzYtm5 Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii Content-Transfer-Encoding: 8bit Hi Max, I've added the ng_ubt_load="YES" and rebooted. It fixed the problem, hcccontrol inquiry command finds my Nokia 3230 phone via bluetooth :-) But I dont know why it didn't work when I used plain kldload ng_ubt, may be it needs more modules(?). Please find the result of the commands attached as a txt file. I'll be trying to pair up my phone with laptop. --- Thanks & Regards, www.VijayKiran.com On Thu, 17 Nov 2005 23:08:00 +0530, Maksim Yevmenkin wrote: > Hello, > >> I've a Laptop with integrated bluetooth. I've loaded the ng_ubt kernel >> module and the dmesg | grep ubt shows the following: >> ubt0: vendor 0x0a12 product 0x0001, rev 2.00/15.93, addr 2 >> ubt0: vendor 0x0a12 product 0x0001, rev 2.00/15.93, addr 2 >> ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 >> ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, >> isoc-out=0x3; wMaxPacketSize=49; nframes=6, buffer size=294 > > looks fine to me > >> This is similar to the example shown in the Handbook. But when I try >> /etc/rc.bluetooth start ubt0 it gives error like: >> bash-2.05b# /etc/rc.bluetooth start ubt0 >> ngctl: send msg: No such file or directory > > strange... could you please provide the output of the following commands > > 1) uname -a > > 2) kldstat -v > > 3) ngctl li (as root) > > and finally try to run (as root) > > # sh -x /etc/rc.bluetooth start ubt0 > >> Did I miss something? Do I need to create the device nodes like on >> Linux? > > no, you do not need to create device nodes. > > thanks, > max > > p.s. i've redirected your question to freebsd-bluetooth@ which is more > appropriate. ------------y7qxwHqhwhwjgtEVmzYtm5 Content-Disposition: attachment; filename=log.txt Content-Type: text/plain; name=log.txt Content-Transfer-Encoding: 8bit FreeBSD shire.vijaykiran.com 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 root@x64.samsco.home:/usr/obj/usr/src/sys/GENERIC i386 Id Refs Address Size Name 1 22 0xc0400000 63070c kernel Contains modules: Id Name 30 xpt 31 probe 32 cam 33 cd 34 ch 35 da 36 scsi_low 37 pass 38 sa 39 ses 40 aac/aacp 41 aac/aacd 42 pci/aac 43 pci/aacch 44 eisa/adv 45 pci/adv 46 pci/adw 47 isa/aha 48 eisa/ahb 49 pccard/aic 50 eisa/ahc_eisa 51 isa/ahc_isa 52 pci/ahc_pci 53 cardbus/ahc_pci 54 pci/ahd 55 cardbus/ahd 56 ahd 57 ahc 58 pci/amd 59 amr/amrd 60 pci/amr 61 isa/an 62 pccard/an 63 pci/an 64 pci/asr 65 ata 66 pccard/ata 67 ata/ad 68 isa/ata 69 pci/atapci 70 atapci/ata 71 ad/subdisk 72 ataraid 73 ata/acd 74 ata/afd 75 ata/ast 76 pccard/awi 77 pci/bfe 78 bfe/miibus 79 pci/bge 80 bge/miibus 81 eisa/bt 82 isa/bt 83 pci/bt 84 cbb/cardbus 85 pci/ciss 86 isa/cs 87 pccard/cs 88 eisa/dpt 89 pci/dpt 90 pccard/ed 91 ed/miibus 92 pci/ed 93 eisa/mainboard 94 eisab/eisa 95 legacy/eisa 96 pci/em 97 eisa/ep 98 isa/ep 99 pccard/ep 100 isa/ex 101 exca 102 pccard/fe 103 fwohci/firewire 104 pci/fwohci 105 cardbus/fwohci 106 firewire/fwe 107 firewire/sbp 108 pci/fxp 109 cardbus/fxp 110 fxp/miibus 111 ida/idad 112 eisa/ida 113 pci/ida 114 isa/ie_3C507 115 isa/ie_EE16 116 isa/ie_SL 117 pci/iir 118 ips/ipsd 119 pci/ips 120 pci/isp 121 pci/if_ixgb 122 pci/lge 123 lge/miibus 124 pci/lnc 125 g_md 126 mem 127 miibus/acphy 128 miibus/amphy 129 miibus/bmtphy 130 miibus/brgphy 131 miibus/ciphy 132 miibus/dcphy 133 miibus/e1000phy 134 miibus/xlphy 135 miibus/inphy 136 miibus/lxtphy 137 miibus/mlphy 138 miibus/nsgphy 139 miibus/nsphy 140 miibus/pnaphy 141 miibus/pnphy 142 miibus/qsphy 143 miibus/rgephy 144 miibus/rlphy 145 miibus/ruephy 146 miibus/tdkphy 147 miibus/tlphy 148 miibus/ukphy 149 miibus/xmphy 150 mlx/mlxd 151 pci/mlx 152 pci/mly 153 mpt_core 154 mpt_cam 155 pci/mpt 156 mpt_raid 157 pccard/ncv 158 pci/nge 159 nge/miibus 160 pccard/nsp 161 null 162 pcic/pccard 163 cbb/pccard 164 isa/cbb 165 pci/cbb 166 pci/eisab 167 pci/fixup_pci 168 pci/ignore_pci 169 pci/isab 170 pcib/pci 171 pci/pcib 172 ppbus/plip 173 ppbus/lpt 174 ppc/ppbus 175 ppbus/ppi 176 pci/pstpci 177 pstpci/pst 178 pccard/ral 179 pci/ral 180 cardbus/ral 181 random 182 pci/re 183 cardbus/re 184 re/miibus 185 pccard/sio 186 pci/sio 187 cardbus/sio 188 isa/sn 189 pccard/sn 190 isa/stg 191 pccard/stg 192 pci/stg 193 pci/sym 194 pci/trm 195 pci/twa 196 pci/twe 197 twe/twed 198 pci/tx 199 tx/miibus 200 pci/txp 201 pci/ehci 202 cardbus/ehci 203 uhub/aue 204 aue/miibus 205 uhub/axe 206 axe/miibus 207 uhub/cdce 208 uhub/cue 209 uhub/kue 210 uhub/ural 211 uhub/rue 212 rue/miibus 213 pci/ohci 214 cardbus/ohci 215 uhub/ugen 216 pci/uhci 217 cardbus/uhci 218 uhub/uhid 219 usb/uhub 220 uhub/uhub 221 uhub/ukbd 222 uhub/ulpt 223 uhub/umass 224 uhub/ums 225 uhub/urio 226 ohci/usb 227 uhci/usb 228 ehci/usb 229 uhub/uscanner 230 pci/vge 231 cardbus/vge 232 vge/miibus 233 eisa/vx 234 pci/vx 235 watchdog 236 pccard/wi 237 pci/wi 238 pccard/xe 239 devfs 240 msdosfs 241 procfs 242 pseudofs 243 g_dev 244 g_disk 245 g_gpt 246 g_vfs 247 isab/isa 248 eisab/isa 249 isa/isahint 250 isa/orm 251 isa/pnp 252 cd9660 253 elf32 254 shell 255 cpu/cpufreq 256 rootbus 257 msgsys 258 msgctl 259 msgget 260 msgsnd 261 msgrcv 262 sysvmsg 263 semsys 264 __semctl 265 semget 266 semop 267 sysvsem 268 shmsys 269 shmat 270 shmctl 271 shmdt 272 shmget 273 sysvshm 274 ether 275 if_faith 276 if_gif 277 loop 278 if_ppp 279 if_sl 280 if_tun 281 wlan 282 nfs4 283 nfs 284 nfslock 285 nfsserver 286 cardbus/dc 287 pci/dc 288 dc/miibus 289 pci/de 290 pci/pcn 291 pcn/miibus 292 pci/rl 293 cardbus/rl 294 rl/miibus 295 pci/sf 296 sf/miibus 297 pci/sis 298 sis/miibus 299 pci/sk 300 skc/sk 301 sk/miibus 302 pci/ste 303 ste/miibus 304 pci/ti 305 pci/tl 306 tl/miibus 307 pci/vr 308 vr/miibus 309 pci/wb 310 wb/miibus 311 cardbus/xl 312 pci/xl 313 xl/miibus 314 ufs 315 g_class 316 isa/adv 317 isa/aic 318 pci/arcmsr 319 atkbdc/atkbd 320 isa/atkbdc 321 acpi/atkbdc 322 atkbdc/psm 323 isa/psmcpnp 324 acpi/psmcpnp 325 isa/ed 326 fdc/fd 327 acpi/fdc 328 isa/fdc 329 pccard/fdc 330 isa/fe 331 pci/hptmv 332 io 333 isa/lnc 334 pci/nve 335 nve/miibus 336 isa/ppc 337 acpi/ppc 338 isa/sio 339 acpi/sio 340 scterm-sc 341 scrndr-vga 342 g_bsd 343 g_mbr 344 g_mbrext 345 isa/pnpbios 346 nexus/legacy 347 legacy/cpu 348 legacy/mptable_pcib 349 pci/mptable_pcib 350 root/nexus 351 isa/sysresource 352 isa/atpic 353 acpi/atpic 354 isa/attimer 355 acpi/attimer 356 elink 357 legacy/isa 358 isa/atdma 359 acpi/atdma 360 nexus/npx 361 isa/npxisa 362 acpi/npxisa 363 isa/pmtimer 364 legacy/pcib 365 pci/hostb 366 isa/pcibus_pnp 367 pci/pcibios_pcib 368 legacy/pir 369 isa/sc 370 isa/vga 371 pci/agp_ali 372 pci/agp_amd 373 pci/agp_amd64 374 pci/agp_i810 375 pci/agp_intel 376 pci/agp_nvidia 377 pci/agp_sis 378 pci/agp_via 2 1 0xc0a31000 32e4 splash_bmp.ko Contains modules: Id Name 3 1 0xc0a35000 4228 vesa.ko Contains modules: Id Name 2 vesa 4 1 0xc0b49000 64ec linprocfs.ko Contains modules: Id Name 5 linprocfs 5 2 0xc0b50000 196c8 linux.ko Contains modules: Id Name 3 linuxelf 4 linuxaout 6 1 0xc0b6a000 b924 ntfs.ko Contains modules: Id Name 6 ntfs 7 2 0xc0b76000 1d408 sound.ko Contains modules: Id Name 7 sound 8 1 0xc0b94000 57c8 snd_ich.ko Contains modules: Id Name 8 pci/snd_ich 9 1 0xc0b9a000 115fc bktr.ko Contains modules: Id Name 10 pci/bktr 10 2 0xc0bac000 1f10 bktr_mem.ko Contains modules: Id Name 9 bktr_mem 11 1 0xc0bae000 77e4 ng_ubt.ko Contains modules: Id Name 12 uhub/ubt 12 3 0xc0bb6000 c510 netgraph.ko Contains modules: Id Name 11 netgraph 13 16 0xc0bc3000 568dc acpi.ko Contains modules: Id Name 13 nexus/acpi 14 acpi/acpi_button 15 acpi/acpi_isab 16 pcib/acpi_pci 17 acpi/acpi_pcib 18 pci/acpi_pcib 19 acpi/acpi_sysresource 20 acpi/acpi_timer 21 acpi/acpi_pci_link 22 acpi/acpi_tz 23 acpi/acpi_acad 24 acpi/acpi_cmbat 25 acpi/cpu 26 acpi/acpi_ec 27 acpi/acpi_lid 28 cpu/acpi_perf 29 cpu/acpi_throttle 14 1 0xc3485000 4000 ng_socket.ko Contains modules: Id Name 379 ng_socket There are 2 total nodes: Name: ngctl10867 Type: socket ID: 00000003 Num hooks: 0 Name: ubt0 Type: ubt ID: 00000001 Num hooks: 0 ------------y7qxwHqhwhwjgtEVmzYtm5-- From owner-freebsd-bluetooth@FreeBSD.ORG Thu Nov 17 19:42:04 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 7CFF816A41F for ; Thu, 17 Nov 2005 19:42:04 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6C1843D45 for ; Thu, 17 Nov 2005 19:42:03 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jAHJfUJ25085; Thu, 17 Nov 2005 14:41:30 -0500 Message-ID: <437CDCE8.4060605@savvis.net> Date: Thu, 17 Nov 2005 11:41:28 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Aniruddha Bohra References: <437CC18A.5040804@savvis.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: Cannot pair with Audiovox SMT5600 Bluetooth X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 19:42:04 -0000 Aniruddha, >> well, from what i can see everything is working as expected. your >> phone requests pin code and we send it back. the next event shows >> that link key is generated and stored. so, "pairing" procedure is >> completed. >> >>> BTW, I tried with both : hccontrol -n ubt0hci >>> write_node_role_switch 0 and without it with the same result. >> >> no, that is not your problem. most likely the phone is trying to do >> something else after it has opened baseband connection. >> >> please install hcidump port from comms/hcidump and run as root >> >> # hcidump -w dump.file > > The file is attached. Actually the problem is only with pairing I > feel. The GPRS connection (through DUN) goes through, even if the > phone says there was an error. nope. the "paring" works as expected. the "pairing" is a authentication procedure, during which, both devices agree on "link key". "link key" can be programmed directly or auto generated from the "pin code". next time the devices talk to each other they will use the same link key. if any of the devices lost the "link key" or "link keys" do not match the connection is rejected. the fact that "dun/gprs" works means that your phone is accepting the connection from freebsd. by default most phones will try to authenticate this type of connection (with link key), so you need "pairing" done. in your particular scenario both freebsd and your phone are agreed on the link key and baseband connection was established. you get the error on the phone because phone is trying to query services available on freebsd. it is a mastery to me why some manufacturers assume that remote device will always answer service discovery query. if you only plan to use freebsd as a bluetooth client you never should be required to answer service discovery queries. in fact to do the pairing you only have anyway, to get rig of the error all you need to do is to run sdpd(8) daemon. just have it running all the time (similar to hcsecd(8)). you only need to kldload bg_btsocket(4) (from loader.conf) before you can start sdpd(8). there is no need to restart both hcsecd(8) and sdpd(8) even if you detach/re-attach the device. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Nov 17 22:20:40 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 AABF316A41F for ; Thu, 17 Nov 2005 22:20:40 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C4D843D45 for ; Thu, 17 Nov 2005 22:20:39 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jAHMK4J29706; Thu, 17 Nov 2005 17:20:05 -0500 Message-ID: <437D0212.5090200@savvis.net> Date: Thu, 17 Nov 2005 14:20:02 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Aniruddha Bohra References: <437CC18A.5040804@savvis.net> <437CDCE8.4060605@savvis.net> In-Reply-To: <437CDCE8.4060605@savvis.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: Cannot pair with Audiovox SMT5600 Bluetooth X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 22:20:40 -0000 err, sorry i was interrupted and sent this incomplete message ... >>> well, from what i can see everything is working as expected. your >>> phone requests pin code and we send it back. the next event shows >>> that link key is generated and stored. so, "pairing" procedure is >>> completed. >>> >>>> BTW, I tried with both : hccontrol -n ubt0hci >>>> write_node_role_switch 0 and without it with the same result. >>> >>> >>> no, that is not your problem. most likely the phone is trying to do >>> something else after it has opened baseband connection. >>> >>> please install hcidump port from comms/hcidump and run as root >>> >>> # hcidump -w dump.file >> >> >> The file is attached. Actually the problem is only with pairing I >> feel. The GPRS connection (through DUN) goes through, even if the >> phone says there was an error. > > nope. the "paring" works as expected. the "pairing" is a authentication > procedure, during which, both devices agree on "link key". "link key" > can be programmed directly or auto generated from the "pin code". next > time the devices talk to each other they will use the same link key. if > any of the devices lost the "link key" or "link keys" do not match the > connection is rejected. > > the fact that "dun/gprs" works means that your phone is accepting the > connection from freebsd. by default most phones will try to authenticate > this type of connection (with link key), so you need "pairing" done. > > in your particular scenario both freebsd and your phone are agreed on > the link key and baseband connection was established. you get the error > on the phone because phone is trying to query services available on > freebsd. it is a mastery to me why some manufacturers assume that remote > device will always answer service discovery query. if you only plan to > use freebsd as a bluetooth client you never should be required to answer > service discovery queries. in fact to do the pairing you only have to open baseband connection. there is no reason to go all the way to application level. > anyway, to get rig of the error all you need to do is to run sdpd(8) > daemon. just have it running all the time (similar to hcsecd(8)). you > only need to kldload bg_btsocket(4) (from loader.conf) before you can > start sdpd(8). there is no need to restart both hcsecd(8) and sdpd(8) > even if you detach/re-attach the device. > thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Fri Nov 18 01:48:50 2005 Return-Path: X-Original-To: bluetooth@freebsd.org 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 A26F816A41F for ; Fri, 18 Nov 2005 01:48:50 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4245B43D45 for ; Fri, 18 Nov 2005 01:48:49 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.25] ([192.168.42.25]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id jAI1mma0042295; Thu, 17 Nov 2005 19:48:48 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <437D32F7.10706@centtech.com> Date: Thu, 17 Nov 2005 19:48:39 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051021 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Maksim Yevmenkin References: <437B2E58.50709@centtech.com> <437B52FF.9040407@savvis.net> <437B5CE2.5000601@centtech.com> <437B93CF.4000403@savvis.net> <437BA490.1010704@centtech.com> <437BAF32.5030502@savvis.net> <437C8547.3060708@centtech.com> <437CC544.6080509@savvis.net> In-Reply-To: <437CC544.6080509@savvis.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1177/Thu Nov 17 02:35:37 2005 on mh1.centtech.com X-Virus-Status: Clean Cc: bluetooth Subject: Re: No route to host for bluetooth devices X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 01:48:50 -0000 Maksim Yevmenkin wrote: > Eric, > > [...] > >>>> I have a Sony VGN-A170P laptop, which does indeed include a switch. >>>> I verified that the switch was on, and the blue light that indicates >>>> the bluetooth is running was lit. The switch also controls the >>>> wireless card, which was working fine at the time. I also tried >>>> switching it off, waiting until the blue light went away, and then >>>> switching it back on, with no change. Only running the bluetooth >>>> script helped. >>> >>> >>> hmm... i'm surprised that switch did not help. on some laptops >>> bluetooth button/switch usually makes internal device to >>> disconnect/connect. in this case devd(8) will get detach/attach event >>> which will trigger 'bluetooth stop/start'. perhaps the switch only >>> controls the light? or may be the radio part of the device, i.e. >>> device will always stay attached, but the radio is powered off? did >>> you try to turn switch off and then bluetooth stop/start? does it >>> give you the same timeout error? >> >> >> Well, here's more information. First, it's reproducable every time I >> boot up. Doing: >> /etc/rc.d/bluetooth start ubt0 >> does not fix it by itself, but doing: >> /etc/rc.d/bluetooth stop ubt0 >> /etc/rc.d/bluetooth start ubt0 >> does. > > > now, i really puzzled. because device fails on to start at boot time, > /etc/rc.d/bluetooth should have backed out and removed all netgraph > nodes it tried to create (except device node and socket nodes). so i do > not understand why do you need to do 'stop' before 'start'. 'stop' > should really be a noop in this case. > > could you please do the following > > 1) do a fresh boot with bluetooth device turned on > > 2) after system boots (and bluetooth device failed to start) please run > as root > > # ngctl li There are 7 total nodes: Name: ngctl992 Type: socket ID: 0000001d Num hooks: 0 Name: ubt0l2cap Type: l2cap ID: 00000017 Num hooks: 3 Name: ubt0hci Type: hci ID: 00000013 Num hooks: 3 Name: btsock_l2c Type: btsock_l2c ID: 00000004 Num hooks: 1 Name: btsock_l2c_raw Type: btsock_l2c_raw ID: 00000003 Num hooks: 1 Name: btsock_hci_raw Type: btsock_hci_raw ID: 00000002 Num hooks: 1 Name: ubt0 Type: ubt ID: 00000001 Num hooks: 1 >> I also tried a fresh boot, then switching the bluetooth off, waiting >> about 20 seconds, and flipping it back on, which *did* in fact work. I >> may not have waited long enough the previous time that failed. > > > ah, ok. could you please check the /var/log/messages file to see if you > get a message saying ubt0 is detached/attached? Here's the snippet upon boot: Nov 17 19:31:32 neutrino kernel: ubt0: ALPS UGX, rev 1.10/11.68, addr 3 Nov 17 19:31:32 neutrino kernel: ubt0: ALPS UGX, rev 1.10/11.68, addr 3 Nov 17 19:31:32 neutrino kernel: ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 Nov 17 19:31:32 neutrino kernel: ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, buffer size=294 Nov 17 19:31:32 neutrino kernel: Device configuration finished. Nov 17 19:31:33 neutrino kernel: WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() Nov 17 19:31:34 neutrino kernel: WARNING: attempt to net_add_domain(netgraph) after domainfinalize() Nov 17 19:31:34 neutrino power_profile: changed to 'performance' Nov 17 19:31:35 neutrino savecore: no dumps found Nov 17 19:31:35 neutrino root: /etc/rc: INFO: amd depends on rpcbind, which will be forced to start. Nov 17 19:31:35 neutrino rpcbind: cannot create socket for udp6 Nov 17 19:31:41 neutrino kernel: ng_hci_process_command_timeout: ubt0hci - unable to complete HCI command OGF=0x3, OCF=0x3. Timeout Nov 17 19:31:43 neutrino kernel: kbd: new array size 4 Nov 17 19:31:43 neutrino kernel: kbd1 at vkbd0 Nov 17 19:31:43 neutrino lpd[613]: lpd startup: logging=1 net-secure Nov 17 19:31:44 neutrino lpd[613]: lpd startup: ready to accept requests Nov 17 19:31:45 neutrino sdpd[659]: Could not bind control socket. Permission denied (13) Nov 17 19:32:01 neutrino kernel: acpi_ec0: info: new max delay is 480 us Nov 17 19:37:19 neutrino kernel: acpi_ec0: info: new max delay is 530 us Nov 17 19:37:42 neutrino kernel: acpi_ec0: info: new max delay is 540 us Nov 17 19:37:54 neutrino kernel: acpi_ec0: info: new max delay is 560 us Nov 17 19:38:21 neutrino kernel: acpi_ec0: info: new max delay is 610 us now I'll run the bluetooth stop, which produces no output. ngctl li now looks like: There are 5 total nodes: Name: ngctl1015 Type: socket ID: 00000020 Num hooks: 0 Name: btsock_l2c Type: btsock_l2c ID: 00000004 Num hooks: 0 Name: btsock_l2c_raw Type: btsock_l2c_raw ID: 00000003 Num hooks: 0 Name: btsock_hci_raw Type: btsock_hci_raw ID: 00000002 Num hooks: 0 Name: ubt0 Type: ubt ID: 00000001 Num hooks: 0 Now I ran bluetooth start, which produces no output, and nothing in /var/log/messages. ngctl li now looks like this: There are 7 total nodes: Name: ngctl1045 Type: socket ID: 0000002c Num hooks: 0 Name: ubt0l2cap Type: l2cap ID: 00000026 Num hooks: 3 Name: ubt0hci Type: hci ID: 00000022 Num hooks: 3 Name: btsock_l2c Type: btsock_l2c ID: 00000004 Num hooks: 1 Name: btsock_l2c_raw Type: btsock_l2c_raw ID: 00000003 Num hooks: 1 Name: btsock_hci_raw Type: btsock_hci_raw ID: 00000002 Num hooks: 1 Name: ubt0 Type: ubt ID: 00000001 Num hooks: 1 Now I wiggle my mouse, and I see this in /var/log/messages: Nov 17 19:47:58 neutrino bthidd[603]: Accepted control connection from 00:07:61:31:27:15 Nov 17 19:47:58 neutrino bthidd[603]: Accepted interrupt connection from 00:07:61:31:27:15 and my mouse now works. >> Oddly enough, I never had a problem before now. I previously started >> the bluetooth stuff from rc.local. The only things I have changed >> are: updated to latest -current, removed inet6 from kernel, rebuilt >> world/kernel, switched to new rc.d bluetooth scripts. I can try >> anything you like. > > > one thing you could try to do is to comment out ubt0 section in > /etc/devd.conf and go back to old style rc.bluetooth script to see if > you have the same problem. if you do - then its not bluetooth related, > if you dont - then its related to new bluetooth rc.d scripts. I can do that if you'd like.. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-bluetooth@FreeBSD.ORG Fri Nov 18 12:41:39 2005 Return-Path: X-Original-To: bluetooth@freebsd.org 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 4D55D16A420 for ; Fri, 18 Nov 2005 12:41:39 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA8C943D64 for ; Fri, 18 Nov 2005 12:41:38 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id jAICfbZv039097; Fri, 18 Nov 2005 06:41:38 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <437DCBF8.1080000@centtech.com> Date: Fri, 18 Nov 2005 06:41:28 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051021 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Maksim Yevmenkin References: <437B2E58.50709@centtech.com> <437B52FF.9040407@savvis.net> <437B5CE2.5000601@centtech.com> <437B93CF.4000403@savvis.net> <437BA490.1010704@centtech.com> <437BAF32.5030502@savvis.net> <437C8547.3060708@centtech.com> <437CC544.6080509@savvis.net> <437D32F7.10706@centtech.com> In-Reply-To: <437D32F7.10706@centtech.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1178/Thu Nov 17 23:27:25 2005 on mh2.centtech.com X-Virus-Status: Clean Cc: bluetooth Subject: Re: No route to host for bluetooth devices X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 12:41:39 -0000 Eric Anderson wrote: > Maksim Yevmenkin wrote: > >> Eric, >> >> [...] >> >>>>> I have a Sony VGN-A170P laptop, which does indeed include a >>>>> switch. I verified that the switch was on, and the blue light that >>>>> indicates the bluetooth is running was lit. The switch also >>>>> controls the wireless card, which was working fine at the time. I >>>>> also tried switching it off, waiting until the blue light went >>>>> away, and then switching it back on, with no change. Only running >>>>> the bluetooth script helped. >>>> >>>> >>>> >>>> hmm... i'm surprised that switch did not help. on some laptops >>>> bluetooth button/switch usually makes internal device to >>>> disconnect/connect. in this case devd(8) will get detach/attach >>>> event which will trigger 'bluetooth stop/start'. perhaps the switch >>>> only controls the light? or may be the radio part of the device, >>>> i.e. device will always stay attached, but the radio is powered off? >>>> did you try to turn switch off and then bluetooth stop/start? does >>>> it give you the same timeout error? >>> >>> >>> >>> Well, here's more information. First, it's reproducable every time I >>> boot up. Doing: >>> /etc/rc.d/bluetooth start ubt0 >>> does not fix it by itself, but doing: >>> /etc/rc.d/bluetooth stop ubt0 >>> /etc/rc.d/bluetooth start ubt0 >>> does. >> >> >> >> now, i really puzzled. because device fails on to start at boot time, >> /etc/rc.d/bluetooth should have backed out and removed all netgraph >> nodes it tried to create (except device node and socket nodes). so i >> do not understand why do you need to do 'stop' before 'start'. 'stop' >> should really be a noop in this case. >> >> could you please do the following >> >> 1) do a fresh boot with bluetooth device turned on >> >> 2) after system boots (and bluetooth device failed to start) please >> run as root >> >> # ngctl li > > > > There are 7 total nodes: > Name: ngctl992 Type: socket ID: 0000001d Num hooks: 0 > Name: ubt0l2cap Type: l2cap ID: 00000017 Num hooks: 3 > Name: ubt0hci Type: hci ID: 00000013 Num hooks: 3 > Name: btsock_l2c Type: btsock_l2c ID: 00000004 Num hooks: 1 > Name: btsock_l2c_raw Type: btsock_l2c_raw ID: 00000003 Num hooks: 1 > Name: btsock_hci_raw Type: btsock_hci_raw ID: 00000002 Num hooks: 1 > Name: ubt0 Type: ubt ID: 00000001 Num hooks: 1 > > >>> I also tried a fresh boot, then switching the bluetooth off, waiting >>> about 20 seconds, and flipping it back on, which *did* in fact work. >>> I may not have waited long enough the previous time that failed. >> >> >> >> ah, ok. could you please check the /var/log/messages file to see if >> you get a message saying ubt0 is detached/attached? > > > Here's the snippet upon boot: > > Nov 17 19:31:32 neutrino kernel: ubt0: ALPS UGX, rev 1.10/11.68, addr 3 > Nov 17 19:31:32 neutrino kernel: ubt0: ALPS UGX, rev 1.10/11.68, addr 3 > Nov 17 19:31:32 neutrino kernel: ubt0: Interface 0 endpoints: > interrupt=0x81, bulk-in=0x82, bulk-out=0x2 > Nov 17 19:31:32 neutrino kernel: ubt0: Interface 1 (alt.config 5) > endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, > buffer size=294 > Nov 17 19:31:32 neutrino kernel: Device configuration finished. > Nov 17 19:31:33 neutrino kernel: WARNING: attempt to > net_add_domain(bluetooth) after domainfinalize() > Nov 17 19:31:34 neutrino kernel: WARNING: attempt to > net_add_domain(netgraph) after domainfinalize() > Nov 17 19:31:34 neutrino power_profile: changed to 'performance' > Nov 17 19:31:35 neutrino savecore: no dumps found > Nov 17 19:31:35 neutrino root: /etc/rc: INFO: amd depends on rpcbind, > which will be forced to start. > Nov 17 19:31:35 neutrino rpcbind: cannot create socket for udp6 > Nov 17 19:31:41 neutrino kernel: ng_hci_process_command_timeout: ubt0hci > - unable to complete HCI command OGF=0x3, OCF=0x3. Timeout > Nov 17 19:31:43 neutrino kernel: kbd: new array size 4 > Nov 17 19:31:43 neutrino kernel: kbd1 at vkbd0 > Nov 17 19:31:43 neutrino lpd[613]: lpd startup: logging=1 net-secure > Nov 17 19:31:44 neutrino lpd[613]: lpd startup: ready to accept requests > Nov 17 19:31:45 neutrino sdpd[659]: Could not bind control socket. > Permission denied (13) > Nov 17 19:32:01 neutrino kernel: acpi_ec0: info: new max delay is 480 us > Nov 17 19:37:19 neutrino kernel: acpi_ec0: info: new max delay is 530 us > Nov 17 19:37:42 neutrino kernel: acpi_ec0: info: new max delay is 540 us > Nov 17 19:37:54 neutrino kernel: acpi_ec0: info: new max delay is 560 us > Nov 17 19:38:21 neutrino kernel: acpi_ec0: info: new max delay is 610 us > > now I'll run the bluetooth stop, which produces no output. > > ngctl li now looks like: > There are 5 total nodes: > Name: ngctl1015 Type: socket ID: 00000020 Num hooks: 0 > Name: btsock_l2c Type: btsock_l2c ID: 00000004 Num hooks: 0 > Name: btsock_l2c_raw Type: btsock_l2c_raw ID: 00000003 Num hooks: 0 > Name: btsock_hci_raw Type: btsock_hci_raw ID: 00000002 Num hooks: 0 > Name: ubt0 Type: ubt ID: 00000001 Num hooks: 0 > > Now I ran bluetooth start, which produces no output, and nothing in > /var/log/messages. > > ngctl li now looks like this: > There are 7 total nodes: > Name: ngctl1045 Type: socket ID: 0000002c Num hooks: 0 > Name: ubt0l2cap Type: l2cap ID: 00000026 Num hooks: 3 > Name: ubt0hci Type: hci ID: 00000022 Num hooks: 3 > Name: btsock_l2c Type: btsock_l2c ID: 00000004 Num hooks: 1 > Name: btsock_l2c_raw Type: btsock_l2c_raw ID: 00000003 Num hooks: 1 > Name: btsock_hci_raw Type: btsock_hci_raw ID: 00000002 Num hooks: 1 > Name: ubt0 Type: ubt ID: 00000001 Num hooks: 1 > > > Now I wiggle my mouse, and I see this in /var/log/messages: > Nov 17 19:47:58 neutrino bthidd[603]: Accepted control connection from > 00:07:61:31:27:15 > Nov 17 19:47:58 neutrino bthidd[603]: Accepted interrupt connection from > 00:07:61:31:27:15 > > and my mouse now works. > > > >>> Oddly enough, I never had a problem before now. I previously started >>> the bluetooth stuff from rc.local. The only things I have changed >>> are: updated to latest -current, removed inet6 from kernel, rebuilt >>> world/kernel, switched to new rc.d bluetooth scripts. I can try >>> anything you like. >> >> >> >> one thing you could try to do is to comment out ubt0 section in >> /etc/devd.conf and go back to old style rc.bluetooth script to see if >> you have the same problem. if you do - then its not bluetooth related, >> if you dont - then its related to new bluetooth rc.d scripts. > > > I can do that if you'd like.. Something else I just tried: booted up, no mouse as usual. Ran /etc/rc.d/bluetooth start ubt0, and got this error: # /etc/rc.d/bluetooth start ubt0 /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0 and mouse still does not work.. Then, ran it again: # /etc/rc.d/bluetooth start ubt0 no error, and voila! my mouse works. Didn't run the 'stop' part at all, just the 'start' twice. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-bluetooth@FreeBSD.ORG Fri Nov 18 17:30:08 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 AF60D16A479 for ; Fri, 18 Nov 2005 17:30:08 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42EEF43D46 for ; Fri, 18 Nov 2005 17:30:05 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jAIHToJ26383; Fri, 18 Nov 2005 12:29:50 -0500 Message-ID: <437E0F8D.6050506@savvis.net> Date: Fri, 18 Nov 2005 09:29:49 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vijay Kiran References: <437CBFF8.7070709@savvis.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD_Bluetooth Subject: Re: Bluetooth on Laptop X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 17:30:08 -0000 Hello, > I've added the ng_ubt_load="YES" and rebooted. It fixed the problem, > hcccontrol inquiry command finds my Nokia 3230 phone via bluetooth :-) > But I dont know why it didn't work when I used plain kldload ng_ubt, did you load ng_ubt(4) module while bluetooth dongle was _attached_? if so, then it would not work, because other driver (i suspect ugen(4)) already claimed the device. you need to unplug the device _after_ you kldload ng_ubt(4) or do what you did and load ng_ubt(4) from loader. this way ng_ubt(4) will attach to the device. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Fri Nov 18 17:43:12 2005 Return-Path: X-Original-To: bluetooth@freebsd.org 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 83C0B16A41F for ; Fri, 18 Nov 2005 17:43:12 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBB3743D58 for ; Fri, 18 Nov 2005 17:42:54 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jAIHgqJ26764; Fri, 18 Nov 2005 12:42:52 -0500 Message-ID: <437E129A.9000204@savvis.net> Date: Fri, 18 Nov 2005 09:42:50 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <437B2E58.50709@centtech.com> <437B52FF.9040407@savvis.net> <437B5CE2.5000601@centtech.com> <437B93CF.4000403@savvis.net> <437BA490.1010704@centtech.com> <437BAF32.5030502@savvis.net> <437C8547.3060708@centtech.com> <437CC544.6080509@savvis.net> <437D32F7.10706@centtech.com> <437DCBF8.1080000@centtech.com> In-Reply-To: <437DCBF8.1080000@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: bluetooth Subject: Re: No route to host for bluetooth devices X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 17:43:12 -0000 Eric, >>>> Well, here's more information. First, it's reproducable every time >>>> I boot up. Doing: >>>> /etc/rc.d/bluetooth start ubt0 >>>> does not fix it by itself, but doing: >>>> /etc/rc.d/bluetooth stop ubt0 >>>> /etc/rc.d/bluetooth start ubt0 >>>> does. >>> >>> now, i really puzzled. because device fails on to start at boot time, >>> /etc/rc.d/bluetooth should have backed out and removed all netgraph >>> nodes it tried to create (except device node and socket nodes). so i >>> do not understand why do you need to do 'stop' before 'start'. 'stop' >>> should really be a noop in this case. >>> >>> could you please do the following >>> >>> 1) do a fresh boot with bluetooth device turned on >>> >>> 2) after system boots (and bluetooth device failed to start) please >>> run as root >>> >>> # ngctl li >> >> There are 7 total nodes: >> Name: ngctl992 Type: socket ID: 0000001d Num hooks: 0 >> Name: ubt0l2cap Type: l2cap ID: 00000017 Num hooks: 3 >> Name: ubt0hci Type: hci ID: 00000013 Num hooks: 3 >> Name: btsock_l2c Type: btsock_l2c ID: 00000004 Num hooks: 1 >> Name: btsock_l2c_raw Type: btsock_l2c_raw ID: 00000003 Num hooks: 1 >> Name: btsock_hci_raw Type: btsock_hci_raw ID: 00000002 Num hooks: 1 >> Name: ubt0 Type: ubt ID: 00000001 Num hooks: 1 hmm... that does not make much sense to me. somehow you still have all nodes connected even if bluetooth device failed to initialize! that explains why do you need 'stop' command before 'start'. just a crazy idea. please double that you are not initializing device twice, i.e. you use new rc.d scripts and some leftovers from old system. or may be you have devd(8) configuration in both /etc in /usr/local/etc? >>>> I also tried a fresh boot, then switching the bluetooth off, waiting >>>> about 20 seconds, and flipping it back on, which *did* in fact work. >>>> I may not have waited long enough the previous time that failed. >>> >>> ah, ok. could you please check the /var/log/messages file to see if >>> you get a message saying ubt0 is detached/attached? >> >> Here's the snippet upon boot: >> >> Nov 17 19:31:32 neutrino kernel: ubt0: ALPS UGX, rev 1.10/11.68, addr 3 >> Nov 17 19:31:32 neutrino kernel: ubt0: ALPS UGX, rev 1.10/11.68, addr 3 >> Nov 17 19:31:32 neutrino kernel: ubt0: Interface 0 endpoints: >> interrupt=0x81, bulk-in=0x82, bulk-out=0x2 >> Nov 17 19:31:32 neutrino kernel: ubt0: Interface 1 (alt.config 5) >> endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, >> buffer size=294 [...] >> Nov 17 19:31:41 neutrino kernel: ng_hci_process_command_timeout: >> ubt0hci - unable to complete HCI command OGF=0x3, OCF=0x3. Timeout device failed to initialize and rc.d/bluetooth should have cleaned the nodes, but it did not happen >> Nov 17 19:31:45 neutrino sdpd[659]: Could not bind control socket. >> Permission denied (13) hmm... this is bad too. can you double check if you have sdpd running? >> now I'll run the bluetooth stop, which produces no output. >> >> ngctl li now looks like: >> There are 5 total nodes: >> Name: ngctl1015 Type: socket ID: 00000020 Num hooks: 0 >> Name: btsock_l2c Type: btsock_l2c ID: 00000004 Num hooks: 0 >> Name: btsock_l2c_raw Type: btsock_l2c_raw ID: 00000003 Num hooks: 0 >> Name: btsock_hci_raw Type: btsock_hci_raw ID: 00000002 Num hooks: 0 >> Name: ubt0 Type: ubt ID: 00000001 Num hooks: 0 that is fine. that is what the output should look like when device is failed to initialize. >> Now I ran bluetooth start, which produces no output, and nothing in >> /var/log/messages. >> >> ngctl li now looks like this: >> There are 7 total nodes: >> Name: ngctl1045 Type: socket ID: 0000002c Num hooks: 0 >> Name: ubt0l2cap Type: l2cap ID: 00000026 Num hooks: 3 >> Name: ubt0hci Type: hci ID: 00000022 Num hooks: 3 >> Name: btsock_l2c Type: btsock_l2c ID: 00000004 Num hooks: 1 >> Name: btsock_l2c_raw Type: btsock_l2c_raw ID: 00000003 Num hooks: 1 >> Name: btsock_hci_raw Type: btsock_hci_raw ID: 00000002 Num hooks: 1 >> Name: ubt0 Type: ubt ID: 00000001 Num hooks: 1 and that is fine too - this is what output should look like when all nodes are properly connected. >> Now I wiggle my mouse, and I see this in /var/log/messages: >> Nov 17 19:47:58 neutrino bthidd[603]: Accepted control connection from >> 00:07:61:31:27:15 >> Nov 17 19:47:58 neutrino bthidd[603]: Accepted interrupt connection >> from 00:07:61:31:27:15 >> >> and my mouse now works. >> >>>> Oddly enough, I never had a problem before now. I previously >>>> started the bluetooth stuff from rc.local. The only things I have >>>> changed are: updated to latest -current, removed inet6 from kernel, >>>> rebuilt world/kernel, switched to new rc.d bluetooth scripts. I can >>>> try anything you like. >>> >>> one thing you could try to do is to comment out ubt0 section in >>> /etc/devd.conf and go back to old style rc.bluetooth script to see if >>> you have the same problem. if you do - then its not bluetooth >>> related, if you dont - then its related to new bluetooth rc.d scripts. >> >> I can do that if you'd like.. yes please, if you can. > Something else I just tried: booted up, no mouse as usual. Ran > /etc/rc.d/bluetooth start ubt0, and got this error: > > # /etc/rc.d/bluetooth start ubt0 > /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0 > > and mouse still does not work.. > > Then, ran it again: > # /etc/rc.d/bluetooth start ubt0 > > no error, and voila! my mouse works. Didn't run the 'stop' part at all, > just the 'start' twice. again the explanation for this is: after the boot device failed to initialize, but for whatever reason, all nodes are still connected. when you do the 'start' command it tries to connect nodes, but it fails because nodes are already connected. because it fails - it tries to clean up after itself and removes all the nodes. thus resetting back to defaults. the next 'start' runs fine, because now everything as it should be. we need to figure out why nodes are still connected after your device failed on boot. thanks, max