From owner-freebsd-current  Thu Jan 21 21:28:15 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA18759
          for freebsd-current-outgoing; Thu, 21 Jan 1999 21:28:15 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18738
          for <current@FreeBSD.ORG>; Thu, 21 Jan 1999 21:28:12 -0800 (PST)
          (envelope-from peter.jeremy@auss2.alcatel.com.au)
Received: by border.alcanet.com.au id <40356>; Fri, 22 Jan 1999 14:44:56 +1100
Date: Fri, 22 Jan 1999 14:45:33 +1100
From: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
Subject: Re: Problem loading 2.x kernel with new bootblocks
To: mike@smith.net.au
Cc: current@FreeBSD.ORG
Message-Id: <99Jan22.144456est.40356@border.alcanet.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Mike Smith <mike@smith.net.au> wrote:
>> The kernel has been built with gcc-2.8.1 -O2.
>
>Please rebuild with the system compiler and -O at most.

It makes no difference.  The kernel loads and runs happily from the
old bootloader, but crashes with /boot/loader.  (I disabled my
gcc-2.8.1, changed make.conf to -O, re-ran config; make depend; make;
make install).

Something that `fell off' my previous posting (it was implied in the
context of my original posting):

Both disks have Booteasy installed.  wd0 has the old bootblocks
(from 2.2.6-RELEASE) and FreeBSD 2.x installed on slice 2.  wd2
has the new bootblocks and 3.0-current built from CTM 'cvs-cur 4996'
occupying all of slice 1 (which is all of the disk).

The boot sequences are:
disk0 booteasy offers: W95, FreeBSD, Disk1:
- select FreeBSD and 2.x boots successfully
- select `disk1' and the disk1 booteasy offers: BSD, disk0

Select BSD and the new /boot/loader comes up.  If I let it continue, I
wind up with the 3.0 (customised, ELF) kernel booting successfully.

If I abort /boot/loader's autostart (giving me a prompt), then (as per
Peter Wemm's elfday tutorial) issue the commands:
  set currdev=disk1s2a
  load /kernel
  boot -s
the system displays garbage on the screen and doesn't respond to anything
gentler than the reset button.

If I load the GENERIC 2.2.6-RELEASE kernel, ("load /kernel.GENERIC" above)
then it works.

Any suggestions as to my next step?

Peter

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message