Return to BSD News archive
Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!spool.mu.edu!howland.reston.ans.net!usc!news.isi.edu!gremlin!nrtc.northrop.com!jpl
From: jpl@nrtc.northrop.com (Jeff P. Lankford)
Subject: [Q] wd0: cannot find label (no disk label)
Message-ID: <CBxB90.B1J@gremlin.nrtc.northrop.com>
Sender: news@gremlin.nrtc.northrop.com (Usenet News Manager)
Organization: Northrop Research and Technology Center
Date: Tue, 17 Aug 1993 21:48:35 GMT
Lines: 28
I can boot Tiny BSD from floppy, but cannot install on hard drive.
# install
wd0: cannot find label (no disk label)
sd0: no disk label
Do you want to install 386BSD on the ENTIRE drive? (y/n) y
#
Even though the response was "y" to install on entire drive,
the result was immediate return to the command line prompt.
Using the Fix-It floppy, "disklabel /dev/ras0d" shows a 386BSD
partition on the SCSI drive, just as i created it using "pfdisk".
However, "disklabel /dev/rwd0d" produces:
wd0: connot find label (no disk label)
disklabel: /dev/rwd0d: Invalid argument
Both the IDE and SCSI drives have several partitions of various types
on them, and DOS partitions work fine under DOS/Windows. The IDE
controller is a no-name Taiwanese (actually, TurboIDE using Appian
ADI2 chip) VESA Local Bus, evidently compatible with Western Digital
controller, at least under DOS/Windows.
Any ideas for debugging this problem? It sounds like an incompatibility
between the IDE controller and the (386BSD) wd driver. I haven't
looked at the 386BSD wd source yet. Is it feasible to debug this driver
(just to reading the disklabel) w/ a debugging kernel on floppy?
I have been told that the Appian ADI2 chip conforms to the ANSI
AT-Attachment spec; does the 386BSD wd driver also conform to this
spec?
all guidance appreciated,
jpl