Re: 2.1.115 and Cyrix detection

Fuzzy Fox (fox@dallas.net)
Thu, 20 Aug 1998 00:24:27 -0500


Scott Wood <master@demonswrath.dyn.ml.org> wrote:
>
> > I have a Cyrix 6x86MX PR200+, though I have to clock it down to about
> > 180 MHz in order for the system to remain stable (still working on that
> > one).
>
> You've been overclocking your chip; it's rated speed is 166MHz. The 200
> is just a performance rating.

A few people have pointed this out to me. My description above was
deliberately simplistic, because the issue has nothing to do with my
question, which is about CPU Detection. I will not bore the list with
my system problems; suffice to say that I'm running my bus clock at 60
MHz instead of the proper 66 MHz, which is definitely underclocking the
chip. That's the reason for my low bogomips rating. I do not feel that
this should cause the chip to appear to be a 486 at all.

Rafael Reilova <rreilova@ececs.uc.edu> wrote:
>
> First of all, what chip do you have?

As I posted previously, my chip appears to be an M2. Here's the
/proc/cpuinfo that the 2.0 "jumbo" patch gives me:

processor : 0
cpu family : 6
model : M2 2.5x Core/Bus Clock
vendor_id : CyrixInstead
stepping : 0 rev 3
fdiv_bug : no
hlt_bug : no
sep_bug : no
f00f_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu de tsc msr cx8 cmov mmx
bogomips : 149.91

> The CPU detection code that is in the Jumbo patch is basically the
> same as in post 2.1.109 kernels. [...] The bug seems to be caused by
> an incomplete asm clobber list in the above macro. This is fixed in
> the 2.1.116-2 (Linus rewrote them to use io.h: inb(), outb()).

I have upgraded to 2.1.116, and found no change at all. :(

> The current Cyrix code follows Cyrix's CPU detection algorithm to the
> letter, so I'll be very interested in any misdetections, but please
> report the chip model you have, kernel version, a copy of
> /proc/cpuinfo, and the CPU line in the boot messages ;-)

Is there some way I can report my chip model more clearly? Does the
above info give enough information? My CPU boot message just says
"CPU0: 486", and my /proc/cpuinfo goes right along with it:

processor : 0
cpu family : 4
model : unknown
vendor_id : unknown
stepping : unknown
fdiv_bug : no
hlt_bug : no
sep_bug : no
f00f_bug : no
fpu : yes
fpu_exception : yes
cpuid level : -1
wp : yes
flags :
bogomips : 149.50

It *almost* looks like the CPUID instruction is not working. But why
would it work when booting 2.0, but not 2.1??

-- 
   fox@dallas.net (Fuzzy Fox)      ||   "Her lips said 'No,' but her
sometimes known as David DeSimone  ||    eyes said 'Read my lips!'"
  http://www.dallas.net/~fox/      ||

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html