From owner-freebsd-questions Sun Mar 10 05:38:54 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA27501 for questions-outgoing; Sun, 10 Mar 1996 05:38:54 -0800 (PST) Received: from arl-gw-6.compuserve.com (arl-gw-6.compuserve.com [198.4.6.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA27490 for ; Sun, 10 Mar 1996 05:38:51 -0800 (PST) Received: from cod.connix.com by arl-gw-6.compuserve.com (8.6.10/5.941228sam) id IAA11272; Sun, 10 Mar 1996 08:36:57 -0500 Date: Sun, 10 Mar 1996 08:36:57 -0500 Message-Id: <199603101336.IAA11272@arl-gw-6.compuserve.com> X-Sender: cod@connix.com (Unverified) X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: freebsd-questions@freebsd.org From: "C. O'Donnell" Subject: 386 won't boot from 2.1 boot.flp Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am trying to upgrade a 386DX-33 w/387, 4 Mb ram, IDE drive to 2.1 A kernel compiled on another machine and copied over will boot without problem, but a dd'ed boot.flp disk yields the message attached below. 1) Can I disable something to allow this to boot? 2) Not enough ram? 3) Since I can get a compiled kernel to boot, is there some other way to upgrade 2.0.5 -> 2.1 from an NFS:/cdrom without the using the boot.flp? Please respond directly as I am not on the questions mailing list. Thanks, Chuck Attachment: ----------------------------------------------------------------- . . . rootfs is 1000 Kbyte compiled in MFS Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xf018c82d code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL=0 current process = 1 swapper interrupt mask = net tty bio panic: page fault . . .