The firmware gets transmitted only partial and the scanner goes into error mode. While the LTS Kernel transmits the scanner firmware in four chunks, the 3.6.x Kernel tries to do it in one chunk. It seems like there has been a change in the usb-stack involving data transfer. 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. Hopefully someone more intimate with the subsystems at play can figure out just what's going on here. 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.ģ.7 and some versions of 3.6.x seem to able to successfully initialize sometimes, but not consistently.Īs 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. 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. 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. The issue is with scanner initialization. Here's what I can see, after a couple of bisects and testing on mainline (3.7-rc3). # found the scanner devices, be sure to adjust access permissions as # You may want to run this program as root to find all devices. # Most Scanners connected to the parallel port or other proprietary ports # Not checking for parallel port scanners. Try scanimage -L and read the backend's manpage. # Your USB scanner was (probably) detected. # Also you need support for SCSI Generic (sg) in your operating system.įound USB scanner (vendor=0x04b8, product=0x0130 ) at libusb:002:002 # you have loaded a kernel SCSI driver for your SCSI adapter. If you expected something different, make sure that # scanner is powered up and properly connected to your computer. # result is different from what you expected, first make sure your # sane-find-scanner will now attempt to detect your scanner. Here is the output of several (seemingly) relevant commands: I also attempted the steps in this post, modified very slightly to the appropriate product (0x0130) with no success: … 0#p1063520 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: … 5#p1157305 When the scanner was working, iscan-data was not necessary, nor is it necessary on the other computer. I've tried this process alternating installing iscan or iscan-data first, but that hasn't changed anything. I've even tried installing iscan-data thinking that perhaps that may be causing my issue. In attempting to resolve this I have removed and reinstalled the latest versions of iscan and iscan-plugin-gt-x770 from the AUR. I am currently using a pure systemd installation as outlined in the wiki and normally use the simple-scan package. 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 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. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |