All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Hesse <christian.hesse-5lmcC6f56PSELgA04lAiVw@public.gmane.org>
To: hgfelger-9nAOAgdJVo4b1SvskN2V4Q@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	liste-9nAOAgdJVo4b1SvskN2V4Q@public.gmane.org
Subject: Re: Success with kernel-swsusp and Nvidia-closed-source
Date: Thu, 4 Nov 2004 09:54:45 +0100	[thread overview]
Message-ID: <200411040954.49879.christian.hesse@linuxob.de> (raw)
In-Reply-To: <Pine.LNX.4.60.0411032322410.4984-KnfdeQs3A3X/9pzu0YdTqQ@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]

On Wednesday 03 November 2004 23:29, liste-9nAOAgdJVo4b1SvskN2V4Q@public.gmane.org wrote:
> Salut Christian,
>
> On Wed, 3 Nov 2004, Christian Hesse wrote:
> > I'm using software suspend 2.1. For me suspend works fine, but the system
> > freezes as soon as it is resumed, I only see a black screen then. Driver
> > nv works without any problems. Any hints what could be the cause?
>
> I did not patch in anything into the kernel. I used a vanilla 2.6.9 (only
> the Makefile was patched to show 2.6.9 instead of 8 ... maybe somebody
> watched a bit too much tv... :-)
> So I did not use swsusp 2.1. And I could not manage to freeze on resume
> this time. So, why didn't you try the vanilla-kernel, with the
> Haggi' s patch for the nvidia driver?
> When you test - be sure to sync before suspending. It's the second best,
> besides having a jung backup handy.

Vanilla kernel's suspend to disk is too slow for me. I needs 90 seconds to 
suspend the system (vs. 10 seconds with swsusp-2.1). I think I'll continue 
using nv until Nvidia releases a version of the driver that works without any 
problems for me.

-- 
Christian Hesse

geek by nature
linux by choice

[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]

      parent reply	other threads:[~2004-11-04  8:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-03 11:25 Success with kernel-swsusp and Nvidia-closed-source liste-9nAOAgdJVo4b1SvskN2V4Q
     [not found] ` <Pine.LNX.4.60.0411031215260.1187-KnfdeQs3A3X/9pzu0YdTqQ@public.gmane.org>
2004-11-03 18:58   ` Christian Hesse
     [not found]     ` <200411031958.47910.christian.hesse-5lmcC6f56PSELgA04lAiVw@public.gmane.org>
2004-11-03 22:29       ` liste-9nAOAgdJVo4b1SvskN2V4Q
     [not found]         ` <Pine.LNX.4.60.0411032322410.4984-KnfdeQs3A3X/9pzu0YdTqQ@public.gmane.org>
2004-11-04  2:11           ` Nigel Cunningham
     [not found]             ` <1099534267.3991.52.camel-r49W/1Cwd2ff0s6lnCXPXw0QcLn3kwYh@public.gmane.org>
2004-11-04 11:59               ` liste-9nAOAgdJVo4b1SvskN2V4Q
     [not found]                 ` <Pine.LNX.4.60.0411041242210.1565-KnfdeQs3A3X/9pzu0YdTqQ@public.gmane.org>
2004-11-04 13:03                   ` Christian Hesse
2004-11-04 16:36                   ` liste-9nAOAgdJVo4b1SvskN2V4Q
     [not found]                     ` <Pine.LNX.4.60.0411041729180.4727-KnfdeQs3A3X/9pzu0YdTqQ@public.gmane.org>
2004-11-04 17:12                       ` Christian Hesse
     [not found]                         ` <200411041812.54813.christian.hesse-5lmcC6f56PSELgA04lAiVw@public.gmane.org>
2004-11-07 19:52                           ` Christian Hesse
     [not found]                             ` <200411072052.53065.mail-8oMOrB1mGocUSW6y5lq3GQ@public.gmane.org>
2004-11-08 15:47                               ` liste-9nAOAgdJVo4b1SvskN2V4Q
     [not found]                                 ` <Pine.LNX.4.60.0411081640410.4713-KnfdeQs3A3X/9pzu0YdTqQ@public.gmane.org>
2004-11-08 16:45                                   ` Karol Kozimor
2004-11-06 22:17                       ` liste-9nAOAgdJVo4b1SvskN2V4Q
     [not found]                         ` <Pine.LNX.4.60.0411062301590.5414-KnfdeQs3A3X/9pzu0YdTqQ@public.gmane.org>
2004-11-15 22:10                           ` liste-9nAOAgdJVo4b1SvskN2V4Q
2004-11-04  8:54           ` Christian Hesse [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200411040954.49879.christian.hesse@linuxob.de \
    --to=christian.hesse-5lmcc6f56pselga04laivw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=hgfelger-9nAOAgdJVo4b1SvskN2V4Q@public.gmane.org \
    --cc=liste-9nAOAgdJVo4b1SvskN2V4Q@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.