Re: [sane-devel] improve scanbd for Debian

2014-12-10 Thread Wilhelm
Am 11.12.2014 um 07:51 schrieb Rolf Leggewie:
> Hello group,
> 
> I'm happy to manage to get scanbd into Debian and replace scanbuttond.
> The package still has many rough edges and even for me as Maintainer
> does not work perfectly.  My local setup includes a Canon LiDE 35
> connected over USB. scanbd generally works fine when called straight
> from the command line as "scanbd -f" even for an ordinary user.  Buttons
> are recognized and scripts called.

Well, I see for in syslog.log

Nov 15 19:08:43 localhost scanbd: scanbd: exec for
/usr/share/scanbd/scripts/copy.script
Nov 15 19:08:43 localhost scanbd: scanbd: execlp: No such file or directory

which meens that your script isn't found ... but the action is triggered
from the scanner (once in this log).


> 
> I recently added the upstream init script to the package (patched to
> include a call to status) and that doesn't seem to work properly.  My
> machine runs Ubuntu Trusty and sysvrc.  scanbd seems to start up fine
> from init as verified with "ps faux".
> 
> saned21838  0.0  0.0  33252  1552 ?Sl   13:35   0:00
>   \_ /usr/sbin/scanbd -c /etc/scanbd/scanbd.conf
> 
> But there is no reaction to button presses on the scanner.  I have
> uploaded one log with successful button presses when the program is
> started directly by the user and one where the program is started from
> init and no reactions occur. Hopefully someone can spot something in
> there or otherwise suggest something for triage to move this along.
> 
> I also reported this as https://bugs.launchpad.net/bugs/1401389
> 
> The attached tar-file contains the log from the console in
> scanbd.console-log and from syslog in scanbd-syslog.log
> 
> First is a startup via init (19:00:53 to 19:07:46, lines 71 to 503).
> This is followed by a call to scanbd straight from the user command line
> (19:08:04 to 19:08:56, lines 504 to 1999). The Canon device is found in
> both cases (19:07:42, line 84 and 19:08:07, line 517). A "file" button
> press is registered at 19:08:42 that triggers the copy.script (line
> 1655). Line numbers refer to the syslog since only that one has time-stamps.
> 
> Regards
> 
> Rolf
> 
> 
> 


-- 
Wilhelm
w.me...@unix.net

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org


Re: [sane-devel] sane to work with USB 3.0

2014-12-10 Thread Olaf Meeuwissen

m. allan noah writes:

> I have just pushed your patches to git. They don't seem to help with
> any scanner that I have, but I doubt they will hurt anything.

Thanks!

> It appears that we also have USB3 issues with Canon scanners as well-
> they do use clear_halt frequently, and it seems that maybe the Linux
> kernel is not passing them down to the scanner in some cases.

Do they halt/stall that frequently?  If there's no stall, clear_halt
should not be used, IIUC.  Hmm, it doesn't look like sanei_usb allows
you to find out about that ...

> allan
>
> On Wed, Dec 10, 2014 at 6:55 PM, Olaf Meeuwissen
>  wrote:
>> Hi Allan,
>>
>> m. allan noah writes:
>>
>>> Your patch makes no difference for the Fujitsu models in question.
>>> I'll commit the patch in the next couple days, after some more
>>> testing.
>>
>> Any progress on this?
>>
>>> allan
>>>
>>> On Mon, Dec 1, 2014 at 9:44 PM, m. allan noah  wrote:
 Ha! As we speak, I am digging into USB3 again, because command
 counting seems to not fix every case. I will try your patch and report
 back.

 allan

 On Mon, Dec 1, 2014 at 9:21 PM, Olaf Meeuwissen
  wrote:
