Rename it to bluez-kernel-2.4.18-mh14_arm.tar.gz and open it with winrar or winzip.There is a bluecard_cs.o in this file. Copy it to your zaurus (lib/modules/2.4.18-rmk7-pxa3-embedix/kernel/drivers/bluetooth) and reboot.

At console use: hciconfig hci0 up"

Installing bluecard_cs.o in the kernel modules means oz now recognises my card.Note this is obviously missing from oz!!

However I still have problems! I do sdptool browse and the z sees my motorola phone mac address - but also says it doesnt have permission to connect to this sdp service ???

Anyway undeterred I enter my phones' mac address into rfcomm.conf.ok I've forgotten what to do next ? (Actually i dont know with oz.!)(I have also set "automatically bind at start up" in rfcomm)

Still cant start bnep0 service in "networks" ....Need some help now please!!

Also I find when I tap on the card manager icon and select "eject lse039 bluetooth card the light on the card goes on and stays on and the z hangs.The only way out is to reboot with the switch at the back. - am I still missing some configuration somewhere???

the cards go up and running. I've just tried to make some "hcitool scan" with other bt peripherals around, just to test, and everything is fine.

But if i try to run:/etc/init.d/bluetooth start

I got this error:Starting Bluetooth subsystem: hcid sdpd Can't open HIDP control socket: No such file or directory hidd rfcomm.

And nothing works.I would like to make at least /etc/init.d/bluetooth start (and stop) to work.Otherwise, being unable to stoppping the service, every time I extract the card I need to reboot the Z to make it work again.

But my device is still unavaiable: "hciconfig -a" gives no outputI've tried to load hci_uart manually (modprobe hci_uart) before running the demon, since that module is required and it's not loaded upon card insertion or by running the bluetooth demon itself.But still no luck. "hciconfig -a" still giving me a blank output.uhm...

The only way I can get a consistent bluetooth connection is if I reboot (flix battery switch to "replace battery then back to normal"When I come up from a reboot I insert my Bluetooth card and it blinks on and off and I run my dial up script from networks ( I have a little script to check the bluecard_cs module is loaded and also runs /etc/init.d/bluetooth start for good measure in the "execute" tab. The phone ask me for the pin number to pair it and the z and I oblige - I am now connected! I can connect and reconnect many times - no problem. Then I suspend the Z and then resume.I start the dial up from networks it runs the script the card light flashes but I just keep getting the message that its trying to initialise the modem. When I look at the phone there's no sign of anything trying to connect to it. I then have to cancel.I can suspend and pull out the card and put it back in again. Lights flash on the card but every time I dial I cant get past the trying to initialisation modem message. Somehow when I suspend the Z something is being altered. I'am pretty sure the bluecard_cs module is loaded ok and bluetooth is being started but it seems something has changed!!It seem that if I want to use bluetooth I have to reboot the z everytime - suggestions anyone!!

I have bluetooth working consistently now - even after a suspend and resume.To do this I have to run a script via the ppp dial up I configured within the networks tab. (The "execute" tab in the ppp dial up account allows you to run a script of your choice.)My script is as follows - call it whatever you like, but make sure you make it executable

First of all I make sure that the bluecard_cs module is properly loaded then I stop and start bluetooth .I found you had to stop bluetooth when you came out of suspend otherwise bluetooth didnt initialise properly and I could get past the modem initialiastion string in the ppp dial up.I added rfcomm bind all and the pand commands just for good measure.Anyway I can now put my bt card in , suspend and resume and make a bluetooth connection to the phone and dial up everytime.I dont use the card manager icon to remove the card if I want to swap in my wifi card later I just yank my bt card out wait until the message saying "ls039 card has been ejected" and plug my wifi card in. I found that if I try and click on the card manger icon to remove the card the light on my bt card comes on and stays on - worse still the Z hangs and I have to reboot!

I'am sure these problems and the usbdo modules not loading properly after a resume are all due to the suspend and resume problem and will go away when this is fixed. I have flashed to the latest zImage which has got rid of the right key press suspend problem but there's obviously still problems with suspend /resume.

I fear my problem is on a most basic level. I'm not trying to setup a connection with a phone by now, but just to have thebluetooth card running smoothly.What I'm asking for, is if it your /etc/init.d/bluetooth script works well without any tweaking, and if it's sufficient by itself to make the bluetooth card up and running.As I said in my previous posts, if I try to run it I get an error, and after tweaking the file I don't get the error anymore, but I'm still unable to use the card properly.But if I use the sequence of 4 commands (setserial, modprobe, hciattach, hciconfig) everything is fine.

So, actually to make the card works you just run the script you posted, that in turns call the /etc/init.d/bluetooth script? No other tweaks?

If this kind of discussion is not of general interest maybe we can move to PM.

The only thing I altered in /etc/initid/bluetoth was that I commented out the references to HIDD which was causing the same sort of error message that you saw appeared on my z when I ran "/etc/init.d/bluetooth start".Once I did that the error message went away.

I then found that when I came out of a suspend and ran "/etc/etc/init.d/bluetooth start" the light on the card flashed but... my dial up script would'nt work.However if I ran "/etc/init.d/bluetooth stop" then "/etc/init.d/bluetooth start" then everything would work just fine.

I've tried modprobeing the bluecard_cs driver in the past but didnt see much happening. I found the rmmod insmod of the driver to do something (at least it told me the bluecard_cs driver was already loaded.) I know your card uses a different driver than mine but it looks like its not being loaded properlyMaybe you should try that approach instead of modprobe. (see script)Sorry I wish I could be more help but I'am not an expert on bluetooth.