OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: Caesium on June 24, 2004, 06:11:07 am
-
Hello,
I did post this to the Accessories forum, but it's only had 7 views in the last couple of days, so it's not really getting much attention and no hope of any help/reply, so maybe here is better - I think this is probably pdaXrom related after all, anyway.
I have a Socket Bluetooth card, Revision G, and I'm finding that I can't get it to do *anything* after I remove it and put it back in. In fact, I have to boot with the card in the slot to make it work at all - if I subsequently take it out and put it back in, it ceases to do anything.
I know it's not the card, because I have a Bluemonkey that does exactly the same. I have to boot in order to get hciconfig to show me anything.
cardctl status shows the card being [ready] after I reinsert it. I've tried dozens of combinations of bluetooth restarting and cardctl resuming etc with absolutely no joy.
Does anyone have any clues to throw me? And ideas why this happens? I'm quite tempted to reflash (using pdaXrom 1.0.5) and start over, I think it's fairly possible I've broken something quite fundamental sad.gif
I haven't actually got rfcomm to work even when hciconfig shows me output yet, but that's another story for another post once I get this fixed - I think it's because the kernel in pdaXrom 1.0.5 doesn't have any -mh patches? So, has anyone managed to get bluetooth of any form working in pdaXrom with the default kernel?
I'm rather hoping the new release will have an upgraded kernel..
-
Deleted message as I realised I had no idea what I was talking about
-
You can get rfcomm to work, just remove the appropriate lines in /etc/rc.d/init.d/bluetooth... You have to use the kernel rfcomm, not the modules..