From owner-freebsd-alpha Mon Jul 31 20:29:27 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from june.cs.washington.edu (june.cs.washington.edu [128.95.1.4]) by hub.freebsd.org (Postfix) with ESMTP id 4292D37BDCA for ; Mon, 31 Jul 2000 20:29:23 -0700 (PDT) (envelope-from wolman@cs.washington.edu) Received: from sampras.cs.washington.edu (sampras.cs.washington.edu [128.95.4.160]) by june.cs.washington.edu (8.9.3/8.9.3/0.3j) with ESMTP id UAA09250 for ; Mon, 31 Jul 2000 20:29:22 -0700 (PDT) (envelope-from wolman@cs.washington.edu) Received: from sampras.cs.washington.edu (localhost [127.0.0.1]) by sampras.cs.washington.edu (8.9.3/8.9.3) with ESMTP id UAA09102 for ; Mon, 31 Jul 2000 20:29:22 -0700 (PDT) (envelope-from wolman@sampras.cs.washington.edu) Message-Id: <200008010329.UAA09102@sampras.cs.washington.edu> To: freebsd-alpha@freebsd.org Subject: sym driver problem with 4.1 release Date: Mon, 31 Jul 2000 20:29:22 -0700 From: "Alec Wolman" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The problem that I posted yesterday about sysinstall is now looking to me as if it is a problem with the sym driver. I managed to view the boot message before sysinstall runs, and here is the problem: da0 at sym0 bus 0 target 0 lun 0 Fixed Direct Access SCSI-2 device da0: 10.000MB/sec transfers (10.000MHz, offset 31) Tagged Queueing Enabled da0: Attempt to query device size failed: NOT READY, (da0:sym0:0:0:0): . CDB: 25 0 0 0 0 0 0 0 0 0 (da0:sym0:0:0:0): NOT READY asc:4,2 (da0:sym0:0:0:0): This disk (da0) has tru64 currently installed on it, and if I boot off of it, it works fine. When I boot off of da1 (which has a version of 4.0-STABLE CVSup'ed around Jun 18th, 2000), it probes properly at 40MHz, offset 31, 16 bit, with a size of 8678MB. Alec To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message