[sane-devel] scanner not recognised

[Karl Heinz Kremer]

I'm CC'ing my answer to the mailing list. Please do reply all, or reply 
list, or whatever the
function is called in your mailer the next time you answer. Thanks.

How many Sane installations do you have on your system? When you 
"upgraded" to 1.0.13, did you
do an RPM upgrade (rpm -U sane-*.rpm), or did you compile Sane from 
sources and installed it?

If it's the latter, you have to make sure that you remove the original 
Sane first. Otherwise
you can get exactly the symptoms you are describing.

Please remove the Sane version that came with Fedora.

If that's not the problem, edit the file dll.conf in your Sane config 
directory and make
sure that the line containing "epson" is not commented out (remove the 
'#' in front of
the line).

Karl Heinz


On Feb 27, 2004, at 7:14 PM, Paul Frisson wrote:

> OK, thank you for answering.
>
> When I log as root does not make any difference, I still got the 
> message "no
> device available" (at least it seems like that when I translate it from
> french).
>
> The command
>
> "export SANE_DEBUG_EPSON=128 xsane > /tmp/scan.log 2>&1"
>
> returns an empty scan.log file when I try to edit it in a text editor.
>
> I also just upgraded to sane 1.0.13, and have still the same 
> "no-device"
> result result.
>
> Paul Frisson
>
>
> On Saturday 28 February 2004 00:40, you wrote:
>> Fedora is very similar to RedHat 9, so this should not cause any
>> problems.
>> I cannot help you with the HP device, but I can probably help you to 
>> get
>> the EPSON scanner to work again.
>>
>> The most common problem for SCSI scanners is that the permissions on 
>> the
>> /dev/sg? device are not correct. An indication for this is that you 
>> can
>> scan as root, but not as normal user. If this is the case, just use 
>> the
>> chmod command to change the permissions of the file:
>>
>> chmod 666 /dev/sg0
>>
>> Replace /dev/sg0 with the device you are using. I fyou don't have any
>> other
>> SCSI devices, it will be /dev/sg0.
>>
>> If this is not the reason, please do the following in a terminal 
>> window:
>>
>> export SANE_DEBUG_EPSON=128
>> xsane > /tmp/scan.log 2>&1
>>
>> This will log all communication between the scanner and the backend,
>> plus
>> some more debug information about the state of the backend. Please 
>> email
>> this file to me.
>>
>> Karl Heinz
>>
>> On Feb 27, 2004, at 10:24 AM, Paul Frisson wrote: