Discussion:
Problem in setting up Xsane
(too old to reply)
Stephen Liu
2003-02-25 17:33:13 UTC
Permalink
Hi all folks,

Desktop KDE
Scanner Agfa Snapscan 310

This is the first time I tried to setup Xsane for scanning on Linux.

As user on console window
# xsane

After acepting the licence following Error warning popup

Failed to open device 'setup'
Invalid argument.


Following URL provides a good example to setup this scanner but working
on SANE which has not been installed as standard installation

http://216.239.53.100/linux?q=cache:7fp6J492cE0C:duvet.eee.nottingham.ac.uk/scanner/snapscan_310_linux.html+How+to+install+scsi+scanner+on+Xsane&hl=en&ie=UTF-8

In addition it requires to make jumper setting on the SCSI card but my
SCSI card coming with the scanner does not have jumpers.

Any folks on the list have experience? Kindly advise.

Thanks in advance.


B.Regards
Stephen Liu
Oliver Schwartz
2003-02-25 19:44:23 UTC
Permalink
Hi,
Post by Stephen Liu
In addition it requires to make jumper setting on the SCSI card but
my SCSI card coming with the scanner does not have jumpers.
Is your SCSI card recognised in Linux (i.e. what's the output of
"cat /proc/scsi/scsi")?

If so, does sane-find-scanner find your scanner?

