parallel port and SANE

[jurgen]

I have a trouble with my parallel port scanner. Under rh 7.3 the same configuration runs without any troubles. Under FC2 I have no idea what to do and what thing I should search through the Web to make it work. I don't think it's the problem of SANE version and even if it was it would recognize my scanner first. I guess the problem is in the parallel port.

/proc/ioports shows me this:
0378-037a : parport0
so it must correspond to 0x378, but:
# SANE_DEBUG_SANEI_PA4S2=128 scanimage -L
[sanei_debug] Setting debug level of sanei_pa4s2 to 128.
[sanei_pa4s2] sanei_pa4s2: interface called for the first time
[sanei_pa4s2] sanei_pa4s2_open: called for device '0x378'
[sanei_pa4s2] sanei_pa4s2_open: trying to connect to port
[sanei_pa4s2] pa4s2_open: trying to attach dev `0x378`
[sanei_pa4s2] pa4s2_init: static int first_time = 1
[sanei_pa4s2] pa4s2_init: called for the first time
[sanei_pa4s2] pa4s2_init: initializing libieee1284
[sanei_pa4s2] pa4s2_init: 1 ports reported by IEEE 1284 library
[sanei_pa4s2] pa4s2_init: port 0 is `parport0`
[sanei_pa4s2] pa4s2_init: allocating port list
[sanei_pa4s2] pa4s2_init: initialized successfully
[sanei_pa4s2] pa4s2_open: looking up port in list
[sanei_pa4s2] pa4s2_open: `0x378` is not a valid device name
[sanei_pa4s2] pa4s2_open: returning SANE_STATUS_INVAL
[sanei_pa4s2] sanei_pa4s2_open: connection failed

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).

Did anyone of you come across the same trouble with a parallel port scaner or printer or other device?

[spottyrover]

This is the answer to my question about the acer 320u. While it is not a parallel port but I remember seeing something about it in one of the web sites below
I think it was the www.sane-project.org page if not try http://snapscan.sourceforge.net

"You are going to have to configure sane in order to get your scanner to work. According to The Sane Project Page, your scanner functions good with the backend. Try checking The Sane Project Page or the SnapScan Backend page for directions on how to set up your scanner. Good luck."

sorry I can't help you any further

Dave

[jurgen]

The problem seems to be in sane-backends. I simply upgraded them. My scanner still does not work, but at least Sane can recognize it's been plugged-in. I guess a number of bugs still require to be fixed. Anyway, rh7.3 with the previous version of Sane solves my troubles. It's just switching that is irritating. Newer doesn't mean better. ;)

[edg]

You are probably trying to use the mustek_pp_ccd driver?
In that case, the format of the scanner description in /etc/sane.d/mustek_pp.conf has changed:
instead of using the parport address (0x378), you should use "parport0" or simply a "*" (auto-detect mode).
For more information, type "man sane-mustek_pp".

[edg]

Addendum: the driver needs the ppdev kernel module.
To check whether it is loaded: /sbin/lsmod | grep ppdev
In case the module doesn't get loaded automatically when you scan, try "modprobe ppdev" (as root) first and then try to scan again.

[jurgen]

ppdev is loaded and the config file modified. Scanner starts scanning, but after few seconds (say 0,5 cm) it stops with the lamp on.

[edg]

What kind of scanner do you have? Is it a Mustek 600CP or 1200CP or an OEM version?
The mustek_pp cis driver in version 1.0.13 of sane-backends has such a bug (see http://home.tiscali.be/EddyDeGreef/Sane/bug-1.0.13.html).
If you are using that driver (ie, if you specify cis600 or cis1200 in your mustek_pp.conf file), you should upgrade to 1.0.14. I've noticed that Fedora 3 test 1 includes it. You can probably just download and install the rpm from here:
http://download.fedora.redhat.com/pub/fedora/linux/core/development/i386/Fedora/RPMS/sane-backends-1.0.14-4.i386.rpm

[jurgen]

This is what I have got.

# SANE_DEBUG_MUSTEK_PP=128 scanimage -L
[sanei_debug] Setting debug level of mustek_pp to 128.
[mustek_pp] sane-mustek_pp, version 0.13-beta. build for SANE 1.0.14
[mustek_pp] backend by Jochen Eisinger <jochen.eisinger@gmx.net>
[mustek_pp] sanei_init: auto probing port
[mustek_pp] ccd_init: found scanner on port ``parport0'' (ASIC id 0xa5, CCD 1)
[mustek_pp] sane_attach: attaching device ``mustek-pp'' to port parport0 (driver ccd300 v0.11-devel by Jochen Eisinger)
[mustek_pp] ccd300_capabilities: 600 III EP Plus flatbed CCD (300 dpi) scanner
device `mustek_pp:mustek-pp' is a Mustek 600 III EP Plus flatbed (CCD 300 dpi)
[mustek_pp] sane_exit: all drivers unloaded

[edg]

I see nothing wrong, but I'm not familiar with the CCD type scanners.
Jochen is more likely to be able to help you.
His website has more info: http://penguin-breeder.org/sane/mustek_pp

Does scanimage -T pass all tests?

[jurgen]

This is what I recieve:
# scanimage -T
scanimage: scanning image of size 433x583 pixels at 24 bits/pixel
scanimage: acquiring RGB frame, 8 bits/sample
scanimage: reading one scanline, 1299 bytes... PASS
scanimage: reading one byte... PASS
scanimage: stepped read, 2 bytes... PASS
scanimage: stepped read, 4 bytes... PASS
scanimage: stepped read, 8 bytes... PASS
scanimage: stepped read, 16 bytes... PASS
scanimage: stepped read, 32 bytes... PASS
scanimage: stepped read, 64 bytes... PASS
scanimage: stepped read, 128 bytes... PASS
scanimage: stepped read, 256 bytes... PASS
scanimage: stepped read, 512 bytes... PASS
scanimage: stepped read, 1024 bytes... PASS
scanimage: stepped read, 2048 bytes... PASS
scanimage: stepped read, 2047 bytes... PASS
scanimage: stepped read, 1023 bytes... PASS
scanimage: stepped read, 511 bytes... PASS
scanimage: stepped read, 255 bytes... PASS
scanimage: stepped read, 127 bytes... PASS
scanimage: stepped read, 63 bytes... PASS
scanimage: stepped read, 31 bytes... PASS
scanimage: stepped read, 15 bytes... PASS
scanimage: stepped read, 7 bytes... PASS
scanimage: stepped read, 3 bytes... PASS

and than it stops.

Best Regards,
j.