> Olaf Meeuwissen writes:
>
>> m. allan noah writes:
>>
>>> I have added a USB3 port to my computer, and have spent a few days
>>> investigating this problem.
>>
>> I haven't had that kind of time, yet :-(
>
> Finally got time to do so.
> # Someone managed to sky-rocket the priority of USB3 support to the top
> # of my TODO list ;-)
>
>>> It seems to be a bug in Linux kernel related to a bookkeeping error
>>> when the USB device is closed.  [...]
>
> Based on two days of looking at USB3 behaviour with three EPSON scanners
> and three backends, that does not seem to be the whole story.
>
>>> I have committed these changes to sane-backends git repo in
>>> 7a590f362e7e93979b706dd9e6ae34584e926ec3. If users of fujitsu scanners
>>> could try it out, I would appreciate any feedback. Note that this does
>>> not fix USB3 problems in other sane backends. Until the kernel is
>>> fixed, these types of repairs will have to be made on a per-backend
>>> basis, at the discretion of the maintainer.
>
> The epson and epson2 backends have been and still are using the kind of
> command counting and making sure to send an even count of reads and
> writes you added to the fujitsu backend.  That notwithstanding, they
> suffer from USB3 I/O problems with the Perfection V700 (GT-X900) and
> ES-H300 (GT-2500).  The epkowa backend does *not* even up the reads and
> writes and unsurprisingly shows the same problems.  In addition, the
> GT-D1000 (GT-1500), a non-free plugin needing device, is also affected.
>
> Making the epkowa backend even up the reads and writes did *not* fix the
> problem.  What did fix the problem for all three scanners and all three
> backends for me was a tiny change in sanei_usb.c.  With that change, the
> evening up of reads and writes was not needed either.
>
> The sanei_usb.c code unconditionally sets the USB configuration.  This
> happens even if the device has only one.  I found that *not* setting the
> USB configuration when there is only one fixed all my USB3 problems.  My
> understanding of the USB2 and USB3 standards is that the default USB
> configuration has to be set before devices become available to libusb.
> If that understanding is correct, then there is no need to set it unless
> you need a configuration that *differs* from the current one.  With only
> one configuration to choose from, there is then no need to set it.
>
> This patch does exactly that.  It skips setting the USB configuration if
> there is only one.  It should not break USB for any of the backends and
> *may* fix USB3 for all of them.
>
> Note: it may still set the default configuration if there are multiple
>   ones to choose from.  I have no devices I can test with to see if
>   that is problematic or not.  Even so, modifying the code to only
>   set a USB configuration if it differs should be safe.
>   # Patch is in preparation.
>
> Allan, can you locally revert your fujitsu fixes and try with the patch
> I applied?  Does that fix your USB3 issues?  Do you still need to even
> up the reads and writes?
>
> Unless it breaks things for you, could you please commit my patch?
> # Even if it does not fix USB3 for you.
>
> Other people with USB3 issues are of course more than welcome to try
> this patch too!
>
>> [...]
>>
>> Hope this helps,
>> --
>> Olaf Meeuwissen, LPIC-2   FLOSS Engineer -- AVASYS CORPORATION
>> FSF Associate Member #1962   Help support software freedom
>>  http://www.fsf.org/jf?referrer=1962


-- 
Olaf Meeuwissen, LPIC-2   FLOSS Engineer -- AVA

Re: [sane-devel] Canoscan LIDE 35 not working: "open of device failed - invalid argument"

2014-12-10 Thread Rolf Leggewie
On 04.10.2014 16:23, Marc Stürmer wrote:
> Am 02.10.2014 um 20:36 schrieb Marc Stürmer:
>> I am trying to get my CanoSCAN LIDE 35 under Gentoo Linux up and
>> running, so far with no success.
>>
>> The scanner itself is working and not broken.
>>
>> Kernel is 3.14.19, sane-backends is version 1.0.24.
> 
> I did some research myself, the results are:
> 
> backends 1.0.23 does work
> backends 1.0.24 does not
> backends 1.0.25 from git does not

I have the same scanner and 1.0.23 works for me as well.  Not sure about
the other releases.


-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org


Re: [sane-devel] Canoscan LIDE 35 not working: "open of device failed - invalid argument"

