Re: 2.0.35 - 6x86L CPU Detection Broken

Jauder Ho (jauderho@transmeta.com)
Sun, 20 Sep 1998 00:52:28 -0700 (PDT)


it's because someone hacked up linux/arch/i386/kernel/setup.c
it ain't that important. if it doesn't work under 2.1, tell me and I'll
take a closer look at it.

--Jauder

On Sat, 19 Sep 1998, Robert Gash wrote:

> I am having problems getting 2.0.35 to see my 6x86L Processor. Since 2.0.34
> has been released, the 6x86L PR166 that I own is always detected as a 486
> processor, however Windows 98 (puke, barf, groan) can see it, and kernels
> that were compiled before I slicked my machine could see the processor fine
> (these were pre-2.0.34 with a 6x86L patch installed). Does anyone have a
> suggested fix for this? The system is Debian 2.0, installed a few days ago.
> I have included the output from a few commands to help anyone interested.
>
> cat /proc/cpuinfo
> processor : 0
> cpu : 486
> model : unknown
> vendor_id : unknown
> stepping : unknown
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid : no
> wp : yes
> flags :
> bogomips : 133.53

-
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.tux.org/lkml/