I don't know where xsane got the "setup" device. Did you specify any
command line arguments? (You shouldn't).

-Oliver
Stephen Liu
2003-02-26 02:42:29 UTC
Permalink
Hi Oliver,

Thanks for your response.

Oliver Schwartz wrote:

- snip -
Post by Oliver Schwartz
Is your SCSI card recognised in Linux (i.e. what's the output of
"cat /proc/scsi/scsi")?
$ cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e
Type: CD-ROM ANSI SCSI revision: 02

It looks the SCSI card detected.
Post by Oliver Schwartz
If so, does sane-find-scanner find your scanner?
No

$ sane-find-scanner
# Note that sane-find-scanner will find any scanner that is connected
# to a SCSI bus and some scanners that are connected to the Universal
# Serial Bus (USB) depending on your OS. It will even find scanners
# that are not supported at all by SANE. It won't find a scanner that
# is connected to a parallel or proprietary port.

# You may want to run this program as super-user to find all devices.
# Once you found the scanner devices, be sure to adjust access
# permissions as necessary.

# If your scanner uses SCSI, you must have a driver for your SCSI
# adapter and support for SCSI Generic (sg) in your Operating System
# in order for the scanner to be used with SANE. If your scanner is
# NOT listed above, check that you have installed the drivers.
Post by Oliver Schwartz
I don't know where xsane got the "setup" device. Did you specify any
command line arguments? (You shouldn't).
I am searching around the "setup" device/step for xsane. I have been
looking around its website either.

Can any folk on the list help

B.Regards
Stephen Liu
Holger Drefs
2003-02-26 09:15:35 UTC
Permalink
Hello Stephen,
Post by Oliver Schwartz
Is your SCSI card recognised in Linux (i.e. what's the output of
"cat /proc/scsi/scsi")?
SL> $ cat /proc/scsi/scsi
SL> Attached devices:
SL> Host: scsi0 Channel: 00 Id: 00 Lun: 00
SL> Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e
SL> Type: CD-ROM ANSI SCSI revision: 02

SL> It looks the SCSI card detected.
Yes but there should be the scanner as well! This is the machine where
the scanner is attached or? Have you got /dev/sg0 .. sg7?

Forget about sane-find-scanner before your scanner isnŽt shown here.
Post by Oliver Schwartz
I don't know where xsane got the "setup" device. Did you specify any
command line arguments? (You shouldn't).
SL> I am searching around the "setup" device/step for xsane. I have been
SL> looking around its website either.

There is a net.conf in C:\sane\etc\sane.d or corresponding path in
linux, you should write here the ip-number of the machine where the
scanner is attached.

Best regards,
Holger Drefs
Stephen Liu
2003-02-26 10:38:59 UTC
Permalink
Hi Holger,

Thanks for your response.

Holger Drefs wrote:

- snip -
Post by Holger Drefs
Yes but there should be the scanner as well! This is the machine where
the scanner is attached or? Have you got /dev/sg0 .. sg7?
$ su
Password:
# locate sg0
/dev/sg0
/home/satimis/Mail/trash/cur/1046100409.1798.sg0n:2,S
# locate sg7
/dev/sg7
/usr/lib/wine/wine/msg711.drv.so

They are there.
Post by Holger Drefs
There is a net.conf in C:\sane\etc\sane.d or corresponding path in
linux, you should write here the ip-number of the machine where the
scanner is attached.
# locate net.conf
/etc/sane.d/net.conf

It is an empty file having following content it

# This is the net config file. Each line names a host to attach to.
# If you list "localhost" then your backends can be accessed either
# directly or through the net backend. Going through the net backend
# may be necessary to access devices that need special privileges.
# localhost

How to find out the ip-number of the scanner. It is a rather old
machine but still working on Windows

B.Regards
Stephen
Holger Drefs
2003-02-26 12:57:25 UTC
Permalink
Dear Stephen,

can you pls tell your general setup.

Is that like:
linux-machine
with scsi-card attached 1 cd-rom, 1 scanner
Xsane running on this machine?

Wednesday, February 26, 2003, 11:38:59 AM, you wrote:
SL> - snip -
Post by Holger Drefs
Yes but there should be the scanner as well! This is the machine where
the scanner is attached or? Have you got /dev/sg0 .. sg7?
SL> Password:
SL> # locate sg0
SL> /dev/sg0
SL> # locate sg7
SL> /dev/sg7
SL> They are there.

ok.

SL> It is an empty file having following content it

SL> # This is the net config file. Each line names a host to attach to.
SL> # If you list "localhost" then your backends can be accessed either
SL> # directly or through the net backend. Going through the net backend
SL> # may be necessary to access devices that need special privileges.
SL> # localhost

You should remove the '# ' before localhost, if you are using Xsane on
the same machine where the scanner is attached.
You must insert the ip-adress of the machine where the scanner is
attached if it is a different machine.

SL> How to find out the ip-number of the scanner. It is a rather old
SL> machine but still working on Windows

???
There is no ip-number for a scanner, only for machines in the network.
WHat do you mean with "but still working on windows"?

Cheerio,
Holger
Henning Meier-Geinitz
2003-02-26 13:29:44 UTC
Permalink
Hi,

On Wed, Feb 26, 2003 at 01:57:25PM +0100, Holger Drefs wrote:
[net.conf]
Post by Holger Drefs
You should remove the '# ' before localhost, if you are using Xsane on
the same machine where the scanner is attached.
Maybe I'm missing something here, but why shouldhe use saned /
net.conf at all? You can use saned as a workaround to not be root, but
that's only relevant for parport scanners.

Bye,
Henning
Holger Drefs
2003-02-26 14:07:24 UTC
Permalink
Hello Henning,

Wednesday, February 26, 2003, 2:29:44 PM, you wrote:
HMG> [net.conf]
Post by Holger Drefs
You should remove the '# ' before localhost, if you are using Xsane on
the same machine where the scanner is attached.
HMG> Maybe I'm missing something here, but why shouldhe use saned /
HMG> net.conf at all? You can use saned as a workaround to not be root, but
HMG> that's only relevant for parport scanners.

Oh sorry, I thought its always working in network mode. I came to sane
because of the network capabilities, never thought about using it only
locally where the scanner is attached.

Have a nice day
Holger
Stephen Liu
2003-02-26 16:07:50 UTC
Permalink
Hi Holger,
Post by Holger Drefs
can you pls tell your general setup.
linux-machine
with scsi-card attached 1 cd-rom, 1 scanner
Xsane running on this machine?
Standalone PC
OS RH7.3
Xsane installed as standard installation (I have no idea to run its setup)
IDE Writer
IDE CDRom
Scanner connected to a ISA SCSI card

as root #type sane
could not find it
# type xscane
xsane is /usr/bin/xsane
Post by Holger Drefs
- snip -
WHat do you mean with "but still working on windows"?
On the machine I have another hard disc mounted on a removable rack with
Windows ME installed

B.Regards
Stephen
Henning Meier-Geinitz
2003-02-26 13:08:08 UTC
Permalink
Hi,
Post by Stephen Liu
Post by Holger Drefs
Yes but there should be the scanner as well! This is the machine where
the scanner is attached or? Have you got /dev/sg0 .. sg7?
$ su
# locate sg0
/dev/sg0
Ok. Please tell us more about your system:

- Which SCSI card is used for your scanner?
- Is the SCSI driver for this card loaded?
- Is your SCSI cdrom connected to the same SCSI card or a different one?

Your problem is not related to xsane (that's "just" the graphical
application, the scanner access is done in the SANE backends).
It's a problem of your kernel or hardware. First make sure that your
scanner is detected in /proc/scsi/scsi, then you can go on with
sane-find-scanner, scanimage and xsane.
Post by Stephen Liu
Post by Holger Drefs
There is a net.conf in C:\sane\etc\sane.d or corresponding path in
linux, you should write here the ip-number of the machine where the
scanner is attached.
# locate net.conf
/etc/sane.d/net.conf
Ignore net.conf. At least if you don't want to use SANE over the
network, you don't need it.

Bye,
Henning
Stephen Liu
2003-02-26 16:23:47 UTC
Permalink
Hi Hwnninf,

Thanks for your response.
Post by Stephen Liu
- snip -
Standalone PC
OS RH7.3
Xsane installed as standard installation (I have no idea to run its setup)
IDE Writer
IDE CDRom
Scanner connected to a ISA SCSI card

- snip -
Post by Stephen Liu
Your problem is not related to xsane (that's "just" the graphical
application, the scanner access is done in the SANE backends).
It's a problem of your kernel or hardware. First make sure that your
scanner is detected in /proc/scsi/scsi, then you can go on with
sane-find-scanner, scanimage and xsane.
as root
# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e
Type: CD-ROM ANSI SCSI revision: 02

/var/log/messages
......
Feb 26 10:20:05 server kernel: scsi0 : SCSI host adapter emulation for
IDE ATAPI devices
Feb 26 10:20:05 server kernel: Vendor: SONY Model: CD-RW CRX160E
Rev: 1.0e
Feb 26 10:20:05 server kernel: Type: CD-ROM
........

I think the ISA SCSI card is not detected.

B.Regards
Stephen Liu
Henning Meier-Geinitz
2003-02-26 16:35:21 UTC
Permalink
Hi,
Post by Stephen Liu
Hi Hwnninf,
Well, I think my name is written slightly different :-)
Post by Stephen Liu
Standalone PC
OS RH7.3
Xsane installed as standard installation (I have no idea to run its setup)
You don't need to run any setup for XSane. The only thing you may need
to setup is the backends.
Post by Stephen Liu
IDE Writer
IDE CDRom
Ah, IDE not SCSI. So you use idescsi. That's why your IDE device is
found in /proc/scsi/scsi.
Post by Stephen Liu
Scanner connected to a ISA SCSI card
I think the ISA SCSI card is not detected.
Yes. So what did you do to load the driver and what happened? It's
explained in detail in the HTML page you referred to in your first post.
(Telling the computer about SCSI).

You have the same card as mentioned in this article?

Bye,
Henning
Stephen Liu
2003-02-27 09:07:30 UTC
Permalink
Hi Henning,

Henning Meier-Geinitz wrote:

- snip -
Post by Henning Meier-Geinitz
Post by Stephen Liu
I think the ISA SCSI card is not detected.
Yes. So what did you do to load the driver and what happened? It's
explained in detail in the HTML page you referred to in your first post.
(Telling the computer about SCSI).
You have the same card as mentioned in this article?
My SCSI card differs from the card mentioned in the article, without
jumpers to set I/O output. However my scanner works on Windows (I have
another hard disk mounted on a removable rack). For such a reason I
hesitate to move and seek advice from folks on the list. If I can't
find a solution from this listing I shall try, omitting the section in
re of setting jumpers to see what happens.

B.Regards
Stephen
Henning Meier-Geinitz
2003-02-27 09:40:19 UTC
Permalink
Hi,
Post by Stephen Liu
Post by Henning Meier-Geinitz
You have the same card as mentioned in this article?
My SCSI card differs from the card mentioned in the article, without
jumpers to set I/O output.
Ok, but it's an Adaptec 1505?
Post by Stephen Liu
However my scanner works on Windows (I have
another hard disk mounted on a removable rack). For such a reason I
hesitate to move and seek advice from folks on the list. If I can't
find a solution from this listing I shall try, omitting the section in
re of setting jumpers to see what happens.
Just load the driver and see what happens. If it doesn't work, try to
vary the io port address.

Bye,
Henning
Holger Drefs
2003-02-26 17:56:58 UTC
Permalink
Hello Stephen,

Wednesday, February 26, 2003, 5:23:47 PM, you wrote:
SL> Standalone PC
SL> OS RH7.3
SL> Xsane installed as standard installation (I have no idea to run its setup)
SL> IDE Writer
SL> IDE CDRom
SL> Scanner connected to a ISA SCSI card

ok

...
SL> as root
SL> # cat /proc/scsi/scsi
SL> Attached devices:
SL> Host: scsi0 Channel: 00 Id: 00 Lun: 00
SL> Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e
SL> Type: CD-ROM ANSI SCSI revision: 02

SL> /var/log/messages
SL> ......
SL> Feb 26 10:20:05 server kernel: scsi0 : SCSI host adapter emulation for
SL> IDE ATAPI devices
SL> Feb 26 10:20:05 server kernel: Vendor: SONY Model: CD-RW CRX160E
SL> Rev: 1.0e
SL> Feb 26 10:20:05 server kernel: Type: CD-ROM
SL> ........

SL> I think the ISA SCSI card is not detected.

I think you are right! Try to find out what type of scsi-card you have
installed. May be Win helps you with some information from device
manager, more or less the scsi chip is the decisive information you
should get.

With this information you should tell RH to load the appropriate driver
for that card. ItŽs very likely that Xsane will work afterwards.

Good luck!
Holger
Stephen Liu
2003-02-27 10:05:12 UTC
Permalink
Hi Holger,
Post by Stephen Liu
- snip -
I think you are right! Try to find out what type of scsi-card you have
installed. May be Win helps you with some information from device
manager, more or less the scsi chip is the decisive information you
should get.
Following information obtained from WinME on the same PC

Adapter AVA-1505 SCSI Host Adapter
AGFA EPPSCSI Miniport driver
Interrupt 09
I/O port 0140-015F
Driver;
C:Windows\system\iosubsys\sparrow.mpd
C:Windows\system\vmm32.vxd(ios.vxd)
Post by Stephen Liu
With this information you should tell RH to load the appropriate driver
for that card. ItŽs very likely that Xsane will work afterwards.
How to proceed?

B.Regards
Stephen
Henning Meier-Geinitz
2003-02-27 12:07:29 UTC
Permalink
Hi,
Post by Stephen Liu
Following information obtained from WinME on the same PC
Adapter AVA-1505 SCSI Host Adapter
AGFA EPPSCSI Miniport driver
Interrupt 09
I/O port 0140-015F
Ok. Use the same values with Linux. Does that work?
Post by Stephen Liu
How to proceed?
See "Telling the computer about SCSI" on the web page you quoted in
your first article.

Bye,
Henning
Stephen Liu
2003-02-27 14:45:27 UTC
Permalink
Hi Henning,
Post by Stephen Liu
- snip -
See "Telling the computer about SCSI" on the web page you quoted in
your first article.
su
password
cd /

[***@server /]# locate aha152x
/usr/src/linux-2.4.18-3/drivers/scsi/README.aha152x
/usr/src/linux-2.4.18-3/drivers/scsi/aha152x.c
/usr/src/linux-2.4.18-3/drivers/scsi/aha152x.h
/usr/src/linux-2.4.18-3/drivers/scsi/pcmcia/aha152x_stub.c
/lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o
/lib/modules/2.4.18-3/kernel/drivers/scsi/pcmcia/aha152x_cs.o
/lib/modules/2.4.18-3/pcmcia/aha152x_cs.o
/opt/ltsp/i386/lib/modules/2.4.18-ltsp-1/kernel/drivers/scsi/aha152x.o
/opt/ltsp/i386/lib/modules/2.4.18-ltsp-1/pcmcia/aha152x_cs.o

The driver is already existing

[***@server /]# /sbin/insmod scsi_mod
Using /lib/modules/2.4.18-3/kernel/drivers/scsi/scsi_mod.o
insmod: a module named scsi_mod already exists

[***@server /]# /sbin/insmod sg
Using /lib/modules/2.4.18-3/kernel/drivers/scsi/sg.o

[***@server /]# /sbin/insmod aha152x aha152x=140h, 9
Using /lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o
/lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o: invalid argument
syntax for aha152x: 'h'

[***@server /]# /sbin/insmod aha152x aha152x=140, 9
Using /lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o
/lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o: init_module: No
such device
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters

I will try again later following the complete steps as descibed in the
article mentioned previously including disable the plug and play software.

B.Regards
Stephen
Post by Stephen Liu
Bye,
Henning
_______________________________________________
Sane-devel mailing list
http://www.mostang.com/mailman/listinfo/sane-devel
Henning Meier-Geinitz
2003-02-27 14:58:41 UTC
Permalink
Hi,
Post by Stephen Liu
Using /lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o
/lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o: invalid argument
syntax for aha152x: 'h'
Please read the webpage again. There is no "140h". It's "0x140". And
there is no space after the comma. Now try:
insmod aha152x aha152x=0x140,9

If that doesn't work, try some combinations of the io port and irqs. I
remember that irq=10 worked for me, but that depends on your setup.

Bye,
Henning
Stephen Liu
2003-02-27 16:57:22 UTC
Permalink
Hi Henning,
Post by Stephen Liu
- snip -
Please read the webpage again. There is no "140h". It's "0x140". And
insmod aha152x aha152x=0x140,9
I tried several combinations but it said 'aha152x' already exists there

[***@server /]# /sbin/insmod aha152x aha152x=0x140,10
Using /lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o
insmod: a module named aha152x already exists
[***@server /]# /sbin/insmod aha152x aha152x=0x140,9
Using /lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o
insmod: a module named aha152x already exists
[***@server /]# /sbin/insmod aha152x aha152x=0x140,11
Using /lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o
insmod: a module named aha152x already exists
[***@server /]# /sbin/insmod aha152x aha152x=0x140,8
Using /lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o
insmod: a module named aha152x already exists
[***@server /]# /sbin/insmod aha152x aha152x=0x140,09
Using /lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o
insmod: a module named aha152x already exists

B.Regards
Stephen
Henning Meier-Geinitz
2003-02-27 17:01:42 UTC
Permalink
Hi,
Post by Stephen Liu
I tried several combinations but it said 'aha152x' already exists there
Using /lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o
insmod: a module named aha152x already exists
Well, yes, it already exists in the kernel :-) Tha means you have
loaded it successfully before. If you want to try again with some
other parameters, remove the module before loading it again: rmmod
aha152x. Have a look at the manpages for understanding what you are
doing (e.g. man insmod).

If the modules loaded without errors, you may be done. Check
/proc/scsi/scsi if your scanner is listed.

Bye,
Henning
Stephen Liu
2003-02-28 02:19:18 UTC
Permalink
Hi Henning


There is something strange. This morrning ater starting the machine,

su
password

# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e
Type: CD-ROM ANSI SCSI revision: 02

# /sbin/rmmod aha152x
rmmod: module aha152x is not loaded

# /sbin/insmod aha152x=0x140,10
Using /lib/modules/2.4.18-3/kernel/abi/cxenix/abi-cxenix.o/aha152x=0x140,10
insmod:
/lib/modules/2.4.18-3/kernel/abi/cxenix/abi-cxenix.o/aha152x=0x140,10:
Not a directory

B.Regards
Stephen
Post by Henning Meier-Geinitz
Hi,
Post by Stephen Liu
I tried several combinations but it said 'aha152x' already exists there
Using /lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o
insmod: a module named aha152x already exists
Well, yes, it already exists in the kernel :-) Tha means you have
loaded it successfully before. If you want to try again with some
other parameters, remove the module before loading it again: rmmod
aha152x. Have a look at the manpages for understanding what you are
doing (e.g. man insmod).
If the modules loaded without errors, you may be done. Check
/proc/scsi/scsi if your scanner is listed.
[***@server satimis]# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e
Type: CD-ROM ANSI SCSI revision: 02
Post by Henning Meier-Geinitz
Bye,
Henning
_______________________________________________
Sane-devel mailing list
http://www.mostang.com/mailman/listinfo/sane-devel
Martijn van Oosterhout
2003-02-28 03:24:15 UTC
Permalink
Post by Stephen Liu
# /sbin/insmod aha152x=0x140,10
Using /lib/modules/2.4.18-3/kernel/abi/cxenix/abi-cxenix.o/aha152x=0x140,10
Not a directory
Wrong command. The arguments are not part of the filename. Besides, you
should be using modprobe as it will take care of any possible dependancies.

