[sane-devel] problems with Umax 1220P and Sane

[stef]

On Sun, Sep 02, 2001 at 07:48:22PM -0400, Afra Ahmad wrote:
> Hello,
> 
> I have read/searched past messages on the mailing list, and it doesn't
> seem like my problem has surfaced for anyone.
> 
> I downloaded sane 1.0.5 and applied the patches for the UMAX 1220P
> scanner, which patched fine (umax1220p-2.1.gz).
> 
> My scanner is the only device attached to the parallel port.
> 
> I set my BIOS to EPP+ECP and my kernel is Linux 2.4.9, which picks up the
> scanner alright:
> 
> parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE,COMPAT,ECP]
> parport0: irq 7 detected
> parport0: cpp_mux: aa55f00f52ad51(06)
> parport0: Found 1 daisy-chained devices
> lp0: using parport0 (polling).
> 
> (Yes, I did select CONFIG_PPDEV within the kernel).
> 

	I think your scanner uses the same ASIC that 600P/610P use, and is different
from the one currently supported in the umax_pp backend. Maybe older 1220P use one,
and newer another one. 

	When I do a 'modprobe lp', with both scanner and daisy-chaine printer
powered on, I get the following:

0x378: FIFO is 16 bytes
0x378: writeIntrThreshold is 16
0x378: readIntrThreshold is 16
0x378: PWord is 8 bits
0x378: Interrupts are ISA-Pulses
0x378: ECP port cfgA=0x10 cfgB=0x4b
0x378: ECP settings irq=7 dma=3
parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA]
parport0: Found 4 daisy-chained devices
parport0: faking semi-colon
parport0 probe: warning, class 'IMAGE' not understood.
parport0 (addr 0): Unknown device, UMAX Astra 1220P
parport0 (addr 1): Printer, EPSON Stylus COLOR 440
parport0 (addr 2): Printer, EPSON Stylus COLOR 440
parport0 (addr 3): Printer, EPSON Stylus COLOR 440
parport0: Printer, EPSON Stylus COLOR 440
lp0: using parport0 (interrupt-driven).

	What does your log report in this case ? Note in this case, and for
any UMAX 1220P reports I had, 4 daisy-chained devices are allways reported. 


> However, if I use umax_pp (as root) to test the scanner, I get this:
> 
> [sanei_debug] Setting debug level of umax_pp_low to 1.
> [umax_pp_low] Using /proc info
> UMAX 1220P scanning program version 2.1 starting ...
> [umax_pp_low] status 7 doesn't match! umax_pp_low.c:2055
> [umax_pp_low] No 1220P/2000P scanner detected by 'RingScanner()'...
> [umax_pp_low] Trying 610P...
> [umax_pp_low] Found 0x0 expected 0x88  (umax_pp_low.c:3649)
> [umax_pp_low] UMAX Astra 610P detected

	Your scanner is detected as a 610P, and support for this model isn't
complete. Only detection is working. So it fails where support stops....

> [umax_pp_low] Probe610P done ...
> [umax_pp_low] EPPRegisterRead, found 0xFF expected 0xC7
> (umax_pp_low.c:2827)
> [umax_pp_low] Error! expected STATUS=0x38, found 0x07!
> (umax_pp_low.c:4678)
> [umax_pp_low] SendWord610P failed, expected tmp=0xC8 , found 0x07
> (umax_pp_low.c:1927)
> [umax_pp_low] SendWord(zero) failed (umax_pp_low.c:3204)
> InitTransport() failed (umax_pp.c:400)
> 
> Does anyone know what is wrong? Obviously scanimage does not work either
> resulting in similar output.
> 
> Did I not set something correctly within the Linux kernel?
> 
> Thank you very much.
> 
> Afra
> 
> _______________________________________________
> Sane-devel mailing list
> Sane-devel@www.mostang.com
> http://www.mostang.com/mailman/listinfo/sane-devel


Regards,
	Stef