From: Collins Richey <erichey2@home.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] kernel source for gentoo
Date: Thu May 17 18:06:02 2001 [thread overview]
Message-ID: <20010517181422.078d0c99.erichey2@home.com> (raw)
In-Reply-To: <3AFE9547.7B9189AC@gentoo.org>
On Sun, 13 May 2001 16:08:07 +0200 AGottinger@t-online.de (Achim Gottinger)
wrote:
> Collins Richey wrote:
> >
> > I'm trying to understand where you hide the kernel source on gentoo and
> > where the options used to generate the standard gentoo kernel are
> located.
> >
> > The kernel you supply, for example, has no sound modules compiled, and
> I would like to recompile for sound support (esssolo1.o and soundcore.o
> are needed) without breaking anything else.
>
> (The default kernel contains all alsa sound modules)
>
fyi, this doesn't do much good unless you have a sound card that works with
als.
> Current kernel source poackage is broken, eigher use
> linux-source-2.4.4-rx.ebuild or
> use a default kernel and run a manual config inbetween.
>
> cd /usr/portage/sys-kernel/linux
> ebuild linux-2.4.4.5.ebuild unpack
> cd /tmp/portage/linux-2.4.4.5/work/linux
> make menuconfig
> cd /usr/portage/sys-kernel/linux
> ebuild linux-2.4.4.5.ebuild merge
>
>
As I alluded to earlier, it isn't a really good idea to overwrite the
working kernel. Fortunately I saved the old kernel and modules. The only
change I made was to add the esssolo1 module, but the new kernel came up
with modules problems and no working eth0.
I think I'll try standard kernel build procedures from the
/tmp/portage/linux-2.4.4.5/work/linux directory with all your patches
applied.
> > Also what is necessary to get ide-cdrw support. I notice that /dev/sr0
> ...
> > have not been generated.
> >
Any answer for this question?
Thanks
--
Collins Richey
Denver area
gentoo system
next prev parent reply other threads:[~2001-05-18 0:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-13 6:53 [gentoo-dev] kernel source for gentoo Collins Richey
2001-05-13 8:37 ` Achim Gottinger
2001-05-13 11:29 ` Collins Richey
2001-05-13 11:37 ` Achim Gottinger
2001-05-13 12:44 ` Daniel Robbins
2001-05-17 18:06 ` Collins Richey [this message]
2001-05-17 18:14 ` Achim Gottinger
2001-05-18 6:14 ` Collins Richey
2001-05-18 11:38 ` Achim Gottinger
2001-05-18 20:33 ` Collins Richey
2001-05-19 10:10 ` Collins Richey
2001-05-19 12:23 ` Achim Gottinger
2001-05-19 13:37 ` Collins Richey
2001-05-19 13:50 ` Achim Gottinger
2001-05-18 1:56 ` Erik Van Reeth
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=20010517181422.078d0c99.erichey2@home.com \
--to=erichey2@home.com \
--cc=gentoo-dev@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