From owner-freebsd-questions Thu Dec 5 11:47:11 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA27815 for questions-outgoing; Thu, 5 Dec 1996 11:47:11 -0800 (PST) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA27808 for ; Thu, 5 Dec 1996 11:47:09 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.3/8.6.12) with SMTP id LAA08400; Thu, 5 Dec 1996 11:44:33 -0800 (PST) Date: Thu, 5 Dec 1996 11:44:33 -0800 (PST) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: "anthony m. vervoort" cc: questions@freebsd.org Subject: Re: installation problem In-Reply-To: <199612051833.KAA28150@netcom22.netcom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 5 Dec 1996, anthony m. vervoort wrote: > so i'm setting up a freebsd box. i've got a known good boot floppy > for 2.1.5-RELEASE, and a cobbled together system with 8 megs, a > generic IDE card and Quantum drive, a standard monochrome card, > and a NE2000 equivalent ethernet card. > > problem is that every time it boots from the floppy, it gets through > decompressing the kernel and then panics and reboots. i've tried it > with a questionable 386 board with a coprocessor, and now with a known > good 486 board. with the 386, it cleared and rebooted before i could > see an error message. with the 486, it gives me this: > > sor write, page not present > instruction pointer = 0x8;0xf01dda3e > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = nested task, resume, IOPL = 0 > current process = 0 () > interrupt mask = net tty bio > panic: page fault > Automatic reboot in 15 seconds - press a key on the console to abort Can you identify exactly where it panics? What messages are above the panic? And can you resurrect the missing first line? Check your RAM -- make sure they're all matched in size and type. > can anybody tell me what piece of hardware it might be gagging on? > the current cpu is an Intel 486DX2-66; the 386 was an AMD 386DX-33 with > a VLSI 387-33. both systems seem to work fine under DOS. the motherboard > is a SIS chipset with an AMI bios. I don't think it's choking on the SiS, I have a Pentium model and FreeBSD loves it. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major