OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Sharp ROMs => Topic started by: bodgit on February 29, 2004, 08:12:21 pm
-
I\'ve just tried theKompany.rom on my SL-5500 and it seems to work great so far, apart from when I either try and eject or awaken my Zaurus, with my Bluemonkey BlueCF Card inserted, (bluecard_cs.o driver). I\'ve tried using both the GUI and using \"cardctl eject\", no difference, solid hang, under either 1.0-final or 2.0-alpha3
I didn\'t have this problem using the latest 3.x Sharp ROM, so on a hunch, I tried installing the bluez .ipk package that I installed under that ROM and it\'s fixed it on both versions.
The thing is, all of the files I\'ve checked so far between the bluez drivers installed on both the theKompany and Sharp ROM appear to be no different so I\'m at a loss to work out what I\'ve changed, (thinking one ROM has an older/newer version of the bluez drivers installed).
I must point out that I\'ve not yet configured any Bluetooth connections yet, I was just testing that the Zaurus identified my various CF cards under theKompany ROM when I hit this problem.
Anyone shed any light on this?
-
I fixed this a little while ago in the separate BlueZ ipks. The only difference is a \'sleep 1\' in /etc/pcmcia/bluetooth . It seems the BlueMonkey card needs a slight pause before the eject procedure is completed.
-
Ah, subtle, found it! :wink: