On Mon, May 14, 2001 at 01:56:20PM +0100, James ''Wez'' Weatherall wrote:
> > I haven't run into this with my testing. The only issue I noticed is that
> > going into sleep, while having the screensaver activated, and then coming
> > out of sleep, causes the screen to turn on. Then, if you tap the screen,
> the
> > screen turns off, requiring that a sleep/resume cycle to get things going
> > again. Is this what you're seeing?
>
>
> I've just been to the pub with David Woodhouse and he says the Flash RAM bug
> I've fallen foul of is a known one that he's fixed - we should probably get
> a more recent kernel image to fix that. Also, there are some alignment
Like any good bug, I didn't hit it till this morning, when I started rapidly
suspending and resuming for a minute. Oh well. There's a new kernel up,
so try it out:
052e2790e63763770ad3d54a362332ab zImage-2.4.3-rmk2-np1-fam2
Thanks for ambushing Dave when he least expected it. ;>
> "fix" bugs in the current 2.4.3 build Familiar uses, according to him.
> The Flash bug only shows up for me after a few sleep/resume cycles. David
> says it was a problem with the jffs2 code not knowing that the machine had
> been slept.
Yeah, that's what the patch looks like.
> The effect I'm seeing is that I press the sleep button and it sleeps, then
> when I press it again, the display briefly powers up, then goes off and
> stays off. No input action will bring it back. This is with or without
> screen saver enabled. The display stays on for about one second, then goes
> off.
>
> The latter bug looks to me like some sort of Xserver confusion, or a problem
> with the touchscreen driver.
Have you tried cycling deep sleep? I'll take a deeper look at it after I get
some food in me.
Alexander
Received on Mon May 14 2001 - 12:44:42 EDT
This archive was generated by hypermail 2.2.0 : Mon Jul 25 2005 - 17:12:24 EDT