From owner-freebsd-questions  Mon Oct 13 00:15:10 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id AAA25530
          for questions-outgoing; Mon, 13 Oct 1997 00:15:10 -0700 (PDT)
          (envelope-from owner-freebsd-questions)
Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA25519
          for <freebsd-questions@FreeBSD.ORG>; Mon, 13 Oct 1997 00:15:06 -0700 (PDT)
          (envelope-from dwhite@gdi.uoregon.edu)
Received: from localhost (dwhite@localhost)
          by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id AAA10495;
          Mon, 13 Oct 1997 00:14:57 -0700 (PDT)
Date: Mon, 13 Oct 1997 00:14:57 -0700 (PDT)
From: Doug White <dwhite@gdi.uoregon.edu>
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: Gaetan Feige <Gaetan@vsg.mobistar.be>
cc: freebsd-questions@FreeBSD.ORG
Subject: Re: Pb installing 2.2 Release on a Pentium Pro Natoma chipset  revision 2 mother board.
In-Reply-To: <3.0.32.19971005231916.007ad5e0@195.61.128.100>
Message-ID: <Pine.BSF.3.96.971013001402.9609j-100000@gdi.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Sun, 5 Oct 1997, Gaetan Feige wrote:

> I have already installed multiple times FreeBSD on many machines.
> 
> I just got a Pentium Pro processor on a Natoma motherboard chipset. It is
> impossible to install the 2.2 Release on this machine.
> 
> I also have an old Pentium 66 processor, if I switch all my cards, hard
> drives, and memory to the old machine then the install goes fine.
> 
> The problem is that I systematically get this message :
> 
> 	Unable to link /kernel into place
> 
> If I open the debuging window I see :
> 
> 	....normal stuff
> 	man/man1/Xmseconfig.1.gz
> 	100 blocks
> 	pid 124 (sh), uid 0 : exited on signal 4 (core dumped)
> 	illegal instruction - core dumped
> 
> What does the install script do that could cause an illegal instruction &
> core dump ?

Wierd.  Never seen that.  I suppose you could drop to the Emergency
Holographic Shell (alt-F4) and ``cp /kernel.GENERIC /kernel''.  I'd have
to look at this in progress so see what the shell script does.

You might check the memory out in this machine.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major