[sane-devel] Re: Re: problem with umax_pp

stef svoltz@wanadoo.fr
Wed, 8 Sep 2004 19:00:21 +0200


On Wed, Sep 08, 2004 at 03:29:16PM +0200, Gerhard Jaeger wrote:
> On Wednesday 08 September 2004 16:10, Nicolas FRANCOIS (AKA El Bofo) wrote:
> > I've got a HP3200C on parport (AMD 2600+ on ASUS KT333 MB, Kernel 2.4,
> > sane-backend 1.0.14). After successfully installing the backend, I have
> > some problems with parport detection. Sometimes it partially works,
> > sometimes I'm told I haven't got a parport !
> >
> > An example :
> >
> > root:/usr/src/sane-backends-1.0.14/tools# ./umax_pp -p -t 1 -n
> > /dev/parport0
> > [sanei_debug] Setting debug level of umax_pp_low to 1.
> > [umax_pp_low] SANE_INB level 3
> > [umax_pp_low] sanei_umax_pp_InitPort(0x378,/dev/parport0)
> > [umax_pp_low] Using /dev/parport0 ...
> > UMAX 1220P scanning program version 5.1 starting ...
> > ppdev character device built-in.
> > direct hardware access built-in.
> > Probing scanner ....
> > [umax_pp_low] UMAX Astra 1220/1600/2000 P ASIC detected (mode=31)
> > [umax_pp_low] Unexpected value for for register 0x0D, expected 0x00 or
> > 0x40, got 0x18 ! (../backend/umax_pp_low.c:7406)
> > [umax_pp_low] 32 bits EPP data transfer
> > [umax_pp_low] Count-down value is 0x00  (../backend/umax_pp_low.c:7621)
> > [umax_pp_low] sendWord failed  got 0xE8 instead of 0xC0 or 0xD0

	This means scanner is in error. Something confused it.

> > (../backend/umax_pp_low.c:4550)
> > [umax_pp_low] Blindly going on .....
> > [umax_pp_low] sendWord failed: acknowledge not received
> > (../backend/umax_pp_low.c:4570)
> > [umax_pp_low] sendData failed  got 0xE8 instead of 0xC0 or 0xD0
> > (../backend/umax_pp_low.c:5400)
> > [umax_pp_low] Blindly going on .....
> > [umax_pp_low] sendData failed: acknowledge not received
> > (../backend/umax_pp_low.c:5423)
> > [umax_pp_low] sendWord failed  got 0xE8 instead of 0xC0 or 0xD0
> > (../backend/umax_pp_low.c:4550)
> > [umax_pp_low] Blindly going on .....
> > [umax_pp_low] sendWord failed: acknowledge not received
> > (../backend/umax_pp_low.c:4570)
> > [umax_pp_low] sendData failed  got 0xE8 instead of 0xC0 or 0xD0
> > (../backend/umax_pp_low.c:5400)
> > [umax_pp_low] Blindly going on .....
> > [umax_pp_low] sendData failed: acknowledge not received
> > (../backend/umax_pp_low.c:5423)
> > [umax_pp_low] sendData(data,2048) failed (../backend/umax_pp_low.c:5717)
> > [umax_pp_low] cmdSetDataBuffer(initbuf) failed !
> > (../backend/umax_pp_low.c:7675)
> >
> > This is what ppdiag tells me :
> >
> > root:/usr/src/sane-backends-1.0.14/tools# ppdiag
> > S01: parport built as module
> >
> > S02: parport0:
> > S02:    modes:PCSPP,TRISTATE,EPP
> > S02:    ADDR :0x378
> > S02:    IRQ  :no IRQ used
> > S02:    DMA  :no DMA used
> >
> > S03: no parport parameters
> >
> > S10: ppdev built as module
> >
> > S12: /dev/parport0 exists ...
> > S12: /dev/parport0 is readable ...
> > S12: /dev/parport0 is writable ...
> >
> > successfull end ....
> >
> > Funny, isn't it ? I'm completly stucked, so could you help a little, or
> > give me some pointer for more documentation ?
> >
> > \bye
> 
> Wrong list!!!
> I'll forward the request to: sane-standard@lists.alioth.debian.org
> 
> Gerhard
> 

	There are some things to test in such a case.
	- run the umax_pp tool in single user mode so that we get sure some 
	daemon isn't perturbing the scans
	- use direct hardware access (provide -a 0x378 option to umax_pp). I
	have grown the feeling that the linux parallel port support is faulty
	on some recent motherboards
	- try to set ECP+EPP in BIOS

Regards,
	Stef