Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!dog.ee.lbl.gov!newshub.nosc.mil!crash!fpm
From: fpm@crash.cts.com (Frank MacLachlan)
Subject: Re: [NetBSD 0.9] patch to wd.c for IDE controller weirdnesses
Organization: CTS Network Services (CTSNET/crash), San Diego, CA
Date: 05 Jan 94 07:44:11 PST
Message-ID: <1994Jan05.074411.11109@crash>
References: <2gaogb$7k@explorer.clark.net> <2gc724$plj@explorer.clark.net> <explorer.757753457@tbird.cc.iastate.edu>
Lines: 18
In article <explorer.757753457@tbird.cc.iastate.edu> explorer@iastate.edu (Michael Graff) writes:
[ stuff deleted ]
>My roomate has a Connor 350 as wd0 and a Maxtor as wd1. When booting, fscp -p
>hangs his box.
I think this is common to all of the BSD wd drivers. I got around the
problem by adding the following to /etc/rc:
dd if=/dev/rwd1c of=/dev/null bs=1k count=1
The important thing is to open and initialize wd1 before the fsck -p
is performed.
--
UUCP: {hplabs!hp-sdd ucsd nosc}!crash!fpm
INET: fpm@crash.cts.com