Hi, On Thu, Jun 19, 2003 at 08:06:21PM -0700, Sopho wrote: > Yes I only use the microtek module. I have attached a > small sample of the error log after I enabled SCSI > debugging at the end of this email. I can send the > whole file if it will be more helpful but it's big.
No, that's ok. Looks like a kernel (or hardware?) problem for me. But the maintainers of the microtek2 SANE backend and the microtek scanner module may know more details. > I should say that I have "Probe all LUNs on each SCSI > device" enabled for my card reader. I don't know if > that has anything to do with this. Try without. I have seen scanners that don't like that. I don't know however, if that's the case with your scanner. If you use ide-scsi, try disbaling this also. > Yes It looks like it. Here is the relevant entry: > > Host: scsi2 Channel: 00 Id: 00 Lun: 00 > Vendor: Model: Scanner 600A4 Rev: 1.10 > Type: Scanner ANSI SCSI > revision: 02 May be ok. > Yes you are right: > found USB scanner (vendor=0x05da, product=0x009a) at > libusb:001:003 But it should also find a SCSI scanner. > [microtek2] attach: device='/dev/sg5' [...] > [sanei_scsi] scsi_req_enter: entered 0x4034a008 > [sanei_scsi] sanei_scsi.issue: 0x4034a008 > dev_max(currently)=11 max_active_device=6 (origin 1) > scsi_dma_free_sectors=160 sg_pool_secs_aval=320 > def_reserved_size=32768 > >>> device=sg5 scsi2 chan=0 id=0 lun=0 em=1 > sg_tablesize=255 excl=1 > FD(1): timeout=120000ms bufflen=131072 (res)sgat=4 > low_dma=0 > cmd_q=1 f_packid=0 k_orphan=0 closed=0 > rb>> rcv: id=0 blen=5 dur=0ms sgat=0 op=0x12 That's the command sent to the device. > [sanei_scsi] scsi_req_enter: queue_used: 1, queue_max: > 1 > [sanei_scsi] sanei_scsi_req_wait: waiting for > 0x4034a008 > [sanei_scsi] sanei_scsi.issue: 0x4034a008 > dev_max(currently)=11 max_active_device=6 (origin 1) > scsi_dma_free_sectors=160 sg_pool_secs_aval=320 > def_reserved_size=32768 > >>> device=sg5 scsi2 chan=0 id=0 lun=0 em=1 > sg_tablesize=255 excl=1 > FD(1): timeout=120000ms bufflen=131072 (res)sgat=4 > low_dma=0 > cmd_q=1 f_packid=0 k_orphan=0 closed=0 > rb>> rcv: id=0 blen=5 dur=0ms sgat=0 op=0x12 Looks like the SCSI device (or the microtek module) hasn't accepted the command at all. > [sanei_scsi] sanei_scsi_req_wait: read 64 bytes > [sanei_scsi] sanei_scsi_req_wait: SCSI command complained: Success > [sanei_scsi] sense buffer: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 An error occured, but the sense buffer doesn't show any details. > [sanei_scsi] target status: 00 host status: 0007 driver status: 0000 It's an error generated by the host, in this case by the microtek kernel module or the SCSI layer. 0x07 is "Internal error". Well, no idea what this really means. > The following is from sane-find-scanner with scsi > debug enabled, right at the are of /dev/sg5 (which is > where my scanner is poking it's head this time) > [sanei_scsi] sanei_scsi_req_wait: SCSI command complained: Success > [sanei_scsi] sense buffer: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > [sanei_scsi] target status: 00 host status: 0007 driver status: 0000 Same here. SANE tries to get an inquiry from the scanner but that doesn't work because of an "internal error". No idea how to fix that, but my guess is that's a problem in the microtek module. I don't think it's related to SANE. Bye, Henning ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
