OESF Portables Forum
Everything Else => General Support and Discussion => Zaurus General Forums => Archived Forums => Accessories => Topic started by: piggity on April 05, 2004, 09:31:48 pm
-
Haven\'t seem much talk around here about the Socket Bluetooth 2.5G card. Has anyone gotten it to work in the Zaurus?
-
Works like a charm with the Sharp or tkcROM and the packages mentioned in this howto:
http://www.zaurususergroup.com/modules.php...ename=Bluetooth (http://www.zaurususergroup.com/modules.php?op=modload&name=phpWiki&file=index&pagename=Bluetooth)
If you follow that howto, it should work perfectly. I have it working with the tkcROM 2.0-alpha3 now.
-
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 (https://www.oesf.org/forums/index.php?showtopic=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?
-
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.
-
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.
-
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
-
# /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.
-
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?
-
n8a,
I tried what you said and are still having the same issue.
-
Tumnus,
Just wondering, did you ever get the other Ambicom bluetooth card to work? (the cheap one with the translucent purple top?)
-
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.
-
Hi piggity,
in order to provide more help, can you please post the contents of your /var/log/messages while inserting the card.
-
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?
-
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).
-
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?
-
It should start logging on the next startup.
(shutdown -r now, or \"Reboot\" in QTopia)
-
i tried to restart and its still not creating a log. Any other ideas on how to make sure this is being run?
-
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.
Cool! Thanks for the update. It\'s hard to justify spending $90+ for the socket card, when I was able to buy the Ambicom for $30 at CompUSA.
-
It\'s hard to justify spending $90+ for the socket card, when I was able to buy the Ambicom for $30 at CompUSA.
You can buy the \"other\" Ambicom, which works with the bt950_cs module, for about $50 at Amazon. (I\'m after the Socket card just b/c it doesn\'t dangle out of the CF slot...)
-
i tried to restart and its still not creating a log. Any other ideas on how to make sure this is being run?
1.) Did you \"reboot,\" as opposed to \"restart qtopia\"? The rc.d scripts only get run at startup (or when you change runlevel).
2.) Try /etc/rc.d/init.d/syslog start (as root).
3.) Does ls /var/log/message* return anything? The syslog script (on my SL-5600) eventually archives eight levels of messages as var/log/messages.#
4.) Try ps ax | grep syslog (It should find--in addition to itself--a running syslogd.)
-
You also have to edit /etc/syslog.conf to get the system log going. You need to remove the \'#\' from the start of the line that also contains \'*.info;main.none....\' then reboot. But remember to disable all this afterwards as it will fill internal storage.
Can you confirm whether your Socket card is working on another computer? It could just be broken.
-
Etheral and Tumnus,
I will try this later today. But yes I can use the socket card on a pocket PC. But I will retry to make sure something hasn\'t changed since I started to try to get it to work on the Z. Thanks alot for your help and I\'ll be back.
-
ok, here is the info from /var/log/messages when i insert the card. any ideas?
Apr 8 23:20:04 localhost cardmgr[173]: initializing socket 0
Apr 8 23:20:04 localhost cardmgr[173]: socket 0: Socket Bluetooth CF Card
Apr 8 23:20:04 localhost cardmgr[173]: executing: \'modprobe bm3_bcsp_cs\'
Apr 8 23:20:04 localhost cardmgr[173]: + modprobe: Can\'t locate module bm3_bcsp_cs
Apr 8 23:20:04 localhost cardmgr[173]: modprobe exited with status 255
Apr 8 23:20:04 localhost cardmgr[173]: module /lib/modules/2.4.18-rmk7-pxa3-embedix/pcmcia/bm3_bcsp_cs.o not available
Apr 8 23:20:05 localhost cardmgr[173]: get dev info on socket 0 failed: Resource temporarily unavailable
-
Looks like they\'ve messed up the serial CF support to me, but I guess the missing module could be compiled once Sharp release the 6000 kernel source or maybe it could work compiled against the 5600 kernel.
-
I\'m having the same issue with my new SL-6000, but here\'s another clue: it seems to be trying
to load a module called: /lib/modules/2.4.18-rmk7-pxa3-embedix/pcmcia/bm3_bcsp_cs.o
This file doesn\'t exist, BUT
1. The compatibility list says this is the wrong driver for the Socket BT card anyway - it should be
using hci_uart driver.
2. The hci_uart driver is on the system, but not in the /lib/modules directory
Does anyone know how to get things to point to the hci_uart driver? I tried to edit /etc/pcmcia/bluetooth.conf, but the changes were\'nt recognized.
-
Try the following:
grep bm3_bcsp_cs /etc/pcmcia/*.conf
grep bm3_bcsp_cs /lib/modules/2.4.18-rmk7-pxa3-embedix/modules.dep
And see if you catch anything. This driver is probably for bluetooth 6000 model.
-albertr
-
There were references in /etc/pcmcia/bm3.conf, but nothing in /lib/modules/.../modules.dep
I think I\'m getting the hci_uart driver now though, here\'s /var/log/mesages:
Apr 15 localhost cardmgr[6072]: socket 0: Socket Bluetooth CF Card
Apr 15 localhost cardmgr[6072]: executing: \'modprobe hci_uart\'
Apr 15 localhost cardmgr[6072]: get dev info on socket 0 failed: Resource temporarily unavailable
But \"hciconfig\" returns nothing and \"spdtool browse\" returns:
Inquiring ...
Inquiry failed
If I type: \"hciattach /dev/ttyS0 bcsp 230400\"
It sits there for a few seconds then prints:
BCSP initialization timed out
If the output to \"cardctl status\" says:
Socket 0:
3.3V 16-bit PC Card
function 0: [ready]
mean that the card is at /dev/ttyS0?
-
The card is probably still at /dev/ttyS3. It looks like the currently compiled BlueZ modules are not compatible with the 6000 kernel even though they load ok. That bm3_bcsp_cs.o kernel module may just be trying to be loaded automatically as part of the serial initialisation, which may or may not have anything to do with the problem. Until Sharp releases the kernel source, there may be nothing that we can do.
-
It looks like the currently compiled BlueZ modules are not compatible with the 6000 kernel even though they load ok. Until Sharp releases the kernel source, there may be nothing that we can do.
tumnus,
What if one flashed the special kernel (v1.3, no cache workaround) onto a SL-6KL? It\'s basically a 2.4.18 kernel for a PXA 255, no? (Of course, if there are no modules available/compilable for Prism 3 support with this kernel, it just trades one problem for another...) Since we know the bluez drivers work with the special kernel, this should solve the problem of module compatibility (and we\'d have a known, published source...)
-
The 5600 kernel most probably will not work on the 6000 and I wouldn\'t advise trying it.
Although piggity seems to have got his card working as he posted in the other Socket Rev G thread. Don\'t know what\'s going on here then.
-
piggity seems to have got his card working as he posted in the other Socket Rev G thread. Don\'t know what\'s going on here then.
I found the other thread, but I think piggity is referring to getting it working with his C860, not the 6000 he refers to in this thread.
Piggity, can you clarify?
-
Yes I sent back the 6000 and got the 860. I can get it to work on the 860, but was never able to on the 6000.
-
Yes I sent back the 6000 and got the 860. I can get it to work on the 860, but was never able to on the 6000.
Hmmm...bad news for me. I was just about to give in and get a 6000L with BT card as an acceptable substitute for the 6000W. However, filling up the CF slot (not really sure what other good use I\'d make of it) is one thing, but having a non-Socket BT card wagging its tongue out the top of my $700 Z is another...
-
The 5600 kernel most probably will not work on the 6000 and I wouldn\'t advise trying it.
At the risk of sounding ignorant (when it comes to Linux, I often am), but why not? Are such things as memory size or screen resolution (which seem to be the primary HW differences between 5600 and 6000) \"hard-coded\" into the kernel at compile time? If not, why wouldn\'t the kernel work, if all the other machine specific things (such as config files) are outside the kernel, and should(?) remain unchanged after a kernel flash?
-
Are such things as memory size or screen resolution (which seem to be the primary HW differences between 5600 and 6000) \"hard-coded\" into the kernel at compile time?
Yes.
-
Does having the kernel source bring the Socket G any closer to working with the 6K? (https://www.oesf.org/forums/index.php?showtopic=3455&postdays=0&postorder=asc&start=0)
-
Tumnus,
So does having the kernel source bring us any closer to figuring what wrong with the Socket Bluetooth 2.5G card for the SL-6000? If there is anything else I can try please let me know.
Thanks
Piggity
-
I honestly haven\'t had a look at it as yet. Not had the time. I also don\'t know if the US 6000L is using the same kernel source/config.