Using LinuxMint v8.0 Helena.
Some time go I purchased one of these scanners, after I found through http://www.buzzard.me.uk/jonathan/scanners-usb.html that they work with Linux, and downloaded and installed sane-backends-1.0.19 and sane-frontends-1.0.14 as suggested. Xsane is installed, also.
However, when I clicked on XSane to launch the scanner the following error appeared: Failed to open device 'snapscan:libusb:001:002': Invalid argument. A search for snapscan:libusb:001:002 does not find it but a libusb command in the Terminal shows that it is installed.
At that time, and this is over a year ago, I decided not to bother about it and abandoned the idea. However, I recently came back to the problem - after all why have a scanner sitting on the desk if it doesn't work :-).
So, I downloaded the HowTo on your website http://www.wlug.org.nz/Benq3300/4300ScannerSetup and carefully followed the directions. Regrettably the scanner still does not work.
When I first ran xSane, the window opened. Clicked on Preview and the scanner sprang into action - well, it made noises as if something was going to happen - and then the xSane window closed.
Ran xSane again and got the error message: Failed to open device 'snapscan:lisusb:002:00': Error during device I/O
Entered the Terminal and did lusb, with the following result
zed@zed-desktop ~ $ lsusb Bus 002 Device 004: ID 04a5:20b0 Acer Peripherals Inc. (now BenQ Corp.) S2W 3300U/4300U Bus 002 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 005: ID 05e3:0702 Genesys Logic, Inc. USB 2.0 IDE Adapter Bus 001 Device 004: ID 03f0:2f17 Hewlett-Packard EWS 2605dn Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub zed@zed-desktop ~ $
So, the Device is there but xSane is "throwing a wobbly" :(
Opened the GIMP to use your suggestion that clicking on Acquire is the easiest way to get the scanner working but I cannot find Acquire in any of the menus in GIMP v2.6.7
From time to time the scanner "chatters" to itself - the light comes on and
flickers, becomes steady and then goes off. I don't know whether that is significant or not.
I have searched Google for the error and although there are numerous entries none seem to apply to my problem.
Any assistance would be much appreciated.
Zed
Some time go I purchased one of these scanners, after I found through http://www.buzzard.me.uk/jonathan/scanners-usb.html that they work with Linux, and downloaded and installed sane-backends-1.0.19 and sane-frontends-1.0.14 as suggested. Xsane is installed, also.
However, when I clicked on XSane to launch the scanner the following error appeared: Failed to open device 'snapscan:libusb:001:002': Invalid argument. A search for snapscan:libusb:001:002 does not find it but a libusb command in the Terminal shows that it is installed.
At that time, and this is over a year ago, I decided not to bother about it and abandoned the idea. However, I recently came back to the problem - after all why have a scanner sitting on the desk if it doesn't work :-).
So, I downloaded the HowTo on your website http://www.wlug.org.nz/Benq3300/4300ScannerSetup and carefully followed the directions. Regrettably the scanner still does not work.
When I first ran xSane, the window opened. Clicked on Preview and the scanner sprang into action - well, it made noises as if something was going to happen - and then the xSane window closed.
Ran xSane again and got the error message: Failed to open device 'snapscan:lisusb:002:00': Error during device I/O
Entered the Terminal and did lusb, with the following result
zed@zed-desktop ~ $ lsusb Bus 002 Device 004: ID 04a5:20b0 Acer Peripherals Inc. (now BenQ Corp.) S2W 3300U/4300U Bus 002 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 005: ID 05e3:0702 Genesys Logic, Inc. USB 2.0 IDE Adapter Bus 001 Device 004: ID 03f0:2f17 Hewlett-Packard EWS 2605dn Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub zed@zed-desktop ~ $
So, the Device is there but xSane is "throwing a wobbly" :(
Opened the GIMP to use your suggestion that clicking on Acquire is the easiest way to get the scanner working but I cannot find Acquire in any of the menus in GIMP v2.6.7
On the command-line, you can use the following command to list all available scanners: scanimage -L
In the past, I had problems with the default sane plugin in GIMP and I switched to "quiteinsance": sudo apt-get install gimp2.0-quiteinsane
The "Acquire" is now available under "Create", if I'm not mistaken. Since the ID of USB devices - like your scanner - can change, depending on the order one plugs in things, I always go through quiteinsane's "selecte device" dialog first.
Cheers, Peter
Peter Reutemann fracpete@gmail.com wrote:
[snip]
So, I downloaded the HowTo on your website http://www.wlug.org.nz/Benq3300/4300ScannerSetup and carefully followed the directions. Regrettably the scanner still does not work.
When I first ran xSane, the window opened. Clicked on Preview and the scanner sprang into action - well, it made noises as if something was going to happen - and then the xSane window closed.
Ran xSane again and got the error message: Failed to open device 'snapscan:lisusb:002:00': Error during device I/O
[snip]
This has to be the quickest response to any query I have placed in a mailing list. Thank you.
On the command-line, you can use the following command to list all available scanners:
scanimage
This returns:
@zed-desktop ~ $ scanimage -L device `snapscan:libusb:002:004' is a Acer FlatbedScanner23 flatbed scanner zed@zed-desktop ~ $
In the past, I had problems with the default sane plugin in GIMP and I switched to "quiteinsance": sudo apt-get install gimp2.0-quiteinsane
Thanks again. It is now installed.
The "Acquire" is now available under "Create", if I'm not mistaken. Since the ID of USB devices - like your scanner - can change, depending on the order one plugs in things, I always go through quiteinsane's "selecte device" dialog first.
Right, I did that. The only device shown was and got the error message:
SANE Message. IO Error while cxommunicating with the device.
Disconnected the scanner and reconnected after about five minutes. It was shown as Device 05 (002:005). However, going through the GIMP - Insane, I still get the same error message. :-(
Zed
[...]
Right, I did that. The only device shown was and got the error message:
SANE Message. IO Error while cxommunicating with the device.
Disconnected the scanner and reconnected after about five minutes. It was shown as Device 05 (002:005). However, going through the GIMP - Insane, I still get the same error message. :-(
Hmm... Don't know what's happening there. Maybe it's possible that you need to load the correct firmware? See the following wiki article: http://www.wlug.org.nz/Benq3300/4300ScannerSetup
Cheers, Peter
Peter Reutemann fracpete@gmail.com wrote:
[...]
Right, I did that. The only device shown was and got the error message:
SANE Message. IO Error while cxommunicating with the device.
Disconnected the scanner and reconnected after about five minutes. It was shown as Device 05 (002:005). However, going through the GIMP - Insane, I still get the same error message. :-(
Hmm... Don't know what's happening there. Maybe it's possible that you need to load the correct firmware? See the following wiki article: http://www.wlug.org.nz/Benq3300/4300ScannerSetup
They were the instructions I found on a web search. I thought I'd done things correctly. However, I'll go through the process again and report back.
Zed
On Tue, Feb 02, 2010 at 02:52:07PM +1300, Zed wrote:
Ran xSane again and got the error message: Failed to open device 'snapscan:lisusb:002:00': Error during device I/O
@zed-desktop ~ $ scanimage -L device `snapscan:libusb:002:004' is a Acer FlatbedScanner23 flatbed scanner
SANE Message. IO Error while cxommunicating with the device.
I have a scanner that used to mis-behave. The problem started when the linux kernel added support for powering down usb ports as a power-saving feature - some USB devices didn't quite fully adhere to the USB spec and weren't doing whatever they were supposed to do to prevent the power-saving mode from being activated.
The linux kernel now has a blacklist of usb vendor/model IDs so that it doesn't activate the power-saving mode of the USB port when my scanner is plugged in.
So firstly - how old is your kernel? This was fixed for me at least a year ago, so if you have a fairly recent kernel then maybe your problem is unrelated.
Secondly, when I had an affected kernel, I couldn't use apps that used the SANE libraries (like the gimp plugin or xsane), but I could scan ok from the command line using 'scanimage'. Maybe you can try scanning from the command line - if it still fails, then you can at least rule out the USB port power-saving problem that I experienced...
John
IIRC, permissions for the scanner can also be an issue.
I've had to amend a config file to get my Epson scanner to work.
Does running the scanner software under sudo work?
Chris
IIRC, permissions for the scanner can also be an issue.
I've had to amend a config file to get my Epson scanner to work.
Does running the scanner software under sudo work?
Good point, I had to do that as well for my Brother MFC215C. Forgot about that...
If it should work as root user (ie sudo), then you'd have to add a udev rule to set the correct permissions.
Open the file (replace vi with nano or any other editor that you prefer): sudo vi /etc/udev/rules.d/45-libsane.rules
And add the following (single) line: SYSFS{idVendor}=="04a5", SYSFS{idProduct}=="20b0", MODE="666", GROUP="scanner"
The values for "idVendor" and "idProduct" are the ones output by lsusb, that you posted earlier.
Cheers, Peter
Peter Reutemann fracpete@gmail.com wrote:
IIRC, permissions for the scanner can also be an issue.
I've had to amend a config file to get my Epson scanner to work.
Does running the scanner software under sudo work?
Good point, I had to do that as well for my Brother MFC215C. Forgot about that...
If it should work as root user (ie sudo), then you'd have to add a udev rule to set the correct permissions.
[snip]
Regrettably it didn't.
Zed
"Chris O'Halloran" cmoman@gmail.com wrote:
IIRC, permissions for the scanner can also be an issue.
I've had to amend a config file to get my Epson scanner to work.
Does running the scanner software under sudo work?
Regrettably no!
zed@zed-desktop ~ $ sudo -s [sudo] password for zed: zed-desktop ~ # scanimage scanimage: sane_start: Error during device I/O Segmentation fault
Zed
John McPherson jrm@wlug.org.nz wrote:
On Tue, Feb 02, 2010 at 02:52:07PM +1300, Zed wrote:
Ran xSane again and got the error message: Failed to open device 'snapscan:lisusb:002:00': Error during device I/O
@zed-desktop ~ $ scanimage -L device `snapscan:libusb:002:004' is a Acer FlatbedScanner23 flatbed scanner
SANE Message. IO Error while cxommunicating with the device.
I have a scanner that used to mis-behave. The problem started when the linux kernel added support for powering down usb ports as a power-saving feature - some USB devices didn't quite fully adhere to the USB spec and weren't doing whatever they were supposed to do to prevent the power-saving mode from being activated.
The linux kernel now has a blacklist of usb vendor/model IDs so that it doesn't activate the power-saving mode of the USB port when my scanner is plugged in.
So firstly - how old is your kernel? This was fixed for me at least a year ago, so if you have a fairly recent kernel then maybe your problem is unrelated.
v2.6.31 - default for LinuxMint v8.0
Secondly, when I had an affected kernel, I couldn't use apps that used the SANE libraries (like the gimp plugin or xsane), but I could scan ok from the command line using 'scanimage'. Maybe you can try scanning from the command line - if it still fails, then you can at least rule out the USB port power-saving problem that I experienced...
scan image gives:
zed@zed-desktop ~ $ scanimage scanimage: sane_start: Error during device I/O Segmentation fault
It's the first time the words "segmentation fault" have appeared. Means nothing to me, but it may do to someone else. I hope :-)
Zed
participants (4)
-
Chris O'Halloran -
John McPherson -
Peter Reutemann -
Zed