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):

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):

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.

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"

No one tested these ipks yet?

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

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.

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.

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.

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

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

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...

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...

Tumnus,

You are the man

I've been tearing my hair out trying to get PAN to work with my C860. Finally came to the conclusion that the bnep module must be the problem (seemed to be no communication between UDP/TCP and L2CAP). Thinking I'm out of luck, I did a search and here you are with an instant (and very new) solution ! Many Thanks.

By the way, I can't comment on the new suspend/resume - the old one worked fine for me.

By the way(2), any idea how to auto set the IP when bnep port becomes available on connection ? All the searches I've done come up with a recommendation which doesn't work.

(C-860 Standard ROM, BlueMonkey (LSE039), PANning to XP with D-Link DBT-120)

Using BT2000E on 6000L.
Downloaded the driver and changed th (_) to (-) where required.
I got the driver installed and confirmed with hciconfig.

Then I began the connecting to bluetooth enabled phone. Nokia 3660. It's bluetooth and Irda enabled.

The link to 'Bluetooth Dialup Applet' was broken so I went to the next suggestion ' Instead create a dialup connection with the Bluetooth entry in the Network application and set the rfcomm device to /dev/rfcomm0'

I can't find 'Bluetooth entry in the network application"

When I go to /dev I get a window that says 'can't show /dev directory'.

I have an Irda connection to my phone I use it for transferring files. I use the bluetooth connection to talk to another bluetooth cell phone. But I can't talk to my Zaurus.

I've corrected the applet links in the Bluetooth howto.

But as for not using the applets, if you read the howto carefully, you create an IrDA network connection and then hack the PPP script to make it use the Bluetooth rfcomm device.

I don't know what you were using to get that error message about /dev, but in the terminal, if you type 'ls -l /dev/rfcomm*' it should list all of the rfcomm devices.

Hi, I'm back.

I'm going to try the new drivers soon (I'll probably have time to play over the weekend). I've just been looking over some of the old forum posts about this. For me, the show-stopper is described at http://www.oesf.org/forums/index.php?showt...402&#entry13402 i.e. it is not that the commands don't work when invoked from /etc/pcmcia/bluetooth, but that /etc/pcmcia/bluetooth isn't run at all when the card description is in /etc/pcmcia/bluetooth.conf . The only way around this that I found was to remove the card description from bluetooth.conf, so my Z falls back on /etc/pcmcia/serial. I never managed to find out how to investigate this beyond the obvious/trivial (file permissions, etc.), so if anyone could give me any pointers I would be very grateful.

By the way, just unpacking the IPK and eyeballing your files, I found the following syntax error in /etc/pcmcia/bluetooth:



should be



But I don't think that is the problem from the past - the current version of this file on my Z (which would have been the last one I tried) is syntactially OK

Regards,
P.

In the latest bluetooth.conf, you should see a device entry called "serial_cs". Any card entry bound to "serial_cs" will run the script as defined by the class attribute of the device. So the latest script should in theory run /etc/pcmcia/bluetooth for serial cards after binding the serial driver to it.


Aha! Thanks for spotting that. Don't know how that got in there. Maybe that's why the script wasn't working

I'll post a new ipk with the corrections shortly.

I've corrected the syntax error spotted by pakman and included the hci_usb driver for SL-6000 users with USB dongles. The alpha3 package is now available on the first post in this topic.

No one with a serial based Bluetooth card tried the alpha3 package yet?

I'm in the process. Making the Irda connection a bluetooth connection is my sticking point.

Tumnus,

Thanks for your effort to bring Bluetooth to Zaurus.

I had SL-6000 in stock Sharp ROM and Ambicom (old one) working with the old package. Just got a Socket N CF card lately and try to make it work with the new pacakge but didn;t quite work. The Z went as far as "connecting" (after "initialing modem") but never made the "connected" status. The phone (Siemens S56) also shows they were connecting so I think I am pretty close.

I also misplaced my Ambicom card so I have no way to test if that card will work with the new package. Where should I look to make the Socket card work with the new package?

Thanks

Frank

Ok, it's working now. All I did was eject the Bluetooth card and reinserted again. Work just like before and the card is flush with the Z.

However, the resume is not working. Even tried it one more time and same result. Have to re-insert the card everytime I power the Z off.

Frank

hey tumnus,
Here's another input.
I tried the alpha3 with a Socket revG and the new susp-resume-bluez (0.9.2) on SL-C860.

The alpha3 package seemed fine, but after a suspend I had to eject/insert the card to get it to work again.

Actually, I noticed 2 things when coming back from standby.
1. "hciconfig" would not display any info about the card.
2. cardctl status would show the card as being in "suspend" mode. Issuing a "cardctl resume" changes the status to ready, and both "hcitool dev" and "hciconfig" would now display the card information.
So I added "cardctl resume" inside the apm.d/bluetooth script (outside of "if" statements) and now my card seems to come back up without having to eject it.

I'm not sure what I'm doing, just trying things out. Hope this can make sense to you.

Does the card automatically eject and reappear when you resume? Look at the CF icon on the taskbar when you resume. If nothing happens to it, did you remember to install the susp-resume and sudo packages too?

Hi Tumnus,

Finally got around to trying the new bluez-zaurus packages, and it works! I deinstalled the old bluez-zaurus, susp-resume-bluez and bluez-csr-serial packages (after carefully making copies of all the files involved so I wouldn't lose my hacks - I used 'ipkg files ...' to help with this).

I installed the new bluez-zaurus package, copied my previous /etc/bluetooth/rfcomm.conf and /etc/bluetooth/hcid.conf back, and everything worked! (Pairings were still OK because this procedure doesn't touch /etc/bluetooth/link_key.) The name of the card now correctly appears when inserted or when I tap the eject icon. More importantly, when the Z is suspended, I only have to do a 'cardctl resume', and after a second or two, 'hciconfig' shows that the interface is up again - this is a real advance over the previous state of affairs where the interface stayed obstinately down unless I did '/etc/rc.d/init.d/bluetooth stop' followed by '/etc/rc.d/init.d/bluetooth start' . Unlike sornett, I didn't have to do an eject/insert to get this to work.

I haven't tried the new susp-resume scripts yet, because being paranoid I would rather leave the card suspended and explicitly enable it when I need it My own scripts are pretty trivial now - a one-liner to start using the card, and a couple of lines to shut down any running PAN's before suspending the card when I have finished.

Many thanks to you and Maslovsky for sorting this out,
P.

hello tumnus.
Yes sudo and susp-resume are installed.
With a Socket Rev F card, I observed that the icon disappeared and reappeared.
But with an H/G card, it does not happen.

The script /etc/apm.d/bluetooth has the follwing section



I tried commenting out all the resume lines in that script and issuing the commands manually. That's where I noticed that the hcidonfig command returned nothing, which means that the other commands in the if statement won;t be executed either.
The other thing was that cardctl status showed the card as suspended. resuming the card restored everything: hciconfig ok, hcitool ok etc...
that's why I simply added the cardctl resume statement to the apm.d/bluetooth script, and things are now working fine.
shouldn't the card manager take care of resuming the card ?

sornette, thanks for pinpointing that. maslovsky just told me about that too.

I'll see if I can write some commands on resume that work with all cards. The reason for that if statement on resume was to only run those commands when there is a Bluetooth card inserted or was inserted when your suspended. For the non-serial based cards this seems to work.

Tumnus,

Thanks for the effort!!!

I need some help here. I have a SL-5500 running TKC ROM with cacko latest kernel upgrade, and as I understand, this cacko release already support my Ambicom BT-2000CF (white label), as I have been having some trouble trying ambicom to exchange it for the old one. I only have basic experience with linux (SUSE 8 and 9 who babysits us newbies with the graphical configuration program).

I have not applied your patches as I already have latest Cacko, Card is recognized when plugged in as MAVIN BLUETOOTH CARD. From there on, I have no idea how to get devices paired (my interest is mainly with cell phone ericsson T39m and PC).

I am in the process to get an Aircable device and try to sell this one to an Ipaq owner down here (in Costa Rica).

What do you think? Any hope to make this one work?

Any help appreciated.

Otto Acuña
Servinfor Data Recovery Services
www.recuperacion.net
San Jose, Costa Rica
Central America

I'm afraid the latest Ambicom BT CF card still isn't supported at all. There are no Linux drivers for it.

In any case, instructions for setting up Bluetooth can be found here

I've uploaded a new version of the susp-resume-bluez package that should resume serial based cards like the Socket Rev G card properly. See the Second Post

*sigh* yep, can definitely confirm the ambicom bt2000c CF card isn't working.... *grumble* ... but the ambicom bt2000 usb dongle works fine... though I really look rather over-techied out when I whip out my digital river usb converter, smack the bluetooth dongle on it, slap it into my gigantic sharp zaurus (with the expansion CF pack lol...) ... ohhh boy... batman factor is on an all-time high these days...

I have no problem to use this card on my laptop Toshiba Satellite 1115-S103 with SUSE 9.2.

What does 'cardctl ident' give for your card? The BT2000E card is supported. The BT2000C card is not. The BT2000C card is the later card.

Socket 1:
product info: "AmbiCom BT2000C", "Bluetooth PC/CF Card", "", ""
manfid: 0x022d, 0x2000
function: 2 (serial)

In fact I have both BT2000E (black top) and BT2000C (blue top).
BTW, SUSE 9.2 found the card BT2000C and Belkin Bluetooth USB adapter once!
Just works!

6k, stock rom, adf's fast kernel
Socket BT rev H with stamp "8510-00159H". Did a search with "rev H" in the whole forum. People reported this exact card did work both with Cacko and Pdax rom.

installed


card recongnized fine as: Socket Bluetooth CF Card Rev G+

but stuck at the point with hciconfig giving back

I know these numbers shouldn't be all zero.

tried

same result.

Anybody get hint? TIA

i got it figured out. i'm typing using the bt dialup. my phone LG PM-325 with Sprint PCS Vision.

first of all, I flashed back to the stock 6K kernel. Now hciconfig returns the correct MAC addr dor my bt card

secondly, I have to do a SW update on my LG phone. This updates the phone OS to v18, which specificly says "improves the bluetooth performance". Without this, sdptool browse won't find anyservice and returns time out.

now. with sdptool browse working. the rest is just following up the bt how-to

note: dial up service is actually set as channel 4 in the LG

enabled my bt phone as always visible
and fire up dial-up connection. that't it. I see the 3G RX TX in my LG phone. Thanks Tumnus for the bluz driver.

more updates about suspend-resume

bluez-zaurus_2.13-2.4.18-alpha3_arm.ipk
susp-resume-bluez 0.9.3
sudo 0.1

suspend resume seems still problematic

hciconfig is able to return the correct MAC address for the BT CF card. However, sdptool browse returns : "inquiry failed".
hcitool dev didn't report any device

then tried. /etc/rc.d/init.d/bluetooth restart
shutting down is ok, but
starting Bluetooth ... BCSP initialization timed out

have to do an
cardctl eject/insert or physically reinsert the card to bring the bluetooth back

will those nice drivers work with a c1000 used with a belkin bluetooth cf?

Look here: http://www.oesf.org/index.php?title=Bluetooth_Card_Support

If a card isn't listed here, then at best no one has tried or updated the list and at worst it doesn't work at all.

thanks for your reply and continuous support tumnus. if it werent for helpful ppl like you the zaurus community would be a whole lot different. thanks again, we really owe you a lot of things..

At this webpage I can see that the Billionton card is unsupported while at post #9 I've read that it works...what's the truth then?

That would come under "no one has updated the list"

If Edbo has tried his Billionton card with the packages I created and got it to work then I guess it sort of is supported. It's not working out of the box at the moment though. You have to make the changes Edbo gives.

I am also not sure whether there are several versions of the Billionton card, so I would prefer that someone with a working card updates the list as they can give specific model and ident details. That's why the list is on a Wiki page after all.

- All is well, essentially. So, if I only had a brain. Case closed.

DELETED

can some one confirm that bt2000c is working as stated here http://www.oesf.org/index.php?title=Bluetooth_Card_Support or still a no no?
thanks

Will this stuff work with pdaXrom?

Will this stuff work with a USB Bluetooth adaptor?

Thanks!

Could somebody please do me a favour & comment on the belkin card I've posted about in this thread. I'd like to know if I have the slightlest chance of getting it to work or should I just return it? thks