[sane-devel] Parportscanner Mustek 600 III EP Plus.
Sun, 03 Apr 2005 22:50:39 +0000
Hi again !
Now I am starting from beginning, perhaps that helps me.
I have totaly erased my tarball sane installation and erased absolutely
all files with "sane" in it.
After that I have done a clean RPM sane reinstall with
"system-config-packages" and my FC3 cd's,
did also a upgrade with "up2date".
So my "sane" installation looks like this now:
I have gone thru the
http://penguin-breeder.org/sane/mustek_pp/#installation once again,
I have enabled the mustek_pp backend in my dll.conf
I have adjusted the mustek_pp.conf file to reflect my hardware setup.
I get this when I am going to verify that the driver is properly installed :
[root] # SANE_DEBUG_MUSTEK_PP=1 scanimage -L
[sanei_debug] Setting debug level of mustek_pp to 1.
........ here it frezzes, nothing happends....
I get this when I use sane-find-scanner to probe for my parallel port
[root] # sane-find-scanner -p
found possible Mustek parallel port scanner at "parport0"
So my scanner is recognized by sane-find-scanner -p, but sane frezzes,
perhaps my scanner is to old, so sane don't recognise the chip in the
Is there a way to check that the chip isn't to old ?
When I do this, I get :
[root] # 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.15
[mustek_pp] backend by Jochen Eisinger <firstname.lastname@example.org>
[mustek_pp] sanei_init: auto probing port
.......here it frezzes, nothing happends ................
When I do this, I get :
[root] # SANE_DEBUG_SANEI_PA4S2=128 scanimage -L
[sanei_pa4s2] sanei_pa4s2_open: detected ASIC id 1013
So obviously it seems that the chip in the scanner is recognized, isn't
that right ?
Why isn't my scanner working for me, I don't understand it, what am I
doing wrong, is there something that I forgett or have I done everything
I can possible do ?
Is it a problem that my scanner and printer sits at the same parport ?
Here is my var/log/messages
dhcppc0 kernel: parport0: PC-style at 0x378 (0x778), irq -930634906
Mar 31 15:45:35 dhcppc0 kernel: parport0: irq -930634906 in use,
resorting to polled operation
Mar 31 15:45:35 dhcppc0 kernel: parport0: Printer, Canon S750
Mar 31 15:45:35 dhcppc0 kernel: lp0: using parport0 (polling).
Mar 31 15:45:35 dhcppc0 kernel: lp0: console ready
Is it a problem here ?
What is irq -930634906 in use ?
Help me ....Don't frezze me out :-)