From owner-freebsd-scsi Tue Jul 22 05:03:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA24179 for freebsd-scsi-outgoing; Tue, 22 Jul 1997 05:03:35 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA24160; Tue, 22 Jul 1997 05:03:26 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id HAA06466; Tue, 22 Jul 1997 07:18:01 -0400 (EDT) From: Peter Dufault Message-Id: <199707221118.HAA06466@hda.hda.com> Subject: Re: help: wiring down scsi devices doesn't work In-Reply-To: from Jay Kuri at "Jul 19, 97 00:06:15 am" To: jaykuri@oneway.com (Jay Kuri) Date: Tue, 22 Jul 1997 07:18:00 -0400 (EDT) Cc: freebsd-scsi@FreeBSD.ORG, questions@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I have been trying, to no avail, to wire down a particular target > device to pt0. Although config gives me no errors, and the kernel > rebuilds fine, it does not wire down the device... and instead reports it > (a scsi scanner) as uk0. It didn't recognize it as a processor type. The device still needs to claim to be a processor type for the kernel to connect it as that. For example, you can't forceably say that a WORM is a CDROM with something like: device cd0 at scbus0 target 5 unit 0 and have it work for whatever shows up in target 5, though it may be a good idea given a required "flag 0x01" etc. Post your verbose boot messages. -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval