From owner-freebsd-stable Tue Jul 23 15:20:49 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C3D5037B400; Tue, 23 Jul 2002 15:20:44 -0700 (PDT) Received: from nova.fnal.gov (nova.fnal.gov [131.225.121.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 163CA43E31; Tue, 23 Jul 2002 15:20:44 -0700 (PDT) (envelope-from zingelman@fnal.gov) Received: from localhost (tez@localhost) by nova.fnal.gov (8.11.6+Sun/8.11.6) with ESMTP id g6NMKgs19892; Tue, 23 Jul 2002 17:20:42 -0500 (CDT) X-Authentication-Warning: nova.fnal.gov: tez owned process doing -bs Date: Tue, 23 Jul 2002 17:20:42 -0500 (CDT) From: Tim Zingelman X-X-Sender: tez@nova.fnal.gov Reply-To: Tim Zingelman To: freebsd-stable@FreeBSD.ORG Cc: re@FreeBSD.ORG, Subject: Re: Installation issues with 4.6.1 RC2 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hans Ottevanger wrote: > Unable to copy /kernel into place. > > On VTY2 the following messages is displayed: > > pid 120 (cp), uid 0: exited on signal 4 (core dumped) > Illegal instruction - core dumped > > Most commands given in the shell on VTY4 (e.g. ls, df, mount, ...) show > the same error message. > > I have a strong feeling that this has to do with the fact that these > systems have an i586 architecture, in contrast with the Celeron that has > an i686 architecture. But of course it could be something completely > different... > > Has anybody else tried the installation on an i586 based system ? Yes. On a pentium 100 I got the same thing with an ftp install after booting from the 4.6.1 RC2 cdrom (the install direct from the cdrom also failed, with different symptoms). Is it possible that 4.6.1 RC2 was somehow built without i586 support? - Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message