*BSD News Article 38173


Return to BSD News archive

Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!asstdc.scgt.oz.au!imb
From: imb@asstdc.scgt.oz.au (michael butler)
Subject: Re: 2.0 Alpha Notes
References: <mmitchel.27.2ECCD346@alb.asctmd.com> <3akshr$mot@agate.berkeley.edu>
Organization: Assorted C Software, Sydney
Date: Sun, 20 Nov 1994 12:19:44 GMT
X-Newsreader: TIN [version 1.2 PL2]
Message-ID: <CzKFKx.9pp@asstdc.scgt.oz.au>
Reply-To: imb@scgt.oz.au
Lines: 37

Jordan K. Hubbard (jkh@violet.berkeley.edu) writes:

: In article <mmitchel.27.2ECCD346@alb.asctmd.com>,
: Mike Mitchell <mmitchel@alb.asctmd.com> wrote:

: > 1. I had a real pain in the butt getting the install floppies to work 
: >properly with a freshly formatted SCSI drive. 

I had similar problems with a machine that has an IDE drive (for DOS) and a
SCSI drive for FreeBSD ..

: Sorry, this should be addressed in the BETA floppies.

Strangely, it would boot and install happily off floppy for me but fail to
load properly from the SCSI drive .. the boot block seems to be unhappy ?

Simply whacking a NetBSD boot block and hard-linking 'kernel' to 'netbsd'
avoided it and ran OK .. weird.

However .. I have a worse problem :-( .. the alpha silently hangs after
about 5 or ten minutes of compilation (my first 'stability' test is to get
it to recompile itself). Attempts to switch between virtual consoles are
ignored as is 'ctrl-alt-del' .. reset 'fixes' it.

The machine in question is an AMD 386DX/40 (Opti 495 chipset) with 8 meg of
RAM, 128k cache, IIT 387, Adaptec 1542b and SMC 8013 on a busy ether .. what
gives ? 1.1.5.1 runs fine.

I also noted that, occasionally, 'cc -O2' will fail with either signals 6 or
11. At first I thought that the memoryuse limit may have come into it (and
gcc's optimiser :-)) and gave it 'unlimit' prior to compiling but that
doesn't seem to help. I should add that I saw a similar effect after having
compiled gcc 2.6.1 on FreeBSD 1.1.5.1 but I haven't managed to get 2.6.2
compiled on 2.0-alpha to see if it fixes it as a consequence of the
'hanging' problem above .. any ideas ?

	michael