From: Romano Giannetti <romanol@upcomillas.es>
To: Antonino Ingargiola <tritemio@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 14:13:43 +0200 [thread overview]
Message-ID: <1180008823.15600.35.camel@localhost> (raw)
In-Reply-To: <5486cca80705240101u2fb6a954q53025752560f3ef7@mail.gmail.com>
On Thu, 2007-05-24 at 10:01 +0200, Antonino Ingargiola wrote:
> 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.
> 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.
That is a problem, yes. But I was referring to the need of a make-kpkg
clean every time you recompile changing the EXTRAVERSION, wich forces a
make clean. I am trying to discover how to build manually and initramfs
that works...
>
> 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.
>
Yep, done that. The kernel does not boot (in the initramfs, there is
a /dev/hda1 but it refuses to mount; and yes, I have ext3 and ext2
compiled in, checked a lot of things, no joy. Will retry).
> 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.
>
What would be great is a tool that generate a config starting from the
lsmod list, to start from there and _enable_ more thing... but I know,
I'm dreaming.
Romano
--
Romano Giannetti --- romano.giannetti@gmail.com
Sorry for the following disclaimer, it's attached by our otugoing server
and I cannot shut it up.
--
La presente comunicación tiene carácter confidencial y es para el exclusivo uso del destinatario indicado en la misma. Si Ud. no es el destinatario indicado, le informamos que cualquier forma de distribución, reproducción o uso de esta comunicación y/o de la información contenida en la misma están estrictamente prohibidos por la ley. Si Ud. ha recibido esta comunicación por error, por favor, notifíquelo inmediatamente al remitente contestando a este mensaje y proceda a continuación a destruirlo. Gracias por su colaboración.
This communication contains confidential information. It is for the exclusive use of the intended addressee. If you are not the intended addressee, please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited by law. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this message. Thank you for your cooperation.
next prev parent reply other threads:[~2007-05-24 12:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 7:25 2.6.21.1 fails to suspend/resume to disk (sort of) 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
2007-05-24 8:17 ` Paolo Ornati
2007-05-24 12:13 ` Romano Giannetti [this message]
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=1180008823.15600.35.camel@localhost \
--to=romanol@upcomillas.es \
--cc=linux-kernel@vger.kernel.org \
--cc=tritemio@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