![]() ![]() |
Nov 6 2005, 10:53 AM
Post
#1
|
|
|
Group: Members Posts: 70 Joined: 12-September 04 From: COSTA RICA Member No.: 4,565 |
Could anyone tell me if the new drivers on BT have compatibility for my Ambicom BT2000-CF? Dont know if the S/N or MAC address would be helpful in determining this.
I got it late last year and was not supported, as the Ambicom supported was the "black label" card. I got it from Amazon and after a month with Customer Support in Ambicom I got: 1. The card was not the old one that worked with Zaurus, but was not compatible also with windows, it only worked for Pocket PC. Ambicom CS told me that the W2K driver was unstable and therefore they were not posting it at that time 2. Got an RMA to exchange the card for the old one: went back, got lost, never heard of it, reapeared, resent, took out of package...... they re-send me the exact same card, with past emails print-outs and everything. 3. Result: Ambicom card sits in my drawer hoping for better times, when the software catches up with the hardware. Any help welcomed Otto |
|
|
|
Nov 6 2005, 12:31 PM
Post
#2
|
|
![]() Group: Members Posts: 1,376 Joined: 11-January 04 From: Poznań, Poland Member No.: 1,413 |
show 'cardctl info' output
|
|
|
|
Nov 6 2005, 12:55 PM
Post
#3
|
|
|
Group: Members Posts: 70 Joined: 12-September 04 From: COSTA RICA Member No.: 4,565 |
QUOTE(Hrw @ Nov 6 2005, 08:31 PM) Thanks for the help: Open Terminal, typed "cardctl info" R/ message stating unrecognized syntax, it states: Usage: cardctl command [socket #] or cardctl [-c configpath] [-f scheme] commands: status config ident suspend resume reset eject insert Output of cardctl status: R/ 3.3v 16bit PC Card [suspended] Output of cardctl ident: R/ product info: "Ambicom_BT2000C", Bluetooth_PC/CF_Card" manfid: 0x0279, 0x95 0b function: 2 (serial) Output of cardctl config R/ Vcc: 0.0v Vpp1: 0.0v Vpp2:0.0v Hope this helps... |
|
|
|
Nov 7 2005, 12:17 AM
Post
#4
|
|
![]() Group: Members Posts: 1,376 Joined: 11-January 04 From: Poznań, Poland Member No.: 1,413 |
That card use serial_cs driver - look in dmesg which serial port it create and hciattach to it.
|
|
|
|
Jul 16 2007, 03:54 PM
Post
#5
|
|
![]() Group: Members Posts: 803 Joined: 30-March 04 From: California Member No.: 2,368 |
Did anyone ever get this working on the zaurus? I don't seem to have a serial_cs driver in my bluez stuff on my zaurus.
|
|
|
|
Jul 17 2007, 11:57 PM
Post
#6
|
|
![]() Group: Members Posts: 803 Joined: 30-March 04 From: California Member No.: 2,368 |
When I plug it in dmesg reports:
CODE ttyS03 at port 0xf60002f8 (irq = 135) is a 16C950/954 BlueZ Core ver 2.4 Copyright (C) 2000,2001 Qualcomm Inc Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com> BlueZ L2CAP ver 2.3 Copyright (C) 2000,2001 Qualcomm Inc Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com> BlueZ RFCOMM ver 1.1 Copyright (C) 2002 Maxim Krasnyansky <maxk@qualcomm.com> Copyright (C) 2002 Marcel Holtmann <marcel@holtmann.org> bash-2.05# It is very interesting that I get "ttyS03 at port 0xf60002f8 (irq = 135) is a 16C950/954" . Does that mean something is working? I have no idea how to use it though, nor do I have any hci devices from the card. How can it have a serial device? Does bluetooth work that way? I bought this dang card off ebay and the auction specificly stated that it was zaurus compatible. I guess they lied. |
|
|
|
![]() ![]() |
|
Lo-Fi Version | Time is now: 21st May 2013 - 10:10 PM |