Date: Sat, 4 Jan 1997 03:00:02 -0800 (PST) From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-bugs Subject: Re: conf/2367: Buslogic SCSI driver bad probe of 742A early revision IRQ and version Message-ID: <199701041100.DAA11706@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR conf/2367; it has been noted by GNATS. From: j@uriah.heep.sax.de (J Wunsch) To: tedm@agora.rdrop.com Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: conf/2367: Buslogic SCSI driver bad probe of 742A early revision IRQ and version Date: Sat, 4 Jan 1997 11:40:30 +0100 As root@testmach%toybox, UNEXPECTED_DATA_AFTER_ADDRESS@.SYNTAX-ERROR. wrote: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Eeek! :) > Jan 3 02:38:07 testing /kernel: bt0: <Buslogic 74xB SCSI host adapter> at 0x330-0x333 0x1c00-0x1cff irq 9 on eisa0 slot 1 > Jan 3 02:38:07 testing /kernel: bt0: Bt742A/G0-(32bit) bus It's been a while ago that i've been using a Bt742A. I remember that it wasn't totally unproblematical for me either. . turn off ISA DMA emulation, . use level-triggered IRQ, and with FreeBSD > 2.1: > Jan 3 02:38:11 testing /kernel: bt: unit number (1) too high > Jan 3 02:38:11 testing /kernel: bt1 not found at 0x330 ...disable the ISA Buslogic driver. Since the EISA device will also respond on the ISA addresses, the driver gets confused otherwise. > This problem DIDN'T occur with FreeBSD version 1.1.5.1 on this machine! Because it didn't have EISA controller code, so the card has been handled as some sort of an ``extended ISA'' device. There was definately no EISA autoprobing in FreeBSD <= 2.1R, but it is there now. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701041100.DAA11706>