Re: Kernel weirdness

[Derek Broughton <dbroughton@lincsat.com>]

Cristian Ionescu-Idbohrn wrote:
> On Fri, 10 Oct 2003, Derek Broughton wrote:
>
>
> > From: "Cristian Ionescu-Idbohrn" <cristian.ionescu-idbohrn@axis.com>
> >
> > > On Sun, 5 Oct 2003, Rob wrote:
> > >
> > >
> > > > I've installed the kernel-image-2.4.22-1-686 package. Until now,
> > > > I've been running the 2.4.18-bf2.4 kernel. Though I didn't change
> > > > what modules I load, with this new kernel package have come a whole
> > > > bunch of new modules that are being loaded. I've run modconfig and
> > > > removed them, but they continue to to load at boot.
> > >
> > > This insane behaviour is caused by initrd:
> >
> > mkinitrd
> >
> > it's not that hard to change
>
>
> Shouldn't need to change anything, if it can be done right from the start.

Of course you should.  You've downloaded a completely generic kernel and
expect it to know what modules _your_ laptop requires.  The only way to
change that is to make your own initrd.  And while you're at it, you
might as well compile your own kernel.