2006/4/11, Gerhard Jaeger <[email protected]>: > > On Tuesday 11 April 2006 10:14, Fibonacci Prower wrote: > > Update: I tried with xsane, and... it still jams. And it hasn't yet > jammed > > under Windows. > > > > -Fibo > > > > 2006/4/5, Fibonacci Prower <[email protected]>: > > > > > > Hello, > > > First of all, I have no experience whatsoever with Linux, so I > > > apologise in advance for any stupidity I might have made, or detail I > > > might have omitted. That being said, I can proceed: > > > > > > I have just installed Fedora Core 5 (2.6.15-1.2054_FC5smp), and I'm > > > trying to use the CanoScan LiDE20 scanner which, according to > > > http://www.sane-project.org/sane-mfgs.html, is completely supported by > > > SANE. sane-find-scanner detects it, but it jams (with the lamps on) > > > whenever I try to scanimage, and nothing short of unplugging it from > > > the PC will stop it. I reboot to Windows XP (ahh, the magic of > > > dual-boot), and it scans perfectly well, not jamming at all (which > > > proves that the scanner is working fine). > > > I then reboot to Linux, sane-find-scanner finds it again, and > > > scanimage makes it jam again. Terminating scanimage gives only a > > > "Trying to stop scanner" message, but the scanner does not stop until > > > I unplug it. Trying to run scanimage again (with the scanner plugged > > > back in, of course) results in "scanimage: no SANE devices found", > > > even though sane-find-scanner still sees it. > > > > > > What can I do about this problem? > > > > > > Thank you for your time, > > > > > > -Fibonacci > > > > > > Hi, > > again my questions: > Which SANE version?
1.0.17, apparently. Which XSANE settings to scan? Ehm... the default settings? I didn't touch anything. Preview scan? Yes. 150DPI scan? Haven't yet learnt how to do that. And please don't answer directly to me, use the mailing list. > TIA > Gerhard > > > -- > sane-devel mailing list: [email protected] > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to [email protected] > -- Ding dong! The bitch is dead! Which old bitch? The wicked bitch! Ding dong! The wicked bitch is dead! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060411/c4a05171/attachment.html From [email protected] Wed Apr 12 01:19:35 2006 From: [email protected] (Patrick Lessard) Date: Wed Apr 12 15:55:25 2006 Subject: [sane-devel] Umax Astra 2100U incorporated into umax1220u backend In-Reply-To: <[email protected]> References: <[email protected]> <[email protected]> Message-ID: <[email protected]> Hi, Here are the comments and corrections. New version attached. On Sunday 09 April 2006 17:42, Henning Meier-Geinitz wrote: > Hi, > > On 2006-03-31 13:05, Patrick Lessard wrote: > > I did incorporate it into the backend. > > Thanks. I'm currently looking at the code. I can't actually test it > because I don't have such a scanner so this is only theoretically. > > It would be good if somebody could test your current code with a Astra > 1220U just to make sure that nothing is broken. > > Comments: > in umax1220-common.c: > - Any reason to partly remove the DEBUG_BOUNDS code (and a + PAD > somewhere)? DEBUG_BOUNDS is actually there. PAD is corrected, I've added it back. > - can all scanners cope with the bigger buffers: > - req = n = (len > 0xf000) ? 0xf000 : len; > + req = n = (len > 0xff00) ? 0xff00 : len; I've change it back to 0xf000. It works fine with the 2100U > - it looks like while you added move_2100, you also changed something > in move () itsself (sending longer buffers to the scanner with cwrite). > Does this also work with the 1220U? I've just moved the ope[8] in the functions , it was a global array. I also removed the { } in the "if (rev)" since there is only 1 instruction. > in umax1220u.c: > - Why is the call to sanei_pv8630_init () removed? Without this I > think you can't use debugging for sanei_pv8630. My work was based on version 1.0.16. This was not present in that version. I've added it and retested everything with version 1.0.17. Compiled and works fine. > - Is there no problem removing this uncondinionally? > - res = UMAX_set_lamp_state (&scanner->scan, UMAX_LAMP_OFF); > Actually, I suggest removing this instruction. This cause the lamp to turn off when quitting the frontend. If you start the frontend again, the lamp do not warm up and cause darker scans at first. Only after 1 or 2 scans, it goes back fine. I'm speaking about the 2100U. > I get some compilation warnings but these may have been already > present in the old code: > umax1220u.c:306: warning: dereferencing type-punned pointer will break > strict-aliasing rules umax1220u.c:348: warning: dereferencing type-punned > pointer will break strict-aliasing rules umax1220u.c:390: warning: > dereferencing type-punned pointer will break strict-aliasing rules > umax1220u.c:432: warning: dereferencing type-punned pointer will break > strict-aliasing rules umax1220u.c: In function > 'sane_umax1220u_control_option': > umax1220u.c:799: warning: format '%p' expects type 'void *', but argument 7 > has type 'SANE_Int *' Yes I'm getting those with the original source tarball. I've included a new source zip file attached with this e-mail. > > Generally it looks quite well. If the above comments are solved, I can > put your code in CVS. If you find anything, let me know. > If you like you can also have CVS access then, > so you can mainatin the backend yourself. To be honest I still don't know the backend 100%, but if I can help, again, I'll try to do it. Bye. Patrick. > > Bye, > Henning -------------- next part -------------- A non-text attachment was scrubbed... Name: umax1220u_backend.zip Type: application/x-zip Size: 18813 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060411/0824d9d8/umax1220u_backend-0001.bin From [email protected] Wed Apr 12 02:31:56 2006 From: [email protected] (Patrick Lessard) Date: Wed Apr 12 16:28:32 2006 Subject: [sane-devel] Umax Astra 2100U incorporated into umax1220u backend In-Reply-To: <[email protected]> References: <[email protected]> <[email protected]> Message-ID: <[email protected]> Hello, Here is another one, I corrected something in the calibration of the 2100U. Please use this one instead. That should be the last for now... Patrick. On Sunday 09 April 2006 17:42, Henning Meier-Geinitz wrote: > Hi, > > On 2006-03-31 13:05, Patrick Lessard wrote: > > I did incorporate it into the backend. > > Thanks. I'm currently looking at the code. I can't actually test it > because I don't have such a scanner so this is only theoretically. > > It would be good if somebody could test your current code with a Astra > 1220U just to make sure that nothing is broken. > > Comments: > in umax1220-common.c: > - Any reason to partly remove the DEBUG_BOUNDS code (and a + PAD > somewhere)? > - can all scanners cope with the bigger buffers: > - req = n = (len > 0xf000) ? 0xf000 : len; > + req = n = (len > 0xff00) ? 0xff00 : len; > - it looks like while you added move_2100, you also changed something > in move () itsself (sending longer buffers to the scanner with cwrite). > Does this also work with the 1220U? > in umax1220u.c: > - Why is the call to sanei_pv8630_init () removed? Without this I > think you can't use debugging for sanei_pv8630. > - Is there no problem removing this uncondinionally? > - res = UMAX_set_lamp_state (&scanner->scan, UMAX_LAMP_OFF); > > I get some compilation warnings but these may have been already > present in the old code: > umax1220u.c:306: warning: dereferencing type-punned pointer will break > strict-aliasing rules umax1220u.c:348: warning: dereferencing type-punned > pointer will break strict-aliasing rules umax1220u.c:390: warning: > dereferencing type-punned pointer will break strict-aliasing rules > umax1220u.c:432: warning: dereferencing type-punned pointer will break > strict-aliasing rules umax1220u.c: In function > 'sane_umax1220u_control_option': > umax1220u.c:799: warning: format '%p' expects type 'void *', but argument 7 > has type 'SANE_Int *' > > Generally it looks quite well. If the above comments are solved, I can > put your code in CVS. If you like you can also have CVS access then, > so you can mainatin the backend yourself. > > Bye, > Henning -------------- next part -------------- A non-text attachment was scrubbed... Name: umax1220u_backend_12042006.zip Type: application/x-zip Size: 18807 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060411/30c97293/umax1220u_backend_12042006.bin From [email protected] Wed Apr 12 19:12:17 2006 From: [email protected] (=?iso-8859-1?q?Ren=E9_Rebe?=) Date: Wed Apr 12 19:14:18 2006 Subject: [sane-devel] Backend for Minolta Dimage Scan Elite 5400. In-Reply-To: <[email protected]> References: <1144502468.3791.23.camel@serge2> <[email protected]> Message-ID: <[email protected]> On Monday 10 April 2006 21:52, Henning Meier-Geinitz wrote: > Hi, > > On 2006-04-08 15:21, Serge Leblanc wrote: > > Here requested logs. > > Thanks. I'll add them to our website. > > > It is possible to have an developmnent effort on this scanner ? I > > will like to make it myself but I don't have C programing since 8 > > years. > > As far as I know nobody is working on a backend for this scanner. So > it's really up to you. Can you use usb snoop to log the traffic of the windows driver? The former Dimage scanners are Avision ASIC based and the Avision backend might be able to drive those. Yours, -- Ren? Rebe - Rubensstr. 64 - 12157 Berlin (Europe / Germany) http://www.exactcode.de | http://www.t2-project.org +49 (0)30 255 897 45
