Hey there, I hope you won't get the message twice .. I used the wrong outgoing SMTP server on my machine so the mailing daemon did not recongize my account ... here we go a second time
I got the following problem: I have a SnapScan e20 USB Scanner at home and tried to get it running but failed: - I run SuSE 7.2 Professional - I followed the instructions @ http://snapscan.sourceforge.net/ - I recompiled SANE with the patched snapscan backend files and installed it # sane-config --version 1.0.5 - I changed the header Files as described in <kernel>/drivers/usb/scanner.h struct usb_device_id scanner_device_ids [] = { ... /* Agfa */ { USB_DEVICE(0x06bd, 0x2091) }, /* SnapScan e20 */ { USB_DEVICE(0x06bd, 0x0001) }, /* SnapScan 1212U */ { USB_DEVICE(0x06bd, 0x0002) }, /* SnapScan 1236U */ { USB_DEVICE(0x06bd, 0x2061) }, /* Another SnapScan 1212U (?)*/ { USB_DEVICE(0x06bd, 0x0100) }, /* SnapScan Touch */ - I recompiled my kernel: version 2..4.10 --> USB drivers as modules - Inserting the scanner module succeds bash-2.05# lsmod Module Size Used by scanner 7264 0 (unused) ... usb-uhci 21216 0 (unused) usbcore 47040 1 [scanner hid usb-uhci] ... - Uploading the firmware seems to work: BUT: the scanner flasshes the lights, moves something internaly, then the lights are OUT, after some tme it turns on again ? Is that normal? bash-2.05# modprobe scanner bash-2.05# agfafirm -v /dev/usbscanner /opt/snapscan/snape20.bin Scanner Information (from scanner) Vendor: AGFA Version: 0100 Model: SNAPSCAN Firmware date: Wed Dec 9 1998 14:37 Firmware Information (from file) Chip: 7107U Vendor: AGFA Version: 0.62 Model: SNAPSCAN e20 Firmware date: Tue Nov 14 2000 14:14 Size: 30149 Uploading new firmware... Done! Scanner Information (from scanner) Vendor: AGFA Version: 0062 Model: SNAPSCAN e20 Firmware date: Tue Nov 14 2000 14:14 - I changed the /etc/sane.d/snapscan.conf File: bash-2.05# more /etc/sane.d/snapscan.conf scsi AGFA scsi COLOR scsi ACERPERI /usr/bin/agfafirm -v /dev/usbscanner /opt/snapscan/snape20.bin # If not automatically found from above, then you may manually specify # a device name. #/dev/scanner /dev/usbscanner #/dev/sga - now when I run xsane it starts up and finds the scanner (seems to ...) hermaf@hermaf:~ > scanimage /dev/usbscanner scanimage: sane_start: Device busy hermaf@hermaf:~ > xscanimage /dev/usbscanner --> Failed to open device '/dev/usbscanner': invalid Argument hermaf@hermaf:~ > xscanimage snapscan:/dev/usbscanner --> Failed to open device 'snapscan:/dev/usbscanner': invalid Argument hermaf@hermaf:~ >xsane --> Scanning for device --> xsan: No devixe available Someone knows what to do or what is wrong ? Thx Felix
