plustek: USB-Code Update to 0.41_2


Previous by date: 21 Jan 2002 14:54:53 -0000 Re: USB-Code Update to 0.41_2, Jaeger, Gerhard
Next by date: 21 Jan 2002 14:54:53 -0000 Re: USB-Code Update to 0.41_2, Gene Heskett
Previous in thread: 21 Jan 2002 14:54:53 -0000 Re: USB-Code Update to 0.41_2, Jaeger, Gerhard
Next in thread: 21 Jan 2002 14:54:53 -0000 Re: USB-Code Update to 0.41_2, Gene Heskett

Subject: Re: USB-Code Update to 0.41_2
From: Gene Heskett ####@####.####
Date: 21 Jan 2002 14:54:53 -0000
Message-Id: <20020121145146921.AAA4024@mail.iolinc.net@there>

On Monday 21 January 2002 02:41 am, Jaeger, Gerhard wrote:
>On Sonntag, 20. Januar 2002 19:00, Gene Heskett wrote:
>[SNIP]
>
>> And a scanimage -L hangs up for about a minute, then returns
>> this message:
>> [epson] error in receive - status = 5
>> [epson] ident failed
>>
>> No scanners were identified. etc etc
>>
>> And the mouse was gone, died and went to mouse heaven I
>> suppose, anyway a reboot was required.
>>
>> Can we point to a specific item from that status = 5 ?
>
>NOPE!
>The error came from the Epson backend ([epson]) and not from the
>Plustek-backend!
>Make sure that your dll.conf contains only the plustek entry,
> then retry. I think that the Epson backend tries to open the
> device and does some stuff it shouldn't do...

Humm, now scanimage -L is a bust.
[root@gene root]# scanimage -L

No scanners were identified. If you were expecting something 
different,
check that the scanner is plugged in, turned on and detected by 
the
sane-find-scanner tool (if appropriate). Please read the 
documentation
-----------------------end of clip
Previously, sane-find-scanner had returned its results instantly, 
but now hangs for about 30 seconds before returning this:

[root@gene root]# sane-find-scanner
# Note that sane-find-scanner will find any scanner that is 
connected
# to a SCSI bus and some scanners that are connected to the 
Universal
# Serial Bus (USB) depending on your OS. It will even find 
scanners
# that are not supported at all by SANE. It won't find a scanner 
that
# is connected to a parallel or proprietary port.

sane-find-scanner: found USB scanner (vendor = 0x04b8, product = 
0x010f) at device /dev/usb/scanner
sane-find-scanner: found USB scanner (vendor = 0x04b8, product = 
0x010f) at device /dev/usb/scanner0
sane-find-scanner: found USB scanner (vendor = 0x04b8, product = 
0x010f) at device /dev/usbscanner
sane-find-scanner: found USB scanner (vendor = 0x04b8, product = 
0x010f) at device /dev/usbscanner0
---------------------end of clip

The 'scanner' module is loaded, but I've not added any options to 
the modules.conf file since the vendor/model codes are compiled 
into it.

Humm, lemme check the other files in /usr/local/etc/sane.d, brb.
plustek.conf had been overwritten by the install, unlike the 
dll.conf, and was pointing at /dev/whatever the parallel port is. 

I pointed it at /dev/usbscanner, and will try it again once all 
this is sent.

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
98.3+% setiathome rank, not too shabby for a hillbilly

Previous by date: 21 Jan 2002 14:54:53 -0000 Re: USB-Code Update to 0.41_2, Jaeger, Gerhard
Next by date: 21 Jan 2002 14:54:53 -0000 Re: USB-Code Update to 0.41_2, Gene Heskett
Previous in thread: 21 Jan 2002 14:54:53 -0000 Re: USB-Code Update to 0.41_2, Jaeger, Gerhard
Next in thread: 21 Jan 2002 14:54:53 -0000 Re: USB-Code Update to 0.41_2, Gene Heskett


Powered by ezmlm-browse 0.20.