*BSD News Article 52199


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.sprintlink.net!in2.uu.net!van-bc!io.org!bpci.net3.io.org!user
From: rrwood@io.org (Roy Wood)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Adding SCSI disk and Adaptec 1542C controller
Date: 28 Sep 1995 16:43:08 GMT
Organization: Silicon Angst Software
Lines: 43
Message-ID: <rrwood-2809951156540001@bpci.net3.io.org>
NNTP-Posting-Host: bpci.net3.io.org

Get this:

I've recently picked up an Adaptec 1542C SCSI controller and a Quantum
250MB SCSI drive, and the combination works great under DOS/Windows.  My
goal was to dedicate the drive to use under FreeBSD, so I'm trying to get
it working, but I've run into some funny problems.

As background, the standard AHA kernel for FreeBSD 2.0 reports this on boot:

ahb0 not found
aha0: 1542C/CF detected, unlocking mailbox
aha0: reading board settings, dma=5 int=11  (bus speed defaulted)
aha0 at 0x330-0x333 irq 11 drq 5 on isa
aha0 waiting for scsi devices to settle
aha0 targ 0 lun 0: type 0(direct) fixed SCSI2
aha0 targ 0 lun 0: <QUANTUM LPS270S         590W>
sd0: 258MB (528808 total sec), 2740 cyl, 2 head, 96 sec, bytes/sec 512


I also made sure to set up the appropriate entries in /dev as follows:

brw-r-----  1 root    operator    4,   0 Sep 28 11:43 sd0a
brw-r-----  1 root    operator    4,   1 Sep 28 11:43 sd0b
brw-r-----  1 root    operator    4,   2 Sep 28 11:43 sd0c
brw-r-----  1 root    operator    4,   3 Sep 28 11:43 sd0d
brw-r-----  1 root    operator    4,   4 Sep 28 11:43 sd0e
brw-r-----  1 root    operator    4,   5 Sep 28 11:43 sd0f
brw-r-----  1 root    operator    4,   6 Sep 28 11:43 sd0g
brw-r-----  1 root    operator    4,   7 Sep 28 11:43 sd0h


Unfortunately, when I try to disklabel the drive, disklabel complains that
sd0 hasn't been configured!

Once again-- this controller/drive combo works great under DOS/Windows,
but FreeBSD isn't very happy with it.  It seems odd that the disk *is*
recognized during boot, but later on disklabel claims it's not
configured.  What am I missing!?!?!?!?!  The FAQ doesn't seem to have any
specific info, so I'm finally breaking down and asking for HELP!

Thanks....

-Roy