From owner-freebsd-hackers Sun May 25 19:20:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA22331 for hackers-outgoing; Sun, 25 May 1997 19:20:20 -0700 (PDT) Received: from merix.merix.com (merix.merix.com [198.145.172.40]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA22233 for ; Sun, 25 May 1997 19:20:16 -0700 (PDT) Received: from sandy.merix.com by merix.merix.com with SMTP (1.38.110.45/16.2) id AA068253818; Sun, 25 May 1997 19:30:18 -0700 Received: by sandy.merix.com (4.1/8.0) id AA20834; Sun, 25 May 97 19:16:31 PDT Date: Sun, 25 May 97 19:16:31 PDT Subject: No reboot on HP Vectra XA 166 (MMX) To: freebsd-hackers@freebsd.org From: Troy Curtiss Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I recently installed FreeBSD 2.2.1R (from CD) on my HP Vectra XA 166 MMX machine here at work. Everything works beautifully (and fast, BTW!) except for reboots. From FreeBSD, the machine is impossible to reboot... er... I mean... FreeBSD does its reboot routine, and the screen goes black (and I can't drop down into the kernel debugger or etc..) and stays that way indefinitely. Win95 seems to tickle the right bits, as does Linux. I've played with the BIOS settings dealing with everything, to no avail. I assume FreeBSD is just using the ol' keyboard controller reboot (with a fallback to a triple-fault or something...), so I'm a little baffled. Anybody else out there seen this behavior?? It really sucks when I wedge the machine remotely :( (BTW... the 'wedges' I speak of seem to have the same inode-free but not really problem that Thomas David Rivers speaks of periodically) Thanks, -Troy -- /-----------------------------------------------------------\ | Troy Curtiss, HW/SW Engineer | Email: troyc@merix.com | | Merix Corporation, CL-302 | Phone: (970) 203-6643 | | Loveland, CO 80537 | Fax : (970) 203-6610 | \-----------------------------------------------------------/