Missing the obvious with my scanner?
OK, I am trying to get my USB HP scanjet 2200c working with SuSE 8.0. According to the various webpages on scanners in Linux (eg http://www.semeniuk.net/linux/hp2200/ ) I should be able to use the plustek backend to fire up the scanner. Thing is, after a couple hours of reading and trying things it's still not working. I have made some progress, but I seem to be stuck trying to initialize the silly thing. Here's what I have so far...... - I can see the scanner if I open the SuSE hardware-detect applet. - If I run usbview, it takes a while - more than a minute, but the window eventually pops up and hanging off one of the USB root devices is the usbscanner device. - cat /proc/bus/usb/devices gives me (as one of the results): ------------------------------------------------- T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=0605 Rev= 1.00 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=usbscanner E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl= 16ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms E: Ad=03(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms ----------------------------------------------- sane-find-scanner gives me: -------------------------------------------------- sane-find-scanner: found USB scanner (vendor = 0x03f0, product = 0x0605) at device /dev/usb/scanner0 sane-find-scanner: found USB scanner (vendor = 0x03f0, product = 0x0605) at device /dev/usbscanner --------------------------------------------------- so... that seems to be right. I have edited /etc/sane.d/plustek.conf so that it looks like this (edited down to take out the instruction comments to save space in the email): --------------------------------------------------- warmup -1 lOffOnEnd -1 lampOff -1 [usb] 0x03f0 0x0605 option lampOff 180 option lOffOnEnd 1 device /dev/usbscanner ------------------------------------------------------- Now when I try to start a scan manually, nothing happens. For example: ---------------------------------------------------------- scanimage -d plustek:/dev/usb/scanner0 scanimage: open of device plustek:/dev/usb/scanner0 failed: Error during device I/O ---------------------------------------------------------- Permissions on /dev/usbscanner are: crw-rw-rw- 1 ccornell users 180, 48 Mar 23 20:50 usbscanner Permissions on /dev/usb/scanner0 are: crw-rw-rw- 1 ccornell users 180, 48 Mar 23 20:50 scanner0 scanimage --list-devices returns the error that no scanners were identified. xscanimage just hangs there for a while (~2 minutes) and exits with a message that no scanners were identified. Kooka takes about 2 minutes to start up, and cannot find any scanners. xsane is the same... hangs for a while, and then reports back that there are no scanner devices. So, anyone see what I have missed here? Why is this scanner just sitting there so smugly, refusing to startup? C.
This gets stranger.... Out of frustration I rebooted. This time around, xsane started up immediately - found the scanner, but would not do a scan... it hung up when I clicked Preview scan. When I xsane regained it's sanity, I exited the app, and restarted it. Now I am back to where I was before... the device is connected and sane-find-scanner can find the device, but sane insists that it is not an LM9832 chip based scanner - I checked, I took the scanner apart and verified that it is indeed an LM9832. Still looking for ideas or suggestions for what is wrong... or what I am missing here. C. On Sunday 28 July 2002 21:43, Clayton Cornell wrote:
OK, I am trying to get my USB HP scanjet 2200c working with SuSE 8.0. According to the various webpages on scanners in Linux (eg http://www.semeniuk.net/linux/hp2200/ ) I should be able to use the plustek backend to fire up the scanner. Thing is, after a couple hours of reading and trying things it's still not working. I have made some progress, but I seem to be stuck trying to initialize the silly thing.
Here's what I have so far......
- I can see the scanner if I open the SuSE hardware-detect applet. - If I run usbview, it takes a while - more than a minute, but the window eventually pops up and hanging off one of the USB root devices is the usbscanner device.
- cat /proc/bus/usb/devices gives me (as one of the results): ------------------------------------------------- T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=0605 Rev= 1.00 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=usbscanner E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl= 16ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms E: Ad=03(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms -----------------------------------------------
sane-find-scanner gives me: -------------------------------------------------- sane-find-scanner: found USB scanner (vendor = 0x03f0, product = 0x0605) at device /dev/usb/scanner0 sane-find-scanner: found USB scanner (vendor = 0x03f0, product = 0x0605) at device /dev/usbscanner ---------------------------------------------------
so... that seems to be right.
I have edited /etc/sane.d/plustek.conf so that it looks like this (edited down to take out the instruction comments to save space in the email): --------------------------------------------------- warmup -1 lOffOnEnd -1 lampOff -1 [usb] 0x03f0 0x0605 option lampOff 180 option lOffOnEnd 1 device /dev/usbscanner -------------------------------------------------------
Now when I try to start a scan manually, nothing happens. For example: ---------------------------------------------------------- scanimage -d plustek:/dev/usb/scanner0 scanimage: open of device plustek:/dev/usb/scanner0 failed: Error during device I/O ----------------------------------------------------------
Permissions on /dev/usbscanner are: crw-rw-rw- 1 ccornell users 180, 48 Mar 23 20:50 usbscanner Permissions on /dev/usb/scanner0 are: crw-rw-rw- 1 ccornell users 180, 48 Mar 23 20:50 scanner0
scanimage --list-devices returns the error that no scanners were identified. xscanimage just hangs there for a while (~2 minutes) and exits with a message that no scanners were identified. Kooka takes about 2 minutes to start up, and cannot find any scanners. xsane is the same... hangs for a while, and then reports back that there are no scanner devices.
So, anyone see what I have missed here? Why is this scanner just sitting there so smugly, refusing to startup?
C.
Did you set-up the scanner in YAST2 before you run any application? (YAST2 -> Hardware -> Scanner) On Sunday 28 July 2002 21:44, Clayton Cornell wrote:
This gets stranger....
Out of frustration I rebooted. This time around, xsane started up immediately - found the scanner, but would not do a scan... it hung up when I clicked Preview scan. When I xsane regained it's sanity, I exited the app, and restarted it. Now I am back to where I was before... the device is connected and sane-find-scanner can find the device, but sane insists that it is not an LM9832 chip based scanner - I checked, I took the scanner apart and verified that it is indeed an LM9832.
Still looking for ideas or suggestions for what is wrong... or what I am missing here.
C.
On Sunday 28 July 2002 21:43, Clayton Cornell wrote:
OK, I am trying to get my USB HP scanjet 2200c working with SuSE 8.0. According to the various webpages on scanners in Linux (eg http://www.semeniuk.net/linux/hp2200/ ) I should be able to use the plustek backend to fire up the scanner. Thing is, after a couple hours of reading and trying things it's still not working. I have made some progress, but I seem to be stuck trying to initialize the silly thing.
Here's what I have so far......
- I can see the scanner if I open the SuSE hardware-detect applet. - If I run usbview, it takes a while - more than a minute, but the window eventually pops up and hanging off one of the USB root devices is the usbscanner device.
- cat /proc/bus/usb/devices gives me (as one of the results): ------------------------------------------------- T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=0605 Rev= 1.00 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=usbscanner E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl= 16ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms E: Ad=03(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms -----------------------------------------------
sane-find-scanner gives me: -------------------------------------------------- sane-find-scanner: found USB scanner (vendor = 0x03f0, product = 0x0605) at device /dev/usb/scanner0 sane-find-scanner: found USB scanner (vendor = 0x03f0, product = 0x0605) at device /dev/usbscanner ---------------------------------------------------
so... that seems to be right.
I have edited /etc/sane.d/plustek.conf so that it looks like this (edited down to take out the instruction comments to save space in the email): --------------------------------------------------- warmup -1 lOffOnEnd -1 lampOff -1 [usb] 0x03f0 0x0605 option lampOff 180 option lOffOnEnd 1 device /dev/usbscanner -------------------------------------------------------
Now when I try to start a scan manually, nothing happens. For example: ---------------------------------------------------------- scanimage -d plustek:/dev/usb/scanner0 scanimage: open of device plustek:/dev/usb/scanner0 failed: Error during device I/O ----------------------------------------------------------
Permissions on /dev/usbscanner are: crw-rw-rw- 1 ccornell users 180, 48 Mar 23 20:50 usbscanner Permissions on /dev/usb/scanner0 are: crw-rw-rw- 1 ccornell users 180, 48 Mar 23 20:50 scanner0
scanimage --list-devices returns the error that no scanners were identified. xscanimage just hangs there for a while (~2 minutes) and exits with a message that no scanners were identified. Kooka takes about 2 minutes to start up, and cannot find any scanners. xsane is the same... hangs for a while, and then reports back that there are no scanner devices.
So, anyone see what I have missed here? Why is this scanner just sitting there so smugly, refusing to startup?
C.
-- Frits J. Wüthrich (Sent with Kmail)
Finally cooled off enough that my computer room is no longer an oven. Found some energy to work on this problem again, so here goes.... To answer everyones suggestions/questions.... On Sunday 28 July 2002 23:14, Frits J. Wüthrich wrote:
Did you set-up the scanner in YAST2 before you run any application? (YAST2 -> Hardware -> Scanner)
That was the first thing I did after reading up on what backend was/is supposed to support the scanner I have. That seemed to have no effect. That was about when I resorted to doing things the manual way. I fired up my favorite console text editor and started poking about in the .config files. in /etc/sane.d On Sunday 28 July 2002 23:13, Alain Barthélemy wrote:
In /etc/sane.d/hp.conf ot /usr/local/etc/sane.d/hp.conf
add the line:
option connect-device
Did that (except its in plustek.conf because that's the backend I need to use for my scanner)... no noticeable effect. On Sunday 28 July 2002 23:50, paul ollion wrote:
Type lsmod to see if your scanner module is listed there.
This also shows the scanner. A few relevant lines from lsmod: ---------------------------------------------- scanner 8480 0 usbcore 55136 1 [scanner usb-uhci] ---------------------------------------------- I rebooted again tonight just to see what would happen. Fired up XSane. It started up nicely and recognised my scanner right off. Under File/Info in XSane, I see this: -------------------------------------------- Scanner and backend Vendor: Hewlett-Packard Model: Scanjet 2200c Type: USB flatbed scanner Device: /dev/usbscanner Loaded backend: plustek Sane version: 1.0.7 -------------------------------------------- So, that tells me that things are almost working. Problem is, I cannot get any farther. If I try to do a scan, nothing happens. The software tries to do something and eventually exits with an error. I turned on the debugging stuff and with the initial startup af XSane, it properly idents the scanner, and appears to work correctly. If I try to scan, or exit and restart XSane, scanimage or whatever scanner app, it just exits with an I/O error. The debug stuff tells me that I no longer have a recognisable scanner -------------------------------------------- [plustek] UIO error [plustek] This is not a LM9831 or LM9832 chip based scanner. --------------------------------------------- Even though it is indeed an LM9832 chip based scanner. So... still looking for suggestions and ideas. C.
For those who care/are interested, I finally got the scanner working. Only after updating SANE to the latest version, double checking the plustek.conf file, reading the info at http://www.gjaeger.de/scanner/usb/Plustek-USB.txt and rebooting again did it actually start working. Interesting, since according to the documentation, the version of Sane that comes with SuSE8 is supposed to support this scanner using the Plustek backend. As for the rebooting, that seems to be a problem with my hotplugging setup - at least I cannot think of anything else that is in the way there. Haven't read up enough on this subject yet to fully understand what's going on here C. On Wednesday 31 July 2002 22:12, Clayton Cornell wrote:
Finally cooled off enough that my computer room is no longer an oven. Found some energy to work on this problem again, so here goes....
To answer everyones suggestions/questions....
On Sunday 28 July 2002 23:14, Frits J. Wüthrich wrote:
Did you set-up the scanner in YAST2 before you run any application? (YAST2 -> Hardware -> Scanner)
That was the first thing I did after reading up on what backend was/is supposed to support the scanner I have. That seemed to have no effect. That was about when I resorted to doing things the manual way. I fired up my favorite console text editor and started poking about in the .config files. in /etc/sane.d
On Sunday 28 July 2002 23:13, Alain Barthélemy wrote:
In /etc/sane.d/hp.conf ot /usr/local/etc/sane.d/hp.conf
add the line:
option connect-device
Did that (except its in plustek.conf because that's the backend I need to use for my scanner)... no noticeable effect.
On Sunday 28 July 2002 23:50, paul ollion wrote:
Type lsmod to see if your scanner module is listed there.
This also shows the scanner. A few relevant lines from lsmod: ---------------------------------------------- scanner 8480 0 usbcore 55136 1 [scanner usb-uhci] ----------------------------------------------
I rebooted again tonight just to see what would happen. Fired up XSane. It started up nicely and recognised my scanner right off. Under File/Info in XSane, I see this: -------------------------------------------- Scanner and backend Vendor: Hewlett-Packard Model: Scanjet 2200c Type: USB flatbed scanner Device: /dev/usbscanner Loaded backend: plustek Sane version: 1.0.7 --------------------------------------------
So, that tells me that things are almost working. Problem is, I cannot get any farther. If I try to do a scan, nothing happens. The software tries to do something and eventually exits with an error. I turned on the debugging stuff and with the initial startup af XSane, it properly idents the scanner, and appears to work correctly. If I try to scan, or exit and restart XSane, scanimage or whatever scanner app, it just exits with an I/O error. The debug stuff tells me that I no longer have a recognisable scanner -------------------------------------------- [plustek] UIO error [plustek] This is not a LM9831 or LM9832 chip based scanner. --------------------------------------------- Even though it is indeed an LM9832 chip based scanner.
So... still looking for suggestions and ideas.
C.
On Sunday 28 July 2002 21:43, you wrote:
scanimage --list-devices returns the error that no scanners were identified. xscanimage just hangs there for a while (~2 minutes) and exits with a message that no scanners were identified. Kooka takes about 2 minutes to start up, and cannot find any scanners. xsane is the same... hangs for a while, and then reports back that there are no scanner devices.
So, anyone see what I have missed here? Why is this scanner just sitting there so smugly, refusing to startup?
C.
Hello Clalyton I am using SuSE 7.3 I have an epson 1650 scanner and had the same problem at the beginning. Type lsmod to see if your scanner module is listed there. if not The solution for me was to write /sbin/modprobe scanner in /etc/init.d.boot.local So that the usb module for the scanner should be loaded at every boot. Maybe it is the same for you. Good luck.
participants (3)
-
Clayton Cornell -
Frits J. Wüthrich -
paul ollion