lkml.org 
[lkml]   [2007]   [Aug]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Linux 2.6.23-rc2
On 8/5/07, Linus Torvalds <torvalds@linux-foundation.org> wrote:

> Jeff - do I understand correctly that the "or" means that even *without* a
> suspend-to-ram sequence, and just by going into X and then going back to
> text-mode, the screen is corrupt?

I've done more tests. It seems that "suspend-to-ram" sequence is the
culprit. After resume, the text console is messed up. Not switching
X/console.

Boot up. Console -> X ok -> Console ok -> s2ram -> console bad -> X ok
-> console bad -> X ok.

> I just want to make sure that there is no suspend-related activity
> required for this at all, and the only common issue is probably just that
> suspend ends up *also* triggering the X mode-setting at resume..

It's suspend as indicated above.


> (Side note: if you have a modern distro, you might try to change the line
> that says
> Driver "i810"
> in the /etc/X11/xorg.conf to say
> Driver "intel"

I'll test this and get back.

Thanks,
Jeff.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-08-05 04:31    [W:0.060 / U:0.020 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site