# /sbin/modprobe aha152x aha152x=0x140,10

Though it might be:

# /sbin/modprobe aha152x io=0x140,10

Which would be more in line with other drivers.

NOTE: I don't own any scsi devices. I just use a CD burner at work.
--
Post by Stephen Liu
Support bacteria! They're the only culture some people have.
Stephen Liu
2003-02-28 08:37:36 UTC
Permalink
Hi Martijn,

Thanks for your response.

su
password

# /sbin/modprobe aha152x aha152x=0x140,10 (enter)
no response

# /sbin/modprobe aha152x aha152x=0x140,9 (enter)
it hanged there for long time compelling me to restart the Koncole Window

Restarted Konsole Window

# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: Model: Rev:
Type: <NULL> ANSI SCSI revision: ffffffff

Started 'Xsane'. After accepting the Licence, a warning popup saying
device not found.

su
password

# /sbin/rmmod aha152x
aha152x: Device or resource busy


I have to re-start the computer.

Also tried
/sbin/modprobe aha152x io=0x140,9
with the same result.


B.Regards
Stephen Liu
Post by Martijn van Oosterhout
Post by Stephen Liu
# /sbin/insmod aha152x=0x140,10
Using
/lib/modules/2.4.18-3/kernel/abi/cxenix/abi-cxenix.o/aha152x=0x140,10
Post by Martijn van Oosterhout
Post by Stephen Liu
Not a directory
Wrong command. The arguments are not part of the filename.
Besides, you
Post by Martijn van Oosterhout
should be using modprobe as it will take care of any possible
dependancies.
Post by Martijn van Oosterhout
# /sbin/modprobe aha152x aha152x=0x140,10
# /sbin/modprobe aha152x io=0x140,10
Which would be more in line with other drivers.
NOTE: I don't own any scsi devices. I just use a CD burner at work.
Holger Drefs
2003-02-28 09:15:58 UTC
Permalink
Dear Stephen,

