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)