Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!sgiblab!cs.uoregon.edu!usenet.ee.pdx.edu!fastrac.llnl.gov!lll-winken.llnl.gov!uop!napa!hughes
From: hughes@napa.eng.uop.edu (Ken Hughes)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: [NetBSD 0.9] patch to wd.c for IDE controller weirdnesses
Date: 4 Jan 1994 02:36:00 GMT
Organization: Electrical and Computer Engineering, University of the Pacific
Lines: 33
Message-ID: <2gakmg$ac4@unix1.cc.uop.edu>
References: <2ga4l7$i75@explorer.clark.net> <2ga76e$r01@unix1.cc.uop.edu> <2gac7i$ma7@explorer.clark.net>
NNTP-Posting-Host: napa.eng.uop.edu
X-Newsreader: TIN [version 1.2 PL2]
Eric S. Hvozda (ack@clark.net) wrote:
: In article <2ga76e$r01@unix1.cc.uop.edu>,
: Ken Hughes <hughes@napa.eng.uop.edu> wrote:
: >
: >Don't know of this is related, but I had a similar problem this weekend when
: >I tried to add a second IDE drive to my system. The system booed fine with
: >one drive (wd0) but adding the second caused a panic/trap/reboot. After
: >capturing the fleeting message on my video recorded and finding the complaint
: >"no disk label on wd0", I discovered that NetBSD was ignoring the CMOS
: >configuration for wd0 and using the parameters as (apparently) queried from
: >the drive. Luckily, my master drive is a Maxtor which I could jumper to
: >specify the "default" configuration and after doing this things were fine.
: Well it was labeled before I patched wd.c, and worked fine then. It's only
: since I've patched wd.c for the famous IDE lock problem that this developed.
: I was thinking or relabeling the disk, but if it can read the label on wd1,
: why not wd0?
That's the thing. The label on my disk was fine; it was the driver which
was miscalculating where to read the label from. The disk was setup
as 936/16/17 but NetBSD determined it was 1024/14/17 when booting with the
second IDE attached, so the disk partition table saying the NetBSD
partition was as x/y/z was calculating the incorrect physical block. As I
said, when I jumpered wd0 things were fine; the disk label was still
there.
I've also applied the patch to wd.c, but all this occured before then.
--
Ken Hughes | "I can't believe this is my life;
(khughes@uop.edu) | I'm going to have to send my SAT
Electrical and Computer Engr | scores to San Quentin instead of
University of the Pacific | Stanford..." _Heathers_