Socket CF Bluetooth Rev 2.5G

[Anonymous]

Sashz, please upgrade the bluez drivers for the Socket CF \"2.5G\".

I\'m finally posting over GPRS-Bluetooth with the damned card. BTW it is very small and fits perfectly in the CF slot. Also needs 40 ma in average.

1st problem
The card rev. 2.5 G is not recognized correctly
I needed to comment out the 3 lines referring to the card in /etc/pcmcia/bluetooth.conf, eject the card, reinsert it and run /etc/pcmcia/bluetooth restart.
At first I tried without installing the  bluez_csr_serial_01 package but apparently it is needed too!

After these steps \"spdmstool browse\" and \"hciconfig\" are giving valid output.

2nd problem
Finally, to connect to my Nokia6310i i needed to edit /etc/bluetooth/rfcomm.conf everytime I reinsert the card... IMhO rfcomm.conf should not get overwritten by ppp dialer!

Now I\'m going to reboot the SL-C860 just to see if my rfcomm.conf get overwritten...and I loose my phone again

[Anonymous]

OK, after reboot my rfcomm.conf is unchanged ... I was doing something wrong before... probably if you start the ppp dialer with bluethoot stopped and it doesn\'t find any card then it fills \"device\" and \"channel\" values with <void>.

Anyway, i forgot to say I\'m using the last Cacko - Qtopia Rom dated 05 March 2004, with \"dynamic\" bluetooth loading.

Previously I got the Socket CF+ 2.5 G card working on 860\'s stock kernel + TKC 2.51 ROM with the bluez-zaurus_2.3-2.4.18d_arm.ipk. Please note the _18d_ version.

[maslovsky]

Now if you could calm down and explain what exactly is needed to make this card work, we\'ll be glad to add support for it to the ROM
What does bluez_csr_serial_01 package package does?  Other then that package - looks like the only problem was extra lines in /etc/pcmcia/bluetooth.conf, correct?

[tumnus]

blurz_csr_serial is a hack that replaces /etc/pcmcia/serial to setup the CSR based uart BT cards and runs hciattach and loads hci_uart at the right point.

I tried putting the setserial stuff in /etc/pcmcia/bluetooth and then run hciattach and load hci_uart there instead. That\'s in version E of the BlueZ packages but doesn\'t work for some reason and I don\'t have a CSR card to debug it with.

[Anonymous]

Tumnus is right. The Bluez \"E\" are not working either with the stock kernel nor with the preemptive one from toshiro.

Also, I never got the card functional after suspend/resume...
The issue is pointed out here in the ZUG in the Bluetooth How-To and the suggestion is to install the following scripts:

susp-resume_0.9-3.1.ipk
sudo-0.1.ipk
susp-resume-bluez_0.9.1_arm.ipk

Unfortunately the packages didn\'t solve the problem for me.

For the moment the only solution is to restart pcmcia or bluetooth by hand from the terminal or simply to eject and reinsert the card (for normal users ;-)

Finally, GREAT JOB, thank you all developers !

[Anonymous]

It works for me when after I added \"killall hciattach\" and \"cardctl eject\" to the suspend part of /etc/apm.d/bluetooth. My Zaurus now takes longer to suspend and wake up, but the card works fine most of the time.

Gunnar

[tumnus]

Strange, a \'cardctl eject\' should do a \'killall hciattach\' automatically anyway, and susp-resume-bluez_0.9.1_arm.ipk ensures that the card is always ejected and reinserted on every resume.

[pakman]

Hi,

Yes, this is basically the problem that I was having over on devnet at http://www.zaurususergroup.com/board/index9231.html?showtopic=7490 ://http://www.zaurususergroup.com/boar...showtopic=7490 ://http://www.zaurususergroup.com/boar...showtopic=7490 ://http://www.zaurususergroup.com/boar...showtopic=7490 ://http://www.zaurususergroup.com/boar...showtopic=7490 .

I don\'t have the time to do much detailed investigation at the moment, but I did get as far as convincing myself that /etc/pcmcia/bluetooth is not run when the card is defined in /etc/pcmcia/bluetooth.conf. I put lines like:

Code: [Select]

echo in bluetooth > /var/log/bt.txt
in /etc/pcmcia/bluetooth, but I never found any evidence that /etc/pcmcia/bluetooth was invoked at all.

I\'ve fallen back on using this card without a /etc/pcmcia/bluetooth.conf file, and starting and stopping bluetooth manually.

Regards,
P.

Update: I am using the \"E\" revision of the BlueZ drivers, not the \"D\" revision.

[Anonymous]

Strange, a \'cardctl eject\' should do a \'killall hciattach\' automatically anyway, and susp-resume-bluez_0.9.1_arm.ipk ensures that the card is always ejected and reinserted on every resume.

I experimented a bit more and they are both needed. If I remove one or both, then the card is down after a suspend (and can\'t get up), but the network icon stays in the taskbar. If I then try to eject the card manually I am told that a program is using the card.

With \"killall hciattach\" and \"cardctl eject\" the network icon disappears after a suspend (it comes back if I start Opera or the network settings applet), but bluetooth still works.

Is cardctl really supposed to know which driver program to kill?


Gunnar

[Anonymous]

Strange, a \'cardctl eject\' should do a \'killall hciattach\' automatically anyway, and susp-resume-bluez_0.9.1_arm.ipk ensures that the card is always ejected and reinserted on every resume.

I forgot to say that I am using the D version of the driver, the E version didn\'t work for me.

Gunnar

[ccrandal]

I get the same problem too with my Socket CF 2.5 card.  I\'m not sure what revision it is, though... can\'t find any model number on the card or in the docs that came with it.

So, are the E drivers not working for everyone?  I\'m also running Cacko Qt ROM 1.20 and `sdptool browse` prompt returns \"Inqury failed\" and `hciconfig` does nothing.

I\'ll try messing with the config files tomorrow.  I wish there was a GUI in the network app for discovering and pair BT devices... perhaps I\'ll have to write one.

Also, I noticed the Bluetooth How-To is either not accurate or the Cacko ROM is different than the ROM that one was written to.  I went to setup a Dialup - IrDA connection, but that wasn\'t listed in the drop down.  I ended up selecting the Dialup - Bluetooth connection... and I did not install the Bluetooth applet whose link was present in the How-To.

Thanks
Curt

[maslovsky]

I went to setup a Dialup - IrDA connection, but that wasn\'t listed in the drop down

To setup IRDA connection you need to select Dialup-PPP and then select IRDA-PPP.

[grey_moon]

The program locking the card seems to be related to bluetooth. if i do a /etc/rc.d/init.d/bluetooth stop i can then eject the card

[ccrandal]

Can anyone tell me where the bluez_csr_serial_01 package is available.  I could not find anything on the Bluez site nor did a Google search yield any response.

I did uncomment the 3 lines associated with the Socket CF Bluetooth Rev 2.5 card, ejected and reinserted the card, and then restarted the /etc/pcmcia/bluetooth command.  That gave me the following error:

Starting Bluetooth... Note: /etc/modules.conf is more recent than /lib/modules/2.4.18-rmk7-pxa3-embedix/modules.dep
Note: /etc/modules.conf is more recent than /lib/modules/2.4.18-rmk7-pxa3-embedix/modules.dep
Can\'t get port settings: input/output error
Can\'t initialize device: input/output error
parse error line 3
Done.

[ccrandal]

I also noticed that Socket Communications has a link to killfilez.de for the Socket card.  It\'s for the Affix Bluetooth protocol stack.  Strange thing is, when you go to that page it specifically says it no longer works with new Socket cards.

Curt