Upgrading kernel across multiple machines

Upgrading kernel across multiple machines

[Brian McGrew]

Hello,

I'm using a Dell PE1800 and I've built a new 2.6.16.16 kernel on the machine
that works fine.  However, if I tar up /lib/modules/2.6.16.16 and /boot and
move it onto another Dell PE1800 running the exact same software (FC3/Stock
install) the new kernel doesn't boot.

On machine #1 life is good but moving it to machine #2, I get

/lib/ata_piix.ko: -l unknown symbol in module.

What am I missing?  Someone help please, I'm in a major time crunch!

Thanks!

:b!

-- 
Brian McGrew    { brian@visionpro.com || brian@doubledimenison.com }

> GUACOMOL: Vegetarian Roadkill!

Re: Upgrading kernel across multiple machines

[Sam Ravnborg]

On Wed, Aug 09, 2006 at 02:52:41PM -0700, Brian McGrew wrote:
> Hello,
> 
> I'm using a Dell PE1800 and I've built a new 2.6.16.16 kernel on the machine
> that works fine.  However, if I tar up /lib/modules/2.6.16.16 and /boot and
> move it onto another Dell PE1800 running the exact same software (FC3/Stock
> install) the new kernel doesn't boot.
> 
> On machine #1 life is good but moving it to machine #2, I get
> 
> /lib/ata_piix.ko: -l unknown symbol in module.
Looks like your kernel modules has ended up in /lib somehow.
Cannot see why atm.

	Sam

Re: Upgrading kernel across multiple machines

[Randy.Dunlap]

On Wed, 09 Aug 2006 14:52:41 -0700 Brian McGrew wrote:

> Hello,
> 
> I'm using a Dell PE1800 and I've built a new 2.6.16.16 kernel on the machine
> that works fine.  However, if I tar up /lib/modules/2.6.16.16 and /boot and
> move it onto another Dell PE1800 running the exact same software (FC3/Stock
> install) the new kernel doesn't boot.
> 
> On machine #1 life is good but moving it to machine #2, I get
> 
> /lib/ata_piix.ko: -l unknown symbol in module.
> 
> What am I missing?  Someone help please, I'm in a major time crunch!

Hi again,
Were you able to get any more kernel log messages?
They will say exactly which symbol(s) is missing.

Maybe adding "debug" to the kernel command line would produce more
messages, although many init scripts change that setting (ugh).

---
~Randy

Re: Upgrading kernel across multiple machines

[Brian McGrew]

It would appear that way; but I assure you, the modules are in
/lib/modules/2.6.16.16/

:b!


On 8/9/06 3:03 PM, "Sam Ravnborg" <sam@ravnborg.org> wrote:

> On Wed, Aug 09, 2006 at 02:52:41PM -0700, Brian McGrew wrote:
>> Hello,
>> 
>> I'm using a Dell PE1800 and I've built a new 2.6.16.16 kernel on the machine
>> that works fine.  However, if I tar up /lib/modules/2.6.16.16 and /boot and
>> move it onto another Dell PE1800 running the exact same software (FC3/Stock
>> install) the new kernel doesn't boot.
>> 
>> On machine #1 life is good but moving it to machine #2, I get
>> 
>> /lib/ata_piix.ko: -l unknown symbol in module.
> Looks like your kernel modules has ended up in /lib somehow.
> Cannot see why atm.
> 
> Sam


:b!

-- 
Brian McGrew    { brian@visionpro.com || brian@doubledimenison.com }

> For economy reasons the light at the end of the tunnel has been turned off!

Re: Upgrading kernel across multiple machines

[Brian McGrew]

This is the most debug I get.  I've taken the rhgb and quiet options out of
my grub.conf file and I still only get about ten lines printed before it
blows up.  There are no files updated on disk that I can find.

:b!


On 8/9/06 3:07 PM, "Randy.Dunlap" <rdunlap@xenotime.net> wrote:

> On Wed, 09 Aug 2006 14:52:41 -0700 Brian McGrew wrote:
> 
>> Hello,
>> 
>> I'm using a Dell PE1800 and I've built a new 2.6.16.16 kernel on the machine
>> that works fine.  However, if I tar up /lib/modules/2.6.16.16 and /boot and
>> move it onto another Dell PE1800 running the exact same software (FC3/Stock
>> install) the new kernel doesn't boot.
>> 
>> On machine #1 life is good but moving it to machine #2, I get
>> 
>> /lib/ata_piix.ko: -l unknown symbol in module.
>> 
>> What am I missing?  Someone help please, I'm in a major time crunch!
> 
> Hi again,
> Were you able to get any more kernel log messages?
> They will say exactly which symbol(s) is missing.
> 
> Maybe adding "debug" to the kernel command line would produce more
> messages, although many init scripts change that setting (ugh).
> 
> ---
> ~Randy


:b!


-- 
Brian McGrew    { brian@visionpro.com || brian@doubledimenison.com }

> YOU!!!  Off my planet!

Re: Upgrading kernel across multiple machines

[David Lloyd]

On Wed, 2006-08-09 at 15:08 -0700, Brian McGrew wrote:
> It would appear that way; but I assure you, the modules are in
> /lib/modules/2.6.16.16/

Maybe you forgot to copy over your initrd image?

- DML

RE: Upgrading kernel across multiple machines

[Brian D. McGrew]

I tried copying over the initrd as well as making a new one!

:b!

-----Original Message-----
From: David Lloyd [mailto:dmlloyd@flurg.com] 
Sent: Wednesday, August 09, 2006 3:18 PM
To: Brian D. McGrew
Cc: Sam Ravnborg; linux-kernel@vger.kernel.org
Subject: Re: Upgrading kernel across multiple machines

On Wed, 2006-08-09 at 15:08 -0700, Brian McGrew wrote:
> It would appear that way; but I assure you, the modules are in
> /lib/modules/2.6.16.16/

Maybe you forgot to copy over your initrd image?

- DML

RE: Upgrading kernel across multiple machines

[David Lloyd]

On Wed, 2006-08-09 at 17:18 -0700, Brian D. McGrew wrote:
> I tried copying over the initrd as well as making a new one!

Ok.  The only reason I mention it is that in many cases, necessary boot
modules are stored in /lib on the initrd image.  Failure to load such a
module would show up early in the boot sequence, before "real" init
started up.

- DML

Re: Upgrading kernel across multiple machines

[Brian McGrew]

We got the system working, well, two of the three are working now.

Yesterday I tarred over /lib/modules/2.6.16.16 and /boot/*2.6.16.16*.  This
morning I did a sum on the *2.6.16.16* files in /boot and they did not match
the originals (!?! go figure !?!) so I copied them over so they match and
the machine came right up.

Now we'll see if I can duplicate this on machine #3.

THANKS FOR ALL THE HELP!

:b!


On 8/10/06 6:13 AM, "David Lloyd" <dmlloyd@flurg.com> wrote:

> On Wed, 2006-08-09 at 17:18 -0700, Brian D. McGrew wrote:
>> I tried copying over the initrd as well as making a new one!
> 
> Ok.  The only reason I mention it is that in many cases, necessary boot
> modules are stored in /lib on the initrd image.  Failure to load such a
> module would show up early in the boot sequence, before "real" init
> started up.
> 
> - DML
> 


:b!

-- 
Brian McGrew    { brian@visionpro.com || brian@doubledimenison.com }

> Is he allowed a plea of insanity for a parking ticket?