[sane-devel] Epson GT6000 parport scanner on RH Linux

[Eric Mills]

Hi Harald

Thanks for the hints - only had not commented out lines in 
dll.conf. Changing this does change symptoms slightly. The debug 
output now has:

[epson] ADF detected
[epson] ADF is enabled
[epson] adf tlx 0.000000 tly 0.000000 brx 88.307327 bry 0.677322 
[mm]

This scanner does not have an ADF! Don't think the GT6000 can 
support one... The bry entry now is not zero and so I don't get 
an invalid parameter error when requesting a scan, however 1mm 
max scan height is not very useful!

Is it possibly to override the autodetect of the ADF as the main 
  size parameters seems to be being downloaded correctly?

Scanner did show E-C but seems to be ready & 100 (normal) after 
a scan request now.

Thanks & Best Regards,
Eric


harald wrote:
> Hello Eric,
> 
> i have the same scanner working on Suse Linux 7.3, 8.0, 8.2, Mandrake 8.2, 
> 9.0, 9.1. [epson] ADF detected
[epson] ADF is enabled
[epson] adf tlx 0.000000 tly 0.000000 brx 88.307327 bry 0.677322 
[mm]

> I should work with Red Hat, too. The only thing you have to do is "switch off" 
> (comment with #) all other backends in dll.conf and enable parport in 
> epson.conf (pio 0x378). Comment all other settings in epson.conf. I tried it 
> with several older sane Versions, all i tried worked. I get always a E-C 
> Message in Scanners panel. But after I am starting any frontend, the "ready" 
> light is on and the scanner works fine. 
> Maybe commenting out entrys in dll.conf will solve your error.
> 
> Please let me know if it works.
> 
> Best Regards to down under, Harald. 
>  
> Am Sonntag, 18. Mai 2003 12:54 schrieb Eric Mills:
> 
>>Hi,
>>
>>For some time now I have been trying to get my GT6000 working locally on
>>RH Linux (7.3, port 0x378). With both the standard 1.0.7 sane provided
>>and the latest 1.0.11 backends with .10 frontends, I get the following
>>problems:
>>
>>1. Without debugging turned on the scanner appears to be reset upon
>>entering any front end and then the backend goes into an infinite loop.
>>Scanner puts up E-1 in the window after 30 seconds.
>>
>>2. With DEBUG=128 initialisation passes, but the backend seems to decide
>>the scanner has an ADF with looney size parameters (0 length) which
>>cases an invalid parameter error on the first scan request.
>>
>>Does anyone have one of these old parport scanners working in the same
>>configuration? Karl does not have access for any suggestions.
>>
>>Thanks,
>>Eric Mills
>>
>>_______________________________________________
>>Sane-devel mailing list
>>Sane-devel at www.mostang.com
>>http://www.mostang.com/mailman/listinfo/sane-devel
> 
>