New Bluetooth Drivers

[tumnus]

I've finally got around to updating the Bluetooth BlueZ driver ipk.

This is only for Sharp ROMs and variants of Sharp ROMs, excluding Cacko ROMs, that use the 2.4.18 kernel. So for example this includes Sharp ROMs on SL-5500, SL-5600, SL-6000, SL-C850, but NOT SL-3000.

Here's some of the improvements:

• Ambicom BT2000C Support. Thanks to tetron for spotting this had been included in the latest drivers. EDIT: Actually it doesn't look like this is working
• Socket Card Rev G Support without requiring the extra bluez-csr-serial ipk. Thanks to maslovsky for sorting this out
• Hopefully Dlink, Mavin, Billionton, BrainBoxes, and Dell cards should all be supported 'out of the box'
• Should work 'out of the box' on the SL-6000. (It moves /etc/pcmcia.bm3.conf out of the way on installation and back again on removal) Thanks to DrWowe for spotting what was wrong previously
• EDIT: Included hci_usb driver would should allow SL-6000L owners to use USB Bluetooth dongles with the appropriate USB cable.

EDIT: The PAN profile should be working now as I resolved a kernel module problem.

Before installing the new ipk, backup your files under /etc/bluetooth and /etc/pcmcia/peers. Then you can easily restore them after installing the new ipk. (You will need to run '/etc/rc.d/init.d/bluetooth restart' after restoring rfcomm.conf and hcid.conf)

Also uninstall all bluez packages before installing this one, including the bluez-csr-serial, which is no longer required with the new package.

So here is the new ipk (Note: the 1st, 3rd and 4th underscores [_] in the filename need to be changed to dashes [-] after downloading):

[tumnus]

I have also improved the susp-resume-bluez package so that all Bluetooth cards should come back automatically after a suspend resume cycle. This includes Socket Rev G cards.

Remember to install susp-resume and sudo if you haven't already.

Uninstall the old package and try this one instead (Note: change the 1st and 2nd underscores [_] to dashes [-] after downloading):

[tumnus]

Please test the ipks above and let me know whether they work with your Bluetooth card or not.

As stated above, the PAN profile currently isn't working, but DUN should work fine.

[tumnus]

I think I might have made a mistake for the serial based cards. They probably work when bluetooth is started or restarted, but not after a resume or inserting the card.

If this is the case, I think it may be fixed by replacing the following line in /etc/pcmcia/bluetooth.conf

class "serial" module "serial_cs"

with

class "bluetooth" module "serial_cs"

[tumnus]

No one tested these ipks yet?

[Pyrates]

Sorry, I don't have anything bluetooth to test with... Great to hear that someone's doing such cool stuff anyway  Are you using OpenEmbedded, or do you have plans to integrate your work? Would surely be great...

Cheers
Philipp

[tumnus]

I've fixed the unresolved symbols problem in the bnep module, so the PAN profile should now be working. I think I've also corrected the PCMCIA config file so serial cards should always work. The alpha2 ipk can be downloaded from the first post above.

[maslovsky]

Here are some results:

Zaurus 5500, Sharp ROM 3.10

sudo, suspend-resume, suspend-esume-bluez, bluez drivers, qpe-terminal

Ambcom BT2000E, Anycom - work
Socket G, Billionton, Anycom C300 (new rev) - don't work. You should be able to make both cards working - see my PM I've sent you yesterday.

[EdbO]

To get the Billionton Bluetoothcard working you must first set up the serial device with "setserial /dev/ttyS3 baud_base 921600". Then you load the kernelmodule "modprobe hci_uart" and last do "hciattach /dev/ttyS3 bcsp".

When you do "hciconfig -a" you see that the bluetoothcard is working.

Above works for me   Both for the SharpRom (with tumnus packages) and for OZ 3.5.2

[maslovsky]

To get the Billionton Bluetoothcard working you must first set up the serial device with "setserial /dev/ttyS3 baud_base 921600". Then you load the kernelmodule "modprobe hci_uart" and last do "hciattach /dev/ttyS3 bcsp".

When you do "hciconfig -a" you see that the bluetoothcard is working.

Above works for me   Both for the SharpRom (with tumnus packages) and for OZ 3.5.2

Yes, I know - that's what is done automaticaly in Cacko ROM  
I've sent tumnus all nessesary scripts to make it work in his package too.

[tumnus]

I know I need to add some scripting options for the setserial stuff for other cards, but I don't know why the Socket Rev G card is not working as that does not need any special setserial settings.

It's a little hard to debug these things without the card. I'm guessing there is an error or something lacking in my bluetooth pcmcia script somewhere and because of its dependencies I haven't been able to test any of the serial section.

[maslovsky]

I know I need to add some scripting options for the setserial stuff for other cards, but I don't know why the Socket Rev G card is not working as that does not need any special setserial settings.

It's a little hard to debug these things without the card. I'm guessing there is an error or something lacking in my bluetooth pcmcia script somewhere and because of its dependencies I haven't been able to test any of the serial section.

The only way it worked for me is when all scripts are executed from /etc/pcmia/serial, not /etc/pcmcia/bluetooth (like in your serial package). That's how it's done in Cacko ROM

[spectrum]

Hi folks,
I have the SL5000D and cacko rom.  I recently bought the Socket bluetooth CF card and would appreciate any help and pointers to get it going.  If you can just direct me to any posts or how-to's I'd appreciate it.

Thanks,
spectrum

[nexxusone]

I've just installed the drivers on my Zaurus c860 using Cacko 1.21b and a Socket rev F card.
When I go into Network Settings and attempt to add add a modem to my Bluetooth Dial-up connection the script immediately says "No devices with DUN profile found" without scanning. It was able to discover my mobile phone immediately prior to installing the ipkg listed above.

Do you have any idea what I might try to get my phone working again with your updated drivers? I'd love to get these working (and contribute any resulting knowledge), but if that's not possible, will it be possible to "roll back" to my working driver, or will I need to restore a backup?

Thanks.

EDIT: sorry, I just noticed that you said EXCLUDING Cacko roms. I'ma go restore a backup now...

[tumnus]

OK, here's a challenge to anyone with a serial based Bluetooth card (such as the Socket Rev G/H):

 - Get the latest ipk working with your card without hacking any default ROM files (i.e. /etc/pcmcia/serial) or at least tell me why using the same serial commands in /etc/pcmcia/bluetooth won't work

No one has reported whether the new susp-resume-bluez ipk works better either...