From owner-freebsd-hardware  Tue Jun 18 09:50:15 1996
Return-Path: owner-hardware
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id JAA08882
          for hardware-outgoing; Tue, 18 Jun 1996 09:50:15 -0700 (PDT)
Received: from shell.monmouth.com (pechter@shell.monmouth.com [205.164.220.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA08877
          for <freebsd-hardware@freebsd.org>; Tue, 18 Jun 1996 09:50:11 -0700 (PDT)
Received: (from pechter@localhost) by shell.monmouth.com (8.6.12/8.6.12) id MAA27979; Tue, 18 Jun 1996 12:45:02 -0400
From: Bill/Carolyn Pechter <pechter@shell.monmouth.com>
Message-Id: <199606181645.MAA27979@shell.monmouth.com>
Subject: Re: FreeBSD works with Cy486DLC processors?
To: michaelv@HeadCandy.com (Michael L. VanLoon -- HeadCandy.com)
Date: Tue, 18 Jun 1996 12:45:01 -0400 (EDT)
Cc: freebsd-hardware@freebsd.org
In-Reply-To: <199606181558.IAA16170@MindBender.HeadCandy.com> from "Michael L. VanLoon -- HeadCandy.com" at Jun 18, 96 08:58:50 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-hardware@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> 
> >Ooppss!!! You are absolutely right. My CPU is a 486DX4 NOT a 486DLC. The
> >problem was that I was looking at what the kernel gives me at boot time:
> >FreeBSD 2.1.0-RELEASE #2: Mon Jun 17 12:22:05 AST 1996
> >    eparis@skynet.ven.ra.rockwell.com:/usr/src/sys/compile/SKYNET
> >CPU: Cy486DLC (486-class CPU)
> >  Origin = "Cyrix"
> 
> Yeah, that's a bone-headed move on Cyrix' part.  The DLC
> identification code was originally taken out of a piece of code used
> to identify DLC/SLC parts, published in a Cyrix manual.
> 
> Then, the idiots went and made their DX processors respond the same
> way to the same test!
> 
> >The processor has "486DX4" written on top of it. My apologies for causing
> >this confussion.
> 
> >Can it be that the problem is that FreeBSD is mistakenly identifying the
> >processor? Can I force FreeBSD to correctly identify the processor?

Got the same thing on my IBM ThinkPad 365 -- but no stability problems
with 2.0.5 or 2.1.0-RELEASE or  -STABLE -- just went to -CURRENT (well
the 5/1/96 -snap last night...)

Bill