Hello Henning Thanks for the quick and helpful answer. The scanner is working now. I used the snapshot, disabled locking and otherwise followed all the instructions in Plustek-USB.txt. Although what it says there about using modprobe scanner to ascertain if the scanner device driver is loaded 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:30AM +0200, Daniel Mang wrote: > > I read the email exchange regarding LiDE 25 in the july 2005 sane-devel > > mailinglist archives but could not understand if the problem was really > > resolved at that time. I also read the september and october email > > exchanges on sane-devel regarding LiDE 25 and tried my best to understand > > them but I have a hard time doing so. It seems I need a patch for > > plustek? And that I can get this patch via CVS, whatever that is? It was > > obvious to me from the beginning that the most up-to-date software is on > > the CVS page, but since I am totally unfamiliar with CVS I stayed away > > from it. > > On the CVS page there is also a link to documentation about CVS. And > you can download files directly via the web (link "Browse CVS > Repository(cvsweb)"). > > Anyway, you can also download a complete snapshot of the development > version of sane-backends instead. This snapshot is generated > automatically every day. The link is on the download page. > > > I use SuSE 9.3 > > YaST recognizes the scanner but it is not on the list of scanners, so > > setting up plustek via YaST doesn't work. > > Tools like YaST that just hide operations are not a big help for new > scanners most of the time. > > > I gathered from the mailing list archives that LiDE 25 support was added > > only recently, so I first tried getting newer SANE versions via YaST. > > SuSE (and most other distributions) only provide new packages of SANE > when there is a new stable version. > > > But when I am all done, whether I do: > > > > modprobe scanner > > > > or: > > > > modprobe scanner vendor=0x04a9 product=0x2220 > > > > the result is always: > > > > FATAL: Module scanner not found. > > That's correct. The kernel scanner module hasn't existes anymore since > quite some time. > > > found USB scanner (vendor=0x04a9 [Canon], product=0x2220 [CanoScan], > > chip=LM9832/3) at libusb:002:002 > > Looks fine. > > > scanimage -L > > > > I get: > > > > No scanners were identified. > > > > I have edited the plustek configuration file (in my case it > > is /etc/sane.d/plustek.conf), adding the lines: > > If you installed from source code and didn't change the default > directories, the file is in /usr/local/etc/sane.d, not in /etc. > > > [plustek] Plustek backend V0.50-4, part of sane-backends 1.0.16 > > Seems to be current. > > > [plustek] sanei_access_lock failed: 11 > > > > I guess the relevant lines here are: > > > > [plustek] usbDev_open(auto,0x04A9-0x2220) - 0x80729b0 > > [plustek] sanei_access_lock failed: 11 > > [plustek] open failed: -1 > > Yes. > > > (or did miss something else?) > > No. > > > But what is sanei_access_lock and why does it fail? > > Read the archive of this list :-) > Either make sure that you can write to the lock directory or just disable > locking: ./configure --disable-locking > > Bye, > Henning