Hi,
> Here goes, with first sane-find-scanner and then with scanimage -L,
> both
> as root:
The interesting information is after the firmware download, which
doesn't happen with scanimage -L. You can send the (compressed) log
of a regular "scanimage" command to me in a private mail.
> You
El s?b, 25-03-2006 a las 11:58, Oliver Schwartz escribi?:
> The problem
> you're reporting has been experienced before by other people (hence
> my remark on that scanner on the snapscan page). I don't know yet how
> to solve this problem - maybe the log from the USB layer can shed
> some more l
Hi,
> The above appears to agree with the information on the
> sane-snapscan page, which gives the USB ID for the Acer/Benq 5300
> as "0x04a5, 0x20fe" and identifies the firmware to use is
> u254v042.bin.
Yes, that should be correct.
> Of course, the firmware file I have might be corrupt. I down
El dom, 19-03-2006 a las 11:55, Oliver Schwartz escribi?:
> The scanner stops responding after the firmware has been sent to the
> scanner. The transfer itself seems to be fine. It's possible that
> neither of the two firmware files is the correct one for your
> scanner. What's the USB ID of you
Hi,
> Once that was done, "scanimage -L" finds an "Acer FlatbedScanner22
> flatbed scanner", which corresponds to an Benq 4300 scanner. (I was
> expecting FlatbedScanner24, which corresponds to my scanner.)
The scanner should report FlatbedScanner24 after a successful firmware
download. Before
I need help getting a Benq 5300U scanner working. Here is what I have
done and what the results have been:
Googling shows me that the scanner is supported by the snapscan backend,
included in sane-backends, and that I need sane-backends-1.0.16 or
newer. I compiled sane-backends-1.0.17 from source,
