Socket CF Bluetooth Rev 2.5G

[ant]

ccrandal,

you are almost there... now:

pull out the card,
#su
#cardctl resume
insert the card
/etc/pcmcia/bluetooth restart

P.S. Ignore the messages about modules.conf...

but you could also have an error on line 3 of your /etc/bluetooth/rfcomm.conf, check device and channel

[ant]

if you are using the Cacko Rom the stack is restarted with
/etc/pcmcia/bluetooth restart

but if you are on the Sharp ROM + Bluez rev. D it is
/etc/rc.d/init.d/bluetooth restart

[ccrandal]

I think that\'s where the error is coming from.  the device and channel are both \"(null)\".  Is something supposed to be populating these fields?

Other than that, I\'m following the directions exactly.  `sdptool browse` and `hciconfig` aren\'t showing anything useful.

Do I really need that bluez_csr_serial_01 package?  I still have been unable to locate it on the web.

Thanks
Curt

[ccrandal]

Oh, and now my Zaurus will not power down w/o ripping out the battery.  Lovely!

I think it\'s time to give this ROM another flash and if that doesn\'t do it I\'ll move on to another ROM.

Curt

[ant]

ccrandal,

please give it a last try: erase the user-rom and reboot with the clean QT 1.2.
Then you only need to comment out the in/famous 3 lines and install bluez_csr_serial_01. Nothing more.
If you install the suspend/resume fixes your Z will seldom power down.The packages need some more work.

[ccrandal]

Can you tell me where the bluez_csr_serial_01 is?

What I meant by power down is that when I hit the off button, everything freezes.  I think a new install will fix that... unless the suspend/resume ipk is the culprit.

I\'d really like to try a X11 ROM, but I really like Hancom Office.  Much nicer than my DataViz Documents To Go on my Clie.

Thanks
Curt

[ccrandal]

Ah Ha!  I finally stumbled across the bluez_csr_serial_01.ipk on sourceforge.  I\'ll have to try the reflash tonight since I forgot the power cable... but at least I\'m starting to put all the pieces together on this.  Thank you very much for the help.

Curt

[ant]

csr_serial here:

ZUG ] how-to ] other ] bluetooth

then install the two qtopia-dial up and qtopia-pan applets to have it easier...

[ccrandal]

OK, I\'m dumb.  I guess I need new glasses or something.  I\'ve been to that page a dozen times, even printed it off, and never saw those links.  Thanks again.

Curt

[tumnus]

If you install the suspend/resume fixes your Z will seldom power down.The packages need some more work.

The suspend/resume ipks work fine. If they don\'t then you\'ve probably forgot to install something like sudo or the ROM you are using has gone even further away from the Sharp ROM.

[ant]

tumnus,

no way to suspend/resume NORMALLY.

The Cacko QT 1.20 ROM has a preinstalled & customized bluetooth stack but the installation layout is different. See \"/etc/pcmcia/bluetooth\" vs. \"/etc/rc.d/init.d/bluetooth\".

Please note following points:

1-sudo is already installed (another build though, smaller)
2-suspend_resume_0.9.3.1 is preinstalled
3-susp-resume-bluez is installed BUT the script /etc/apm.d/bluetooth is different:

Cacko-QT 1.2:

case \"$1\" in
suspend)
   if [ \"`/usr/sbin/hciconfig`\" != \"\" ]; then
      hcitool dc `hcitool con | awk \'/ACL/ {print $3}\'`
      hciconfig hci0 down
   fi
;;


From susp-resume-bluez:

case \"$1\" in
suspend)
   if [ \"`/usr/sbin/hciconfig`\" != \"\" ]; then
      hcitool dc `hcitool con | grep ACL | sed \'s/^.*([0-9A-F]{2}(:[0-9A-F]{2}){5}).*$/1/\'`
      hciconfig hci0 down
   fi
;;

4- rfcomm.conf is empty at the beginning. That\'s for the pairing problems.

Byez

Ant

[tumnus]

Huh? The two /etc/apm.d/bluetooth scripts do exactly the same thing. I simply removed the dependence on awk from my ipk because the Sharp ROM doesn\'t come with awk.

rfcomm.conf isn\'t empty in the latest BlueZ ipks.

In any case I don\'t see why you cannot suspend \'normally\'. If the Cacko ROM comes with the suspend/resume scripts preinstalled then that\'s nothing to do with the suspend/resume ipks. They work fine with the Sharp ROM and also tkcROM which comes with them preinstalled too.

[ant]

hi tumnus,

I\'m talking about Cacko QT 1.20 distro.

]Huh? The two /etc/apm.d/bluetooth scripts do exactly the same thing. I ]simply removed the dependence on awk from
So it means Cacko\'s ROM has this \"newer\" version of the script.

I don\'t know what for a mixed bluetooth-stack is installed. It\'s newer than Bluez _D but older then _E because /etc/pcmcia/bluetooth.conf contains the 3 \"offending\" lines for the Socket Rev. 2.5.

BTW /etc/bluetooth/uart mentions the Socket card.

[maslovsky]

Cacko QT 1.20 has awk preinstalled, so both suspend/resume scripts will work fine.
The rfcomm.conf file is populated automaticaly when you configure a dialup connection using Network Applet. This file is not needed initialy, the bluetooth stack will initialise even wihout it.

The only difference between the two stacks seems to be the handling of Socket 2.5 cards. I wish I had one to test before releasing the ROM...

[ccrandal]

OK, I\'m still stuck.  Here\'s what I\'ve done so far:

1.) Reloaded the Cacko Qt 1.20 ROM
2.) Installed bluez_csr_serial_01.ipk, qtopia-bluetoothnetworkapplet.ipk, qtopia-pannetworkapplet.ipk
3.) Opened Qkonsole and su\'d to root
4.) Edited /etc/pcmcia/bluetooth.conf to comment out the 3 offending lines related to the Socket CF rev2.5 card
5.) Ejected the Socket CF card
6.) Executed `cardctl resume`
7.) Reinserted the Socket CF card
8.) Executed `/etc/pcmcia/bluetooth restart`

I now get the errors:
Can\'t get port settings: Input/output error
Can\'t initialize device: Input/output error

I checked /etc/bluetooth/rfcomm.conf and it is empty (no channel, no device).  When I insert the card, though, the card applet correctly identifies the card, though.

I did not install the susp-resume, sudo, and susp-resume-bluez packages as the last time I did that, I could not turn my Z off.  I\'d rather try getting bluetooth working before introducing another potential problem.

Thanks,
Curt