Socket 2.5 bluetooth - now working

[DrWowe]

I\'ve found the problem with the bluez drivers.  There is a file /etc/pcmcia/bm3.conf that already contains driver mappings for various bluetooth cards.  This file conflicts with the bluez driver mappings, and to make matters worse, the kernel modules refered to by bm3.conf don\'t seem to exist on the 6000L.

The fix is simple:  Just delete the file, or move it out of the way.

[Ethereal]

1.) So you have the Socket card working in all respects...?  You rock!

2.) On my 5600, although the card is properly initalised and configured, it isn\'t recognised by QTopia--the network icon doesn\'t appear after insertion, only after opening either Network Settings or Opera.  This problem is unique to the Socket card--at least it doesn\'t occur with my Ambicom card.  Does this same peculiarity manifest itself on the SL-6K?

[DrWowe]

1) I can get online through my T608 which is the only respect I really care about.    I haven\'t tried doing anything else yet.  The card currently stops working after a suspend/resume but there are already known fixes for that I think.

2) Because of WiFi, the network icon is available all the time anyway.

[Ethereal]

1) I can get online through my T608 which is the only respect I really care about.    I haven\'t tried doing anything else yet.  The card currently stops working after a suspend/resume but there are already known fixes for that I think.

Yes, if all the \"layers\" required to get ppp going work, anything else (like my BT GPS receiver) will, too.

2) Because of WiFi, the network icon is available all the time anyway.

I guess the more relevant question then would be: is your PCS Vision connection offered as an option when you tap the network icon immediately after inserting the BT card?

[piggity]

Great work DrWowe! this make my 6000 almost perfect.  But Ethereal my network icon does not work if I have a wifi connection setup.  If I don\'t have one it will show the bluetooth connection.  Has anyone been able to get this to work?

[DrWowe]

I followed the instructions on the bluetooth faq here to get it set up, using the IRDA mode and then editing the ppp peers file to use /dev/rfcomm0.  When I click on the network icon, it first gives me a choice between IRDA and Wireless LAN.  I see this choice even if the Bluetooth card is removed.

[piggity]

Ok.  I was using the bluetooth applet, not setting it up as IRDA.  I\'ll give that a try.  Thanks!

[piggity]

Yep that works great.  Thanks again.

[Ethereal]

It\'s a little fidgety (especially since the Network Config application shaves the /dev/rfcomm0 off the file every time it edits it) but that is a great workaround for whatever is preventing the bluetooth interface from being recognised by the Net applet...

DrWowe, you are making my $700 less safe all the time...

[Ethereal]

OK, the Socket 2.5 card does indeed work with /etc/pcmcia/bm3.conf moved aside!  However, tumnus\' elegant suspend/reume package doesn\'t properly re-initialise the card after resuming from suspend.  My best guess (based on manually running the commands from the script) is that something about the special way the card is initialised prevents the card from being ejected (\"ioctl() resource busy\").  Modifying the script to shut down bluetooth before ejecting/inserting the card and then start it again afterwards seems to have fixed the problem.

#!/bin/sh

PATH=$PATH:/usr/bin

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
;;
resume)
   if [ \"`/usr/sbin/hciconfig`\" != \"\" ]; then
      /etc/rc.d/init.d/bluetooth stop
      cardctl eject
      cardctl insert
      /etc/rc.d/init.d/bluetooth start
      rfcomm bind all
   fi
esac

Anyone with a similar problem, or am I the only one to experience this?

[anmol10]

I'm using a Socket Bluetooth CF for the SL-6000. Can someone send me a link to appropriate BlueZ ipkg?

I tried the BlueZ link from Zaurus Software Index, for both combined ipkg and individual ipks for the latest versions of bluez utils, libs and hcidump. However, modprobe cannot locate 'hci_uart' and 'rfcomm'. I assume that after installing the ipkgs I delete the file mentioned above.

Thanks,
-Anmol

[anmol10]

Aha. I found the Bluetooth FAQ on ZUG and got the appropriate ipks. Even after following instructions and moving the file /etc/pcmcia/bm3.conf, when I run,

/etc/rc.d/init.d/bluetooth restart

I get,
...
Starting Bluetooth..Can't get port settings: Input/output error
Can't initialise device.. I / o error

-Anmol
SL6000 out of the box with Socket  Bluetooth CF A / J

[hafken]

Same problem here, with a socket  rev H card --

I have followed the how-to, moved bm3.conf out of the way, and when I try to start up bluetooth I get:


Starting Bluetooth... Can't get port settings: Input/output error
Can't initialize device: Input/output error
Done.


Can anyone help??

Thanks,
Dave

[hafken]

Ok, I got it working! I'm not entirely sure what it is that finally did it (I did lots of tinkering) but I think the key things to get it working were:

(1) starting up the hci_uart module (I'm wondering if this should be added to /etc/rc.d/init.d/bluetooth?)
(2) restarting pcmcia (probably had to due this to clear out the 'busy' states I had created)

then I restarted bluetooth, and everything started to work.

I then struggled to get the connection working with my t-mobile phone, and that took a while too but finally all is well and working.

-dave

[zoaib]

Hi there. I am quite new to linux and trying to make socket bluetooth rev "H" card work with my sl-6000. I am getting the same errors as you were having.

You recommend to start hci_uart module and restart pcmcia. Can you please provide me information how to make these happen as I am complete newbie to linux.

Thanks