Friday, February 28, 2003, 9:37:36 AM, you wrote:
SL> # /sbin/modprobe aha152x aha152x=0x140,10 (enter)
SL> no response

SL> # cat /proc/scsi/scsi
SL> Attached devices:
SL> Host: scsi0 Channel: 00 Id: 00 Lun: 00
SL> Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e
SL> Type: CD-ROM ANSI SCSI revision: 02
SL> Host: scsi1 Channel: 00 Id: 00 Lun: 00
SL> Vendor: Model: Rev:
SL> Type: <NULL> ANSI SCSI revision: ffffffff

SL> Started 'Xsane'. After accepting the Licence, a warning popup saying
SL> device not found.

It canŽt find anything because there is anything.

BUT, i found a step-by-step advisory for you, try this:
http://duvet.eee.nottingham.ac.uk/scanner/snapscan_310_linux.html

I could read that there is some more parameters and prerequisites
necessary for your card.

Best regards,
Holger

--

PS Being yealous on Henning because his mails go much faster into the
list, app. 1 hour less.
Pierre SOUCHAY
2003-02-28 10:14:01 UTC
Permalink
Hi,

To make it work on my machine (debian stable) :

/etc/modutils/actions :
----------
post-install aha152x modprobe sg
----------

/etc/modutils/aliases :
----------
alias scsi_host aha152x
options aha152x aha152x=0x140,10
alias /dev/sg1 scsi_host
----------

If you don't own a debian, put these 4 lines into your modules.conf.
Else, don't forget the update-modules command on debian !!

Regards.
Pierre Souchay
Stephen Liu
2003-02-28 12:45:54 UTC
Permalink
Hi folks

Lot of thanks for your advice. Thanks to Holger for the link which is
the same as on my 1st posting.

My problem is now half solved. The trick is I have to disable the Plug
and Play driver on the ISA SCSI card by following the steps described on
the aforesaid link

su
password

# /sbin/insmod sg
Using /lib/modules/2.4.18-3/kernel/drivers/scsi/sg.o
# /sbin/insmod aha152x aha152x=0x140,9,7,0
Using /lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o
# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 02 Lun: 00
Vendor: AGFA Model: SNAPSCAN 310 Rev: 1.90
Type: Scanner ANSI SCSI revision: 02

Starting 'Xsane' still could not detect the scanner (licence accepted).
I don't know its setup. Can any folk on the list shed me some light


Another strange thing is when I restart the PC I have to do 'insmod'
again otherwise the scanner could not be detected.

# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e
Type: CD-ROM ANSI SCSI revision: 02

The scanner disappeared. Any solution?

Thanks in advance.

B.Regards
Stephen
Post by Holger Drefs
Dear Stephen,
SL> # /sbin/modprobe aha152x aha152x=0x140,10 (enter)
SL> no response
SL> # cat /proc/scsi/scsi
SL> Host: scsi0 Channel: 00 Id: 00 Lun: 00
SL> Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e
SL> Type: CD-ROM ANSI SCSI revision: 02
SL> Host: scsi1 Channel: 00 Id: 00 Lun: 00
SL> Type: <NULL> ANSI SCSI revision: ffffffff
SL> Started 'Xsane'. After accepting the Licence, a warning popup saying
SL> device not found.
It canŽt find anything because there is anything.
http://duvet.eee.nottingham.ac.uk/scanner/snapscan_310_linux.html
I could read that there is some more parameters and prerequisites
necessary for your card.
Best regards,
Holger
--
PS Being yealous on Henning because his mails go much faster into the
list, app. 1 hour less.
Henning Meier-Geinitz
2003-02-28 12:56:51 UTC
Permalink
Hi,
Post by Stephen Liu
# cat /proc/scsi/scsi
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 02 Lun: 00
Vendor: AGFA Model: SNAPSCAN 310 Rev: 1.90
Type: Scanner ANSI SCSI revision: 02
Good.

Does sane-find-scanner find your scanner? Does it find it if you run
as user? If it only works as root, you must set up permissions for the
SCSI devices. See man sane-scsi and search for "permission".

When it's found by sane-find-scanner, try scanimage -L. If it's not
found, show us the output of

SANE_DEBUG_SNAPSCAN=255 scanimage -L

Bye,
Henning
Stephen Liu
2003-02-28 15:55:06 UTC
Permalink
Hi Henning,
Post by Stephen Liu
- snip -
Does sane-find-scanner find your scanner? Does it find it if you run
as user? If it only works as root, you must set up permissions for the
SCSI devices. See man sane-scsi and search for "permission".
I hesitate to proceed as "root" because a warning popup. I did all
configuration as user with 'su' command.

Sorry what 'permission' you are referring to? I could not find it on
man sane-scsi

as user
# sane-find-scanner
# Note that sane-find-scanner will find any scanner that is connected
# to a SCSI bus and some scanners that are connected to the Universal
# Serial Bus (USB) depending on your OS. It will even find scanners
# that are not supported at all by SANE. It won't find a scanner that
# is connected to a parallel or proprietary port.

sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 310 1.90" at device
/dev/sg1
sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 310 1.90" at device
/dev/sg
Post by Stephen Liu
When it's found by sane-find-scanner, try scanimage -L.
# scanimage -L

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).

(remark: the scanner has been turned on when starting the computer)
Post by Stephen Liu
If it's not found, show us the output of
SANE_DEBUG_SNAPSCAN=255 scanimage -L
# sane_debug_snapscan=255 scanimage -L

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages)
.
# sane_debug_snapscan=310 scanimage -L

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).

B.Regards
Stephen
Henning Meier-Geinitz
2003-02-28 17:09:48 UTC
Permalink
Hi,
Post by Stephen Liu
Post by Stephen Liu
- snip -
Does sane-find-scanner find your scanner? Does it find it if you run
as user? If it only works as root, you must set up permissions for the
SCSI devices. See man sane-scsi and search for "permission".
I hesitate to proceed as "root" because a warning popup.
If you do what I write there is no warning popup. I didn't say you
should do your usual scanning as root. Just the detection to find out
what's going on.
Post by Stephen Liu
Sorry what 'permission' you are referring to? I could not find it on
man sane-scsi
The permissions of the scsi devices (e.g. /dev/sg0). They must be set
up so the user can access them. Is this really not in your man page?
Aynway, it doesn't matter as the permissions semm to be set up
Post by Stephen Liu
as user
# sane-find-scanner
sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 310 1.90" at device /dev/sg1
Fine, there it is. So there is no need to run as root.
Post by Stephen Liu
Post by Stephen Liu
If it's not found, show us the output of
SANE_DEBUG_SNAPSCAN=255 scanimage -L
# sane_debug_snapscan=255 scanimage -L
No, please do exactly what I wrote. Hint: capital letters. Use
copy&paste to make sure that you don't make any mistakes.

If this doesn't produce any debug output, check that "snapscan" (in
this exact spelling) is in /etc/sane.d/dll.conf.

Bye,
Henning
Stephen Liu
2003-03-01 03:45:57 UTC
Permalink
Hi Henning,
Post by Stephen Liu
- snip -
The scanner has been turned before booting PC

# sane-find-scanner
# Note that sane-find-scanner will find any scanner that is connected
# to a SCSI bus and some scanners that are connected to the Universal
# Serial Bus (USB) depending on your OS. It will even find scanners
# that are not supported at all by SANE. It won't find a scanner that
# is connected to a parallel or proprietary port.

sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 310 1.90" at device
/dev/scanner
sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 310 1.90" at device
/dev/sg1
sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 310 1.90" at device
/dev/sgb


# ls -l /dev/sg1
crwxrwxrwx 1 satimis root 21, 1 Apr 11 2002 sg1
# ls -l /dev/sgb
lrwxrwxrwx 1 root root 3 Aug 24 2002 sgb -> sg1

I think my scanner uses /dev/sg1 (If wrong, please correct me)
as safety measure I also did

# chmod -c 0777 /dev/sg0
mode of `sg0' changed to 0777 (rwxrwxrwx)
Post by Stephen Liu
- snip -
No, please do exactly what I wrote. Hint: capital letters. Use
copy&paste to make sure that you don't make any mistakes.
# SANE_DEBUG_SNAPSCAN=255 scanimage -L
[sanei_debug] Setting debug level of snapscan to 255.
[snapscan] sane_snapscan_init
[snapscan] sane_snapscan_init: Snapscan backend version 1.4.7
[snapscan] add_device(/dev/sg0)
[snapscan] add_device: Detected (kind of) a SCSI device
[snapscan] mini_inquiry
[snapscan] snapscan_cmd
[snapscan] add_device: Is vendor "SONY" model "CD-RW CRX160E" a
supported scanner?
[snapscan] add_device: "SONY CD-RW CRX160E" is not one of AGFA SnapScan
300, 310, 600, 1212, 1236, e20, e25, e26, e40, e42, e50, e52 or e60
Acer 300, 310, 610, 610+, 620, 620+, 640, 1240, 3300, 4300 or 5300
Guillemot MaxiScan A4 Deluxe
[snapscan] sane_snapscan_get_devices (0xbffff498, 0)

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
[snapscan] sane_snapscan_exit


B.Regards
Stephen
Henning Meier-Geinitz
2003-03-01 10:56:39 UTC
Permalink
Hi,
sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 310 1.90" at device /dev/scanner
sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 310 1.90" at device /dev/sg1
sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 310 1.90" at device /dev/sgb
# ls -l /dev/sg1
crwxrwxrwx 1 satimis root 21, 1 Apr 11 2002 sg1
# ls -l /dev/sgb
lrwxrwxrwx 1 root root 3 Aug 24 2002 sgb -> sg1
I think my scanner uses /dev/sg1 (If wrong, please correct me)
You are right. The two other files are just links.
as safety measure I also did
# chmod -c 0777 /dev/sg0
mode of `sg0' changed to 0777 (rwxrwxrwx)
Not needed. If sane-find-scanner detects the scanner (as user), the
permissions are set up correctly.
# SANE_DEBUG_SNAPSCAN=255 scanimage -L
[sanei_debug] Setting debug level of snapscan to 255.
[snapscan] sane_snapscan_init
[snapscan] sane_snapscan_init: Snapscan backend version 1.4.7
[snapscan] add_device(/dev/sg0)
The snapscan backend looks for "/dev/sg0" not "/dev/sg1" or
"/dev/scanner" for some reason. Check snapscan.conf (somewhere in
/etc/sane.d/ or /usr/local/etc/sane.d/) and change /dev/sg0 to /dev/sg1.

Current versions of sane-backends don't have this hardcoded path so
I'm a bit surprised.

Please also have a look at man sane-snapscan.

Bye,
Henning
Stephen Liu
2003-03-01 14:39:22 UTC
Permalink
Hi Henning

Henning Meier-Geinitz wrote:

- snip -
Post by Henning Meier-Geinitz
The snapscan backend looks for "/dev/sg0" not "/dev/sg1" or
"/dev/scanner" for some reason. Check snapscan.conf (somewhere in
/etc/sane.d/ or /usr/local/etc/sane.d/) and change /dev/sg0 to /dev/sg1.
/etc/sane.d/snapscan.conf

Changed /dev/sg0 to /dev/sg1

PROBLEM SOLVED NOW. Xsane can be started to scan document.

However the scanned document can be saved in .jpg, png, pnm, format etc
but not .gif


Lot of thanks for your continue effort and time spent in advising me.
Also I hereby express my thanks to other folks on the list for their
effort giving me constructive advice/comment.

Although I have done lot of scanning in the past but on Windows only.
This is the first time for me to do scanning on Linux. I shall go
through the relevant documentation later.

One futher question:

On Windows I use 'PageKeeper' or "PaperPort' as desktop/platform for
collecting all scanned documents and combine them as files, how about on
Linux?
Post by Henning Meier-Geinitz
Current versions of sane-backends don't have this hardcoded path so
I'm a bit surprised.
Please also have a look at man sane-snapscan.
Yes. I will upgrade the software another time


B.Regards
Stephen
Henning Meier-Geinitz
2003-03-01 14:58:12 UTC
Permalink
Hi,
Post by Stephen Liu
/etc/sane.d/snapscan.conf
Changed /dev/sg0 to /dev/sg1
PROBLEM SOLVED NOW. Xsane can be started to scan document.
That's fine.
Post by Stephen Liu
However the scanned document can be saved in .jpg, png, pnm, format etc
but not .gif
Most free software doesn't support gif. There are some patent
restrictions and I guess the software authors don't want to pay fees :-)

Use one of the free formats instead (e.g. png).

Bye,
Henning
Dr. Jones
2003-03-01 15:51:11 UTC
Permalink
Another question to follow up my HP scanjet dilemma.

When I was running windows with my machine, the scanner worked just fine and rarely had more than a hiccup.

Is it possible that my HP scsi adapter card has gone bad/failed/died? How would I evaluate it to make sure it's the card at fault?

Scott
Henning Meier-Geinitz
2003-03-01 16:38:29 UTC
Permalink
Hi,
Post by Dr. Jones
When I was running windows with my machine, the scanner worked just
fine and rarely had more than a hiccup.
Is it possible that my HP scsi adapter card has gone bad/failed/died?
Possible: yes. Likely: no. At least I havne't ever destroyed any SCSI
card. And I have quite a lot of these cheap "came-with-scanner"
thingies.
Post by Dr. Jones
How would I evaluate it to make sure it's the card at fault?
Try it with some other operating system and/or on a different computer.

Bye,
Henning

Stephen Liu
2003-03-01 07:49:34 UTC
Permalink
Hi Henning,


KDE desktop
===========

Further to my late posting as at foot of this email. New discovery,
quite strange;


1) login as 'user'

# chmod -c 777 /dev/sg1
mode of `/dev/sg1' changed to 0777 (rwxrwxrwx)

I am allowed to change the permission even without issuing the command
# su
# password

After logout and re-login to the same 'user'

# ls -l /dev/sg1
crw------- 1 satimis root 21, 1 Apr 11 2002 /dev/sg1

permission cancelled

I also tried inptting 'su' command with the same result


2) login as 'root'

# chmod -c 777 /dev/sg1
mode of `/dev/sg1' changed to 0777 (rwxrwxrwx)