2014-12-10 Thread Rolf Leggewie
On 04.10.2014 16:23, Marc Stürmer wrote:
> Am 02.10.2014 um 20:36 schrieb Marc Stürmer:
>> I am trying to get my CanoSCAN LIDE 35 under Gentoo Linux up and
>> running, so far with no success.
>>
>> The scanner itself is working and not broken.
>>
>> Kernel is 3.14.19, sane-backends is version 1.0.24.
> 
> I did some research myself, the results are:
> 
> backends 1.0.23 does work
> backends 1.0.24 does not
> backends 1.0.25 from git does not

I have the same scanner and 1.0.23 works for me as well.  Not sure about
the other releases.


-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org


[sane-devel] improve scanbd for Debian

2014-12-10 Thread Rolf Leggewie
Hello group,

I'm happy to manage to get scanbd into Debian and replace scanbuttond.
The package still has many rough edges and even for me as Maintainer
does not work perfectly.  My local setup includes a Canon LiDE 35
connected over USB. scanbd generally works fine when called straight
from the command line as "scanbd -f" even for an ordinary user.  Buttons
are recognized and scripts called.

I recently added the upstream init script to the package (patched to
include a call to status) and that doesn't seem to work properly.  My
machine runs Ubuntu Trusty and sysvrc.  scanbd seems to start up fine
from init as verified with "ps faux".

saned21838  0.0  0.0  33252  1552 ?Sl   13:35   0:00
  \_ /usr/sbin/scanbd -c /etc/scanbd/scanbd.conf

But there is no reaction to button presses on the scanner.  I have
uploaded one log with successful button presses when the program is
started directly by the user and one where the program is started from
init and no reactions occur. Hopefully someone can spot something in
there or otherwise suggest something for triage to move this along.

I also reported this as https://bugs.launchpad.net/bugs/1401389

The attached tar-file contains the log from the console in
scanbd.console-log and from syslog in scanbd-syslog.log

First is a startup via init (19:00:53 to 19:07:46, lines 71 to 503).
This is followed by a call to scanbd straight from the user command line
(19:08:04 to 19:08:56, lines 504 to 1999). The Canon device is found in
both cases (19:07:42, line 84 and 19:08:07, line 517). A "file" button
press is registered at 19:08:42 that triggers the copy.script (line
1655). Line numbers refer to the syslog since only that one has time-stamps.

Regards

Rolf


scanbd.log.tar.bz2
Description: application/bzip
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] sane to work with USB 3.0

2014-12-10 Thread m. allan noah
I have just pushed your patches to git. They don't seem to help with
any scanner that I have, but I doubt they will hurt anything. It
appears that we also have USB3 issues with Canon scanners as well-
they do use clear_halt frequently, and it seems that maybe the Linux
kernel is not passing them down to the scanner in some cases.

allan

On Wed, Dec 10, 2014 at 6:55 PM, Olaf Meeuwissen
 wrote:
> Hi Allan,
>
> m. allan noah writes:
>
>> Your patch makes no difference for the Fujitsu models in question.
>> I'll commit the patch in the next couple days, after some more
>> testing.
>
> Any progress on this?
>
>> allan
>>
>> On Mon, Dec 1, 2014 at 9:44 PM, m. allan noah  wrote:
>>> Ha! As we speak, I am digging into USB3 again, because command
>>> counting seems to not fix every case. I will try your patch and report
>>> back.
>>>
>>> allan
>>>
>>> On Mon, Dec 1, 2014 at 9:21 PM, Olaf Meeuwissen
>>>  wrote:
 Olaf Meeuwissen writes:

> m. allan noah writes:
>
>> I have added a USB3 port to my computer, and have spent a few days
>> investigating this problem.
>
> I haven't had that kind of time, yet :-(

 Finally got time to do so.
 # Someone managed to sky-rocket the priority of USB3 support to the top
 # of my TODO list ;-)

>> It seems to be a bug in Linux kernel related to a bookkeeping error
>> when the USB device is closed.  [...]

 Based on two days of looking at USB3 behaviour with three EPSON scanners
 and three backends, that does not seem to be the whole story.

