Re: Upgrading pcmcia modules with self-built kernel
> On Fri, 28 Jan 2000, Heather wrote:
>
> > > The packages kernel-source-2.2.x and pcmcia-source should build the
> > > -custom packages. I don't know if that's possible to combine with the
> > > maintainers using those packages to build the -generic packages.
> > >
> > > Do you think this is a sollution for this problem, or is it solvable in
> > > another way ?
>
> > When making your kernel from source, first you get your options settled in
> > (make menuconfig or xconfig), but before running make, adjust the Makefile
> > that results, there is an extra variable. I used this on my laptop to
> > create an x.y.z-HGS version, so that's where my personally compiled modules
> > went too.
> >
> > In my case it was overkill (I was cooking a 2.3.x kernel anyway) but this
> > is the same way that Mandrake sneaks in mdk to their kernel name, and how
> > RedHat puts an additional number on the end. I also tweaked lilo.conf so
> > it's willing to boot off either the "normal" sequence, or my kernel,
> > and defaulting to mine which isn't going to change out from under it as
> > often.
> >
> > I think the extra variable is EXTRAVERSION but I'm not sure; I'm sitting in
> > front of a different system at the moment.
>
> Well, it's not the kernel version that's the problem, it's dpkg that
> (correctly) considers the pcmcia maintainer's build of
> pcmcia-modules-2.2.x more recent than my own build. This breaks my system,
> because pcmcia-modules and kernel-image need to match.
What I described does not correct dpkg's behavior in this regard, that's
true. What it does is take the kernel and associated modules that you
build, out of the sequence of things that dpkg is planning to squish.
So you end up with two kernel sets:
/boot/vmlinuz-2.2.<dpkg bait>
/lib/modules/2.2.<dpkg bait>
and
/boot/vmlinuz-2.2.13-homegrown
/lib/modules/2.2.13-homegrown
While you will have to add the second kit to lilo.conf, I can tell you,
lilo.conf is easier to defend than your entire kernel kit.
> I use kernel-package to build the kernel, so EXTRAVERSION is pointless in
> this context.
Ah well, there's a problem. I have no experience with doing it that way.
Sorry.
Try renaming your /lib/modules/<bait number> directory and old kernel
before the fresh build?
> Currently my laptop has pcmcia-modules-2.2.13 version 3.1.5-1+laptop.2,
> but the official Debian version is at least 3.1.8-4, so dpkg wants to
> install that version if I didn't put it on hold.
>
> --
> Tot ziens,
> Bart-Jan
Good luck
-* Heather Stern * Starshine Technical Services * star@starshine.org *-
Reply to: