Upgrading kernel across multiple machines
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!
Signature · 1 line
Brian McGrew { [email protected] || [email protected] }Quoted 1 line
GUACOMOL: Vegetarian Roadkill!
Quoted 10 lines · 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.16and /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
It would appear that way; but I assure you, the modules are in /lib/modules/2.6.16.16/
:b!
Quoted 8 lines · Sam Ravnborg
Quoted 7 lines · 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.16and /boot and move it onto another Dell PE1800 running the exact same software (FC3/Stock install) the new kernel doesn't boot.
Quoted 7 lines
Quoted 3 lines
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!
Signature · 1 line
Brian McGrew { [email protected] || [email protected] }Quoted 1 line
For economy reasons the light at the end of the tunnel has been turned off!
Quoted 2 lines · Brian McGrew
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
Quoted 7 lines · 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.16and /boot and move it onto another Dell PE1800 running the exact same software (FC3/Stock install) the new kernel doesn't boot.
Quoted 5 lines
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
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!
Quoted 19 lines · Randy.Dunlap
Quoted 7 lines · 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.16and /boot and move it onto another Dell PE1800 running the exact same software (FC3/Stock install) the new kernel doesn't boot.Quoted 5 lines
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.
Quoted 5 lines
Maybe adding "debug" to the kernel command line would produce more messages, although many init scripts change that setting (ugh).
---
~Randy
:b!
Signature · 1 line
Brian McGrew { [email protected] || [email protected] }Quoted 1 line
YOU!!! Off my planet!