From owner-freebsd-bluetooth@FreeBSD.ORG Wed May 4 05:02:48 2005 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CCAF16A4CE for ; Wed, 4 May 2005 05:02:48 +0000 (GMT) Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01B6D43D75 for ; Wed, 4 May 2005 05:02:48 +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.04.01 201-2131-118-101-20041129) with ESMTP id <20050504050247.CHUF8952.mta9.adelphia.net@[192.168.1.254]>; Wed, 4 May 2005 01:02:47 -0400 Message-ID: <4278578F.8070006@savvis.net> Date: Tue, 03 May 2005 22:03:11 -0700 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: <4278433E.3050006@centtech.com> In-Reply-To: <4278433E.3050006@centtech.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-bluetooth@freebsd.org Subject: Re: Bluetooth device broken X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 May 2005 05:02:48 -0000 [moved to bluetooth@] Eric, > I'm trying to get the internal Bluetooth adapter in my Dell D610 > working. I see these messages on boot: > > ubt0: vendor 0x413c product 0x8103, rev 2.00/16.57, addr 2 > ubt0: vendor 0x413c product 0x8103, rev 2.00/16.57, 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 that looks just fine to me. the usb device has been recognized and it does seem to have all required usb interfaces/endpoints. > start_init: trying /sbin/init > WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() > WARNING: attempt to net_add_domain(netgraph) after domainfinalize() those are harmless, imo. i have those too. > Partial output from usbdevs -v: > Controller /dev/usb1: > addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), > Intel(0x0000), rev 1.00 > port 1 addr 2: full speed, self powered, config 1, product > 0x8103(0x8103), vendor 0x413c(0x413c), rev 16.57 that looks fine too > Do I just need to add the device info in a table somewhere, or are there > other issues (from the 'attempt to net_add_domain...' stuff)? why do you think your bluetooth device is broken? the fact that you do not see human readable name for your device's manufacturer/name does not mean that the device will not work. and, yes, if you want to see human readable names you need to add manufacturer (vendor) id and product id to the /sys/dev/usb/usbdevfs file. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Wed May 4 13:23:04 2005 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6EDB716A542 for ; Wed, 4 May 2005 13:23:04 +0000 (GMT) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6995F43D86 for ; Wed, 4 May 2005 13:23:03 +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 j44DMjsI099038; Wed, 4 May 2005 08:22:45 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4278CCA3.5080406@centtech.com> Date: Wed, 04 May 2005 08:22:43 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050325 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Maksim Yevmenkin References: <4278433E.3050006@centtech.com> <4278578F.8070006@savvis.net> In-Reply-To: <4278578F.8070006@savvis.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-bluetooth@freebsd.org Subject: Re: Bluetooth device broken X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 May 2005 13:23:04 -0000 Maksim Yevmenkin wrote: > [moved to bluetooth@] > > Eric, > >> I'm trying to get the internal Bluetooth adapter in my Dell D610 >> working. I see these messages on boot: >> >> ubt0: vendor 0x413c product 0x8103, rev 2.00/16.57, addr 2 >> ubt0: vendor 0x413c product 0x8103, rev 2.00/16.57, 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 > > > that looks just fine to me. the usb device has been recognized and it > does seem to have all required usb interfaces/endpoints. > >> start_init: trying /sbin/init >> WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() >> WARNING: attempt to net_add_domain(netgraph) after domainfinalize() > > > those are harmless, imo. i have those too. > >> Partial output from usbdevs -v: >> Controller /dev/usb1: >> addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), >> Intel(0x0000), rev 1.00 >> port 1 addr 2: full speed, self powered, config 1, product >> 0x8103(0x8103), vendor 0x413c(0x413c), rev 16.57 > > > that looks fine too > >> Do I just need to add the device info in a table somewhere, or are >> there other issues (from the 'attempt to net_add_domain...' stuff)? > > > why do you think your bluetooth device is broken? the fact that you do > not see human readable name for your device's manufacturer/name does not > mean that the device will not work. > > and, yes, if you want to see human readable names you need to add > manufacturer (vendor) id and product id to the /sys/dev/usb/usbdevfs file. Hmm.. I guess I should have tried it with the tools again. I tried this a weeks or two ago, and it would never create a ubt0 device for me to use, but now it works. (I've updated several times since then). Sorry for the false alarm!! I guess it was fixed and I didn't realize it! Now that's good service!! :) Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology A lost ounce of gold may be found, a lost moment of time never. ------------------------------------------------------------------------ From owner-freebsd-bluetooth@FreeBSD.ORG Wed May 4 20:54:41 2005 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCB8316A4CE for ; Wed, 4 May 2005 20:54:41 +0000 (GMT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A80343D60 for ; Wed, 4 May 2005 20:54:41 +0000 (GMT) (envelope-from wigglesworth02@comcast.net) Received: from [192.168.2.55] (c-24-125-177-237.hsd1.va.comcast.net[24.125.177.237]) by comcast.net (sccrmhc13) with SMTP id <2005050420382701600dt0lfe>; Wed, 4 May 2005 20:38:27 +0000 From: Martes G Wigglesworth To: Maksim Yevmenkin In-Reply-To: <4278F473.9060108@savvis.net> References: <200504210205.04358.jesse@theholymountain.com> <4267D2EC.90205@savvis.net> <1114102866.657.2.camel@Mobil1.276NET> <1114107065.657.14.camel@Mobil1.276NET> <1114109852.670.1.camel@Mobil1.276NET> <1114319343.676.2.camel@Mobil1.276NET> <426BE46C.20203@savvis.net> <1114475450.84979.16.camel@Mobil1.276NET> <1114477783.84979.20.camel@Mobil1.276NET> <1114545301.685.25.camel@Mobil1.276NET> <1115217422.2395.10.camel@Mobil1.276NET> <4278F473.9060108@savvis.net> Content-Type: multipart/mixed; boundary="=-dL1fmFoURe+xN3idBs+b" Message-Id: <1115239109.2395.32.camel@Mobil1.276NET> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 04 May 2005 16:38:29 -0400 cc: Bluetooth Subject: Re: The Bluetooth over Ambicom BT2000 adapter. X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: wigglesworth02@comcast.net List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 May 2005 20:54:42 -0000 --=-dL1fmFoURe+xN3idBs+b Content-Type: text/plain Content-Transfer-Encoding: 7bit No luck with ppp-over-usb. I am going to install linux on a spair laptop, and attempt to do the indigenous install of synce/etc... so that I can see if the issue truely is the ms-chap thing. I did find that my settings were for an exchange server, hence the connection attempts/failures looking as they did prior to the ms-chap. After removing the exchange server info, I realized that the authentication/usb ppp problem will not even let me associate the pda with the bsd box. I have nothing in the drop-down menu. Now, instead of just a connection failure, it just does not connect, and the pda tell me that I have to associate the pda with a pc first. Hence, I am back where I started. I posted on the synce list like three times, and no one will even bother to reply, including the "developers." There is a freebsd developer, and he has not made an appearance, after a few directed emails. Man, this should not be so difficult. Thanks for the attempts to help. I did eventually get a bluetooth usb adapter, however, there is no clear way to make the pda sync with the bsd box, anyhow, so even if we were able to get the adapter to work, I would not have found any clear method of installation anyway. All the bsd bluetooth stack stuff is working, I just can't figure out how to make the pda "pair" with the bsd box. When I try, I get nothing from the bsd box. I think that I am suppose to turn on some services, however, no one know what one are required to make pocketpc recognize that it should "pair" with the bsd box. Any further information would be very helpful. I have read through about three howtos, and all are geared towards nokia smartphones with bluetooth, or just a bluetooth phone. None say what I am supposed to do to make my bsd box "searchable" to other bluetooth devices. I also emailed the Ambicom people. They are completely unhelpful. They just seemed to restate my questions. I have attached this useless exchange. Maybe you can let me know, via translations, what the heck these people were talking about. I think that one of them actually emailed the other asking what a "baudrate" was..... :/ On Wed, 2005-05-04 at 12:12, Maksim Yevmenkin wrote: > Martes, > > > Have you had any luck with the Ambicom CF adapter? > > unfortunately, no. i still did not get one :( i bid on ebay on several > similar adapters, but i was outbid :( > > did you manage to get ppp-over-usb stuff working? > > thanks, > max --=-dL1fmFoURe+xN3idBs+b Content-Disposition: attachment; filename=Ambicomemail Content-Type: text/plain; name=Ambicomemail; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi, Our CF card is only working at that baudrate, I don't know how you configured your system. that is the fact. Ambicom ----- Original Message ----- From: "Martes G Wigglesworth" To: "xing guo" Cc: "AmbiCom" Sent: Wednesday, April 27, 2005 5:08 PM Subject: Re: Problems using BT2000D-CF adapter on Unix/Linux > What are you talking about? > > I already said that it only will respond to 2400 baud. How am I > supposed to go about setting something like that? > > Did you even read my email? > > On Wed, 2005-04-27 at 12:44, xing guo wrote: > > Hi, Wigglesworth: > > You can try to set the baudrate to 14.4Kbps. > > > > Ambicom > > > > ----- Original Message ----- > > From: "AmbiCom" > > To: > > Sent: Tuesday, April 26, 2005 1:01 PM > > Subject: FW: Problems using BT2000D-CF adapter on Unix/Linux > > > > > > > > xing, > > > > know any of this baud rate thing? > > > > > > -----Original Message----- > > From: Martes G Wigglesworth [mailto:wigglesworth02@comcast.net] > > Sent: Tuesday, April 26, 2005 12:39 PM > > To: support@ambicom.com > > Subject: Problems using BT2000D-CF adapter on Unix/Linux > > > > > > I have been trying to get this card to work on my unix system for a > > month. I have a program that sends the CF card information, and waits > > for it to send back info. I have gotten it from a buddy, so I am not > > sure how it works, however, when I use the program, it only responds on > > 2400 baud. I think that there may be something wrong with my card, and > > it is too late to get a replacement from CompUSA. Can you give any > > assistance? > > I am using the product listed below: > > > > Ambicom Bluetooth CF adapter w/ PCMCIA adapter. > > Model: BT2000D-CF > > S/N: BT2442000048 > > MAC: 001060AB1C4A > > Adapter for PCMCIA Interface: > > S/N: C030168201 > --=-dL1fmFoURe+xN3idBs+b-- From owner-freebsd-bluetooth@FreeBSD.ORG Wed May 4 21:21:18 2005 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B50016A4CE for ; Wed, 4 May 2005 21:21:18 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5815143D49 for ; Wed, 4 May 2005 21:21:17 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailgate1b.savvis.net (Postfix) with ESMTP id B66743BEF9; Wed, 4 May 2005 16:20:41 -0500 (CDT) Received: from mailgate1b.savvis.net ([127.0.0.1]) by localhost (mailgate1b.savvis.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 18642-01-15; Wed, 4 May 2005 16:20:41 -0500 (CDT) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45]) by mailgate1b.savvis.net (Postfix) with ESMTP id 7FCCB3BE6C; Wed, 4 May 2005 16:20:41 -0500 (CDT) Received: from s228130hz1ew031.apptix-01.savvis.net ([10.146.4.28]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 4 May 2005 16:20:24 -0500 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew031.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 4 May 2005 16:20:17 -0500 Message-ID: <42793C90.5040904@savvis.net> Date: Wed, 04 May 2005 14:20:16 -0700 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: wigglesworth02@comcast.net References: <200504210205.04358.jesse@theholymountain.com> <4267D2EC.90205@savvis.net> <1114102866.657.2.camel@Mobil1.276NET> <4267DE6C.1040508@savvis.net> <1114107065.657.14.camel@Mobil1.276NET> <4267F2C5.7020306@savvis.net> <1114109852.670.1.camel@Mobil1.276NET> <1114319343.676.2.camel@Mobil1.276NET> <426BE46C.20203@savvis.net> <426D7939.4010401@savvis.net> <1114475450.84979.16.camel@Mobil1.276NET> <426D8EC8.6090803@savvis.net> <1114477783.84979.20.camel@Mobil1.276NET> <426E6F4F.3020306@savvis.net> <1114545301.685.25.camel@Mobil1.276NET> <426EA3FE.3020902@savvis.net> <1115217422.2395.10.camel@Mobil1.276NET> <4278F473.9060108@savvis.net> <1115239109.2395.32.camel@Mobil1.276NET> In-Reply-To: <1115239109.2395.32.camel@Mobil1.276NET> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 04 May 2005 21:20:17.0170 (UTC) FILETIME=[118BAF20:01C550EF] X-Virus-Scanned: amavisd-new at savvis.net X-Mailman-Approved-At: Thu, 05 May 2005 11:56:08 +0000 Subject: Re: The Bluetooth over Ambicom BT2000 adapter. X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 May 2005 21:21:18 -0000 Martes, > No luck with ppp-over-usb. bad :( if you want i could try to help you to get this working, but we better take it off the list. > I am going to install linux on a spair laptop, and attempt to do the > indigenous install of synce/etc... so that I can see if the issue truely > is the ms-chap thing. I did find that my settings were for an exchange > server, hence the connection attempts/failures looking as they did prior > to the ms-chap. After removing the exchange server info, I realized ok, we have official disconnect now :) how does exchange server came into this mess? :) do you mean "exchange server" as "microsoft exchange server", i.e. mail server? > that the authentication/usb ppp problem will not even let me associate > the pda with the bsd box. I have nothing in the drop-down menu. Now, > instead of just a connection failure, it just does not connect, and the > pda tell me that I have to associate the pda with a pc first. Hence, I > am back where I started. i think we should take this off the list and go back to the beginning. so you have a pda that runs some soft of microsoft operating system, right? you also have a some sort of usb cable/cradle that you could plug into into your pda (the other end obviously goes into your pc), right? lets forget everything else for now. what happens on bsd when you just connect pda and pc with the usb cable? does bsd recognize that you have plugged the cable? what driver (if any) gets attached? ugen(4), uvisor(4), ucom(4), uftdi(4) etc? /var/log/messages should tell you that. also running "usbdevs -dv" as root should tell you which usb devices are attached. > I posted on the synce list like three times, and no one will even bother > to reply, including the "developers." There is a freebsd developer, and > he has not made an appearance, after a few directed emails. Man, this > should not be so difficult. no, it should not. just need to understand what exactly is the problem. > Thanks for the attempts to help. I did eventually get a bluetooth usb > adapter, however, there is no clear way to make the pda sync with the > bsd box, anyhow, so even if we were able to get the adapter to work, I > would not have found any clear method of installation anyway. All the > bsd bluetooth stack stuff is working, I just can't figure out how to > make the pda "pair" with the bsd box. "pairing" is handled by hcsecd(8) daemon. you need to add an entry for your pda in /etc/bluetooth/hcsecd.conf (see the file and the man page for details) and then run hcsecd(8) as root. > When I try, I get nothing from the bsd box. I think that I am suppose > to turn on some services, however, no one know what one are required to > make pocketpc recognize that it should "pair" with the bsd box. "pairing" has nothing to do with the services. the idea of "pairing" is to create pre-shared key which both devices can use to encrypt data. > Any further information would be very helpful. I have read through > about three howtos, and all are geared towards nokia smartphones with > bluetooth, or just a bluetooth phone. None say what I am supposed to do > to make my bsd box "searchable" to other bluetooth devices. your bsd box is "searchable"/"visible"/whatever by default. the reason is that you getting nothing from bsd box is because (like you said) you do not run any services. at least you should start service discovery daemon (sdpd(8)) after you start bluetooth stack. as root type "/usr/sbin/sdpd". after that you should be able to check if daemon is running by "/usr/sbin/sdpcontrol -l browse" as root. service discovery daemon (sdpd(8)) provides Service Discovery Service that other bluetooth devices (such as your pda) can use to discover other services that you have on your pc. note: both sdpd and hcsecd should only be started once (after you start bluetooth stack for the first time). once started these daemons will run until you reboot your pc. you can start/stop bluetooth stack while these daemons are running. > I also emailed the Ambicom people. They are completely unhelpful. They > just seemed to restate my questions. I have attached this useless > exchange. Maybe you can let me know, via translations, what the heck > these people were talking about. I think that one of them actually > emailed the other asking what a "baudrate" was..... :/ at least they said something about 14400 (14.4Kbps). i did not expect you would get anything other then "canned" reply - you are not using "supported" os, so get lost. thanks, max