>> I have committed these changes to sane-backends git repo in
>> 7a590f362e7e93979b706dd9e6ae34584e926ec3. If users of fujitsu scanners
>> could try it out, I would appreciate any feedback. Note that this does
>> not fix USB3 problems in other sane backends. Until the kernel is
>> fixed, these types of repairs will have to be made on a per-backend
>> basis, at the discretion of the maintainer.

 The epson and epson2 backends have been and still are using the kind of
 command counting and making sure to send an even count of reads and
 writes you added to the fujitsu backend.  That notwithstanding, they
 suffer from USB3 I/O problems with the Perfection V700 (GT-X900) and
 ES-H300 (GT-2500).  The epkowa backend does *not* even up the reads and
 writes and unsurprisingly shows the same problems.  In addition, the
 GT-D1000 (GT-1500), a non-free plugin needing device, is also affected.

 Making the epkowa backend even up the reads and writes did *not* fix the
 problem.  What did fix the problem for all three scanners and all three
 backends for me was a tiny change in sanei_usb.c.  With that change, the
 evening up of reads and writes was not needed either.

 The sanei_usb.c code unconditionally sets the USB configuration.  This
 happens even if the device has only one.  I found that *not* setting the
 USB configuration when there is only one fixed all my USB3 problems.  My
 understanding of the USB2 and USB3 standards is that the default USB
 configuration has to be set before devices become available to libusb.
 If that understanding is correct, then there is no need to set it unless
 you need a configuration that *differs* from the current one.  With only
 one configuration to choose from, there is then no need to set it.

 This patch does exactly that.  It skips setting the USB configuration if
 there is only one.  It should not break USB for any of the backends and
 *may* fix USB3 for all of them.

 Note: it may still set the default configuration if there are multiple
   ones to choose from.  I have no devices I can test with to see if
   that is problematic or not.  Even so, modifying the code to only
   set a USB configuration if it differs should be safe.
   # Patch is in preparation.

 Allan, can you locally revert your fujitsu fixes and try with the patch
 I applied?  Does that fix your USB3 issues?  Do you still need to even
 up the reads and writes?

 Unless it breaks things for you, could you please commit my patch?
 # Even if it does not fix USB3 for you.

 Other people with USB3 issues are of course more than welcome to try
 this patch too!

> [...]
>
> Hope this helps,
> --
> Olaf Meeuwissen, LPIC-2   FLOSS Engineer -- AVASYS CORPORATION
> FSF Associate Member #1962   Help support software freedom
>  http://www.fsf.org/jf?referrer=1962



-- 
"well, I stand up next to a mountain- and I chop it down with the edge
of my hand"

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org


Re: [sane-devel] help scanner not detected

2014-12-10 Thread m. allan noah
That scanner is not supported by the hp backend. It is probably
supported by the hplip project, which makes a separate backend for the
hp all in one machines.

allan

On Wed, Dec 10, 2014 at 8:42 PM, david beckwith  wrote:
> I am running Mepis 12 (Debian derived) with xsane 0.998-3+b1.
> My scanner is an HP Officejet 6700 All-In-One.
> The printer is connected by wireless, the scanner by usb.
> This scanner used to work, what has changed is my desktop
> hardware - but the same printer, OS, and version of xsane.
> Of course I have had to re-install my OS.
> I can't remember now what I changed to make it work the
> first time... but I have updated /etc/sane.d/hp.conf, and
> added /etc/sane.d/hp6700.conf
>
> saneimage -L shows
> "# scanimage -L
> device `v4l:/dev/video0' is a Noname UVC Camera (046d:0819) virtual device"
>
> lsusb shows:
> "# lsusb
> Bus 002 Device 002: ID 8087:8000 Intel Corp.
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 002: ID 8087:8008 Intel Corp.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 002: ID 1058:0810 Western Digital Technologies, Inc.
> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 003 Device 005: ID 046d:c52f Logitech, Inc. Wireless Mouse M305
> Bus 003 Device 004: ID 0461:4e24 Primax Electronics, Ltd
> Bus 003 Device 003: ID 046d:0819 Logitech, Inc. Webcam C210
> Bus 003 Device 006: ID 0a5c:216c Broadcom Corp.  Bus 003 Device 002: ID 0409:0059 NEC Corp. HighSpeed Hub
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub"
>
> sane-find-scanner shows:
> "# 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.
>
> found USB scanner (vendor=0x0a5c [Broadcom Corp], product=0x216c
> [BCM43142A0]) at libusb:003:006
>   # 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."
>
>
> xsane show only my webcam as a scanning device.
>
> Any assistance would be greatly appreciated.
>
> --
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
> to sane-devel-requ...@lists.alioth.debian.org



-- 
"well, I stand up next to a mountain- and I chop it down with the edge
of my hand"

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org


[sane-devel] help scanner not detected

2014-12-10 Thread david beckwith

I am running Mepis 12 (Debian derived) with xsane 0.998-3+b1.
My scanner is an HP Officejet 6700 All-In-One.
The printer is connected by wireless, the scanner by usb.
This scanner used to work, what has changed is my desktop
hardware - but the same printer, OS, and version of xsane.
Of course I have had to re-install my OS.
I can't remember now what I changed to make it work the
first time... but I have updated /etc/sane.d/hp.conf, and
added /etc/sane.d/hp6700.conf

saneimage -L shows
"# scanimage -L
device `v4l:/dev/video0' is a Noname UVC Camera (046d:0819) virtual device"

