Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!mips!mips!zaphod.mps.ohio-state.edu!caen!destroyer!news.iastate.edu!tbird.cc.iastate.edu!explorer From: explorer@iastate.edu (Michael Graff) Subject: Re: (new, unofficial) patched bootables on agate... Message-ID: <explorer.711907649@tbird.cc.iastate.edu> Keywords: 386bsd, 0.1, patched, boot floppy, dist.fs, fixit.fs Sender: news@news.iastate.edu (USENET News System) Organization: Iowa State University, Ames IA References: <14ljgrINNka3@agate.berkeley.edu> Date: Thu, 23 Jul 1992 16:07:29 GMT Lines: 31 In <14ljgrINNka3@agate.berkeley.edu> cgd@agate.berkeley.edu (Chris G. Demetriou) writes: >I've put some new patched boot floppies in >agate.berkeley.edu:~ftp/pub/386BSD/386bsd-0.1/unofficial/newbootables.cgd >They have the fix for the wd boot block, the fix for the wd driver, >and there are various combinations of ones having no >Isolink driver in the kernel, no "we" driver in the kernel, and >ones having debugging bootstraps installed... Ok, I got the new binaries (I've tried dist.fs-noIS.debug, dist.fs-noIS, and dist.fs) and now my Z-386/25 boots... And boots... And boots... I get some sort of panic right after the floppy found message, and have NO idea what the rest says, other than a "trap 12" or something like that... the blasted thing clears the screen too quickly! This is the same problem I had on my PC at home (386 clone) and only seemed to appear when I use a partition rather than the entire disk for 386. It seems that 386BSD might not quite have the partition thing down yet... Thanks to Chris for providing that kernel! Now I can compile at home, and I'm getting closer on the Z-386! -- -- Michael Graff Iowa State University Computation Center Project Vincent 215 Durham voice: (515) 294-4994 explorer@iastate.edu Ames, IA 50010 fax: (515) 294-1717 gg.mlg@isumvs.bitnet