You are not logged in.
This is my first post; I've been using ArchLinux as my only OS for just over a year, and prior to that used Linux Mint since eschewing MicroSoft products sometime in 2008.
I performed an update recently which included systemd package, which I think may be related to the issue as the problem began only after the update. I have never had any issues with the scanner prior to this update and I have another computer which I have not updated to systemd which is still able to use the scanner as before. I am currently using a pure systemd installation as outlined in the wiki and normally use the simple-scan package.
In attempting to resolve this I have removed and reinstalled the latest versions of iscan and iscan-plugin-gt-x770 from the AUR. I've even tried installing iscan-data thinking that perhaps that may be causing my issue. I've tried this process alternating installing iscan or iscan-data first, but that hasn't changed anything.
When the scanner was working, iscan-data was not necessary, nor is it necessary on the other computer.
I was experiencing the 'Failed cupsGetDevices' error as explained in another thread, but followed the instructions in this post and haven't had any further issues of this type: https://bbs.archlinux.org/viewtopic.php … 5#p1157305
I also attempted the steps in this post, modified very slightly to the appropriate product (0x0130) with no success: https://bbs.archlinux.org/viewtopic.php … 0#p1063520
Here is the output of several (seemingly) relevant commands:
$ > lsusb
Bus 001 Device 002: ID 046d:c062 Logitech, Inc. LS1 Laser Mouse, corded
Bus 002 Device 002: ID 04b8:0130 Seiko Epson Corp. GT-X770 [Perfection V500]
Bus 002 Device 005: ID 2001:f103 D-Link Corp. DUB-H7 7-port USB 2.0 hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
$ > scanimage -L
device `epkowa:interpreter:002:002' is a Epson (unknown model) flatbed scanner
$ > 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=0x0130 [EPSON Scanner]) at libusb:002:002
# Your USB scanner was (probably) detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.
# You may want to run this program as root to find all devices. Once you
# found the scanner devices, be sure to adjust access permissions as
# necessary.
$ > iscan
Could not send command to scanner.
Check the scanner's status.
I've tried adding the following to /etc/sane.d/epkowa.conf:
usb 0x04b8 0x0130
which produces this:
$ > scanimage -L
device `epkowa:usb:002:002' is a Epson (unknown model) flatbed scanner
device `epkowa:interpreter:002:002' is a Epson (unknown model) flatbed scanner
but also just takes much longer before the error light starts flashing on the scanner.
Any help is highly appreciated.
edit: It occurs to me that I also updated to linux kernel 3.6.2 in the same update as systemd, so that may be the issue as well. There seems to be a somewhat similar issue in this post: https://bbs.archlinux.org/viewtopic.php?id=150960
Last edited by beholdbob (2012-10-24 21:54:40)
Offline
I double this. Absolutely the same situation with Epson Perfection V300 Photo scaner.
Have no clue how to resolve it.
Offline
Installing linux-lts (kernel 3.0.46-1-lts) has brought my V500 back to life.
iScan, Sane and Vuescan all work again.
Fortunately you can have both the lts and the bleeding edge kernels installed together.
Pete
Offline
Are you in the "scanner" group?
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
Are you in the "scanner" group?
Yes, in the first post I linked to this was a critical step.
Installing linux-lts (kernel 3.0.46-1-lts) has brought my V500 back to life.
I'll give this a shot when I get home from work and post my results.
Offline
Sorry, I didn't even read the initial post... I just Ctrl+F and searched for "scanner", and then searched for "group" and there were no results. I had a similar problem, with Epson Perfection V33, in a VirtualBox session, and it worked only after adding my user to the "scanner" group on the host OS. It seems that it's actually a very important step. Check with:
$ groups
Logout or reboot if you just added yourself now, for the changes to take effect.
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
Sorry, I didn't even read the initial post... I just Ctrl+F and searched for "scanner", and then searched for "group" and there were no results. I had a similar problem, with Epson Perfection V33, in a VirtualBox session, and it worked only after adding my user to the "scanner" group on the host OS. It seems that it's actually a very important step. Check with:
$ groups
Logout or reboot if you just added yourself now, for the changes to take effect.
I guess you didn't read it this time either as I have already established that I am in correct group:
I was experiencing the 'Failed cupsGetDevices' error as explained in another thread, but followed the instructions in this post and haven't had any further issues of this type: https://bbs.archlinux.org/viewtopic.php … 5#p1157305
I very much appreciate that you are trying to help my issue, but with your signature being almost entirely devoted to proper grammer, I would have expected you to _read_.
Please consider that I've been using Arch for quite some time and this is the first issue I have posted about. I am well aware of the groups issue some users have experienced, which is well documented. Thank you.
Offline
Installing linux-lts (kernel 3.0.46-1-lts) has brought my V500 back to life.
I've installed linux-lts but still no luck.
Additionally, I've uninstalled and reinstalled iscan and iscan-plugin-gt-x770, ensured my system is completely up to date and rebooted, but I get the exact same result as before.
Thank you for the suggestion.
Offline
Not trying to be funny here, but you did change/add add an entry to your bootloader to boot linux-lts instead of linux didn't you?
I quite like having both linux and linux-lts installed, then if something goes wrong after a kernel update you can quickly reboot into the 'other' one and hopefully get going again.
Pete
Last edited by shetland_breeder (2012-10-24 08:16:38)
Offline
Not trying to be funny here, but you did change/add add an entry to your bootloader to boot linux-lts instead of linux didn't you?
Ha! No, I must not have been thinking clearly.
I'll try again this evening, thank you.
Offline
And it now seems there's a serious bug in 3.6.2 and 3.6.3 if you run ext4 filesystems: https://bbs.archlinux.org/viewtopic.php?id=151341
Another reason for using linux-lts ATM.
Off to downgrade my laptop which has an SSD and thus ext4 fs...
Offline
My aged Epson Perfection 3170 Photo is working again after booting with the linux-lts kernel. I've had all sorts of fun and games keeping this scanner working with linux over the past 8 years but I've never, ever had the red error light flashing at me.
Offline
shetland_breeder wrote:Not trying to be funny here, but you did change/add add an entry to your bootloader to boot linux-lts instead of linux didn't you?
Ha! No, I must not have been thinking clearly.
I'll try again this evening, thank you.
This worked perfectly. Thanks again.
Offline
I know this is marked as "solved" but I had similar issues with my Epson Perfection 3590 scanner. I mainly use it inside a VirtualBox VM running Windows XP. When I try to run the scanner utility, it complains about not being able to communicate with the scanner.
I tried installing linux-lts and booting the 3.0.48 kernel and the scanner works again in the VM.
While this is a great work-around for me, I'm not sure that qualifies as "solved". I'd prefer to have my scanner working with the latest kernel, but right now, I'll take a working scanner.
Offline
I had the same problem with a V500. I solved it by downgrading to linux-3.5.6.
Offline
Same here, with Epson Perfection V300 Photo. 3.5.6 works. Building 3.7-rc3 to see if that has the same problem or not.
Offline
Here's what I can see, after a couple of bisects and testing on mainline (3.7-rc3).
The issue is with scanner initialization. If the scanner is initialized in linux-lts or linux 3.5.6 or another working version, it can scan without problems, even in 3.6.3 -- just don't turn your scanner off/on between reboots.
If the scanner is turned on while hooked up to a computer running 3.6, it instantly gets an error light, along with some dmesg output about microframes. I don't see the instant error light in 3.6.3, but the error light can activate if I try to initialize from 3.6.3.
3.7 and some versions of 3.6.x seem to able to successfully initialize sometimes, but not consistently.
As I am not familiar with the kernel's USB subsystem and since it appears to be difficult to determine exactly what should count as a "bad" commit (as there are probably multiple bugs at play here; the instant error light, which may already be fixed, and the rare successful initialization from 3.6.1+), I have given up on my bisection. Hopefully someone more intimate with the subsystems at play can figure out just what's going on here.
Last edited by cookiecaper (2012-10-29 08:36:02)
Offline
I checked the usb initialization sequence for my Epson Perfection V330 Photo using usbmon and compared Kernel 3.6.3 with the current LTS Kernel. It seems like there has been a change in the usb-stack involving data transfer. While the LTS Kernel transmits the scanner firmware in four chunks, the 3.6.x Kernel tries to do it in one chunk. The problem is - the chunk is too small. The firmware gets transmitted only partial and the scanner goes into error mode. Still need to report this upstream...
My guess is that this bug also affects scanners by other manufacturers and possibly other devices needing an usb firmware upload.
Edit: The changelog fot the current 3.6.4 kernel has a patch listed that might solve this problem:
commit e4e29779ec498f4905461a13b6ba58ba4f60152b
Author: Henrik Rydberg <rydberg@euromail.se>
Date: Sat Oct 13 12:20:36 2012 +0200
usbdevfs: Fix broken scatter-gather transfer
commit 014639003c77a51fc319c9fdf225e7747cb6e18d upstream.
The handling of large output bulk transfers is broken; the same user
page is read over and over again. Fixed with this patch.
Edit: I tried 3.6.4 from testing-repo. Works like a charm
Last edited by twi (2012-10-29 15:34:08)
Offline
@twi,@cookiecaper
Thanks for the updates. I may try to enable the testing repos and try 3.6.4 to see if my issues are fixed as well.
Offline
Scanner is now working without issues with linux 3.6.5.
Offline
I still get inconsistent results with 3.6.10.
Offline
I had to downgrade to 3.6.8-1. Working well now.
I also had to comment out two redundant entries in /usr/var/lib/iscan/interpreter before the scanner started to work. (I am using Epson Perfection V10).
# interpreter usb 0x04b8 0x012d /usr/lib64/iscan/libesint66 /usr/share/iscan/esfw66.bin
# interpreter usb 0x04b8 0x012d /usr/lib/iscan/libesint66 /usr/share/iscan/esfw66.bin
interpreter usb 0x04b8 0x012d /usr/lib/iscan/libesint66 /usr/share/iscan/esfw66.bin
Last edited by kuba_66 (2013-01-02 03:28:29)
Offline
Kernel 3.6.11 solves it. No need to downgrade any more.
Offline