Now I am trying a new Diamond Fireport 40, an NCR53c875J based card.
I get the same thing.
*After* I turned parity off, I get the scanner seen by the card bios and
setup screens.
The kernel module does no see it.
I am about to start meandering the driver next, but since this now
happens under 2 different cards, redhat 5.1 and redhat 5.2, I wanted to
know if I am S.O.L. to start with.
Or can I convince SANE the scanner is there with the kernel admitting
it? (oh I know, that is insane, but perhaps it is in SANE).
Any help would be appreciated. Including any driver options to the scsi
module to turn more debugging on. Unfortunately the system disks are
SCSI and I have to reboot to try a new driver.
(BTW I have completely different cables).
I assuming this is a parity/SCSI-IvsII/UMAX sucks issue. But since this
worked fine under a NCR on board SCSI (NCR chip on mother board that
gave me Adaptec SCSI 78xx) and the included SCSI card under 95 and NT,
I'd like to fix this now...
Thanks in advance!
-- Zot O'Connorwww.ZotConsulting.com www.WhiteKnightHackers.com
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com