![]() ![]() |
Apr 5 2004, 05:31 PM
Post
#1
|
|
|
Group: Members Posts: 28 Joined: 5-April 04 Member No.: 2,683 |
Haven't seem much talk around here about the Socket Bluetooth 2.5G card. Has anyone gotten it to work in the Zaurus?
|
|
|
|
Apr 5 2004, 05:52 PM
Post
#2
|
|
|
Group: Members Posts: 235 Joined: 5-January 04 From: Chicago, Illinois Member No.: 1,359 |
Works like a charm with the Sharp or tkcROM and the packages mentioned in this howto:
http://www.zaurususergroup.com/modules.php...ename=Bluetooth If you follow that howto, it should work perfectly. I have it working with the tkcROM 2.0-alpha3 now. |
|
|
|
Apr 5 2004, 06:24 PM
Post
#3
|
|
|
Group: Members Posts: 28 Joined: 5-April 04 Member No.: 2,683 |
Thanks for the quick responce. I did try using the how to you referenced, but its not working. I am having many of the same issue referenced in ( http://www.zaurususergroup.com/index.php?n...iewtopic&t=1053 ). I was able to get an Ambicom card working without issues using the how to you posted, but when I use the socket card I get the follwing error.
# /etc/rc.d/init.d/bluetooth restart Shutting down Bluetooth... Done. Starting Bluetooth... Can't get port settings: input/output error Can't initialized device: Input/output error Done. Any Ideas? |
|
|
|
Apr 5 2004, 11:16 PM
Post
#4
|
|
|
Group: Members Posts: 1,176 Joined: 3-October 03 From: UK Member No.: 547 |
Which Z do you have and which ROM are you using? Did you install the bluez-csr-serial ipk? Which version of the BlueZ packages did you install? You need v2.3-2.4.18d as pointed to in the howto.
|
|
|
|
Apr 6 2004, 04:34 AM
Post
#5
|
|
|
Group: Members Posts: 28 Joined: 5-April 04 Member No.: 2,683 |
I have the SL-6000L with the stock ROM. The Kernel is 2.4.18-rmk7-pxa3-embedix. ROM version 1.12. I installed:
bluez-zaurus_2.3-2.4.18d_arm.ipk bluez-csr-serial_0.1_arm.ipk susp-resume_0.9-3.1.ipk sudo-0.1.ipk susp-resume-bluez_0.9.1_arm.ipk And the Dial up applet. I tried installing with and without the resume part. I followed the instuctions reference here with no luck. The Ambicom card works fine everytime, but the Socket doesn't. I have tried serveral things listed in these forums, but I keep getting the input/output error. And direction would be greatly appreciated. |
|
|
|
Apr 6 2004, 05:47 AM
Post
#6
|
|
|
Group: Members Posts: 1,176 Joined: 3-October 03 From: UK Member No.: 547 |
They could have changed the (PCMCIA) serial subsystem on the SL6000. The Socket card works fine on 5x00 and Cxxx models, but it requires a bit of hacking with a PCMCIA script which is what the bluez-csr-serial ipk does.
The Socket Rev G card is connected differently than the Ambicom BT2000E card. It must be initialised as a serial CF card and then the hci_uart module must be loaded and hciattach run with the correct parameters. What is the output of the command 'cardctl ident' with the Socket card in your Z? What do you get when you run the following commands as root: modprobe hci_uart hciattach /dev/ttyS3 bcsp 230400 hciconfig hci0 up |
|
|
|
Apr 6 2004, 09:18 AM
Post
#7
|
|
|
Group: Members Posts: 235 Joined: 5-January 04 From: Chicago, Illinois Member No.: 1,359 |
QUOTE # /etc/rc.d/init.d/bluetooth restart Shutting down Bluetooth... Done. Starting Bluetooth... Can't get port settings: input/output error Can't initialized device: Input/output error Done. First, I would suggest installing the bluez-zaurus package, then the csr-serial package. Then, restart pcmcia (for good measure at least), do a cardctl insert, restart bluetooth, and see if you still get that message. Also, I would try hciconfig despite that message to see if it's working. I've found that sometimes I will get that message but bluetooth will still work. For the record, I've never been able to get the command #hciattach /dev/ttyS3 bcsp 240300 (or whatever) to work correctly - it always gives me a time out error. Nevertheless, bluetooth works great for me with the files on the howto page. In short, as long as hciconfig returns the correct results and sdptool browse finds your phone, I would bet that they can connect and you should be able to get them to communicate successfully. But, I don't know the differences between your 5600 + rom and my 5500 and tkcROM. |
|
|
|
Apr 6 2004, 02:56 PM
Post
#8
|
|
|
Group: Members Posts: 28 Joined: 5-April 04 Member No.: 2,683 |
tumnus,
Here is what I get. #cardctl ident Socket 0: product info:"Socket", "CF+ Personal Network Crd Rev 2.5" manfid: 0x0104, 0x0096 function: 2 (serial) Socket 1: no product info available #modprobe hci_uart #hciattach /dev/ttyS3 bcsp 230400 Can't get port settings Input/output error Can't initialize device: Input/output error #hciconfig hci0 up Can't get device info: No Such Device Thanks for you help. Any other suggestions? |
|
|
|
Apr 6 2004, 02:59 PM
Post
#9
|
|
|
Group: Members Posts: 28 Joined: 5-April 04 Member No.: 2,683 |
n8a,
I tried what you said and are still having the same issue. |
|
|
|
Apr 6 2004, 04:34 PM
Post
#10
|
|
|
Group: Members Posts: 696 Joined: 17-January 04 Member No.: 1,468 |
Tumnus,
Just wondering, did you ever get the other Ambicom bluetooth card to work? (the cheap one with the translucent purple top?) |
|
|
|
Apr 6 2004, 11:26 PM
Post
#11
|
|
|
Group: Members Posts: 1,176 Joined: 3-October 03 From: UK Member No.: 547 |
piggity, I'm wondering whether they changed the device that points to a serial CF card. Does hciattach return immediately or does it take a few seconds to show the error messages? You could try a few different devices (e.g. /dev/ttyS2, /dev/ttyS4, etc)
DrWowe, still working on it. I've got a contact at Ambicom now who has given me a few technical details. I just need to learn about UART stuff now and will start hacking hciattach. The hci_uart driver should be able to drive the card then. |
|
|
|
Apr 7 2004, 01:06 AM
Post
#12
|
|
|
Group: Members Posts: 385 Joined: 3-December 03 Member No.: 1,038 |
Hi piggity,
in order to provide more help, can you please post the contents of your /var/log/messages while inserting the card. |
|
|
|
Apr 7 2004, 03:12 PM
Post
#13
|
|
|
Group: Members Posts: 28 Joined: 5-April 04 Member No.: 2,683 |
Tumnus,
The I tried ttyS1, S2, S3, S4, S5. S1 returned BCSP initialization timed out (but i'm not sure what S1 is really for) The rest returned the same as my ealier post and are almost immediante. zmiq2, I don't have the file /var/log/messges Is there anything I need to do so it will be created? |
|
|
|
Apr 7 2004, 03:42 PM
Post
#14
|
|
|
Group: Members Posts: 236 Joined: 17-February 04 From: Gainesville, FL Member No.: 1,914 |
QUOTE I don't have the file /var/log/messges Is there anything I need to do so it will be created? In /etc/rc.d/rc5.d, rename _S02syslog to S02syslog to enable logging (assuming 5 is default runlevel, as it is on my 5600). |
|
|
|
Apr 7 2004, 04:26 PM
Post
#15
|
|
|
Group: Members Posts: 28 Joined: 5-April 04 Member No.: 2,683 |
Thanks Ethereal
But I did this and it didn't seem to make a difference. I also renamed the one in rc3.d and rc4.d and same results. I tried to restart or actually run it and neither seemed to help. Is there something else I need to be doing? |
|
|
|
![]() ![]() |
|
Lo-Fi Version | Time is now: 20th May 2013 - 10:28 AM |