From: Daniel Iliev <danny@ilievnet.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] kernel recompile?
Date: Tue, 31 Oct 2006 19:31:42 +0200 [thread overview]
Message-ID: <4547887E.4030606@ilievnet.com> (raw)
In-Reply-To: <45478234.4050302@verizon.net>
Sean wrote:
>
> Since my gcc upgrade all my modules fail on boot with an error of
> version magic '2.6.16-gentoo-r9 SMP gcc-4.1' should be
> '2.6.16.16-gentoo-r9 SMP gcc-3.4'
>
> However when I try to start the rebuild of my kernel it stops just
> after starting with the line
>
> 'if [ -r System.map -a -x /sbin/depmod ]; then /sbin/depmod -ae -F
> System.map 2.6.16-gentoo-r9; fi'
>
> any ideas on the cause?
cp /usr/src/linux/.config /usr/src/ # preserve the configuration
cd /usr/src/linux/
make mrproper # this puts the kernel source tree in a state as if it
was just extracted
cp /usr/src/.config . # restore the configuration
make && make modules_install
Then do what you do to install your new kernel. For example I have 2
boot entries:
- "Gentoo" (default after 5 seconds) with kernel "/boot/bzImage"
- "Test" with kernel "/boot/bzTest"
So the commands in my case are:
cp /usr/src/linux/arch/x86_64/boot/bzImage /boot/bzTest
cp System.map /boot
lilo
When I compile a new kernel, I first try it with "Test" and if it works,
a do
cp /boot/bzTest /boot/bzImage && lilo # to make it default boot option
After you are ready with the new kernel and it boots OK (no module
problems etc.) you'll have to emerge nvidia-drivers...again.
In fewer words: Recompile the kernel to solve its problems and then
emerge nvidia-drivers.
HTH
--
Best regards,
Daniel
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-31 17:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 14:10 [gentoo-amd64] kernel recompile? Sean
2006-10-31 14:16 ` Piotr Pruszczak
2006-10-31 14:25 ` Daniel Iliev
2006-10-31 14:37 ` Piotr Pruszczak
2006-10-31 15:59 ` Daniel Iliev
2006-10-31 16:14 ` Boyd Stephen Smith Jr.
2006-11-02 9:48 ` Michel Merinoff
2006-11-02 10:36 ` Neil Bothwick
2006-10-31 16:19 ` Pawel Kraszewski
2006-10-31 16:49 ` Daniel Iliev
2006-10-31 17:04 ` Sean
2006-10-31 17:18 ` Mathieu Seigneurin
2006-10-31 17:31 ` Daniel Iliev [this message]
2006-10-31 18:14 ` Sean
2006-10-31 18:21 ` Daniel Iliev
2006-10-31 18:39 ` Daniel Iliev
2006-10-31 18:48 ` Sean
2006-10-31 19:11 ` Daniel Iliev
2006-10-31 19:38 ` sean
2006-10-31 21:57 ` Daniel Iliev
2006-11-01 19:24 ` sean
2006-11-01 20:39 ` Daniel Iliev
2006-11-01 9:05 ` Pawel Kraszewski
2006-11-01 12:47 ` Daniel Iliev
2006-11-01 14:32 ` Pawel Kraszewski
2006-11-01 16:55 ` Florian D.
2006-11-01 16:37 ` Jesús Guerrero
2006-11-01 19:14 ` Pawel Kraszewski
2006-11-01 17:06 ` [gentoo-amd64] [OT] " Daniel Iliev
2006-11-01 19:01 ` [gentoo-amd64] [OOT] Apologies Pawel Kraszewski
2006-11-01 20:02 ` [gentoo-amd64] [OOT] [SOLVED] Apologies Daniel Iliev
2006-10-31 14:22 ` [gentoo-amd64] kernel recompile? Sebastian Redl
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=4547887E.4030606@ilievnet.com \
--to=danny@ilievnet.com \
--cc=gentoo-amd64@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox