Hi Stef,
On Monday 03 June 2013 21:13:13 Stef wrote:
[...]
> when compiled with libusb-1.0, sane-find-scanner didn't any of the
> usb chip probes. I have added back this feature, but limited to the
> genesys ASICs. I plan to add GT68xx and rts8891 tests soon since I have
> the hardware to
Hello,
when compiled with libusb-1.0, sane-find-scanner didn't any of the
usb chip probes. I have added back this feature, but limited to the
genesys ASICs. I plan to add GT68xx and rts8891 tests soon since I have
the hardware to test it on. Adding other tests is only a matter of
con
Hi Max,
Please read and follow the build and installation description in
README.linux (is part of the source code or read here:
http://www.sane-project.org/README.linux), especially the stuff around
libsane.so.1 and symbolic links.
Don't remove the sane packages from debian. You need them e.g. to
Hi Rolf -
Thanks for the reply. It seems I had to remove the sane packages installed
by debian and re-build. However, I can't seem to figure out how to get a
front end installed without wiping out the backend version. Even if I
install a package, the try to re-build over the sane-backends upgra
Hi Max,
your scanimage uses the 1.0.22 backend. It must be >=1.0.23.
Please read README.linux and follow the installation desription.
Cheers,
Rolf
Am 02.12.2012 22:54, schrieb Max Resnick:
> Hi Everyone -
>
> -Scanner Model is CanoScane 9000F - and is supported via
> Pixma. http://www.sane-pro
Hi Everyone -
-Scanner Model is CanoScane 9000F - and is supported via Pixma.
http://www.sane-project.org/man/sane-pixma.5.html
-I'm running Debian Wheezy 64 Bit.
-I've also tried on Ubuntu 12.04 64 Bit.
-Scanner runs in windows just fine
-libusb-dev is installed via apt
I've ran with the distros
Le vendredi 8 juillet 2011 18:39:20 yohann at rebattu.fr, vous avez ?crit :
> > Le jeudi 7 juillet 2011 22:56:18 yohann at rebattu.fr, vous avez ?crit :
> >> Hello all,
> >> first thank you, you did great work with sane.
> >>
> >> then i have a litle problem to make my scanner (lexmark X1150) work
> Le jeudi 7 juillet 2011 22:56:18 yohann at rebattu.fr, vous avez ?crit :
>> Hello all,
>> first thank you, you did great work with sane.
>>
>> then i have a litle problem to make my scanner (lexmark X1150) works
>> with
>> sane, and more disturbing i can't figure out where things goes wrong.
>>
>
Le jeudi 7 juillet 2011 22:56:18 yohann at rebattu.fr, vous avez ?crit :
> Hello all,
> first thank you, you did great work with sane.
>
> then i have a litle problem to make my scanner (lexmark X1150) works with
> sane, and more disturbing i can't figure out where things goes wrong.
>
> first as
Hello all,
first thank you, you did great work with sane.
then i have a litle problem to make my scanner (lexmark X1150) works with
sane, and more disturbing i can't figure out where things goes wrong.
first as said in documentation i run sane-find-scanner:
found USB scanner (vendor=0x043d, produ
Pete Lancashire writes:
> as root
>
> # echo 262144 > /proc/scsi/sg/def_reserved_size
>
> # cat /proc/scsi/sg/def_reserved_size
> 262144
>
> as non-root user
>
> [root at localhost ram0]# su - pete
> [pete at localhost ~]$ cat /proc/scsi/sg/def_reserved_size
> 262144
> $ sane-find-scanner -q
> fo
as root
# echo 262144 > /proc/scsi/sg/def_reserved_size
# cat /proc/scsi/sg/def_reserved_size
262144
as non-root user
[root at localhost ram0]# su - pete
[pete at localhost ~]$ cat /proc/scsi/sg/def_reserved_size
262144
$ sane-find-scanner -q
found SCSI processor "EPSON SCANNER GT-3 1.53" a
On 20/05/07, Julien BLACHE wrote:
> "Hugh McMaster" wrote:
>
> > This is the best explanation, since libusb can communicate with the
> > mouse, so it would get displayed wouldn't it? Although I thought
> > sane-find-scanner was programmed to display scanners only?
>
> There's no way to reliably id
Hi Gerald,
Thankyou for your reply.
On 20/05/07, Gerald Murray wrote:
> Quoting Hugh McMaster:
>
> > Hi everyone,
> >
> > I just ran the sane-find-scanner command on my computer, and I noticed
> > that in the verbose output, the programme detected my USB mouse.
> >
> > I assume that is would be t
Hi everyone,
I just ran the sane-find-scanner command on my computer, and I noticed
that in the verbose output, the programme detected my USB mouse.
I assume that is would be the behaviour of libusb, since it detects
most USB devices. Is that correct? Libusb detected my scanner (Canon
3000F) as
"Hugh McMaster" wrote:
> This is the best explanation, since libusb can communicate with the
> mouse, so it would get displayed wouldn't it? Although I thought
> sane-find-scanner was programmed to display scanners only?
There's no way to reliably identify a USB scanner; sane-find-scanner
uses
Quoting Hugh McMaster :
> Hi everyone,
>
> I just ran the sane-find-scanner command on my computer, and I noticed
> that in the verbose output, the programme detected my USB mouse.
>
> I assume that is would be the behaviour of libusb, since it detects
> most USB devices. Is that correct? Libusb
Hello,
> Attached devices:
> Host: scsi0 Channel: 00 Id: 03 Lun: 00
> Vendor: UMAX Model: Astra 1200S Rev: V2.9
> Type: Scanner ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 06 Lun: 00
> Vendor: MICROTEK Model: ScanMaker II Rev: 5.61
> Type:
Hello
On Aug 9 00:59 Ulrich Deiters wrote (shortened):
> The undetected scanner is a Canoscan 2710S, an SCSI slide scanner.
First of all have a look at
https://bugzilla.novell.com/show_bug.cgi?id=177492
To get (a lot of) debug messages use
---
as root-
SANE_DEBUG_CANON=255 scanimage -L
do you see the canon backend produce any messages?
allan
On Wed, 9 Aug 2006, Ulrich Deiters wrote:
> The undetected scanner is a Canoscan 2710S, an SCSI slide scanner. It
> used to function properly with my previous computer (HP-UX). It does
> not ma
The undetected scanner is a Canoscan 2710S, an SCSI slide scanner. It
used to function properly with my previous computer (HP-UX). It does
not matter whether I run SANE as user or superuser.
Regards,
Ulrich Deiters
--
Prof. Dr. Ulrich K. Deiters __
Insti
this is because there is no sane backend being loaded which supports the
scanner. what scanner is it?
allan
On Tue, 8 Aug 2006, Ulrich Deiters wrote:
> Much more interesting than this discussion why sane-find-scanner works
> would be a hint what can be done if scanimage -L does not detect
> th
Much more interesting than this discussion why sane-find-scanner works
would be a hint what can be done if scanimage -L does not detect
the scanner. I have this problem under Linux with an SCSI scanner
(i.e., sane-find-scanner sees it, but scanimage not).
Regards,
Ulrich Deiters
--
Prof. Dr. Ul
Johannes Meixner wrote:
> Hello,
>
> On Aug 8 08:04 m. allan noah wrote (shortened):
>>unlike scsi, there is no usb class for scanners
>
> I thought there is even no SCSI class for scanners.
> At least my SCSI scanner HP ScanJet 6200C shows up as "Processor":
> ---
On Tue, 8 Aug 2006, Johannes Meixner wrote:
>
> Hello,
>
> On Aug 8 08:04 m. allan noah wrote (shortened):
>> unlike scsi, there is no usb class for scanners
>
> I thought there is even no SCSI class for scanners.
> At least my SCSI scanner HP ScanJet 6200C shows up as "Processor":
> -
On Tue, Aug 08, 2006 at 06:36:10PM +0530, Parag N() wrote:
> >On Aug 8 08:04 m. allan noah wrote (shortened):
> >> unlike scsi, there is no usb class for scanners
> >
> >I thought there is even no SCSI class for scanners.
> >At least my SCSI scanner HP ScanJet 6200C shows up as "Process
Hi,
On 8/8/06, Johannes Meixner wrote:
>
> Hello,
>
> On Aug 8 08:04 m. allan noah wrote (shortened):
> > unlike scsi, there is no usb class for scanners
>
> I thought there is even no SCSI class for scanners.
> At least my SCSI scanner HP ScanJet 6200C shows up as "Processor":
> -
Hello,
On Aug 8 08:04 m. allan noah wrote (shortened):
> unlike scsi, there is no usb class for scanners
I thought there is even no SCSI class for scanners.
At least my SCSI scanner HP ScanJet 6200C shows up as "Processor":
# l
sane-find-scanner is a tool for a very specific task, locating possible
scanners connected to the system, even if they are not supported by sane.
unlike scsi, there is no usb class for scanners, so sane has no generic
way of determining if a usb id is a scanner or not.
that is why we also recom
d Apr 5 20:38:20 2006
Subject: [sane-devel] sane-find-scanner and scanimage produces wrong /
mistakable output
In-Reply-To: <200604051908.19945.mar...@pibbs.org>
References: <200604051908.19945.mar...@pibbs.org>
Message-ID: <4434284d.3090...@uniting.com.au>
Martin Seek
Hi,
On Sun, Sep 25, 2005 at 11:55:56PM +0200, Enrico Weigelt wrote:
> Seems suitable for me.
> Is it in the next release ?
sane-find-scanner in CVS now prints the following if no scanners are
found (and libusb is not available):
hmg1:~# sane-find-scanner
# sane-find-scanner will now attempt
* Henning Meier-Geinitz schrieb:
> What we could add is a link to the sane-usb manpage:
>
> Instead of:
>
> # No USB scanners found. If you expected something different, make sure that
> # you have loaded a driver for your USB host controller and have installed a
> # kernel scanner modul
Hi,
On Mon, Aug 01, 2005 at 10:49:37AM +0200, Enrico Weigelt wrote:
> after some time of searching why my lide20 wasn't working I've
> recognized that /proc/bus/usb wasn't mounted.
> It would be great if this hint could be added sane-find-scanner's
> notice output.
>
> I'll check out the latest
On Thursday 30 September 2004 18:56, Lloyd Sumpter wrote:
> Henning Meier-Geinitz wrote:
> > Hi,
> >
> > On Tue, Sep 28, 2004 at 01:22:01PM -0700, Lloyd Sumpter wrote:
> >>[sanei_debug] Setting debug level of sanei_usb to 255.
> >>[sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner0: No such
Henning Meier-Geinitz wrote:
> Hi,
>
> On Tue, Sep 28, 2004 at 01:22:01PM -0700, Lloyd Sumpter wrote:
>
>>[sanei_debug] Setting debug level of sanei_usb to 255.
>>[sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner0: No such device
>>[sanei_usb] sanei_usb_init: found 0 devices
>
>
> Oh.
Hi,
On Tue, Sep 28, 2004 at 01:22:01PM -0700, Lloyd Sumpter wrote:
> [sanei_debug] Setting debug level of sanei_usb to 255.
> [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner0: No such device
> [sanei_usb] sanei_usb_init: found 0 devices
Oh. That means that SANE isn't built with libusb
Gerhard Jaeger wrote:
> Hi,
>
> On Thursday 23 September 2004 18:42, Lloyd Sumpter wrote:
>
>>Hi,
>>
>>My Canon Lide20 (USB) was working on Mandrake 9.0 (sane 1.0.11, iirc and
>>Linux 2.4.x) using scanner.o. I upgraded to Mandrake 10.0 (sane 1.0.13,
>>Linux 2.6.3) and I found scanner.o has been
Hi,
On Thursday 23 September 2004 18:42, Lloyd Sumpter wrote:
> Hi,
>
> My Canon Lide20 (USB) was working on Mandrake 9.0 (sane 1.0.11, iirc and
> Linux 2.4.x) using scanner.o. I upgraded to Mandrake 10.0 (sane 1.0.13,
> Linux 2.6.3) and I found scanner.o has been discontinued, and I have to
> use
On Thu, 2004-09-23 at 16:42, Lloyd Sumpter wrote:
> Hi,
>
> My Canon Lide20 (USB) was working on Mandrake 9.0 (sane 1.0.11, iirc and
> Linux 2.4.x) using scanner.o. I upgraded to Mandrake 10.0 (sane 1.0.13,
> Linux 2.6.3) and I found scanner.o has been discontinued, and I have to
> use libusb.
gerard klaver wrote:
> On Thu, 2004-09-23 at 16:42, Lloyd Sumpter wrote:
>
>>Hi,
>>
>>My Canon Lide20 (USB) was working on Mandrake 9.0 (sane 1.0.11, iirc and
>>Linux 2.4.x) using scanner.o. I upgraded to Mandrake 10.0 (sane 1.0.13,
>>Linux 2.6.3) and I found scanner.o has been discontinued, an
Hi,
My Canon Lide20 (USB) was working on Mandrake 9.0 (sane 1.0.11, iirc and
Linux 2.4.x) using scanner.o. I upgraded to Mandrake 10.0 (sane 1.0.13,
Linux 2.6.3) and I found scanner.o has been discontinued, and I have to
use libusb. Sane tells me the scanner is supported with plustek backend.
Hi,
Eddy De Greef wrote:
> It looks good.
> I'm all for including it (but I may be a bit prejudiced :-).
It's included since yesterday (just before feature freeze :-)
kind regards
-- jochen
On 06-04-04 20:24:53 Jochen Eisinger wrote:
> I just wrote a short patch to sane-find-scanner which detects mustek
> parallel port devices. With sanei_pa4s2 it's possible to get a list
> of possible ports. All the patch does is trying to open those ports
> using the sanei_pa4s2 - the sanei_pa4s
This is a multi-part message in MIME format.
--070004080404080406040306
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi,
I just wrote a short patch to sane-find-scanner which detects mustek
parallel port devices. With sanei_pa4s2 it's possible to get a li
Hi,
I've just added support for detecting USB chipsets in
sane-find-scanner in CVS. If you don't have access to CVS, a snapshot
of sane-backends is here: http://www.meier-geinitz.de/sane/snapshots/
If the chipset is detected, the output looks like this:
found USB scanner (vendor=0x05d8, product=
-Oprindelig meddelelse-
Fra: Michael Rasile [mailto:kee...@neo.rr.com]
Sendt: 28. juni 2003 19:01
Til: Christoffer Holm Kjølbæk
Emne: Re: [sane-devel] sane-find-scanner can find my scanner, but Xsane
can't?
Hey Mike
Thanks for you answer
I think the problem is the old backend, that
Hi,
On Sat, Jun 28, 2003 at 03:23:08PM +0200, Christoffer Holm Kjølbæk wrote:
> I have a Canon LiDe30, wich shuold be supported by sane
It is, but the comment says "Poor color picture quality".
> And if I run sane-find-scanner, it finds the scanner at /dev/usb/scanner0
Ok, so it was found by th
Hey
I have a Canon LiDe30, wich shuold be supported by sane
And if I run sane-find-scanner, it finds the scanner at /dev/usb/scanner0
But, Xsane says, that there is no devices available, why?
Kind regards - and thanks in adance
Christoffer Kjølbæk
On Fri, 2003-03-21 at 11:08, Jaeger, Gerhard wrote:
> Hi,
>
> On Freitag, 21. März 2003 10:39, Henning Meier-Geinitz wrote:
> > Hi,
> >
> > Please reply to the list, not to me personally. There are developers
> > that know much more about the plustek backend than me.
>
> really ;-)
>
> [SNIPSNAP
Hi,
On Sat, Mar 22, 2003 at 03:53:30PM +0200, Marius Andreiana wrote:
> I'm trying to setup a Plustek OpticPro 1248U ( on USB ).
> It shows up in /proc/bus/usb/devices ( with product id = 400, not 401 as
> it was in gt68.conf, changed that )
That's not enough. You need at least gt68xx backend ve
Hi
I'm trying to setup a Plustek OpticPro 1248U ( on USB ).
It shows up in /proc/bus/usb/devices ( with product id = 400, not 401 as
it was in gt68.conf, changed that )
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P
Hi,
On Freitag, 21. März 2003 10:39, Henning Meier-Geinitz wrote:
> Hi,
>
> Please reply to the list, not to me personally. There are developers
> that know much more about the plustek backend than me.
really ;-)
[SNIPSNAP]
> > sane-backends identified as 1.0.8
>
> May be too old. But that's a d
Hi,
Please reply to the list, not to me personally. There are developers
that know much more about the plustek backend than me.
On Thu, Mar 20, 2003 at 08:02:27PM -0600, Charles Mims wrote:
> I am sure you are correct about this. I just was trying to say that it
> is supposed to use the plustek
Hi,
On Wed, Mar 19, 2003 at 04:46:06PM -0600, Charles Mims wrote:
> I am try to use a Canon Lide30 scanner(USB) with Linux RH8.0.
> Evidently a rebranded Plustek
Really? I think it just uses the lm983x chip as some Plustek USB
scanners do.
> I then loaded the scanner module and then ran 'sane-
I am try to use a Canon Lide30 scanner(USB) with Linux RH8.0.
Evidently a rebranded Plustek
I first checked with 'lsusb' and the scanner is recognized.
I then loaded the scanner module and then ran 'sane-find-scanner and it
reported the scanner at /dev/usb/scanner0. However when I started Xsan
--oNLI4EWr1RPQuPCf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, May 27, 2002 at 02:13:10PM -0500, Joel Uckelman wrote:
> Thanks! That did the trick. What does reinstalling the sane-backends=20
> package do that fixes th
Thus spake Tim Waugh:
>
> On Sun, May 26, 2002 at 09:09:45PM -0500, Joel Uckelman wrote:
>
> > I upgraded to RedHat 7.3 yesterday, which apparently has caused my
> > Epson 610 to stop working.
>
> This is a known issue that will be addressed shortly. In the mean
> time, you should be able to wor
--mYCpIKhGyMATD0i+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Your /proc/bus/usb/devices output is incomplete: You've left out
a few lines that show which driver did recognize your scanner. You
need the first "I:" line after t
--b1ERR0FXR0PvNIRE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Sun, May 26, 2002 at 09:09:45PM -0500, Joel Uckelman wrote:
> I upgraded to RedHat 7.3 yesterday, which apparently has caused my
> Epson 610 to stop working.
This is a known issue that will be addressed
> crw-r--r--1 root root 180, 48 Apr 11
> 09:25 /dev/usb/scanner0
Shouldn't you have write access to the device ?
___
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com
Thus spake Sylvain Petreolle:
>
> > crw-r--r--1 root root 180, 48 Apr 11
> > 09:25 /dev/usb/scanner0
>
> Shouldn't you have write access to the device ?
Yes, but since I was screwing with it as root, I did have write access. I'd
twiddled the permissions a bit in the process---it wa
I upgraded to RedHat 7.3 yesterday, which apparently has caused my Epson
610 to stop working. Now, sane-find-scanner detects it:
sane-find-scanner: found USB scanner (vendor = 0x04b8, product = 0x0103) at
device /dev/usb/scanner0
And it shows up in /proc/bus/usb/devices:
C:* #Ifs= 1 Cfg#= 1 At
Hi,
> the directory /usr/lib/sane had contained lots of links to 1.0.5
> files. but the 1.0.5 files did not exists, since the 1.0.7 files did
> exist, i removed the invalid symbolic links and replaced them with
> valid 1.0.7 links.
Normally the Redhat package manager should take care of this
did you check the "scanner" module is loaded ?
try to run 'lsmod' to see if it's present.
if not, launch 'modprobe scanner' and report if it
scans. hotplug should have loaded it when you connect
the scanner otherwise.
--- Jim Newton a écrit : > hi
wolfgang, i was indeed able to get the scanner
>
Sylvain Petreolle schrieb:
>
> I 've only these two lines in my snapscan.conf :
> (I've not updated the file for months though I have
> the last CVS code)
>
> /dev/usb/scanner0
> firmware /mnt/hda/windows/system/snape20.bin
>
For me I also have a similar snapscan.conf entry like above.
What kern
hi wolfgang, i was indeed able to get the scanner working yesterday.
although it no longer works today. In the directory /usr/lib/sane
had contained lots of links to 1.0.5 files. but the 1.0.5 files did
not exists, since the 1.0.7 files did exist, i removed the invalid
symbolic links and replace
I 've only these two lines in my snapscan.conf :
(I've not updated the file for months though I have
the last CVS code)
/dev/usb/scanner0
firmware /mnt/hda/windows/system/snape20.bin
--- Jim Newton a écrit : > do i
need to be using /etc/sane.d or
> /usr/local/etc/sane.d
>
> in response to you
and
> for sane, but i have not
> > found an explanation of what it is that scanimage
> needs in order to find
> > a scanner. aparently it needs something more than
> sane-find-scanner
> > needs.
> >
> > -jim
> >
> > > Date: Thu, 9 May 2002 19:3
on of what it is that scanimage needs in order to find
> a scanner. aparently it needs something more than sane-find-scanner
> needs.
>
> -jim
>
> > Date: Thu, 9 May 2002 19:33:50 +0200
> > From: Henning Meier-Geinitz
> > To: sane-de...@mostang.com
> > Subje
Hi,
On Thu, May 09, 2002 at 04:05:44PM +0200, Jim Newton wrote:
> hi, i've installed all the lastest sane rpms under redhat 7.2.
> when i run sane-find-scanner i get promising results.
If you read the text sane-find-scanner prints you will find out that
this just means that your scanner was detec
hi, i've installed all the lastest sane rpms under redhat 7.2.
when i run sane-find-scanner i get promising results.
but scanimage cannot find any SANE devices. Any ideas of what
might be wrong, or what i can try, or how i can get more debugging
information?
-jim
[jimka@localhost sane-backend
On Tue, 07 May 2002, Douglas Gilbert wrote:
> Carsten Neumann wrote:
> > On Mon, 06 May 2002, Douglas Gilbert wrote:
> >
> >>Johan,
> >>In your kernel config (assuming you have built that kernel)
> >>turn off CONFIG_SCSI_MULTI_LUN . Some SCSI scanners don't
> >>react properly to being probed for l
A big thanks to both Ray Curtis and Carsten Neumann.
I recompiled the kernel with the MULTI_LUN off and that has done the trick.
The scanner now works beautifully, and is about 20% faster than under windows
using the Microtek Twain Driver, no lockups and the colour output is fine
despite readin
Sorry, did forget to say what the problem is with this setup.
Currently whenever I try to scan , whether from the comand line or from
xscanimage or using the KDE3 scan utility I hear the scanner move for a
couple of seconds then I get a total system freeze , no coredump or any other
messages , j
Carsten Neumann wrote:
> On Mon, 06 May 2002, Douglas Gilbert wrote:
>
>>Johan,
>>In your kernel config (assuming you have built that kernel)
>>turn off CONFIG_SCSI_MULTI_LUN . Some SCSI scanners don't
>>react properly to being probed for logical unit numbers (luns).
>>They should only respond to
On Monday 06 May 2002 10:45 am, Carsten Neumann wrote:
>On Mon, 06 May 2002, Douglas Gilbert wrote:
>> Johan,
>> In your kernel config (assuming you have built that kernel)
>> turn off CONFIG_SCSI_MULTI_LUN . Some SCSI scanners don't
>> react properly to being probed for logical unit numbers
>> (lu
> I think from looking at the listing below it is pretty obvious that
> the scsi card is detecting muliple scanners, at ID 1 Lun 00-07.
agreed
> Not being familiar with this scsi card I can't really help much
> except the suggest moving the ID from 1 to maybe 4 or 5. The lower
This won't do much
On Mon, 06 May 2002, Johan Wehtje wrote:
> Sorry, did forget to say what the problem is with this setup.
> Currently whenever I try to scan , whether from the comand line or from
> xscanimage or using the KDE3 scan utility I hear the scanner move for a
> couple of seconds then I get a total syste
On Mon, 06 May 2002, Douglas Gilbert wrote:
> Johan,
> In your kernel config (assuming you have built that kernel)
> turn off CONFIG_SCSI_MULTI_LUN . Some SCSI scanners don't
> react properly to being probed for logical unit numbers (luns).
> They should only respond to lun==0 but they respond to a
On Mon, May 06, 2002 at 10:05:29PM +1200, V K wrote:
> > I think from looking at the listing below it is pretty obvious that
> > the scsi card is detecting muliple scanners, at ID 1 Lun 00-07.
>
> agreed
>
> > Not being familiar with this scsi card I can't really help much
> > except the suggest
have read the docs as well as the SCSI 2.4 how to but am still none the
wiser as to why I get the following output from sane-find-scanner
===
sane-find-scanner: found SCSI scanner " Scanner 1.40" at device /dev/scanner
sane-find-scanner: found SCSI scanner
> "jw" == Johan Wehtje writes:
jw> Sorry, did forget to say what the problem is with this setup.
jw> Currently whenever I try to scan , whether from the comand line or from
jw> xscanimage or using the KDE3 scan utility I hear the scanner move for a
jw> couple of seconds then
Johan Wehtje wrote:
> have read the docs as well as the SCSI 2.4 how to but am still none the
> wiser as to why I get the following output from sane-find-scanner
> ===
> sane-find-scanner: found SCSI scanner " Scanner 1.40" at device /dev/scanner
> sane-fin
Hi, Johan,
you've missed to tell what your problems actually are!
I don't see any problem why you can't use your scanner.
But you haven't told that you cannot use it.
What are the errors you get, if there are any?
Carsten
On Mon, 06 May 2002, Johan Wehtje wrote:
> have read the docs as
> "cn" == Carsten Neumann writes:
cn> Hi, Johan,
cn> you've missed to tell what your problems actually are!
cn> I don't see any problem why you can't use your scanner.
cn> But you haven't told that you cannot use it.
cn> What are the errors you get, if there are any?
I have the following problem with an UMAX SuperVista S12 scanner under
Slackware 8. I used to have this scanner running previously with
installations of LFS and SuSE 7.2 on this same box. sane-find-scanner sees
the scanner perfectly on /dev/sg0 and /dev/sga but other programs such as
xsane and scan
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,
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 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.
Yves Duret wrote:
>
> s...@michael.mailshell.com writes:
>
> > I have a Cannon FS2710:
> >
> > [root@corwin@mir scsi]# cat /proc/scsi/scsi
> > Attached devices:
> > Host: scsi0 Channel: 00 Id: 02 Lun: 00
> > Vendor: CANONModel: IX-27025ERev: 1.13
> > Type: Scanner
s...@michael.mailshell.com writes:
> I have a Cannon FS2710:
>
> [root@corwin@mir scsi]# cat /proc/scsi/scsi
> Attached devices:
> Host: scsi0 Channel: 00 Id: 02 Lun: 00
> Vendor: CANONModel: IX-27025ERev: 1.13
> Type: Scanner ANSI SCSI revision: 02
> Ho
I have a Cannon FS2710:
[root@corwin@mir scsi]# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 02 Lun: 00
Vendor: CANONModel: IX-27025ERev: 1.13
Type: Scanner ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: RICOH
98 matches
Mail list logo
