For only $16 shipped, I'm willing to call this problem
sorted. :-)
Scott Alfter
sc...@alfter.us
--
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 "unsubscrib
On 12/16/2015 9:20 PM, Stef wrote:
> On 17/12/2015 04:41, Scott Alfter wrote:
>> I then put the patch back in (or, more precisely, didn't patch it
>> out), recompiled, and tried again under the newer kernel. It seems to
>> be running about the same with the workarou
On 12/17/2015 12:35 AM, Johannes Meixner wrote:
> On Dec 16 12:45 Scott Alfter wrote (excerpt):
>> ... lsusb -t shows the following for the home system:
>>
>> [snipped]
>
> You did not tell what of those devices the scanner is.
At the time I ran it, none of them were th
pi and below.
The patch doesn't appear to be making much of a difference one way or
the other. Instead, it would appear the kernel developers may have
fixed whatever was broken with USB 3.0 support somewhere between 4.1.12
and 4.3.3.
--
Scott Alfter
sc...@alfter.us
--
sane-
t helps.
(If it makes a difference, I'm running Gentoo's latest stable kernel,
which is based on 4.1.12. Kernel versions up to 4.3.3 are available
under gentoo-sources.)
--
Scott Alfter
sc...@alfter.us
signature.asc
Description: OpenPGP digital signature
--
sane-devel mailing list:
On 12/16/2015 2:42 AM, Johannes Meixner wrote:
> On Dec 15 13:29 Scott Alfter wrote (excerpt):
>> The new motherboard supports USB 3.0 as well as 2.0
>
> Really pure traditional USB 2 hardware?
>
> In general when your scanner is connected via USB:
>
> There are curr
too Linux in a VirtualBox VM under Windows 7. I already have that box
working with an ancient LiDE 20 that Canon doesn't support under
anything newer than Windows XP and would just need to compile in the
genesys backend (the LiDE 20 uses the plustek backend).
--
Scott Alf
On 2015-12-15 14:52, John S. Weber wrote:
On Tue, Dec 15, 2015 at 2:29 PM, Scott Alfter wrote:
I've had this scanner working with prerelease code and the final
1.0.25
release for several months, but when I tried scanning something in the
other day, it refused to start up. I normall
changed since May 2013. What would explain this
breakage? Is it something that can be fixed or worked around, or should
I start looking for something else to scan photos? (I probably
should've been using gscan2pdf for documents...need to familiarize
myself with that a bit better.)
--
