From: Brian McGrew <brian@visionpro.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Upgrading kernel across multiple machines
Date: Wed, 09 Aug 2006 15:08:48 -0700 [thread overview]
Message-ID: <C0FFAB00.89A2%brian@visionpro.com> (raw)
In-Reply-To: <20060809220309.GA14665@mars.ravnborg.org>
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!
next prev parent reply other threads:[~2006-08-09 22:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 21:52 Upgrading kernel across multiple machines Brian McGrew
2006-08-09 22:03 ` Sam Ravnborg
2006-08-09 22:08 ` Brian McGrew [this message]
2006-08-09 22:18 ` David Lloyd
2006-08-09 22:07 ` Randy.Dunlap
2006-08-09 22:10 ` Brian McGrew
-- strict thread matches above, loose matches on Subject: below --
2006-08-10 0:18 Brian D. McGrew
2006-08-10 13:13 ` David Lloyd
2006-08-10 14:36 ` Brian McGrew
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C0FFAB00.89A2%brian@visionpro.com \
--to=brian@visionpro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox