On Thu, 28 Sep 2000, John Summerfield wrote:
> >
> > When you change the kernel configuration even while staying on the same
> > version it's possible (or likely, I think) that internal kernel
> > datastructures change. Some of them are more critical than others.
> >
> > If you want more detail
Sorry, I meant make bzImage...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Mike A. Harris
Sent: Wednesday, September 27, 2000 8:38 AM
To: Red Hat Development List
Subject: Re: kernel modules
On Tue, 26 Sep 2000, Balazs Wellisch wrote:
>Date:
>
> make clean is not needed, but make bzImage is. I'm not sure what
> the make install target does, but I'll bet that it requires make
> bzImage first. Read the kernel README for details.
>
Oh, it will make a kernel, and it will probably work. the kernel it makes may
be or not be the one des
>
> When you change the kernel configuration even while staying on the same
> version it's possible (or likely, I think) that internal kernel
> datastructures change. Some of them are more critical than others.
>
> If you want more detailed explanation you'll have to search the net (read
> lin
> On Wed, 27 Sep 2000, Dave Ihnat wrote:
> > On Tue Sep 26 2000 at 18:04, "Balazs Wellisch" wrote:
> > > Can anyone tell me how to correct the following error:
> > >
> > > depmod: *** Unresolved symbols in /lib/modules/2.2.16-3/misc/emu10k1.o
> > >From the make menuconfig or xconfig, disable
> >
"Mike A. Harris" <[EMAIL PROTECTED]> writes:
> make clean is not needed, but make bzImage is. I'm not sure what
> the make install target does, but I'll bet that it requires make
> bzImage first.
You lose the bet.
make install is defined in
/usr/src/linux-2.2.16/arch/i386/boot/Makefile as
i
On Tue, 26 Sep 2000, Balazs Wellisch wrote:
>Date: Tue, 26 Sep 2000 18:04:17 -0700
>From: Balazs Wellisch <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Cc: Red Hat Development List <[EMAIL PROTECTED]>
>Content-Type: text/plain;
> charset="iso-8859-1"
>Subject: kernel modules
>
>Can anyone tel
On Wed, 27 Sep 2000, Dave Ihnat wrote:
> On Wed, Sep 27, 2000 at 03:32:03PM +0300, Panu Matilainen wrote:
> > It'll stop the complaining for the most part but might also break your
> > kernel in interesting ways :)
>
> Explain? To the best of my knowledge, this only has an effect if you may
> ha
On Wed, Sep 27, 2000 at 03:32:03PM +0300, Panu Matilainen wrote:
> It'll stop the complaining for the most part but might also break your
> kernel in interesting ways :)
Explain? To the best of my knowledge, this only has an effect if you may
have modules built for different versions of the kern
On Wed, 27 Sep 2000, Dave Ihnat wrote:
> On Tue Sep 26 2000 at 18:04, "Balazs Wellisch" wrote:
> > Can anyone tell me how to correct the following error:
> >
> > depmod: *** Unresolved symbols in /lib/modules/2.2.16-3/misc/emu10k1.o
> >From the make menuconfig or xconfig, disable
>
> "Set versio
On Tue Sep 26 2000 at 18:04, "Balazs Wellisch" wrote:
> Can anyone tell me how to correct the following error:
>
> depmod: *** Unresolved symbols in /lib/modules/2.2.16-3/misc/emu10k1.o
>From the make menuconfig or xconfig, disable
"Set version information on all symbols for modules".
This sets
On Wed, 27 Sep 2000, Tony Nugent wrote:
> On Tue Sep 26 2000 at 18:04, "Balazs Wellisch" wrote:
>
> > Can anyone tell me how to correct the following error:
> >
> > depmod: *** Unresolved symbols in /lib/modules/2.2.16-3/misc/emu10k1.o
>
> FWIW, I've seen exactly the same error using the stock
On Tue Sep 26 2000 at 18:04, "Balazs Wellisch" wrote:
> Can anyone tell me how to correct the following error:
>
> depmod: *** Unresolved symbols in /lib/modules/2.2.16-3/misc/emu10k1.o
FWIW, I've seen exactly the same error using the stock kernel-sources-*
package to rebuild a new kernel.
The
13 matches
Mail list logo
