From owner-freebsd-questions Tue Jun 18 08:59:01 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA05498 for questions-outgoing; Tue, 18 Jun 1996 08:59:01 -0700 (PDT) Received: from portal.spi.net ([199.238.225.153]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA05493; Tue, 18 Jun 1996 08:59:00 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@MindBender.HeadCandy.com [199.238.225.168]) by portal.spi.net (8.6.12/8.6.9) with ESMTP id IAA26638; Tue, 18 Jun 1996 08:58:55 -0700 Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.6.9) with SMTP id IAA16170; Tue, 18 Jun 1996 08:58:53 -0700 (PDT) Message-Id: <199606181558.IAA16170@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "Eloy A. Paris" cc: "M.R.Murphy" , questions@freebsd.org, hardware@freebsd.org Subject: Re: FreeBSD works with Cy486DLC processors? In-reply-to: Your message of Tue, 18 Jun 96 10:30:16 -0400. <2.2.16.19960618104803.1597ca9a@zeus.ven.ra.rockwell.com> Date: Tue, 18 Jun 1996 08:58:50 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-questions@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? Unlikely. That message is just telling you what FreeBSD found. Unless someone has significantly changed the code since the last time I read it, the kernel should just be using the processor the way the BIOS sets it up. Keeping in mind that you have a DX processor, and are seeing those problems, you probably just have a badly designed motherboard, and that CPU might work OK in a better motherboard. Alternatively, you might be overheating the CPU if it's a 100MHz part. Make sure your CPU fan is securly fastened and makes uniform contact across the entire surface of the chip. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. -----------------------------------------------------------------------------