plustek@linuxhacker.org

Hi,

On Sonntag, 28. September 2003 15:45, Martin Biallas wrote:
[SNIPSNAP]
> The problems start with the use of scanimage. In two of three cases
> scanimage -L suceeds and delivers plustek:/dev/usb/scanner0  . In the
> other cases, a kernel panic is caused.
> In rare cases it is possible to start
> scanimage -d plustek:/dev/usb/scanner0 and hear a "toc"-like sounding
> life-sign (perhaps a starting motor) of the scanner, before the kernel
> panic pops up. Most times the kernel panic pops up before the scanner
> does anything.
>
> The the last lines of the scanimage -d plustek:/dev/usb/scanner0
> command, when a export SANE DEBUG DLL=12 and export
> SANE DEBUG PLUSTEK=12 proceeded, are like (scanner did nothing):
>
> [plustek] * Totalbytes 2151031668
> [plustek] * PL: 295 , coeffsize = 216 , scaler = 1
> [plustek] * PauseLimit = 295 , [0x4e]=0x91 , [0x4f]=0x01
> [plustek] usb SetScanParameters() done.
>
What's the output of SANE DEBUG PLUSTEK=255?
Do you see the kernel-oops message?

To be honest, I've never seen this behaviour, but I use kernel
2.4.21 without the kernel scanner module. It might be a good idea
to try also libusb if the kernel still makes problems...

Gerhard