You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
(27) |
Apr
(55) |
May
(91) |
Jun
(20) |
Jul
(13) |
Aug
(8) |
Sep
(15) |
Oct
(10) |
Nov
(18) |
Dec
(10) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(29) |
Feb
(8) |
Mar
(5) |
Apr
(11) |
May
(9) |
Jun
(4) |
Jul
|
Aug
(4) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
2003 |
Jan
(1) |
Feb
|
Mar
|
Apr
(8) |
May
(2) |
Jun
(8) |
Jul
(3) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2004 |
Jan
(8) |
Feb
(1) |
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
(2) |
Dec
|
2005 |
Jan
|
Feb
|
Mar
(7) |
Apr
(3) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(5) |
Aug
(1) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
From: Marian E. <mar...@fr...> - 2007-07-23 14:18:24
|
On Mon, Jun 25, 2007 at 09:43:32PM +0200, Vizvári Tamás wrote: > Hi, Marian! > > I want to share my scanner by an Asus WL500gx router, but it doesn't > work. The output of SANE_DEBUG_SM3600 is: > > SANE_DEBUG_SM3600=255 scanimage > [sanei_debug] Setting debug level of sm3600 to 255. > [sm3600] SM3600 init > [sm3600] SM3600 version: 1000006 > [sm3600] found dev 05DA/40B3, /dev/usb/scanner0 > [sm3600] opening /dev/usb/scanner0 > [sm3600] /dev/usb/scanner0<>/dev/usb/scanner0 > scanimage: rounded value of br-x from 50 to 49.9954 > scanimage: rounded value of br-y from 80 to 79.9927 > [sm3600] starting scan... > [sm3600] mode=0, res=75, BC=[0,0], xywh=[1039,1417,1323,2362] > [sm3600] DoOriginate() > [sm3600] lt1=9 > [sm3600] lt2=3 > scanimage: sane_start: Error during device I/O > [sm3600] cancel called... > [sm3600] closing scanner > [sm3600] Error status: 9, Timeout while waiting for CSTAT > > I'm not a Linux guru, this failure notice says me nothing. What have I > to do? Yes, SANE does not allow for too specific application level reporting, anyway. EIO hmm... Perhaps You may to intrument the code a bit tighter to get a specific line. I guess, that one INST_ASSERT fails for any reason, and this should not happen. sm3600-homerun.c is the mother of trouble: vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv while (lt!=ltHome && !this->state.bCanceled) { lt=GetLineType(this); DBG(DEBUG_JUNK,"lt2=%d\n",(int)lt); INST_ASSERT(); switch (lt) { case ltHome: continue; case ltBed: DoJog(this,-240); break; /* worst case: 1 cm */ default: DoJog(this,-15); break; /* 0.X mm */ } } DoJog(this,1); INST_ASSERT(); /* Correction for 1 check line */ DBG(DEBUG_JUNK,"lt3=%d\n",(int)lt); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ It seems, as if the code does not detect the lt3 type of scan line. This means, that GetLineType() fails to find the desired gray/black-Pattern, which is absolutely possible given the degrees of freedom of the casing hardware. There's far too much "works for me" in the backend design, I have to admit. "Specification rulez" :-( I presume, that the camera slider steps back to the Origin and much more, until the process is canceled from within? GetLineType() is a real hack of code, with many hardcoded constants resulting from measurements of my scanner case and Glenn's, and some "reasonable" margins around. Probably there is a Problem, when the code found lt1 and lt2. Or it is an exposure problem, and You might want to tweak "CHASSIS_GRAY_LEVEL" a bit. When You set DEBUG_LEVEL to something including DEBUG_ORIG (4), You may get an idea of the probes that the camera gets during the homerun. This process is the most delicate one and the mother of trouble to some sm3600 owners. I most certainly will buy a scanner from a manufacture with a better API in the future (where the firmware abstracts from the physical tolerances). Hope it helps a bit, anyway... > > Thx in advance for any idea: > > Tamas Vizvari -- Mit freundlichen Gruessen / Yours sincerely Marian Eichholz Postmaster ---------------------------------------------------------------------------- Telefon: + 49 (0) 211 53087 521 Telefax: + 49 (0) 211 5381573 E-Mail: mar...@fr... Website: http://www.freenet.de ; http://www.mobilcom.de ---------------------------------------------------------------------------- freenet AG Willstätterstraße 13 40549 Düsseldorf ---------------------------------------------------------------------------- Vorsitzender des Aufsichtsrates: Prof. Dr. Helmut Thoma Vorstand: Eckhard Spoerr (Vors.), Axel Krieger, Stephan Esch, Eric Berger Sitz: Büdelsdorf Amtsgericht Kiel HRB 7306 KI |
From: <vi...@fr...> - 2007-06-25 19:43:46
|
Hi, Marian! I want to share my scanner by an Asus WL500gx router, but it doesn't work. The output of SANE_DEBUG_SM3600 is: SANE_DEBUG_SM3600=255 scanimage [sanei_debug] Setting debug level of sm3600 to 255. [sm3600] SM3600 init [sm3600] SM3600 version: 1000006 [sm3600] found dev 05DA/40B3, /dev/usb/scanner0 [sm3600] opening /dev/usb/scanner0 [sm3600] /dev/usb/scanner0<>/dev/usb/scanner0 scanimage: rounded value of br-x from 50 to 49.9954 scanimage: rounded value of br-y from 80 to 79.9927 [sm3600] starting scan... [sm3600] mode=0, res=75, BC=[0,0], xywh=[1039,1417,1323,2362] [sm3600] DoOriginate() [sm3600] lt1=9 [sm3600] lt2=3 scanimage: sane_start: Error during device I/O [sm3600] cancel called... [sm3600] closing scanner [sm3600] Error status: 9, Timeout while waiting for CSTAT I'm not a Linux guru, this failure notice says me nothing. What have I to do? Thx in advance for any idea: Tamas Vizvari |
From: Marian E. <mar...@fr...> - 2006-09-21 11:13:48
|
On Thu, Sep 21, 2006 at 04:37:04PM +0530, Joshua N Pritikin wrote: > I don't really understand the details but the scanner > seems to work fine with CHASSIS_GRAY_LEVEL=50. Wow, that's perfect! Good work! Probably You want to make patchfile to be safe wuth future releases. I am not confident that 50 is a value for everyone... > Date: Tue, 19 Sep 2006 13:56:35 +0200 > From: Marian Eichholz <mar...@fr...> > To: Joshua N Pritikin <jpr...@po...> > Subject: Re: [sm3600-devel] sm3600 doesn't scan (debian bug #387407) > Message-ID: <200...@ur...> > Reply-To: mar...@fr... > > On Tue, Sep 19, 2006 at 04:42:07PM +0530, Joshua N Pritikin wrote: > > > Here is the debug output: > > > > [sm3600] lt2=1 > > debug:jogging -15 units... > > debug:bulk read: 4096 -> 4096 > > debug:bulk read: 1204 -> 1204 > > debug:writing 5300 bytes > > debug: i=567 c=118 #0=626 i=1781 c=111 #1=1837 i=2991 c=115 #2=3049 > > 011221002222222222220222222222222202222222222222222221111111 - 57 > > [sm3600] lt2=1 > > debug:jogging -15 units... > > debug:bulk read: 4096 -> 4096 > > debug:bulk read: 1204 -> 1204 > > debug:writing 5300 bytes > > debug: i=567 c=118 #0=626 i=1781 c=111 #1=1837 i=2991 c=115 #2=3049 > > 011221002222222222220222222222222202222222222222222211111111 - 58 > > Good news' part, Joshua: You see, that the detection is basically fine. > > The 0s, 1s and 2s are quantized brightness values at > quantized positions. Just to make the actual data > understandable and handable. > > You see three single/double "holes" of 0s left to the middle, well? > > That's good! > > See Glenn's picture for reference: > > http://sm3600.sourceforge.net/technical.html > > Probable issues, as far as I remember without the source at > hand: > > - Wrong position. > > - Wrong width. The first 0 ist double. Don't know, if that > is a problem. > > - Left hole too dark. You see the left corner as "1" due to > vignettized illumination. That'S where playing with > GRAYLEVEL (and the rough pre-normalisation) might help. > > There is some heuristik to distinguish "good" calibration > spots from arbitrary paper content on the glass. The > Scanner shall safely find home from whatever position it > may be. > > You might even want to skip the test for the left "hole" at > all and only test the middle and right one. That's > completely ok. You will just lose some safety against > effects from content on the glass, when the scanner is used > without slider in home position. > > This trouble we have here is the immediate result from > lacking documentation of the rationales of the scanner > machine design. We got documentation about the controller > (when it was too late to implement it really correctly and > with good design and with fun). The application of the > controller is still to be reversed engineered or guessed > :-( > > Ther eis far too much magic in the code. > Anyone who wants to improve or reimplement it cleanly is > welcome :-)))) > > > > > > > etc > > > > What should I do? Reduce CHASSIS_GRAY_LEVEL to 50? > > > > -- > Mit freundlichen Gruessen / Yours sincerely > > Marian Eichholz > Postmaster > freenet.de AG Vorsitzender des Aufsichtsrates: Prof. Dr. Helmut Thoma > Deelbögenkamp 4c Vorstand: Eckhard Spoerr (Vors.), Axel Krieger, > Stephan Esch, Eric Berger > 22297 Hamburg Amtsgericht Hamburg, HRB 74048 > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > sm3600-devel mailing list > sm3...@li... > https://lists.sourceforge.net/lists/listinfo/sm3600-devel -- Mit freundlichen Gruessen / Yours sincerely Marian Eichholz Postmaster freenet.de AG Vorsitzender des Aufsichtsrates: Prof. Dr. Helmut Thoma Deelbögenkamp 4c Vorstand: Eckhard Spoerr (Vors.), Axel Krieger, Stephan Esch, Eric Berger 22297 Hamburg Amtsgericht Hamburg, HRB 74048 |
From: Joshua N P. <jpr...@po...> - 2006-09-21 11:07:46
|
I don't really understand the details but the scanner seems to work fine with CHASSIS_GRAY_LEVEL=50. |
From: Joshua P. <jo...@ca...> - 2006-09-14 08:26:00
|
Package: libsane Version: 1.0.18-3 Severity: normal sunil@ltsp1:~$ SANE_DEBUG_SM3600=255 scanimage -L [sanei_debug] Setting debug level of sm3600 to 255. [sm3600] SM3600 init [sm3600] SM3600 version: 1000006 [sm3600] found dev 05DA/40B3, libusb:001:009 device `sm3600:libusb:001:009' is a Microtek ScanMaker 3600 flatbed scanner sunil@ltsp1:~$ SANE_DEBUG_SM3600=255 scanimage [sanei_debug] Setting debug level of sm3600 to 255. [sm3600] SM3600 init [sm3600] SM3600 version: 1000006 [sm3600] found dev 05DA/40B3, libusb:001:009 [sm3600] opening libusb:001:009 [sm3600] libusb:001:009<>libusb:001:009 scanimage: rounded value of br-x from 50 to 49.9954 scanimage: rounded value of br-y from 80 to 79.9927 [sm3600] starting scan... [sm3600] mode=0, res=75, BC=[0,0], xywh=[1039,1417,1323,2362] [sm3600] DoOriginate() [sm3600] lt1=1 [sm3600] lt2=1 [sm3600] lt2=1 [sm3600] lt2=1 [sm3600] lt2=1 [sm3600] lt2=1 This last line repeats forever. The lamp never progresses across the page. Any other diagnostics I can provide? -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.15.4-b2 Locale: LANG=C, LC_CTYPE=C Versions of packages libsane depends on: ii adduser 3.59 Add and remove users and groups ii libc6 2.3.6-7 GNU C Library: Shared libraries ii libgphoto2-2 2.2.1-3+b1 gphoto2 digital camera library ii libgphoto2-port0 2.2.1-3+b1 gphoto2 digital camera port librar ii libieee1284-3 0.2.8-2 Cross-platform library for paralle ii libjpeg62 6b-13 The Independent JPEG Group's JPEG ii libtiff4 3.8.2-5 Tag Image File Format (TIFF) libra ii libusb-0.1-4 2:0.1.12-2 userspace USB programming library ii makedev 2.3.1-80 creates device files in /dev -- no debconf information |
From: Marian E. <mar...@fr...> - 2006-08-07 20:44:29
|
Hello, today I investigated the issue with recent Kernels. There are *some* problems, that can be tackled with package updates. SANE: At least in the CVS code (1.0.18-cvs) the USB library calls are encapsulated into the sanei_* namespace. The modules are less likeley to make incompatible calls. The good thing is: 1.0.18-CVS sane backends work without additional tuning. Just give it a go. It looks, as if we have not been the only backend with trouble :-) Speaking abount libusb: The current libusb-0.1.12 returns an error code (or an equivalent) with the usb_find_busses(). This breaks the USB initialisation with my scantool-frontend and with old SANE backends ("no USB"). Last, but not least, the usb_claim_interface() does no longer work with the old parameter (...,0) but needs (..., 1). Honestly I have no idea about that parameter, as it was "magic" when I needed it. It still is magic for me. Well, with the new parameter the code works. So, just update Your backends and probably the libusb, and You should be fine. I'll release a scantool update, when I have some spare time again, but You might fix the two calls by Yourself, now that You know. Most of You never will use that special tool :-) Have fun! Marian |
From: Marian E. <mar...@fr...> - 2006-07-31 07:08:55
|
On Sat, Jul 29, 2006 at 10:31:13AM -0400, Jason wrote: > on yalls webpage it says to contact you folks to get a snoopy dump/trace for this scanner.. > I just picked up one at a yardsale for $1 and it seems to work (it powers on), and id like to get it to > work under linux. Do you folks still want this snoopy output? If so, please let me know what I need to > get you. To be honest, I have no time for new scanner development. But if You get it to work, and the code can be merged, You are really welcome. I really think that SANE backends are to be provided by the manufacture, and that scanner shoukld come with developer documentation. The other way round: We should buy scanners from companies that support SANE backend development by any means. My personal POV ;-) In the meantime, I really shoudl figure out, why the newer 2.6 kernels break our backend :-/ - Marian |
From: Jason <ja...@mo...> - 2006-07-29 14:31:19
|
on yalls webpage it says to contact you folks to get a snoopy dump/trace for this scanner.. I just picked up one at a yardsale for $1 and it seems to work (it powers on), and id like to get it to work under linux. Do you folks still want this snoopy output? If so, please let me know what I need to get you. regards, Jason |
From: Chien-Yu C. <to...@gm...> - 2006-07-28 19:49:17
|
sorry, havn't have time to deal with this due to family emergency will test what you suggested once I get back to the States. On 7/26/06, Marian Eichholz <mar...@fr...> wrote: > On Tue, Jul 11, 2006 at 11:26:54AM +0200, Marian Eichholz wrote: > > On Thu, Jun 29, 2006 at 04:46:59PM +0000, Chien-Yu Chen wrote: > > > > Hi! > > > > > > I am trying to use sane for microtek 3600...when I do > > > > > > -------- > > > kiosque jpeg # scanimage -T > > > ---------- > > > > > > I get > > > > > > --------- > > > scanimage: open of device sm3600:1/1 failed: Error during device I/O > > Hey folks, did it read something like "set config 0 claimed by devfs ... = device busy ..."? > > Obviously they broke something in kernel 2.6.17.27 > (again!), at least with this kernel my scanner > application(s) won't work any longer. > > My, 2.6.x is pure pain in the ***... > > Due to severe lack of time I cannot investigate right now, > but it looks like a basical problem with libusb and usbfs > interaction. > > > Chien-Yu, does the Scanner respond mechanically? Any activity? > > > > Obviously the backend detects it's device. Something other goes wrong. > > > > Please let me suggest, to set the > > Debug-Environment-Variable for the test to something other > > than 0, to get some useful information from the (otherwise > > silent as recommended) backend code. > > > > See "man sane-sm3600" for reference: > > > > SANE_DEBUG_SM3600 > > If the library was compiled with debug support > > enabled, this environment variable controls the > > debug level for this backend. E.g., a value of 128 > > requests all debug output to be printed. Smaller > > levels reduce verbosity. To see error messages on > > stderr set SANE_DEBUG_SM3600 to 1. > > > > E.g. just say: > > export SANE_DEBUG_SM3600=3D5 > > > > There is really really a number of possible reasons for > > returning SANE_STATUS_IO_ERROR, since this is AFAIK the > > correct and only way to report virtuately everything(!) that can go wro= ng > > during all kind of communication with the scanner. > > > > > > > --------- > > > > > > I ran this as root, and still get the error... > > > here are some info for the usb system. > > > > > > ---------- > > > kiosque jpeg # ls -laR /proc/bus/usb/ > > > /proc/bus/usb/: > > > total 0 > > > drwxr-xr-x 3 root root 0 Jun 26 02:52 . > > > dr-xr-xr-x 5 root root 0 Jun 26 02:52 .. > > > drwxrwxrwx 2 root root 0 Jun 28 16:20 001 > > > -rwxrwxrwx 1 root root 0 Jun 29 10:53 devices > > > > > > /proc/bus/usb/001: > > > total 0 > > > drwxrwxrwx 2 root root 0 Jun 28 16:20 . > > > drwxr-xr-x 3 root root 0 Jun 26 02:52 .. > > > -rwxrwxrwx 1 root usb 43 Jun 28 16:20 001 > > > -rwxrwxrwx 1 root usb 43 Jun 29 00:45 004 > > > ------------- > > > > > > ------------ > > > kiosque jpeg # cat /proc/bus/usb/devices > > > > > > T: Bus=3D01 Lev=3D00 Prnt=3D00 Port=3D00 Cnt=3D00 Dev#=3D 1 Spd=3D1= 2 MxCh=3D 2 > > > B: Alloc=3D 0/900 us ( 0%), #Int=3D 0, #Iso=3D 0 > > > D: Ver=3D 1.10 Cls=3D09(hub ) Sub=3D00 Prot=3D00 MxPS=3D64 #Cfgs=3D= 1 > > > P: Vendor=3D0000 ProdID=3D0000 Rev=3D 2.06 > > > S: Manufacturer=3DLinux 2.6.16-gentoo-r9 uhci_hcd > > > S: Product=3DUHCI Host Controller > > > S: SerialNumber=3D0000:00:1f.2 > > > C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3Dc0 MxPwr=3D 0mA > > > I: If#=3D 0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub ) Sub=3D00 Prot=3D00 Dr= iver=3Dhub > > > E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 2 Ivl=3D255ms > > > > > > T: Bus=3D01 Lev=3D01 Prnt=3D01 Port=3D01 Cnt=3D01 Dev#=3D 4 Spd=3D1= 2 MxCh=3D 0 > > > D: Ver=3D 1.00 Cls=3Dff(vend.) Sub=3Dff Prot=3Dff MxPS=3D64 #Cfgs=3D= 1 > > > P: Vendor=3D05da ProdID=3D40ca Rev=3D 0.00 > > > C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3D60 MxPwr=3D100mA > > > I: If#=3D 0 Alt=3D 0 #EPs=3D 1 Cls=3Dff(vend.) Sub=3Dff Prot=3Dff Dr= iver=3D(none) > > > E: Ad=3D82(I) Atr=3D02(Bulk) MxPS=3D 64 Ivl=3D0ms > > > -------------- > > > > > > thanks for any suggestion > > > > > > chen > > > > > > Using Tomcat but need to do more? Need to support web services, secur= ity? > > > Get stuff done quickly with pre-integrated technology to make your jo= b easier > > > Download IBM WebSphere Application Server v.1.0.1 based on Apache Ger= onimo > > > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&d= at=3D121642 > > > _______________________________________________ > > > sm3600-devel mailing list > > > sm3...@li... > > > https://lists.sourceforge.net/lists/listinfo/sm3600-devel > > > > -- > > Mit freundlichen Gruessen / Yours sincerely > > > > Marian Eichholz > > Postmaster > > freenet.de AG Vorsitzender des Aufsichtsrates: Prof. Dr. Helmu= t Thoma > > Deelb=F6genkamp 4c Vorstand: Eckhard Spoerr (Vors.), Axel Krieger= , > > Stephan Esch, Eric Berger > > 22297 Hamburg Amtsgericht Hamburg, HRB 74048 > > > > > > -----------------------------------------------------------------------= -- > > Using Tomcat but need to do more? Need to support web services, securit= y? > > Get stuff done quickly with pre-integrated technology to make your job = easier > > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geron= imo > > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat= =3D121642 > > _______________________________________________ > > sm3600-devel mailing list > > sm3...@li... > > https://lists.sourceforge.net/lists/listinfo/sm3600-devel > > -- > Mit freundlichen Gruessen / Yours sincerely > > Marian Eichholz > Postmaster > freenet.de AG Vorsitzender des Aufsichtsrates: Prof. Dr. Helmut = Thoma > Deelb=F6genkamp 4c Vorstand: Eckhard Spoerr (Vors.), Axel Krieger, > Stephan Esch, Eric Berger > 22297 Hamburg Amtsgericht Hamburg, HRB 74048 > --=20 .--. |o_o | Freedom of Choice |:_/ | __ // \ \ / / __ __ __ __ __ __ __ (| | ) / /__ / / / \/ / / /_/ / \ \/ / /'\_ _/`\ /_____/ /_/ /_/\__/ /_____/ /_/\_\ \___)=3D(___/ |
From: Marian E. <mar...@fr...> - 2006-07-28 18:49:11
|
On Tue, Jul 11, 2006 at 11:26:54AM +0200, Marian Eichholz wrote: > On Thu, Jun 29, 2006 at 04:46:59PM +0000, Chien-Yu Chen wrote: > > Hi! > > > > I am trying to use sane for microtek 3600...when I do > > > > -------- > > kiosque jpeg # scanimage -T > > ---------- > > > > I get > > > > --------- > > scanimage: open of device sm3600:1/1 failed: Error during device I/O Hey folks, did it read something like "set config 0 claimed by devfs ... device busy ..."? Obviously they broke something in kernel 2.6.17.27 (again!), at least with this kernel my scanner application(s) won't work any longer. My, 2.6.x is pure pain in the ***... Due to severe lack of time I cannot investigate right now, but it looks like a basical problem with libusb and usbfs interaction. > Chien-Yu, does the Scanner respond mechanically? Any activity? > > Obviously the backend detects it's device. Something other goes wrong. > > Please let me suggest, to set the > Debug-Environment-Variable for the test to something other > than 0, to get some useful information from the (otherwise > silent as recommended) backend code. > > See "man sane-sm3600" for reference: > > SANE_DEBUG_SM3600 > If the library was compiled with debug support > enabled, this environment variable controls the > debug level for this backend. E.g., a value of 128 > requests all debug output to be printed. Smaller > levels reduce verbosity. To see error messages on > stderr set SANE_DEBUG_SM3600 to 1. > > E.g. just say: > export SANE_DEBUG_SM3600=5 > > There is really really a number of possible reasons for > returning SANE_STATUS_IO_ERROR, since this is AFAIK the > correct and only way to report virtuately everything(!) that can go wrong > during all kind of communication with the scanner. > > > > --------- > > > > I ran this as root, and still get the error... > > here are some info for the usb system. > > > > ---------- > > kiosque jpeg # ls -laR /proc/bus/usb/ > > /proc/bus/usb/: > > total 0 > > drwxr-xr-x 3 root root 0 Jun 26 02:52 . > > dr-xr-xr-x 5 root root 0 Jun 26 02:52 .. > > drwxrwxrwx 2 root root 0 Jun 28 16:20 001 > > -rwxrwxrwx 1 root root 0 Jun 29 10:53 devices > > > > /proc/bus/usb/001: > > total 0 > > drwxrwxrwx 2 root root 0 Jun 28 16:20 . > > drwxr-xr-x 3 root root 0 Jun 26 02:52 .. > > -rwxrwxrwx 1 root usb 43 Jun 28 16:20 001 > > -rwxrwxrwx 1 root usb 43 Jun 29 00:45 004 > > ------------- > > > > ------------ > > kiosque jpeg # cat /proc/bus/usb/devices > > > > T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 > > B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 > > D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > > P: Vendor=0000 ProdID=0000 Rev= 2.06 > > S: Manufacturer=Linux 2.6.16-gentoo-r9 uhci_hcd > > S: Product=UHCI Host Controller > > S: SerialNumber=0000:00:1f.2 > > C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA > > I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub > > E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms > > > > T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0 > > D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 > > P: Vendor=05da ProdID=40ca Rev= 0.00 > > C:* #Ifs= 1 Cfg#= 1 Atr=60 MxPwr=100mA > > I: If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) > > E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms > > -------------- > > > > thanks for any suggestion > > > > chen > > > > Using Tomcat but need to do more? Need to support web services, security? > > Get stuff done quickly with pre-integrated technology to make your job easier > > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > _______________________________________________ > > sm3600-devel mailing list > > sm3...@li... > > https://lists.sourceforge.net/lists/listinfo/sm3600-devel > > -- > Mit freundlichen Gruessen / Yours sincerely > > Marian Eichholz > Postmaster > freenet.de AG Vorsitzender des Aufsichtsrates: Prof. Dr. Helmut Thoma > Deelbögenkamp 4c Vorstand: Eckhard Spoerr (Vors.), Axel Krieger, > Stephan Esch, Eric Berger > 22297 Hamburg Amtsgericht Hamburg, HRB 74048 > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > sm3600-devel mailing list > sm3...@li... > https://lists.sourceforge.net/lists/listinfo/sm3600-devel -- Mit freundlichen Gruessen / Yours sincerely Marian Eichholz Postmaster freenet.de AG Vorsitzender des Aufsichtsrates: Prof. Dr. Helmut Thoma Deelbögenkamp 4c Vorstand: Eckhard Spoerr (Vors.), Axel Krieger, Stephan Esch, Eric Berger 22297 Hamburg Amtsgericht Hamburg, HRB 74048 |
From: Marian E. <mar...@fr...> - 2006-07-11 09:27:03
|
On Thu, Jun 29, 2006 at 04:46:59PM +0000, Chien-Yu Chen wrote: > Hi! > > I am trying to use sane for microtek 3600...when I do > > -------- > kiosque jpeg # scanimage -T > ---------- > > I get > > --------- > scanimage: open of device sm3600:1/1 failed: Error during device I/O Chien-Yu, does the Scanner respond mechanically? Any activity? Obviously the backend detects it's device. Something other goes wrong. Please let me suggest, to set the Debug-Environment-Variable for the test to something other than 0, to get some useful information from the (otherwise silent as recommended) backend code. See "man sane-sm3600" for reference: SANE_DEBUG_SM3600 If the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. E.g., a value of 128 requests all debug output to be printed. Smaller levels reduce verbosity. To see error messages on stderr set SANE_DEBUG_SM3600 to 1. E.g. just say: export SANE_DEBUG_SM3600=5 There is really really a number of possible reasons for returning SANE_STATUS_IO_ERROR, since this is AFAIK the correct and only way to report virtuately everything(!) that can go wrong during all kind of communication with the scanner. > --------- > > I ran this as root, and still get the error... > here are some info for the usb system. > > ---------- > kiosque jpeg # ls -laR /proc/bus/usb/ > /proc/bus/usb/: > total 0 > drwxr-xr-x 3 root root 0 Jun 26 02:52 . > dr-xr-xr-x 5 root root 0 Jun 26 02:52 .. > drwxrwxrwx 2 root root 0 Jun 28 16:20 001 > -rwxrwxrwx 1 root root 0 Jun 29 10:53 devices > > /proc/bus/usb/001: > total 0 > drwxrwxrwx 2 root root 0 Jun 28 16:20 . > drwxr-xr-x 3 root root 0 Jun 26 02:52 .. > -rwxrwxrwx 1 root usb 43 Jun 28 16:20 001 > -rwxrwxrwx 1 root usb 43 Jun 29 00:45 004 > ------------- > > ------------ > kiosque jpeg # cat /proc/bus/usb/devices > > T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 > B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 > D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > P: Vendor=0000 ProdID=0000 Rev= 2.06 > S: Manufacturer=Linux 2.6.16-gentoo-r9 uhci_hcd > S: Product=UHCI Host Controller > S: SerialNumber=0000:00:1f.2 > C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub > E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms > > T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0 > D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 > P: Vendor=05da ProdID=40ca Rev= 0.00 > C:* #Ifs= 1 Cfg#= 1 Atr=60 MxPwr=100mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) > E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms > -------------- > > thanks for any suggestion > > chen > > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > sm3600-devel mailing list > sm3...@li... > https://lists.sourceforge.net/lists/listinfo/sm3600-devel -- Mit freundlichen Gruessen / Yours sincerely Marian Eichholz Postmaster freenet.de AG Vorsitzender des Aufsichtsrates: Prof. Dr. Helmut Thoma Deelbögenkamp 4c Vorstand: Eckhard Spoerr (Vors.), Axel Krieger, Stephan Esch, Eric Berger 22297 Hamburg Amtsgericht Hamburg, HRB 74048 |
From: Chien-Yu C. <to...@gm...> - 2006-06-29 16:47:02
|
Hi! I am trying to use sane for microtek 3600...when I do -------- kiosque jpeg # scanimage -T ---------- I get --------- scanimage: open of device sm3600:1/1 failed: Error during device I/O --------- I ran this as root, and still get the error... here are some info for the usb system. ---------- kiosque jpeg # ls -laR /proc/bus/usb/ /proc/bus/usb/: total 0 drwxr-xr-x 3 root root 0 Jun 26 02:52 . dr-xr-xr-x 5 root root 0 Jun 26 02:52 .. drwxrwxrwx 2 root root 0 Jun 28 16:20 001 -rwxrwxrwx 1 root root 0 Jun 29 10:53 devices /proc/bus/usb/001: total 0 drwxrwxrwx 2 root root 0 Jun 28 16:20 . drwxr-xr-x 3 root root 0 Jun 26 02:52 .. -rwxrwxrwx 1 root usb 43 Jun 28 16:20 001 -rwxrwxrwx 1 root usb 43 Jun 29 00:45 004 ------------- ------------ kiosque jpeg # cat /proc/bus/usb/devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 2.06 S: Manufacturer=Linux 2.6.16-gentoo-r9 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=0000:00:1f.2 C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 P: Vendor=05da ProdID=40ca Rev= 0.00 C:* #Ifs= 1 Cfg#= 1 Atr=60 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms -------------- thanks for any suggestion chen |
From: Henning Meier-G. <he...@me...> - 2005-05-26 09:33:46
|
Hi Marian, Is there any reason not to apply the patch posted by Julien (attached below)? Otherwise I'd commit it to CVS. Bye, Henning On Sat, Apr 30, 2005 at 02:16:04PM +0200, Julien BLACHE wrote: > Marian Eichholz <mar...@fr...> wrote: > > >> "SANE_DEBUG_SM3600=255 scanimage -L" > >> ---cut here--- > >> [sanei_debug] Setting debug level of sm3600 to 255. > >> [sm3600] SM3600 init > >> [sm3600] SM3600 version: 1000005 > > > > Thats pretty much sparse. Is usbdevfs in place? > > There's a bug in sane_init(), a misuse of usb_find_busses(). Patch > attached. > > >From the libusb documentation: > --- > usb_find_busses will find all of the busses on the system. Returns the > number of changes since previous call to this function (total of new > busses and busses removed). > --- > > JB. > > -- > Julien BLACHE <http://www.jblache.org> > <jb...@jb...> GPG KeyID 0xF5D65169 > Content-Description: sane_init libusb patch > Index: backend/sm3600.c > =================================================================== > RCS file: /cvsroot/sane/sane-backends/backend/sm3600.c,v > retrieving revision 1.12 > diff -u -r1.12 sm3600.c > --- backend/sm3600.c 15 Apr 2004 19:56:53 -0000 1.12 > +++ backend/sm3600.c 30 Apr 2005 12:13:02 -0000 > @@ -374,11 +374,12 @@ > pdevFirst=NULL; > > usb_init(); > - rc=usb_find_busses(); > - if (rc) > - return SANE_STATUS_GOOD; > + usb_find_busses(); > + if (!usb_busses) > + return SANE_STATUS_IO_ERROR; > + > usb_find_devices(); > - if (!usb_busses) return SANE_STATUS_IO_ERROR; > + > iBus=0; > DBG(DEBUG_INFO,"starting bus scan\n"); > for (pbus = usb_busses; pbus; pbus = pbus->next) |
From: Julien B. <jb...@jb...> - 2005-04-30 10:07:24
|
Marian Eichholz <mar...@fr...> wrote: >> "SANE_DEBUG_SM3600=255 scanimage -L" >> ---cut here--- >> [sanei_debug] Setting debug level of sm3600 to 255. >> [sm3600] SM3600 init >> [sm3600] SM3600 version: 1000005 > > Thats pretty much sparse. Is usbdevfs in place? I'm getting the same output here, with usbfs in place. Moreover, I have received a couple of bug reports where the sm3600 backend is poisoning other backends, leading to all kinds of funny segfaults, with a mangled stack or heap (http://bugs.debian.org/302527). There's something going wrong with this backend... JB. -- Julien BLACHE <http://www.jblache.org> <jb...@jb...> GPG KeyID 0xF5D65169 |
From: <su...@se...> - 2005-04-30 02:19:18
|
SuSE Linux 9.3 Professional x86_64 (64 bit) kernel 2.6.11.4 (x86_64) libusb-0.1.so.4.4.0 (libusb version 0.1.8) libsane.so.1.0.15 (sane version 1.0.15) Microtek ScanMaker 3600 (vendor=0x05da product=0x40ca) (Genius WebCam Web V4 (vendor=0458 product=700f)) "cat /proc/bus/usb/devices" ---cut here--- T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh=10 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 2.06 S: Manufacturer=Linux 2.6.11.4-20a-default ohci_hcd S: Product=OHCI Host Controller S: SerialNumber=0000:00:02.0 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=02 Lev=01 Prnt=01 Port=08 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=ff(vend.) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0458 ProdID=700f Rev= 1.00 C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=160mA I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=81(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=10ms I: If#= 0 Alt= 1 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=81(I) Atr=01(Isoc) MxPS= 128 Ivl=1ms E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=10ms I: If#= 0 Alt= 2 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=81(I) Atr=01(Isoc) MxPS= 192 Ivl=1ms E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=10ms I: If#= 0 Alt= 3 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=81(I) Atr=01(Isoc) MxPS= 256 Ivl=1ms E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=10ms I: If#= 0 Alt= 4 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=81(I) Atr=01(Isoc) MxPS= 384 Ivl=1ms E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=10ms I: If#= 0 Alt= 5 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=81(I) Atr=01(Isoc) MxPS= 512 Ivl=1ms E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=10ms I: If#= 0 Alt= 6 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=81(I) Atr=01(Isoc) MxPS= 768 Ivl=1ms E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=10ms I: If#= 0 Alt= 7 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=81(I) Atr=01(Isoc) MxPS=1023 Ivl=1ms E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=10ms T: Bus=02 Lev=01 Prnt=01 Port=09 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 P: Vendor=05da ProdID=40ca Rev= 0.00 C:* #Ifs= 1 Cfg#= 1 Atr=60 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=ff Prot=ff Driver=usbscanner E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=10 B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS= 8 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 2.06 S: Manufacturer=Linux 2.6.11.4-20a-default ehci_hcd S: Product=EHCI Host Controller S: SerialNumber=0000:00:02.1 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms ---cut here--- - after my scanner power on: "tail /var/log/messages" ---cut here--- Apr 30 02:32:58 linux kernel: usb 2-10: new full speed USB device using ohci_hcd and address 3 Apr 30 02:33:00 linux kernel: scanner: unsupported module, tainting kernel. Apr 30 02:33:00 linux kernel: /usr/src/linux-2.6.11.4-20a/drivers/usb/image/scanner.c: USB scanner device (0x05da/0x40ca) now attached to usb/scanner0 Apr 30 02:33:00 linux kernel: usbcore: registered new driver usbscanner Apr 30 02:33:00 linux kernel: /usr/src/linux-2.6.11.4-20a/drivers/usb/image/scanner.c: 0.4.16:USB Scanner Driver Apr 30 02:33:00 linux kernel: /usr/src/linux-2.6.11.4-20a/drivers/usb/image/scanner.c: probe_scanner: User specified USB scanner -- Vendor:Product - 5da:40ca Apr 30 02:33:00 linux /etc/hotplug.d/usb/50-usb.hotplug[8291]: setting permissions of /proc/bus/usb/002/003 ---cut here--- "sane-find-scanner" ---cut here--- # No SCSI scanners found. If you expected something different, make sure that # you have loaded a SCSI driver for your SCSI adapter. found USB scanner (vendor=0x05da, product=0x40ca) at /dev/usb/scanner0 found USB scanner (vendor=0x05da, product=0x40ca) at /dev/usbscanner found USB scanner (vendor=0x05da, product=0x40ca) at libusb:002:003 found USB scanner (vendor=0x0458, product=0x700f) at libusb:002:002 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. ---cut here--- "SANE_DEBUG_SM3600=255 scanimage -L" ---cut here--- [sanei_debug] Setting debug level of sm3600 to 255. [sm3600] SM3600 init [sm3600] SM3600 version: 1000005 No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). ---cut here--- 1) I add support for scanner.ko for recent 2.6.x kernel (http://www.linuxquestions.org/questions/showthread.php?s=&postid=851819) 2) create files libsane.usermap, libusbscanenr, sm3600, sm3600.usermap, scanner, sm3600 "cat /etc/hotplug/usb/libsane.usermap" ---cut here--- libusbscanner 0x0003 0x05da 0x40ca 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000 ---cut here--- "cat /etc/hotplug/usb/libusbscanenr" ---cut here--- if [ -z "$DEVICE" ] ; then IF=`echo $DEVPATH | sed 's/\(bus\/usb\/devices\/\)\(.*\)-\(.*\)/\2/'` DEV=`echo $DEVPATH | sed 's/\(bus\/usb\/devices\/\)\(.*\)-\(.*\)/\3/'` DEV=`expr $DEV + 1` DEVICE=`printf '/proc/bus/usb/%.03d/%.03d' $IF $DEV` fi if [ "$ACTION" = "add" -a "$TYPE" = "usb" ]; then chmod 0666 "$DEVICE" fi ---cut here--- "cat /etc/hotplug/usb/sm3600" ---cut here--- #!/bin/sh cd /etc/hotplug . hotplug.functions mesg setting permissions of $DEVICE chown 777 $DEVICE ---cut here--- "cat /etc/hotplug/usb/sm3600.usermap" ---cut here--- sm3600 0x0003 0x05da 0x40ca 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x000000000 ---cut here--- "cat /etc/modprobe.d/scanner" ---cut here--- alias char-major-180 scanner options scanner vendor=0x05da product=0x40ca ---cut here--- "cat /etc/modprobe.d/sm3600" ---cut here--- alias char-major-180 sm3600 options sm3600 vendor=0x05da product=0x40ca ---cut here--- 3) edit files usb.usermap, usb.handmap, modules.alias, mudels.usbmap, dll.conf "cat /etc/hotplug/usb.usermap" ---cut here--- sm3600 0x0003 0x05da 0x40ca 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x000000000 libusbscanner 0x0003 0x05da 0x40ca 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x000000000 ---cut here--- "cat /etc/hotplug/usb.handmap" ---cut here--- 0x00 0x00 0x00 0x00000000 ---cut here--- "cat /lib/modules/2.6.11.4/modules.alias" (other lines with "alia xyz scanner" removed) ---cut here--- alias usb:v05DAp40CAdl*dh*dc*dsc*dp*ic*isc*ip* scanner ---cut here--- "cat /lib/modules/2.6.11.4/modules.usbmap" (other lines with "scanner xyz" removed) ---cut here--- scanner 0x0003 0x05da 0x40ca 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0 ---cut here--- "cat /etc/sane.d/dll.conf" ---cut here--- microtek microtek2 sm3600 ---cut here--- 4) Scanner do not working with or without support scanner.ko in recent 2.6.x kernel. some tryes: linux:/ # scanimage -d sm3600:/dev/usb/scanner0 >image.pnm scanimage: open of device sm3600:/dev/usb/scanner0 failed: Invalid argument linux:/ # scanimage -d sm3600:/dev/usbscanner >image.pnm scanimage: open of device sm3600:/dev/usbscanner failed: Invalid argument linux:/ # scanimage -d sm3600:/proc/bus/usb/002/003 >image.pnm scanimage: open of device sm3600:/proc/bus/usb/002/003 failed: Invalid argument linux:/ # scanimage -d sm3600:/libusb:002:003 >image.pnm scanimage: open of device sm3600:/libusb:002:003 failed: Invalid argument linux:/ # scanimage -d sm3600:libusb:002:003 >image.pnm scanimage: open of device sm3600:libusb:002:003 failed: Invalid argument linux:/ # scanimage -d microtek:/dev/usb/scanner0 >image.pnm scanimage: open of device microtek:/dev/usb/scanner0 failed: Invalid argument linux:/ # scanimage -d microtek:/dev/usbscanner >image.pnm scanimage: open of device microtek:/dev/usbscanner failed: Invalid argument linux:/ # scanimage -d microtek:/proc/bus/usb/002/003 >image.pnm scanimage: open of device microtek:/proc/bus/usb/002/003 failed: Invalid argument linux:/ # scanimage -d microtek2:/dev/usb/scanner0 >image.pnm scanimage: open of device microtek2:/dev/usb/scanner0 failed: Invalid argument linux:/ # scanimage -d microtek2:/dev/usbscanner >image.pnm scanimage: open of device microtek2:/dev/usbscanner failed: Invalid argument linux:/ # scanimage -d microtek2:/proc/bus/usb/002/003 >image.pnm scanimage: open of device microtek2:/proc/bus/usb/002/003 failed: Invalid argument Can You help me please how can I make Microtek ScanMaker 3600 working? Thank You very much for answer Petr Novak su...@se... |
From: Marian E. <mar...@fr...> - 2005-03-16 07:42:37
|
On Tue, Mar 15, 2005 at 11:10:28PM +0100, Dorian Büttner wrote: > On Tuesday 15 March 2005 22:18, Ben Johnson wrote: > > or, hm.... this is starting to come back to me. There was one definite > > problem with my scanner. Apparently the case was a slightly darker > > color than most people's version of the sm3600. One of the problems this > > caused was it wasn't able to find home because it couldn't distinguish > > between the color of the plastic case and whatever else is inside the > > scanner case at the "home" position that's intended to provide contrast. Yes, Ben/Dorian, since the "home" position can only be tested through heuristics, this is a painful weak point in the whole concept, since Mikrotek might freely change every bit in the products without notice. If the backend cannot find these spots where it expects them, it has to resort to a "home run" accross the whole glass plate, including the "sound of doom" from the belt. shudder... There is something we never talked about, it is the *cameras*, and the lightings, of course. The controller part of the scanner supports various line camera types. Each of them has unique signal timings that better be respected for a reasonable result. Worse, these timings have to be *actively* selected by register programming of the scanning application (e.g. the back end). Here where at least I have to give up, because I have no sufficient concept of these devices, I do not know how to distinguish them within the back end, do not know what parts Microtek used (and they won't tell either, I presume) etc. It is possible that the weird scans are a result from a "wrong camera". It might, and it might not. > > I wrote in this list earlier about adjusting some constant in the driver > > code. You might want to try that. > Yes, that was exactly what I was fiddling around with. I tried values 100, 75, > 50 - none of them worked. > So I was just experiencing some coincidence: > your talking about the contrast between the black markers and the gray > contrast led me to the painful easy idea of sticking a piece of white paper > over the home, copying the black thingies with a black felt tip. For the > purpose of making tha black spots visible through the paper, I drew my desk > light, which is halogene one, right near the glass plate. While repainting > the spots, I noticed that the stickers which fit the glass plate in the cover > were kind of luminescating in a shiney green tone, this could probably be > another useful interesting point? > However, I made a shot with my mobile phone cam, I don't own a real one, I > just need to reboot into the windows os to suck it out and let you have a > look. It looks interesting, but I'm confident that this is an artifact resulting from the green color of the glass and the the light traversing the whole glass *length* before "coupled out". Sorry, my physics dictionary is not available right now :-) > So far, > Dorian > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > sm3600-devel mailing list > sm3...@li... > https://lists.sourceforge.net/lists/listinfo/sm3600-devel -- Mit freundlichen Gruessen / Yours sincerely Marian Eichholz Postmaster freenet.de AG Vorsitzender des Aufsichtsrates: Prof. Dr. Helmut Thoma Deelbögenkamp 4c Vorstand: Eckhard Spoerr (Vors.), Axel Krieger, Stephan Esch, Eric Berger 22297 Hamburg Amtsgericht Hamburg, HRB 74048 |
From: <dor...@gm...> - 2005-03-15 22:52:10
|
Just a try if the pic goes into the list |
From: Dorian <dor...@gm...> - 2005-03-15 22:10:04
|
On Tuesday 15 March 2005 22:18, Ben Johnson wrote: > or, hm.... this is starting to come back to me. There was one definite > problem with my scanner. Apparently the case was a slightly darker > color than most people's version of the sm3600. One of the problems this > caused was it wasn't able to find home because it couldn't distinguish > between the color of the plastic case and whatever else is inside the > scanner case at the "home" position that's intended to provide contrast. > I wrote in this list earlier about adjusting some constant in the driver > code. You might want to try that. Yes, that was exactly what I was fiddling around with. I tried values 100, 75, 50 - none of them worked. So I was just experiencing some coincidence: your talking about the contrast between the black markers and the gray contrast led me to the painful easy idea of sticking a piece of white paper over the home, copying the black thingies with a black felt tip. For the purpose of making tha black spots visible through the paper, I drew my desk light, which is halogene one, right near the glass plate. While repainting the spots, I noticed that the stickers which fit the glass plate in the cover were kind of luminescating in a shiney green tone, this could probably be another useful interesting point? However, I made a shot with my mobile phone cam, I don't own a real one, I just need to reboot into the windows os to suck it out and let you have a look. So far, Dorian |
From: Ben J. <be...@bl...> - 2005-03-15 21:18:31
|
On Tue, Mar 15, 2005 at 04:10:06PM +0100, Dorian B?ttner wrote: > Hello, > I'm having the sm3600 and wanted to go with it on my FreeBSD 5.3 > So far, so good. The usb stuff goes fine, device attaches probably but when > starting a prescan the slider stays in it's home doing some kind of knocking > sounds (which appears to be the belt). I went through the archives and found I've seen this problem too. It's been a very long time and I don't remember now how I fixed it. If I remember right, what was happening in my case was that the scanner/software got confused about the position of the scanning light/thing or about the size of the scanning bed and was trying to push the light off the end of the track because it thought "home" was further in that direction. As I said, I don't remember how I fixed it but I'm pretty sure I didn't have to hack the software at all. There may be some options to change that will give the scanner a clue that it should try something different. or, hm.... this is starting to come back to me. There was one definite problem with my scanner. Apparently the case was a slightly darker color than most people's version of the sm3600. One of the problems this caused was it wasn't able to find home because it couldn't distinguish between the color of the plastic case and whatever else is inside the scanner case at the "home" position that's intended to provide contrast. I wrote in this list earlier about adjusting some constant in the driver code. You might want to try that. - Ben |
From: Dorian <dor...@gm...> - 2005-03-15 15:08:58
|
Hello, I'm having the sm3600 and wanted to go with it on my FreeBSD 5.3 So far, so good. The usb stuff goes fine, device attaches probably but when starting a prescan the slider stays in it's home doing some kind of knocking sounds (which appears to be the belt). I went through the archives and found some hint on changing value in homerun.c which I followed, but no success. What I am really astonished about - when I did the initial install about two months ago, the scanner worked, despite the fact that the colors were quite useless -> white paper background appeared as some kind of yellow. Since a couple of weeks later, the problem as described above appears. I'd like to commit at least some debugging/testing, but need some advice. One posting mentions the 'scantool', but that seems to be quite linux-specific, at least I wasn't able to find it. Kind regards, Dorian |
From: Marian E. <mar...@fr...> - 2005-03-02 14:15:50
|
On Tue, Mar 01, 2005 at 09:51:52AM +0100, Helge Hielscher wrote: > Hello, > > since I would like to clean the glas inside the scanner, I wonder what's the > best way to open the scanner like in > http://sm3600.sourceforge.net/calstrip.jpeg Helge, just remove the lid/cover by gently lifting it upwards. Down the revealed pits You find 2 Screws to unlock. After removal of the scews You can remove the upper half of the case containing the glass. It's quite simple after all. > > TIA, > Helge > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > sm3600-devel mailing list > sm3...@li... > https://lists.sourceforge.net/lists/listinfo/sm3600-devel -- Mit freundlichen Gruessen / Yours sincerely Marian Eichholz Postmaster freenet.de AG Vorsitzender des Aufsichtsrates: Prof. Dr. Helmut Thoma Deelbögenkamp 4c Vorstand: Eckhard Spoerr (Vors.), Axel Krieger, Stephan Esch, Eric Berger 22297 Hamburg Amtsgericht Hamburg, HRB 74048 |
From: Helge H. <hhi...@un...> - 2005-03-01 21:35:28
|
Hello, since I would like to clean the glas inside the scanner, I wonder what's the best way to open the scanner like in http://sm3600.sourceforge.net/calstrip.jpeg TIA, Helge |
From: Marian E. <mar...@fr...> - 2004-11-24 07:39:24
|
On Tue, Nov 09, 2004 at 01:10:59AM -0800, Damjan Jovanovic wrote: > Hi > > I am working on a SANE backend for the Microtek > Scanmaker 3800. Currently I can replay the scanning > logs I made under Windows, but that doesn't tell me > enough about how the scanner works to make a proper > driver. Any help you guys could give me about how you > went about making the driver for the 3600 would really > help. Sorry, Damjan, for being *really* busy these weeks. In fact, it's getting worse and worse. > Who did you guys speak to at Microtek to get the > documentation for the 3600? It's a guy from Taiwan, calles Woody Wu. > How did you make your logs? I am basically changing > the DLL import table to fool SMCE32.dll into loading a > fake KERNEL32.dll which then records the WriteFile(), > ReadFile(), and DeviceIoControl() system calls so I > can replay them with libusb (usbsnoopy and family > don't work). In fact, as we mention on our project page(s), we use snoopy, but in a slightly hacked version, because it loses data on large transfers (racing condition) and the author made a patch to cut the bulk transfers. We were interested in the VENDOR commands. > Do you have any information about how ScanWizard 5 > works internally? What parameters do the > scanner-specific DLL's functions like StartScan() > take? No idea. We used it as black box. We were just interested in the command blocks and their results. > What do memory writes (and reads) do to your scanner; Just have a look to the source as "reverse documentation". Since I'm not really shure if I am allowed to pass You a copy of the documentation from microtek. The Memory-commands to precisely what they are called, they write to the memory of the scanner. More or less it is the gamma correction table and the gain correction table. > what do you use them for? A huge amount of data (4-7 > Kb) is written to my scanner through a USB bulk pipe > several times, I am trying to figure out why. No idea. The controllers of our two scanner might work completely different, since the sm3600 uses no bulk writes at all. Bulk transfer is read only for the camera samples. > How did you figure out what the different registers > do? How many are there in total? "Use the source, Luke" :) We have some documentation spread around it, and It will give You a hint, how things work in general. Of course, there is *plenty* of "magic number" stuff around it, I'm sorry. But to make everything nice, shiny and symbolic seems to be a waste of time, since the 3600 series (and therefore the backend design) was obsoleted by Mikrotec *so* fast. > Is anyone with a 3800 interested in helping? It may *really* be interesting if there are *any* similarities between the models. > > Thank you > Damjan > > > > __________________________________ > Do you Yahoo!? > Check out the new Yahoo! Front Page. > www.yahoo.com > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Sybase ASE Linux Express Edition - download now for FREE > LinuxWorld Reader's Choice Award Winner for best database on Linux. > http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click > _______________________________________________ > sm3600-devel mailing list > sm3...@li... > https://lists.sourceforge.net/lists/listinfo/sm3600-devel -- Mit freundlichen Gruessen / Yours sincerely Marian Eichholz Postmaster freenet.de AG Vorsitzender des Aufsichtsrates: Prof. Dr. Helmut Thoma Deelbögenkamp 4c Vorstand: Eckhard Spoerr (Vors.), Axel Krieger, Stephan Esch, Eric Berger 22297 Hamburg Amtsgericht Hamburg, HRB 74048 |
From: Damjan J. <dj...@ya...> - 2004-11-09 09:11:07
|
Hi I am working on a SANE backend for the Microtek Scanmaker 3800. Currently I can replay the scanning logs I made under Windows, but that doesn't tell me enough about how the scanner works to make a proper driver. Any help you guys could give me about how you went about making the driver for the 3600 would really help. Who did you guys speak to at Microtek to get the documentation for the 3600? How did you make your logs? I am basically changing the DLL import table to fool SMCE32.dll into loading a fake KERNEL32.dll which then records the WriteFile(), ReadFile(), and DeviceIoControl() system calls so I can replay them with libusb (usbsnoopy and family don't work). Do you have any information about how ScanWizard 5 works internally? What parameters do the scanner-specific DLL's functions like StartScan() take? What do memory writes (and reads) do to your scanner; what do you use them for? A huge amount of data (4-7 Kb) is written to my scanner through a USB bulk pipe several times, I am trying to figure out why. How did you figure out what the different registers do? How many are there in total? Is anyone with a 3800 interested in helping? Thank you Damjan __________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com |
From: Eve M. <dpl...@ya...> - 2004-08-12 00:56:45
|
I found it. This was the one you were talking about I think. http://www.trydownloading.com/ref44.html You're able to download dvd movies, console games, music. I had found at least 82 CD's on there that I wanted. I can't wait untill you get a load of this selection of games & music & movies - it's nuts. Theres areas in the website that have walkthroughs on how to burn your selections to CD. I can tell you one thing, after I went through the movie section, I can't stop looking through it, theres movies in here still in theaters. I'll call later. Arron |