From: "Ray Lee" <ray-lk@madrabbit.org>
To: "Romano Giannetti" <romanol@upcomillas.es>
Cc: "Antonino Ingargiola" <tritemio@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.21.1 fails to suspend/resume to disk (sort of)
Date: Thu, 24 May 2007 06:56:49 -0700 [thread overview]
Message-ID: <2c0942db0705240656k7d7e4e47r9c43168cc4cecf49@mail.gmail.com> (raw)
In-Reply-To: <1180008823.15600.35.camel@localhost>
On 5/24/07, Romano Giannetti <romanol@upcomillas.es> wrote:
> On Thu, 2007-05-24 at 10:01 +0200, Antonino Ingargiola wrote:
> > 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...
Yeah, the make-kpkg clean is highly annoying, and eventually made me
give up on using that tool. Instead, I've been using the deb-pkg
target that ships with the kernel. When bisecting, I use a script like
the one below to test a new kernel with a minimum of interaction. It
should give you a good idea of how to do all the steps by hand.
And yeah, paring down the .config is critical :-).
#!/bin/bash
sudo -v
make oldconfig
fakeroot make -j2 deb-pkg
sudo dpkg -i ../linux-2.6.20_2.6.20_amd64.deb
sudo update-initramfs -c -k 2.6.20
prev parent reply other threads:[~2007-05-24 13:56 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
2007-05-24 8:17 ` Paolo Ornati
2007-05-24 12:13 ` Romano Giannetti
2007-05-24 13:56 ` Ray Lee [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=2c0942db0705240656k7d7e4e47r9c43168cc4cecf49@mail.gmail.com \
--to=ray-lk@madrabbit.org \
--cc=linux-kernel@vger.kernel.org \
--cc=romanol@upcomillas.es \
--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
Powered by JetHome