From owner-aic7xxx Thu Mar 19 20:45:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20350 for aic7xxx-outgoing; Thu, 19 Mar 1998 20:45:04 -0800 (PST) (envelope-from owner-aic7xxx@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20338 for ; Thu, 19 Mar 1998 20:44:58 -0800 (PST) (envelope-from stevebr@primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id VAA01302 for ; Thu, 19 Mar 1998 21:44:53 -0700 (MST) Received: from ip242.msp.primenet.com(206.165.50.242) via SMTP by smtp04.primenet.com, id smtpd001283; Thu Mar 19 21:44:43 1998 From: stevebr@primenet.com (Steve Brueggeman) To: aic7xxx@FreeBSD.ORG Subject: Problems applying 5.0.x patches Date: Fri, 20 Mar 1998 04:44:54 GMT Message-ID: <3511f09f.59947@smtp.primenet.com> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id UAA20340 Sender: owner-aic7xxx@FreeBSD.ORG Precedence: bulk Well, after I sent my last message, I scanned this lists archives, and found the problem with "Bad scbptr...) was known. I changed my Adaptec BIOS settings for my Tape to narrow, 5Mhz, and that got me past the scrolling "Bad scbptr...) errors hang. That led me to the next problem. I was getting a kernel panic after all SCSI devices were found, and negotiated, and the rest of the boot process should have proceeded. Apparently, between the driver included in the linux-2.0.33.tar.gz kernel, and aic7xxx-5.0.8, the order of PCI scan was reversed. This is a real delema, because (if I understand things correctly), lilo uses the BIOS scan order to determine which device to get the kernel from (/dev/sda), but then when it comes time to continue on, what was /dev/sda as far as lilo was concerned is not /dev/sda after the kernel scans the devices. I found this by removing all devices from my 2nd controller, and found I was able to boot OK. A couple of questions. (1) Is the problem of HAVING to have the BIOS settings match the actual device capabilities, going to be fixed. The sequencer should be able to let the kernel know what the device ended up agreeing to for the width and sync negotiations. This is basic SCSI stuff. What changed between the old drivers and the new, to break this? (2) I've seen threads about the PCI scan order problem enough, to suspect there is still no good solution to this problem. So... could somebody out there be kind enough to let me know how, or where to find info on, how to force a PCI scan order, so the kernel finds my Adaptec PCI cards in the same order that the BIOS finds them in? Reguards Steve Brueggeman. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe aic7xxx" in the body of the message