Date: Sat, 18 Apr 1998 13:16:05 -0400 From: Randall Hopper <rhh@ct.picker.com> To: scsi@FreeBSD.ORG Subject: SCSI Scanner question Message-ID: <19980418131605.A3370@ct.picker.com>
next in thread | raw e-mail | index | archive | help
Hi. I'm attempting to get my scanner (Microtek E6) working with -current
and SANE. I'm not code-savy with SCSI, so I would appreciate any tips
those with more experience could provide.
I set this up first in MSW95. Works fine -- no problems. But I'd of
course like to scan in FreeBSD if I could.
The device probes up fine as uk0, Sane probes the device correctly as a
Microtek ScanMaker E6, but when Sane tries to scan with it, it gives:
scanimage: sane_start: Device busy
and this appears in /var/log/messages:
uk0: extraneous data discarded.
uk0: COMMAND FAILED (9 0) @f0551000.
Here are the particulars:
dmesg:
scbus0 target 6 lun 0: < Scanner 600 1.91> type 6 fixed SCSI 3
uk0 at scbus0 target 6 lun 0
uk0: Unknown
setenv SANE_DEBUG_MICROTEK 100; scanimage -d microtek:/dev/scanner
...
[microtek] sane_get_parameters...
[microtek] sane_get_parameters: res_code = 16 (10)
[microtek] sane_get_parameters: dots_per_mm: 3.937008
[microtek] sane_get_parameters: units_per_mm: 23.622047
[microtek] sane_get_parameters: lines: 0
[microtek] .wait_ready 3...
[microtek] .mode_select_1 3...
[microtek] .mode_sense_1...
scanimage: sane_start: Device busy <-----------------------
[microtek] sane_cancel...[microtek] sane_close...
[microtek] sane_exit...
[microtek] sane_exit: MICROTEK says goodbye.
Tail of SCSIDEBUG output for "scanimage -d microtek:/dev/scanner"
(enabled with "scsi -f /dev/uk0 -d 255"):
/kernel: uk0(ncr0:6:0): back from sleep
/kernel: uk0(ncr0:6:0): scsi_do_ioctl(0xc0605101)
/kernel: uk0(ncr0:6:0): user_strategy
/kernel: uk0(ncr0:6:0): scsi_cmd
/kernel: uk0(ncr0:6:0): get_xs
/kernel: uk0(ncr0:6:0): returning
/kernel: xs(0xf06fdf00): flg(0x828)sc_link(0xf06fde80)retr(0x0)timo(0xea60)cmd(0xf06fdf58)len(0x6)data(0xf3e75f8a)len(0x24)res(0x0)err(0
x0)bp(0xf0851d00)uk0: command: 19,0,0,0,1e,0-[36 bytes]
/kernel: ------------------------------
/kernel: 000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
/kernel: 016: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0 4f
/kernel: 032: bf ef 75 a3
/kernel: ------------------------------
/kernel: uk0(ncr0:6:0): about to sleep
/kernel: uk0: extraneous data discarded. <---------------------
/kernel: uk0: COMMAND FAILED (9 0) @f0551000. <---------------------
/kernel: uk0(ncr0:6:0): scsi_done
/kernel: uk0: command: 19,0,0,0,1e,0-[36 bytes]
/kernel: ------------------------------
/kernel: 000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
/kernel: 016: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0 4f
/kernel: 032: bf ef 75 a3
/kernel: ------------------------------
/kernel: uk0(ncr0:6:0): calling user done()
/kernel: uk0(ncr0:6:0): user-done
/kernel: uk0(ncr0:6:0): timeout <---------------------
/kernel: uk0(ncr0:6:0): returned from user done()
/kernel: uk0(ncr0:6:0): free_xs
/kernel: uk0(ncr0:6:0): returning to adapter
/kernel: uk0(ncr0:6:0): back from sleep
/kernel: uk0(ncr0:6:0): ukclose: Closing device
I notice that this is the the only occurance of "timeout" in the messages
output. Is this significant?
Regarding the "extraneous data discarded", I see in pci/ncr.c that this
occurs when (cp->xerr_status == XE_EXTRA_DATA), which seems to be set in a
script at the top. The comment for the set reference reads:
** The target wants to tranfer too much data
** or in the wrong direction.
** Remember that in extended error.
Do I need to bump buffer sizes or timeouts somewhere?
Sort of stabbing in the dark on this one, so anything you can suggest or
clarify would be appreciated.
Thanks,
Randall
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980418131605.A3370>