Cacko 1.21 breaks Bluez

[jag]

I found issues with using Bluetooth on my PDA running Cacko 1.21b (SL860).

Reverting back to the initial Rom (Purchased from Shirtpocket.co.uk), got the driver working again.  Any thoughts?

/etc/rc.d/init.d/pcmcia stop was showing a stack trace/dumo in dmesg.

hciconfig was showing a card with mac address of 00:00:00:00:00:00.

Re-flashing to the original Rom appears to have fixed this.

I'm now trying Cacko 1.20, will let you know how that worls.

 

[jag]

Similar problem with Cacko 1.20, though I don't get a stack dump when I restart pcmcia,  Off to try Cacko 1.18

[jag]

And Cacko 1.18 doesn't support the 860, coming up with an error about Invalid device or similar error.

[jag]

Invalid model.

That's the error I get with Cacko 1.18.

So it looks like I'm stuck with the original Rom that came with the Zaurus, Yeuch.  It doesn't even have bash on there..

Oh well.

[jag]

Just tried OpenZaurus, that turned out to be a bit of a pain too, It hangs when I plug the USB cable into my Linux system and the fonts on the included terminal program are almost unuseable.  I knew there was a reason why I opted out of OpenZaurus last time I tried it..

The bluemonkey card llights do liight up though hciconfig reports and error.  However, based on the other problems, I'm going on to give pdaXrom a quick try, I had tried it before and I remember giving up on that initially because of the font size issues.

[jag]

Update: I've had to go back to the original rom, Have tried Cacko again and tried different version of the bluez ipks, no luck.  Real shame.

[zbones]

what exactly is your problem with the cacko rom and your bluetooth card?
1.21b works fine with my bluemonkey card with just a very minor amendment to stop it  from hanging on eject.

Peter?

[petesouthan]

Hi,
I had a similar problem with a Shirtpocket "Blue Monkey" card with an 860 and cacko 1.21b.
My card was actually, as I found out a; "CC&C BT-0101M" card. Shirtpocket were really helpful when I contacted them, but I still couldn't manage to get the card to function.
I gave up in the end and got a good old socket card, it worked straight away.
Have a look on: www.ccandc.com.tw/product/BT-0101M
It may help you.
I am only a Linux novice I'm afraid my patience is not to good!!
good luck!

[Zuber]

We got our "Blue Monkey" cards from expansys. Problem is, they soon became the same as CC&C cards.

Apparently, Expansys own the BlueMonkey name and so they decide what a BlueMonkey card is

I assume they had a big batch of the "old style" BlueMonkey cards which has now expired and now sell these ones under that brand.

New ones are much nicer to be honest. Plastic end on old one tends to come off too easily and these are a liitle more descrete/in tune with Zaurus appearance...

Problem with Cacko rom is if drifts off from the standard bluez driver install. Has some nice touchs (GUI autodetect MAC), but makes things complicated in terms of getting standard solutions working.

Not got time at the moment (struggling with Sony U50/U70 English install), but since it is basically bluez, I'm sure it must just be a question of finding the right bit to edit.

Do the newer Socket "G" cards work no hitch under Cacko Sharp ROM ?

Since they require installation of the same serial file under standard roms.
Would assume it would be a case of locating the same file under Cacko and puttin in the entry there...

[henley_regatta]

Wierd! I got my not-really-a-Bluemonkey card from Shirtpocket last week, and got it working the same night.

I'm using Cacko 1.21b myself, and the inbuilt Bluez stack seems to work, with one caveat: I did have to load the bluez-csr-serial ipk from the package set on the Shirtpocket site:
http://www.shirtpocket.co.uk/spforum/index.php?showtopic=30

Although I mostly followed the instructions from that site, I started from the point after loading the bluez modules (since they're already loaded). I specifically did not reload pcmcia or reboot.

I note that after inserting the card, I have the modules bluez, hci_uart and rfcomm loaded. This got me to the point where I could run hciconfig and verify that the magic incantation UP appears in the output; note that I am still subject to the only-works-if-no-suspend used.

I did alter /etc/bluetooth/uart as specified to add the line:

Code: [Select]

"Bluetooth BT0100M", "", "":/dev/ttyS3 bcsp

[Zuber]

Thanks for the feedback.

Yes Cacko already has Bluez stuff installed (though a little differently).

But having seen posts saying they had socket card working, thought they might already have serial file installed as well perhaps to different location.

Hence the question about anyone got Socket G working.

Good to know the instructions make some sense  

jag,

Just to confirm, you did not install all the bluez drivers did you ?

If so, then it looks like you have a solution (don't).

[henley_regatta]

Thanks for the feedback.
[snip]
Good to know the instructions make some sense   


jag,

Just to confirm, you did not install all the bluez drivers did you ?

If so, then it looks like you have a solution (don't).

Zuber,

Well, thank you for providing the instructions in the first place!  

Let me confirm:

I did NOT install any package EXCEPT the bluez-csr-serial package. This only provides a replacement /etc/pcmcia/serial script. Cacko 1.21b provides all of the driver modules and most of the script infrastructure needed as part of the base.


jag,

I got my starter on this from a post by maslovsky (Cacko creator) himself in this thread

If you have installed additional bluez drivers, note that removing them might cause problems too (since they're part of the base in the read-only filesystem, but the config files are in the read-write jffs2 filesystem).

[jag]

Ahh.. Perfect, I'be finally come back to Cacko and am happy, I see that hciconfig does indeed pick up and show my bluetooth card.

So, the secret it to keep away from the main bluez package but DO install the csr one.

Thanks a bundle.  

(I've also clicked on the 'Track this discussion' link for this discussion.. now)