Is your SCSI driver loaded?
If you have a 2.4 kernel, what do you get from
cat /proc/scsi/scsi
You should see an entry for your scanner if the kernel can talk to it.
If there is no entry, then don't bother with sane - you have to get your
kernel to talk scsi first. this is usually accomplished by setting up
modules.conf to load the right module for your SCSI card.
Look in the SCSI-HOWTO for more info.
Ben.
Mick Barry wrote:
> Hi all,
>
> Got a problem talking to a SCSI Canon under OS/2.
>
> My question is what should be in the conf file? Looked around and
> can't find this documented anywhere.
> Currently been trying variations of:
> scsi canon
> b2t2l0 # <- this is the device
>
> tia
> mick
>
> PS. Here's some debug output if it helps.
>
> [sanei_debug] Setting debug level of canon to 4.
> [canon] >> sane_init
> [canon] sane_init: sane 1.0.3
> [canon] >> attach_one
> [canon] >> attach
> [canon] attach: opening SCSI CANON
> [canon] attach: open failed: Invalid argument
> [canon] << attach_one
> [canon] << sane_init
> [canon] >> sane_open
> scanimage: open of device canon:b2t2l0 failed: Invalid argument
> Type ``scanimage --help -d DEVICE'' to get list of all options for DEV
>
> List of available devices:[canon] >> sane_get_devices
> [canon] << sane_get_devices
>
> pnm:0 pnm:1
> [canon] >> sane_exit
> [canon] << sane_exit
>
>
> --
> Source code, list archive, and docs: http://www.mostang.com/sane/
> To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Tue May 22 2001 - 18:04:47 PDT