Date: Fri, 11 May 2001 09:36:50 -0400 From: Timothy Reaves <treaves@silverfields.com> To: "Justin T. Gibbs" <gibbs@scsiguy.com> Cc: aic7xxx <aic7xxx@FreeBSD.ORG> Subject: Re: BUGS in 2.4.4 aic7xxx driver Message-ID: <3AFBEAF2.4080204@silverfields.com> References: <200105101527.f4AFRPU74741@aslan.scsiguy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Justin T. Gibbs wrote: >> I've noticed that scsi1:A:1:0 is having the same problem. >> > > ... > > Can you try v6.1.13 of the aic7xxx driver and see if it corrects > your problem? You can get the patches for 2.4.4 from here: > > http://people.FreeBSD.org/~gibbs/linux/ > Thank you. This seems to have taken care of that issue, however one still remains. I have two scanners attached to my system, and they were what was related to the previous problem. On scaner is a HP 3C flatbed, a very generic scanner. The other printer is a Polariod SprintScan 35+, a very high end film scanner. It is still having trouble, although not that above. I was hoping that the 6.1.3 patch would fix that too, but it didn't. I contacted the software vendor of tha application I use with that scanner, and after looking at a log file from his software has said "The problem is that the "GET WINDOW" command is returning bad data from the scsi driver, and this is messing up subsequent scsi commands. You might check to see if there's a newer (or fixed) scsi driver for your scsi card." I've asked him if he has any further information, nad I'll e-mail as soon as I find out. Also, would looking at the log I sent him be of any use? The difference in the way that scanner is mis-behaiving was different from the stock 2.4.4 to the 2.4.4 with patch, so the driver did make some difference, but not enough. Again, thanks for the help! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe aic7xxx" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3AFBEAF2.4080204>