# Re: Getting UMAX scanner to work with Future domain 1

Oliver Rauch (oliver.rauch@Wolfsburg.DE)
Mon, 24 Aug 1998 16:49:30 +0200

- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: Tilman Vogel: "Mustang Paragon 1200 SP (bugs)"
- Previous message: Oliver Rauch: "Re: Umax 610P Scanner"
- Maybe in reply to: Zot O'Connor: "Getting UMAX scanner to work with Future domain 1"

Zot O'Connor wrote:

> I am having problems getting my future domain controller
> (old ISA) to recognize my Vista S8 scanner.
>
> The controller worked extremely well recently, but I
> replaced it when I upgraded. I have an UDS-1101 (or whatever)
> working as a full SCSI under NT. I though I'd move it to Linux.
>
> I have a jaz drive on the card too, it works.
>
> The Scanner does not seem to report to the kernel module (it is at ID1)
> Aug 14 15:19:30 eater kernel: scsi2 <fdomain>: BIOS version 2.0 at 0xca000 using
> scsi id 6
> Aug 14 15:19:30 eater kernel: scsi2 <fdomain>: TMC-1800 chip at 0x140 irq 15
> Aug 14 15:19:30 eater kernel: scsi2 : Future Domain TMC-16x0 SCSI driver, versio
> n 5.44
> Aug 14 15:19:30 eater kernel: scsi : 1 host.
> Aug 14 15:19:30 eater kernel: Vendor: iomega Model: jaz 1GB Rev:
> H.62
> Aug 14 15:19:30 eater kernel: Type: Direct-Access ANSI
> SCSI revision: 02
> Aug 14 15:19:30 eater kernel: Detected scsi removable disk sda at scsi2, channel
> 0, id 5, lun 0
> Aug 14 15:19:30 eater kernel: SCSI device sda: hdwr sector= 512 bytes. Sectors=
> 2091050 [1021 MB] [1.0 GB]
> Aug 14 15:19:30 eater kernel: sda: Write Protect is off
> Aug 14 15:19:30 eater kernel: sda: sda4
>
> [root@eater /root]# cat /proc/scsi/fdomain/2
> Future Domain TMC-16x0 SCSI driver, version 5.44
> [root@eater /root]# cat /proc/scsi/scsi
> Attached devices:
> Host: scsi2 Channel: 00 Id: 05 Lun: 00
> Vendor: iomega Model: jaz 1GB Rev: H.62
> Type: Direct-Access ANSI SCSI revision: 02
>
> Yet when I scanimage --list-devices I get some recognition:
>
> Scanlist
> [umax] attach_scanner: opening /dev/sga
> [umax] init
> [umax] initialize_values
> [umax] identify_scanner
> [umax] do_inquiry
> [umax] check condition sense handler
> [umax] check condition sense: ILLEGAL REQUEST
> [umax] -> no error
> [umax] -> illegal field in CDB
> [umax] check condition sense handler
> [umax] check condition sense: ILLEGAL REQUEST
> [umax] -> no error
> [umax] -> illegal field in CDB
> [umax] attach_scanner: scanner-identification failed
> [umax] attach_scanner: opening /dev/sgb
> [umax] attach_scanner: open failed
> [umax] attach_scanner: opening /dev/sgb
> [umax] attach_scanner: open failed
> [umax] attach_scanner: opening /dev/sge
> [umax] attach_scanner: open failed
> [umax] attach_scanner: opening /dev/sda
> [umax] init
> [umax] initialize_values
> [umax] identify_scanner
> [umax] do_inquiry
> [umax] check condition sense handler
> [umax] invalid sense key => handled as DEVICE BUSY!
> [umax] check condition sense handler
> [umax] invalid sense key => handled as DEVICE BUSY!
> [umax] attach_scanner: scanner-identification failed
> [umax] attach_scanner: opening /dev/scanner
> [umax] attach_scanner: open failed
>
> I have had parity errors with this card and an old NEC Cdrom.
> I though that was fixed now. Any ideas?
>
>

Hi,

please send me the output of:

ls -l /dev/sg*

and

cat /proc/scsi

Bye
Oliver

    --
    Source code, list archive, and docs: http://www.mostang.com/sane/
    To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com

- Next message: Tilman Vogel: "Mustang Paragon 1200 SP (bugs)"
- Previous message: Oliver Rauch: "Re: Umax 610P Scanner"
- Maybe in reply to: Zot O'Connor: "Getting UMAX scanner to work with Future domain 1"