7:52 p.m.
Recently I've been trying to compile KQemu so I can get decent speed running
Qemu (for those who want to know why, my stupid college requires Visual
Studio and I don't really want to waste a whole partition keeping Windows
around). However, when I compile it, I get an error stating that the format
of the kernel module is not compatible with the kernel. WTF?
--
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
8:08 p.m.
Kelly wrote:
Recently I've been trying to compile KQemu so I can get decent
speed running
Qemu (for those who want to know why, my stupid college requires Visual
Studio and I don't really want to waste a whole partition keeping Windows
around). However, when I compile it, I get an error stating that the format
of the kernel module is not compatible with the kernel. WTF?
I don't know anything about your build problem, but is your hardware
capable of HVM? You could use qemu-kvm instead of kqemu.
Warren Togami
wtogami(a)redhat.com
9:01 p.m.
On Saturday, May 05, 2007 9:08 pm Warren Togami wrote:
Kelly wrote:
> Recently I've been trying to compile KQemu so I can get decent speed
> running Qemu (for those who want to know why, my stupid college requires
> Visual Studio and I don't really want to waste a whole partition keeping
> Windows around). However, when I compile it, I get an error stating that
> the format of the kernel module is not compatible with the kernel. WTF?
I don't know anything about your build problem, but is your hardware
capable of HVM? You could use qemu-kvm instead of kqemu.
Warren Togami
wtogami(a)redhat.com
Probably not; it's an AMD Mobile Sempron.
--
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
10:16 p.m.
Kelly wrote:
> Recently I've been trying to compile KQemu so I can get
decent speed
> running Qemu (for those who want to know why, my stupid college requires
> Visual Studio and I don't really want to waste a whole partition keeping
> Windows around). However, when I compile it, I get an error stating that
> the format of the kernel module is not compatible with the kernel. WTF?
BTW, I noticed that I'm also getting these errors from ndiswrapper, most of
the ALSA sound drivers, and just about every driver that doesn't come with
the Fedora default setup.
--
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
11:07 p.m.
On Sat, 2007-05-05 at 23:16 -0400, Kelly wrote:
Kelly wrote:
BTW, I noticed that I'm also getting these errors from ndiswrapper, most of
the ALSA sound drivers, and just about every driver that doesn't come with
the Fedora default setup.
Have you verified that the modules are building against the sources for
the kernel that you're running, and not against something else (Check
the terminal output of make)? I'm betting that this isn't some error
within Fedora, namely since I've never heard of this issue previously,
but if it turns out that kernel-devel has been updated incorrectly for
your architecture, that would be good to check.
-Sean Stangl
12:22 a.m.
On Sunday, May 06, 2007 12:07 am Sean Stangl wrote:
On Sat, 2007-05-05 at 23:16 -0400, Kelly wrote:
> Kelly wrote:
> BTW, I noticed that I'm also getting these errors from ndiswrapper, most
> of the ALSA sound drivers, and just about every driver that doesn't come
> with the Fedora default setup.
Have you verified that the modules are building against the sources for
the kernel that you're running, and not against something else (Check
the terminal output of make)? I'm betting that this isn't some error
within Fedora, namely since I've never heard of this issue previously,
but if it turns out that kernel-devel has been updated incorrectly for
your architecture, that would be good to check.
-Sean Stangl
In this case, not only am I getting the errors from modules I built, but also
modules I've downloaded through ATRPMS and modules automated through DKMS.
When I first started getting the errors, I went and double-checked that the
version & arch numbers were the same, so that's not the problem.
--
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
6:33 a.m.
On Sun, May 06, 2007 at 01:22:14AM -0400, Kelly wrote:
On Sunday, May 06, 2007 12:07 am Sean Stangl wrote:
> On Sat, 2007-05-05 at 23:16 -0400, Kelly wrote:
> > Kelly wrote:
> > BTW, I noticed that I'm also getting these errors from ndiswrapper, most
> > of the ALSA sound drivers, and just about every driver that doesn't come
> > with the Fedora default setup.
>
> Have you verified that the modules are building against the sources for
> the kernel that you're running, and not against something else (Check
> the terminal output of make)? I'm betting that this isn't some error
> within Fedora, namely since I've never heard of this issue previously,
> but if it turns out that kernel-devel has been updated incorrectly for
> your architecture, that would be good to check.
>
> -Sean Stangl
In this case, not only am I getting the errors from modules I built, but also
modules I've downloaded through ATRPMS and modules automated through DKMS.
How do these errors look like? Maybe i586 vs i686 mismatches? Please
post the exact output of the errors.
When I first started getting the errors, I went and double-checked
that the
version & arch numbers were the same, so that's not the problem.
The only case known to me when ATrpms' modules are involved is the
i586/i686 mismatch explained here:
http://fedoraproject.org/wiki/Bugs/FC6Common#head-e0676100ebd965b92fbaa71...
--
Axel.Thimm at ATrpms.net
1:53 p.m.
Il giorno dom, 06/05/2007 alle 13.33 +0200, Axel Thimm ha scritto:
How do these errors look like? Maybe i586 vs i686 mismatches? Please
post the exact output of the errors.
Hello,
I don't know if it helps, but I had problems with few drivers as well,
for example compiling the alsa drivers and the vmware modules with the
first 2.6.20 kernel update on FC6.
The error for the alsa drivers was something like this:
error: implicit declaration of function 'is_power_of_2'
I've solved patching the drivers. In the case of vmware, I installed new
vmware-any-any.
The alsa drivers were downloaded by the personal page of Martin
Stransky, so I think they are at least a bit tested and should work, but
in my case I was not able to compile them. Maybe you have this same
problem (but other than try to patch the single packages I don't know
what else to tell, because I don't know if they were caused by some
version mismatches or what)?
Mario
--
Lima Software - http://www.limasoftware.net/
GNU Classpath Developer - http://www.classpath.org/
Jabber: neugens(a)jabber.org - Profile: http://www.gtalkprofile.com/profile/9661.html
pgp key: http://subkeys.pgp.net/
PGP Key ID: 80F240CF
Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF
Please, support open standards:
http://opendocumentfellowship.org/petition/
http://www.nosoftwarepatents.com/
2:41 p.m.
On Sunday, May 06, 2007 7:33 am Axel Thimm wrote:
How do these errors look like? Maybe i586 vs i686 mismatches? Please
post the exact output of the errors.
As I said, that's pretty much the first thing I checked.
I've switched from the latest kernel (*48) to the previous kernel (*44) and
now everything appears to be working.
--
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
6209
days inactive
6209
days old
8 comments
5 participants
participants (5)
-
Axel Thimm -
Kelly Miller -
Mario Torre -
Sean Stangl -
Warren Togami