From: "tgelter" <tgelter@gurulabs.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: <email.ahmedkamal@googlemail.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: Problems building btrfs
Date: Fri, 18 Jul 2008 12:51:03 -0600 [thread overview]
Message-ID: <f70cef3dd5bd52cbf48509a8d3ab1ad9@gurulabs.com> (raw)
In-Reply-To: <1216405254.6932.41.camel@think.oraclecorp.com>
On 12:20 pm 07/18/08 Chris Mason <chris.mason@oracle.com> wrote:
> On Fri, 2008-07-18 at 10:36 -0600, Tim Gelter wrote:
>
> > Hello all,
> > I've been silently following the development of btrfs for a while
> > now. After checking out and building the kernel module, I am
> > unable to insmod it. It complains that it's not of a valid type.
> > Any ideas? -Tim
> >
>
> Hello,
>
> Could you please cut n' paste the error messages, as well as anything
> from the kernel dmesg.
>
> -chris
[tgelter@guapFed kernel]$ uname -r
2.6.25.10-86.fc9.x86_64
[tgelter@guapFed kernel]$ make
make -C /lib/modules/`uname -r`/build M=`pwd` modules
make[1]: Entering directory `/usr/src/kernels/2.6.25.10-86.fc9.x86_64'
Building modules, stage 2.
MODPOST 1 modules
make[1]: Leaving directory `/usr/src/kernels/2.6.25.10-86.fc9.x86_64'
[tgelter@guapFed kernel]$ su -
Password or swipe finger:
[root@guapFed ~]# cd /home/tgelter/btrfs/kernel/
[root@guapFed kernel]# modprobe libcrc32c
[root@guapFed kernel]# lsmod | grep libcrc32c
libcrc32c 11008 0
[root@guapFed kernel]# insmod btrfs.ko
insmod: error inserting 'btrfs.ko': -1 Invalid module format
[root@guapFed kernel]#
[root@guapFed kernel]# dmesg
---snip---
btrfs: version magic '2.6.25.10-86.fc9.x86_64stripped SMP mod_unload '
should be '2.6.25.10-86.fc9.x86_64 SMP mod_unload '
---snip---
Looks like I've got some residue of a custom kernel compile I was trying
before cached somewhere. I haven't the foggiest idea how to get things
straightened out...looks like I'll be hitting up freenode's #fedora for
help.
prev parent reply other threads:[~2008-07-18 18:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3da3b5b40807160139w4b8e3474te113980d0086ba9c@mail.gmail.com>
2008-07-16 9:06 ` QA suite plans Ahmed Kamal
2008-07-16 12:05 ` Josef Bacik
2008-07-16 13:22 ` Ahmed Kamal
2008-07-17 14:25 ` Miguel Sousa Filipe
2008-07-18 16:30 ` Ahmed Kamal
2008-07-18 16:36 ` Tim Gelter
2008-07-18 18:20 ` Problems building btrfs Chris Mason
2008-07-18 18:51 ` tgelter [this message]
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=f70cef3dd5bd52cbf48509a8d3ab1ad9@gurulabs.com \
--to=tgelter@gurulabs.com \
--cc=chris.mason@oracle.com \
--cc=email.ahmedkamal@googlemail.com \
--cc=linux-btrfs@vger.kernel.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