Hello,
On Mar 20 00:17 Bernhard Reiter wrote (excerpt):
Xerox WorkCentre 3225 connected with USB.
In general when your scanner is connected via USB: There are currently isues when the xhci kernel module is used for USB ports where the scanner is connected. Only "lsusb -t" will tell you what kernel module/driver is actually used for the USB bus and port where your scanner is connected to. Check the "lsusb -t" output if the "xhci_hcd" USB kernel driver (a.k.a. "USB 3") is used. Neither the color nor what the port is labeled on the computer is reliable regarding what kernel driver is used for the port. For example my testing machine has 4 USB ports, two labeled with the "super speed" USB logo (a.k.a. USB 3) and two labeled with the normal USB logo (a.k.a. USB 2) but for all 4 ports xhci is used. Furthermore all USB ports on my testing machine have same dark color. Also the "super speed" (USB 3) labeled ports are basically black. Their exact color is "very dark" but not "100% black" and neither blue (USB 3.0) nor teal blue (USB 3.1), cf. https://en.wikipedia.org/wiki/USB#Colors Only "lsusb -t" output shows what kernel driver is actually used. See https://bugzilla.suse.com/show_bug.cgi?id=955079#c2 and https://bugzilla.opensuse.org/show_bug.cgi?id=856794 in particular see https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c50 Regarding "USB 2" versus "USB 3" see also http://lists.alioth.debian.org/pipermail/sane-devel/2015-December/034197.html and http://lists.alioth.debian.org/pipermail/sane-devel/2015-December/034207.html In particular in http://lists.alioth.debian.org/pipermail/sane-devel/2015-December/034197.html there is: ---------------------------------------------------------------- When your scanner is not connected at a USB port where the kernel module xhci_hcd is used as kernel driver (e.g. when your scanner is connected at a USB port where the kernel module uhci_hcd or ehci_hcd is used as kernel driver), then have a look at "Trouble-Shooting (Debugging)" in https://en.opensuse.org/SDB:Configuring_Scanners For example to get USB debugging information you could use comands (as root) like export SANE_DEBUG_SANEI_USB=128 scanimage -L unset SANE_DEBUG_SANEI_USB ----------------------------------------------------------------
Source RPM : sane-backends-1.0.23-9.2.3.src.rpm
You may try out if the current sane-backends-1.0.25 perhaps works better. For direct RPM download of sane-backends-1.0.25 from the OBS "graphics" project, use http://download.opensuse.org/repositories/graphics/ and select your exact operating system and architecture. In particular see https://bugzilla.suse.com/show_bug.cgi?id=856794#c30 and subsequent comments. The current sane-backends-1.0.25 RPM from the OBS "graphics" project should no longer have issues with "libgphoto2" on released openSUSE versions because meanwhile the gphoto2 backend was removed because its usefulness is highly questionable, but adds many (indirect) build and runtime dependencies, see the current RPM changelog: https://build.opensuse.org/package/view_file/graphics/sane-backends/sane-backends.changes?expand=1 Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- sane-devel mailing list: [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to [email protected]
