Re: [jornada] Jornada 720: Debian Sarge/X/Rebooting.

On Tuesday 24 January 2006, Colin Sauze wrote:
> On 24/01/06, Travis Poppe <tlp_at_liquidx.org> wrote:
> > However, I do have a few questions/problems. When I switch to console
> > and then attempt to switch back to X, I get a blank screen and cannot
> > do anything (including switching back to console). I can remedy the
> > problem by logging into the Jornada via ssh and initiating X from
> > there, which gives me control of the system again.
> >
> > This works fine so long as I have ssh access to the machine, but if I
> > don't, the only solution is to reboot. And that doesn't work, unless
> > you remove all sources of power to the system, boot into WinCE, and
> > re-run linexec.
>
> Your machine is obviously still responding. Try pressing ctrl alt
> backspace, this should kill off X. Although this may or may not cause the
> display to be reinitialised. Still worth trying.

When this occurs, X actually crashes (or the process just ends) and leaves me
with a blank screen. So, it has already been 'killed', but doesn't do it in a
graceful way or something. I've discovered this when running 'startx' in an
ssh session and then watching what happens when I try to switch back to X
from the terminal.

Also, it doesn't occur every time. Sometimes I can successfully switch back to
X.

> > Is there a method of rebooting the Jornada -without- doing a "hard"
> > reboot? The stylus reset button leaves the system in an unusable state.
> > I see a very dark HP logo and then nothing happens.
>
> Which kernel are you using? I seem to remember (but may be wrong on this)
> that newer versions of the kernel could reboot the jornada properly?

I'd certainly love to see that feature, if its possible. I'm running Linux
2.4.31. uname -a output below:

Linux jornada 2.4.31-j720 #1 Sat Jul 23 17:03:18 CEST 2005 armv4l GNU/Linux

Although this does not happen frequently, I've had sound support (madplay-ing
an mp3) crash the system, which require two reboots. One to do the initial
fsck, and the second because Debian/fsck requests a reboot after it gets
done.

Thanks,

-- 
Travis Poppe
IRC: tlp @ irc.freenode.net