[sane-devel] 1.0.25 is out, now what?
paddy-hack at member.fsf.org
Wed Oct 28 08:44:42 UTC 2015
Johannes Meixner writes:
> On Oct 21 21:32 Olaf Meeuwissen wrote (excerpt):
>> Alessandro Zummo writes:
>>> There's probably still some bug in the usb code. I have
>>> intermittent results with some scanners on usb2
>>> and with others on usb3. switching among the two usb
>>> standards solves them all.
>> I'm curious about USB related issues that other backends
>> are facing that might be solved by switching to libusb-1
>> as the default.
> At openSUSE we use libusb-1 since openSUSE 12.2
> (i.e. we use libusb-1 since about April 2012)
> via "configure --enable-libusb_1_0".
> I am not aware of issues because of this.
Thanks for the info. So at least changing to libusb-1 is unlikely to
cause any trouble.
My original question however, was if doing so would fix any outstanding
libusb-0 issues that we may have. I could go through the open tickets
but if someone knows of any off the top of their head ...
# The Alioth tracker's advanced query functionality still has me
# completely mistified.
> Regarding USB 3, see
> It seems one needs a very current kernel for USB 3.
> For me kernel 4.1.6 did not work with sane-backends-1.0.25.
> For me kernel-vanilla-4.3.rc5 works where it seems
> the xhci USB driver is now at least somewhat fixed.
> But I needed additionally the workarounds for
> the broken xhci driver in sane-backends-1.0.25
> i.e. sane-backends-1.0.24 did not work for me
> with kernel-vanilla-4.3.rc5, see
USB 3 is known to be a bit of a "rough ride" and nobody seems to know
what the secret mix is to get things to work.
Thanks again for the feedback.
Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27
Support Free Software Support the Free Software Foundation
GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9
More information about the sane-devel