From owner-freebsd-hackers Wed Oct 4 16:38:45 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA08770 for hackers-outgoing; Wed, 4 Oct 1995 16:38:45 -0700 Received: from trepan.io.org (taob@trepan.io.org [198.133.36.8]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA08764 for ; Wed, 4 Oct 1995 16:38:41 -0700 Received: (from taob@localhost) by trepan.io.org (8.6.9/8.6.9) id TAA02180; Wed, 4 Oct 1995 19:38:29 -0400 Date: Wed, 4 Oct 1995 19:38:28 -0400 (EDT) From: Brian Tao To: David Greenman cc: FreeBSD hackers Subject: Flaky reboot problem with this SP3G board In-Reply-To: <199510040436.VAA00321@corbin.Root.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG Precedence: bulk On Tue, 3 Oct 1995, David Greenman wrote: > > Try just pressing "Enter". The machine actually does a 'halt', not a > reboot, and it needs a before it will reboot. I don't think virtual > console switching works at this stage, either, which explains why the machine > appears dead. I hit Enter at first, then spacebar, then I tried the switch virtual consoles, etc. But after some more fiddling last night, I think it just might be the hardware itself. The machine was rebooted five times after I did the installation last night. Twice it hung as I described, twice it rebooted itself properly and once it cleared the screen (as if to reboot) and then stayed there. After hitting the hardware reset, I get a message saying the CMOS checksums don't match (or something) and that it was reloading the factory defaults. Is this a bad BIOS revision problem, or bad memory, or what? -- Brian Tao System Administrator, Internex Online Inc. "Though this be madness, yet there is method in't"