From owner-freebsd-alpha Thu Jan 30 17:37:10 2003 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8065537B405 for ; Thu, 30 Jan 2003 17:37:09 -0800 (PST) Received: from wolfram.com (wri-dns0.wolfram.com [140.177.205.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50CA643F79 for ; Thu, 30 Jan 2003 17:37:08 -0800 (PST) (envelope-from hemi@just.puresimplicity.net) Received: from just.puresimplicity.net ([140.177.207.10]) by wolfram.com (8.11.2/8.11.2) with ESMTP id h0V1b1f26259 for ; Thu, 30 Jan 2003 19:37:02 -0600 Received: (from hemi@localhost) by just.puresimplicity.net (8.12.6/8.12.6/Submit) id h0V1jgmS007346 for freebsd-alpha@FreeBSD.org; Thu, 30 Jan 2003 19:45:42 -0600 (CST) (envelope-from hemi) Date: Thu, 30 Jan 2003 19:45:42 -0600 From: Josh Tolbert To: freebsd-alpha@FreeBSD.org Subject: Unusual SCSI problem... Message-ID: <20030131014541.GB7260@just.puresimplicity.net> References: <20030125055014.GA86967@just.puresimplicity.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030125055014.GA86967@just.puresimplicity.net> User-Agent: Mutt/1.4i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I've got a PC164LX, 533MHz 21164A and 1G RAM. I'm trying to use a Symbios/LSI Logic SYM22910 dual-channel, U2W SCSI controller with various hard drives. With some drives (specifically IBM DDYS-34560 UW drives) everything appears to function just fine, However, with other drives the controller and SRM see the drive, but exer_werite on the drive doesn't work and FreeBSD doesn't see the drive. During boot of the 5.0 miniinst CD I get (noperiph:sym0:-1:-1) or something of the sort for both channels after the "waiting 15 seconds for SCSI devices" message appears. Some wise Alpha people (in #Alpha on freenode; #FreeBSD-alpha seems to be fairly empty a lot of the time) advised me to "chmod +w dka300.3.0.6.0", which worked fine and gave me no errors. At that point I was able to "exer -a w dka300" just fine, as well as exer_write the drive, but FreeBSD's dmesg still didn't show a drive present. What gives? The drives are jumpered properly, the same drives/cables/controller/terminators work fine in an x86 machine and the 4.5G IBM drives all work fine in the Alpha...Why won't the other drives?. I've updated the controller's firmware and the drive's firmware when applicable. I've tried just about everything I can think of. Any ideas would be appreciated. Thanks, Josh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message