plustek@linuxhacker.org
plustek@linuxhacker.org
Hi,
thank you for the answer ...
On Mon, Sep 29, 2003 at 09:26:54AM +0200, Gerhard Jaeger wrote:
...
> > 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?
I don't notice any kernel-ooops messages. When SANE_DEBUG_PLUSTEK=255 is
used, the last lines before the kernel-panic starts look like:
[plustek] Device description for >0x04B8-0x011D< found.
[plustek] usb_initDev (32,0x04B8,0)
[plustek] Device WAF: 0x00000002
[plustek] usb_switchLampX (N=0, TPA=1)
[plustek] Switch Lamp: 0 , regs [0x59] = 0x00
----- here the kenerl panic began. In a second try, the above and the
following was readable before the kernel-panic message:
[plustek] REG[0x02]=0x81
[plustek] TPA NOT detected
[plustek] Vendor adjusted to: >Epson<
[plustek] REG[0x5b]=0x19 (msk=0x80)
[plustek] LAMP-STATUS: 0x00000000
[plustek] RESETTING REGISTERS(0)
[plustek] MISC I/O after RESET: 0x41, 0x44, 0x14
> 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...
Well, I guess I will go for a newer kernel. This may take a while. I'll
let you know when the scanner works.
Regards,
Martin
--
Email-Address: martin.biallas@web.de , PGP Key-ID: 9E753FE0
plustek@linuxhacker.org