From owner-freebsd-questions Fri Oct 24 20:03:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA07916 for questions-outgoing; Fri, 24 Oct 1997 20:03:00 -0700 (PDT) (envelope-from owner-freebsd-questions) Received: from ns2.cetlink.net (root@ns2.cetlink.net [209.54.54.20]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA07908 for ; Fri, 24 Oct 1997 20:02:57 -0700 (PDT) (envelope-from jak@cetlink.net) Received: from ts1-cltnc-19-s08.cetlink.net (ts1-cltnc-19-s08.cetlink.net [209.54.58.19]) by ns2.cetlink.net (8.8.5/8.8.5) with SMTP id XAA03903 for ; Fri, 24 Oct 1997 23:02:49 -0400 (EDT) From: jak@cetlink.net (John Kelly) To: freebsd-questions@FreeBSD.ORG Subject: Re: 48 meg double fault moved to 64 meg in 2.2.5 Date: Fri, 24 Oct 1997 22:44:00 -0400 Message-ID: In-Reply-To: Lines: 27 Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk jack wrote: >> Looks like the 48M boot floppy bug has crawled to a different location. > >I've booted from the 2.2.5 boot floppy on two different 64M boxes, and a >20M, so far. No problems. ?????? I have two machines with identical hardware configurations. Intel 486DX4-100, VLB motherboard with UMC chipset, Buslogic 445C SCSI controller, 64 MB RAM. The problem appears on both machines. I also have a test machine, another VLB 486 with 64 MB RAM, but a VIA chipset and no SCSI -- No problem on this machine. So it seems the problem is specific to certain hardware. I have extra parts to build a third machine identical to the configuration which shows the problem. In the next few days I'll try to build one piece by piece until the problem starts. If the problem starts with the motherboard itself I'll poke around with the CMOS settings to see if they have any effect. John