From: tprado <tprado@charter.net>
To: Burton Samograd <kruhft@kruhft.dyndns.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] new gentoo-sources kernels (r5+)
Date: Tue, 17 Sep 2002 23:53:45 -0400 [thread overview]
Message-ID: <3D87F8C9.5070003@charter.net> (raw)
In-Reply-To: 20020918032411.GK4904@kruhft.dyndns.org
I haven't had any problems with the gentoo kernel sources. I have r9 on
a couple machines. r7 on another and a custom ACPI enabled kernel
(http://sourceforge.net/projects/acpi) on my laptop based off the
vanilla 2.4.19 (with 2.4.20-pre5 patched in).
It sounds like you're probably making a simple mistake somewhere in your
kernel upgrade somewhere.
My usual kernel install procedure is:
#cd /usr/portage/sys-kernel/...
#ebuild <insert kernel ebuild version here> merge (so it won't
unmerge any older ones)
#cd /usr/src/linux-<version>
#cp /usr/src/linux/.config .
#make oldconfig
#make dep && make clean bzImage modules modules_install
#cp arch/i386/boot/bzImage /boot/gentoo<version>-<my-build#>.img
#cp System.map /boot/System.map-<version>-<my-build#>
#cd /usr/src
#rm linux
#ln -s linux-<version> linux
#cd /boot
#rm System.map
#ln -s System.map-<version>-<my-build#> System.map
edit /etc/lilo.conf for the new version (okay, I still use lilo :-)
#lilo
#shutdown -r now
Wow, I actually do all that? I've never written it all down before :-)
I don't have /boot in it's own partition in my setup...
It's gonna be something silly, I'm sure :-)
Good luck,
Tom
Burton Samograd wrote:
>Hi,
>
>Is it just me, or are the new gentoo-sources unusable? I just went
>through hell trying to get one of them to boot with absolutely no
>sucess. I kept getting "Cannot find init errors" to "* respawning too
>quickly" to whatever you could think of. I've never had this many
>problems with installing a kernel in my life, and I'm wondering if I'm
>doing something dreadfully wrong or if these new sources are just
>really unstable with all the patches installed.
>
>Just to let you know, i'm not experiencing newbie mistakes as i've
>been using linux for over 8 years and never had a kernel not boot
>unless it was something stupid on my part. I did everything in my
>experience to get these darn things working and well...they just don't
>for me. Anybody else having problems like this?
>
>Oh, and the linux-beta sources also won't boot either, but those are
>beta and i don't expect anything from them :)
>
>burton
>
next prev parent reply other threads:[~2002-09-18 3:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-18 3:24 [gentoo-dev] new gentoo-sources kernels (r5+) Burton Samograd
2002-09-18 3:53 ` tprado [this message]
2002-09-18 15:52 ` Burton Samograd
2002-09-18 16:15 ` Toby Dickenson
2002-09-18 23:48 ` Burton Samograd
2002-09-19 1:17 ` Christopher J. PeBenito
2002-09-19 7:11 ` Evan Read
2002-09-19 9:06 ` Christian Axelsson
2002-09-18 16:15 ` Mike Lundy
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=3D87F8C9.5070003@charter.net \
--to=tprado@charter.net \
--cc=gentoo-dev@gentoo.org \
--cc=kruhft@kruhft.dyndns.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