[sane-devel] Avision: Scanner Light Does Not Move--Garbage in Preview Window

Dan McGhee farmerdan@i-rule.net
Tue, 15 Mar 2005 05:33:17 -0600


Dan McGhee wrote:

> Dan McGhee wrote:
>
>> I did all of this on 20050306.  I have a HP Scanjet 5370C (Avision).
>>
>> Compiled and installed libusb-0.1.10a, sane-backends-1.0.15 and 
>> sane-frontends-1.0.13.  All were release versions.  For sane-backends 
>> I used avision.c, avision.h, avision.conf, sanei_usb.c and 
>> sanei_usb.h from http://svn.exactcode.de/sane-avision/trunk/.  In 
>> everything I used <./configure --prefix=/usr --sysconfdir=/etc.  
>> (Except maybe I didn't set sysconfdir for libusb--could this be the 
>> problem?)
>
>
> Recompiled everything and made sure that directories were what I wanted.
>
>>
>> In xscanimage and xsane, I get "garbage" in the preview window when I 
>> select "Acquire Preview."  I also noticed that in all cases the 
>> scanner light comes on, travels a very small distance and then turns 
>> off.  The scanner sounds normal.
>
>
> I checked out the cvs version of sane.  The scanner now scans, but for 
> a preview scan I get vertical colored lines in a black and white 
> document  When I scan, the image is rotated 45 degrees clockwise and 
> the colored lines are still there--also rotated.  I can try to "hack" 
> on the avision.c file--I'm not really very good at this--to see if I 
> can find the differences between the cvs and the latest build.  Pointers?
>
Results of troubleshooting so far:
1.  backends-1.0.15 as released--vertical color bars in preview and 
image rotated 45 degrees on scan

2.  backends-1.0.15 with latest posted build of avision--scanner bar 
does not move

3.  backends-1.0.14 will not find scanner (libusb vs hpusbscsi?)

4.  scanner works with vuescan

I've researched the documentation, mailing lists and forums and have 
tried every trouble shooting technique that I think applies.  The 
results are the same.  I've gone as far as I can with my current 
knowlege level.  I am in need of help.

I would be more than happy to post a "debug" log, or sections of it, if 
anyone would ask for it.

Thanks,

Dan