lsusb shows:
"# lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 1058:0810 Western Digital Technologies, Inc.
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 005: ID 046d:c52f Logitech, Inc. Wireless Mouse M305
Bus 003 Device 004: ID 0461:4e24 Primax Electronics, Ltd
Bus 003 Device 003: ID 046d:0819 Logitech, Inc. Webcam C210
Bus 003 Device 006: ID 0a5c:216c Broadcom Corp.   # No SCSI scanners found. If you expected something different, make 
sure that

  # you have loaded a kernel SCSI driver for your SCSI adapter.

found USB scanner (vendor=0x0a5c [Broadcom Corp], product=0x216c 
[BCM43142A0]) at libusb:003:006
  # 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."


xsane show only my webcam as a scanning device.

Any assistance would be greatly appreciated.

--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-requ...@lists.alioth.debian.org


Re: [sane-devel] sane to work with USB 3.0

2014-12-10 Thread Olaf Meeuwissen
Hi Allan,

m. allan noah writes:

> Your patch makes no difference for the Fujitsu models in question.
> I'll commit the patch in the next couple days, after some more
> testing.

Any progress on this?

> allan
>
> On Mon, Dec 1, 2014 at 9:44 PM, m. allan noah  wrote:
>> Ha! As we speak, I am digging into USB3 again, because command
>> counting seems to not fix every case. I will try your patch and report
>> back.
>>
>> allan
>>
>> On Mon, Dec 1, 2014 at 9:21 PM, Olaf Meeuwissen
>>  wrote:
>>> Olaf Meeuwissen writes:
>>>
 m. allan noah writes:

> I have added a USB3 port to my computer, and have spent a few days
> investigating this problem.

 I haven't had that kind of time, yet :-(
