FS#12640 - usb scanner not work (multifunction printer EPSON DX4250)
Attached to Project:
Arch Linux
Opened by pcxz (pcxz) - Friday, 02 January 2009, 13:58 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 20 January 2009, 06:01 GMT
Opened by pcxz (pcxz) - Friday, 02 January 2009, 13:58 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 20 January 2009, 06:01 GMT
|
Details
Description: usb scanner not work (multifunction printer
EPSON DX4250)
Additional info: If remove module usblp scanner work, ..and printer no, I found this solution in this post (speak of patch required to sane) http://lists.alioth.debian.org/pipermail/sane-devel/2005-September/014721.html Steps to reproduce: From root search scanner with command: bash-3.2# 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. found USB scanner (vendor=0x04b8 [EPSON], product=0x0820 [USB2.0 MFP(Hi-Speed)]) at libusb:002:012 found USB scanner (vendor=0x046d, product=0x08da) at libusb:001:003 # 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. bash-3.2# After this add command: bash-3.2# scanimage -L device `v4l:/dev/video0' is a Noname USB Camera (046d:08da) virtual device bash-3.2# ..lost. dmesg report this: bash-3.2# dmesg .. usblp0: USB Bidirectional printer dev 12 if 1 alt 0 proto 2 vid 0x04B8 pid 0x0820 usb 2-2: usbfs: interface 1 claimed by usblp while 'scanimage' sets config #1 bash-3.2# |
This task depends upon
#scanimage -L
device `brother2:bus1;dev1' is a Brother DCP-7010 USB scanner
FS#12820.This is fixed for me using kernel 2.6.28.1 from testing
Thx all
FS#12820as far as i can tell. Theres no need to patch it.