From owner-freebsd-questions Tue Jun 18 07:31:20 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA29293 for questions-outgoing; Tue, 18 Jun 1996 07:31:20 -0700 (PDT) Received: from ns3.mke.ab.com (ns3.mke.ab.com [130.151.86.191]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA29284; Tue, 18 Jun 1996 07:31:15 -0700 (PDT) Received: from by ns3.mke.ab.com (4.1/SMI-4.1) id AB05961; Tue, 18 Jun 96 09:31:01 CDT Received: from pegasus.ven.ra.rockwell.com (pegasus.ven.ra.rockwell.com [130.151.17.156]) by zeus.ven.ra.rockwell.com (8.6.12/8.6.9) with SMTP id KAA23492; Tue, 18 Jun 1996 10:30:16 -0400 Date: Tue, 18 Jun 1996 10:30:16 -0400 Message-Id: <2.2.16.19960618104803.1597ca9a@zeus.ven.ra.rockwell.com> Organization: Rockwell Automation de Venezuela X-Sender: eparis@zeus.ven.ra.rockwell.com X-Mailer: Windows Eudora Pro Version 2.2 (16) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: "M.R.Murphy" From: "Eloy A. Paris" Subject: Re: FreeBSD works with Cy486DLC processors? Cc: questions@freebsd.org, hardware@freebsd.org Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Are you sure it's a 486DLC CPU? I have a system with a Cyrix 486DLC >(running System V R2), and it's a 40MHz part and is not clock-multiplied. >I also have a newer Cyrix486DX2/66 system (which will not run at 33MHz, >but is fine at 25MHz making it in reality a DX2/50). At 33MHz it gets >random odd hardware errors including both hangs and signal 4, 10 and 11. >I'm satisfied with it at 25MHz since it just acts as a PPP connection and >firewall and a DX2/50 is fast enough for that. 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" . . . The processor has "486DX4" written on top of it. My apologies for causing this confussion. >If it works sometimes and not others, then the probability of a hardware >problem is greater. I agree. This has to be a hardware problem, nothing more, nothing less. Can it be that the problem is that FreeBSD is mistakenly identifying the processor? Can I force FreeBSD to correctly identify the processor? Regards, Eloy.- -- Eloy A. Paris Global Technical Services Rockwell Automation de Venezuela Telephone: 58-2-9432311 Fax: 58-2-9430323