[sane-devel] Problem: X-Server crashes when using XSane
Hi, thanks. Well...but there is more than just crashes of the X-Server. With other Programs (xscanimage) i only get a error message. I think the X-Server crash is just the consequenz of something else. As i wrote, i sometimes also get this Failed to start scanner: error during device I/O message. And in the sane-project.org FAQ is written to connect the mailing list, if an error like this appears. I'd really be happy if i could solve this problem... Christoph Julien BLACHE schrieb: Christoph M. Schr?der cmschroeder at maxi-dsl.de wrote: Hi, But suddenly, (i think after i did some black and white negative scans), i could not use the transparency adapter anymore. Every time i want to use it now, the X-Server crashes up and starts from new (also when i As they say at X.org, an X server crash is a bug in the X server :) JB.
[sane-devel] Problem: X-Server crashes when using XSane
Christoph M. Schr?der cmschroeder at maxi-dsl.de wrote: Hi, i wrote, i sometimes also get this Failed to start scanner: error during device I/O message. And in the sane-project.org FAQ is written to connect the mailing list, if an error like this appears. I'd really be happy if i could solve this problem... You should post the logs somewhere publicly viewable, as the forum you used seems to be password-protected. JB. -- Julien BLACHE http://www.jblache.org jb at jblache.org GPG KeyID 0xF5D65169
[sane-devel] Problem: X-Server crashes when using XSane
Hi, thanks for the information. My fault. You can now find them here: http://home.mnet-online.de/hta/syslog.txt http://home.mnet-online.de/hta/messages.txt Christoph Julien BLACHE schrieb: Christoph M. Schr?der cmschroeder at maxi-dsl.de wrote: Hi, i wrote, i sometimes also get this Failed to start scanner: error during device I/O message. And in the sane-project.org FAQ is written to connect the mailing list, if an error like this appears. I'd really be happy if i could solve this problem... You should post the logs somewhere publicly viewable, as the forum you used seems to be password-protected. JB.
[sane-devel] USB problems - [wasno devices available]
Well, it seems that you are well on the way to solving the problems. What you have to do about the camera ought to be quite similar to what you have to do about the scanner. The reason why I cannot give you more specific advice is that I have no idea of the way that Hardy Heron is setting up these kinds of things. There are all kinds of ways to do it. Some examples: let root only run the given class of usb devices let all users run the given class of usb devices let only one user run the given class of usb devices let a group do it, for example a group called scanner and if it is done this way then any given user who is supposed to have access to the scanner needs to get added to the group, a separate operation. In all of the above, for scanner you can substitute camera of course. And by all means, you should finish the job in a manner which is compatible with Hardy Heron. If they want you to use a group, then use a group. Call it what they called it for the rest of the scanners (cameras). And so on. Now, I am just curious. Is there a specific line for your camera in the libgphoto2.rules file? If so, then what does it say? If that line is set up correctly, then IMHO the camera ought to work. If it is a PTP camera, then PTP support is done through the libgphoto2 PTP driver. If it requires some proprietary Canon driver, then that is supported through the libgphoto2 Canon driver. In either event, the permissions given in libgphoto2.rules ought to suffice for access to the camera, and AFAICT there ought to be no need at all for a more general statement in the permissions.rules file. Similar remarks pertain to the scanner, naturally. Theodore Kilgore On Sat, 21 Jun 2008, earther at eartherdesigns.com wrote: Yes, you are correct that it is a permissions problem, I finally got the camera working properly by editing /etc/udev/rules.d/40-permissions.rules as per this thread: http://ubuntuforums.org/showthread.php?t=784864 I can now run xsane as root but not as user. I have looked through Groups settings several times and everything looks OK so I'm guessing I'll need to do more hand-editing. I'm too tired to do any more with this tonight but tomorrow I will revisit your comments and see where I can go with them. Thanks so much for your thoughts on this. Quoting kilgota at banach.math.auburn.edu: Hi, Don't know about the scanner, but I do know a bit about the internals of libgphoto2. The problem with the scanner is most probably similar to what appears to happen with the camera: With approximately 99% probability, I would say that your problem with the camera is a permissions problem. Quite likely, what has happened is that the camera and perhaps the scanner also, is not listed in any of the appropriate files in /etc/udev/rules.d in spite of the fact that you have upgraded udev. Either that, or along with the upgraded udev the rules are not what you expect. For example, the libgphoto2.rules might expect you, as a user, to belong to a group called camera or some variation on the same theme. One of the things that you might do to try to localize the problem is to try running these devices as root. If that works, then definitely it is a permissions problem and you need to create the right entries in the libgphoto2.rules file and the libsane.rules files, which are suitable for yourself, or if you do find entries in those files for these devices (look for the USB Vendor:Product number combination) and it wants your userid to belong to some group and it does not, then either add yourself to the group or change the rules file to let you do what you want. By all means, too, you can contact Ubuntu and ask them just exactly what they have in mind about how they intend for things like this to be done in Hardy Heron. I do not know how they are handling such things as upgrades because I am not using Ubuntu and instead I usually deal with things like this by hand-editing the affected files. Sorry that there are these problems with permissions, but the alternative is that these problems are not under control and then we would have a Linux with all the lack of security that is found in Windows. Clearly, none of us want that. But in return for the care about security comes some occasional inconvenience, in the form of problems like this. I hope this helps. Theodore Kilgore On Fri, 20 Jun 2008, earther at eartherdesigns.com wrote: Good news. I have made some progress after upgrading the Hardy udev package but still not out of the woods. lsusb now prints out correctly: ~$ lsusb Bus 008 Device 001: ID : Bus 007 Device 001: ID : Bus 006 Device 002: ID 03f0:0205 Hewlett-Packard ScanJet 3300c Bus 006 Device 001: ID : Bus 005 Device 001: ID : Bus 004 Device 001: ID : Bus 003 Device 001: ID : Bus 002 Device 006: ID 04a9:30fd Canon, Inc. PowerShot A610 (normal mode)/PowerShot
[sane-devel] Problem with libusb and 64 bits 2.6.25 kernel
Hi Dennis, A bug was opened a while back by Sam Varshavchik, concerning the pixma backend for Canon ImageClass MF-4270, when compiled and used on a 64 bits platform (no issue so far on 32 bits), details are given here: https://alioth.debian.org/tracker/?group_id=30186atid=410366func=detailaid=310861 We shared with Sam some info to try to locate the origin, which looked to be related to the 64 bits libusb. Sam has performed investigations since then, his conclusions spot on that 32 and 64 bits libusb behave slightly differently when reading data from USB, more precisely, the 64 bits libusb seems to expect an exact count of bytes to read (but not 32 bits libusb), and fails (timeout) if such count is not satisfied. Sam, in his last post on the bug report page, proposes a patch, which looks to me fine for both 32 and 64 bits, and impacts only the ImageClass part of the backend. Dennis, If you don't mind, could you also have a look and give a try, so that we can commit into CVS. Nicolas
[sane-devel] USB problems - [wasno devices available]
More in depth response to come but I wanted to send a quick note that the problem has been solved! Buried in the 60 page thread on running the Hardy kernel on Gutsy, I found the solution! http://ubuntuforums.org/showpost.php?p=4335549postcount=364 I added that file and I can now run xsane as user. I suspect that it fixed the camera problem too - I realize the other solution was just a workaround. Hopefully this thread will be useful for others in the future. Thanks so much for all your input. I will digest it a bit later - kinda burned out now. :) Quoting kilgota at banach.math.auburn.edu: Well, it seems that you are well on the way to solving the problems. What you have to do about the camera ought to be quite similar to what you have to do about the scanner. The reason why I cannot give you more specific advice is that I have no idea of the way that Hardy Heron is setting up these kinds of things. There are all kinds of ways to do it. Some examples: let root only run the given class of usb devices let all users run the given class of usb devices let only one user run the given class of usb devices let a group do it, for example a group called scanner and if it is done this way then any given user who is supposed to have access to the scanner needs to get added to the group, a separate operation. In all of the above, for scanner you can substitute camera of course. And by all means, you should finish the job in a manner which is compatible with Hardy Heron. If they want you to use a group, then use a group. Call it what they called it for the rest of the scanners (cameras). And so on. Now, I am just curious. Is there a specific line for your camera in the libgphoto2.rules file? If so, then what does it say? If that line is set up correctly, then IMHO the camera ought to work. If it is a PTP camera, then PTP support is done through the libgphoto2 PTP driver. If it requires some proprietary Canon driver, then that is supported through the libgphoto2 Canon driver. In either event, the permissions given in libgphoto2.rules ought to suffice for access to the camera, and AFAICT there ought to be no need at all for a more general statement in the permissions.rules file. Similar remarks pertain to the scanner, naturally. Theodore Kilgore On Sat, 21 Jun 2008, earther at eartherdesigns.com wrote: Yes, you are correct that it is a permissions problem, I finally got the camera working properly by editing /etc/udev/rules.d/40-permissions.rules as per this thread: http://ubuntuforums.org/showthread.php?t=784864 I can now run xsane as root but not as user. I have looked through Groups settings several times and everything looks OK so I'm guessing I'll need to do more hand-editing. I'm too tired to do any more with this tonight but tomorrow I will revisit your comments and see where I can go with them. Thanks so much for your thoughts on this. Quoting kilgota at banach.math.auburn.edu: Hi, Don't know about the scanner, but I do know a bit about the internals of libgphoto2. The problem with the scanner is most probably similar to what appears to happen with the camera: With approximately 99% probability, I would say that your problem with the camera is a permissions problem. Quite likely, what has happened is that the camera and perhaps the scanner also, is not listed in any of the appropriate files in /etc/udev/rules.d in spite of the fact that you have upgraded udev. Either that, or along with the upgraded udev the rules are not what you expect. For example, the libgphoto2.rules might expect you, as a user, to belong to a group called camera or some variation on the same theme. One of the things that you might do to try to localize the problem is to try running these devices as root. If that works, then definitely it is a permissions problem and you need to create the right entries in the libgphoto2.rules file and the libsane.rules files, which are suitable for yourself, or if you do find entries in those files for these devices (look for the USB Vendor:Product number combination) and it wants your userid to belong to some group and it does not, then either add yourself to the group or change the rules file to let you do what you want. By all means, too, you can contact Ubuntu and ask them just exactly what they have in mind about how they intend for things like this to be done in Hardy Heron. I do not know how they are handling such things as upgrades because I am not using Ubuntu and instead I usually deal with things like this by hand-editing the affected files. Sorry that there are these problems with permissions, but the alternative is that these problems are not under control and then we would have a Linux with all the lack of security that is found in Windows. Clearly, none of us want that. But in return for the care about security comes some occasional inconvenience, in the form of problems
[sane-devel] New Scanner Purchase .....
HP is the only brand in the market here (Chiang Mai, Thailand). There are others of course but they are at the total junk status. HP is the only company with anything credible ... You may take a look at HP 5590 model. Most of the basic functions are supported, and it has ADF unit (in my opinion, has low mechanical reliability). The model is still available, at least on HP.com. And HP7650 is also supported, which has improved scanning speed, but is more expensive. Anyway, I would consider them as the models for low volume scanning, otherwise I would prefer Fujitsu. Best regards, -- Ilia Sotnikov
[sane-devel] problems with genesys and MD6228
Am Dienstag, 17. Juni 2008 06:38:30 schrieb stef: I've gone through the logs, and I think they are logs of another usb device on the windows machine where they have been recorded. Sorry, I'm late, but my access to a Windows-PC is difficult. Yes, the old logs come from the mouse, but in each cases the scanner was selected. The UsbSnoop-programms seems to work a bit incorrect. It takes more than one try to snoop the right device and not the mouse. My indikation was the growth from the log file with automatic refresh 1 s. I found 2 scanner-devices in the UsbSnoop-window, but only 1 was connected. Also, I have made a log with each device. Both works, 100 dpi, A4. I hope it helps. Files are coming direct. -- Viele Gr??e Werner Holtfreter
[sane-devel] Plustek OpticPro UT12 [0x07b3/0x0013] [plustek backend] works!
Hi all, this is my first post :) I have Plustek OpticPro UT12 usb scanner marked as Unsupported and it works with x-sane/sane at line/gray/RGB up to 1200dpi. Please add it to supported list http://www.sane-project.org/sane-mfgs.html and correct libsane.usermap Thanks LLG :D -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080622/ffa93f55/attachment.htm -- next part -- An embedded and charset-unspecified text was scrubbed... Name: PlustekUT12-lsusb.txt Url: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080622/ffa93f55/attachment.txt -- next part -- An embedded and charset-unspecified text was scrubbed... Name: PlustekUT12-sane-find-scanner.txt Url: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080622/ffa93f55/attachment-0001.txt -- next part -- An embedded and charset-unspecified text was scrubbed... Name: PlustekUT12-libsane.usermap.txt Url: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080622/ffa93f55/attachment-0002.txt
[sane-devel] Plustek OpticPro UT12 [0x07b3/0x0013] [plustek backend] works!
On Sunday 22 June 2008 21:58:48 litlle girl wrote: Hi all, this is my first post :) I have Plustek OpticPro UT12 usb scanner marked as Unsupported and it works with x-sane/sane at line/gray/RGB up to 1200dpi. Please add it to supported list http://www.sane-project.org/sane-mfgs.html and correct libsane.usermap Thanks LLG :D Hi, thanks for this report. In fact the support for the device with devid 0x0013 is already included, but it has not been identified as UT12 so far - I'll change that. BTW: could you please send mit the output of: export SANE_DEBUG_PLUSTEK=19 ; scanimage -L TIA Gerhard
[sane-devel] Could XSane process the threshold while lineArt scan?
Hi, I have a doubt that who in charge of processing the threshold while lineArt scan.XSane or my driver? If XSane could process the threshold, how could my drvier to do? My driver process threshold while lineArt scan now. If XSane could process threshold, my driver would get simple. Thank you. -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080623/06f9dd36/attachment.htm
[sane-devel] Could XSane process the threshold while lineArt scan?
On Mon, Jun 23, 2008 at 05:04:57PM +0800, eagleskycloud wrote: My driver process threshold while lineArt scan now. If XSane could process threshold, my driver would get simple. IMHO lineArt should be advertised only for devices that can do the conversion in hardware. Doing it in hardware has the benefit of reduced USB/SCSI bandwidth. Drivers should not cover up for cheap hardware. There is a list of planned features for XSane. http://www.xsane.org/xsane-future.html If you want lineArt conversion to be included there, you need to contact the author. He is no longer on this mailing list. Daniel
[sane-devel] Could XSane process the threshold while lineArt scan?
On 6/23/08, Daniel Gl?ckner daniel-gl at gmx.net wrote: On Mon, Jun 23, 2008 at 05:04:57PM +0800, eagleskycloud wrote: My driver process threshold while lineArt scan now. If XSane could process threshold, my driver would get simple. IMHO lineArt should be advertised only for devices that can do the conversion in hardware. Doing it in hardware has the benefit of reduced USB/SCSI bandwidth. Drivers should not cover up for cheap hardware. There is a list of planned features for XSane. http://www.xsane.org/xsane-future.html If you want lineArt conversion to be included there, you need to contact the author. He is no longer on this mailing list. this is a place where i disagree with daniel, for two reasons- 1. It would still help with bandwidth in the net backend case, which sould like it might become the standard in some future version of sane. 2. it is good if all backends present a similar interface, so that front-ends like scanimage can still have access to these functions. to that end- i have been working on a sanei_threshold library that backends of dumb scanners could share. it still has the same effect of code only in one place. i need a good algorithm though- eagleskycloud- what mechanism were you planning to use? straight threshold, or something adaptive? allan -- The truth is an offense, but not a sin
[sane-devel] [RFC][PATCH] sanei configuration framework extension
Le Thursday 19 June 2008 15:36:59 m. allan noah, vous avez ?crit?: pretty good, but i have two comments: 1. i think calling the struct SANE_Config instead of something with sanei in it, makes it look too much like something that should be in the SANE standard, instead of the internal-use function that it is. 2. some backends seem to have dozens of options, that struct is going to become quite large if it is extending to hold everything. does it instead make more sense for the callback to be run for each line extracted from the file, with a flag indicating that it was an option instead of an attach line? allan Hello, here's a new take at config option parsing. The struct is now called SANEI_Config, and holds an array of SANE_Option_Descriptor and an array of placeholder for the values of the options. To parse options, a backend first creates a list of the options it wants using SANE_Option_Descriptor. Then it calls sanei_configure_initialize() which creates the placeholders. When the SANEI_Config is ready, the backend calls sanei_configure_attach() which opens the configuration, parse it according to the given descriptors. Whenever a line no recognized as an option is met, the sanei_configure_attach() calls the backend provided (*attach)(SANEI_Config *, char *devname) attach function. This backend specific function calls the usb/scsi/parport attach functions allready provided by sanei library. As a parameter it has the currently parsed options in the config struct and so may use them during the attach. A sanei_configure_get_value() helper is given to access the values of the options. Once parsing is done, there is a sanei_configure_dispose() function to release allocated ressources. By doing this way, configuration is parsed only with the options the backend needs. The existing sanei_check_value() may be reused to check if constraints are respected. Only a couple options that need a complex syntax couldn't be handled right now (such as 'calibrate /path/name port' from canon_pp) but could be handled by a SANE_TYPE_STRING_LIST to be created. The appended patch currently only manage SANE_TYPE_STRING options and as been tested with a modified rts8891 backend. Regards, Stef -- next part -- A non-text attachment was scrubbed... Name: proposal.patch.gz Type: application/x-gzip Size: 4841 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080623/81b6169c/attachment.bin
[sane-devel] problems with genesys and MD6228
Le Sunday 22 June 2008 19:12:23 Werner Holtfreter, vous avez ?crit?: Am Dienstag, 17. Juni 2008 06:38:30 schrieb stef: I've gone through the logs, and I think they are logs of another usb device on the windows machine where they have been recorded. Sorry, I'm late, but my access to a Windows-PC is difficult. Yes, the old logs come from the mouse, but in each cases the scanner was selected. The UsbSnoop-programms seems to work a bit incorrect. It takes more than one try to snoop the right device and not the mouse. My indikation was the growth from the log file with automatic refresh 1 s. I found 2 scanner-devices in the UsbSnoop-window, but only 1 was connected. Also, I have made a log with each device. Both works, 100 dpi, A4. I hope it helps. Files are coming direct. -- Viele Gr??e Werner Holtfreter Hello, thanks a lot for the data. I'm currently trying to find what may be going on in it. Regards, Stef
[sane-devel] [RFC][PATCH] sanei configuration framework extension
On Mon, Jun 23, 2008 at 3:36 PM, stef stef.dev at free.fr wrote: Le Thursday 19 June 2008 15:36:59 m. allan noah, vous avez ?crit : pretty good, but i have two comments: 1. i think calling the struct SANE_Config instead of something with sanei in it, makes it look too much like something that should be in the SANE standard, instead of the internal-use function that it is. 2. some backends seem to have dozens of options, that struct is going to become quite large if it is extending to hold everything. does it instead make more sense for the callback to be run for each line extracted from the file, with a flag indicating that it was an option instead of an attach line? allan Hello, here's a new take at config option parsing. The struct is now called SANEI_Config, and holds an array of SANE_Option_Descriptor and an array of placeholder for the values of the options. brilliant. enables us to reuse lots of code, and keep a familiar interface. bravo. To parse options, a backend first creates a list of the options it wants using SANE_Option_Descriptor. great. Then it calls sanei_configure_initialize() which creates the placeholders. When the SANEI_Config is ready, the backend calls sanei_configure_attach() which opens the configuration, parse it according to the given descriptors. Whenever a line no recognized as an option is met, the sanei_configure_attach() calls the backend provided (*attach)(SANEI_Config *, char *devname) attach function. This backend specific function calls the usb/scsi/parport attach functions allready provided by sanei library. As a parameter it has the currently parsed options in the config struct and so may use them during the attach. A sanei_configure_get_value() helper is given to access the values of the options. Once parsing is done, there is a sanei_configure_dispose() function to release allocated ressources. i would rather that the backend provided the placeholder memory if possible, for two reasons: 1. to keep all the memory allocations in one place, 2. so that the placeholders can be pre-loaded with default values by the backend. By doing this way, configuration is parsed only with the options the backend needs. The existing sanei_check_value() may be reused to check if constraints are respected. Only a couple options that need a complex syntax couldn't be handled right now (such as 'calibrate /path/name port' from canon_pp) but could be handled by a SANE_TYPE_STRING_LIST to be created. The appended patch currently only manage SANE_TYPE_STRING options and as been tested with a modified rts8891 backend. this sounds quite good- thank you very much for taking on the task! allan -- The truth is an offense, but not a sin
[sane-devel] Could XSane process the threshold while lineArt scan?
My driver process the threshold at present . If the value of pixel greater than the threshold ,the value of pixel is set 255. Otherwise the value of pixel is set 0. 2008/6/23 m. allan noah kitno455 at gmail.com: On 6/23/08, Daniel Gl?ckner daniel-gl at gmx.net wrote: On Mon, Jun 23, 2008 at 05:04:57PM +0800, eagleskycloud wrote: My driver process threshold while lineArt scan now. If XSane could process threshold, my driver would get simple. IMHO lineArt should be advertised only for devices that can do the conversion in hardware. Doing it in hardware has the benefit of reduced USB/SCSI bandwidth. Drivers should not cover up for cheap hardware. There is a list of planned features for XSane. http://www.xsane.org/xsane-future.html If you want lineArt conversion to be included there, you need to contact the author. He is no longer on this mailing list. this is a place where i disagree with daniel, for two reasons- 1. It would still help with bandwidth in the net backend case, which sould like it might become the standard in some future version of sane. 2. it is good if all backends present a similar interface, so that front-ends like scanimage can still have access to these functions. to that end- i have been working on a sanei_threshold library that backends of dumb scanners could share. it still has the same effect of code only in one place. i need a good algorithm though- eagleskycloud- what mechanism were you planning to use? straight threshold, or something adaptive? allan -- The truth is an offense, but not a sin -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080624/3b78b4b4/attachment.htm
[sane-devel] Could XSane process the threshold while lineArt scan?
On 6/23/08, eagleskycloud eagleskycloud at gmail.com wrote: My driver process the threshold at present . If the value of pixel greater than the threshold ,the value of pixel is set 255. Otherwise the value of pixel is set 0. well, that is not very much code, so i would leave it in your backend. if someone ever writes a good adaptive algorithm and your source code is free, it can be updated. I plan to do the same with my backends. allan 2008/6/23 m. allan noah kitno455 at gmail.com: On 6/23/08, Daniel Gl?ckner daniel-gl at gmx.net wrote: On Mon, Jun 23, 2008 at 05:04:57PM +0800, eagleskycloud wrote: My driver process threshold while lineArt scan now. If XSane could process threshold, my driver would get simple. IMHO lineArt should be advertised only for devices that can do the conversion in hardware. Doing it in hardware has the benefit of reduced USB/SCSI bandwidth. Drivers should not cover up for cheap hardware. There is a list of planned features for XSane. http://www.xsane.org/xsane-future.html If you want lineArt conversion to be included there, you need to contact the author. He is no longer on this mailing list. this is a place where i disagree with daniel, for two reasons- 1. It would still help with bandwidth in the net backend case, which sould like it might become the standard in some future version of sane. 2. it is good if all backends present a similar interface, so that front-ends like scanimage can still have access to these functions. to that end- i have been working on a sanei_threshold library that backends of dumb scanners could share. it still has the same effect of code only in one place. i need a good algorithm though- eagleskycloud- what mechanism were you planning to use? straight threshold, or something adaptive? allan -- The truth is an offense, but not a sin -- The truth is an offense, but not a sin
[sane-devel] Problem: X-Server crashes when using XSane
Hi, please also provide the log produced by SANE_DEBUG_SNAPSCAN=255 xsane 2 debug.log then use xsane until the error occurs. The logs tend to get quite big, so you should compress it. Regards, Oliver On 21.06.2008, at 17:46, Christoph M. Schr?der wrote: Hi, thanks for the information. My fault. You can now find them here: http://home.mnet-online.de/hta/syslog.txt http://home.mnet-online.de/hta/messages.txt Christoph Julien BLACHE schrieb: Christoph M. Schr?der cmschroeder at maxi-dsl.de wrote: Hi, i wrote, i sometimes also get this Failed to start scanner: error during device I/O message. And in the sane-project.org FAQ is written to connect the mailing list, if an error like this appears. I'd really be happy if i could solve this problem...
[sane-devel] New Scanner Purchase .....
An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080624/f6121bc0/attachment.htm
[sane-devel] New Scanner Purchase .....
On Tue, Jun 24, 2008 at 1:15 PM, David Lochrin dlochrin at d2.net.au wrote: On Tuesday 24 June 2008 19:13, peter wrote: HP it seems is a very interesting company when it comes to the planet as a whole. The HP Scanjet 5590 is listed at US$299.99 on the hp.com site. The open market in the States will offer for say 10% less. In Thailand the price (converted on xe.com) is US$596. Now that is a shock. But in what I thought was fair and open Singapore the price is even higher, US$658. Fascinating! In Australia it's listed at AU$999 or US$953 - see http://h10010.www1.hp.com/wwpc/au/en/ho/WF02a/1090037-1090177-1090485.html Better to rush out and buy HP stock, at these margins the company is going to make a lot of money. Considering that the price is too high for this model (in my opinion) the whole picture becomes rather sad. -- Ilia Sotnikov
[sane-devel] Problem with libusb and 64 bits 2.6.25 kernel
Right now my build system is acting a bit screwy. I started working on another USB device and now xsane isn't working, so I think I messed something up and am not currently set up to do sane development at the moment. In any case, I took a look at the patch. Basically, it's a one-liner that changes the minimum block size from 512 to the remainder. The reason I chose a 512 byte minimum block size is that the Windows driver does it that way, so I imitated. If the patch works in 64bit libusb, it looks to me that it would likely work in 32bit as well. However, it may take me a few days to rebuild my sane development environment and confirm. My recollection of the USB spec is a bit hazy, but 64bit libusb behavior doesn't seem correct to me. -Dennis - Original Message From: Nicolas nicolas.mar...@freesurf.fr To: Dennis Lou dlou99 at yahoo.com Cc: mrsam-guest at alioth.debian.org; sane-devel sane-devel at lists.alioth.debian.org Sent: Saturday, June 21, 2008 9:07:56 AM Subject: Re: [sane-devel] Problem with libusb and 64 bits 2.6.25 kernel Hi Dennis, A bug was opened a while back by Sam Varshavchik, concerning the pixma backend for Canon ImageClass MF-4270, when compiled and used on a 64 bits platform (no issue so far on 32 bits), details are given here: https://alioth.debian.org/tracker/?group_id=30186atid=410366func=detailaid=310861 We shared with Sam some info to try to locate the origin, which looked to be related to the 64 bits libusb. Sam has performed investigations since then, his conclusions spot on that 32 and 64 bits libusb behave slightly differently when reading data from USB, more precisely, the 64 bits libusb seems to expect an exact count of bytes to read (but not 32 bits libusb), and fails (timeout) if such count is not satisfied. Sam, in his last post on the bug report page, proposes a patch, which looks to me fine for both 32 and 64 bits, and impacts only the ImageClass part of the backend. Dennis, If you don't mind, could you also have a look and give a try, so that we can commit into CVS. Nicolas
[sane-devel] New Scanner Purchase .....
On Tuesday 24 June 2008 19:13, peter wrote: HP it seems is a very interesting company when it comes to the planet as a whole.? The HP Scanjet 5590 is listed at US$299.99 on the hp.com site.? The open market in the States will offer for say 10% less. In Thailand the price (converted on xe.com) is US$596.? Now that is a shock.? But in what I thought was fair and open Singapore the price is even higher, US$658. Fascinating! In Australia it's listed at AU$999 or US$953 - see http://h10010.www1.hp.com/wwpc/au/en/ho/WF02a/1090037-1090177-1090485.html Better to rush out and buy HP stock, at these margins the company is going to make a lot of money. But not from me. Or me. David
[sane-devel] Problem: X-Server crashes when using XSane
Hi, thanks Oliver. This is what i'm getting showed in the terminal: $ SANE_DEBUG_SNAPSCAN=255 xsane 2debug.log User defined signal 1 $ And here you can find what appeared today in var/log/debug: http://home.mnet-online.de/hta/debug.txt Christoph Oliver Schwartz schrieb: Hi, please also provide the log produced by SANE_DEBUG_SNAPSCAN=255 xsane 2 debug.log then use xsane until the error occurs. The logs tend to get quite big, so you should compress it. Regards, Oliver On 21.06.2008, at 17:46, Christoph M. Schr?der wrote: Hi, thanks for the information. My fault. You can now find them here: http://home.mnet-online.de/hta/syslog.txt http://home.mnet-online.de/hta/messages.txt Christoph Julien BLACHE schrieb: Christoph M. Schr?der cmschroeder at maxi-dsl.de wrote: Hi, i wrote, i sometimes also get this Failed to start scanner: error during device I/O message. And in the sane-project.org FAQ is written to connect the mailing list, if an error like this appears. I'd really be happy if i could solve this problem...
[sane-devel] Problem: X-Server crashes when using XSane
Sorry, here the complete compressed debug.log. Christoph M. Schr?der schrieb: Hi, thanks Oliver. This is what i'm getting showed in the terminal: $ SANE_DEBUG_SNAPSCAN=255 xsane 2debug.log User defined signal 1 $ And here you can find what appeared today in var/log/debug: http://home.mnet-online.de/hta/debug.txt Christoph Oliver Schwartz schrieb: Hi, please also provide the log produced by SANE_DEBUG_SNAPSCAN=255 xsane 2 debug.log then use xsane until the error occurs. The logs tend to get quite big, so you should compress it. Regards, Oliver On 21.06.2008, at 17:46, Christoph M. Schr?der wrote: Hi, thanks for the information. My fault. You can now find them here: http://home.mnet-online.de/hta/syslog.txt http://home.mnet-online.de/hta/messages.txt Christoph Julien BLACHE schrieb: Christoph M. Schr?der cmschroeder at maxi-dsl.de wrote: Hi, i wrote, i sometimes also get this Failed to start scanner: error during device I/O message. And in the sane-project.org FAQ is written to connect the mailing list, if an error like this appears. I'd really be happy if i could solve this problem... -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080624/93d5281c/attachment-0001.htm -- next part -- A non-text attachment was scrubbed... Name: debug.tar.gz Type: application/x-gzip Size: 14017 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080624/93d5281c/attachment-0001.bin
[sane-devel] Problem: X-Server crashes when using XSane
Hi, the interesting part is the contents of the file 'debug.log', which should be created in the directory from which you started xsane. Regards, Oliver On 24.06.2008, at 17:50, Christoph M. Schr?der wrote: Hi, thanks Oliver. This is what i'm getting showed in the terminal: $ SANE_DEBUG_SNAPSCAN=255 xsane 2debug.log User defined signal 1 $
[sane-devel] Problem: X-Server crashes when using XSane
Sorry, i missunderstood. But were can i find it? XSane just started up when i typed in what you wrote me. And i don't know were i can find an XSane directory... Oliver Schwartz schrieb: Hi, the interesting part is the contents of the file 'debug.log', which should be created in the directory from which you started xsane. Regards, Oliver On 24.06.2008, at 17:50, Christoph M. Schr?der wrote: Hi, thanks Oliver. This is what i'm getting showed in the terminal: $ SANE_DEBUG_SNAPSCAN=255 xsane 2debug.log User defined signal 1 $
[sane-devel] Problem: X-Server crashes when using XSane
Sorry, now i got it. Oliver Schwartz schrieb: Hi, the interesting part is the contents of the file 'debug.log', which should be created in the directory from which you started xsane. Regards, Oliver On 24.06.2008, at 17:50, Christoph M. Schr?der wrote: Hi, thanks Oliver. This is what i'm getting showed in the terminal: $ SANE_DEBUG_SNAPSCAN=255 xsane 2debug.log User defined signal 1 $ -- next part -- A non-text attachment was scrubbed... Name: debug.log.tar.gz Type: application/x-gzip Size: 3064 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080624/ff64b51a/attachment.bin
[sane-devel] New Scanner Purchase .....
I've been following this thread from the beginning shown below. I only recently got involved with Linux as part of a work project to determine if it was a suitable replacement for Windows on some of our computers. I also decided to try it on my three home computers. After investigating a number of distributions, I decided against it because of connectivity problems with our network, and at home I had a lot of trouble using a dialup modem. While reading a book on current hardware, I noticed the author highly recommended Xandros. I hadn't tried it so I purchased their professional version to test. It worked wonderful. Very user friendly, which is important to desktop users without computer skills. Also, no network or modem problems. I now have Xandros on seven systems at work and all three of my home systems. This brings us to my current disappointment. First, I sent two e-mails to this forum about HP4890 support without a single response. Now I see this overall support issue is pretty widespread. Without a reasonable support structure for peripheral devices, printers included along with scanners, Linux is never going to be a mainstream OS. Some people may say that's just fine, but then this superb distribution of software is lost on a small number of people. Many of the packages that are available with Linux are far better than their Windows counterparts - and they're free. Please, please don't ask me to buy another scanner when I have a top-of-the-line HP scanner and there's no support for it. HP is one of the world leaders in scanning equipment, and this type of hardware is widespread and needs to be supported. Chuck Brigermann Original Message From: peter...@gmail.com To: sane-devel at lists.alioth.debian.org Subject: [sane-devel] New Scanner Purchase . Date: Sat, 21 Jun 2008 14:29:33 +0700 My HP Scanjet 3970 is on its way out . I would like to replace with another HP and I have just been comparing the HP Scanjet current models (from the HP site) with what is and what is not supported in Sane. It appears that more or less everything is not supported. This I find very surprising and so I was wondering if I had missed the point somewhere?br br I would like to use either a Scanjet G4010 or a G4050 but since both are unsupported (in common with the rest of the current scanners) I am very reluctant to buy and see what happens.br br Could anyone please tell me if I have got this wrong or is there another way round this?br br br /body /html
[sane-devel] Fwd: New Scanner Purchase .....
embarrased Apologies to Chuck, I hit the wrong respond button. /embarrased Marty -- Forwarded message -- From: Skorous skor...@gmail.com Date: Tue, Jun 24, 2008 at 1:33 PM Subject: Re: [sane-devel] New Scanner Purchase . To: chuck brigermann co2 at lenoxlaser.com My grandmother always said, God helps those who help themselves. ;-) Being serious for a moment, this is not HP tech support. If HP doesn't provide a driver ( I don't know if they do or not, I didn't look ) then _someone_ has to write one. And many of these companies aren't forthcoming with design specs. This means someone has to by the equipment, reverse engineer the protocol, then write the software. Keep in mind that these people are _not_ employed by HP to do this. If you really need support for this scanner and no one in the development community has written one, then you need to complain to HP. However, this is just my $.02. Marty On Tue, Jun 24, 2008 at 12:50 PM, chuck brigermann co2 at lenoxlaser.com wrote: I've been following this thread from the beginning shown below. I only recently got involved with Linux as part of a work project to determine if it was a suitable replacement for Windows on some of our computers. I also decided to try it on my three home computers. After investigating a number of distributions, I decided against it because of connectivity problems with our network, and at home I had a lot of trouble using a dialup modem. While reading a book on current hardware, I noticed the author highly recommended Xandros. I hadn't tried it so I purchased their professional version to test. It worked wonderful. Very user friendly, which is important to desktop users without computer skills. Also, no network or modem problems. I now have Xandros on seven systems at work and all three of my home systems. This brings us to my current disappointment. First, I sent two e-mails to this forum about HP4890 support without a single response. Now I see this overall support issue is pretty widespread. Without a reasonable support structure for peripheral devices, printers included along with scanners, Linux is never going to be a mainstream OS. Some people may say that's just fine, but then this superb distribution of software is lost on a small number of people. Many of the packages that are available with Linux are far better than their Windows counterparts - and they're free. Please, please don't ask me to buy another scanner when I have a top-of-the-line HP scanner and there's no support for it. HP is one of the world leaders in scanning equipment, and this type of hardware is widespread and needs to be supported. Chuck Brigermann Original Message From: petercmx at gmail.com To: sane-devel at lists.alioth.debian.org Subject: [sane-devel] New Scanner Purchase . Date: Sat, 21 Jun 2008 14:29:33 +0700 My HP Scanjet 3970 is on its way out . I would like to replace with another HP and I have just been comparing the HP Scanjet current models (from the HP site) with what is and what is not supported in Sane. It appears that more or less everything is not supported. This I find very surprising and so I was wondering if I had missed the point somewhere?br br I would like to use either a Scanjet G4010 or a G4050 but since both are unsupported (in common with the rest of the current scanners) I am very reluctant to buy and see what happens.br br Could anyone please tell me if I have got this wrong or is there another way round this?br br br /body /html -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org
[sane-devel] Fwd: New Scanner Purchase .....
I always check printers and scanners, etc. for Linux support before I buy them. :-) A good rule of thumb is not to buy something recent. Btw, someone is maybe going to add support for that scanner since it is a new Genesys chip and the specs are available. On Tue, June 24, 2008 1:37 pm, Skorous wrote: embarrased Apologies to Chuck, I hit the wrong respond button. /embarrased Marty -- Forwarded message -- From: Skorous skorous at gmail.com Date: Tue, Jun 24, 2008 at 1:33 PM Subject: Re: [sane-devel] New Scanner Purchase . To: chuck brigermann co2 at lenoxlaser.com My grandmother always said, God helps those who help themselves. ;-) Being serious for a moment, this is not HP tech support. If HP doesn't provide a driver ( I don't know if they do or not, I didn't look ) then _someone_ has to write one. And many of these companies aren't forthcoming with design specs. This means someone has to by the equipment, reverse engineer the protocol, then write the software. Keep in mind that these people are _not_ employed by HP to do this. If you really need support for this scanner and no one in the development community has written one, then you need to complain to HP. However, this is just my $.02. Marty On Tue, Jun 24, 2008 at 12:50 PM, chuck brigermann co2 at lenoxlaser.com wrote: I've been following this thread from the beginning shown below. I only recently got involved with Linux as part of a work project to determine if it was a suitable replacement for Windows on some of our computers. I also decided to try it on my three home computers. After investigating a number of distributions, I decided against it because of connectivity problems with our network, and at home I had a lot of trouble using a dialup modem. While reading a book on current hardware, I noticed the author highly recommended Xandros. I hadn't tried it so I purchased their professional version to test. It worked wonderful. Very user friendly, which is important to desktop users without computer skills. Also, no network or modem problems. I now have Xandros on seven systems at work and all three of my home systems. This brings us to my current disappointment. First, I sent two e-mails to this forum about HP4890 support without a single response. Now I see this overall support issue is pretty widespread. Without a reasonable support structure for peripheral devices, printers included along with scanners, Linux is never going to be a mainstream OS. Some people may say that's just fine, but then this superb distribution of software is lost on a small number of people. Many of the packages that are available with Linux are far better than their Windows counterparts - and they're free. Please, please don't ask me to buy another scanner when I have a top-of-the-line HP scanner and there's no support for it. HP is one of the world leaders in scanning equipment, and this type of hardware is widespread and needs to be supported. Chuck Brigermann Original Message From: petercmx at gmail.com To: sane-devel at lists.alioth.debian.org Subject: [sane-devel] New Scanner Purchase . Date: Sat, 21 Jun 2008 14:29:33 +0700 My HP Scanjet 3970 is on its way out . I would like to replace with another HP and I have just been comparing the HP Scanjet current models (from the HP site) with what is and what is not supported in Sane. It appears that more or less everything is not supported. This I find very surprising and so I was wondering if I had missed the point somewhere?br br I would like to use either a Scanjet G4010 or a G4050 but since both are unsupported (in common with the rest of the current scanners) I am very reluctant to buy and see what happens.br br Could anyone please tell me if I have got this wrong or is there another way round this?br br br /body /html -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org
[sane-devel] Fwd: New Scanner Purchase .....
An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080625/eff8cd0b/attachment.htm
[sane-devel] Problem: X-Server crashes when using XSane
Hi, the interesting part of the log is at the end: [snapscan] sense_handler(6, 0x84ba800, 0x8265d78) [snapscan] sense_handler: sense key: 0x04, asc: 0x00, ascq: 0x00, i1: 0x00, i2: 0x4c [snapscan] sense_handler: Hardware error. (0x00, 0x4c) [snapscan] read_calibration_data: snapscan_cmd command failed: Error during devi ce I/O [snapscan] calibrate: read_calibration_data command failed: Error during device I/O [snapscan] sane_snapscan_start: calibration failed. [snapscan] release_unit [snapscan] snapscan_cmd [snapscan] sane_snapscan_cancel [snapscan] killing reader_process According to my docs the hardware error is a scan module locked error. Maybe the transportation lock is still engaged? Do you get the error only if you use the transparency adapter or also in flatbed mode? I'm not sure why the Xserver crashes when a child process is killed, but maybe the people at X.org would find the information useful. Kind regards, Oliver Am 24.06.2008 um 18:07 schrieb Christoph M. Schr?der: Sorry, now i got it. Oliver Schwartz schrieb: Hi, the interesting part is the contents of the file 'debug.log', which should be created in the directory from which you started xsane. Regards, Oliver On 24.06.2008, at 17:50, Christoph M. Schr?der wrote: Hi, thanks Oliver. This is what i'm getting showed in the terminal: $ SANE_DEBUG_SNAPSCAN=255 xsane 2debug.log User defined signal 1 $ -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org ! Oliver Schwartz Tel.: +41 / (0)44 / 461 06 29 (fest) ! ! D?ltschiweg 3 +41 / (0)76 / 566 29 72 (mobil) ! ! CH-8055 Z?richE-Mail: Oliver.Schwartz at gmx.de!
[sane-devel] Problem with libusb and 64 bits 2.6.25 kernel
Ok, then I propose to commit this patch to CVS, but I agree, libusb64 behavior is here pretty wierd... Concerning potential buffer overflow risk in this function, raised by Sam, could be possible to add a couple of lines in here, to reject too many bytes read: error = pixma_read (s-io, data, chunksize); if (error 0) return count; count += error; data += error; + chunksize = error; + if (chunksize size) +return PIXMA_EIO; size -= error; } return count; } Sam, worth a try with these lines ? (I attached the patch from CVS to this post) Nicolas So unless I'm wrong, Le lundi 23 juin 2008 ? 21:53 -0700, Dennis Lou a ?crit : Right now my build system is acting a bit screwy. I started working on another USB device and now xsane isn't working, so I think I messed something up and am not currently set up to do sane development at the moment. In any case, I took a look at the patch. Basically, it's a one-liner that changes the minimum block size from 512 to the remainder. The reason I chose a 512 byte minimum block size is that the Windows driver does it that way, so I imitated. If the patch works in 64bit libusb, it looks to me that it would likely work in 32bit as well. However, it may take me a few days to rebuild my sane development environment and confirm. My recollection of the USB spec is a bit hazy, but 64bit libusb behavior doesn't seem correct to me. -Dennis - Original Message From: Nicolas nicolas.martin at freesurf.fr To: Dennis Lou dlou99 at yahoo.com Cc: mrsam-guest at alioth.debian.org; sane-devel sane-devel at lists.alioth.debian.org Sent: Saturday, June 21, 2008 9:07:56 AM Subject: Re: [sane-devel] Problem with libusb and 64 bits 2.6.25 kernel Hi Dennis, A bug was opened a while back by Sam Varshavchik, concerning the pixma backend for Canon ImageClass MF-4270, when compiled and used on a 64 bits platform (no issue so far on 32 bits), details are given here: https://alioth.debian.org/tracker/?group_id=30186atid=410366func=detailaid=310861 We shared with Sam some info to try to locate the origin, which looked to be related to the 64 bits libusb. Sam has performed investigations since then, his conclusions spot on that 32 and 64 bits libusb behave slightly differently when reading data from USB, more precisely, the 64 bits libusb seems to expect an exact count of bytes to read (but not 32 bits libusb), and fails (timeout) if such count is not satisfied. Sam, in his last post on the bug report page, proposes a patch, which looks to me fine for both 32 and 64 bits, and impacts only the ImageClass part of the backend. Dennis, If you don't mind, could you also have a look and give a try, so that we can commit into CVS. Nicolas -- next part -- A non-text attachment was scrubbed... Name: ovfl-24-06-2008.diff Type: text/x-patch Size: 682 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080624/95c455cd/attachment.bin
[sane-devel] udev entry for hp psc 1315
Hi,
I'm using sane 1.0.19 und hplib 2.8.4 and had to add
ATTRS{idVendor}==03f0, ATTRS{idProduct}==3f11, MODE=0664,
GROUP=scanner, ENV{libsane_matched}=yes
to my udev rules to make the all-in-one scanner hp psc 1315 work.
Or should i send this info to the hplib developers?
Hope this helps anyone.
bye,
Johnny
--
http://www.johannes-schoepfer.de
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser
[sane-devel] Problem: X-Server crashes when using XSane
Hi, thanks for this information. The transportation lock of the transparency adaptor is not engaged anymore. I will also have a look at the lock of the scanner itself. But i only get this when i use the transparency adaptor. And the really weird thing is: I can scan in linart mode (but i can't use the preview mode in lineart!!!) and if i try any other mode (preview and scan) this happens. I also thought about installing windows, too, and try it there. But i don't have to much time at the moment, so i don't know when i can do this. Thank you again! Regards, Christoph Oliver Schwartz schrieb: Hi, the interesting part of the log is at the end: [snapscan] sense_handler(6, 0x84ba800, 0x8265d78) [snapscan] sense_handler: sense key: 0x04, asc: 0x00, ascq: 0x00, i1: 0x00, i2: 0x4c [snapscan] sense_handler: Hardware error. (0x00, 0x4c) [snapscan] read_calibration_data: snapscan_cmd command failed: Error during devi ce I/O [snapscan] calibrate: read_calibration_data command failed: Error during device I/O [snapscan] sane_snapscan_start: calibration failed. [snapscan] release_unit [snapscan] snapscan_cmd [snapscan] sane_snapscan_cancel [snapscan] killing reader_process According to my docs the hardware error is a scan module locked error. Maybe the transportation lock is still engaged? Do you get the error only if you use the transparency adapter or also in flatbed mode? I'm not sure why the Xserver crashes when a child process is killed, but maybe the people at X.org would find the information useful. Kind regards, Oliver Am 24.06.2008 um 18:07 schrieb Christoph M. Schr?der: Sorry, now i got it. Oliver Schwartz schrieb: Hi, the interesting part is the contents of the file 'debug.log', which should be created in the directory from which you started xsane. Regards, Oliver On 24.06.2008, at 17:50, Christoph M. Schr?der wrote: Hi, thanks Oliver. This is what i'm getting showed in the terminal: $ SANE_DEBUG_SNAPSCAN=255 xsane 2debug.log User defined signal 1 $ -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org ! Oliver Schwartz Tel.: +41 / (0)44 / 461 06 29 (fest) ! ! D?ltschiweg 3 +41 / (0)76 / 566 29 72 (mobil) ! ! CH-8055 Z?richE-Mail: Oliver.Schwartz at gmx.de! -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080624/7e324032/attachment-0001.htm
[sane-devel] Problem with libusb and 64 bits 2.6.25 kernel
Nicolas writes: Ok, then I propose to commit this patch to CVS, but I agree, libusb64 behavior is here pretty wierd... Concerning potential buffer overflow risk in this function, raised by Sam, could be possible to add a couple of lines in here, to reject too many bytes read: error = pixma_read (s-io, data, chunksize); if (error 0) return count; count += error; data += error; + chunksize = error; + if (chunksize size) +return PIXMA_EIO; size -= error; } return count; } Sam, worth a try with these lines ? (I attached the patch from CVS to this post) I don't think this is necessary any more, because with my patch this function no longer asks for more bytes than it expects. By changing the requested chunk size not to exceed the expected # of bytes, you'll no longer need to deal with this possibility. Additionally, I do agree that it's rather bizarre that my problem only happens on x86_64. On i386, the same version of libusb works perfectly. After some further pondering, it seems more likely that the difference lies deeper, in the kernel. My 64 bit motherboard, of course, has different onboard USB hardware than my 32 bit laptop, so the real answer probably lies with the driver differences in the kernel. That's probably what the real answer is, but that's mostly educational now. I've done all kinds of scans, at various resolutions, with my patch applied, and it's been flawless every time. Just one more confirmation that MF-4270 is working good. Nicolas So unless I'm wrong, Le lundi 23 juin 2008 ? 21:53 -0700, Dennis Lou a ?crit : Right now my build system is acting a bit screwy. I started working on another USB device and now xsane isn't working, so I think I messed something up and am not currently set up to do sane development at the moment. In any case, I took a look at the patch. Basically, it's a one-liner that changes the minimum block size from 512 to the remainder. The reason I chose a 512 byte minimum block size is that the Windows driver does it that way, so I imitated. If the patch works in 64bit libusb, it looks to me that it would likely work in 32bit as well. However, it may take me a few days to rebuild my sane development environment and confirm. My recollection of the USB spec is a bit hazy, but 64bit libusb behavior doesn't seem correct to me. -Dennis - Original Message From: Nicolas nicolas.martin at freesurf.fr To: Dennis Lou dlou99 at yahoo.com Cc: mrsam-guest at alioth.debian.org; sane-devel sane-devel at lists.alioth.debian.org Sent: Saturday, June 21, 2008 9:07:56 AM Subject: Re: [sane-devel] Problem with libusb and 64 bits 2.6.25 kernel Hi Dennis, A bug was opened a while back by Sam Varshavchik, concerning the pixma backend for Canon ImageClass MF-4270, when compiled and used on a 64 bits platform (no issue so far on 32 bits), details are given here: https://alioth.debian.org/tracker/?group_id=30186atid=410366func=detailaid=310861 We shared with Sam some info to try to locate the origin, which looked to be related to the 64 bits libusb. Sam has performed investigations since then, his conclusions spot on that 32 and 64 bits libusb behave slightly differently when reading data from USB, more precisely, the 64 bits libusb seems to expect an exact count of bytes to read (but not 32 bits libusb), and fails (timeout) if such count is not satisfied. Sam, in his last post on the bug report page, proposes a patch, which looks to me fine for both 32 and 64 bits, and impacts only the ImageClass part of the backend. Dennis, If you don't mind, could you also have a look and give a try, so that we can commit into CVS. Nicolas -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080624/bf3be401/attachment.pgp
[sane-devel] Problem with libusb and 64 bits 2.6.25 kernel
The way I see it, Sam's buffer overflow concern is predicated on a misbehaving device. I haven't witnessed it but it is possible given that we're reverse engineering things rather than working from a formal spec. Nicolas' buffer overflow concern is predicated on a misbehaving usb stack. It's also possible, but probably less likely than Sam's concern. Which to implement depends on how paranoid you are about the behavior of the device and libusb. -Dennis - Original Message From: Sam Varshavchik mr...@courier-mta.com To: Nicolas nicolas.martin at freesurf.fr Cc: Dennis Lou dlou99 at yahoo.com; mrsam-guest mrsam-guest at alioth.debian.org; sane-devel sane-devel at lists.alioth.debian.org Sent: Tuesday, June 24, 2008 3:21:08 PM Subject: Re: [sane-devel] Problem with libusb and 64 bits 2.6.25 kernel Nicolas writes: Ok, then I propose to commit this patch to CVS, but I agree, libusb64 behavior is here pretty wierd... Concerning potential buffer overflow risk in this function, raised by Sam, could be possible to add a couple of lines in here, to reject too many bytes read: error = pixma_read (s-io, data, chunksize); if (error 0) return count; count += error; data += error; + chunksize = error; + if (chunksize size) +return PIXMA_EIO; size -= error; } return count; } Sam, worth a try with these lines ? (I attached the patch from CVS to this post) I don't think this is necessary any more, because with my patch this function no longer asks for more bytes than it expects. By changing the requested chunk size not to exceed the expected # of bytes, you'll no longer need to deal with this possibility. Additionally, I do agree that it's rather bizarre that my problem only happens on x86_64. On i386, the same version of libusb works perfectly. After some further pondering, it seems more likely that the difference lies deeper, in the kernel. My 64 bit motherboard, of course, has different onboard USB hardware than my 32 bit laptop, so the real answer probably lies with the driver differences in the kernel. That's probably what the real answer is, but that's mostly educational now. I've done all kinds of scans, at various resolutions, with my patch applied, and it's been flawless every time. Just one more confirmation that MF-4270 is working good. Nicolas So unless I'm wrong, Le lundi 23 juin 2008 ? 21:53 -0700, Dennis Lou a ?crit : Right now my build system is acting a bit screwy. I started working on another USB device and now xsane isn't working, so I think I messed something up and am not currently set up to do sane development at the moment. In any case, I took a look at the patch. Basically, it's a one-liner that changes the minimum block size from 512 to the remainder. The reason I chose a 512 byte minimum block size is that the Windows driver does it that way, so I imitated. If the patch works in 64bit libusb, it looks to me that it would likely work in 32bit as well. However, it may take me a few days to rebuild my sane development environment and confirm. My recollection of the USB spec is a bit hazy, but 64bit libusb behavior doesn't seem correct to me. -Dennis - Original Message From: Nicolas nicolas.martin at freesurf.fr To: Dennis Lou dlou99 at yahoo.com Cc: mrsam-guest at alioth.debian.org; sane-devel sane-devel at lists.alioth.debian.org Sent: Saturday, June 21, 2008 9:07:56 AM Subject: Re: [sane-devel] Problem with libusb and 64 bits 2.6.25 kernel Hi Dennis, A bug was opened a while back by Sam Varshavchik, concerning the pixma backend for Canon ImageClass MF-4270, when compiled and used on a 64 bits platform (no issue so far on 32 bits), details are given here: https://alioth.debian.org/tracker/?group_id=30186atid=410366func=detailaid=310861 We shared with Sam some info to try to locate the origin, which looked to be related to the 64 bits libusb. Sam has performed investigations since then, his conclusions spot on that 32 and 64 bits libusb behave slightly differently when reading data from USB, more precisely, the 64 bits libusb seems to expect an exact count of bytes to read (but not 32 bits libusb), and fails (timeout) if such count is not satisfied. Sam, in his last post on the bug report page, proposes a patch, which looks to me fine for both 32 and 64 bits, and impacts only the ImageClass part of the backend. Dennis, If you don't mind, could you also have a look and give a try, so that we can commit into CVS. Nicolas
[sane-devel] Problem with libusb and 64 bits 2.6.25 kernel
Thanks Sam and Dennis for these explanations, I think also that buffer overflow risk is now very unlikely to happen: - The read function now requests the exact count of bytes to read from usb, which secures against device misbehaving - A failing usb stack that would return more bytes than expected is improbable. So not worth adding special code in this function, we stay then with Sam's patch, and I'll commit it into CVS. Nicolas Dennis Lou wrote: The way I see it, Sam's buffer overflow concern is predicated on a misbehaving device. I haven't witnessed it but it is possible given that we're reverse engineering things rather than working from a formal spec. Nicolas' buffer overflow concern is predicated on a misbehaving usb stack. It's also possible, but probably less likely than Sam's concern. Which to implement depends on how paranoid you are about the behavior of the device and libusb. -Dennis -- View this message in context: http://www.nabble.com/Problem-with-libusb-and-64-bits-2.6.25-kernel-tp17478721p18108619.html Sent from the SANE - Dev mailing list archive at Nabble.com.
[sane-devel] [GT68xx] Plustek Optic Slim 2400 Plus [ID 07b3:0454] works and supported?? Please help and check :D
Hi, this is my try with *Plustek Optic Slim 2400 PLUS (+)* lsusb, sane-find-scanner, debug and test.png in attached file :) My try: copy firmware to /usr/share/sane/gt68xx/cis3r5b1.fw file /etc/hotplug/usb/libsane.usermap add # Plustek OpticSlim 2400 Plus libusbscanner 0x0003 0x07b3 0x0454 0x 0x 0x00 0x00 0x00 0x00 0x00 0x00 0x file /etc/sane.d/gt68xx.conf add # Autodetect Plustek OpticSlim 2400 plus usb 0x07b3 0x0454 firmware /usr/share/sane/gt68xx/cis3r5b1.fw vendor Plustek model OpticSlim 2400 Plus override plustek-opticslim-2400 scanner works, scanimage --mode Color -l 10 -t 10 -x 10 -y 10 test.png output image attached, at the beginnig of scan, scanner is callibrating (?) about 18-20sec (scanner is blinking - is this normal? at win scans scans start imediatelly), and go scanning, warning? - [gt68xx] gt68xx_afe_cis_auto: setting exposure reached limit output file is ok. color/gray/lineart works, Can anyone check attached debug file if every thing is correct? Regards LLG -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080625/2f7cb996/attachment-0001.htm -- next part -- A non-text attachment was scrubbed... Name: POS2400Plus.tgz Type: application/x-gzip Size: 50398 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080625/2f7cb996/attachment-0001.bin
[sane-devel] fujitsu production scanner documentation
I'm hoping to find documentation that would enable me to expand the sane-fujitsu driver to control the imprinter and double-feed and misfeed handling on the current Fujitsu production scanner (fi-4860, I think). The TWAIN driver and ScanDall21 application offer this control, but the current SANE driver does not appear to provide this. Does anyone on this list have access to the necessary documentation? Thanks in advance. Mitch Trachtenberg -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080625/9a60c65e/attachment.htm
[sane-devel] fujitsu production scanner documentation
2008/6/25 Mitch Trachtenberg mjtrac at gmail.com: I'm hoping to find documentation that would enable me to expand the sane-fujitsu driver to control the imprinter and double-feed and misfeed handling on the current Fujitsu production scanner (fi-4860, I think). The TWAIN driver and ScanDall21 application offer this control, but the current SANE driver does not appear to provide this. Does anyone on this list have access to the necessary documentation? i have already replied to mitch privately, so this mail is for the benefit of those reading/searching the mailing list. As of version 65, sane-fujitsu features full endorser support, and most double feed controls have been exposed for awhile, except the control over the 'continue' option, which wont be hard to add if someone needs it. allan -- The truth is an offense, but not a sin
[sane-devel] fujitsu production scanner documentation
On Wed, Jun 25, 2008 at 11:46 AM, m. allan noah kitno455 at gmail.com wrote: 2008/6/25 Mitch Trachtenberg mjtrac at gmail.com: I'm hoping to find documentation that would enable me to expand the sane-fujitsu driver to control the imprinter and double-feed and misfeed handling on the current Fujitsu production scanner (fi-4860, I think). The TWAIN driver and ScanDall21 application offer this control, but the current SANE driver does not appear to provide this. Does anyone on this list have access to the necessary documentation? i have already replied to mitch privately, so this mail is for the benefit of those reading/searching the mailing list. As of version 65, sane-fujitsu features full endorser support, and most double feed controls have been exposed for awhile, except the control over the 'continue' option, which wont be hard to add if someone needs it. and i should have included that the endorser support was funded by: O A S Oilfield Accounting Service Ltd 1500, 840 - 7th Avenue S.W. Calgary, Alberta T2P 3G2 Canada 1-403-263-2600 www.oas.ca allan -- The truth is an offense, but not a sin
[sane-devel] Problem: X-Server crashes when using XSane
Hi everyone, today i had the chance to try if i get my scanner working and it worked. I thinks there is some hardwareproblem. nothing really was locked, but it kind of hung. So i tried some things with the lock screw and then it worked again. then it didn't work again and so on. But if it does not work, now i know what to do. And if i have the time again, i will try to open the transparency adaptor and look where it is hanging. So thanks a lot everyone, especially Oliver! Regards, Christoph PS: But i'm still wondering why it always worked in linart-scan mode?! Oliver Schwartz schrieb: Hi, the interesting part of the log is at the end: [snapscan] sense_handler(6, 0x84ba800, 0x8265d78) [snapscan] sense_handler: sense key: 0x04, asc: 0x00, ascq: 0x00, i1: 0x00, i2: 0x4c [snapscan] sense_handler: Hardware error. (0x00, 0x4c) [snapscan] read_calibration_data: snapscan_cmd command failed: Error during devi ce I/O [snapscan] calibrate: read_calibration_data command failed: Error during device I/O [snapscan] sane_snapscan_start: calibration failed. [snapscan] release_unit [snapscan] snapscan_cmd [snapscan] sane_snapscan_cancel [snapscan] killing reader_process According to my docs the hardware error is a scan module locked error. Maybe the transportation lock is still engaged? Do you get the error only if you use the transparency adapter or also in flatbed mode? I'm not sure why the Xserver crashes when a child process is killed, but maybe the people at X.org would find the information useful. Kind regards, Oliver Am 24.06.2008 um 18:07 schrieb Christoph M. Schr?der: Sorry, now i got it. Oliver Schwartz schrieb: Hi, the interesting part is the contents of the file 'debug.log', which should be created in the directory from which you started xsane. Regards, Oliver On 24.06.2008, at 17:50, Christoph M. Schr?der wrote: Hi, thanks Oliver. This is what i'm getting showed in the terminal: $ SANE_DEBUG_SNAPSCAN=255 xsane 2debug.log User defined signal 1 $ -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org ! Oliver Schwartz Tel.: +41 / (0)44 / 461 06 29 (fest) ! ! D?ltschiweg 3 +41 / (0)76 / 566 29 72 (mobil) ! ! CH-8055 Z?richE-Mail: Oliver.Schwartz at gmx.de!
[sane-devel] [RFC][PATCH] sanei configuration framework extension
Le Monday 23 June 2008 22:06:30 m. allan noah, vous avez ?crit?: On Mon, Jun 23, 2008 at 3:36 PM, stef stef.dev at free.fr wrote: Le Thursday 19 June 2008 15:36:59 m. allan noah, vous avez ?crit : pretty good, but i have two comments: 1. i think calling the struct SANE_Config instead of something with sanei in it, makes it look too much like something that should be in the SANE standard, instead of the internal-use function that it is. 2. some backends seem to have dozens of options, that struct is going to become quite large if it is extending to hold everything. does it instead make more sense for the callback to be run for each line extracted from the file, with a flag indicating that it was an option instead of an attach line? allan Hello, here's a new take at config option parsing. The struct is now called SANEI_Config, and holds an array of SANE_Option_Descriptor and an array of placeholder for the values of the options. brilliant. enables us to reuse lots of code, and keep a familiar interface. bravo. To parse options, a backend first creates a list of the options it wants using SANE_Option_Descriptor. great. Then it calls sanei_configure_initialize() which creates the placeholders. When the SANEI_Config is ready, the backend calls sanei_configure_attach() which opens the configuration, parse it according to the given descriptors. Whenever a line no recognized as an option is met, the sanei_configure_attach() calls the backend provided (*attach)(SANEI_Config *, char *devname) attach function. This backend specific function calls the usb/scsi/parport attach functions allready provided by sanei library. As a parameter it has the currently parsed options in the config struct and so may use them during the attach. A sanei_configure_get_value() helper is given to access the values of the options. Once parsing is done, there is a sanei_configure_dispose() function to release allocated ressources. i would rather that the backend provided the placeholder memory if possible, for two reasons: 1. to keep all the memory allocations in one place, 2. so that the placeholders can be pre-loaded with default values by the backend. By doing this way, configuration is parsed only with the options the backend needs. The existing sanei_check_value() may be reused to check if constraints are respected. Only a couple options that need a complex syntax couldn't be handled right now (such as 'calibrate /path/name port' from canon_pp) but could be handled by a SANE_TYPE_STRING_LIST to be created. The appended patch currently only manage SANE_TYPE_STRING options and as been tested with a modified rts8891 backend. this sounds quite good- thank you very much for taking on the task! allan -- The truth is an offense, but not a sin Hello, here's the patch modified like you suggest. Now both descriptors and placeholders are given by the backend. There is no need for a free'ing function anymore. Regards, Stef -- next part -- A non-text attachment was scrubbed... Name: proposal.patch.gz Type: application/x-gzip Size: 4750 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080625/411eb2c4/attachment.bin
[sane-devel] problems with genesys and MD6228
Hello, I have compared the log you sent with one done with my scanner, and both are similar. So there no sign of hardware differences. I am searching in these logs and comparing with backend's log running at 100 dpi to find if there is something different that could lead to the problem you have. Regards, Stef
[sane-devel] Problem with libusb and 64 bits 2.6.25 kernel
Dennis Lou writes: The way I see it, Sam's buffer overflow concern is predicated on a misbehaving device. I haven't witnessed it but it is possible given that we're reverse engineering things rather than working from a formal spec. Nicolas' buffer overflow concern is predicated on a misbehaving usb stack. It's also possible, but probably less likely than Sam's concern. Which to implement depends on how paranoid you are about the behavior of the device and libusb. Clarification: my patch is needed to fix the following bug, referenced earlier in the thread: Hi Dennis, A bug was opened a while back by Sam Varshavchik, concerning the pixma backend for Canon ImageClass MF-4270, when compiled and used on a 64 bits platform (no issue so far on 32 bits), details are given here: https://alioth.debian.org/tracker/?group_id=30186atid=410366func=detailaid=310861 The original code issues a read request to libusb for more bytes than actually expected, and, apparently, on some hardware that causes a USB timeout, with Various Bad Things?, as I described in the bug. Besides a single scan now taking ~30 minutes, the resulting pnm is corrupted. By changing the code not to ask to read more than what's expected, that fixes both the original bug, and the overflow problem. -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080625/f781e6d1/attachment.pgp
[sane-devel] [GT68xx] Plustek Optic Slim 2400 Plus [ID 07b3:0454] works and supported?? Please help and check :D
Hi, this is my try with *Plustek Optic Slim 2400 PLUS (+)* lsusb, sane-find-scanner,full debug in attached files :) My try: copy firmware to /usr/share/sane/gt68xx/cis3r5b1 (md5sum d5984f6a2c984af60c88e9f8c84ba195) file /etc/hotplug/usb/libsane.usermap add # Plustek OpticSlim 2400 Plus libusbscanner 0x0003 0x07b3 0x0454 0x 0x 0x00 0x00 0x00 0x00 0x00 0x00 0x file /etc/sane.d/gt68xx.conf add # Autodetect Plustek OpticSlim 2400 plus usb 0x07b3 0x0454 firmware /usr/share/sane/gt68xx/cis3r5b1.fw vendor Plustek model OpticSlim 2400 Plus override plustek-opticslim-2400 scanner works, scanimage --mode Color -l 10 -t 10 -x 10 -y 10 test.png output image is ok XSANE works too, at the beginnig of scan, scanner is callibrating (?) about 18-20sec (scanner is blinking - is this normal? at win scans scans start imediatelly), and go scanning, warning? - [gt68xx] gt68xx_afe_cis_auto: setting exposure reached limit output file is ok. color/gray/lineart works, Can anyone check attached debug file if every thing is correct and are there any differences to Optic Slim 2400? Regards LLG -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080626/f3583889/attachment-0001.htm -- next part -- A non-text attachment was scrubbed... Name: POS2400Plus-full-debug.tgz Type: application/x-gzip Size: 18327 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080626/f3583889/attachment-0003.bin -- next part -- A non-text attachment was scrubbed... Name: POS2400PLUS-lsusb.tgz Type: application/x-gzip Size: 715 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080626/f3583889/attachment-0004.bin -- next part -- A non-text attachment was scrubbed... Name: POS2400PLUS-sane-find-scanner.tgz Type: application/x-gzip Size: 805 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080626/f3583889/attachment-0005.bin
[sane-devel] Problem with libusb and 64 bits 2.6.25 kernel
FYI, I managed to scrape together a spare machine for testing and the patch works fine here. -Dennis - Original Message From: Sam Varshavchik mr...@courier-mta.com To: Dennis Lou dlou99 at yahoo.com Cc: Nicolas nicolas.martin at freesurf.fr; mrsam-guest mrsam-guest at alioth.debian.org; sane-devel sane-devel at lists.alioth.debian.org Sent: Wednesday, June 25, 2008 3:20:22 PM Subject: Re: [sane-devel] Problem with libusb and 64 bits 2.6.25 kernel Dennis Lou writes: The way I see it, Sam's buffer overflow concern is predicated on a misbehaving device. I haven't witnessed it but it is possible given that we're reverse engineering things rather than working from a formal spec. Nicolas' buffer overflow concern is predicated on a misbehaving usb stack. It's also possible, but probably less likely than Sam's concern. Which to implement depends on how paranoid you are about the behavior of the device and libusb. Clarification: my patch is needed to fix the following bug, referenced earlier in the thread: Hi Dennis, A bug was opened a while back by Sam Varshavchik, concerning the pixma backend for Canon ImageClass MF-4270, when compiled and used on a 64 bits platform (no issue so far on 32 bits), details are given here: https://alioth.debian.org/tracker/?group_id=30186atid=410366func=detailaid=310861 The original code issues a read request to libusb for more bytes than actually expected, and, apparently, on some hardware that causes a USB timeout, with Various Bad Things?, as I described in the bug. Besides a single scan now taking ~30 minutes, the resulting pnm is corrupted. By changing the code not to ask to read more than what's expected, that fixes both the original bug, and the overflow problem.
[sane-devel] Xsane lineart bug [hpaio HPLJ3200]
tested on Gentoo 2.6.25-r5 x86_64 and Kubuntu 2.6.24-19 i686 Printer/scanner/fax: HP LaserJet 3200 USB Problem: When i'm scanning 4 pages in one time at Gray mode using X-sane multipage every thing is OK When i'm scanning 1 page in Lineart mode using X-sane multipage every thing is OK but When im scanning the same 4 pages in one time at Lineart using the same X-sane multipage there are errors: tail -f /var/log/messages |grep sane Jun 26 21:35:10 xsane: invalid read: exp=11 act=2 ReadMfpdtfBlock scan/sane/mfpdtf.c 527 Jun 26 21:37:26 xsane: invalid bufsize: size=131080 max=17408 ReadMfpdtfBlock scan/sane/mfpdtf.c 518 Jun 26 21:39:13 xsane: invalid read: exp=8 act=2 ReadMfpdtfBlock scan/sane/mfpdtf.c 527 Jun 26 21:57:59 xsane: invalid read: exp=12 act=2 ReadMfpdtfBlock scan/sane/mfpdtf.c 527 Jun 26 21:58:46 xsane: invalid read: exp=91 act=4 ReadMfpdtfBlock scan/sane/mfpdtf.c 527 Jun 26 21:59:29 xsane: invalid read: exp=88 act=4 ReadMfpdtfBlock scan/sane/mfpdtf.c 527 Jun 26 22:01:09 xsane: invalid read: exp=79 act=4 ReadMfpdtfBlock scan/sane/mfpdtf.c 527 Jun 26 22:02:37 xsane: invalid read: exp=12 act=4 ReadMfpdtfBlock scan/sane/mfpdtf.c 527 Jun 26 22:08:09 xsane: invalid read: exp=12 act=4 ReadMfpdtfBlock scan/sane/mfpdtf.c 527 Jun 26 22:08:09 xsane: invalid read: exp=12 act=4 ReadMfpdtfBlock scan/sane/mfpdtf.c 527 Jun 26 22:11:58 xsane: invalid bufsize: size=738197760 max=17408 ReadMfpdtfBlock scan/sane/mfpdtf.c 518 Jun 26 22:13:30 xsane: invalid read: exp=37 act=4 ReadMfpdtfBlock scan/sane/mfpdtf.c 527 When scanning page progress indicator don't reach the end, stops near end and then shows errors Kooka have problem with lineart scans. Does it mean the problem is in hpaio and lineart? Regards LLG
[sane-devel] How to accurately scan A4(210mmx297mm) size paper?
Hi, I want to accurately scan A4 paper(210mmx297mm),but there is not A4(210mmx297mm) item in preset area drop down box in preview window of XSane. I add 210mmx297mm item in the preset area drop down box. XSane exit and output segmentation fault in console after I select 210mmx297mm and I don't click the scan button. The 210mmx297mm item that I just added has not already in the drop down box when I run XSane at the second time. I drag and adjust the scan size to 210.31mmx297.15mm, then click the scan button and the scan is OK . I couldn't accurately drag and adjust the scan size to 210mmx297mm. How to accurately scan A4(210mmx297mm) size?The version of XSane is 0.99. Why there is not ISO standard paper size (e.g.A4(210mmx297mm)) in preset area drop down box in preview window of XSane? How to accurately scan A4(210mmx297mm)paper? Thank you. -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080627/f08dd262/attachment.htm
[sane-devel] How to accurately scan A4(210mmx297mm) size paper?
On 6/26/08, eagleskycloud eagleskycloud at gmail.com wrote: Hi, I want to accurately scan A4 paper(210mmx297mm),but there is not A4(210mmx297mm) item in preset area drop down box in preview window of XSane. my version of Xsane (.95) has DIN A3, A4, and A5, both in portrait and landscape. I add 210mmx297mm item in the preset area drop down box. XSane exit and output segmentation fault in console after I select 210mmx297mm and I don't click the scan button. chances are your backend did something weird when xsane changed the x and y params, like some math that produced a negative scan area? put in some debugging and see if you can reproduce it. The 210mmx297mm item that I just added has not already in the drop down box when I run XSane at the second time. because it crashed before saving your change. I drag and adjust the scan size to 210.31mmx297.15mm, then click the scan button and the scan is OK . I couldn't accurately drag and adjust the scan size to 210mmx297mm. How to accurately scan A4(210mmx297mm) size? it may not be possible to set those exact sizes, that depends on your backend, and the fact that the x and y values are SANE_FIX/SANE_UNFIX, things always get rounded a little bit, depending on the size of your 'quant'. but some of this might be clunkyness in the xsane interface- try using a command line front-end like scanimage, and see if you can set the sizes there. allan -- The truth is an offense, but not a sin
[sane-devel] Xsane lineart bug [hpaio HPLJ3200]
no one on this list produces drivers for this machine. they are provided by an outside project, hplip.sourceforge.net. i would suggest you contact them. allan On 6/26/08, litlle girl little.linux.girl at gmail.com wrote: tested on Gentoo 2.6.25-r5 x86_64 and Kubuntu 2.6.24-19 i686 Printer/scanner/fax: HP LaserJet 3200 USB Problem: When i'm scanning 4 pages in one time at Gray mode using X-sane multipage every thing is OK When i'm scanning 1 page in Lineart mode using X-sane multipage every thing is OK but When im scanning the same 4 pages in one time at Lineart using the same X-sane multipage there are errors: tail -f /var/log/messages |grep sane Jun 26 21:35:10 xsane: invalid read: exp=11 act=2 ReadMfpdtfBlock scan/sane/mfpdtf.c 527 Jun 26 21:37:26 xsane: invalid bufsize: size=131080 max=17408 ReadMfpdtfBlock scan/sane/mfpdtf.c 518 Jun 26 21:39:13 xsane: invalid read: exp=8 act=2 ReadMfpdtfBlock scan/sane/mfpdtf.c 527 Jun 26 21:57:59 xsane: invalid read: exp=12 act=2 ReadMfpdtfBlock scan/sane/mfpdtf.c 527 Jun 26 21:58:46 xsane: invalid read: exp=91 act=4 ReadMfpdtfBlock scan/sane/mfpdtf.c 527 Jun 26 21:59:29 xsane: invalid read: exp=88 act=4 ReadMfpdtfBlock scan/sane/mfpdtf.c 527 Jun 26 22:01:09 xsane: invalid read: exp=79 act=4 ReadMfpdtfBlock scan/sane/mfpdtf.c 527 Jun 26 22:02:37 xsane: invalid read: exp=12 act=4 ReadMfpdtfBlock scan/sane/mfpdtf.c 527 Jun 26 22:08:09 xsane: invalid read: exp=12 act=4 ReadMfpdtfBlock scan/sane/mfpdtf.c 527 Jun 26 22:08:09 xsane: invalid read: exp=12 act=4 ReadMfpdtfBlock scan/sane/mfpdtf.c 527 Jun 26 22:11:58 xsane: invalid bufsize: size=738197760 max=17408 ReadMfpdtfBlock scan/sane/mfpdtf.c 518 Jun 26 22:13:30 xsane: invalid read: exp=37 act=4 ReadMfpdtfBlock scan/sane/mfpdtf.c 527 When scanning page progress indicator don't reach the end, stops near end and then shows errors Kooka have problem with lineart scans. Does it mean the problem is in hpaio and lineart? Regards LLG -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin
[sane-devel] How to accurately scan A4(210mmx297mm) size paper?
Yes my XSane alse has DIN A3 , DIN A4 and so on,and both in portrait and landscape. But is DIN A3 same to A3? Is DIN A4 same to A4?Is DIN A5 same to A5? DIN is standard of Germany.Is the size of DIN A3 is 297mm x 420mm? Is the size of DIN A4 is 210mm x 297mm? 2008/6/27 m. allan noah kitno455 at gmail.com: On 6/26/08, eagleskycloud eagleskycloud at gmail.com wrote: Hi, I want to accurately scan A4 paper(210mmx297mm),but there is not A4(210mmx297mm) item in preset area drop down box in preview window of XSane. my version of Xsane (.95) has DIN A3, A4, and A5, both in portrait and landscape. -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080627/39ee6bb4/attachment.htm
[sane-devel] How to accurately scan A4(210mmx297mm) size paper?
DIN is the German standards body that actually 'invented' the A, B and C paper standards in 1922, but ISO copied them. DIN A4 is thus exactly the same as ISO A4, DIN A3 is the same as ISO A3, etc. I do wonder why XSane uses DIN is the name as it might confuse a few people and doesn't add anything. Might be that a person from Germany made that bit of the interface, whenever I'm there the word DIN is still added on most packs of paper too, probably just be a little national pride at work. On 2008-06-27, at 07:26, eagleskycloud wrote: Yes my XSane alse has DIN A3 , DIN A4 and so on,and both in portrait and landscape. But is DIN A3 same to A3? Is DIN A4 same to A4? Is DIN A5 same to A5? DIN is standard of Germany.Is the size of DIN A3 is 297mm x 420mm? Is the size of DIN A4 is 210mm x 297mm? 2008/6/27 m. allan noah kitno455 at gmail.com: On 6/26/08, eagleskycloud eagleskycloud at gmail.com wrote: Hi, I want to accurately scan A4 paper(210mmx297mm),but there is not A4(210mmx297mm) item in preset area drop down box in preview window of XSane. my version of Xsane (.95) has DIN A3, A4, and A5, both in portrait and landscape. -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org
[sane-devel] How to accurately scan A4(210mmx297mm) size paper?
Patrick Londema patrick at evilplatypus.net writes: DIN is the German standards body that actually 'invented' the A, B and C paper standards in 1922, but ISO copied them. DIN A4 is thus exactly the same as ISO A4, DIN A3 is the same as ISO A3, etc. I do wonder why XSane uses DIN is the name as it might confuse a few people and doesn't add anything. Might be that a person from Germany made that bit of the interface, whenever I'm there the word DIN is still added on most packs of paper too, probably just be a little national pride at work. To add to the paper size confusion, the Japanese standards body (JIS) introduced JIS A, JIS B and JIS C series. While the A and C series are the same as the ISO ones, the B series is NOT. [snip] -- Olaf Meeuwissen FLOSS Engineer -- AVASYS Corporation FSF Associate Member #1962 sign up at http://member.fsf.org/
[sane-devel] How to accurately scan A4(210mmx297mm) size paper?
-Oprindelig meddelelse- Fra: sane-devel-bounces+webmaster=keenan.dk at lists.alioth.debian.org [mailto:sane-devel-bounces+webmaster=keenan.dk at lists.alioth.de bian.org] P? vegne af Patrick Londema Sendt: 27. juni 2008 10:40 Til: sane-devel at lists.alioth.debian.org Emne: Re: [sane-devel] How to accurately scan A4(210mmx297mm) size paper? DIN is the German standards body that actually 'invented' the A, B and C paper standards in 1922, but ISO copied them. DIN A4 is thus exactly the same as ISO A4, DIN A3 is the same as ISO A3, etc. I do wonder why XSane uses DIN is the name as it might confuse a few people and doesn't add anything. Might be that a person from Germany made that bit of the interface, whenever I'm there the word DIN is still added on most packs of paper too, probably just be a little national pride at work. IIRC the person who wrote XSane is indeed german (Oliver Schwartz) Regards Ren? Kjellerup -- as life grows older, I gain experience.
[sane-devel] How to accurately scan A4(210mmx297mm) size paper?
Hello all, IIRC the person who wrote XSane is indeed german (Oliver Schwartz) well, I'm german, but I didn't write XSane :-( That honour belongs to Oliver Rauch (who is also german AFAIK). Regards, Oliver
[sane-devel] How to accurately scan A4(210mmx297mm) size paper?
-Oprindelig meddelelse- Fra: Oliver Schwartz [mailto:Oliver.Schwartz at gmx.de] Sendt: 27. juni 2008 12:24 Til: Ren? Kjellerup Cc: sane-devel at lists.alioth.debian.org Emne: Re: [sane-devel] How to accurately scan A4(210mmx297mm) size paper? Hello all, IIRC the person who wrote XSane is indeed german (Oliver Schwartz) well, I'm german, but I didn't write XSane :-( That honour belongs to Oliver Rauch (who is also german AFAIK). Ah close call it was an Oliver :) And sorry for the confusion. Regards, Oliver Regards Ren? Kjellerup -- as life grows older, I gain experience.
[sane-devel] How to accurately scan A4(210mmx297mm) size paper?
Am 27.06.2008 um 07:26 schrieb eagleskycloud: But is DIN A3 same to A3? Is DIN A4 same to A4?Is DIN A5 same to A5? DIN is standard of Germany.Is the size of DIN A3 is 297mm x 420mm? Is the size of DIN A4 is 210mm x 297mm? Yes, they are basically the same. The A series was first standardised as DIN 476 in Germany in 1922, was widely accepted in other countries later and then, around the 1970s, standadised internationally as EN ISO 216. The success is based on the good geometric properties: A0 has a size of 1 m^2 and a ratio of (approximately) 2^0,5=sqrt(2) (larger to smaller side), and from there you get each smaller format [A1 from A0, A2 from A1, ...] by halving the larger one parallel to the short side, and the ratio of the sides always remains the same. However, DIN 476 demands tighter tolerances: +/- 1,0 mm (for dimensions up to 150 mm), +/- 1,5 mm (for dimensions from 150 mm to 600 mm), whereas ISO allows 1,5 mm and 2,0 mm, respectively. So some rounding is acceptable. But you are right, you should try to get the paper size as precisely as possible from the scanner. See http://en.wikipedia.org/wiki/Paper_size for details, its all well described there. HTH -M
[sane-devel] Problem with libusb and 64 bits 2.6.25 kernel
Sounds good then. Thank Denis for your feedback! Nicolas Le mercredi 25 juin 2008 ? 23:25 -0700, Dennis Lou a ?crit : FYI, I managed to scrape together a spare machine for testing and the patch works fine here. -Dennis - Original Message From: Sam Varshavchik mrsam at courier-mta.com To: Dennis Lou dlou99 at yahoo.com Cc: Nicolas nicolas.martin at freesurf.fr; mrsam-guest mrsam-guest at alioth.debian.org; sane-devel sane-devel at lists.alioth.debian.org Sent: Wednesday, June 25, 2008 3:20:22 PM Subject: Re: [sane-devel] Problem with libusb and 64 bits 2.6.25 kernel Dennis Lou writes: The way I see it, Sam's buffer overflow concern is predicated on a misbehaving device. I haven't witnessed it but it is possible given that we're reverse engineering things rather than working from a formal spec. Nicolas' buffer overflow concern is predicated on a misbehaving usb stack. It's also possible, but probably less likely than Sam's concern. Which to implement depends on how paranoid you are about the behavior of the device and libusb. Clarification: my patch is needed to fix the following bug, referenced earlier in the thread: Hi Dennis, A bug was opened a while back by Sam Varshavchik, concerning the pixma backend for Canon ImageClass MF-4270, when compiled and used on a 64 bits platform (no issue so far on 32 bits), details are given here: https://alioth.debian.org/tracker/?group_id=30186atid=410366func=detailaid=310861 The original code issues a read request to libusb for more bytes than actually expected, and, apparently, on some hardware that causes a USB timeout, with Various Bad Things?, as I described in the bug. Besides a single scan now taking ~30 minutes, the resulting pnm is corrupted. By changing the code not to ask to read more than what's expected, that fixes both the original bug, and the overflow problem.
[sane-devel] Epson cx3700 not recognized after upgrade to 1.0.19
Everything worked absolutely flawlessly under 1.0.18. After the upgrade, which according to the ChangeLog added this device (usb 0x4b8 0x818) to backend/epson_usb.c (which I thought would make everything work better), I can't get scanimage (or any other program for that matter) to see the device (even though sane-find-scanner does). If I downgrade back to 1.0.18, then everything works again. I don't know what you need to diagnose this, but let me start with: # sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. # Also you need support for SCSI Generic (sg) in your operating system. # If using Linux, try modprobe sg. found USB scanner (vendor=0x04b8 [EPSON], product=0x0818 [USB MFP]) at libusb:004:012 # 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. # scanimage -L 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). # sane-config --version 1.0.19 # sane-config --ldflags -L/usr/lib -Wl,-rpath,/usr/lib # sane-config --libs -lsane -lusb -lpthread -lm -ljpeg -ltiff -lieee1284 -lgphoto2 -lgphoto2_port -lexif -lm -lusb -ldl I did notice under 1.0.18, I got these messages in /var/log/messages: usb 4-2: usbfs: interface 1 claimed by usblp while 'scanimage' sets config #1 usb 4-2: usbfs: interface 1 claimed by usblp while 'scanimage' sets config #1 But under 1.0.19, I get this instead: usb 4-2: usbfs: interface 1 claimed by usblp while 'scanimage' sets config #1 usb 4-2: usbfs: interface 0 claimed by usbfs while 'scanimage' sets config #1 I would appreciate any help you can give me with this. Thank you in advance.
[sane-devel] How to accurately scan A4(210mmx297mm) size paper?
Keep in mind that some backend may perform adjustments on width and height values, that are imposed by the scanner. For instance, in the pixma backend, the count of pixels in width and height need to be aligned to 32 bits for some models, because this is simply imposed by the pixma protocol. The consequence is that you cannot scan at all possible width/height dimensions, but only at discrete width/height sizes. The step between 2 consecutive widths is therefore conditioned by resolution, i.e. step (in mm) = 32 x 25.4 / xdpi At 600 dpi, this is about 1.4 mm ... but more than 1 cm at 75 dpi! Nicolas Le vendredi 27 juin 2008 ? 11:05 +0800, eagleskycloud a ?crit : Hi, I want to accurately scan A4 paper(210mmx297mm),but there is not A4(210mmx297mm) item in preset area drop down box in preview window of XSane. I add 210mmx297mm item in the preset area drop down box. XSane exit and output segmentation fault in console after I select 210mmx297mm and I don't click the scan button. The 210mmx297mm item that I just added has not already in the drop down box when I run XSane at the second time. I drag and adjust the scan size to 210.31mmx297.15mm, then click the scan button and the scan is OK . I couldn't accurately drag and adjust the scan size to 210mmx297mm. How to accurately scan A4(210mmx297mm) size?The version of XSane is 0.99. Why there is not ISO standard paper size (e.g.A4(210mmx297mm)) in preset area drop down box in preview window of XSane? How to accurately scan A4(210mmx297mm)paper? Thank you. -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org
[sane-devel] Re : Re: LiDE 90 half ccd
Hello, Sorry not to answer quickly I have had lots of work. Nothing very new since months I just do some windows snoops in 1200dpi and 2400dpi translated into C with usbsnoop2libusb.pl. they are : http://ggastebois.free.fr/lide90_snoop/lide90_1200dpi_216x7.c and http://ggastebois.free.fr/lide90_snoop/lide90_2400dpi_216x7.c I don't see big differences Guillaume Gastebois schrieb: Hello, No progress on 2400dpi. DPIHW is 2400 and dpiset 600 for a 300dpi scan. Don't know where to look yet for that problem ! I'd try to get a log from a 2400dpi scan from windows and compare. about byte nibbles modifying reg_0x79 from 0x3f to 0x3e (very few contrasted image) or 0x40(black image) gives me bad images !!! What is effect of this register on clk3 ?? It's very sensible. register 0x77 to 0x79 describe a bitmask, that determines when the clk3 signal is high or low. For 0x0003f(lsb is register 0x79), this would give: time=== ! next pixel bit of 0x79! 0x78 !0x77! 0x79 0 1 2 3 4 5 6 7!0 1 2 3 4 5 6 7!0 1!0 1 2 3 4 5 6... 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 ___ ___ |___| | 0x40 is this: bit of 0x79! 0x78 !0x77! 0x79 0 1 2 3 4 5 6 7!0 1 2 3 4 5 6 7!0 1!0 1 2 3 4 5 6... 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 _ _ ___| |_| | As you can see, this gives a very short pulse, which will probably not be recognized by the ccd, while 0x3e just shortens the clock pulse at the beginning. The datasheet mentions that the scanner does not need to use the full 18 bits of the bitmask, but uses the first 6, 12 or 18 bits depending on the scanning mode. 12 seems to be correct for the mode the backend programs for cis scanners. Please try if modifying bitmask for clk4(0x7a to 0x7c iirc) shows any effects. Also, other values you may want to try on clk3: 0xff03f, 0xff801f, 0xffc00f. Another thing to try may be to send two clock pulses, for example 0x001c7. If clk3 is connected to the ccd, this may give interesting results(like, reducing the resolution by half), but for the 4-bit latch/D-FlipFlop, only the last clock pulse before the gl841 samples the data bits is relevant. I tryed lot's of differents values for clk3 (differents pulse width and positions) succesless. Only entropy program on offset files gives me sometimes malformed crosses. regards, Guillaume Regards, Pierre Regards Guillaume
[sane-devel] CIS scanners: to calibrate or not to calibrate :) this is the question (my scanner is mad and lazy :)
litlle girl wrote: Hi guyz, i recognize that win drivers dont calibrate my CIS scanner before scan. gt68xx backend is loosing about 20sec every time on calibrating! Is there any way to turn off gt68xx backend calibrating? Most stuff i scan at lineart and i don't need calibrating neither loosing about 20sec every time. Is 20sec calibrating normal ?? Or my scanner is lazy and mad ?? :) Plustek OpticSlim 2400 Plus @ Plustek OpticSlim 2400 override (vendor=0x07b3, product=0x0454 [1200dpi USB Scanner], chip=GT-6816) The windows driver probably calibrates once, when the scanner is first used, and stores the reference data somewhere (file, registry, etc.). The SANE driver should try to do the same (not registry of course, but some /var/... whatever file-system location. Yours, -- Ren? Rebe - ExactCODE GmbH - Europe, Germany, Berlin http://exactcode.de | http://t2-project.org | http://rene.rebe.name
[sane-devel] How to accurately scan A4(210mmx297mm) size paper?
Is it all about 0.02mm? When I select DIN A4 portrait in Xsane, selects seable area, Xsane gets scan area 210.00m x 296.98mm. All works ;) BTW: It is very common that paper size from laser printers is streched or bended in result of thermal printing proces. Regard LLG
[sane-devel] How to accurately scan A4(210mmx297mm) size paper?
Actually, result may depend on the scanner and backend you are using. Be careful that size in mm indicated by Xsane preview may not represent the actual scanned area. In the case of the pixma backend, due to alignment rounding, the actual scanned area is given by the pixel area size (on the left of Xsane start scan button), but not the size in cm indicated just below. Nicolas Le samedi 28 juin 2008 ? 11:09 +0200, litlle girl a ?crit : Is it all about 0.02mm? When I select DIN A4 portrait in Xsane, selects seable area, Xsane gets scan area 210.00m x 296.98mm. All works ;) BTW: It is very common that paper size from laser printers is streched or bended in result of thermal printing proces. Regard LLG
[sane-devel] CIS scanners: to calibrate or not to calibrate :) this is the question (my scanner is mad and lazy :)
The windows driver probably calibrates once, when the scanner is first used, and stores the reference data somewhere (file, registry, etc.). The SANE driver should try to do the same (not registry of course, but some /var/... whatever file-system location. Yours, -- Ren? Rebe - ExactCODE GmbH - Europe, Germany, Berlin http://exactcode.de | http://t2-project.org | http://rene.rebe.name This is very good idea! :) I think calibrate.conf is good place to put calibrate data. calibrate.conf structure: vendor, product, mode (Lineart,Gray,Color) calibrate data Maybe recalibrate option will be needed :) LLG
[sane-devel] CIS scanners: to calibrate or not to calibrate :) this is the question (my scanner is mad and lazy :)
litlle girl wrote: The windows driver probably calibrates once, when the scanner is first used, and stores the reference data somewhere (file, registry, etc.). The SANE driver should try to do the same (not registry of course, but some /var/... whatever file-system location. Yours, -- Ren? Rebe - ExactCODE GmbH - Europe, Germany, Berlin http://exactcode.de | http://t2-project.org | http://rene.rebe.name This is very good idea! :) I think calibrate.conf is good place to put calibrate data. calibrate.conf structure: vendor, product, mode (Lineart,Gray,Color) calibrate data Maybe recalibrate option will be needed :) As proecssed run with normal user's ID have to be able to write to it some Un*x a-like /var/state/sane/$backend-$model.raw file should be more suitable. But as I'm not in CPU-less scanners the backend authors will probably figure out what they like most. Yours, -- Ren? Rebe - ExactCODE GmbH - Europe, Germany, Berlin http://exactcode.de | http://t2-project.org | http://rene.rebe.name
[sane-devel] SANE -backends-1.0.19-10.fc9 and HP SJ 5590 ADF - with gscan2pdf - A4-duplex scan - paper dimensions wrong
Dear All, First, great thanks for the SANE developers for providing so extensive set of OSS for all of us! Advise is kindly searched for the following situation: On Fedora 9 environment (see Annex A), with SANE versions (see B), using HW HP ScanJet 5590 with ADF, and A4 paper sizes , the gscan2pdf v. 0.9.23 (parameters as per Annex C) strangely behaves as follows: 1. Note: gscan2pdf using SANE backend for HP LJ 5590 with duplex ADF scan needs definition, that the reverse side must be rotated 180 degrees, otherwise the scan result gives that upside down. Page sizes are defined as A4 in the GUI of gscan2pdf. 2. Page 2 (reverse side of A4 size aper original (209 mm wide, 297 mm height) scanned) starts in output image PDF result as 6 mm late (clipped from top of page 2), 12 mm shifted left on page 2 and ends about 24 mm shrinked at bottom. 3. The phenomenon accumulates in multi-page ADF feeded double-size documents, stepping up with about 12 mm on each 4. The end result is, that multi-page double-sized ADF scans get cutted from wrong places and the result is a PDF document, where the page images are combination of a cropped end-of-page parts of previous page and the current page. Due to the ADF duplex processing or reverse side, then some parts of the text are upside down. Problem solving: PS1. Modifications of the gscan2pdf parameters for aligning the image w.r.t. page borders, did not have effect. PS2. A suspicion is, that the problem is related to the scan page image paper size dimension parameters, as eg. US is using letter size and Europe A4, which differ by about one inch in height. Some of the software modules used by gscan2pdf may be using US letter sizes inadvertedly. So my question is: how you control the page size parametrization in the SANE? Thanks for advice! Rgds Ari Annex A. Fedora 9 2.6.25.6-55.fc9.i686 Annex B. xsane 0.995, gscan2pdf V. 0.9.23, sane-baxckends-1.0.19-10.fc9, sane-backends-libs-1.0.19-10.fc9 Annex C. gscan2pdf : ADF Duplex used, A4-paper size used, in duplex scans, rotate reverse side 180 degrees. -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080628/12aa20f8/attachment.htm
[sane-devel] HP 6300C scanner
Hello, I'm currently having problems using a HP 6300C scanner and the ADF. If I use scanadf, it does scan the pages I put in the ADF without problems, but it doesn't stop scanning after the ADF is empty. Is this normal? Should I tell it how many papers are in the ADF or should it detect this by the sensor? I can see an paper-sensor in the ADF, which I can push down, and it pops up again without problems. As I don't have any windows at hand just now so I'm not able to test against it. But I'll try to get my hand on one to know if windows has the same behaviour. Marc Dirix
[sane-devel] How to accurately scan A4(210mmx297mm) size paper?
Maybe beter scan bigger area and then crop/autocrop image, in the case of the pixma backend. LLG
[sane-devel] avision problem with Minolta Scan Dual III
Tommy Thomas wrote: I am having a problem getting my scanner to work - I've looked thru the archives and everything I can find says this scanner should work. I have tried with xsane and with Gimp also, but with the same basic errors. When I run scanimage -L it finds it and identifies it correctly. But then when I run scanimage it makes (good) noises and I get scanimage: open of device avision:libusb:004:012 failed: Error during device I/O. If I don't run scanimage -L but first run scanimage -T or scanimage -n, I get no sound from scanner and scanimage: open of device avision:libusb:004:013 failed: Out of memory. I installed the scanner on a Windows machine with the Minolta software and it all works fine. I appreciate any help, I feel this is something simple but I've spent a bit of time reading the man pages and other archive mail-lists and things and I'm just missing it.
[sane-devel] anyone working on Lexmark X2330 support?
On Sat, 2008-06-14 at 15:42 +0200, Gerard Klaver wrote: Let me know when you have something. Ok, the attached c file works with my scanner. I haven't tested it exhaustively yet, there are timing issues in general (grabbing the data too slowly or too quickly leads to badness and the need for resetting) and you have to edit the code to change the scan parameters, but it works for me in a few cases (colour/greyscale at 150 DPI). I'll do some more tweaking/testing, try to figure out some of the unknown bits in the protocol and the advanced stuff the Lexmark Windows app can do and make it a bit more robust with resetting the scanner to a good state in case of failure. To compile it with GCC you'll probably need to delete the first line, I've been using tcc to merge compile+run into just run. It needs libusb and libpng installed to compile/run and will write out lexmark_scanner.png to the current directory and a bunch of debugging output to stdout. Hopefully some SANE developer can help me turn it into a SANE backend. I'd also like to know if it is similar to any other scanners that are already supported and maybe an existing driver should be extended. I also wrote a short protocol document, not sure if that is useful to SANE developers or not though. -- bye, pabs http://pabs.zip.to -- next part -- A non-text attachment was scrubbed... Name: lexmark-x2330-scanner.c Type: text/x-csrc Size: 10857 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080629/0a25344a/attachment-0001.c -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080629/0a25344a/attachment-0001.pgp
[sane-devel] How to accurately scan A4(210mmx297mm) size paper?
Yep But was just warning eagleskycloud, whose concern was to get an exact sized scan area, in mm Can be possible with pixma too, but requires scanning at 600 dpi Which apparently is not possible with Canon's Win driver, but works fine (up to 4800 dpi on some pixma models) with Sane pixma backend ;-) Nicolas Le samedi 28 juin 2008 ? 22:49 +0200, litlle girl a ?crit : Maybe beter scan bigger area and then crop/autocrop image, in the case of the pixma backend. LLG
[sane-devel] CIS scanners: to calibrate or not to calibrate :) this is the question (my scanner is mad and lazy :)
2008/6/28 Rene Rebe rene at exactcode.de: litlle girl wrote: The windows driver probably calibrates once, when the scanner is first used, and stores the reference data somewhere (file, registry, etc.). The SANE driver should try to do the same (not registry of course, but some /var/... whatever file-system location. Yours, -- Ren? Rebe - ExactCODE GmbH - Europe, Germany, Berlin http://exactcode.de | http://t2-project.org | http://rene.rebe.name This is very good idea! :) I think calibrate.conf is good place to put calibrate data. calibrate.conf structure: vendor, product, mode (Lineart,Gray,Color) calibrate data Maybe recalibrate option will be needed :) As proecssed run with normal user's ID have to be able to write to it some Un*x a-like /var/state/sane/$backend-$model.raw file should be more suitable. But as I'm not in CPU-less scanners the backend authors will probably figure out what they like most. Yours, -- Ren? Rebe - ExactCODE GmbH - Europe, Germany, Berlin http://exactcode.de | http://t2-project.org | http://rene.rebe.name I've made some research, I scan 3 times at lineart, gray and color mode and grep from log last calibrated exposure_time. Lineart 1st [gt68xx] gt68xx_generic_set_exposure_time: 0x300 0x3b3 0x40a 2nd [gt68xx] gt68xx_generic_set_exposure_time: 0x301 0x300 0x3fc 3rd [gt68xx] gt68xx_generic_set_exposure_time: 0x301 0x3b3 0x29c Gray 1st [gt68xx] gt68xx_generic_set_exposure_time: 0x300 0x2c2 0x29c 2nd [gt68xx] gt68xx_generic_set_exposure_time: 0x341 0x3d2 0x29c 3rd [gt68xx] gt68xx_generic_set_exposure_time: 0x350 0x40b 0x44c Color 1st [gt68xx] gt68xx_generic_set_exposure_time: 0x33b 0x2c8 0x29c 2nd [gt68xx] gt68xx_generic_set_exposure_time: 0x300 0x2c9 0x29c 3rd [gt68xx] gt68xx_generic_set_exposure_time: 0x300 0x2c7 0x29c It doesnt make much sense :( LLG
[sane-devel] CIS scanners: to calibrate or not to calibrate :) this is the question (my scanner is mad and lazy :)
AFE settings looks more stable: grep \[gt68xx\] afe ./* ./color-1.log:[gt68xx] afe 0x0f 0x04 0x10 0x05 0x0f 0x04 ./color-2.log:[gt68xx] afe 0x0f 0x04 0x10 0x05 0x0f 0x04 ./color-3.log:[gt68xx] afe 0x0f 0x04 0x10 0x05 0x0f 0x04 ./gray-1.log:[gt68xx] afe 0x0f 0x04 0x10 0x05 0x0f 0x04 ./gray-2.log:[gt68xx] afe 0x0f 0x04 0x0f 0x04 0x0f 0x04 ./gray-3.log:[gt68xx] afe 0x0f 0x04 0x0f 0x04 0x0e 0x03 ./lineart-1.log:[gt68xx] afe 0x0f 0x04 0x0f 0x04 0x0e 0x03 ./lineart-2.log:[gt68xx] afe 0x0f 0x04 0x0f 0x04 0x0e 0x03 ./lineart-3.log:[gt68xx] afe 0x0f 0x04 0x0f 0x04 0x0f 0x04 Reg. LLG
[sane-devel] CIS scanners: to calibrate or not to calibrate :) this is the question (my scanner is mad and lazy :)
litlle girl wrote: AFE settings looks more stable: grep \[gt68xx\] afe ./* ./color-1.log:[gt68xx] afe 0x0f 0x04 0x10 0x05 0x0f 0x04 ./color-2.log:[gt68xx] afe 0x0f 0x04 0x10 0x05 0x0f 0x04 ./color-3.log:[gt68xx] afe 0x0f 0x04 0x10 0x05 0x0f 0x04 ./gray-1.log:[gt68xx] afe 0x0f 0x04 0x10 0x05 0x0f 0x04 ./gray-2.log:[gt68xx] afe 0x0f 0x04 0x0f 0x04 0x0f 0x04 ./gray-3.log:[gt68xx] afe 0x0f 0x04 0x0f 0x04 0x0e 0x03 ./lineart-1.log:[gt68xx] afe 0x0f 0x04 0x0f 0x04 0x0e 0x03 ./lineart-2.log:[gt68xx] afe 0x0f 0x04 0x0f 0x04 0x0e 0x03 ./lineart-3.log:[gt68xx] afe 0x0f 0x04 0x0f 0x04 0x0f 0x04 Aside exposure and AFE the backend probably uploads a scaling value for each image sensor element (white / dark shading etc.?) that should be pretty constant. (And no, I still have not read the genesys backend source to verify what it's doing, this is just from other educated experience.) I bet the Windows driver also does not re-calibrate every scan, at least the Mac driver for the Canon Lide 70 does only calibrate once after unpacking. Yours, -- Ren? Rebe - ExactCODE GmbH - Europe, Germany, Berlin http://exactcode.de | http://t2-project.org | http://rene.rebe.name
[sane-devel] anyone working on Lexmark X2330 support?
On Sun, 2008-06-29 at 14:33 +0800, Paul Wise wrote: On Sat, 2008-06-14 at 15:42 +0200, Gerard Klaver wrote: Let me know when you have something. Ok, the attached c file works with my scanner. I haven't tested it exhaustively yet, there are timing issues in general (grabbing the data too slowly or too quickly leads to badness and the need for resetting) and you have to edit the code to change the scan parameters, but it works for me in a few cases (colour/greyscale at 150 DPI). I'll do some more tweaking/testing, try to figure out some of the unknown bits in the protocol and the advanced stuff the Lexmark Windows app can do and make it a bit more robust with resetting the scanner to a good state in case of failure. To compile it with GCC you'll probably need to delete the first line, I've been using tcc to merge compile+run into just run. It needs libusb and libpng installed to compile/run and will write out lexmark_scanner.png to the current directory and a bunch of debugging output to stdout. Hopefully some SANE developer can help me turn it into a SANE backend. I'd also like to know if it is similar to any other scanners that are already supported and maybe an existing driver should be extended. I also wrote a short protocol document, not sure if that is useful to SANE developers or not though. Maybe using copy of the lexmark backend naming it lexmark2 or copy from logitech1 backend (see http://gkall.hobby.nl/logitech-pagescan-usb.html) to lexmark2 backend?? A quick check on your file seems that there are not many commands needed to do a scan, so pasting into a backend will be not so much work. I can take a look how i can paste it in a copy of the logitech1 backend. -- m.vr.gr. Gerard Klaver
[sane-devel] CIS scanners: to calibrate or not to calibrate :) this is the question (my scanner is mad and lazy :)
Hi, On Freitag, 27. Juni 2008, litlle girl wrote: Hi guyz, i recognize that win drivers dont calibrate my CIS scanner before scan. Most probably it will calibrate. Right after installation of the drivers, you'll be asked to insert a white calibration paper with black marks on it. Then it starts calibration and stores this data somewhere. gt68xx backend is loosing about 20sec every time on calibrating! Is there any way to turn off gt68xx backend calibrating? have a look @ the M12 entry, the flag GT68XX_FLAG_SHEET_FED should do the trick. It'll avoid calibration. The plustek-backend is able to store calibration data and to read them back before scanning. This backend (and probably most others also) needs the value from coarse calibration (the AFE stuff) and the fine calibration (for each sensor pixel). The calibration data is stored for each user in its ~/.sane directory. HTH Gerhard
[sane-devel] CIS scanners: to calibrate or not to calibrate :) this is the question (my scanner is mad and lazy :)
Rene Rebe schrieb: litlle girl wrote: AFE settings looks more stable: grep \[gt68xx\] afe ./* ./color-1.log:[gt68xx] afe 0x0f 0x04 0x10 0x05 0x0f 0x04 ./color-2.log:[gt68xx] afe 0x0f 0x04 0x10 0x05 0x0f 0x04 ./color-3.log:[gt68xx] afe 0x0f 0x04 0x10 0x05 0x0f 0x04 ./gray-1.log:[gt68xx] afe 0x0f 0x04 0x10 0x05 0x0f 0x04 ./gray-2.log:[gt68xx] afe 0x0f 0x04 0x0f 0x04 0x0f 0x04 ./gray-3.log:[gt68xx] afe 0x0f 0x04 0x0f 0x04 0x0e 0x03 ./lineart-1.log:[gt68xx] afe 0x0f 0x04 0x0f 0x04 0x0e 0x03 ./lineart-2.log:[gt68xx] afe 0x0f 0x04 0x0f 0x04 0x0e 0x03 ./lineart-3.log:[gt68xx] afe 0x0f 0x04 0x0f 0x04 0x0f 0x04 Aside exposure and AFE the backend probably uploads a scaling value for each image sensor element (white / dark shading etc.?) that should be pretty constant. (And no, I still have not read the genesys backend source to verify what it's doing, this is just from other educated experience.) I don't know what the gt68xx uses for calibration data, but the highly experimental genesys/calibration-cache code stores(in memory only) for each combination of color mode and resolution: * exposure time * AFE offset and gain * per pixel offset and gain(actually just the black/white levels, but the offset and gain are fully defined by those) I bet the Windows driver also does not re-calibrate every scan, at least the Mac driver for the Canon Lide 70 does only calibrate once after unpacking. Yours, Regards, Pierre
[sane-devel] CIS scanners: to calibrate or not to calibrate :) this is the question (my scanner is mad and lazy :)
Hi, Pierre Willenbrock wrote: Rene Rebe schrieb: litlle girl wrote: AFE settings looks more stable: grep \[gt68xx\] afe ./* ./color-1.log:[gt68xx] afe 0x0f 0x04 0x10 0x05 0x0f 0x04 ./color-2.log:[gt68xx] afe 0x0f 0x04 0x10 0x05 0x0f 0x04 ./color-3.log:[gt68xx] afe 0x0f 0x04 0x10 0x05 0x0f 0x04 ./gray-1.log:[gt68xx] afe 0x0f 0x04 0x10 0x05 0x0f 0x04 ./gray-2.log:[gt68xx] afe 0x0f 0x04 0x0f 0x04 0x0f 0x04 ./gray-3.log:[gt68xx] afe 0x0f 0x04 0x0f 0x04 0x0e 0x03 ./lineart-1.log:[gt68xx] afe 0x0f 0x04 0x0f 0x04 0x0e 0x03 ./lineart-2.log:[gt68xx] afe 0x0f 0x04 0x0f 0x04 0x0e 0x03 ./lineart-3.log:[gt68xx] afe 0x0f 0x04 0x0f 0x04 0x0f 0x04 Aside exposure and AFE the backend probably uploads a scaling value for each image sensor element (white / dark shading etc.?) that should be pretty constant. (And no, I still have not read the genesys backend source to verify what it's doing, this is just from other educated experience.) I don't know what the gt68xx uses for calibration data, but the highly experimental genesys/calibration-cache code stores(in memory only) for each combination of color mode and resolution: * exposure time * AFE offset and gain * per pixel offset and gain(actually just the black/white levels, but the offset and gain are fully defined by those) Yeah, my point was to write them out to some permanent storage (filesystem) to cache the values and thus avoid 20-30s(++) every time a user accesses the scanner. I bet the Windows driver also does not re-calibrate every scan, at least the Mac driver for the Canon Lide 70 does only calibrate once after unpacking. Yours, Regards, Pierre -- Ren? Rebe - ExactCODE GmbH - Europe, Germany, Berlin http://exactcode.de | http://t2-project.org | http://rene.rebe.name
[sane-devel] CIS scanners: to calibrate or not to calibrate :) this is the question (my scanner is mad and lazy :)
2008/6/29 Gerhard Jaeger gerhard at gjaeger.de: Hi, On Freitag, 27. Juni 2008, litlle girl wrote: Most probably it will calibrate. Right after installation of the drivers, you'll be asked to insert a white calibration paper with black marks on it. Then it starts calibration and stores this data somewhere. Yes, i think too, that win calibrates scanner right after installation of the drivers. Hi guyz, i recognize that win drivers dont calibrate my CIS scanner before scan. I ment win dont calibrate every time :) It was difficoult to see win calibration bacause my scanner Plustek OpticSlim 2400+ dont need to insert a white calibration paper with white and black marks on it, because white and black marks are inside the scanner. gt68xx backend is loosing about 20sec every time on calibrating! Is there any way to turn off gt68xx backend calibrating? have a look @ the M12 entry, the flag GT68XX_FLAG_SHEET_FED should do the trick. It'll avoid calibration. The plustek-backend is able to store calibration data and to read them back before scanning. This backend (and probably most others also) needs the value from coarse calibration (the AFE stuff) and the fine calibration (for each sensor pixel). The calibration data is stored for each user in its ~/.sane directory. HTH Gerhard Maybe code from plustek-backend will be usable in GT68XX backend??
[sane-devel] CIS scanners: to calibrate or not to calibrate :) this is the question (my scanner is mad and lazy :)
I don't know what the gt68xx uses for calibration data, but the highly experimental genesys/calibration-cache code stores(in memory only) for each combination of color mode and resolution: * exposure time * AFE offset and gain * per pixel offset and gain(actually just the black/white levels, but the offset and gain are fully defined by those) gt68xx uses for calibration data internal white and black marks inside the scanner, below the glas (at the -y positon of scanner head) Regards LLG
[sane-devel] Crazy idea :)
Hi, flatbed scanners are scanning moving head forward, there in no reason to loose time on moving head backward useles, next page can be scanned at head backward move, and then fliped horizontally. What do you think? Regards LLG
[sane-devel] Crazy idea :)
On Sun, 2008-06-29 20:22:23 +0200, litlle girl little.linux.girl at gmail.com wrote: flatbed scanners are scanning moving head forward, there in no reason to loose time on moving head backward useles, next page can be scanned at head backward move, and then fliped horizontally. What do you think? Sure. Just send patches. (And a real name instead of litlle girl would be nice, too.) MfG, JBG -- Jan-Benedict Glaw jbglaw at lug-owl.de +49-172-7608481 Signature of:Lauf nicht vor Deinem Gl?ck davon: the second : Es k?nnte hinter Dir stehen! -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080629/d4d7f075/attachment.pgp
[sane-devel] problems with genesys and MD6228
Hello, the only difference I could spot is slightly different motor acceleration tables. The ones generated by the backend are very close to the ones in windows logs, but in case your scanner's motor is less tolerant (or failing ?), it might not like them. But I'd like to be sure at what point the trouble arise. Could you try to trigger the problem with scanning scanning script at 100 dpi and do a CTRL-C when there is a motor trouble ? The log will show us at what exact the problem is happening. Regards, Stef
[sane-devel] xsane: scanning the selected region
Hi! For a while we thought our scanner was broken: it only scanned part of the page. After taking a closer look it turned out a region was selected in the 'preview' window - however, as we typically don't have the preview window open (and just scan entire pages), we didn't notice. This was a rather puzzling experience. Perhaps it would be a nice idea to reset the selection to 'the entire page' on every startup? I'd be happy to try and prepare a patch, provided there's a good chance of inclusion :). Kind regards, Arnout
[sane-devel] Crazy idea :)
Jan-Benedict Glaw wrote: On Sun, 2008-06-29 20:22:23 +0200, litlle girl little.linux.girl at gmail.com wrote: flatbed scanners are scanning moving head forward, there in no reason to loose time on moving head backward useles, next page can be scanned at head backward move, and then fliped horizontally. What do you think? Sure. Just send patches. (And a real name instead of litlle girl would be nice, too.) Maybe she is a little girl :-)? Anyway, not all scanners allow something like this, however, you might be able to convince some CPU-less ones (Genesys, et. al). to scan backward. Yours, -- Ren? Rebe - ExactCODE GmbH - Europe, Germany, Berlin http://exactcode.de | http://t2-project.org | http://rene.rebe.name
[sane-devel] xsane: scanning the selected region
we dont produce xsane, and it's author is no longer on this list. i suggest you contact him directly. see the help menu... allan On 6/30/08, Arnout Engelen sane at bzzt.net wrote: Hi! For a while we thought our scanner was broken: it only scanned part of the page. After taking a closer look it turned out a region was selected in the 'preview' window - however, as we typically don't have the preview window open (and just scan entire pages), we didn't notice. This was a rather puzzling experience. Perhaps it would be a nice idea to reset the selection to 'the entire page' on every startup? I'd be happy to try and prepare a patch, provided there's a good chance of inclusion :). Kind regards, Arnout -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin
[sane-devel] xsane: scanning the selected region
On Mon, Jun 30, 2008 at 07:20:12AM -0400, m. allan noah wrote: we dont produce xsane, and it's author is no longer on this list. i suggest you contact him directly. see the help menu... Oh, sorry for the noise, I'll ask him to update http://www.xsane.org/xsane-mailinglist.html while i'm at it. Thanks, Arnout On 6/30/08, Arnout Engelen sane at bzzt.net wrote: Hi! For a while we thought our scanner was broken: it only scanned part of the page. After taking a closer look it turned out a region was selected in the 'preview' window - however, as we typically don't have the preview window open (and just scan entire pages), we didn't notice. This was a rather puzzling experience. Perhaps it would be a nice idea to reset the selection to 'the entire page' on every startup? I'd be happy to try and prepare a patch, provided there's a good chance of inclusion :). Kind regards, Arnout -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin
[sane-devel] [PATCH] epkowa: 16-bit on Epson 4490
Carl Troein carl.troein at ed.ac.uk writes: Hi all, Hi Carl, A while back I got an Epson Perfection 4490 Photo and found out that the 16-bit scanning didn't work, so I made a patch for the epkowa driver to fix the problem. I posted it on the avasys message board, but evidently didn't do enough research to find out that I could've posted it here. Now Johannes Meixner has alerted me to the fact that Olaf Meeuwissen is active on this list and the epkowa driver is indeed on-topic. Sorry for the late follow-up. My patch has been mentioned on this list before: http://lists.alioth.debian.org/pipermail/sane-devel/2007-September/019874.html but now I've split it into the actual 16-bit fix and some entirely optional code cosmetics. Thanks for the patches. I'll take a look and see what, if, when and in what form things will make it into the epkowa backend. Please note that from iscan's (somewhat myopic) point of view, 16-bit support is not required. All scans, except bi-level, are done with 8-bit. That means that any 16-bit support that makes it in will be pretty much untested. The reason that 16-bit scanning didn't work is that the 4490 is a 'D' level scanner, which means that it doesn't do colour correction. Instead, the driver does this (which means that 16-bit raw data from the scanner is all the more important to reduce discretization) but the driver assumes that the data is 8-bit RGB. So the first patch merely adds a 16-bit version of color_correct and a check for the depth. The modified code path is only reachable for D-level scanners and should change nothing for the 8-bit case. Hmm, I'd say all 16-bit scans should take that code path, irrespective of the scanner level (unless colour correction has been taken care of by the hardware already). The second and third patch are just minor cleanup that should have no noticable effects except on code size. The first-middle-last cases of the data download are rolled into a smaller (and IMHO more readable) loop, and a redundant memset is removed. I'm not sure about the unrolling of the loop. Apart from code size (and readability) does it improve anything else? Performance? I like to have variables initialised to a sane, well-known state before I use them, but other than that, yes, the memset() is not necessary. Hope this helps, -- Olaf Meeuwissen FLOSS Engineer -- AVASYS Corporation FSF Associate Member #1962 sign up at http://member.fsf.org/
[sane-devel] sane-net and scanimage arguments
I've got a bit of a problem with saned / sane-net and scanimage arguments. If I do this on host1 with the scanner attached: host1$ scanimage -d epson:libusb:002:008 --resolution 150 --mode Color image.pnm then it works fine. If I move to host2 and use scanimage to talk via scand with this command: host2$ scanimage -d net:host1:epson:libusb:002:008 --resolution 150 --mode Color image.pnm then scanimage errors out with: scanimage: unrecognized option `--mode' It turns out that if both --mode and --resolution are specified then scanimage barfs. I can specify --mode on its own and get a 50dpi color image, or --resolution on its own and get an 150dpi monochrome image. If I swap the arguments around then scanimage complains: scanimage: unrecognized option `--resolution' This is with the debian packaged scanutils 1.0.19-12 Nick.
[sane-devel] sane-net and scanimage arguments
Nick Andrew nick at nick-andrew.net wrote: Hi, This is with the debian packaged scanutils 1.0.19-12 Upgrade to 1.0.19-14 at least and try again. It should fix the problem. JB. -- Julien BLACHE http://www.jblache.org jb at jblache.org GPG KeyID 0xF5D65169
[sane-devel] Addressbook, and multiple email recipients
When creating an email project, in order to send to multiple email recipients does one simply separate email addresses in the box where you add the recipient (eg. jane at yahoo.com, mike at gmail.com)? Also, is there any way to import a Thunderbird addressbook into xsane for easier drop-down box type list when sending a email project to multiple recipients? Neil -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080801/033a75af/attachment.htm
[sane-devel] HP G2410 SCANNER
Le Monday 28 July 2008 19:42:50 Robert John Morton, vous avez ?crit?: Re: recent mails from: m. allan noah, amol verule, Volnei... stef, please could you help? I am using Ubuntu Linux 8.04 (Hardy Heron). I have a HP G2410 scanner. It does not work with sane at the moment. I am trying to get the information necessary to configure the sane back-end for this scanner. The scanner uses the GL646 chip set. But it is called the GL646_HP chip set. I think the HP at the end indicates that a ROM within the chip set has been programmed by Hewlett Packard specially for their scanner. It probably contains their proprietary commands and responses. I have used the HP G2410 scanner on my Windows XP computer. It works perfectly. I installed UsbSnoop on my Windows XP computer. I have used this to monitor the USB traffic between the computer and the scanner. I recorded this data for 3 different types of scan: colour, grey-scale and black and white. I recorded the data for these scans in 3 corresponding files: UsbSnoop_colour.log UsbSnoop_grey.log UsbSnoop_black_white.log I copied these 3 files to my Ubuntu Linux computer. I downloaded stef's scripts. I ran stef's script decode.sh for each of the 3 log files using the commands: ./decode.sh UsbSnoop_colour.log ./decode.sh UsbSnoop_grey.log ./decode.sh UsbSnoop_black_white.log Unfortunately, I got no results. The 3 output files UsbSnoop_colour.log.decode, UsbSnoop_grey.log.decode, UsbSnoop_black_white.log.decode were all empty. Below is the full terminal output for running the scrip for the 3 files. Does anybody have any ideas about what I have done wrong? I do not know how to proceed further at the moment. Rob Morton Terminal output... root at smoothneddy:/home/rob/Personal/computer/drivers/HP Scanner/stefs_stuff/dist# ./decode.sh UsbSnoop_black_white.log reformatting data ... compacting URBs ... sorting ... reordering in/out ... awk: program limit exceeded: maximum number of fields size=32767 FILENAME=- FNR=192 NR=192 depacking ... parsing ... awk: parse1.awk: line 105: regular expression compile failed (missing operand) * Next urb * executing motor2.awk... executing genesys_get_status.awk... awk: genesys_get_status.awk: line 77: function strtonum never defined awk: genesys_get_status.awk: line 77: function and never defined awk: genesys_get_status.awk: line 77: function and never defined awk: genesys_get_status.awk: line 77: function and never defined awk: genesys_get_status.awk: line 77: function and never defined executing testR70.awk... executing genesys_fe_write_data.awk... executing genesys_set_buffer_address.awk... executing genesys_set_buffer_address2.awk... executing genesys_read_feed_steps.awk... executing genesys_bulk_write_data.awk... awk: genesys_bulk_write_data.awk: line 49: function strtonum never defined awk: genesys_bulk_write_data.awk: line 49: function strtonum never defined executing genesys_bulk_write_next.awk... awk: genesys_bulk_write_next.awk: line 74: function strtonum never defined awk: genesys_bulk_write_next.awk: line 74: function strtonum never defined executing genesys_bulk_read_data.awk... awk: genesys_bulk_read_data.awk: line 68: function strtonum never defined awk: genesys_bulk_read_data.awk: line 68: function strtonum never defined executing genesys_bulk_read_next.awk... awk: genesys_bulk_read_next.awk: line 72: function strtonum never defined awk: genesys_bulk_read_next.awk: line 72: function strtonum never defined executing genesys_bulk_read_next2.awk... awk: genesys_bulk_read_next2.awk: line 68: function strtonum never defined awk: genesys_bulk_read_next2.awk: line 68: function strtonum never defined executing genesys_bulk_read_next3.awk... awk: genesys_bulk_read_next3.awk: line 70: function strtonum never defined awk: genesys_bulk_read_next3.awk: line 70: function strtonum never defined executing genesys_bulk_write_register2.awk... awk: genesys_bulk_write_register2.awk: line 738: function strtonum never defined awk: genesys_bulk_write_register2.awk: line 738: function strtonum never defined awk: genesys_bulk_write_register2.awk: line 738: function strtonum never defined awk: genesys_bulk_write_register2.awk: line 738: function strtonum never defined awk: genesys_bulk_write_register2.awk: line 738: function strtonum never defined executing genesys_bulk_write_register.awk... awk: genesys_bulk_write_register.awk: line 734: function strtonum never defined awk: genesys_bulk_write_register.awk: line 734: function strtonum never defined awk: genesys_bulk_write_register.awk: line 734: function strtonum never defined awk: genesys_bulk_write_register.awk: line 734: function strtonum never defined awk: genesys_bulk_write_register.awk: line 734: function strtonum never defined executing bulk_motor.awk... executing genesys_read_register.awk... awk: genesys_read_register.awk: line 734: function strtonum never defined awk:
[sane-devel] HP G2410 SCANNER
hi stef, G2410 scanner wont support by sane package which is available??is there any way to other than to make change in code of main sane package to use G2410 scanner in linux? if require to change in source code what changes require be done and how to? On Sun, Aug 3, 2008 at 2:11 AM, stef stef.dev at free.fr wrote: Le Monday 28 July 2008 19:42:50 Robert John Morton, vous avez ?crit : Re: recent mails from: m. allan noah, amol verule, Volnei... stef, please could you help? I am using Ubuntu Linux 8.04 (Hardy Heron). I have a HP G2410 scanner. It does not work with sane at the moment. I am trying to get the information necessary to configure the sane back-end for this scanner. The scanner uses the GL646 chip set. But it is called the GL646_HP chip set. I think the HP at the end indicates that a ROM within the chip set has been programmed by Hewlett Packard specially for their scanner. It probably contains their proprietary commands and responses. I have used the HP G2410 scanner on my Windows XP computer. It works perfectly. I installed UsbSnoop on my Windows XP computer. I have used this to monitor the USB traffic between the computer and the scanner. I recorded this data for 3 different types of scan: colour, grey-scale and black and white. I recorded the data for these scans in 3 corresponding files: UsbSnoop_colour.log UsbSnoop_grey.log UsbSnoop_black_white.log I copied these 3 files to my Ubuntu Linux computer. I downloaded stef's scripts. I ran stef's script decode.sh for each of the 3 log files using the commands: ./decode.sh UsbSnoop_colour.log ./decode.sh UsbSnoop_grey.log ./decode.sh UsbSnoop_black_white.log Unfortunately, I got no results. The 3 output files UsbSnoop_colour.log.decode, UsbSnoop_grey.log.decode, UsbSnoop_black_white.log.decode were all empty. Below is the full terminal output for running the scrip for the 3 files. Does anybody have any ideas about what I have done wrong? I do not know how to proceed further at the moment. Rob Morton Terminal output... root at smoothneddy:/home/rob/Personal/computer/drivers/HP Scanner/stefs_stuff/dist# ./decode.sh UsbSnoop_black_white.log reformatting data ... compacting URBs ... sorting ... reordering in/out ... awk: program limit exceeded: maximum number of fields size=32767 FILENAME=- FNR=192 NR=192 depacking ... parsing ... awk: parse1.awk: line 105: regular expression compile failed (missing operand) * Next urb * executing motor2.awk... executing genesys_get_status.awk... awk: genesys_get_status.awk: line 77: function strtonum never defined awk: genesys_get_status.awk: line 77: function and never defined awk: genesys_get_status.awk: line 77: function and never defined awk: genesys_get_status.awk: line 77: function and never defined awk: genesys_get_status.awk: line 77: function and never defined executing testR70.awk... executing genesys_fe_write_data.awk... executing genesys_set_buffer_address.awk... executing genesys_set_buffer_address2.awk... executing genesys_read_feed_steps.awk... executing genesys_bulk_write_data.awk... awk: genesys_bulk_write_data.awk: line 49: function strtonum never defined awk: genesys_bulk_write_data.awk: line 49: function strtonum never defined executing genesys_bulk_write_next.awk... awk: genesys_bulk_write_next.awk: line 74: function strtonum never defined awk: genesys_bulk_write_next.awk: line 74: function strtonum never defined executing genesys_bulk_read_data.awk... awk: genesys_bulk_read_data.awk: line 68: function strtonum never defined awk: genesys_bulk_read_data.awk: line 68: function strtonum never defined executing genesys_bulk_read_next.awk... awk: genesys_bulk_read_next.awk: line 72: function strtonum never defined awk: genesys_bulk_read_next.awk: line 72: function strtonum never defined executing genesys_bulk_read_next2.awk... awk: genesys_bulk_read_next2.awk: line 68: function strtonum never defined awk: genesys_bulk_read_next2.awk: line 68: function strtonum never defined executing genesys_bulk_read_next3.awk... awk: genesys_bulk_read_next3.awk: line 70: function strtonum never defined awk: genesys_bulk_read_next3.awk: line 70: function strtonum never defined executing genesys_bulk_write_register2.awk... awk: genesys_bulk_write_register2.awk: line 738: function strtonum never defined awk: genesys_bulk_write_register2.awk: line 738: function strtonum never defined awk: genesys_bulk_write_register2.awk: line 738: function strtonum never defined awk: genesys_bulk_write_register2.awk: line 738: function strtonum never defined awk: genesys_bulk_write_register2.awk: line 738: function strtonum never defined executing genesys_bulk_write_register.awk... awk: genesys_bulk_write_register.awk: line 734: function strtonum never defined awk: genesys_bulk_write_register.awk: line 734: function
[sane-devel] Samsung SCX-4200 Series
Hallo,
my english is not good, but I will try it:-)
I have the Samsung SCX-4200 Series multifunction printer (with scanner) and I
am using this rule for this scanner in the z60_libsane.rules file
# Samsung SCX-4200 Series
SYSFS{idVendor}==04e8, SYSFS{idProduct}==341b, MODE=0666,
GROUP=scanner, ENV{libsane_matched}=yes
S pozdravom
Ing.Slavko Fedorik
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url :
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080803/aff2e919/attachment.pgp
[sane-devel] Problem in detecting usb scanner
Hi all, I am testing once again a new linux kernel for mips architecture (both 2.6.26-rc9 and 2.6.26.1). On this machine (SGI O2) I am trying an usb scanner (epson perfection 1670) without luck, but I suspect something is missing among kernel modules. currently installed SANE is giuseppe at sgi:~$ LC_LANG=C dpkg -l \*sane\* | grep ^ii ii libsane1.0.18-5 API library for scanners ii sane 1.0.14-2 scanner graphical frontends ii sane-utils 1.0.18-5 API library for scanners -- utilities What happens: when I plug in the usb cable, I get those new lines in syslog: [17221259.26] usb 3-2: new high speed USB device using ehci_hcd and address 2 [17221259.44] usb 3-2: configuration #1 chosen from 1 choice [17221259.496000] usb 3-2: New USB device found, idVendor=04b8, idProduct=011f [17221259.532000] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [17221259.564000] usb 3-2: Product: EPSON Scanner [17221259.596000] usb 3-2: Manufacturer: EPSON then a new device appears as /dev/bus/usb/003/002. This device is correctly owned by scanner group, so udev communicate with the scanner and correctly get vendor/product giuseppe at sgi:~$ find /dev/bus/usb/ -ls 16710 drwxr-xr-x 5 root root 100 ago 3 2008 /dev/bus/usb/ 16990 drwxr-xr-x 2 root root 80 ago 3 19:15 /dev/bus/usb/003 2072600 crw-rw-r-- 1 root scanner ago 3 19:15 /dev/bus/usb/003/002 17000 crw-rw-r-- 1 root root ago 3 19:17 /dev/bus/usb/003/001 16910 drwxr-xr-x 2 root root 60 ago 3 2008 /dev/bus/usb/002 16920 crw-rw-r-- 1 root root ago 3 19:17 /dev/bus/usb/002/001 16720 drwxr-xr-x 2 root root 60 ago 3 2008 /dev/bus/usb/001 16730 crw-rw-r-- 1 root root ago 3 19:17 /dev/bus/usb/001/001 libusb might use /proc/bus/usb instead of /dev/bus/usb, so check it: giuseppe at sgi:~$ find /proc/bus/usb/ -ls 14300 drwxr-xr-x 5 root root0 ago 3 21:19 /proc/bus/usb/ 14860 dr-xr-xr-x 2 root root0 ago 3 21:19 /proc/bus/usb/003 2071660 -rw-r--r-- 1 root root 57 ago 3 19:15 /proc/bus/usb/003/002 14900 -rw-r--r-- 1 root root 43 ago 3 21:19 /proc/bus/usb/003/001 14740 dr-xr-xr-x 2 root root0 ago 3 21:19 /proc/bus/usb/002 14820 -rw-r--r-- 1 root root 43 ago 3 21:19 /proc/bus/usb/002/001 14320 dr-xr-xr-x 2 root root0 ago 3 21:19 /proc/bus/usb/001 14700 -rw-r--r-- 1 root root 43 ago 3 21:19 /proc/bus/usb/001/001 14310 -r--r--r-- 1 root root0 ago 3 19:15 /proc/bus/usb/devices why /proc/bus/usb/003/002 is not owned by scanner group? sane-find-scanner doesn't find any scanner. Logging sanei_usb I see: giuseppe at sgi:~$ env SANE_DEBUG_SANEI_USB=255 sane-find-scanner [sanei_debug] Setting debug level of sanei_usb to 255. [sanei_usb] sanei_usb_init: Looking for kernel scanner devices [sanei_usb] sanei_usb_init: can't stat /dev/usb/: No such file or directory [sanei_usb] sanei_usb_init: Looking for libusb devices usb_set_debug: Setting debugging level to 255 (on) usb_os_find_busses: Found 003 usb_os_find_busses: Found 002 usb_os_find_busses: Found 001 usb_os_find_devices: Couldn't open /dev/bus/usb/003/002 usb_os_find_devices: couldn't get connect info [...] currently loaded modules are: giuseppe at sgi:~$ lsmod | egrep 'usb|hcd' ehci_hcd 64240 0 ohci_hcd 37040 0 usbcore 223696 3 ehci_hcd,ohci_hcd finally, why lsusb does not list the scanner? giuseppe at sgi:~$ lsusb Bus 003 Device 001: ID 1d6b:0001 Bus 002 Device 001: ID 1d6b:0001 Bus 001 Device 001: ID 1d6b:0001 giuseppe at sgi:~$ sudo lsusb Password: Bus 003 Device 001: ID 1d6b:0001 Bus 002 Device 001: ID 1d6b:0001 Bus 001 Device 001: ID 1d6b:0001 Many thanks to all, Giuseppe
[sane-devel] Problem in detecting usb scanner
Giuseppe, silly question: did you specify the location of the firmware (is required by the backend for the Epson Perfection 1670 as far as I know)? Regards Wolfram Heider On Sun, 03 Aug 2008 21:05:41 +0200, Giuseppe Sacco giuseppe at eppesuigoccas.homedns.org wrote: Hi all, I am testing once again a new linux kernel for mips architecture (both 2.6.26-rc9 and 2.6.26.1). On this machine (SGI O2) I am trying an usb scanner (epson perfection 1670) without luck, but I suspect something is missing among kernel modules. currently installed SANE is giuseppe at sgi:~$ LC_LANG=C dpkg -l \*sane\* | grep ^ii ii libsane1.0.18-5 API library for scanners ii sane 1.0.14-2 scanner graphical frontends ii sane-utils 1.0.18-5 API library for scanners -- utilities What happens: when I plug in the usb cable, I get those new lines in syslog: [17221259.26] usb 3-2: new high speed USB device using ehci_hcd and address 2 [17221259.44] usb 3-2: configuration #1 chosen from 1 choice [17221259.496000] usb 3-2: New USB device found, idVendor=04b8, idProduct=011f [17221259.532000] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [17221259.564000] usb 3-2: Product: EPSON Scanner [17221259.596000] usb 3-2: Manufacturer: EPSON then a new device appears as /dev/bus/usb/003/002. This device is correctly owned by scanner group, so udev communicate with the scanner and correctly get vendor/product giuseppe at sgi:~$ find /dev/bus/usb/ -ls 16710 drwxr-xr-x 5 root root 100 ago 3 2008 /dev/bus/usb/ 16990 drwxr-xr-x 2 root root 80 ago 3 19:15 /dev/bus/usb/003 2072600 crw-rw-r-- 1 root scanner ago 3 19:15 /dev/bus/usb/003/002 17000 crw-rw-r-- 1 root root ago 3 19:17 /dev/bus/usb/003/001 16910 drwxr-xr-x 2 root root 60 ago 3 2008 /dev/bus/usb/002 16920 crw-rw-r-- 1 root root ago 3 19:17 /dev/bus/usb/002/001 16720 drwxr-xr-x 2 root root 60 ago 3 2008 /dev/bus/usb/001 16730 crw-rw-r-- 1 root root ago 3 19:17 /dev/bus/usb/001/001 libusb might use /proc/bus/usb instead of /dev/bus/usb, so check it: giuseppe at sgi:~$ find /proc/bus/usb/ -ls 14300 drwxr-xr-x 5 root root0 ago 3 21:19 /proc/bus/usb/ 14860 dr-xr-xr-x 2 root root0 ago 3 21:19 /proc/bus/usb/003 2071660 -rw-r--r-- 1 root root 57 ago 3 19:15 /proc/bus/usb/003/002 14900 -rw-r--r-- 1 root root 43 ago 3 21:19 /proc/bus/usb/003/001 14740 dr-xr-xr-x 2 root root0 ago 3 21:19 /proc/bus/usb/002 14820 -rw-r--r-- 1 root root 43 ago 3 21:19 /proc/bus/usb/002/001 14320 dr-xr-xr-x 2 root root0 ago 3 21:19 /proc/bus/usb/001 14700 -rw-r--r-- 1 root root 43 ago 3 21:19 /proc/bus/usb/001/001 14310 -r--r--r-- 1 root root0 ago 3 19:15 /proc/bus/usb/devices why /proc/bus/usb/003/002 is not owned by scanner group? sane-find-scanner doesn't find any scanner. Logging sanei_usb I see: giuseppe at sgi:~$ env SANE_DEBUG_SANEI_USB=255 sane-find-scanner [sanei_debug] Setting debug level of sanei_usb to 255. [sanei_usb] sanei_usb_init: Looking for kernel scanner devices [sanei_usb] sanei_usb_init: can't stat /dev/usb/: No such file or directory [sanei_usb] sanei_usb_init: Looking for libusb devices usb_set_debug: Setting debugging level to 255 (on) usb_os_find_busses: Found 003 usb_os_find_busses: Found 002 usb_os_find_busses: Found 001 usb_os_find_devices: Couldn't open /dev/bus/usb/003/002 usb_os_find_devices: couldn't get connect info [...] currently loaded modules are: giuseppe at sgi:~$ lsmod | egrep 'usb|hcd' ehci_hcd 64240 0 ohci_hcd 37040 0 usbcore 223696 3 ehci_hcd,ohci_hcd finally, why lsusb does not list the scanner? giuseppe at sgi:~$ lsusb Bus 003 Device 001: ID 1d6b:0001 Bus 002 Device 001: ID 1d6b:0001 Bus 001 Device 001: ID 1d6b:0001 giuseppe at sgi:~$ sudo lsusb Password: Bus 003 Device 001: ID 1d6b:0001 Bus 002 Device 001: ID 1d6b:0001 Bus 001 Device 001: ID 1d6b:0001 Many thanks to all, Giuseppe
