Re: 2.0.35+Jumbo9 cpuid still broken for me... (brain oops)

John Caldwell (jcald@lake.ml.org)
Mon, 3 Aug 1998 23:23:17 -0700 (PDT)


On Mon, 3 Aug 1998, John Caldwell wrote:

>
> relevant info:
>
> processor type: 6x86MX-PR200 v2.4
>
>
> Linux groom.lake.ml.org 2.0.35 #3 Mon Jul 27 23:30:59 MST 1998 i486
> unknown
>
> in the config:
> ---
> Processor type: PPro
> (the rest left default)
>
>
> /proc/cpuinfo:
> ---
> processor : 0
> cpu : 486
> model : 486 DX-25/33
> vendor_id : GenuineIntel
> stepping : unknown
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid : no
> wp : yes
> flags :
> bogomips : 166.30
>
>
>
> CPUID has worked in the past, listing it as a CyrixInstead. I forget which
> version of the jumbo patch it worked with. When i compile it and it comes
> out listed as a i686, the system is unstable, and stuff starts getting
> sigsegv after ~24 hours. The bogomips comes out right, since
> its clocked at 166mhz. Any ideas why its calling my machine a 486-33?
>

My paths were a bit fscked up, and it was booting the wrong kernel, one
that I patched with some old stuff. the *CORRECT* kernel boots and lists
it as an i686.... sorry for the false alarm. :\

--
 -------------------------
| John Caldwell
| jcald@lake.ml.org
| http://www.lake.ml.org/
 -------------------------

- 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