mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Antonino Ingargiola" <tritemio@gmail.com>
To: "Romano Giannetti" <romano.giannetti@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.21.1 fails to suspend/resume to disk (sort of)
Date: Thu, 24 May 2007 10:01:21 +0200	[thread overview]
Message-ID: <5486cca80705240101u2fb6a954q53025752560f3ef7@mail.gmail.com> (raw)
In-Reply-To: <1179914262.7043.56.camel@localhost>

Hi,

2007/5/23, Romano Giannetti <romano.giannetti@gmail.com>:
[cut]
> Uf, I will try to find the time. I am on my way to try to compile
> 2.6.21.2 now. Problem is that a kernel compile "the ubuntu way" last
> hours here. If there is an expert on make-kpkg here, I could use some
> advise. I'd prefer to test patches over a 2.6.21 stable release, to
> avoid mixing symptoms from an experimental -rc...

Is not the ubuntu or debian way to take hours to compile. Is that you
have to trim the config and enable the only modules you need for your
hardware, then a rebuild cycle could last 10-15 min.

You will spend one hour once to cut down the configuration, but then
you can reuse the .config for new kernels too with make oldconfig.

To find the minimum configuration for you hardware use lspci -v,
menuconfig help, and look at chapter 7 and 8 of Linux Kernel in a
Nutshell:

http://www.kroah.com/lkn/

Also, pasting "lspci -n" output in the following page can be of some help:

http://kmuto.jp/debian/hcl/

Hope this helps.

> Romano

    ~ Antonio

  parent reply	other threads:[~2007-05-24  8:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23  7:25 Romano Giannetti
2007-05-23  9:05 ` Rafael J. Wysocki
2007-05-23  9:57   ` Romano Giannetti
2007-05-23 16:57     ` Rafael J. Wysocki
2007-05-24  5:20       ` Romano Giannetti
2007-05-24 19:27         ` Rafael J. Wysocki
2007-05-24 22:51           ` Romano Giannetti
2007-05-24  8:01     ` Antonino Ingargiola [this message]
2007-05-24  8:17       ` Paolo Ornati
2007-05-24 12:13       ` Romano Giannetti
2007-05-24 13:56         ` Ray Lee

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=5486cca80705240101u2fb6a954q53025752560f3ef7@mail.gmail.com \
    --to=tritemio@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=romano.giannetti@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®