From owner-freebsd-questions Fri May 28 0:36: 8 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mongoose.slip.net (mongoose.slip.net [207.171.193.14]) by hub.freebsd.org (Postfix) with ESMTP id A3FC214D86 for ; Fri, 28 May 1999 00:36:06 -0700 (PDT) (envelope-from leonard@ssl.berkeley.edu) Received: from [209.152.177.103] (helo=zeus) by mongoose.slip.net with smtp (Exim 2.12 #4) id 10nHBU-0000bY-00 for questions@freebsd.org; Fri, 28 May 1999 00:36:05 -0700 Message-Id: <4.1.19990528002950.00b3ac90@yikes.com> X-Sender: leonard@yikes.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 28 May 1999 00:36:37 -0700 To: questions@freebsd.org From: Leonard Chung Subject: Does FreeBSD no longer work with 386's? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I'm currently running 2.2.7 on an old 386 with 8 megs of non-parity RAM and two NE2000 ethernet cards. The system is primarily used just to run natd for computers on the internal network to talk to ones on the external net. I wanted to upgrade the system to 3.2, but unfortunately I can't even boot off the boot disk. Right after the loader has shown the symbol info and just before it would normally ask for the MFS disk, it craps out with a constant beep and the following dump (leading zeros have been stripped): [sic]... +0x24acd] int=d err=13 efl=30246 eip=37e7 eax=3c03 ebx=7 ecx=fffe edx=0 esi=3739 edi=0 ebp=3f8 esp=366 cs=c000 ds=40 es=3773 fs=0 gs=0 ss=9e65 cs: eip=e2 fe 8a c4 e6 61 c3 a0-4a 00 fe c8 8a 26 84 00 ss: esp=f9 19 73 37 00 00 15 d2-00 00 00 00 07 00 17 As I've said, the computer has been extremely bulletproof with 2.2.7 (over 222 days uptime! :-), but won't boot off the install disks at all with 3.2. Any ideas? Leonard -- Leonard Chung - SETI@home - The Search for Extraterrestrial Intelligence @ home http://www.setiathome.ssl.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message