From owner-freebsd-questions Fri Mar 17 20:11:47 2000 Delivered-To: freebsd-questions@freebsd.org Received: from jander.fl.net.au (jander.fl.net.au [202.181.0.27]) by hub.freebsd.org (Postfix) with ESMTP id A7ECB37B557 for ; Fri, 17 Mar 2000 20:11:42 -0800 (PST) (envelope-from acs@jander.fl.net.au) Received: from localhost (acs@localhost) by jander.fl.net.au (8.9.2/8.8.8) with ESMTP id PAA21750; Sat, 18 Mar 2000 15:11:09 +1100 (EST) (envelope-from acs@jander.fl.net.au) Date: Sat, 18 Mar 2000 15:11:09 +1100 (EST) From: Andrew To: Chip Cc: "seafug@dub.net" , "'freebsd-questions@freebsd.org'" Subject: Re: Install fails with 'signal 11' In-Reply-To: <38D2F0A2.470E37D6@wiegand.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 17 Mar 2000, Chip wrote: > When I try to install fbsd 3.3 I get all the way to the choose a install > method, such as cdrom or ftp etc, and I get a signal 11 error and the > machine reboots by itself. There was a bug in the installer in 3.4 that had this problem if you chose custom install...I dont think it was in 3.3 though...if you are chossing the custom install pick something else instead and see if that works around the problem. You can FTP new disk images from the ftp site if need be. If its not the above try getting brand new floppies and writing out the disk images again...seems to solve 60% of peoples problems. sig11 is oftena n indication of hardware failure (bad RAM or cache etc) but hopefully not in this case. Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message