Date: Thu, 19 Feb 2004 14:10:21 -0700 From: "Justin T. Gibbs" <gibbs@scsiguy.com> To: Cristiano Duarte <cunha17@uol.com.br> Cc: aic7xxx@freebsd.org Subject: Re: BUG introduced in kernels above 2.4.18 ? Message-ID: <432780000.1077225021@aslan.btc.adaptec.com> In-Reply-To: <40352373.1080201@uol.com.br> References: <4034D259.5050001@uol.com.br> <370790000.1077213725@aslan.btc.adaptec.com> <40350174.7000305@uol.com.br> <403520000.1077219848@aslan.btc.adaptec.com> <40352373.1080201@uol.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
> I don't want to bother you, but even the kernel(aic7xxx) doesn't > recognizes the scanner anymore, so IMHO that's nothing to do with SANE, > am I right ? Yes. It could just be that your scanner is broken. > If the kernel can't recognize the scsi device, there are three points > of error: the kernel, the controller or the scsi device. Is it possible > that a scsi device that works on Windows, works with Adaptec Controller > BIOS(it is detected by the BIOS), kernel versions 2.4.18 and before makes > a protocol violation? Certainly. The commands used to probe the scanner are likely very different in Linux than under Windows. I'm also quite sure that the Adaptec BIOS does not flag the same errors as the Linux driver. > Is there a way to debug(or trace) the scsi protocol? I use a SCSI bus analyzer. You can also enable some SCSI layer logging to see if that is helpful. -- Justin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?432780000.1077225021>