logout and re-login as 'root'

# ls -l /dev/sg1
crwxrwxrwx root 21, 1 Apr 11 2002 /dev/sg1

Permission was still there.

Logout and re-login as 'user'

Permission cancelled.

I could not find out its cause


B.Regards
Stephen






##############################
Post by Stephen Liu
- snip -
The scanner has been turned before booting PC

# sane-find-scanner
# Note that sane-find-scanner will find any scanner that is connected
# to a SCSI bus and some scanners that are connected to the Universal
# Serial Bus (USB) depending on your OS. It will even find scanners
# that are not supported at all by SANE. It won't find a scanner that
# is connected to a parallel or proprietary port.

sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 310 1.90" at device
/dev/scanner
sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 310 1.90" at device
/dev/sg1
sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 310 1.90" at device
/dev/sgb


# ls -l /dev/sg1
crwxrwxrwx 1 satimis root 21, 1 Apr 11 2002 sg1
# ls -l /dev/sgb
lrwxrwxrwx 1 root root 3 Aug 24 2002 sgb -> sg1

I think my scanner uses /dev/sg1 (If wrong, please correct me)
as safety measure I also did

# chmod -c 0777 /dev/sg0
mode of `sg0' changed to 0777 (rwxrwxrwx)
Post by Stephen Liu
- snip -
No, please do exactly what I wrote. Hint: capital letters. Use
copy&paste to make sure that you don't make any mistakes.
# SANE_DEBUG_SNAPSCAN=255 scanimage -L
[sanei_debug] Setting debug level of snapscan to 255.
[snapscan] sane_snapscan_init
[snapscan] sane_snapscan_init: Snapscan backend version 1.4.7
[snapscan] add_device(/dev/sg0)
[snapscan] add_device: Detected (kind of) a SCSI device
[snapscan] mini_inquiry
[snapscan] snapscan_cmd
[snapscan] add_device: Is vendor "SONY" model "CD-RW CRX160E" a
supported scanner?
[snapscan] add_device: "SONY CD-RW CRX160E" is not one of AGFA SnapScan
300, 310, 600, 1212, 1236, e20, e25, e26, e40, e42, e50, e52 or e60
Acer 300, 310, 610, 610+, 620, 620+, 640, 1240, 3300, 4300 or 5300
Guillemot MaxiScan A4 Deluxe
[snapscan] sane_snapscan_get_devices (0xbffff498, 0)

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
[snapscan] sane_snapscan_exit


B.Regards
Stephen
Henning Meier-Geinitz
2003-03-01 10:58:31 UTC
Permalink
Hi,
Post by Stephen Liu
Further to my late posting as at foot of this email. New discovery,
quite strange;
1) login as 'user'
# chmod -c 777 /dev/sg1
mode of `/dev/sg1' changed to 0777 (rwxrwxrwx)
I am allowed to change the permission even without issuing the command
# su
# password
After logout and re-login to the same 'user'
# ls -l /dev/sg1
crw------- 1 satimis root 21, 1 Apr 11 2002 /dev/sg1
permission cancelled
Your distribution has set up setting permissions automatically for
you when you are logged in locally. Isn't it nice :-)

This should be documented in your distribution's manual.

Bye,
Henning
Dr. Jones
2003-02-28 16:02:00 UTC
Permalink
Herr Meier-Geinitz:

I am having trouble getting sane and xsane set up on my system. I have an HP ScanJet 4c with the symbios SCSI card. It worked fine under windows and I notice in the sane docs that it should work with linux.

My problems may lie in the initial set up of sane, xsane and sane-frontends in my debian linux system. I read that I could run 'sane-find-scanner' and yet even after reinstalling sane and xsane, I could not run that command.

If I run 'locate sane' I get a host of directories where various sane files and folders exist. I am wishing I could purge everything related to sane from my system and then start afresh with a clean new setup of sane.

Any suggestions on how to accomplish this?

Scott
Henning Meier-Geinitz
2003-02-28 17:21:27 UTC
Permalink
Hi,
Sorry for starting a rant just at the beginning, it's not directed to
you only:

1) This is a mailing list. I'm not the only one who answers. Please do
not direct mails to me. If I can, I will answer. But most of the
time there are other developers or users who are qualified better.
2) Start a new thread when you don't respond to an existing message.
If you want to ask about a different topic, do not reply to an existing
message but write a new one. I nearly missed your message because
it was inside this thread.
Post by Dr. Jones
I am having trouble getting sane and xsane set up on my system. I
have an HP ScanJet 4c with the symbios SCSI card. It worked fine
under windows and I notice in the sane docs that it should work with
linux.
My problems may lie in the initial set up of sane, xsane and
sane-frontends in my debian linux system.
For most scanners, it's not necessary to set up any part of SANE at all.
Post by Dr. Jones
I read that I could run 'sane-find-scanner' and yet even after
reinstalling sane and xsane, I could not run that command.
You mean that that file is not found? So you didn't install it. Which
version of SANE do you use? In very old versions sane-find-scanner was
not installed.
Post by Dr. Jones
If I run 'locate sane' I get a host of directories where various sane
files and folders exist. I am wishing I could purge everything
related to sane from my system and then start afresh with a clean new
setup of sane.
If you use RPMs, just uninstall all the sane packages from your system
by using your package management tool or rpm directly.

As for your scanner: First load the SCSI driver for your symbios scsi
card and make sure it is detected (cat /proc/scsi/scsi).

Bye,
Henning
Dr. Jones
2003-02-28 21:57:44 UTC
Permalink
As a matter of update and additional information, here's what I find when I
checked on my SCSI adapter.

cat /proc/scsi/scsi produced the following output:

Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SONY Model: CDU5211 Rev: yys2
Type: cd-rom revision: 02 ANSI SCSI

Please bear in mind that my system's CD Rom drive is indeed a Sony model,
52x, but it is connect to the motherboard with a simple ribbon cabble to a
connector right next to the RAM slots. I called my system manufacturer and
was assured that my system has a CD ROM with IDE interface. For reasons
unknown to me, and perhaps very clear to some of you, my cd rom is somehow
being associated with the SCSI card I have installed in my system for my
scanner.

Here's information from the card itself:

SBC -2AA 94v-0
fcc id cmc 2502
27-95 rev b c2502-66500
3529
532 4HEGCPF

1) This is a mailing list. I'm not the only one who answers. Please do
not direct mails to me. If I can, I will answer. But most of the
time there are other developers or users who are qualified better.
2) Start a new thread when you don't respond to an existing message.
If you want to ask about a different topic, do not reply to an existing
message but write a new one. I nearly missed your message because
it was inside this thread.

Fair enough, Henning. I wouldn't want to answer everyone's questions
directly either.
Post by Dr. Jones
I am having trouble getting sane and xsane set up on my system. I
have an HP ScanJet 4c with the symbios SCSI card. It worked fine
under windows and I notice in the sane docs that it should work with
linux.
My problems may lie in the initial set up of sane, xsane and
sane-frontends in my debian linux system.
Post by Henning Meier-Geinitz
For most scanners, it's not necessary to set up any part of SANE at all.
I am running debian and have run apt-get install xsane as well as apt-get
install sane. Yeah, likely redundant, but damn...I am just trying to get
this scanner working.
Post by Dr. Jones
I read that I could run 'sane-find-scanner' and yet even after
reinstalling sane and xsane, I could not run that command.
Post by Henning Meier-Geinitz
You mean that that file is not found? So you didn't install it. Which
version of SANE do you use? In very old versions sane-find-scanner was
not installed.

