On Tue, Mar 27, 2007 at 02:43:28PM +0100, Matthew Johnson wrote:
> On Tue, Mar 27, 2007 at 12:48:29PM +0200, Stefan Seyfried wrote:
> > And when you pressed enter, did you get a readable prompt or was it
> > all fscked up until you switched to X?
>
> If I suspend from X with -p it works (since it
On Tue, Mar 27, 2007 at 12:48:29PM +0200, Stefan Seyfried wrote:
> On Mon, Mar 26, 2007 at 04:24:58PM +0100, Matthew Johnson wrote:
> > On Mon, Mar 26, 2007 at 05:21:39PM +0200, Stefan Seyfried wrote:
> > >
> > > did -p -m leave the console totally dark, or was it just empty, (but
> > > pressing
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"
> > > did -p -m leave the console totally dark, or was it just empty, (but
> > > pressing
> > > enter gave you a new prompt)? I'm asking because the console being empty
> > > is
> > > not a bug but working as expected (this is documented, and somebody who
> > > really cares should probably fix it
Hi Stefan,
> > Otherwise, I'm mostly curious whether the fact that vga=0 does *not*
> > work for a Dell X200 is unique to this machine. Perhaps the web site
> > should mention it as yet something else to try...
>
> It should actually also work with vga=0. Note that "only garbage on console
> aft
On Mon, Mar 26, 2007 at 04:24:58PM +0100, Matthew Johnson wrote:
> On Mon, Mar 26, 2007 at 05:21:39PM +0200, Stefan Seyfried wrote:
> >
> > did -p -m leave the console totally dark, or was it just empty, (but
> > pressing
> > enter gave you a new prompt)? I'm asking because the console being empt
On Mon, Mar 26, 2007 at 10:16:19PM -0400, Marten van Kerkwijk wrote:
> Hi Matt, Stefan,
>
> OK, so I finally have a working s2ram on my Dell X200!! I first
good :-)
> So, Matt, perhaps you can:
> * confirm that -p -m is sufficient after starting up the machine?
> * check that somewhere or othe
Hi Matt, Stefan,
OK, so I finally have a working s2ram on my Dell X200!! I first
thought it was related to the fact that Matt used intelfb while I did
not, but it turned out the trick is to have vga=792 (=0x318) as a boot
option (with or without intelfb; surprisingly vga=773, which should be
the
On Mon, Mar 26, 2007 at 05:21:39PM +0200, Stefan Seyfried wrote:
> On Mon, Mar 26, 2007 at 03:17:29PM +0100, Matthew Johnson wrote:
> > On Mon, Mar 26, 2007 at 09:02:19AM +0200, Stefan Seyfried wrote:
> > > On Mon, Mar 26, 2007 at 04:18:13AM +0100, Matthew Johnson wrote:
> > > > On Sun, Mar 25, 200
On Mon, Mar 26, 2007 at 03:17:29PM +0100, Matthew Johnson wrote:
> On Mon, Mar 26, 2007 at 09:02:19AM +0200, Stefan Seyfried wrote:
> > On Mon, Mar 26, 2007 at 04:18:13AM +0100, Matthew Johnson wrote:
> > > On Sun, Mar 25, 2007 at 09:05:32PM -0400, Marten van Kerkwijk wrote:
> > > > Dear Matt,
> >
On Mon, Mar 26, 2007 at 09:02:19AM +0200, Stefan Seyfried wrote:
> On Mon, Mar 26, 2007 at 04:18:13AM +0100, Matthew Johnson wrote:
> > On Sun, Mar 25, 2007 at 09:05:32PM -0400, Marten van Kerkwijk wrote:
> > > Dear Matt,
> > >
> > > I was very interested to see you say that
> > >
> > > > I also
On Mon, Mar 26, 2007 at 08:59:10AM +0200, Stefan Seyfried wrote:
> On Sun, Mar 25, 2007 at 11:06:04AM +0100, Matthew Johnson wrote:
> > I have an Asus M2V which I tried using s2ram on. It works fine with no
> > workarounds, but is listed as unknown. The output of s2ram -i is:
>
> Does it work from
On Mon, Mar 26, 2007 at 04:18:13AM +0100, Matthew Johnson wrote:
> On Sun, Mar 25, 2007 at 09:05:32PM -0400, Marten van Kerkwijk wrote:
> > Dear Matt,
> >
> > I was very interested to see you say that
> >
> > > I also have a dell X200 which works with the -p and -s workarounds. The
> > > output o
On Sun, Mar 25, 2007 at 11:15:14AM +0100, Matthew Johnson wrote:
> On Sun, Mar 25, 2007 at 11:06:03AM +0100, Matthew Johnson wrote:
> > I have an Asus M2V which I tried using s2ram on. It works fine with no
> > workarounds, but is listed as unknown. The output of s2ram -i is:
>
> I also have a del
On Sun, Mar 25, 2007 at 11:06:04AM +0100, Matthew Johnson wrote:
> I have an Asus M2V which I tried using s2ram on. It works fine with no
> workarounds, but is listed as unknown. The output of s2ram -i is:
Does it work from both X and from text console?
> [EMAIL PROTECTED]:~ $ sudo s2ram -i
> Th
On Sun, Mar 25, 2007 at 09:05:32PM -0400, Marten van Kerkwijk wrote:
> Dear Matt,
>
> I was very interested to see you say that
>
> > I also have a dell X200 which works with the -p and -s workarounds. The
> > output of s2ram -i on that is:
Hmm... Maybe I don't have working s2ram. I now have rea
On Sun, Mar 25, 2007 at 09:05:32PM -0400, Marten van Kerkwijk wrote:
> I just tried again, and s2ram -f -p -s just kills my system (like all
> other combinations): it suspends fine, but on resume, it starts but
> then dies, screen remaining dark, CAPS LOCK not working, etc. This
> both from X an
Dear Matt,
I was very interested to see you say that
> I also have a dell X200 which works with the -p and -s workarounds. The
> output of s2ram -i on that is:
>
> [EMAIL PROTECTED]:~ $ sudo s2ram -i
> This machine can be identified by:
> sys_vendor = "Dell Computer Corporation"
> sys_
On Sun, Mar 25, 2007 at 11:06:03AM +0100, Matthew Johnson wrote:
> I have an Asus M2V which I tried using s2ram on. It works fine with no
> workarounds, but is listed as unknown. The output of s2ram -i is:
I also have a dell X200 which works with the -p and -s workarounds. The
output of s2ram -i o
I have an Asus M2V which I tried using s2ram on. It works fine with no
workarounds, but is listed as unknown. The output of s2ram -i is:
[EMAIL PROTECTED]:~ $ sudo s2ram -i
This machine can be identified by:
sys_vendor = "System manufacturer"
sys_product = "System Product Name"
sys_ver
20 matches
Mail list logo
