Problems applying 5.0.x patches

Steve Brueggeman stevebr at primenet.com
Thu Mar 19 20:45:04 PST 1998


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 at FreeBSD.org
with "unsubscribe aic7xxx" in the body of the message



More information about the aic7xxx mailing list