>I ran Slackware 3.4 on an AMD 586 133 which I had O/C'd to 160 for about 18
>months before getting better hardware and upgrading without a problem.
>Never crashed or anything. I recompiled the kernel (2.0.36) as a 486 when I
>included IP forwarding. It sat there doing routing, mail and a minimally
>used web server.
>
>I've still got the MOBO n cpu in a mobo box in my cupboard (got some ram
>for it too somewhere).
Ok, I looked at the AMD site and there is the K5, which is not the one I
had in mind, and the AMD 486, which definitely works. The one I remember
was labelled 586 but was actually a 486. This is probably Cyrix which
got a bad reputation with their early offerings. Unfortunately since
VIA took over Cyrix, they have thrown out all the old docs.
So I looked in the kernel source, and in setup.c I found:
__initfunc(void dodgy_tsc(void))
{
get_cpu_vendor(&boot_cpu_data);
if(boot_cpu_data.x86_vendor != X86_VENDOR_CYRIX)
{
return;
}
cyrix_model(&boot_cpu_data);
}
I'll leave it to the keen to look at the code and decode what it all
means, but it seem to indicate that there is something dodgy about some
of Cyrix's early processors.
--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to [EMAIL PROTECTED] with
unsubscribe in the text
