http://bugzilla.opensuse.org/show_bug.cgi?id=920067 --- Comment #1 from robert spitzenpfeil --- Created attachment 624922 --> http://bugzilla.opensuse.org/attachment.cgi?id=624922&action=edit hwinfo --all -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=920067 --- Comment #3 from robert spitzenpfeil --- Created attachment 624925 --> http://bugzilla.opensuse.org/attachment.cgi?id=624925&action=edit lsusb -v -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=920067 --- Comment #5 from robert spitzenpfeil --- Created attachment 624927 --> http://bugzilla.opensuse.org/attachment.cgi?id=624927&action=edit sane-find-scanner -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=920067 --- Comment #7 from robert spitzenpfeil --- Created attachment 624929 --> http://bugzilla.opensuse.org/attachment.cgi?id=624929&action=edit "scanimage -L" hanging -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=920067 --- Comment #9 from robert spitzenpfeil --- Created attachment 624931 --> http://bugzilla.opensuse.org/attachment.cgi?id=624931&action=edit scanimage segfault -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=920067 --- Comment #11 from robert spitzenpfeil --- Created attachment 624933 --> http://bugzilla.opensuse.org/attachment.cgi?id=624933&action=edit xsane error -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=920067 --- Comment #13 from robert spitzenpfeil --- Created attachment 624935 --> http://bugzilla.opensuse.org/attachment.cgi?id=624935&action=edit xsane trace -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=920067 --- Comment #15 from robert spitzenpfeil --- Created attachment 624937 --> http://bugzilla.opensuse.org/attachment.cgi?id=624937&action=edit yast scanner setup -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=920067 --- Comment #17 from robert spitzenpfeil --- It seems that "sane-find-scanner" always works, it detects the scanner correctly. But I'm not sure if this actually needs talking to the scanner, or if this is just the same information as provided by "lsusb". Anything that actually talks to the device doesn't end well. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=920067 Martin Pluskal changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsmeix@suse.com, | |mpluskal@suse.com, | |oneukum@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=920067 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Found By|--- |Community User Resolution|--- |UPSTREAM --- Comment #20 from Johannes Meixner --- It is a known issue at SANE upstream that some/many/most? scanners do not work at USB 3 ports on some/many/most? computers. I am not at all a USB expert which means I can neither debug lower-level USB issues nor fix them. As far as I noticed on some USB3 related mail threads on the "sane-devel@lists.alioth.debian.org" mailing list, something seems to have changed how the kernel works in case of USB3 compated to how it worked with USB2. FYI, see also "USB Speed" at https://en.opensuse.org/SDB:Configuring_Scanners

From my non-expert point of view the issue is not caused by openSUSE, neither by openSUSE-specific changes of our kernel or libusb nor by openSUSE-specific changes of the sane-backends software.

Therefore the issue belongs to "upstream", either the kernel or libusb or SANE or perpaps even all of them. You can still add comments to this issue report regardless that it is closed as "upstream" - i.e. there is no need to reopen it only to provide more information. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=920067 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(oneukum@suse.com) --- Comment #22 from Johannes Meixner --- Oliver Neukum, what is the generic method to tell the kernel to make a USB3 port behave as if it was only a USB2 port? It seems something like "rmmod xhci_hcd ; modprobe ehci_hcd" does not make a hardware USB3 port behave as if it was only USB2. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=920067 --- Comment #24 from robert spitzenpfeil --- It seems a possible workaround for xhci + scanners was committed to the sane-backends repo some time ago. I've tested the plustek backend (canon scanners) on my USB 2 machine a bit, and it still scans, which is good. Tomorrow I'll try replacing the plustek backend on the USB 3 laptop and shall report my findings. Fingers crossed. If this should work, updating sane might be a quicker short-term fix for 13.x than waiting for a kernel update. Less impact, if something should go sour. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=920067 --- Comment #26 from Johannes Meixner --- I provide sane-backends version git20150108 RPMs an unstable development source only for testing, without any guarantee or warranty, and without any support in my openSUSE build service home project "home:jsmeix". The sane-backends-git20150108 sources contain in the ChangeLog file: ------------------------------------------------------------------------- 2014-12-16 m. allan noah <kitno455 at gmail dot com> * sanei/sanei_usb.c: add calls to sanei_usb_set_altinterface in sanei_usb_close and sanei_usb_clear_halt- hopefully work around USB3/xhci problems in Linux. ------------------------------------------------------------------------- Please carefully read https://build.opensuse.org/project/show?project=home:jsmeix You can get the packages in the "home:jsmeix" project for example for openSUSE 13.2 via this direct URL http://download.opensuse.org/repositories/home:/jsmeix/openSUSE_13.2/ When you like to upgrade an installed sane-backends 1.0.23 or 1.0.24 to sane-backends development version git20150108 you need to install version git20150108 with plain rpm using "--force" e.g. like # rpm -Uhv --force sane-backends-git20150108-2.1.x86_64.rpm because for rpm the version number git2015010 is lower than the installed version number 1.0.23 or 1.0.24. For my scanner that uses the plustek driver sane-backends development version git20150108 still works for me. This only means that sane-backends development version git20150108 is not totally broken but it does not mean that sane-backends development version git20150108 can also be used for your particular scanner at your particular computer. Caution: When you try it out and your scanner makes bad-sounding noises the usual reason is that the scanner's internal moving parts "do bad things" which means the scanner hardware could get damaged. Perhaps you are a venturous openSUSE user who likes to try out if sane-backends development version git20150108 works for you? If you like to try it out, please report whether or not it works for you. Many thanks in advance for testing it and for your feedback! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=920067 --- Comment #28 from robert spitzenpfeil --- (In reply to Johannes Meixner from comment #27) Yes, that is correct. -- You are receiving this mail because: You are on the CC list for the bug.