From owner-freebsd-bluetooth@FreeBSD.ORG Sun Apr 17 23:08:34 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 2082816A4CE; Sun, 17 Apr 2005 23:08:34 +0000 (GMT) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7378543D1D; Sun, 17 Apr 2005 23:08:33 +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 (sccrmhc11) with SMTP id <2005041723083201100hmlnbe>; Sun, 17 Apr 2005 23:08:32 +0000 From: Martes G Wigglesworth To: Hackers-list-bsd , Norfolk Unix Users' Group , freebsd-questions , Bluetooth Content-Type: text/plain Message-Id: <1113779315.669.266.camel@Mobil1.276NET> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 17 Apr 2005 19:08:35 -0400 Content-Transfer-Encoding: 7bit Subject: Possible Kernel patch/hack needed, for use of Ambicom BT2000 CF 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: Sun, 17 Apr 2005 23:08:34 -0000 I am having difficulties using my CF/PCCard Bluetooth adapter from Ambicom. I have found similar error messages, associated with an individual that was attempting to get his palm to sync with BSD, back in 2003. The respondent to the individual's inquiry, indicated a patch, and the subsequent response was that the patch worked. I am unable to locate the archived mail, via google, however, I am new to patching, and have not yet been able to figure out where I might do so. I get continuous loop of errors when attempting to use the rc.bluetooth script, or hcseriald with the correct ttyd4 device. Can anyone indicate where I might find a way to patch this problem, or if I may be able to edit some src, that has to do with this device interface driver? (sio4) I get the following in my dmesg output while executing the following: >hcseriald -d -f /dev/ttyd4 -n sio4 -s 115200 >ng_h4_input: sio4 - ignoring unknown packet type=0 >ng_h4_input: sio4 - ignoring unknown packet type=0x80 >dmesg output for the connection renders the following: >sio4: at port 0x3e8-0x3ef irq 11 >function 0 config 2 on pccard1 >sio4: type 16550A >sio4: unable to activate interrupt in fast mode - using normal mode I am stuck, and unable to get any farther than the start of hcseriald. I am unable to use my bluetooth at all, because I am unable to even find a good howto for using hcseriald or even how I am supposed to connect the interface even if I can use hcseriald. Nothing ever happens other than the output listed above. my system is as follows: FreeBSD 5.3-Release Bluetooth CF Adapter: Ambicom BT2000 via PCCard CF adapter Asus M6BN Please give some direction. I am at a loss. From owner-freebsd-bluetooth@FreeBSD.ORG Mon Apr 18 01:18:09 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 EC97716A4CE for ; Mon, 18 Apr 2005 01:18:08 +0000 (GMT) Received: from mta11.adelphia.net (mta11.adelphia.net [68.168.78.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EEC843D2D for ; Mon, 18 Apr 2005 01:18:08 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [192.168.1.254] (really [70.32.199.60]) by mta11.adelphia.net (InterMail vM.6.01.04.01 201-2131-118-101-20041129) with ESMTP id <20050418011807.LVKY5402.mta11.adelphia.net@[192.168.1.254]>; Sun, 17 Apr 2005 21:18:07 -0400 Message-ID: <42630AE5.2070909@savvis.net> Date: Sun, 17 Apr 2005 18:18:29 -0700 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: wigglesworth02@comcast.net References: <1113779315.669.266.camel@Mobil1.276NET> In-Reply-To: <1113779315.669.266.camel@Mobil1.276NET> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Bluetooth cc: Norfolk Unix Users' Group Subject: Re: Possible Kernel patch/hack needed, for use of Ambicom BT2000 CF 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: Mon, 18 Apr 2005 01:18:09 -0000 Martes, > I am having difficulties using my CF/PCCard Bluetooth adapter from > Ambicom. I have found similar error messages, associated with an > individual that was attempting to get his palm to sync with BSD, back in > 2003. The respondent to the individual's inquiry, indicated a patch, > and the subsequent response was that the patch worked. I am unable to > locate the archived mail, via google, however, I am new to patching, and > have not yet been able to figure out where I might do so. I get > continuous loop of errors when attempting to use the rc.bluetooth > script, or hcseriald with the correct ttyd4 device. > > Can anyone indicate where I might find a way to patch this problem, or > if I may be able to edit some src, that has to do with this device > interface driver? (sio4) serial bluetooth devices do not work very well currently. the reason is high interrupt latency. because of it sio(4) driver can not fetch bytes from fifo in time and this creates fifo overflows and some characters are lost. when this happens host and adapter are considered to be out of sync. unfortunately, bluetooth serial transport protocol (chapter h4 in bluetooth specification) is very simple and does not provide any way to recover from "out of sync" condition. removable bluetooth serial devices (such as pcmcia cards etc.) are even worse. not only you have the high interrupt latency problem, but now you have to try to convince the system to assign separate irq to the device. if separate irq can not be assigned (for whatever reason) the system uses shared irq. this means there could be several interrupt handlers attached to the same irq. in this case once interrupt happens every interrupt handler must be called and check if it has anything to do. i'm not sure about the patch you are talking about, but you could try to search for "silo overflow". you would normally see these messages (from sio(4) driver) when it can not fetch data from the fifo. > I get the following in my dmesg output while executing the following: > >>hcseriald -d -f /dev/ttyd4 -n sio4 -s 115200 > >>ng_h4_input: sio4 - ignoring unknown packet type=0 >>ng_h4_input: sio4 - ignoring unknown packet type=0x80 typically those errors mean that the host and the adapter are out of sync. the ng_h4(4) line discipline tries to split incoming stream data (from the bluetooth adapter) into separate bluetooth hci packets. it expects to find certain bytes that denote the beginning of each packet etc. and can not find them. >>dmesg output for the connection renders the following: >>sio4: at port 0x3e8-0x3ef irq 11 >>function 0 config 2 on pccard1 >>sio4: type 16550A >>sio4: unable to activate interrupt in fast mode - using normal mode well, "unable to activate interrupt in fast mode" is not a good thing. i think it means device got shared irq. > I am stuck, and unable to get any farther than the start of hcseriald. > I am unable to use my bluetooth at all, because I am unable to even find > a good howto for using hcseriald or even how I am supposed to connect > the interface even if I can use hcseriald. Nothing ever happens other > than the output listed above. yes, unfortunately handbook does not have any examples, but it is fairly simple. once you have plugged your bluetooth card all you need to do is to start bluetooth stack, i.e. as root # rc.bluetooth start sio4 you will find example rc.bluetooth script in /usr/share/examples/netgraph/bluetooth. this script is generic and should work for you. the script will load all required modules and will start hcseriald(8) for you. after you run the script you should see the output very similar to one in the freebsd handbook. then you should be able to follow handbook instructions - just replace adapter name, i.e. use "sio4hci" instead of "ub0hci" etc. thanks, max p.s. in the future please do not cross post into several freebsd lists. From owner-freebsd-bluetooth@FreeBSD.ORG Mon Apr 18 04:36:21 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 AC4CB16A4CE for ; Mon, 18 Apr 2005 04:36:21 +0000 (GMT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FDD943D55 for ; Mon, 18 Apr 2005 04:36:21 +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 (rwcrmhc11) with SMTP id <2005041804361001300kdm9qe>; Mon, 18 Apr 2005 04:36:20 +0000 From: Martes G Wigglesworth To: Maksim Yevmenkin In-Reply-To: <42630AE5.2070909@savvis.net> References: <1113779315.669.266.camel@Mobil1.276NET> <42630AE5.2070909@savvis.net> Content-Type: text/plain Message-Id: <1113798969.651.5.camel@Mobil1.276NET> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Mon, 18 Apr 2005 00:36:09 -0400 Content-Transfer-Encoding: 7bit cc: Bluetooth cc: Norfolk Unix Users' Group Subject: Re: Possible Kernel patch/hack needed, for use of Ambicom BT2000 CF 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: Mon, 18 Apr 2005 04:36:21 -0000 Thanks for the info. I appologize for cross-posting, however, I have been posting this problem on different lists for about a week, and no responses came back, so I decided to multply my output in the hopes for a response. Anyhow: When I attempt the rc.bluetooth script, I get the following: > ># sudo /etc/rc.bluetooth start sio4 > # > #Could not execute command "reset". Operation timed out I also find it extremely difficult to get anywhere when things don't work. Whenever I post to the appropriate list, I get nothing. In fact, your very needed response, only came in spite of my posts to Bluetooth, and Stable, where I would hope I would be able to find such informed answers. Any tips on specific posts, such as mine? It is like people only want to talk about hacking stuff that works already, and don't budge, when something needs repair, or explanation. Thanks again, for your input. Got anything on my results from the rc.bluetooth script? From owner-freebsd-bluetooth@FreeBSD.ORG Mon Apr 18 16:35:23 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 7D4C216A4CE for ; Mon, 18 Apr 2005 16:35:23 +0000 (GMT) Received: from mta10.adelphia.net (mta10.adelphia.net [68.168.78.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA90D43D58 for ; Mon, 18 Apr 2005 16:35:22 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [192.168.1.254] (really [70.32.199.60]) by mta10.adelphia.net (InterMail vM.6.01.04.01 201-2131-118-101-20041129) with ESMTP id <20050418163522.KYGM7277.mta10.adelphia.net@[192.168.1.254]>; Mon, 18 Apr 2005 12:35:22 -0400 Message-ID: <4263E1E0.1000303@savvis.net> Date: Mon, 18 Apr 2005 09:35:44 -0700 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: wigglesworth02@comcast.net References: <1113779315.669.266.camel@Mobil1.276NET> <42630AE5.2070909@savvis.net> <1113798969.651.5.camel@Mobil1.276NET> In-Reply-To: <1113798969.651.5.camel@Mobil1.276NET> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Bluetooth cc: Norfolk Unix Users' Group Subject: Re: Possible Kernel patch/hack needed, for use of Ambicom BT2000 CF 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: Mon, 18 Apr 2005 16:35:23 -0000 Martes, > Thanks for the info. I appologize for cross-posting, however, I have > been posting this problem on different lists for about a week, and no > responses came back, so I decided to multply my output in the hopes for > a response. hmmm... i must have missed it :( > Anyhow: > > When I attempt the rc.bluetooth script, I get the following: > >>># sudo /etc/rc.bluetooth start sio4 >> >># >>#Could not execute command "reset". Operation timed out "reset" is the very first command in the initialization sequence. since it has timed out then communication between host and adapter is broken (for whatever reason). after google'ing a bit i found out that this particular card 1. uses 16c950/954 uart, which is a good thing because it has 128 bytes fifo (compared to 16 bytes in 16c550a). you might want to try puc(4) driver that might have support for this uart. 2. apparently needs extra initialization sequence. that is you need to send extra vendor specific command to the adapter to setup uart speed. my guess item (2) above is the reason why you got timeout in "reset". basically i need to prepare a patch for hcseriald(8) and send it to you. it will take me a few days to do that. since i do not have the card here i will rely on you to help me with testing. in the mean time you might want to try item (1) above to see if puc(4) driver works and recognize 16c950/954 uart. if you feel like hacking it yourself, you might want to take a look as linux bluez hciattach utility (online cvs http://cvs.sourceforge.net/viewcvs.py/bluez/utils/tools/hciattach.c?rev=1.29&view=markup). this utility does a similar (to hciseriald(8)) job. if you get it working please send me the patches and i will review and commit them. > I also find it extremely difficult to get anywhere when things don't work. Whenever I post to the appropriate list, > I get nothing. again, i must have missed it. i usually read bluetooth@ and mobile@ and look for bluetooth related questions. please use bluetooth@ list for all your bluetooth related questions. > In fact, your very needed response, only came in spite of my posts to Bluetooth, and Stable, where I would hope > I would be able to find such informed answers. > > Any tips on specific posts, such as mine? It is like people only want to talk about hacking stuff > that works already, and don't budge, when something needs repair, or explanation. it is better to post bluetooth related questions in bluetooth@ mailing list. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Mon Apr 18 21:10:07 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 4498B16A4CE for ; Mon, 18 Apr 2005 21:10:07 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B03843D2D for ; Mon, 18 Apr 2005 21:10:06 +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 (sccrmhc12) with SMTP id <200504182110040120052gsee>; Mon, 18 Apr 2005 21:10:04 +0000 From: Martes G Wigglesworth To: Maksim Yevmenkin , Bluetooth In-Reply-To: <4263E1E0.1000303@savvis.net> References: <1113779315.669.266.camel@Mobil1.276NET> <42630AE5.2070909@savvis.net> <1113798969.651.5.camel@Mobil1.276NET> <4263E1E0.1000303@savvis.net> Content-Type: text/plain Message-Id: <1113858606.651.10.camel@Mobil1.276NET> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Mon, 18 Apr 2005 17:10:06 -0400 Content-Transfer-Encoding: 7bit Subject: Re: Possible Kernel patch/hack needed, for use of Ambicom BT2000 CF 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: Mon, 18 Apr 2005 21:10:07 -0000 Thanks for the response. I am just starting into the C-programming stuff. I have some good books, but I won't be taking my C++ class until the fall, so I am just winging it currently. Are there any good howtos on what is needed to patch as you have indicated? I really want to get into this stuff, however, I am not well versed in programming operating systems, yet. Any hints? I have downloaded the Architecure Manual/Handbook, for FreeBSD, but I was hoping for a no frills quick-start, for someone like myself. I have not found good information on what in actually involved in patching the kernel. Thanks again, and will be waiting for that patch. On Mon, 2005-04-18 at 12:35, Maksim Yevmenkin wrote: > Martes, > > > Thanks for the info. I appologize for cross-posting, however, I have > > been posting this problem on different lists for about a week, and no > > responses came back, so I decided to multply my output in the hopes for > > a response. > > hmmm... i must have missed it :( > > > Anyhow: > > > > When I attempt the rc.bluetooth script, I get the following: > > > >>># sudo /etc/rc.bluetooth start sio4 > >> > >># > >>#Could not execute command "reset". Operation timed out > > "reset" is the very first command in the initialization sequence. since > it has timed out then communication between host and adapter is broken > (for whatever reason). > > after google'ing a bit i found out that this particular card > > 1. uses 16c950/954 uart, which is a good thing because it has 128 bytes > fifo (compared to 16 bytes in 16c550a). you might want to try puc(4) > driver that might have support for this uart. > > 2. apparently needs extra initialization sequence. that is you need to > send extra vendor specific command to the adapter to setup uart speed. > > my guess item (2) above is the reason why you got timeout in "reset". > basically i need to prepare a patch for hcseriald(8) and send it to you. > it will take me a few days to do that. since i do not have the card here > i will rely on you to help me with testing. > > in the mean time you might want to try item (1) above to see if puc(4) > driver works and recognize 16c950/954 uart. > > if you feel like hacking it yourself, you might want to take a look as > linux bluez hciattach utility (online cvs > http://cvs.sourceforge.net/viewcvs.py/bluez/utils/tools/hciattach.c?rev=1.29&view=markup). > this utility does a similar (to hciseriald(8)) job. if you get it > working please send me the patches and i will review and commit them. > > > I also find it extremely difficult to get anywhere when things don't work. Whenever I post to the appropriate list, > > I get nothing. > > again, i must have missed it. i usually read bluetooth@ and mobile@ and > look for bluetooth related questions. please use bluetooth@ list for all > your bluetooth related questions. > > > In fact, your very needed response, only came in spite of my posts to Bluetooth, and Stable, where I would hope > > I would be able to find such informed answers. > > > > Any tips on specific posts, such as mine? It is like people only want to talk about hacking stuff > > that works already, and don't budge, when something needs repair, or explanation. > > it is better to post bluetooth related questions in bluetooth@ mailing list. > > thanks, > max > From owner-freebsd-bluetooth@FreeBSD.ORG Tue Apr 19 16:53:16 2005 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0655A16A4CE for ; Tue, 19 Apr 2005 16:53:16 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B75A43D39 for ; Tue, 19 Apr 2005 16:53:15 +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 769C33BF77; Tue, 19 Apr 2005 11:53:14 -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 26922-01-43; Tue, 19 Apr 2005 11:53:14 -0500 (CDT) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45]) by mailgate1b.savvis.net (Postfix) with ESMTP id 3EBDE3BE25; Tue, 19 Apr 2005 11:53:14 -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); Tue, 19 Apr 2005 11:52:48 -0500 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew031.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Tue, 19 Apr 2005 11:52:30 -0500 Message-ID: <42653749.8090601@savvis.net> Date: Tue, 19 Apr 2005 09:52:25 -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: <1113779315.669.266.camel@Mobil1.276NET> <42630AE5.2070909@savvis.net> <1113798969.651.5.camel@Mobil1.276NET> <4263E1E0.1000303@savvis.net> <1113858606.651.10.camel@Mobil1.276NET> In-Reply-To: <1113858606.651.10.camel@Mobil1.276NET> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 19 Apr 2005 16:52:30.0217 (UTC) FILETIME=[2CB2F790:01C54500] X-Virus-Scanned: amavisd-new at savvis.net cc: Bluetooth Subject: Re: Possible Kernel patch/hack needed, for use of Ambicom BT2000 CF 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: Tue, 19 Apr 2005 16:53:16 -0000 Martes, sorry for the delay. > Thanks for the response. I am just starting into the C-programming > stuff. I have some good books, but I won't be taking my C++ class until > the fall, so I am just winging it currently. Are there any good howtos that's fine. btw for this particular project you would not need c++. everything is written in c. > on what is needed to patch as you have indicated? I really want to get i do not think so. i would recommend to get a good unix programming book. something like Advanced Programming in the UNIX Environment, Addison-Wesley, 1992, ISBN 0-201-56317-7 > into this stuff, however, I am not well versed in programming operating > systems, yet. Any hints? I have downloaded the Architecure > Manual/Handbook, for FreeBSD, but I was hoping for a no frills > quick-start, for someone like myself. I have not found good information > on what in actually involved in patching the kernel. again, for this particular project, you probably wont have to patch the kernel. i need to change hcseriald(8) (which is a user-space daemon) so it would send extra initialization command to the device. since device looks like a serial port (modem) all i need to do is to send/receive few bytes to/from serial port. thanks, max > Thanks again, and will be waiting for that patch. > > On Mon, 2005-04-18 at 12:35, Maksim Yevmenkin wrote: > >>Martes, >> >> >>>Thanks for the info. I appologize for cross-posting, however, I have >>>been posting this problem on different lists for about a week, and no >>>responses came back, so I decided to multply my output in the hopes for >>>a response. >> >>hmmm... i must have missed it :( >> >> >>>Anyhow: >>> >>>When I attempt the rc.bluetooth script, I get the following: >>> >>> >>>>># sudo /etc/rc.bluetooth start sio4 >>>> >>>># >>>>#Could not execute command "reset". Operation timed out >> >>"reset" is the very first command in the initialization sequence. since >>it has timed out then communication between host and adapter is broken >>(for whatever reason). >> >>after google'ing a bit i found out that this particular card >> >>1. uses 16c950/954 uart, which is a good thing because it has 128 bytes >>fifo (compared to 16 bytes in 16c550a). you might want to try puc(4) >>driver that might have support for this uart. >> >>2. apparently needs extra initialization sequence. that is you need to >>send extra vendor specific command to the adapter to setup uart speed. >> >>my guess item (2) above is the reason why you got timeout in "reset". >>basically i need to prepare a patch for hcseriald(8) and send it to you. >>it will take me a few days to do that. since i do not have the card here >>i will rely on you to help me with testing. >> >>in the mean time you might want to try item (1) above to see if puc(4) >>driver works and recognize 16c950/954 uart. >> >>if you feel like hacking it yourself, you might want to take a look as >>linux bluez hciattach utility (online cvs >>http://cvs.sourceforge.net/viewcvs.py/bluez/utils/tools/hciattach.c?rev=1.29&view=markup). >>this utility does a similar (to hciseriald(8)) job. if you get it >>working please send me the patches and i will review and commit them. >> >> >>>I also find it extremely difficult to get anywhere when things don't work. Whenever I post to the appropriate list, >>>I get nothing. >> >>again, i must have missed it. i usually read bluetooth@ and mobile@ and >>look for bluetooth related questions. please use bluetooth@ list for all >>your bluetooth related questions. >> >> >>>In fact, your very needed response, only came in spite of my posts to Bluetooth, and Stable, where I would hope >>>I would be able to find such informed answers. >>> >>>Any tips on specific posts, such as mine? It is like people only want to talk about hacking stuff >>>that works already, and don't budge, when something needs repair, or explanation. >> >>it is better to post bluetooth related questions in bluetooth@ mailing list. >> >>thanks, >>max >> > > From owner-freebsd-bluetooth@FreeBSD.ORG Wed Apr 20 11:56:56 2005 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2356E16A4CF for ; Wed, 20 Apr 2005 11:56:56 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id EE76A43D39 for ; Wed, 20 Apr 2005 11:56:54 +0000 (GMT) (envelope-from free.bsd@gmx.net) Received: (qmail invoked by alias); 20 Apr 2005 11:56:53 -0000 Received: from pD9E7FFC8.dip.t-dialin.net (EHLO [192.168.2.101]) [217.231.255.200] by mail.gmx.net (mp030) with SMTP; 20 Apr 2005 13:56:53 +0200 X-Authenticated: #20105305 Message-ID: <4266436A.9080406@gmx.net> Date: Wed, 20 Apr 2005 19:56:26 +0800 From: FreeBSD Daemon User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-bluetooth@freebsd.org, freebsd-hardware@freebsd.org, freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: USB Bluetooth dongle recommendation 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, 20 Apr 2005 11:56:56 -0000 dear list, i will have to work on a project involving bluetooth technologie, for this i will have to get me a usb bluetooth dongle. i would be very happy to receive recommendations on devices that work esecially well (under FreeBSD). TIA zheyu From owner-freebsd-bluetooth@FreeBSD.ORG Wed Apr 20 16:50:17 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 B725816A4CE for ; Wed, 20 Apr 2005 16:50:17 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D0CE43D1F for ; Wed, 20 Apr 2005 16:50: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 DFFDF3BFAF; Wed, 20 Apr 2005 11:50:16 -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 00522-01-38; Wed, 20 Apr 2005 11:50:16 -0500 (CDT) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45]) by mailgate1b.savvis.net (Postfix) with ESMTP id B65BE3BF64; Wed, 20 Apr 2005 11:50:16 -0500 (CDT) Received: from s228130hz1ew171.apptix-01.savvis.net ([10.146.4.29]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 20 Apr 2005 11:50:03 -0500 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew171.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 20 Apr 2005 11:49:48 -0500 Message-ID: <42668833.3060104@savvis.net> Date: Wed, 20 Apr 2005 09:49:55 -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: FreeBSD Daemon References: <4266436A.9080406@gmx.net> In-Reply-To: <4266436A.9080406@gmx.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 20 Apr 2005 16:49:48.0345 (UTC) FILETIME=[F6A10290:01C545C8] X-Virus-Scanned: amavisd-new at savvis.net cc: freebsd-bluetooth@freebsd.org Subject: Re: USB Bluetooth dongle recommendation 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, 20 Apr 2005 16:50:17 -0000 hello, > i will have to work on a project involving bluetooth technologie, for > this i will have to get me a usb bluetooth dongle. > i would be very happy to receive recommendations on devices that work > esecially well (under FreeBSD). any bluetooth usb device that conforms with the bluetooth specification v1.1 should work. bluetooth usb devices based on broadcom bluetooth chip may require firmware download. they will work, but you need to obtain firmware elsewhere. csr chip based devices usually work very well right out of the box. the following link may help you with your decision http://www.holtmann.org/linux/bluetooth/features.html thanks, max p.s. please do not cross post to multiple freebsd mailing lists. From owner-freebsd-bluetooth@FreeBSD.ORG Wed Apr 20 18:18:19 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 900D616A4CE for ; Wed, 20 Apr 2005 18:18:19 +0000 (GMT) Received: from ronald.echteman.nl (h8441134153.dsl.speedlinq.nl [84.41.134.153]) by mx1.FreeBSD.org (Postfix) with SMTP id 16F1743D2D for ; Wed, 20 Apr 2005 18:18:18 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: (qmail 11758 invoked from network); 20 Apr 2005 18:18:16 -0000 Received: from unknown (HELO laptop.klop.ws) (10.0.1.4) by ronald.echteman.nl with SMTP; 20 Apr 2005 18:18:16 -0000 Received: (qmail 829 invoked from network); 20 Apr 2005 18:17:54 -0000 Received: from localhost.thuis.klop.ws (HELO smtp.local) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; 20 Apr 2005 18:17:54 -0000 Date: Wed, 20 Apr 2005 20:17:50 +0200 To: freebsd-bluetooth@freebsd.org References: <42444AB4.7080300@savvis.net> <42483D9F.2090805@savvis.net> From: "Ronald Klop" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: User-Agent: Opera M2/7.54 (FreeBSD, build 955) Subject: Re: bthidd 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, 20 Apr 2005 18:18:19 -0000 On Wed, 30 Mar 2005 16:12:05 +0200, Ronald Klop wrote: > On Mon, 28 Mar 2005 09:23:43 -0800, Maksim Yevmenkin > wrote: > >> Ronald, >> >>>>> Is bthidd usable? It isn't connected to the build. >>>> >>>> define "usable"? :) you should be able to use it with bluetooth >>>> mice, but not with bluetooth keyboards. so, imo, its not very usable >>>> at the moment. bluetooth keyboard support is not there because i do >>>> not like the fact that i can not have more then one keyboard >>>> attached to the system. as soon as i find some time i will look into >>>> the system console driver to see what it takes to add support for >>>> more then one keyboard. >>> Usable... Mmm. I have a SonyEricsson K700i phone and on Windows I can >>> use the joystick of the phone as a mouse to control mediaplayer, etc. >>> I would like to do the same on FreeBSD, just for the coolness of it. >>> :-) >> >> :) >> >>> Can I just do this? >> >> i do not know. it depends. if k700i looks like mouse then it most >> likely will work. if k700i looks like keypad/keyboard then it will not >> work (for the reason described above - cant have more then one active >> keyboard/keypad attached to the console). >> >> there is a bthidcontrol(8) tool in >> /usr/src/usr.sbin/bluetooth/bthidcontrol. could you please compile it >> and send me the output of "query" command? there is a bthidcontrol.8 >> man page in the same directory ("nroff -man bthidcontrol.8 |less" - to >> read it) >> >>> cd /usr/src/usr.sbin/bluetooth/bthidd/ >>> make && make install && make clean >>> Or is there more to it? >> >> you will also need to create /etc/bluetooth/bthidd.conf configuration >> file. bthidcontrol(8) will help you with that. > > Thanks for the info. I'm going to try this soon. But I left my phone at > my moms house, just one evening before she went on holiday for two > weeks. :-( Da phone is back. # bthidcontrol -a phone query device { bdaddr 00:0f:de:78:93:d8; control_psm 0x11; interrupt_psm 0x13; reconnect_initiate true; battery_power false; normally_connectable false; hid_descriptor { 0x05 0x01 0x09 0x06 0xa1 0x01 0x85 0x01 0x05 0x07 0x19 0xe0 0x29 0xe7 0x15 0x00 0x25 0x01 0x75 0x01 0x95 0x08 0x81 0x02 0x95 0x01 0x75 0x08 0x81 0x03 0x95 0x05 0x75 0x01 0x05 0x08 0x19 0x01 0x29 0x05 0x91 0x02 0x95 0x01 0x75 0x03 0x91 0x03 0x95 0x06 0x75 0x08 0x15 0x00 0x25 0x65 0x05 0x07 0x19 0x00 0x29 0x65 0x81 0x00 0xc0 0x05 0x01 0x09 0x02 0xa1 0x01 0x85 0x02 0x09 0x01 0xa1 0x00 0x05 0x09 0x19 0x01 0x29 0x03 0x15 0x00 0x25 0x01 0x95 0x03 0x75 0x01 0x81 0x02 0x95 0x01 0x75 0x05 0x81 0x03 0x05 0x01 0x09 0x30 0x09 0x31 0x15 0x81 0x25 0x7f 0x75 0x08 0x95 0x02 0x81 0x06 0xc0 0xc0 }; } # bthidcontrol -a phone query > /etc/bluetooth/bthidd.conf # bthidd -d > bthidd[786]: Accepted control connection from 00:0f:de:78:93:d8 > bthidd[786]: Accepted interrupt connection from 00:0f:de:78:93:d8 that looks fine. it means there is a hid session between phone and the computer. please use hcidump to see if there is any hid events going from the phone. > And now I'm stuck. I don't see a new device in /dev or a msg in > dmesg/console. there wont be any device. the mouse part *might* work. btw try to run bthidd on console (not on xterm). thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Apr 20 20:06:26 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 DC0D516A4CE for ; Wed, 20 Apr 2005 20:06:26 +0000 (GMT) Received: from ronald.echteman.nl (h8441134153.dsl.speedlinq.nl [84.41.134.153]) by mx1.FreeBSD.org (Postfix) with SMTP id AA2A043D1D for ; Wed, 20 Apr 2005 20:06:25 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: (qmail 12416 invoked from network); 20 Apr 2005 20:06:23 -0000 Received: from unknown (HELO laptop.klop.ws) (10.0.1.4) by ronald.echteman.nl with SMTP; 20 Apr 2005 20:06:23 -0000 Received: (qmail 12340 invoked from network); 20 Apr 2005 20:06:21 -0000 Received: from localhost.thuis.klop.ws (HELO smtp.local) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; 20 Apr 2005 20:06:21 -0000 To: freebsd-bluetooth@freebsd.org References: <42444AB4.7080300@savvis.net> <42483D9F.2090805@savvis.net> <4266B2DA.50609@savvis.net> Message-ID: Date: Wed, 20 Apr 2005 22:06:17 +0200 From: "Ronald Klop" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: <4266B2DA.50609@savvis.net> User-Agent: Opera M2/7.54 (FreeBSD, build 955) Subject: Re: bthidd 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, 20 Apr 2005 20:06:27 -0000 On Wed, 20 Apr 2005 12:51:54 -0700, Maksim Yevmenkin wrote: > Ronald, > >>>>>>> Is bthidd usable? It isn't connected to the build. >>>>>> >>>>>> >>>>>> define "usable"? :) you should be able to use it with bluetooth >>>>>> mice, but not with bluetooth keyboards. so, imo, its not very >>>>>> usable at the moment. bluetooth keyboard support is not there >>>>>> because i do not like the fact that i can not have more then one >>>>>> keyboard attached to the system. as soon as i find some time i >>>>>> will look into the system console driver to see what it takes to >>>>>> add support for more then one keyboard. >>>>> >>>>> Usable... Mmm. I have a SonyEricsson K700i phone and on Windows I >>>>> can use the joystick of the phone as a mouse to control >>>>> mediaplayer, etc. I would like to do the same on FreeBSD, just for >>>>> the coolness of it. :-) >>>> >>>> :) >>>> >>>>> Can I just do this? >>>> >>>> i do not know. it depends. if k700i looks like mouse then it most >>>> likely will work. if k700i looks like keypad/keyboard then it will >>>> not work (for the reason described above - cant have more then one >>>> active keyboard/keypad attached to the console). >>>> >>>> there is a bthidcontrol(8) tool in >>>> /usr/src/usr.sbin/bluetooth/bthidcontrol. could you please compile >>>> it and send me the output of "query" command? there is a >>>> bthidcontrol.8 man page in the same directory ("nroff -man >>>> bthidcontrol.8 |less" - to read it) >>>> >>>>> cd /usr/src/usr.sbin/bluetooth/bthidd/ >>>>> make && make install && make clean >>>>> Or is there more to it? >>>> >>>> you will also need to create /etc/bluetooth/bthidd.conf >>>> configuration file. bthidcontrol(8) will help you with that. >>> >>> Thanks for the info. I'm going to try this soon. But I left my phone >>> at my moms house, just one evening before she went on holiday for >>> two weeks. :-( >> Da phone is back. >> # bthidcontrol -a phone query >> device { >> bdaddr 00:0f:de:78:93:d8; >> control_psm 0x11; >> interrupt_psm 0x13; >> reconnect_initiate true; >> battery_power false; >> normally_connectable false; >> hid_descriptor { >> 0x05 0x01 0x09 0x06 0xa1 0x01 0x85 0x01 >> 0x05 0x07 0x19 0xe0 0x29 0xe7 0x15 0x00 >> 0x25 0x01 0x75 0x01 0x95 0x08 0x81 0x02 >> 0x95 0x01 0x75 0x08 0x81 0x03 0x95 0x05 >> 0x75 0x01 0x05 0x08 0x19 0x01 0x29 0x05 >> 0x91 0x02 0x95 0x01 0x75 0x03 0x91 0x03 >> 0x95 0x06 0x75 0x08 0x15 0x00 0x25 0x65 >> 0x05 0x07 0x19 0x00 0x29 0x65 0x81 0x00 >> 0xc0 0x05 0x01 0x09 0x02 0xa1 0x01 0x85 >> 0x02 0x09 0x01 0xa1 0x00 0x05 0x09 0x19 >> 0x01 0x29 0x03 0x15 0x00 0x25 0x01 0x95 >> 0x03 0x75 0x01 0x81 0x02 0x95 0x01 0x75 >> 0x05 0x81 0x03 0x05 0x01 0x09 0x30 0x09 >> 0x31 0x15 0x81 0x25 0x7f 0x75 0x08 0x95 >> 0x02 0x81 0x06 0xc0 0xc0 >> }; >> } > > i have copied your config and run 'bthidcontrol dump' > > % bthidcontrol -a 00:0f:de:78:93:d8 dump > Collection page=Generic_Desktop usage=Keyboard > Input id=1 size=1 count=1 page=Keyboard usage=Keyboard_LeftControl > Variable, logical range 0..1 > Input id=1 size=1 count=1 page=Keyboard usage=Keyboard_LeftShift > Variable, logical range 0..1 > Input id=1 size=1 count=1 page=Keyboard usage=Keyboard_LeftAlt > Variable, logical range 0..1 > Input id=1 size=1 count=1 page=Keyboard usage=Keyboard_Left_GUI > Variable, logical range 0..1 > Input id=1 size=1 count=1 page=Keyboard usage=Keyboard_RightControl > Variable, logical range 0..1 > Input id=1 size=1 count=1 page=Keyboard usage=Keyboard_RightShift > Variable, logical range 0..1 > Input id=1 size=1 count=1 page=Keyboard usage=Keyboard_RightAlt > Variable, logical range 0..1 > Input id=1 size=1 count=1 page=Keyboard usage=Keyboard_Right_GUI > Variable, logical range 0..1 > Input id=1 size=8 count=1 page=0x0000 usage=0x0000 Const Variable, > logical range 0..1 > Output id=1 size=1 count=1 page=LEDs usage=Num_Lock Variable, logical > range 0..1 > Output id=1 size=1 count=1 page=LEDs usage=Caps_Lock Variable, logical > range 0..1 > Output id=1 size=1 count=1 page=LEDs usage=Scroll_Lock Variable, > logical range 0..1 > Output id=1 size=1 count=1 page=LEDs usage=Compose Variable, logical > range 0..1 > Output id=1 size=1 count=1 page=LEDs usage=Kana Variable, logical range > 0..1 > Output id=1 size=3 count=1 page=0x0000 usage=0x0000 Const Variable, > logical range 0..1 > Input id=1 size=8 count=6 page=Keyboard > usage=Reserved_(no_event_indicated), logical range 0..101 > End collection > Collection page=Generic_Desktop usage=Mouse > Collection page=Generic_Desktop usage=Pointer > Input id=2 size=1 count=1 page=Button usage=Button_1 Variable, logical > range 0..1 > Input id=2 size=1 count=1 page=Button usage=Button_2 Variable, logical > range 0..1 > Input id=2 size=1 count=1 page=Button usage=Button_3 Variable, logical > range 0..1 > Input id=2 size=5 count=1 page=0x0000 usage=0x0000 Const Variable, > logical range 0..1 > Input id=2 size=8 count=1 page=Generic_Desktop usage=X Variable > Relative, logical range -127..127 > Input id=2 size=8 count=1 page=Generic_Desktop usage=Y Variable > Relative, logical range -127..127 > End collection > End collection > > looks like the phone has both keyboard and the mouse part. do you know > if phone sends mouse events (if you move joystick i guess)? how about > running 'hcidump' while pressing buttons on the phone? > >> # bthidcontrol -a phone query > /etc/bluetooth/bthidd.conf >> # bthidd -d >> >> bthidd[786]: Accepted control connection from 00:0f:de:78:93:d8 >> bthidd[786]: Accepted interrupt connection from 00:0f:de:78:93:d8 > > that looks fine. it means there is a hid session between phone and the > computer. please use hcidump to see if there is any hid events going > from the phone. > >> And now I'm stuck. I don't see a new device in /dev or a msg in >> dmesg/console. > > there wont be any device. the mouse part *might* work. btw try to run > bthidd on console (not on xterm). I understand more now. I need to run moused to make it work. With moused I can use my phone to control the mouse-pointer and mouse-buttons on the console. I think I need to set up X11 to use moused for this to work on X also. Does this work? Ronald -- Ronald Klop, Amsterdam, The Netherlands From owner-freebsd-bluetooth@FreeBSD.ORG Wed Apr 20 20:18:35 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 84DF016A4CE for ; Wed, 20 Apr 2005 20:18:35 +0000 (GMT) Received: from ronald.echteman.nl (h8441134153.dsl.speedlinq.nl [84.41.134.153]) by mx1.FreeBSD.org (Postfix) with SMTP id 858F043D49 for ; Wed, 20 Apr 2005 20:18:34 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: (qmail 12544 invoked from network); 20 Apr 2005 20:18:32 -0000 Received: from unknown (HELO laptop.klop.ws) (10.0.1.4) by ronald.echteman.nl with SMTP; 20 Apr 2005 20:18:31 -0000 Received: (qmail 14754 invoked from network); 20 Apr 2005 20:18:29 -0000 Received: from localhost.thuis.klop.ws (HELO smtp.local) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; 20 Apr 2005 20:18:29 -0000 To: freebsd-bluetooth@freebsd.org References: <42444AB4.7080300@savvis.net> <42483D9F.2090805@savvis.net> <4266B2DA.50609@savvis.net> Message-ID: Date: Wed, 20 Apr 2005 22:18:27 +0200 From: "Ronald Klop" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Opera M2/7.54 (FreeBSD, build 955) Subject: Re: bthidd 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, 20 Apr 2005 20:18:35 -0000 On Wed, 20 Apr 2005 22:13:10 +0200, Ronald Klop wrote: > On Wed, 20 Apr 2005 12:51:54 -0700, Maksim Yevmenkin > wrote: > >> Ronald, > > [ removed a lot of text ] > >> looks like the phone has both keyboard and the mouse part. do you know >> if phone sends mouse events (if you move joystick i guess)? how about >> running 'hcidump' while pressing buttons on the phone? >> >>> # bthidcontrol -a phone query > /etc/bluetooth/bthidd.conf >>> # bthidd -d >>> >>> bthidd[786]: Accepted control connection from 00:0f:de:78:93:d8 >>> bthidd[786]: Accepted interrupt connection from 00:0f:de:78:93:d8 >> >> that looks fine. it means there is a hid session between phone and >> the computer. please use hcidump to see if there is any hid events >> going from the phone. >> >>> And now I'm stuck. I don't see a new device in /dev or a msg in >>> dmesg/console. >> >> there wont be any device. the mouse part *might* work. btw try to run >> bthidd on console (not on xterm). > > I understand more now. I need to run moused to make it work. With moused > I can use my phone to control the mouse-pointer and mouse-buttons on > the console. I think I need to set up X11 to use moused for this to > work on X also. Does this work? right, i assumed you ran moused(8). so, basically here is what i do 1) run moused(8) 2) specify 'Option "Device" "/dev/sysmouse"' in my /etc/X11/XF86Config 3) run bthidd(8) on the console. now i can control mouse pointer in both console and X with both (wired and wireless) mice. thanks for the hcidump. it shows that phone sends both mouse and keyboard events. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Apr 20 21:16:25 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 728FC16A4CE for ; Wed, 20 Apr 2005 21:16:25 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD6CB43D2F for ; Wed, 20 Apr 2005 21:16:24 +0000 (GMT) (envelope-from wigglesworth02@comcast.net) Received: from [192.168.1.101] (unknown[128.172.172.195]) by comcast.net (sccrmhc12) with SMTP id <2005042021162401200f44vue>; Wed, 20 Apr 2005 21:16:24 +0000 From: Martes G Wigglesworth To: Bluetooth Message-Id: <1114031784.668.54.camel@Mobil1.276NET> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 20 Apr 2005 17:16:24 -0400 Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: The Bluetooth over Ambicom BT2000 CF adapter debug 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, 20 Apr 2005 21:16:25 -0000 Hey, Makism: I tried the extra device, "card" and it caused a bad compile, so I left it out. I added pcic, since that was the only attribute not present, and have restarted. I have edited the appropriate sysctl options: #> sudo sysctl -w hw.cardbus.debug=1 #hw.cardbus.debug: 0 -> 1 #> sudo sysctl -w hw.cardbus.cis_debug=1 #hw.cardbus.cis_debug: 0 -> 1 #> sudo sysctl -w hw.pccard.debug=1 #hw.pccard.debug: 0 -> 1 #> sudo sysctl -w hw.pccard.cis_debug=1 #hw.pccard.cis_debug: 0 -> 1 #> After plugging my adapter into the machine: "Please reference attached text file, titled: BT2000-post-sysctledit-with-device-inserted-with-messagesout ." After editing the rc.bluetooth script, as prescribed by you, I came up with the following errors: Reference: "BT2000-post-sysctledit-with-device-inserted-with-s57600-messagesout." The messages come so quickly that I am unable to stop them fast enough to get the entire sequence, so I just picked an arbitrary place, prior to the Timeout, and copied it. I hope this helps. PS: No luck with pccard dumpcis. I get the following output: #> sudo pccardc dumpcis #0 slots found -- Martes G Wigglesworth, CEO WiggTekMicroSystems, Inc. From owner-freebsd-bluetooth@FreeBSD.ORG Thu Apr 21 06:05:52 2005 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA8A216A4CE for ; Thu, 21 Apr 2005 06:05:52 +0000 (GMT) Received: from ms-smtp-01.rdc-nyc.rr.com (ms-smtp-01-smtplb.rdc-nyc.rr.com [24.29.109.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9C2343D41 for ; Thu, 21 Apr 2005 06:05:51 +0000 (GMT) (envelope-from jesse@theholymountain.com) Received: from [192.168.2.6] (cpe-24-90-151-231.nyc.res.rr.com [24.90.151.231])j3L65mT3006254; Thu, 21 Apr 2005 02:05:49 -0400 (EDT) From: Jesse Callaway Date: Thu, 21 Apr 2005 02:05:03 -0400 User-Agent: KMail/1.7.2 To: FreeBSD Daemon MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200504210205.04358.jesse@theholymountain.com> X-Virus-Scanned: Symantec AntiVirus Scan Engine cc: freebsd-bluetooth@freebsd.org Subject: Fwd: USB Bluetooth dongle recommendation X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2005 06:05:52 -0000 Sorry this isn't indented... I have been borrowing my friend's D-Link Bluetooth DBT-120 usb device. As far as I know my knowledge of bluetooth has been the only source of failure. I'm running 5.3 i386. I can post a more detailed message if you want. I am not sure if this device works "especially" well but it seems to do the trick. -jesse ---------- Forwarded Message ---------- Subject: USB Bluetooth dongle recommendation Date: Wednesday 20 April 2005 07:56 am From: FreeBSD Daemon To: freebsd-bluetooth@freebsd.org, freebsd-hardware@freebsd.org, freebsd-questions@freebsd.org dear list, i will have to work on a project involving bluetooth technologie, for this i will have to get me a usb bluetooth dongle. i would be very happy to receive recommendations on devices that work esecially well (under FreeBSD). TIA zheyu _______________________________________________ freebsd-bluetooth@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@freebsd.org" ------------------------------------------------------- From owner-freebsd-bluetooth@FreeBSD.ORG Thu Apr 21 16:14:39 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 4D29E16A4CE for ; Thu, 21 Apr 2005 16:14:39 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id E27A143D45 for ; Thu, 21 Apr 2005 16:14:38 +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 E30CE3C155; Thu, 21 Apr 2005 11:14:37 -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 07466-01-88; Thu, 21 Apr 2005 11:14:37 -0500 (CDT) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45]) by mailgate1b.savvis.net (Postfix) with ESMTP id B5BEE3C142; Thu, 21 Apr 2005 11:14:37 -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); Thu, 21 Apr 2005 11:14:37 -0500 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew031.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 21 Apr 2005 11:14:20 -0500 Message-ID: <4267D15B.8090801@savvis.net> Date: Thu, 21 Apr 2005 09:14:19 -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: Guillermo Sobalvarro References: <20050421094810.11686.qmail@web52601.mail.yahoo.com> In-Reply-To: <20050421094810.11686.qmail@web52601.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 21 Apr 2005 16:14:20.0221 (UTC) FILETIME=[2C94CED0:01C5468D] X-Virus-Scanned: amavisd-new at savvis.net cc: Bluetooth Subject: Re: USB Dongle X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2005 16:14:39 -0000 Guillermo, please read bluetooth chapter in the freebsd handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-bluetooth.html all your questions and more are answered there. > Max, thank you for your reply. As you state, I must > be doing something wrong because when I connect the > dongle all I get in /var/log/messages is: > > Apr 21 04:39:37 toshi kernel: ugen0: 3Com Bluetooth > USB dongle, rev 1.10/5.26, addr 2 well, you did not load ng_ubt(4) driver. ugen(4) is a *generic* usb device driver. it will attach to *any* usb device if no other driver claims it. > As to rc.bluetooth in /usr/local/etc, I have no such > file/script. Must be I have something missing from my > system that I have not installed? Please point this > out if it is the case and what steps I have to take to > get it to work. i just copied /usr/share/examples/netgraph/bluetooth/rc.bluetooth script. this is a generic script that will work for most bluetooth users. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Apr 21 16:21:43 2005 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2937E16A4CE for ; Thu, 21 Apr 2005 16:21:43 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6E5B43D3F for ; Thu, 21 Apr 2005 16:21:42 +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 986183BE45; Thu, 21 Apr 2005 11:21:42 -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 07547-01-92; Thu, 21 Apr 2005 11:21:42 -0500 (CDT) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45]) by mailgate1b.savvis.net (Postfix) with ESMTP id 6F8093BEBC; Thu, 21 Apr 2005 11:21:42 -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); Thu, 21 Apr 2005 11:21:18 -0500 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew031.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 21 Apr 2005 11:20:59 -0500 Message-ID: <4267D2EC.90205@savvis.net> Date: Thu, 21 Apr 2005 09:21:00 -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: Jesse Callaway References: <200504210205.04358.jesse@theholymountain.com> In-Reply-To: <200504210205.04358.jesse@theholymountain.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 21 Apr 2005 16:20:59.0829 (UTC) FILETIME=[1AC42650:01C5468E] X-Virus-Scanned: amavisd-new at savvis.net cc: freebsd-bluetooth@freebsd.org Subject: Re: Fwd: USB Bluetooth dongle recommendation X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2005 16:21:43 -0000 Jesse, > Sorry this isn't indented... > > I have been borrowing my friend's D-Link Bluetooth DBT-120 usb > device. As far as I know my knowledge of bluetooth has been the only > source of failure. I'm running 5.3 i386. I can post a more detailed > message if you want. I am not sure if this device works "especially" > well but it seems to do the trick. if you did not report the problem i can not look into it and help you to fix it :) care to tell us what sort of bluetooth failures you are having? also, earlier revisions of d-link dbt-120 adapter were using broadcom bluetooth chip. basically you have to obtain firmware elsewhere (either windows cd that came with adapter or linux bluez) and use bcmfw(8) tool (included with freebsd) to download firmware into the adapter. then it works. i have belkin bluetooth adapter that is broadcom bluetooth chip based and it works just fine. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Apr 21 17:01:08 2005 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE5F416A4CE for ; Thu, 21 Apr 2005 17:01:08 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FDB743D55 for ; Thu, 21 Apr 2005 17:01:08 +0000 (GMT) (envelope-from wigglesworth02@comcast.net) Received: from [192.168.1.101] (unknown[128.172.172.195]) by comcast.net (sccrmhc12) with SMTP id <2005042117010701200f4gqae>; Thu, 21 Apr 2005 17:01:07 +0000 From: Martes G Wigglesworth To: Maksim Yevmenkin In-Reply-To: <4267D2EC.90205@savvis.net> References: <200504210205.04358.jesse@theholymountain.com> <4267D2EC.90205@savvis.net> Content-Type: text/plain Message-Id: <1114102866.657.2.camel@Mobil1.276NET> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 21 Apr 2005 13:01:06 -0400 Content-Transfer-Encoding: 7bit cc: Bluetooth Subject: The Bluetooth over Ambicom BT2000 adapter thing... 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: Thu, 21 Apr 2005 17:01:09 -0000 Greetings. I have not seen any responses to my last two emails, did you get the required information, from my last post? I know that you are busy, however, I can resend the information, if you did not get it. I was hoping that you had some information on why my pccardc dumpcis output indicated 0 found. Thanks. -- Martes G Wigglesworth, CEO WiggTekMicroSystems, Inc. From owner-freebsd-bluetooth@FreeBSD.ORG Thu Apr 21 17:10:23 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 1893316A4CE for ; Thu, 21 Apr 2005 17:10:23 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5E8643D49 for ; Thu, 21 Apr 2005 17:10:22 +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 664A43BEFB; Thu, 21 Apr 2005 12:10:22 -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 09232-01-44; Thu, 21 Apr 2005 12:10:22 -0500 (CDT) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44]) by mailgate1b.savvis.net (Postfix) with ESMTP id 3810B3BE45; Thu, 21 Apr 2005 12:10:22 -0500 (CDT) Received: from s228130hz1ew031.apptix-01.savvis.net ([10.146.4.28]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 21 Apr 2005 12:10:15 -0500 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew031.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 21 Apr 2005 12:10:05 -0500 Message-ID: <4267DE6C.1040508@savvis.net> Date: Thu, 21 Apr 2005 10:10:04 -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> In-Reply-To: <1114102866.657.2.camel@Mobil1.276NET> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 21 Apr 2005 17:10:05.0302 (UTC) FILETIME=[F667A960:01C54694] X-Virus-Scanned: amavisd-new at savvis.net cc: Bluetooth Subject: Re: The Bluetooth over Ambicom BT2000 adapter thing... X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2005 17:10:23 -0000 Martes, > I have not seen any responses to my last two emails, did you get the > required information, from my last post? I know that you are busy, > however, I can resend the information, if you did not get it. yes, i have receved your email, but i did not get required information. i did not get the file you were refering to "BT2000-post-sysctledit-with-device-inserted-with-s57600-messagesout." > I was hoping that you had some information on why my pccardc dumpcis > output indicated 0 found. well, may be i did not explain it correctly, but in your kernel config you can have, *either* 1) NEWCARD device cbb # cardbus (yenta) bridge device pccard device cardbus *or* 2) OLDCARD device card # pccard bus device pcic # PCMCIA bridge entries, but *not both*. if you have (1) in your kernel config then you need to use sysctl's commands. if you have (2) in you kernel config then you need to use "pccardc dumpcis" also puc(4) driver will not attach to you card because it does not have your card id's in the list of supported devices. that is why i need to get manufacturer id and product id to add them to puc(4) driver. thanks, max p.s. if you know the where i can buy similar (to yours) card for under $30 please let me know. From owner-freebsd-bluetooth@FreeBSD.ORG Thu Apr 21 18:37:09 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 922D516A4CE for ; Thu, 21 Apr 2005 18:37:09 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E92743D4C for ; Thu, 21 Apr 2005 18:37:09 +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 6C1D03BE9E; Thu, 21 Apr 2005 13:37:08 -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 11977-01-14; Thu, 21 Apr 2005 13:37:08 -0500 (CDT) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45]) by mailgate1b.savvis.net (Postfix) with ESMTP id 3DEE23BE2A; Thu, 21 Apr 2005 13:37:08 -0500 (CDT) Received: from s228130hz1ew171.apptix-01.savvis.net ([10.146.4.29]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 21 Apr 2005 13:37:05 -0500 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew171.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 21 Apr 2005 13:36:54 -0500 Message-ID: <4267F2C5.7020306@savvis.net> Date: Thu, 21 Apr 2005 11:36:53 -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> In-Reply-To: <1114107065.657.14.camel@Mobil1.276NET> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 21 Apr 2005 18:36:54.0941 (UTC) FILETIME=[17977CD0:01C546A1] X-Virus-Scanned: amavisd-new at savvis.net cc: Bluetooth Subject: Re: The Bluetooth over Ambicom BT2000 adapter thing... X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2005 18:37:09 -0000 Martes, > All the necessary info should be contained within the attachment. I > sent is last time, however, it may have been stripped, along the way. unfortunately that is not what i want. you keep sending me those errors but they are not useful at this point. we already know that host can not communicate with the card. that is the reason you see these errors in the first place. > My product info is as follows: > > 0x3e8-0x3ef well, somehow i doubt that. that looks like i/o port range. here is what i'm looking for: i have in my kernel config file the following lines: # NEW CARD device cbb # cardbus (yenta) bridge device pccard device cardbus now i have set sysctl # sysctl hw.cardbus.debug=1 hw.cardbus.debug: 0 -> 1 # sysctl hw.cardbus.cis_debug=1 hw.cardbus.cis_debug: 0 -> 1 # sysctl hw.pccard.debug=1 hw.pccard.debug: 0 -> 1 # sysctl hw.pccard.cis_debug=1 hw.pccard.cis_debug: 0 -> 1 and now i plug my pcmcia card. then i view /var/log/messages and [...] Apr 21 11:31:19 beetle kernel: pccard1: check_cis_quirks Apr 21 11:31:19 beetle kernel: pccard1: CIS version PCCARD 2.0 or 2.1 Apr 21 11:31:19 beetle kernel: pccard1: CIS info: 3Com, Megahertz 589E, TP/BNC LAN PC Card, 005 Apr 21 11:31:19 beetle kernel: pccard1: Manufacturer code 0x101, product 0x589 [...] note the last line it has "Manufacturer code" and "product". that is what i'm looking for. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Apr 21 18:57:37 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 9C48B16A4CE for ; Thu, 21 Apr 2005 18:57:37 +0000 (GMT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C4BA43D2F for ; Thu, 21 Apr 2005 18:57:37 +0000 (GMT) (envelope-from wigglesworth02@comcast.net) Received: from [192.168.1.101] (unknown[128.172.172.195]) by comcast.net (rwcrmhc12) with SMTP id <2005042118573501400mso3se>; Thu, 21 Apr 2005 18:57:36 +0000 From: Martes G Wigglesworth To: Maksim Yevmenkin In-Reply-To: <4267F2C5.7020306@savvis.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> Content-Type: multipart/mixed; boundary="=-QlSj9X5VycZ1oOgc1WX0" Message-Id: <1114109852.670.1.camel@Mobil1.276NET> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 21 Apr 2005 14:57:32 -0400 cc: Bluetooth Subject: Re: The Bluetooth over Ambicom BT2000 adapter thing... 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: Thu, 21 Apr 2005 18:57:37 -0000 --=-QlSj9X5VycZ1oOgc1WX0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Sorry, the original attachment had this information, however, it was quite a bit of other stuff, so here is a 50 line output for the pccard when I connect the adapter. The product id is: pccard1: Manufacturer code 0x22d, product 0x2000 Sorry for the miss understood info. Thanks again, for your help. On Thu, 2005-04-21 at 14:36, Maksim Yevmenkin wrote: > Martes, > > > All the necessary info should be contained within the attachment. I > > sent is last time, however, it may have been stripped, along the way. > > unfortunately that is not what i want. you keep sending me those errors > but they are not useful at this point. we already know that host can not > communicate with the card. that is the reason you see these errors in > the first place. > > > My product info is as follows: > > > > 0x3e8-0x3ef > > well, somehow i doubt that. that looks like i/o port range. here is what > i'm looking for: > > i have in my kernel config file the following lines: > > # NEW CARD > device cbb # cardbus (yenta) bridge > device pccard > device cardbus > > now i have set sysctl > > # sysctl hw.cardbus.debug=1 > hw.cardbus.debug: 0 -> 1 > # sysctl hw.cardbus.cis_debug=1 > hw.cardbus.cis_debug: 0 -> 1 > # sysctl hw.pccard.debug=1 > hw.pccard.debug: 0 -> 1 > # sysctl hw.pccard.cis_debug=1 > hw.pccard.cis_debug: 0 -> 1 > > and now i plug my pcmcia card. then i view /var/log/messages and > > [...] > > Apr 21 11:31:19 beetle kernel: pccard1: check_cis_quirks > Apr 21 11:31:19 beetle kernel: pccard1: CIS version PCCARD 2.0 or 2.1 > Apr 21 11:31:19 beetle kernel: pccard1: CIS info: 3Com, Megahertz 589E, > TP/BNC LAN PC Card, 005 > Apr 21 11:31:19 beetle kernel: pccard1: Manufacturer code 0x101, product > 0x589 > > [...] > > note the last line it has "Manufacturer code" and "product". that is > what i'm looking for. > > thanks, > max --=-QlSj9X5VycZ1oOgc1WX0 Content-Disposition: attachment; filename=dmesgwithsysctl Content-Type: text/plain; name=dmesgwithsysctl; charset=UTF-8 Content-Transfer-Encoding: 7bit Apr 21 14:47:30 Mobil1 kernel: pccard1: chip_socket_enable Apr 21 14:47:30 Mobil1 kernel: pccard1: read_cis Apr 21 14:47:32 Mobil1 kernel: cis mem map 0xe68d3000 (resource: 0xff910000) Apr 21 14:47:32 Mobil1 kernel: pccard1: CIS tuple chain: Apr 21 14:47:32 Mobil1 kernel: CISTPL_DEVICE type=null speed=null Apr 21 14:47:32 Mobil1 kernel: 01 02 00 ff Apr 21 14:47:32 Mobil1 kernel: unhandled CISTPL 1c Apr 21 14:47:32 Mobil1 kernel: 1c 02 02 ff Apr 21 14:47:32 Mobil1 kernel: CISTPL_VERS_1 Apr 21 14:47:32 Mobil1 kernel: 15 2c 07 01 43 6f 6d 70 61 63 74 20 46 6c 61 73 Apr 21 14:47:32 Mobil1 kernel: 68 00 42 6c 75 65 74 6f 6f 74 68 20 43 61 72 64 Apr 21 14:47:32 Mobil1 kernel: 00 00 00 00 00 00 00 00 00 00 00 00 00 ff Apr 21 14:47:32 Mobil1 kernel: CISTPL_MANFID Apr 21 14:47:32 Mobil1 kernel: 20 04 2d 02 00 20 Apr 21 14:47:32 Mobil1 kernel: CISTPL_FUNCID Apr 21 14:47:32 Mobil1 kernel: 21 02 02 00 Apr 21 14:47:32 Mobil1 kernel: CISTPL_FUNCE Apr 21 14:47:32 Mobil1 kernel: 22 04 00 02 0f 7f Apr 21 14:47:32 Mobil1 kernel: CISTPL_CONFIG Apr 21 14:47:32 Mobil1 kernel: 1a 04 00 03 f8 0f Apr 21 14:47:32 Mobil1 kernel: CISTPL_CFTABLE_ENTRY Apr 21 14:47:32 Mobil1 kernel: 1b 15 c1 41 99 77 b5 1e 35 b5 3c 36 36 05 a3 60 Apr 21 14:47:32 Mobil1 kernel: f8 02 07 f0 bc 86 28 Apr 21 14:47:32 Mobil1 kernel: CISTPL_CFTABLE_ENTRY Apr 21 14:47:32 Mobil1 kernel: 1b 07 02 08 a3 60 e8 03 07 Apr 21 14:47:32 Mobil1 kernel: CISTPL_CFTABLE_ENTRY Apr 21 14:47:32 Mobil1 kernel: 1b 07 03 08 a3 60 e8 02 07 Apr 21 14:47:32 Mobil1 kernel: CISTPL_END Apr 21 14:47:32 Mobil1 kernel: ff Apr 21 14:47:32 Mobil1 kernel: cis mem map e68d3000 Apr 21 14:47:32 Mobil1 kernel: CISTPL_LINKTARGET expected, code ff observed Apr 21 14:47:32 Mobil1 kernel: pccard1: check_cis_quirks Apr 21 14:47:32 Mobil1 kernel: pccard1: CIS version PC Card Standard 7.1 Apr 21 14:47:32 Mobil1 kernel: pccard1: CIS info: Compact Flash, Bluetooth Card, , Apr 21 14:47:32 Mobil1 kernel: pccard1: Manufacturer code 0x22d, product 0x2000 Apr 21 14:47:32 Mobil1 kernel: pccard1: function 0: serial port, ccr addr f8 mask f Apr 21 14:47:32 Mobil1 kernel: pccard1: function 0, config table entry 1: I/O card; irq mask 86bc; iomask 3, iospace 2f8-2ff; rdybsy_active io8 irqshare irqpulse irqlevel powerdown audio Apr 21 14:47:32 Mobil1 kernel: pccard1: function 0, config table entry 2: I/O card; irq mask 86bc; iomask 3, iospace 3e8-3ef; rdybsy_active io8 irqshare irqpulse irqlevel powerdown audio Apr 21 14:47:32 Mobil1 kernel: pccard1: function 0, config table entry 3: I/O card; irq mask 86bc; iomask 3, iospace 2e8-2ef; rdybsy_active io8 irqshare irqpulse irqlevel powerdown audio Apr 21 14:47:32 Mobil1 kernel: pccard1: functions scanning Apr 21 14:47:32 Mobil1 kernel: pccard1: Card has 1 functions. pccard_mfc is 0 Apr 21 14:47:32 Mobil1 kernel: pccard1: I/O rid 0 start 2f8 end 2ff Apr 21 14:47:32 Mobil1 kernel: pccard1: Allocation failed for cfe 1 Apr 21 14:47:32 Mobil1 kernel: pccard1: I/O rid 0 start 3e8 end 3ef Apr 21 14:47:32 Mobil1 kernel: pccard1: ccr_res == ff902000-ff9023ff, base=f8 Apr 21 14:47:32 Mobil1 kernel: pccard1: function 0 CCR at 0 offset f8: 42 20 e 0, 2 0 ff 1c, 2 Apr 21 14:47:32 Mobil1 kernel: sio4: at port 0x3e8-0x3ef irq 11 function 0 config 2 on pccard1 Apr 21 14:47:32 Mobil1 kernel: sio4: type 16550A Apr 21 14:47:32 Mobil1 kernel: sio4: unable to activate interrupt in fast mode - using normal mode Apr 21 14:47:32 Mobil1 kernel: pccard1: function 0 CCR at 0 offset f8 mask f: 42 20 e 0, 2 0 ff 1c, 2 --=-QlSj9X5VycZ1oOgc1WX0--