Yes, I mean if I run 'locate sane-find-scanner' nothing is returned except
the prompt. How do I get that installed?
Post by Dr. Jones
If I run 'locate sane' I get a host of directories where various sane
files and folders exist. I am wishing I could purge everything
related to sane from my system and then start afresh with a clean new
setup of sane.
Post by Henning Meier-Geinitz
As for your scanner: First load the SCSI driver for your symbios scsi
card and make sure it is detected (cat /proc/scsi/scsi).

In loading my driver..where are suggesting I would find the driver files?

Scott
Henning Meier-Geinitz
2003-02-28 23:35:43 UTC
Permalink
Hi,
Post by Dr. Jones
As a matter of update and additional information, here's what I find when I
checked on my SCSI adapter.
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SONY Model: CDU5211 Rev: yys2
Type: cd-rom revision: 02 ANSI SCSI
Please bear in mind that my system's CD Rom drive is indeed a Sony model,
52x, but it is connect to the motherboard with a simple ribbon cabble to a
connector right next to the RAM slots. I called my system manufacturer and
was assured that my system has a CD ROM with IDE interface. For reasons
unknown to me, and perhaps very clear to some of you, my cd rom is somehow
being associated with the SCSI card I have installed in my system for my
scanner.
It's called "idescsi". A SCSI simulation usually used for CD writers.
So that's ok. With earlier kernel versions there was some trouble with
this emulation so you may want to remove it at least for testing
(rmmod idescsi).
Post by Dr. Jones
SBC -2AA 94v-0
fcc id cmc 2502
27-95 rev b c2502-66500
3529
532 4HEGCPF
I am running debian and have run apt-get install xsane as well as apt-get
install sane. Yeah, likely redundant, but damn...I am just trying to get
this scanner working.
Have a look ath the packages's descriptions. xsane is a frontend
(application) and the package "sane" includes some other frontends
(xscanimage, xcam and scanadf). The backends (drivers) are in the
package "libsane" which was probably installed by dependency.
sane-find-scanner and scanimage are in package "sane-utils".
Post by Dr. Jones
Post by Henning Meier-Geinitz
As for your scanner: First load the SCSI driver for your symbios scsi
card and make sure it is detected (cat /proc/scsi/scsi).
In loading my driver..where are suggesting I would find the driver files?
In the directory where you store your modules for your ckernel.
Something like /lib/modules/[version]/kernel/drivers/scsi .

Sorry, I don't know which driver is for your card. Search the net
and/or the hp backend homepage.

Bye,
Henning
Martijn van Oosterhout
2003-03-01 02:10:27 UTC
Permalink
Post by Dr. Jones
Yes, I mean if I run 'locate sane-find-scanner' nothing is returned except
the prompt. How do I get that installed?
apt-get install sane-utils

This is one reason why frontends are good (dselect,apititude). It would have
made sure you had all the bits rather than installing the bare minimum.

Also, if you don't know how to get a particular file, go to
http://www.au.debian.org/distrib/packages and type the filename at the
bottom of the page.
--
Post by Dr. Jones
Support bacteria! They're the only culture some people have.
Stephen Liu
2003-02-28 17:10:16 UTC
Permalink
Hi Henning,

Further to my later posting

I take following actions;

as user

su
password

[***@server /]# rpm -qa|grep sane
sane-backends-1.0.7-6
sane-frontends-1.0.7-2
xsane-0.84-2
sane-backends-devel-1.0.7-6

[***@server /]# sane-find-scanner
# Note that sane-find-scanner will find any scanner that is connected
# to a SCSI bus and some scanners that are connected to the Universal
# Serial Bus (USB) depending on your OS. It will even find scanners
# that are not supported at all by SANE. It won't find a scanner that
# is connected to a parallel or proprietary port.

sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 310 1.90" at device
/dev/sg1
sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 310 1.90" at device
/dev/sgb

[***@server /]# cd /dev/
[***@server dev]# ln -s sgb scanner
[***@server /]# ls -l /dev/sgb
lrwxrwxrwx 1 root root 3 Aug 24 2002 /dev/sgb -> sg1
[***@server dev]# cd /
[***@server /]# chmod -c 0777 /dev/sg1
mode of `/dev/sg1' changed to 0777 (rwxrwxrwx)

Start 'xsane'. After accepting the licence an Error warning popup
xane: no devices available

B.Regards
Stephen
Post by Henning Meier-Geinitz
Hi,
Post by Stephen Liu
# cat /proc/scsi/scsi
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 02 Lun: 00
Vendor: AGFA Model: SNAPSCAN 310 Rev: 1.90
Type: Scanner ANSI SCSI revision: 02
Good.
Does sane-find-scanner find your scanner? Does it find it if you run
as user? If it only works as root, you must set up permissions for the
SCSI devices. See man sane-scsi and search for "permission".
When it's found by sane-find-scanner, try scanimage -L. If it's not
found, show us the output of
SANE_DEBUG_SNAPSCAN=255 scanimage -L
Bye,
Henning
_______________________________________________
Sane-devel mailing list
http://www.mostang.com/mailman/listinfo/sane-devel
Frank
2003-03-01 04:16:36 UTC
Permalink
On Sat, 01 Mar 2003 06:10, Stephen Liu wrote:

Hi Stephen

As a technically inclined newbie I tried what you did and discovered the below
difference. Maybe might help you?

" Hi Henning,
"
" Further to my later posting
"
" I take following actions;
"
" as user
"
" su
" password
"
" [***@server /]# rpm -qa|grep sane
" sane-backends-1.0.7-6
" sane-frontends-1.0.7-2
" xsane-0.84-2
" sane-backends-devel-1.0.7-6
"
" [***@server /]# sane-find-scanner
" # Note that sane-find-scanner will find any scanner that is connected
" # to a SCSI bus and some scanners that are connected to the Universal
" # Serial Bus (USB) depending on your OS. It will even find scanners
" # that are not supported at all by SANE. It won't find a scanner that
" # is connected to a parallel or proprietary port.
"
" sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 310 1.90" at device
" /dev/sg1
" sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 310 1.90" at device
" /dev/sgb

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
In the following section I was sure to include exactly what sane-find-scanner
returned. In your case might I suggest : ( NB -Do not go as su! )

#cd /dev
#chmod -c 0777 sg1

I not sure why but I think in ensures 777 status to your sg1 file as local and
not possibly only as root. [ This also allowed me to see the double entry I
did know I had of my scanner when I issued xsane. I was given given a choice
in my case to select xxx/scanner or xxx/scanner0. Hmmmm........ Both worked.

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

"
" [***@server /]# cd /dev/
" [***@server dev]# ln -s sgb scanner
" [***@server /]# ls -l /dev/sgb
" lrwxrwxrwx 1 root root 3 Aug 24 2002 /dev/sgb -> sg1
" [***@server dev]# cd /
" [***@server /]# chmod -c 0777 /dev/sg1
" mode of `/dev/sg1' changed to 0777 (rwxrwxrwx)
"
" Start 'xsane'. After accepting the licence an Error warning popup
" xane: no devices available
"
" B.Regards
" Stephen
"
"
" Henning Meier-Geinitz wrote:
" > Hi,
" >
" > On Fri, Feb 28, 2003 at 08:45:54PM +0800, Stephen Liu wrote:
" >
" >># cat /proc/scsi/scsi
" >>Attached devices:
" >>Host: scsi0 Channel: 00 Id: 00 Lun: 00
" >> Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e
" >> Type: CD-ROM ANSI SCSI revision: 02
" >>Host: scsi1 Channel: 00 Id: 02 Lun: 00
" >> Vendor: AGFA Model: SNAPSCAN 310 Rev: 1.90
" >> Type: Scanner ANSI SCSI revision: 02
" >
" >
" > Good.
" >
" > Does sane-find-scanner find your scanner? Does it find it if you run
" > as user? If it only works as root, you must set up permissions for the
" > SCSI devices. See man sane-scsi and search for "permission".
" >
" > When it's found by sane-find-scanner, try scanimage -L. If it's not
" > found, show us the output of
" >
" > SANE_DEBUG_SNAPSCAN=255 scanimage -L
" >
" > Bye,
" > Henning
" > _______________________________________________
" > Sane-devel mailing list
" > Sane-***@www.mostang.com
" > http://www.mostang.com/mailman/listinfo/sane-devel
" >
"
"
"
"
" _______________________________________________
" Sane-devel mailing list
" Sane-***@www.mostang.com
" http://www.mostang.com/mailman/listinfo/sane-devel
"
"
--
Regards

