Date: Fri, 3 Feb 2006 11:46:42 +0000 (UTC)
From: [EMAIL PROTECTED]
Subject: Re: [LIB] stanby/hibernate kernel 2.6.14
On Tue, 31 Jan 2006, Richard Mittendorfer wrote:
Date: Tue, 31 Jan 2006 20:52:14 +0100
From: Richard Mittendorfer <[EMAIL PROTECTED]>
Subject: Re: [LIB] stanby/hibernate kernel 2.6.14
Also sprach [EMAIL PROTECTED] (Tue, 31 Jan 2006 09:09:55 -0800):
On Tue, 31 Jan 2006, Richard Mittendorfer wrote:
Also sprach Jose Tavares <[EMAIL PROTECTED]> (Mon, 30 Jan 2006
21:51:09 -0800):
Date: Tue, 31 Jan 2006 03:28:23 -0200
From: Jose Tavares <[EMAIL PROTECTED]>
Subject: Re: [LIB] stanby/hibernate kernel 2.6.14
On Mon, 2006-01-30 at 10:43 -0800, [EMAIL PROTECTED] wrote:
Date: Mon, 30 Jan 2006 12:41:20 +0000 (UTC)
From: [EMAIL PROTECTED]
Subject: stanby/hibernate kernel 2.6.14
anyone know how to keep the display from messing up recoving from
standby and hibernate?
which libby model?
If it's about 1x0ct and the somewhat downward displaced display (X
is ok, only console) after comming back from resume, booting with
the frambuffer console does help. I first noticed this with 2.6.12
IIRC.
its the u100 and it comes up with all kinds of funky colors.
This sounds like an error in the X display driver initializing the
chipset. AFAIK there's some intel GMCH inside? I've read about problems
somewhere. Can't remember exactly where, but likely on LKML.
I had similar symptoms with various graphiccards and un-/semisupported
displaydrivers since starting with linux. Choosing vesa schould solve
it, but will give you nonacellerated video and for sure is no good
option. At last for isolating the troublemaker.
I'm running vesa now. actually runs like junk on mine, for some reason,
andI can't even get the intel one to work. sucks. but not a big issue
since I don't really use standby anyway just hibernate and I can always
get that too work. u100 uses about 2 times too much power anyway so I
don't loose anything. whith the chips toshiba uses it should only use
about 400mAh but it uses 800.
>>> I'm quite sure the wrong way seeing the
display geometry causes
this. X thinks it's 800x600 not 800x480 -- about the gap the display
is displaced. I don't think it's some kernel problem. It looks like
rather X related.
it could be similar since the native res is 800x600 (I believe) and I
am running it at 1024x748. I'm thinking its a combination of that and
the sync being wrong from the start.
Don't know about the new libretto. I assume a driver problem.
thanks for the help.
sl ritch
