public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Collins Richey <erichey2@home.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] kernel source for gentoo
Date: Fri May 18 20:33:02 2001	[thread overview]
Message-ID: <20010518204053.422af17f.erichey2@home.com> (raw)
In-Reply-To: <3B05570A.4866E010@gentoo.org>

On Fri, 18 May 2001 19:08:26 +0200 AGottinger@t-online.de (Achim Gottinger)
wrote:

> Collins Richey wrote:
> > 
> > On Fri, 18 May 2001 01:44:52 +0200 AGottinger@t-online.de (Achim
> Gottinger)
> > wrote:
> > 
> > > Collins Richey wrote:
> > > >
> > > > On Sun, 13 May 2001 16:08:07 +0200 AGottinger@t-online.de (Achim
> > > Gottinger)
> > > > wrote:
> > > >
> > > > > Collins Richey wrote:
> > > > > >
> > 
> > > > > > 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.
> > >
> > > Hi Collins,
> > >
> > > I updated the kernel packages yesterday, you can now use
> > > linux-sources-2.4.4.9
> > >
> > > If you want the default configuration copy
> > > /usr/portage/sys-kernel/linux-sources/files/2.4.4-ac9/config.bootcomp
> to
> > > /usr/src/linux/.config before you run make {x,menu}config.
> > >
> > > This kernel package uses the following USE variables for extras "lvm
> > > lm_sensors pcmcia-cs alsa".
> > > Add the ones you want top the USE variable in /etc/make.conf.
> > >
> > > After you have build the kernel you can build the extras modules and
> > > utilities by installing
> > >
> > > linux-extras-2.4.4.9.ebuild.
> > >
> > 
> > It doesn't work.  I did the following
> > 
> >         cd /usr/portage/sys-kernel/linux-sources
> >         ebuild linux-2.4.4.9.ebuild unpack
> >         cp
> /usr/portage/sys-kernel/linux-sources/files/2.4.4-ac9/config.bootcomp
> > /usr/src/linux/.config
> >         cd /tmp/portage/linux-2.4.4.9/work/linux
> >         tried make xconfig (error option not found)
> >         make menuconfig (added esssolo1 and corrected stuff for
> ide-scsi)
> >         cd /usr/portage/sys-kernel/linux-sources
> >         ebuild linux-2.4.4.9.ebuild merge
> > 
> > When I booted from the new kernel, eth0 would not start.  I discovered
> that
> > the procedure had added empty /etc/modules/2.4.4-ac5 for 2.4.4-ac5 but
> no
> > /lib/modules/2.4.4-ac5.  Only /etmodules/2.4.4-ac3 and
> > /lib/modules/2.4.4-ac3 contain data.  Since the kernel calls itself
> -ac5,
> > modprobe, etc. will not use any of the modules.
> 
> Hmm, there seems to be a bug in modultils.
> /lib/modules/[uname-r]/modules.dep is not generated correct.
> 
> Remove /etc/modules/[unname -r] and /etc/modules.conf  and run
> /etc/rc.d/init.d/modules. This will generate those files again.
> 
> I'm working on that bug here at the moment.
> 

That may be a problem, too, but I don't think that will fix my problem. 
Something went wrong with the kernel + modules ebuild.  The normal output
of the kernel sequence, ie make mrproper, make xxxconfig, make deps make,
make modules and make modules_install is a bzImage (ebuild got that right)
and a modules directory /lib/module/kernelname (ebuild did not produce
this), so the merge really failed even though it said it was complete.  It
won't do me any good to rebuild the modules.conf etc - the modules
themselves are missing in action.

Thanks,
-- 
Collins Richey
Denver area
gentoo system



  reply	other threads:[~2001-05-19  2:32 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
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 [this message]
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=20010518204053.422af17f.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