EFW Support

Support => Installation Support => Topic started by: jeremysavoy on Saturday 06 November 2010, 03:00:24 pm



Title: Installation fails right away, CPU does not support cmov instruction
Post by: jeremysavoy on Saturday 06 November 2010, 03:00:24 pm
Hi, I have an old box with a VIA Sameul-2 C3 processor, which is i686 instruction set compatible except that it is missing the cmov instruction. In the past, I've always installed Linux distro's using either the i386 or i586 kernel and glibc.

When I try to load Endian on this box, I get an immediate error:

Code:
This Kernel requires the following features not present on the CPU:
 cmov

Unable to boot - please use a Kernel appropiated for your CPU

I'm assuming that the installation kernel was compiled for i686, and this is causing the issue as the i686 kernel likely has checks against this processor - although in the RPMS directory on the ISO I do notice that the kernel that gets installed is compiled for i586, this is quite common to have kernels compiled for different instruction sets for the installer vs the installed system.

Is there any way possible to get an i586 or i386 version of the installer kernel, vmlinuz? I am PXE installing Endian and all I need is the kernel itself, and possibly a recompiled initrd.

Do you guys think that there is any way to get this? I can even compile it myself if someone can point me to the source for the installer kernel.


Title: Re: Installation fails right away, CPU does not support cmov instruction
Post by: jeremysavoy on Sunday 07 November 2010, 03:35:42 am
Just confirmed by installing into a VM --- it looks like your installer kernel was built for i686 CPUs, but the running kernel of the installed OS was built for i386 CPUs -- you can verify this by checking the "hardware type" field of "uname -a".

Any chance you can produce and ISO with a installer kernel that is only optimized for i386 instruction set?


Title: Re: Installation fails right away, CPU does not support cmov instruction
Post by: jeremysavoy on Sunday 07 November 2010, 04:02:33 am
Actually the installer kernel and the installed kernel both have the same md5 sum ... which does not support my theory.

Any one else have any ideas or suggestions ?