>>>
>>> Finally got time to do so.
>>> # Someone managed to sky-rocket the priority of USB3 support to the top
>>> # of my TODO list ;-)
>>>
> It seems to be a bug in Linux kernel related to a bookkeeping error
> when the USB device is closed.  [...]
>>>
>>> Based on two days of looking at USB3 behaviour with three EPSON scanners
>>> and three backends, that does not seem to be the whole story.
>>>
> I have committed these changes to sane-backends git repo in
> 7a590f362e7e93979b706dd9e6ae34584e926ec3. If users of fujitsu scanners
> could try it out, I would appreciate any feedback. Note that this does
> not fix USB3 problems in other sane backends. Until the kernel is
> fixed, these types of repairs will have to be made on a per-backend
> basis, at the discretion of the maintainer.
>>>
>>> The epson and epson2 backends have been and still are using the kind of
>>> command counting and making sure to send an even count of reads and
>>> writes you added to the fujitsu backend.  That notwithstanding, they
>>> suffer from USB3 I/O problems with the Perfection V700 (GT-X900) and
>>> ES-H300 (GT-2500).  The epkowa backend does *not* even up the reads and
>>> writes and unsurprisingly shows the same problems.  In addition, the
>>> GT-D1000 (GT-1500), a non-free plugin needing device, is also affected.
>>>
>>> Making the epkowa backend even up the reads and writes did *not* fix the
>>> problem.  What did fix the problem for all three scanners and all three
>>> backends for me was a tiny change in sanei_usb.c.  With that change, the
>>> evening up of reads and writes was not needed either.
>>>
>>> The sanei_usb.c code unconditionally sets the USB configuration.  This
>>> happens even if the device has only one.  I found that *not* setting the
>>> USB configuration when there is only one fixed all my USB3 problems.  My
>>> understanding of the USB2 and USB3 standards is that the default USB
>>> configuration has to be set before devices become available to libusb.
>>> If that understanding is correct, then there is no need to set it unless
>>> you need a configuration that *differs* from the current one.  With only
>>> one configuration to choose from, there is then no need to set it.
>>>
>>> This patch does exactly that.  It skips setting the USB configuration if
>>> there is only one.  It should not break USB for any of the backends and
>>> *may* fix USB3 for all of them.
>>>
>>> Note: it may still set the default configuration if there are multiple
>>>   ones to choose from.  I have no devices I can test with to see if
>>>   that is problematic or not.  Even so, modifying the code to only
>>>   set a USB configuration if it differs should be safe.
>>>   # Patch is in preparation.
>>>
>>> Allan, can you locally revert your fujitsu fixes and try with the patch
>>> I applied?  Does that fix your USB3 issues?  Do you still need to even
>>> up the reads and writes?
>>>
>>> Unless it breaks things for you, could you please commit my patch?
>>> # Even if it does not fix USB3 for you.
>>>
>>> Other people with USB3 issues are of course more than welcome to try
>>> this patch too!
>>>
 [...]

Hope this helps,
-- 
Olaf Meeuwissen, LPIC-2   FLOSS Engineer -- AVASYS CORPORATION
FSF Associate Member #1962   Help support software freedom
 http://www.fsf.org/jf?referrer=1962

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org


[sane-devel] Samsung M2070

2014-12-10 Thread Danil Smirnov
Hi there!

