OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: Zumi on October 12, 2004, 03:55:29 pm
-
Thank you for the info.
My main issue with pdaXrom since first RC is when it freeze with:
_ they keyboard frozen in X11 (no more way to get out with Control-Alt-Backspace)
_ no more click even sent to application
_ but the mouse is still moving and follow on screen click
I saw strange behaviour on matchbox tray so perhaps it grabs all events and then freeze. Or perhaps it's a X11 issue as It manages slowly input evens like click on screen or keyboard for applications...
And last info, the "freeze" only occur at power (SL-C760).
I have the same issue, but not sure of it's conditions when it happens, so I haven't posted about it before.
The mouse cursor is moving, but I can't click on anything and keyboard input is broken too (I think the poweroff button working however on the back, not 100% sure). Once happened the matchbox-responding-but-nothing-starts thing too.
I only have a slight idea what causes it: it usually happens after I change the system clock, with the builtin timesetting app (made by Laze, I think ) and with the "ntpdate" command from the console too.
It seems somehow linked with that. If I reboot before the lockup, the date is stored but it's not a very comfortable way of setting time and if system locks up after that, the time when I rebooted comes back to the system clock.
That's all I can say about it.
Zumi
-
zumi - don't know why you decided to add this post to the other thread... I've split it into it's own (as it should be).
which version of the rom are having this trouble on?
-
zumi - don't know why you decided to add this post to the other thread... I've split it into it's own (as it should be).
Well, I tought it's OK in the main RC5 thread. A new thread is better maybe, right.
which version of the rom are having this trouble on?
I'm currently using RC5 and this problem exists there. I had problems with the system clock before (since I'm using the ROM, so 1.0.5), but I don't know whether it's in the other RCs 'cause it's getting outlined for me now, in the RC5.
Hope we can get rid of this bug, because virtually I haven't seen an accurate date on Zaurus since I'm using it.
-
We have discovered some problems with this and hopefully some of the date problems is further solved in the next RC (arghh we are never going to release a final ) :-)
-
We have discovered some problems with this and hopefully some of the date problems is further solved in the next RC (arghh we are never going to release a final ) :-)
Better have a lot of RC than a buggy final!
Good to hear that you know about this error.
Zumi
-
I also have this behaviour quite often.
Scott
ps: c700