From owner-freebsd-bugs Sun Apr 16 14:17:44 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA14766 for bugs-outgoing; Sun, 16 Apr 1995 14:17:44 -0700 Received: from metronet.com (root@feenix.metronet.com [192.245.137.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA14760 for ; Sun, 16 Apr 1995 14:17:43 -0700 Received: from eul64.metronet.com by metronet.com with SMTP id AA28818 (5.67a/IDA1.5hp for ); Sun, 16 Apr 1995 16:17:28 -0500 Date: Sun, 16 Apr 1995 16:17:28 -0500 Message-Id: <199504162117.AA28818@metronet.com> X-Sender: haseltin@metronet.com X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: bugs@FreeBSD.org From: haseltin@metronet.com (Doug Haseltine) Subject: Adaptec 2940W / Fast Wide SCSI Sender: bugs-owner@FreeBSD.org Precedence: bulk Howdy: I acquired a Pentium 90 with an Adaptec 2940W controller, Toshiba 4x CDROM and Fujitsu fast/wide 1Gb SCSI2 HD in January of this year. At that time, neither the latest Linux (Slackware) nor FreeBSD distribution would recognize the fact that I did indeed have a hard disk. As of your previous March SNAP release, this changed for the better; during initialization from the BOOT floppy, a correct PCI scan and SCSI lookup found both my CDROM and hard disk. However, when I first attempted to run your fdisk after running creating sufficient space via fips, the response information was erroneously stating that I had four partitions instead of the actual single MSDOS partition with an extra Non-DOS partition set up by fips. Modifications to these partions could never be saved and it appeared that the FreeBSD simply was never connecting to the hard disk correctly. With the 4/12/95 SNAP release (from Walnut Creek's site) I can now get a lot further along. The disk partitions are correctly read and I can get through the initial setup of the slices including setting up the mount (/, swap, /usr) points. However, occasionally during the setup process I receive an error message stating that ahc0 has timed out. Invariably once I get to the point of proceeding with the installation, I always get this message that ahc0 is timed out, repeated to the screen over and over again. Thanks for everyone's efforts getting this latest of Adaptec's controllers up and running with FreeBSD. At the current rate of progress, I'm sure the next release will make it all the way through installation. Just thought I'd let you know of the status of the most recent version as it operates on this machine. I'm not sure if more frequent checks on the status of the controller are needed within the boot code between read/write operations to disk or whether it would be worthwhile changing the data rate from 10Mb/sec (20) down to a smaller value in the Adaptec BIOS just to see what happens. Thanks and good luck.