Frank

***@snapafun.co.nz
025853824
Stephen Liu
2003-03-01 04:35:10 UTC
Permalink
Hi Frank,

Thanks for your advice.
Post by Stephen Liu
- snip -
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
In the following section I was sure to include exactly what sane-find-scanner
returned. In your case might I suggest : ( NB -Do not go as su! )
#cd /dev
#chmod -c 0777 sg1
I not sure why but I think in ensures 777 status to your sg1 file as local and
not possibly only as root. [ This also allowed me to see the double entry I
did know I had of my scanner when I issued xsane. I was given given a choice
in my case to select xxx/scanner or xxx/scanner0. Hmmmm........ Both worked.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
I have done that but can't help. When I started 'xsane' it did not
offer me selection. I think it is the problem of the simulated scsi
connection of the Cdwriter. If I remove it from /etc/grub.conf, the
CDwriter could not work.

B.R.
Stephen

- snip -
Henning Meier-Geinitz
2003-03-01 11:00:33 UTC
Permalink
Hi,
Post by Stephen Liu
I have done that but can't help. When I started 'xsane' it did not
offer me selection. I think it is the problem of the simulated scsi
connection of the Cdwriter. If I remove it from /etc/grub.conf, the
CDwriter could not work.
Generally speaking, idescsi may be a problem. But I don't think it's
the case here. The Snapscan backend didn't even try to access /dev/sg1.

Bye,
Henning
abel deuring
2003-02-28 10:37:32 UTC
Permalink
Post by Stephen Liu
Hi Martijn,
Thanks for your response.
su
password
# /sbin/modprobe aha152x aha152x=0x140,10 (enter)
no response
# /sbin/modprobe aha152x aha152x=0x140,9 (enter)
it hanged there for long time compelling me to restart the Koncole Window
Restarted Konsole Window
# cat /proc/scsi/scsi
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Type: <NULL> ANSI SCSI revision: ffffffff
That "smells" like a cabling problem or some other hardware issue. The
adapter driver seems to find some sort of deice, but probably can't read
the result of the usual SCSI INQUIRY command. At least the field "type"
should be "scanner" or perhaps "processor".

Please check /var/log/messages, if there is any entry from the aha152x
driver, when you insmod thatz module.

Abel
Holger Drefs
2003-02-27 17:29:26 UTC
Permalink
Hello Stephen,

What does lsmod show now?
What does cat /proc/scsi/scsi show now?

Thursday, February 27, 2003, 5:57:22 PM, you wrote:
SL> I tried several combinations but it said 'aha152x' already exists there
SL> [***@server /]# /sbin/insmod aha152x aha152x=0x140,10
...
SL> Using /lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o
SL> insmod: a module named aha152x already exists

Ok, so itŽs already loaded on system boot, you should find out which
parameters are used, because they are may be wrong.

Best regards,
Holger
Stephen Liu
2003-02-28 02:22:49 UTC
Permalink
Hi Holger,

Please see my reply to Henning

B.Regards
Stephen
Post by Holger Drefs
Hello Stephen,
What does lsmod show now?
What does cat /proc/scsi/scsi show now?
SL> I tried several combinations but it said 'aha152x' already exists there
...
SL> Using /lib/modules/2.4.18-3/kernel/drivers/scsi/aha152x.o
SL> insmod: a module named aha152x already exists
Ok, so itŽs already loaded on system boot, you should find out which
parameters are used, because they are may be wrong.
Best regards,
Holger
Oliver Schwartz
2003-02-27 17:50:16 UTC
Permalink
Post by Stephen Liu
I tried several combinations but it said 'aha152x' already exists there
You need to run "rmmod aha152x" before running insmod again.

The syntax (according to the source code of aha152x) is

insmod aha152x io=0x140 irq=9

-Oliver
Stephen Liu
2003-02-28 02:24:41 UTC
Permalink
Hi Oliver,

Please see my reply to Henning.

B.Regards
Stephen
Post by Oliver Schwartz
Post by Stephen Liu
I tried several combinations but it said 'aha152x' already exists there
You need to run "rmmod aha152x" before running insmod again.
The syntax (according to the source code of aha152x) is
insmod aha152x io=0x140 irq=9
-Oliver
_______________________________________________
Sane-devel mailing list
http://www.mostang.com/mailman/listinfo/sane-devel
Holger Drefs
2003-02-27 12:36:59 UTC
Permalink
Hello Stephen,

Thursday, February 27, 2003, 11:05:12 AM, you wrote:
SL> Following information obtained from WinME on the same PC
SL> Adapter AVA-1505 SCSI Host Adapter
SL> AGFA EPPSCSI Miniport driver
SL> Interrupt 09
SL> I/O port 0140-015F
Post by Holger Drefs
With this information you should tell RH to load the appropriate driver
for that card. ItŽs very likely that Xsane will work afterwards.
SL> How to proceed?

As Henning wrote you should load the appropriate driver for the adapter.
As google also would find for you, try this:
http://igloo.its.unimelb.edu.au/Webmail/tips/msg00262.html

You can try first the same settings as they are used in windows (irq 9,
i/o 140h.

Best regards,
Holger
Stephen Liu
2003-02-26 16:26:35 UTC
Permalink
Hi Henning,

Further to my late posting. Sorry for mis-typing your name

B.Regards
Stephen
Post by Henning Meier-Geinitz
Hi,
Post by Stephen Liu
Post by Holger Drefs
Yes but there should be the scanner as well! This is the machine where
the scanner is attached or? Have you got /dev/sg0 .. sg7?
$ su
# locate sg0
/dev/sg0
- Which SCSI card is used for your scanner?
- Is the SCSI driver for this card loaded?
- Is your SCSI cdrom connected to the same SCSI card or a different one?
Your problem is not related to xsane (that's "just" the graphical
application, the scanner access is done in the SANE backends).
It's a problem of your kernel or hardware. First make sure that your
scanner is detected in /proc/scsi/scsi, then you can go on with
sane-find-scanner, scanimage and xsane.
Post by Stephen Liu
Post by Holger Drefs
There is a net.conf in C:\sane\etc\sane.d or corresponding path in
linux, you should write here the ip-number of the machine where the
scanner is attached.
# locate net.conf
/etc/sane.d/net.conf
Ignore net.conf. At least if you don't want to use SANE over the
network, you don't need it.
Bye,
Henning
_______________________________________________
Sane-devel mailing list
http://www.mostang.com/mailman/listinfo/sane-devel
Loading...