Bad first experience

[iamasmith]

Hi,

I installed Cacko 1.21 +Hotfix B at the weekend on my SL-C860 and had a couple of significant problems that caused my probably to unduly doubt the stability of the build. If anyone has any ideas on how to overcome these issues then I would LOVE to try Cacko again - It looks a great ROM and I like having nearly 96Mb user flash.

i. I have a Bluemonkey Bluetooth card with the model number 'LSE039/12 R2B' on the back. It seems to function in every respect quite nicely until I either cardctl eject from a terminal or use the card manager applet to eject the card. The Z then freezes and all I can do is pull the battery, wait a few seconds and try again. - Interestingly enough a 'surprise eject' and suspend/resume seem to work fairly well - I'm wondering if the driver is polling some status from the card which isn't ever responding on this rev. I had the same problem with the Stock kernel and Rev E drivers, downgrading to Rev D worked fine with the stock kernel. Unfortunately the Rev. D drivers don't seem to function with Cacko 1.21b (fail to initialize the card following reboot, hciconfig shows a zero mac address etc.).

ii. I had a couple of surprise suspends, can't say that I noticed a pattern here. Following resume the touch screen seemed to still be active (screen tap sounds coming through), however Qtopia didn't respond to any touch screen actions - again resulting in a remove battery/power cycle.

In the end I restored my previous stock image from a NAND restore.

BTW: my stock ROM image is as close as I would consider to 'bullet proof', none of the above problems, however, as I say I'm on the Rev. D bluetooth drivers.

Any ideas would be greatly appreciated.

Regards,

Andy

[tumnus]

I thought the Bluemonkey eject problem had been fixed in the Cacko ROM?!?!

The exact problem is that the Bluemonkey card needs a second to shutdown after the driver shuts down. If it isn't given this second, it locks up the PCMCIA subsystem, which causes the Z to hang. This was easy to fix in the bluez packages. All I did was add a 'sleep 1' after the 'hciconfig hci0 down' in /etc/pcmcia/bluetooth, however the BlueZ drivers work differently in the Cacko ROM and is why the BlueZ packages do not work with the Cacko ROM after bootup.

If you can find a 'hciconfig hci0 down' in /etc/rc.d/init.d/bluetooth and put a 'sleep 1' on the line after it, that might fix it if that hasn't been done already.

[iamasmith]

Cheers, thanks for the tip.

Do you thing that the suspend/resume thing may just be a glitch triggered by this driver/card combo or is anyone else seeing something similar with different hardware ?

[tumnus]

It's the driver/card combo. There are similar symptons with another card, but that is for different reasons and uses a completly different driver.

[iamasmith]

Well I've got Cacko back on, the /etc/hotplug/bluetooth script has the sleep 1 statement and the thing still hangs when I soft eject my Bluemonkey card.

It would be really great to find an answer to this one, I may be being picky but it's the only thing that spoils the experience of an otherwise great ROM.

I think I'll persist a little longer with this installation though.

[stupkid]

Just to be 100% sure.  You are using the bluez drivers that come with the ROM right, not installing bluez on top of the built-in drivers?

[iamasmith]

Yep, back to the original Cacko ROM drivers.

When I originally tried this and had the problem I overlayed the Rev D Bluez modules from the community.zaurus.com site (non-preemptive) and they worked perfectly including the eject. Until I rebooted the Zaurus and then they stopped initialising the card.

Since then I reflashed Sharp ROM, ran for a couple of days (again this is perfectly stable with the Rev D Bluez modules but has the same problem if I try to use Rev E (from the zaurususergroup download section).

Last night I reinstalled Cacko, haven't 'played' with anything yet. Just put on Hotfix B and a few apps and the Bluez driver behaves as described.

When you hit the Eject option on the card manager applet the applet mostly disappears, leaves a line of pixels on the task bar and the Z hangs.

If I go to the command line, stop all the Bluez services (hcid, slpd etc), wait for a good while and then cardctl eject I get exactly the same thing. BTW LED on the card lights up when this happens and stays lit.

[zbones]

iamasmith,

All you have to do to fix the hang on eject with the bluemonkey card is to edit /etc/pcmcia/bluetooth

change line 59 from

hciconfig $2 down

to

hciconfig hci0 down

and save it.

Peter
(i am a smith too   )

[iamasmith]

Excellent !,

Thanks so much, that's stopped me from 'braining' myself against the wall !

+ I can stop pestering Maslovsky now for the old Bluez source that worked on the stock ROM. - Sorry bud, GREAT ROM - just had to have this fixed.

Peter, I mean it, thanks - just can't leave problems like this alone until they are nailed and it has made my day to get this fixed. - top man !

Now I don't have to worry if I accidentally eject the BT card instead of the storage card ! (too much reading small fonts I guess )

[maslovsky]

All you have to do to fix the hang on eject with the bluemonkey card is to edit /etc/pcmcia/bluetooth

change line 59 from

hciconfig $2 down

to

hciconfig hci0 down

Thanks for the tip, I'll make sure this goes into the next ROM update.