Hi Henning
Thanks for your tips - I've successfully built & installed
sane-backends-1.06 and sane-frontends-1.06 as well as xsane-0.80 now.
Sadly I'm still getting weird stripes, but I found a previous discussion on
this and I've mailed the folk involved to see if they made any progress.
To answ
Hi Steven,
now the backend is talking to the scanner. But it is getting some
problems with the communication. Some new Linux kernels have a bug. Add
to your hp.conf-file below the /dev/scanner a line
option disable-scsi-request
Maybe this can solve the final problem.
--Peter
Steven Lembark wro
(cc'd to sane-devel)
Hi,
On Sun, Nov 11, 2001 at 12:56:28PM -0600, Steven Lembark wrote:
> Sorry about that, bad paste. /opt/sane.d -> /opt/sane/etc/sane.d
> and everything from /opt/sane/1.06 is soft linked up one level
> (makes it easier to change versions, just replace a few soft links).
I t
Hi,
On Sun, Nov 11, 2001 at 07:02:30PM +0100, steve sheriff wrote:
> Yes, I know. Take a look at my howto for this scanner. The lists purists hate
> it. It's very crude but it *always* works!
I don't think anyone hates additional documentation and user reports.
> www.arrakis.es/~fsanta/sane
AR
Hi.
Yes, I know. Take a look at my howto for this scanner. The lists purists hate
it. It's very crude but it *always* works!
www.arrakis.es/~fsanta/sane
Good luck, Steve.
On Saturday 10 November 2001 03:04, you wrote:
> AUGH!!! I can't take it anymore!
> I just upgrade my system and I can't ge
Hello
Following my previous mail to the list I received some info, which may be
"just what we want".
Those interested in participating in the development/testing of the avision
backend, so that it can use the scanners that are known to be manufactured by
avision, but are not supported by the
Hi,
> My configuration is the following one :
>
> - SuSE 7.2
> - Kernel 2.4.4 or 2.4.13
> - Sane 1.0.5
> - Xsane 0.80
You should upgrade to sane-1.0.6 or use the latest snapscan backend from
hpttp://sourceforge.net/projects/snapscan. It will determine automatically
if your scanner needs a firmwar
Hi,
in addition to Peter's comments:
On Sun, Nov 11, 2001 at 03:00:19AM -0600, Steven Lembark wrote:
> The Sane and HP FAQ's seem to imply that anything the finderizer
> can locate whould be found identically by scanimage --list-devices.
The only thing sane-find-scanner does is to send a SCSI in
--==2085129384==
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
-- Peter Kirchgessner
> Hi Steven,
>
> now the backend is talking to the scanner. But it is getting some
> problems with the communication. Som
-- Peter Kirchgessner
> now the backend is talking to the scanner. But it is getting some
> problems with the communication. Some new Linux kernels have a bug. Add
> to your hp.conf-file below the /dev/scanner a line
>
> option disable-scsi-request
>
> Maybe this can solve the final problem.
Fi
-- Henning Meier-Geinitz
> export SANE_CONFIG_DIR=/opt/sane/1.0.6/etc/sane.d/
[dll] add_backend: adding backend umax
[dll] add_backend: adding backend v4l
[dll] load: loading backend hp
[dll] load: couldn't find /opt/sane/1.0.6/libsane-hp.so.1 (No such file or
directory)
scanimage: open of de
Did a strings on the scanner binary, found "SANE_DEFAULT_DEVICE".
Tried it:
root@dizzy:bin # export
SANE_DEFAULT_DEVICE='hp:/dev/scsi/host2/bus0/target1/lun0/generic'
root@dizzy:bin # ./scanimage
[sanei_debug] Setting debug level of dll to 255.
[dll] sane_init: SANE dll backend v
Hi,
On Sat, Nov 10, 2001 at 11:25:01PM +, Michael Thomson wrote:
> 2) When I downloaded the sane-frontends and sane-backends version 1.06,
> I tried to compile the backends first, and get the following error:
>
> > make[1]: Entering directory `/home/michthom/sane-backends-1.0.6/tools'
>
Hi Steven,
please have a look if you have another hp.conf at /usr/local/etc/sane.d.
You can also try an
export SANE_DEBUG_HP=17
and run
scanimage -L
to see what happens to the hp-backend. Send the generated listing back
to me.
--Peter
Steven Lembark wrote:
>
> The finderizer locates the sc
The finderizer locates the scanner (an HP6100C) nicely enough,
scanimage -L doesn't. Same effect as me and su. Checking
"/dev/scanner" or "/dev/scsi/host2/bus0/target1/lun0/generic"
gives the same result (see below). The hp.config lists the
correct device, no help.
System is a heavily hacked RH-7.
15 matches
Mail list logo
