[sane-devel] Umax 1220P not detected with /dev/parport0

[Ryan Harkin]

Hi Stef,

Sorry, I accidently sent the last email before I finished typing it!  Here's 
the complete message.....

Thanks for getting back to me so quickly.

Unfortunately, this isn't the problem that I am experiencing.  My computer was 
originally set for ECP/EPP when I had SuSE 7.2.  I could not get the scanner 
to work at all (directio or ppdev).  A simple change to EPP only and it 
sprung into life!

Now, I have tried some of the latest distros as I mentioned (all with kernel 
2.4.19 as you guessed) and cannot get the scanner to work in EPP only mode.  
So I have tried your suggestions and switched back to ECP/EPP and now I get 
no response whatsoever.

Whilst I could drop back to kernel 2.4.18.0, this could only be seen as a 
temporary solution, as you can imagine.  I can't go back any earlier because 
GCC 3.0.1 will not compile any earlier kernels than 2.4.18.0, IIRC.  For now, 
I'd rather just use directio, EPP and root user to scan when I need to.

Here's my latest results.

With directio:
--------------

# SANE_DEBUG_UMAX_PP=255 scanimage -L
[sanei_debug] Setting debug level of umax_pp to 255.
[umax_pp] init: SANE_Auth_Callback not supported (yet) ...
[umax_pp] init: SANE v1.0.9-pre1, backend v1.0.8-devel
[umax_pp] init: evaluating option <option buffer 2097152>
[umax_pp] init: option buffer 2097152
[umax_pp] init: setting global option buffer to 2097152
[umax_pp] init: trying port `0x378'
[umax_pp] attach(0x378)
[umax_pp_low] TestVersion(0) (umax_pp_low.c:4423) failed ...
[umax_pp_low] TestVersion(0) (umax_pp_low.c:4439) failed ...
[umax_pp_low] Found 0x0 expected 0xC7 or 0x88  (umax_pp_low.c:4519)
[umax_pp] attach: failed to probe scanner on 0x378
[umax_pp] attach: couldn't attach to `0x378' (Error during device I/O)
[umax_pp] umax_pp(v1.0.8-devel): line 246: debug exception
[umax_pp] init: couldn't attach to port `0x378'
[umax_pp] get_devices
[umax_pp] unused arg: local_only = 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).
[umax_pp] sane_exit: (...)


With ppdev:
-----------
# SANE_DEBUG_UMAX_PP=255 scanimage -L
[sanei_debug] Setting debug level of umax_pp to 255.
[umax_pp] init: SANE_Auth_Callback not supported (yet) ...
[umax_pp] init: SANE v1.0.9-pre1, backend v1.0.8-devel
[umax_pp] init: evaluating option <option buffer 2097152>
[umax_pp] init: option buffer 2097152
[umax_pp] init: setting global option buffer to 2097152
[umax_pp] init: trying port `/dev/parport0'
[umax_pp] attach(/dev/parport0)
[umax_pp] attach: failed to probe scanner on /dev/parport0
[umax_pp] attach: couldn't attach to `/dev/parport0' (Error during device I/O)
[umax_pp] umax_pp(v1.0.8-devel): line 246: debug exception
[umax_pp] init: couldn't attach to port `/dev/parport0'
[umax_pp] get_devices
[umax_pp] unused arg: local_only = 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).
[umax_pp] sane_exit: (...)



If I test using umax_pp, I get the following:

# ./umax_pp -p -t 255
[sanei_debug] Setting debug level of umax_pp_low to 255.
[umax_pp_low] no '/dev/io' device
UMAX 1220P scanning program version 2.15 starting ...
ppdev character device built-in.
direct hardware access built-in.
Probing scanner ....
[umax_pp_low] status 6 doesn't match! umax_pp_low.c:2662
[umax_pp_low] No scanner detected by 'RingScanner(2,0)'...
[umax_pp_low] status 6 doesn't match! umax_pp_low.c:2662
[umax_pp_low] No scanner detected by 'RingScanner(5,0)'...
[umax_pp_low] status 6 doesn't match! umax_pp_low.c:2662
[umax_pp_low] No scanner detected by 'RingScanner(5,10000)'...
[umax_pp_low] status 6 doesn't match! umax_pp_low.c:2662
[umax_pp_low] No scanner detected by 'RingScanner(5,10000)'...
[umax_pp_low] RingScanner passed...
[umax_pp_low] SendCommand(0x30) passed ... (umax_pp_low.c:4412)
[umax_pp_low] SendCommand(0x00) passed... (umax_pp_low.c:4419)
[umax_pp_low] status 0 doesn't match count 0xF0! umax_pp_low.c:2860
[umax_pp_low] TestVersion(0) (umax_pp_low.c:4423) failed ...
[umax_pp_low] TestVersion(0) passed...
[umax_pp_low] status 0 doesn't match count 0xF0! umax_pp_low.c:2860
[umax_pp_low] TestVersion(1) failed (expected) ... (umax_pp_low.c:4430)
[umax_pp_low] status 0 doesn't match count 0xF0! umax_pp_low.c:2860
[umax_pp_low] TestVersion(0) (umax_pp_low.c:4439) failed ...
[umax_pp_low] TestVersion(0) passed...
[umax_pp_low] status 0 doesn't match count 0xF0! umax_pp_low.c:2860
[umax_pp_low] TestVersion(1) failed (expected) ... (umax_pp_low.c:4446)
[umax_pp_low] SendCommand(0x40) passed...
[umax_pp_low] SendCommand(0xE0) passed...
[umax_pp_low] ClearRegister(0) passed...
[umax_pp_low] SPPResetLPT() passed...
[umax_pp_low] Found 0x0 expected 0xC7 or 0x88  (umax_pp_low.c:4519)


# ./umax_pp -p -t 255 -n /dev/parport0
[sanei_debug] Setting debug level of umax_pp_low to 255.
[umax_pp_low] parport modes: 43
[umax_pp_low] parport modes:
                PARPORT_MODE_PCSPP
                PARPORT_MODE_TRISTATE

[umax_pp_low] port 0x378 does not have EPP or ECP, giving up ...
failed to gain direct acces to port 0x378!

[Note, I am now using 1.0.9-pre1 with my little debug lines as per the first 
email.]

I'll try my other BIOS settings and see what they do, but you can assume that 
they failed if I don't get back to you on this list.

Thanks,
Ryan.