linux-kernel - Re: Upgrading kernel across multiple machines

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20060809150737.7a0c99ee.rdunlap@xenotime.net>
Date:	Wed, 9 Aug 2006 15:07:37 -0700
From:	"Randy.Dunlap" <rdunlap@...otime.net>
To:	Brian McGrew <brian@...ionpro.com>
Cc:	<linux-kernel@...r.kernel.org>
Subject: Re: Upgrading kernel across multiple machines

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/