*BSD News Article 4167


Return to BSD News archive

Path: sserve!manuel!munnari.oz.au!uunet!mcsun!uknet!cf-cm!news
From: spedpr@thor.cf.ac.uk (Paul Richards)
Newsgroups: comp.unix.bsd
Subject: 386bsd-0.1 disklabel
Keywords: 386BSD
Message-ID: <6443.9208262143@thor.cf.ac.uk>
Date: 26 Aug 92 21:43:30 GMT
References: <ache.714840717@cpuv1>
Sender: news@cm.cf.ac.uk (Network News System)
Organization: University of Wales College at Cardiff
Lines: 33
X-Mailer: Cardiff Computing Maths PP Mail Open News Gateway

I think the 0.1 disklabel is causing problems with some machines, it is
with mine.

I totally failed to get the 0.1 dist to boot from my hard disk. I'd get
the spinning a: drive phenomenon. When I went back to 0.0 and used the
disklabel from that it worked fine. I suspect that the boot code has
changed. My disklabel is the same and using the 0.0 boot code it still
runs the 0.1 kernel but using the 0.1 boot code it doesn't. It seems
that the 0.1 code isn't finding the kernel or that it isn't being
installed properly on the disk. I think the latter, the result being
that no boot code is found on the hard disk and the bios tries the a:
drive instead. I'm only guessing though. Any ideas??

Anyway, as a solution to those that can get the floppy to boot and then
find that when its copied to the hard disk it doesn't boot: get a copy
of the 0.0 disklabel and use that.

Procedure:
1) disklabel the disk using disklabel 0.0
2) reboot using 0.1 fixit.fs
3) newfs the partion (or partitions) (DON'T re-disklabel the disk)
4) follow instructions as given previously for manual installation

The fact that the above procedure works is what makes me suspect that
bootwd is the culprit. (Oh yes it's bootwd and wdboot I'm using since my
drives a seagate st1144a ide)

-- 
  Paul Richards at Cardiff university, UK.

  spedpr@uk.ac.cf.thor	Internet: spedpr%thor.cf.ac.uk@nsfnet-relay.ac.uk
  UUCP:     spedpr@cf-thor.UUCP or ...!uunet!mcsun!uknet!cf!thor!spedpr
+++