From owner-freebsd-hackers Sun Jul 13 12:00:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA03437 for hackers-outgoing; Sun, 13 Jul 1997 12:00:17 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA03429 for ; Sun, 13 Jul 1997 12:00:12 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id MAA01735 for ; Sun, 13 Jul 1997 12:00:13 -0700 (PDT) Message-Id: <199707131900.MAA01735@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: hackers@freebsd.org Subject: aha1522 ?? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 13 Jul 1997 12:00:13 -0700 From: Amancio Hasty Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Move from the sane list.... Do we have an aha1522 expert? Cheers, Amancio gord@m-tech.ab.ca said: > Hi! > >>>>> eric writes: > e> First, it wasn't a matter of the scanner blocking the scsi bus -- > e> it had an entire scsi bus to itself on an Adaptec 1522 (which > e> turned out to be the problem) Second, I'm using the "pt" driver, > e> although i suspect the "uk" driver would work too now that I've > e> moved the scanner to an Adaptec 2940W. Everything works more or > e> less fine now, except the scanner still needs to be the _only_ > e> device on the bus. If I put a disk on the same bus as the scanner, > e> (with a different SCSI id# obviously) accesses to the disk time > e> out and stuff. It seems like it may be a termination issue, which > e> I'll fiddle around with some more. But anyway, it will not work > e> at all using an AHA1522, with either a Umax or an HP4c scanner. > Amancio... > I have a strong suspicion that the FreeBSD AHA1522 driver is a little > flaky. Last year, when I was trying to port the PINT (`ss' SCSI > scanner device) driver to FreeBSD 2.1.5 using my AHA1522, I ran into > endless problems, because the scanner just *would not respond* to any > commands I sent it. > It was very frustrating, and at the time, I attributed it to my shoddy > kernel hacking, so I did not report the bug. > When I talked more with PINT's author, and tried both `upgrading' > (?... don't know if that's the right word for it) to NetBSD 1.2, then > reintegrating PINT, it worked like a charm. > Later, I became even more convinced that my kernel hacking job had > been correct, and that FreeBSD's AHA1522 driver was at fault. Again, > I didn't report this because I didn't have a FreeBSD machine any more > in order to narrow down the bug. > Anyway, now that it appears somebody else is having the same problem, > this may be an opportunity to find out what it is. > Right now I'm running my ScanJet 4p with an AHA1522 under Linux > without any problems, and as I said before, it also worked under > NetBSD. > Thanks for any comments you folks may have. I'd really like to figure > out if this behaviour is a driver bug, so that the FreeBSD folks can > fix it (if it isn't fixed already)! :) > -- > Gord Matzigkeit | Proudly running pieces of the GNU operating > system. > gord@m-tech.ab.ca | Jacques Cousteau loved programming in > assembler.