# Re: UMAX found but xscanimage not working right.

Oliver Rauch (oliver.rauch@Wolfsburg.DE)
Thu, 01 Oct 1998 22:32:12 +0200

- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: Simon Thompson: "Re: Having problems with canon backend"
- Previous message: A. R. M.: "RE: UMAX found but xscanimage not working right."

A. R. M. wrote:

> I tried that. It says:
> find-scanner: found scanner "UMAX SuperVista S-12 V1.2" at device
> /dev/scanner
> find-scanner: found scanner "UMAX SuperVista S-12 V1.2" at device /dev/sg1
>
> Then if I try typing xscanimage sg1 or xscanimage /dev/sg1 or if I
> put
> /dev/scanner or /dev/sg1 in my umax.conf file, it doesn't work.
> If I put /dev/sgb or /dev/sgb0 in umax.conf and invoke it by just typing
> xscanimage then it comes up with a little dialog box asking me to choose
> either
> pnm:0 or pnm:1.
>
> The reason I tried /dev/sgb in umax.conf file is the following message in
> /var/adm/messages
> Oct 1 10:33:50 maniac kernel: Detected scsi generic sgb at scsi0, channel
> 0, id 5, lun 0
>
> I get this everytime I try to access the scanner, for example when I run
> find-scanner, or xscanimage.
>
> Any other ideas please?
> Thanks.

/dev/sgb and /dev/sg1 are identically if both exist. Do
ls -l /dev/sg*
Use the one of sgb or sg1 that exists!
Do as root:
chmod 777 /dev/sgb

then do (not as root)
xscanimage
or if that does not work:
xscanimage umax

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: Simon Thompson: "Re: Having problems with canon backend"
- Previous message: A. R. M.: "RE: UMAX found but xscanimage not working right."