From owner-freebsd-bugs  Tue Jan 11 10:41: 9 2000
Delivered-To: freebsd-bugs@freebsd.org
Received: from netcom.com (netcom12.netcom.com [199.183.9.112])
	by hub.freebsd.org (Postfix) with ESMTP id 728B815453
	for <freebsd-bugs@FreeBSD.ORG>; Tue, 11 Jan 2000 10:41:05 -0800 (PST)
	(envelope-from katcher@netcom.com)
Received: (from katcher@localhost)
	by netcom.com (8.9.3/8.9.3) id KAA13241
	for freebsd-bugs@FreeBSD.ORG; Tue, 11 Jan 2000 10:41:02 -0800 (PST)
From: Jeff Katcher <katcher@netcom.com>
Message-Id: <200001111841.KAA13241@netcom.com>
Subject: Camcontrol display anomalies and Zip drive clarification
To: freebsd-bugs@FreeBSD.ORG
Date: Tue, 11 Jan 2000 10:41:01 -0800 (PST)
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

(Sorry for not using send-pr.  My FreeBSD system is not on the Net.)

1.) Using camcontrol devlist -v with only parallel/SCSI (vpo) prints
strange stuff:

rasputin# camcontrol devlist -v
scbus-1 on xpt922294671 bus 0:
<  >                               at scbus-1 target -1 lun -1 (xpt0)
scbus0 on vpo0 bus 0:
<IOMEGA ZIP 100 P.04>              at scbus0 target 6 lun 0 (da0)
<  >                               at scbus0 target -1 lun -1 ()
rasputin# 

This is the only SCSI device on this system.

2.) Adding the FAQ-listed items to my kernel allows the ZIP parallel
interface to be seen, but the drive itself wasn't visible.  The fix, which
should be mentioned either in the FAQ or the vpo man page is to force a
more conducive parallel port mode using the kernel ppo configu flags.

Best regards,

Jeff Katcher
katcher@netcom.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message