[Buildroot] Building For 486

[Buildroot] Building For 486

[Ted Wood]

I'm trying to use Buildroot to build an image for a Vortex 6326D SBC with a
486 processor.

 

Even if I set the processor options to 486 using  menuconfig, when I try to
run it, the built kernel comes up with the message 

 

"This kernel requires an i586 CPU, but only detected an i486 CPU. Unable to
boot please use a kernel appropriate for your CPU"

 

Is it that the Linux kernel simply does not support 486 processors after a
certain version?

 

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130103/41f293a6/attachment.html>

[Buildroot] Building For 486

[Richard Braun]

On Thu, Jan 03, 2013 at 04:14:59PM -0000, Ted Wood wrote:
> Even if I set the processor options to 486 using  menuconfig, when I try to
> run it, the built kernel comes up with the message 

Just in case: use make linux-menuconfig and make sure the *kernel*
configuration (in addition to the buildroot configuration) matches the
target hardware.

-- 
Richard Braun

[Buildroot] Building For 486

[Ted Wood]

Kernel Config is i386

[Buildroot] Building For 486

[Will Moore]

Hi Ted,

> -----Original Message-----
> From: buildroot-bounces at busybox.net [mailto:buildroot-bounces at busybox.net] On
> Behalf Of Ted Wood
> Sent: 03 January 2013 16:15
> 
> I'm trying to use Buildroot to build an image for a Vortex 6326D SBC with a
> 486 processor.
> 

It is DM&P vortex86dx on the 6326D, I am using the same processor on a ICOP
VDX-6354D using buildroot.  I am sure you already know this is not an i486 but a
SoC that is *something* like a i486...
 
> 
> Even if I set the processor options to 486 using  menuconfig, when I try to
> run it, the built kernel comes up with the message
> 

You need to ensure you use "an appropriate" kernel configuration for the
vortex86dx and correctly configure buildroot to build the kernel with it, let me
know if this makes no sense and you need more details...

IMHO a good starting place is the 2.6.29.6 kernel config provided by DM&P in
their X-Linux distribution.  I say a good starting place as I have had no end of
problems moving to more recent kernels.  (OT: I have had no end of problems with
this CPU full-stop, I have a deep seated suspicion that the FPU is "broken" or
at least both Linux and QNX kernels don't like it much, I run with it turned off
and use the Linux FPE. YMMV).

> 
> "This kernel requires an i586 CPU, but only detected an i486 CPU. Unable to
> boot please use a kernel appropriate for your CPU"
> 
> Is it that the Linux kernel simply does not support 486 processors after a
> certain version?

Nope, you can run Linux on a vortex86dx, you can run it on a vortex86sx too.
 
HTH,


Will

> 
> 
> 
> 
> 
> 
> 
> 

[Buildroot] Building For 486

[Gustavo Zacarias]

On 01/03/2013 01:59 PM, Will Moore wrote:
> You need to ensure you use "an appropriate" kernel configuration for the
> vortex86dx and correctly configure buildroot to build the kernel with it, let me
> know if this makes no sense and you need more details...
> 
> IMHO a good starting place is the 2.6.29.6 kernel config provided by DM&P in
> their X-Linux distribution.  I say a good starting place as I have had no end of
> problems moving to more recent kernels.  (OT: I have had no end of problems with
> this CPU full-stop, I have a deep seated suspicion that the FPU is "broken" or
> at least both Linux and QNX kernels don't like it much, I run with it turned off
> and use the Linux FPE. YMMV).

I've got one of those "nice" ebox2300 boxes that use the original
Vortex86 (AKA SiS 550).
They're something like a 486-586 depending on how you look at it.
I don't know how much they carried over to the newer SX/DX/MX variants
but i vividly remember that the linux kernel configuration must be
almost perfect to boot on these.
I also recall that some kernel versions flat out don't like them, so
trying is the best option until you find a suitable one.
If you're interested i might be able to dig a kernel .config, but
remember it's a different beast from the newer variants and it might not
help at all.
Regards.