[sane-devel] CanoScan LiDE 25 problem resolved / Thanks, Henning

2005-10-15 Thread Daniel Mang
is outdated, according to you, right? (You say: "> That's correct. The kernel scanner module hasn't existes anymore since quite some time.>") Bye Daniel On Saturday 15 October 2005 12:48, Henning Meier-Geinitz wrote: > Hi, > > On Sat, Oct 15, 2005 at 09:44:3

[sane-devel] CanoScan LiDE 25 problem

2005-10-15 Thread Daniel Mang
calling backend `sp15c's exit function [dll] sane_exit: calling backend `snapscan's exit function [dll] sane_exit: calling backend `sm3840's exit function [dll] sane_exit: calling backend `sm3600's exit function [dll] sane_exit: calling backend `sharp's exit function [dll] sane_exit: calling backend `sceptre's exit function [dll] sane_exit: calling backend `s9036's exit function [dll] sane_exit: calling backend `ricoh's exit function [dll] sane_exit: calling backend `qcam's exit function [dll] sane_exit: calling backend `plustek's exit function [plustek] sane_exit [dll] sane_exit: calling backend `pie's exit function [dll] sane_exit: calling backend `niash's exit function [dll] sane_exit: calling backend `nec's exit function [dll] sane_exit: calling backend `mustek_usb's exit function [dll] sane_exit: calling backend `mustek's exit function [dll] sane_exit: calling backend `microtek2's exit function [dll] sane_exit: calling backend `microtek's exit function [dll] sane_exit: calling backend `matsushita's exit function [dll] sane_exit: calling backend `ma1509's exit function [dll] sane_exit: calling backend `leo's exit function [dll] sane_exit: calling backend `ibm's exit function [dll] sane_exit: calling backend `hp5400's exit function [dll] sane_exit: calling backend `hpsj5s's exit function [dll] sane_exit: calling backend `hp's exit function [dll] sane_exit: calling backend `gt68xx's exit function [dll] sane_exit: calling backend `genesys's exit function [dll] sane_exit: calling backend `fujitsu's exit function [dll] sane_exit: calling backend `epson's exit function [dll] sane_exit: calling backend `dmc's exit function [dll] sane_exit: calling backend `coolscan2's exit function [dll] sane_exit: calling backend `coolscan's exit function [dll] sane_exit: calling backend `canon630u's exit function [dll] sane_exit: calling backend `canon's exit function [dll] sane_exit: calling backend `bh's exit function [dll] sane_exit: calling backend `artec_eplus48u's exit function [dll] sane_exit: calling backend `artec's exit function [dll] sane_exit: calling backend `avision's exit function [dll] sane_exit: calling backend `apple's exit function [dll] sane_exit: calling backend `agfafocus's exit function [dll] sane_exit: calling backend `abaton's exit function [dll] sane_exit: calling backend `net's exit function [dll] sane_exit: finished I guess the relevant lines here are: [plustek] usbDev_open(auto,0x04A9-0x2220) - 0x80729b0 [plustek] sanei_access_lock failed: 11 [plustek] open failed: -1 (or did miss something else?) But what is sanei_access_lock and why does it fail? This seems to be the same problem identified by Gerhard Jaeger in his email to this list on Mon Jul 18 08:26:58 UTC 2005. I have not tried the solution he proposed yet because from what I understood from a subsequent email it did not entirely resolve the problem. The proposed solution (reinstalling with configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var) seems to have been superseded by some later proposals, which I don't understand or don't have the skills to apply -or has it? Thanks in advance for your comments Daniel Mang