On Mon, Mar 26, 2007 at 10:16:19PM -0400, Marten van Kerkwijk wrote:
> Hi Matt, Stefan,
> 
> Note that I do not need an additional "-s" as suggested by Matt
> (though that works too).  I think that suggestion might be related to
> something I noted while trying different variations, that after "-p"
> on its own the console gets all garbled (green stuff on it; as Matt
> said, it needs switching to X and back to clear).  And after that
> happened once, "-p -m" was not enough any more -> it would lead to
> green stuff again.  But as long as one sticks to "-p -m" from the
> beginning, it's fine.

This is true, I don't think I rebooted between trying them, that's the
effect I got.

> 
> So, Matt, perhaps you can:
> * confirm that -p -m is sufficient after starting up the machine? 

Yes, it works.

> * check that somewhere or other you use vga=792 as well (it wasn't
>   explicitly in the /proc/cmdline you sent; mine is

It doesn't feature in the cmdline, but I have the following in dmesg:

vesafb: framebuffer at 0xe8000000, mapped to 0xe8080000, using 3072k,
total 8000k
vesafb: mode is 1024x768x16, linelength=2048, pages=4
vesafb: protected mode interface info at 00ff:44f0
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:5:5, shift=0:10:5:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device

and /etc/lilo.conf says vga=790.

Matt
--
Matthew Johnson

Attachment: signature.asc
Description: Digital signature

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Suspend-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/suspend-devel

Reply via email to