No doubt I will have forgotten a lot of things, but feel free to ask me any questions. Using media-gfx/sane-backends-1.0.18-r6 without any problems. Upgraded to media-gfx/sane-backends-1.0.19-r1 (newly stable) as part of regular updates. Using Kooka (KDE scan program). After the upgrade, Kook could not longer the scanner (an Epson multifunction device), even after rebooting the machine (yes, I did upgrade the configuration files). I reinstalled media-gfx/sane-backends-1.0.19-r1 and everything worked fine again. I did notice a slight difference in the log file between the libraries. First, with the new (non-working) library: Jun 9 10:01:49 system usb 4-2: new full speed USB device using uhci_hcd and address 4 Jun 9 10:01:49 system usb 4-2: configuration #1 chosen from 1 choice Jun 9 10:01:49 system usblp0: USB Bidirectional printer dev 4 if 1 alt 0 proto 2 vid 0x04B8 pid 0x0818 Jun 9 10:01:55 system usb 4-2: usbfs: interface 1 claimed by usblp while 'kooka' sets config #1 Jun 9 10:01:56 system usb 4-2: usbfs: interface 0 claimed by usbfs while 'kooka' sets config #1 Jun 9 10:01:56 system usb 4-2: usbfs: interface 0 claimed by usbfs while 'kooka' sets config #1 And with the older (working) library: Jun 9 10:22:00 system usb 4-2: new full speed USB device using uhci_hcd and address 5 Jun 9 10:22:00 system usb 4-2: configuration #1 chosen from 1 choice Jun 9 10:22:00 system usblp0: USB Bidirectional printer dev 5 if 1 alt 0 proto 2 vid 0x04B8 pid 0x0818 Jun 9 10:22:06 system usb 4-2: usbfs: interface 1 claimed by usblp while 'kooka' sets config #1 Jun 9 10:22:09 system usb 4-2: usbfs: interface 1 claimed by usblp while 'kooka' sets config #1 $ emerge -p --info Portage 2.1.4.4 (default-linux/x86/2007.0/desktop, gcc-4.1.2, glibc-2.6.1-r0, 2.6.23-gentoo-r9 i686) ================================================================= System uname: 2.6.23-gentoo-r9 i686 Intel(R) Pentium(R) 4 CPU 2.60GHz Timestamp of tree: Sat, 07 Jun 2008 23:06:01 +0000 app-shells/bash: 3.2_p33 dev-java/java-config: 1.3.7, 2.1.6 dev-lang/python: 2.4.4-r13 dev-python/pycrypto: 2.0.1-r6 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox: 1.2.18.1-r2 sys-devel/autoconf: 2.13, 2.61-r1 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.1 sys-devel/binutils: 2.18-r1 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.23-r3 ACCEPT_KEYWORDS="x86" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer -mfpmath=sse" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/udev/rules.d" CXXFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer -mfpmath=sse" DISTDIR="/usr/portage/distfiles" EMERGE_DEFAULT_OPTS="--with-bdeps y" FEATURES="distlocks metadata-transfer sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://imperator/ http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo" LANG="en_NZ.UTF-8" LINGUAS="en ru" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage /usr/local/porttemp /usr/portage/local/layman/sunrise" SYNC="rsync://imperator/gentoo-portage" USE="X a52 aac aalib acpi alsa arts audiofile berkdb bitmap-fonts bzip2 cairo caps cdparanoia cdr cjk cpudetection cracklib crypt css cups dbus dga directfb dri dvd dvdr dvdread encode exif expat fam fbcon ffmpeg flac gcj ggi gif glibc-omitfp gmp gphoto2 gpm gstreamer hal iconv idea imagemagick imap imlib ipv6 javascript jbig joystick jpeg kde lcms libcaca libwww live lm_sensors mad matroska mbox memlimit midi mmx mmxext mng mp3 mpeg mudflap mysql nas ncurses network nls no-old-linux nodrm nptl nptlonly ogg opengl openmp oscar pcre pdf perl png qt3 quicktime readline real rtc samba scanner sdl sensord silc smtp sndfile speex spell sse sse2 ssl stream svg sysfs tcpd theora threads threadsafe tiff timidity truetype truetype-fonts type1-fonts unicode usb userlocales utf8 vcd vorbis wideband win32codecs x86 xinerama xml xorg xv xvid yahoo zlib zrtp" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CAMERAS="ptp2" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LINGUAS="en ru" USERLAND="GNU" VIDEO_CARDS="i810" Unset: CPPFLAGS, CTARGET, INSTALL_MASK, LC_ALL, LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Oops. I meant "I reinstalled media-gfx/sane-backends-1.0.18-r6 and everything worked fine again." I reinstalled the OLD version, and Kooka recognized the scanner again.
Sorry if I am just a little blind - but where exactly did you write which backend/scanner you're using?
(In reply to comment #2) > Sorry if I am just a little blind - but where exactly did you write which > backend/scanner you're using? Using Kooka (KDE scan program). ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The log file even mentions it. :)
(In reply to comment #3) > (In reply to comment #2) > > Sorry if I am just a little blind - but where exactly did you write which > > backend/scanner you're using? > > Using Kooka (KDE scan program). > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > The log file even mentions it. :) Um... as it says in the brackets, "scan program" - I meant which SANE backend you are using. I saw now that you are using "an epson multifunction device", but that does not help me much. Sane is not monolithic, it uses a common framework and dedicated drivers for different scanner types. According to http://www.sane-project.org/sane-mfgs.html there are Epson scanners using the backends epson, epson2, snapscan and plustek - which one is yours? And what is the output of "scanimage -vvL" with .18 and .19?
Sorry, I didn't understand what you meant (and I am still not sure I understand what you want). One thing at a time, though. The device is an Epson CX-3700. I have no idea what I am doing, but it worked before using this line as my /etc/sane.d/epson.conf: usb 0x4b8 0x818 Does that mean I am using the epson backend? It does seem like I should be using epson2 now, but that doesn't make any difference. > And what is the output of "scanimage -vvL" with .18 and .19? For 1.0.18-r6: $ scanimage -vvL device `epson:libusb:004:006' is a Epson CX3800 flatbed scanner Calling sane_exit scanimage: finished For 1.0.19-r1: $ scanimage -vvL No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). Calling sane_exit scanimage: finished Also using 1.0.19-r1: $ 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. # Also you need support for SCSI Generic (sg) in your operating system. # If using Linux, try "modprobe sg". found USB scanner (vendor=0x04b8 [EPSON], product=0x0818 [USB MFP]) at libusb:004:007 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. [...] I don't know why it gets identified as a 3800 instead of a 3700 (not that there is much difference anyway). I don't understand why it is not getting recognized. If anything, this model should be better supported now - the 1.0.19 ChangeLog shows the following: 2006-08-22 Karl Heinz Kremer <khk@khk.net> * backend/epson_usb.c: Add product ID for CX3800/3810, V700/V750 If you have any other questions, please ask. Thank you.
(In reply to comment #5) [...] > Does that mean I am using the epson backend? It does seem like I should be > using epson2 now, but that doesn't make any difference. No, it is in the old unmaintained "epson" backend. [...] > I don't understand why it is not getting recognized. If anything, this model > should be better supported now - the 1.0.19 ChangeLog shows the following: > > 2006-08-22 Karl Heinz Kremer <khk@khk.net> > > * backend/epson_usb.c: Add product ID for CX3800/3810, V700/V750 This does only what you did in your epson.conf before. > If you have any other questions, please ask. Thank you. I would like to see the build log for .19-r1 and the output of strace -f -o strace-log scanimage -vvL Please be patient if I don't reply before monday, from monday on I will be on holidays for three weeks.
(In reply to comment #6) > (In reply to comment #5) > [...] > > Does that mean I am using the epson backend? It does seem like I > > should be using epson2 now, but that doesn't make any difference. > > No, it is in the old unmaintained "epson" backend. Sorry, I meant that using epson2 doesn't make any difference. > I would like to see the build log for .19-r1 and the output of > strace -f -o strace-log scanimage -vvL I can do the first right away (assuming I can get bugzilla to work - I tried a couple of times and got an error message). I need to rebuild the newer version to get the strace (something not possible at the moment, but I can do it in a few hours). > Please be patient if I don't reply before monday, from monday on > I will be on holidays for three weeks. No problem, since the old version works.
Created attachment 158609 [details] build log (compressed)
Created attachment 158657 [details] strace log (compressed) as requested
Looks a bit like the old version manages to solve the conflict with your usb printer driver and the new one doesn't. Could you add an strace log for the working version?
Created attachment 159049 [details] strace log using sane-backends-1.0.18-r6
The strace log of .19 shows that (in contrast to .18) the epson2 driver is tried before the epson driver is loaded. epson2 manages to claim the interface while epson doesn't. Could you maybe try rebuilding .19 with SANE_BACKENDS="epson" set and then try again? Maybe some other driver (perhaps epson2) messes with the usb access.
Could you please try 1.0.19-r2, maybe? It looks like the epson2 driver did not always close the scanner device, perhaps this is the problem.
(In reply to comment #12) > Could you maybe try rebuilding .19 with SANE_BACKENDS="epson" set and > then try again? Maybe some other driver (perhaps epson2) messes with > the usb access. That did work, although I thought I should lean toward epson2, as you said no one maintains the original epson driver now. I will try -r2 and report on it within a day. Thanks again.
(In reply to comment #14) > I will try -r2 and report on it within a day. Thanks again. I think the day is over. Any progress?
(In reply to comment #15) > I think the day is over. Any progress? Sorry for the delay. I actually did install this a few days ago, but I have the scanner hooked up to my wife's machine, and didn't have a good chance to take a look at it. I only did a very superficial test just now, but the application program DID recognize the scanner. Any thoughts about how to get this working with the epson2 backend instead of the (unsupported) epson. Thanks again.
(In reply to comment #16) [...] > Any thoughts about how to get this working with the epson2 > backend instead of the (unsupported) epson. Thanks again. I am not sure if your scanner is supported by epson2, but you can of course try. Commenting out the "epson" entry in /etc/sane.d/dll.conf should do the job. Or you can define the available backends before building sane-backends like suggested in comment #12. For now, I consider the issue "fixed".
I was getting the same error with a Canon Pixma 240, After updating the kernel to 2.6.8-r2 (gentoo sources) with Device Drivers -> USB support-> Support for Host-side USB (USB [=y] enabled (probably not important). Started working after this.
