From: Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Unknown symbol __PAGE_KERNEL_EXEC
Date: Tue, 26 Jul 2005 16:28:53 +1200 [thread overview]
Message-ID: <1122352134.13708.4.camel@unixadmindazfc2.chh.co.nz> (raw)
Hi All, Fabrice,
Compiling the new kqemu-0.7.1 on Fedora Core 4 with kernel
2.6.12-1.1398_FC4 gives this error:
-------------8<-------------------
[dixond@unixadmindazfc2 kqemu]$ make
make -C /lib/modules/2.6.12-1.1398_FC4/build M=`pwd` modules
make[1]: Entering directory `/usr/src/kernels/2.6.12-1.1398_FC4-i686'
CC [M] /opt/src/qemu-0.7.1/kqemu/kqemu-linux.o
cp /opt/src/qemu-0.7.1/kqemu/kqemu-mod-i386.o /opt/src/qemu-0.7.1/kqemu/kqemu-mod.o
LD [M] /opt/src/qemu-0.7.1/kqemu/kqemu.o
Building modules, stage 2.
MODPOST
Warning: could not find /opt/src/qemu-0.7.1/kqemu/.kqemu-mod.o.cmd
for /opt/src/qemu-0.7.1/kqemu/kqemu-mod.o
*** Warning: "__PAGE_KERNEL_EXEC" [/opt/src/qemu-0.7.1/kqemu/kqemu.ko]
undefined!
CC /opt/src/qemu-0.7.1/kqemu/kqemu.mod.o
LD [M] /opt/src/qemu-0.7.1/kqemu/kqemu.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.12-1.1398_FC4-i686'
-------------8<-------------------
And then the module fails to modrobe successfully:
-------------8<-------------------
[root@unixadmindazfc2 qemu-0.7.1]# /sbin/modprobe kqemu
FATAL: Error inserting kqemu
(/lib/modules/2.6.12-1.1398_FC4/misc/kqemu.ko): Unknown symbol in
module, or unknown parameter (see dmesg)
[root@unixadmindazfc2 qemu-0.7.1]# dmesg|tail -1
kqemu: Unknown symbol __PAGE_KERNEL_EXEC
-------------8<-------------------
Please CC me on any replies as I am no longer subscribed to the list.
Cheers,
--
Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
next reply other threads:[~2005-07-26 5:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 4:28 Darryl Dixon [this message]
2005-07-26 5:56 ` [Qemu-devel] Unknown symbol __PAGE_KERNEL_EXEC Pascal Terjan
2005-07-26 6:06 ` Pascal Terjan
2005-07-26 11:10 ` Darryl Dixon
2005-07-26 15:53 ` Sebastian Kaliszewski
2005-07-26 21:34 ` Fabrice Bellard
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=1122352134.13708.4.camel@unixadmindazfc2.chh.co.nz \
--to=esrever_otua@pythonhacker.is-a-geek.net \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).