Jason Joy wrote:
>
> Hey there.
>
> I have a UMAX Astra 610S scanner, which is listed as being supported by
> sane, but I am unable to get it to work and think that I'm just missing
> something easy to fix. So, I am asking if anyone would know what is
> wrong based on what I do know.
>
> [root@dilophosaur /dev]# insmod aha152x aha152x=0x140,11,6,1
> aha152x: BIOS test: passed, detected 1 controller(s)
> aha152x0: vital data: PORTBASE=0x140, IRQ=11, SCSI ID=6,
> reconnect=enabled,
> parity=enabled, synchronous=disabled, delay=100, extended
> translation=disabled
> aha152x: trying software interrupt, ok.
> scsi0 : Adaptec 152x SCSI driver; $Revision: 1.7 $
> scsi : 1 host.
> Vendor: UMAX Model: Astra 610S Rev: V1.3
> Type: Scanner ANSI SCSI revision: 02
> Vendor: IOMEGA Model: ZIP 100 Rev: J.02
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi removable disk sda at scsi0, channel 0, id 5, lun 0
> SCSI device sda: hdwr sector= 512 bytes. Sectors= 196608 [96 MB] [0.1
> GB]
> sda: Write Protect is on
> sda: sda4
Something is missing here. If sg is built into the kernel then
it will report all scsi devices that are neither discs, nor tapes
nor cdroms. In other words it will report scanners. On the other
hand sg may be a module ....
> ---
> To me, it seems that the adaptor's modules loaded correctly. The
> adaptor is just a generic aha152x adaptec card.
>
> Next, I check everything is truly connected.
> ---
> [root@dilophosaur /root]# cat /proc/scsi/scsi
> Attached devices:
> Host: scsi0 Channel: 00 Id: 02 Lun: 00
> Vendor: UMAX Model: Astra 610S Rev: V1.3
> Type: Scanner ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 05 Lun: 00
> Vendor: IOMEGA Model: ZIP 100 Rev: J.02
> Type: Direct-Access ANSI SCSI revision: 02
> ---
> Looks good to me.
Fine.
> Next, I set the UMAX debug level and try to see if SANE will see it...
> ---
> [user@dilophosaur user]$ scanimage -L
> [sanei_init_debug]: Setting debug level of umax to 128.
> [umax] sane_init
> [umax] This is sane-umax version 1.0 build 18
> [umax] (C) 1997-2000 by Oliver Rauch
> [umax] EMAIL: Oliver.Rauch@Wolfsburg.DE
> [umax] attach_scanner: /dev/scanner
> [umax] attach_scanner: opening /dev/scanner
> [umax] attach_scanner: open failed
> [umax] attach_scanner: /dev/sga
> [umax] attach_scanner: opening /dev/sga
> [umax] attach_scanner: open failed
> [umax] attach_scanner: /dev/sgb
> [umax] attach_scanner: opening /dev/sgb
> [umax] attach_scanner: open failed
> [umax] sane_get_devices
> [umax] sane_exit
> ---
> Checking my devices....
> ---
> [user@dilophosaur user]$ ls -l /dev/sg*
> lrwxrwxrwx 1 root root 3 Jan 22 19:42 /dev/sg0 -> sga
> lrwxrwxrwx 1 root root 3 Jan 22 19:42 /dev/sg1 -> sgb
> lrwxrwxrwx 1 root root 3 Jan 22 19:42 /dev/sg2 -> sgc
> lrwxrwxrwx 1 root root 3 Jan 22 19:42 /dev/sg3 -> sgd
> lrwxrwxrwx 1 root root 3 Jan 22 19:42 /dev/sg4 -> sge
> lrwxrwxrwx 1 root root 3 Jan 22 19:42 /dev/sg5 -> sgf
> lrwxrwxrwx 1 root root 3 Jan 22 19:42 /dev/sg6 -> sgg
> lrwxrwxrwx 1 root root 3 Jan 22 19:42 /dev/sg7 -> sgh
> crwxrwxrwx 1 root sys 21, 0 May 5 1998 /dev/sga
> crwxrwxrwx 1 root sys 21, 1 May 5 1998 /dev/sgb
> crwxrwxrwx 1 root sys 21, 2 May 5 1998 /dev/sgc
> crwxrwxrwx 1 root sys 21, 3 May 5 1998 /dev/sgd
> crwxrwxrwx 1 root sys 21, 4 May 5 1998 /dev/sge
> crwxrwxrwx 1 root sys 21, 5 May 5 1998 /dev/sgf
> crwxrwxrwx 1 root sys 21, 6 May 5 1998 /dev/sgg
> crwxrwxrwx 1 root sys 21, 7 May 5 1998 /dev/sgh
> [user@dilophosaur user]$ ls -l /dev/scanner
> lrwxrwxrwx 1 root root 3 Feb 24 20:55 /dev/scanner ->
> sga
> ---
> Hmmm. The last bit of information I want to contribute is:
> ---
> [kyroraz@dilophosaur sane.d]$ cat umax.conf
> scsi UMAX * Scanner
> scsi LinoHell Office
> scsi LinoHell Office2
> scsi LinoHell SAPHIR2
> scsi Nikon AX-210
> /dev/scanner
> /dev/sga
> /dev/sgb
>
> -----
>
> Anyone have any ideas? I'm running out of them tonight... The
> ZIP drive works perfectly, so I don't think it's the SCSI card, and the
> scanner detects in Windows, at least, Windows says that it's there
> (haven't scanned in Windows at all). I hope this is the right forum for
> this too. :)
Has the scsi generic driver been selected in the kernel build?
Alternatively if you have an off-the-shelf distribution try:
$ insmod sg
to install the scsi generic module then try SANE again.
Doug Gilbert
-- 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 : Thu Feb 24 2000 - 20:34:51 PST