Are there support for subj device in the last libsane? (My hope rose after
reading that "The current development version of SANE has limited support
for some of the Xpress-type printers.
")

I've just downloaded and built last git version of libsane for Debian Weezy:



*scanimage -Vscanimage (sane-backends) 1.0.25git; backend version 1.0.25*
Then I made similar additions into config files (like this
)
but scanner still can't be found by scanimage -L. :((

Please help.

Danil
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Support of Mustek A3 2400S

2014-12-10 Thread Troels Thomsen
m. allan noah once wrote:"You might
also want to investigate Fujitsu scanners, they are pricey, but they
give me protocol documentation for most of their models, and so are
fairly easy to support"

/T




2014-12-10 21:49 GMT+01:00 Jehan Pagès :

> Hi,
>
> On Wed, Dec 10, 2014 at 8:54 PM, Bob Gustafson  wrote:
> > There is a nicer model -
> > http://www.mustek.com/products/large-a3-scanner/9-a3f2400n.html
> > In the specifications under 'System Requirements' it shows:
> >
> >   Windows 8 / 7 / Vista / XP (Service Pack 3)
> >
> >   Mac OS X 10.7~10.10
> >
> >   Linux Ubuntu12.04 kernel 3.11 32bit / Fedora 20 kernel 3.15 32bit
>
> Yes after sending this email to the Sane mailing list, I checked other
> scanners and discovered as well that some had announced Linux support,
> which is nice.
>
> Rather than the A3F2400N though, the A3 1200 HS looks interesting by
> being faster, which I prefer to having buttons on the scanner, as long
> as this does not affect the scan quality (there is also a A3 2400 HS
> in their webshop, apparently so recently released that it is not even
> in the main website, but honestly I think 1200 dpi is more than
> enough). Now they don't really give much information on how faster it
> would be (only comparison point is A3 200 dpi in 2.3 s for the HS, and
> 3 s for the N model, no info for higher resolutions).
>
> > Perhaps they are not really that serious about the Linux 32 bit?
>
> Oh I didn't realize the 32 bit part. This is indeed annoying!
> Maybe I'll send an email and ask.
>
> > In their Support Drivers Downloads they don't specify bit size for Linux
> >
> > Driver A3F2400N NA Sep 19, 2014Linux
> >
> > Technical Support is tsupp...@mustek.com
> >
> > --
> >
> > I have been looking at Mustek for awhile - more or less limited by the
> same
> > software driver issues.
>
> Do you know of other good brands which make A3 scanners? Good quality
> but reasonable price is what I am looking for.
> Thanks!
>
> Jehan
>
> > Bob G
> >
> >
> > On 12/10/2014 01:17 PM, Jehan Pagès wrote:
> >
> > Hello,
> >
> > I've been interested into a A3 scanner, found the Mustek A3 2400S on
> > Amazon (http://www.amazon.fr/Mustek-A3-2400-Scanner-Plat/dp/B00A1K9M2Q)
> > but I just can't figure out whether or not it is supported on Linux
> > (and to which level of support).
> >
> > I used the scanner Search Engine:
> > http://www.sane-project.org/cgi-bin/driver.pl?manu=mustek
> > But no model seems to be exactly named "2400S" (there are a lot of
> > 2400 CU|CS|TA (PLUS)? and so on, but no "S", and they all seem to have
> > an additional naming like BearPaw, ScanExpress, etc. but such names
> > are not used for this mustek product).
> >
> > Would anyone know if that is actually a different naming for another
> > scanner in the Sane list, or is it simply not in the list? And if it
> > is not, would anyone know if it would work anyway, has any experience
> > with it or something?
> > Also what seems to be the officiel spec:
> > http://www.mustek.com/products/large-a3-scanner/12-a3-2400s.html
> >
> > Thanks.
> >
> > Jehan
> >
> >
> >
> > --
> > sane-devel mailing list: sane-devel@lists.alioth.debian.org
> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> > Unsubscribe: Send mail with subject "unsubscribe your_password"
> >  to sane-devel-requ...@lists.alioth.debian.org
>
> --
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>  to sane-devel-requ...@lists.alioth.debian.org
>
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Support of Mustek A3 2400S

2014-12-10 Thread Jehan Pagès
Hi,

On Wed, Dec 10, 2014 at 8:54 PM, Bob Gustafson  wrote:
> There is a nicer model -
> http://www.mustek.com/products/large-a3-scanner/9-a3f2400n.html
> In the specifications under 'System Requirements' it shows:
>
>   Windows 8 / 7 / Vista / XP (Service Pack 3)
>
>   Mac OS X 10.7~10.10
>
>   Linux Ubuntu12.04 kernel 3.11 32bit / Fedora 20 kernel 3.15 32bit

Yes after sending this email to the Sane mailing list, I checked other
scanners and discovered as well that some had announced Linux support,
which is nice.

Rather than the A3F2400N though, the A3 1200 HS looks interesting by
being faster, which I prefer to having buttons on the scanner, as long
as this does not affect the scan quality (there is also a A3 2400 HS
in their webshop, apparently so recently released that it is not even
in the main website, but honestly I think 1200 dpi is more than
enough). Now they don't really give much information on how faster it
would be (only comparison point is A3 200 dpi in 2.3 s for the HS, and
3 s for the N model, no info for higher resolutions).

> Perhaps they are not really that serious about the Linux 32 bit?

Oh I didn't realize the 32 bit part. This is indeed annoying!
Maybe I'll send an email and ask.

> In their Support Drivers Downloads they don't specify bit size for Linux
>
> Driver A3F2400N NA Sep 19, 2014Linux
>
> Technical Support is tsupp...@mustek.com
>
> --
>
> I have been looking at Mustek for awhile - more or less limited by the same
> software driver issues.

Do you know of other good brands which make A3 scanners? Good quality
but reasonable price is what I am looking for.
Thanks!

Jehan

> Bob G
>
>
> On 12/10/2014 01:17 PM, Jehan Pagès wrote:
>
> Hello,
>
> I've been interested into a A3 scanner, found the Mustek A3 2400S on
> Amazon (http://www.amazon.fr/Mustek-A3-2400-Scanner-Plat/dp/B00A1K9M2Q)
> but I just can't figure out whether or not it is supported on Linux
> (and to which level of support).
>
> I used the scanner Search Engine:
> http://www.sane-project.org/cgi-bin/driver.pl?manu=mustek
> But no model seems to be exactly named "2400S" (there are a lot of
> 2400 CU|CS|TA (PLUS)? and so on, but no "S", and they all seem to have
> an additional naming like BearPaw, ScanExpress, etc. but such names
> are not used for this mustek product).
>
> Would anyone know if that is actually a different naming for another
> scanner in the Sane list, or is it simply not in the list? And if it
> is not, would anyone know if it would work anyway, has any experience
> with it or something?
> Also what seems to be the officiel spec:
> http://www.mustek.com/products/large-a3-scanner/12-a3-2400s.html
>
> Thanks.
>
> Jehan
>
>
>
> --
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>  to sane-devel-requ...@lists.alioth.debian.org

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Support of Mustek A3 2400S

2014-12-10 Thread Bob Gustafson
There is a nicer model - 
http://www.mustek.com/products/large-a3-scanner/9-a3f2400n.html

In the specifications under 'System Requirements' it shows:

  Windows 8 / 7 / Vista / XP (Service Pack 3)

  Mac OS X 10.7~10.10

  Linux Ubuntu12.04 kernel 3.11 32bit / Fedora 20 kernel 3.15 32bit

Perhaps they are not really that serious about the Linux 32 bit?

In their Support Drivers Downloads they don't specify bit size for Linux

Driver A3F2400N NA Sep 19, 2014Linux

Technical Support is tsupp...@mustek.com 

--

I have been looking at Mustek for awhile - more or less limited by the 
same software driver issues.


Bob G

On 12/10/2014 01:17 PM, Jehan Pagès wrote:

Hello,

I've been interested into a A3 scanner, found the Mustek A3 2400S on
Amazon (http://www.amazon.fr/Mustek-A3-2400-Scanner-Plat/dp/B00A1K9M2Q)
but I just can't figure out whether or not it is supported on Linux
(and to which level of support).

I used the scanner Search Engine:
http://www.sane-project.org/cgi-bin/driver.pl?manu=mustek
But no model seems to be exactly named "2400S" (there are a lot of
2400 CU|CS|TA (PLUS)? and so on, but no "S", and they all seem to have
an additional naming like BearPaw, ScanExpress, etc. but such names
are not used for this mustek product).

Would anyone know if that is actually a different naming for another
scanner in the Sane list, or is it simply not in the list? And if it
is not, would anyone know if it would work anyway, has any experience
with it or something?
Also what seems to be the officiel spec:
http://www.mustek.com/products/large-a3-scanner/12-a3-2400s.html

Thanks.

Jehan



-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

[sane-devel] Support of Mustek A3 2400S

2014-12-10 Thread Jehan Pagès
Hello,

I've been interested into a A3 scanner, found the Mustek A3 2400S on
Amazon (http://www.amazon.fr/Mustek-A3-2400-Scanner-Plat/dp/B00A1K9M2Q)
but I just can't figure out whether or not it is supported on Linux
(and to which level of support).

I used the scanner Search Engine:
http://www.sane-project.org/cgi-bin/driver.pl?manu=mustek
But no model seems to be exactly named "2400S" (there are a lot of
2400 CU|CS|TA (PLUS)? and so on, but no "S", and they all seem to have
an additional naming like BearPaw, ScanExpress, etc. but such names
are not used for this mustek product).

Would anyone know if that is actually a different naming for another
scanner in the Sane list, or is it simply not in the list? And if it
is not, would anyone know if it would work anyway, has any experience
with it or something?
Also what seems to be the officiel spec:
http://www.mustek.com/products/large-a3-scanner/12-a3-2400s.html

Thanks.

Jehan

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org