This is a multi-part message in MIME format.
--=_NextPart_000_0001_01C3D2FF.57805EF0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Re: [sane-devel] mustek_pp trouble
- Original Message -=20
From: jim.geo...@blueyonder.c
On 02-01-04 22:49:12 Jim George wrote:
> I tried that but got the following before I'd had a chance to run
> scanimage.
>
> Have a lot of fun...
> tassi:~ # SANE_DEBUG_MUSTEK_PP=255 gdb saned
> ...
> (gdb) r -d128
> Starting program: /usr/sbin/saned -d128
> [saned] main: starting debug mode (level
Hi,
Jim George wrote:
> [sanei_pa4s2] sanei_pa4s2_open: could not find scanner
> [sanei_pa4s2] sanei_pa4s2_open: reported ASIC id 0xb5
this looks like the backend couldn't find your scanner (0xa5 would have
been a valid ID for example)
> [sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with valu
Hi,
On Fri, Dec 26, 2003 at 10:21:27PM -, Jim George wrote:
> I did enable SANE_DEBUG_SANEI_PA4S2=255 and retried scanimage (although
> not through saned). The result is in the attached file, does it help to
> explain what's going on? To me it seems more confusing than ever.
The scanner was
Op 26-12-03 16:36:05 schreef Henning Meier-Geinitz:
> So either the mustek_pp backend is in an endless loop here or it
> exited for some reason. If it were in an endless loop, saned wouldn't
> exit (but it does, doesn't it?). You don't get a segmantation fault
> after saned has exited?
>
> Ok, let
--=_20031226222127_61890
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
> Hi,
>
> On Fri, Dec 26, 2003 at 04:22:18PM -, Jim George wrote:
...SNIP...
>
> These are the last few lines:
>
> [saned] process_request: waiting for request
> [saned] process_request: g
Hi,
On Fri, Dec 26, 2003 at 04:22:18PM -, Jim George wrote:
> I don't understand what's happening here :( I checked the connection of
> the scanner on the parallel port and then re-did the scanimage with
> SANE_DEBUG_MUSTEK_PP=255 (I didn't use SANE_DEBUG_SANEI_PA4S2=255 because
> it filled m
