Lutz wrote:
> now the scanner is seen by scanimage -L -
> but it does not work - if I continue with Lamp error, I finally end up with a
> command sequence error.
> ---
> and her comes the not so nice part
> ---
> [canon] sense cate
Am Donnerstag, 17. August 2006 15:29 schrieb abel deuring:
> Lutz wrote:
> > Am Mittwoch, 16. August 2006 18:58 schrieb abel deuring:
(...)
> The problem is that this error occurs
> quite early during the setup of the device structures. Perhaps you
> can simply comment out this call of TEST UNIT RE
Lutz wrote:
> Am Mittwoch, 16. August 2006 18:58 schrieb abel deuring:
>>Lutz wrote:
>>>to me, it looks like that the (working) Epson scanner gives much more
>>>info than the canon does.
>>right: the Epson seems to be OK, while something is broken with the
>>FS2700, see below.
>>
>>>I already tried
I did test runs with the new canon.conf with my 2710F and everything
worked OK. I suspect there is a hardware error that causes the
sense_handler to take action. Perhaps it is a minor problem that
can be ignored?
Regards,
Ulrich Deiters
--
Prof. Dr. Ulrich K. Deiters __
Am Mittwoch, 16. August 2006 18:58 schrieb abel deuring:
> Lutz wrote:
> > to me, it looks like that the (working) Epson scanner gives much more
> > info than the canon does.
>
> right: the Epson seems to be OK, while something is broken with the
> FS2700, see below.
>
> > I already tried to debug
Am Dienstag, 15. August 2006 14:50 schrieb Johannes Meixner:
> Hello,
>
> On Aug 15 00:59 Ulrich Deiters wrote (shortened):
> > I have the same problem since I switched to Linux. Now I made sure
> > that canon.conf contains /dev/sg0 and /dev/scanner
> > AND I created a symbolic link: ln -s /dev/sg0
On Tue, 15 Aug 2006, Johannes Meixner wrote:
>
> Hello,
>
> On Aug 15 00:59 Ulrich Deiters wrote (shortened):
>> I have the same problem since I switched to Linux. Now I made sure
>> that canon.conf contains /dev/sg0 and /dev/scanner
>> AND I created a symbolic link: ln -s /dev/sg0 /dev/scanner.
>
Hello,
On Aug 15 00:59 Ulrich Deiters wrote (shortened):
> I have the same problem since I switched to Linux. Now I made sure
> that canon.conf contains /dev/sg0 and /dev/scanner
> AND I created a symbolic link: ln -s /dev/sg0 /dev/scanner.
> Now "scanimage -L" sees my Canon scanner.
Does this m
I have the same problem since I switched to Linux. Now I made sure
that canon.conf contains /dev/sg0 and /dev/scanner
AND I created a symbolic link: ln -s /dev/sg0 /dev/scanner.
Now "scanimage -L" sees my Canon scanner.
Regards,
Ulrich Deiters
--
Prof. Dr. Ulrich K. Deiters ___
John Bird wrote:
> Hi,
> Thanks to all for the past assistance but I'm still having problems getting a
> canon 2700f SCSI film scanner to work with SANE. I have tried the suggestions
> offered so far but as sane-find-scanner still produces the following output.
>
> found SCSI scanner "CANON IX-2
Hi,
Thanks to all for the past assistance but I'm still having problems getting a
canon 2700f SCSI film scanner to work with SANE. I have tried the suggestions
offered so far but as sane-find-scanner still produces the following output.
found SCSI scanner "CANON IX-27015C 1.15" at /dev/sg0
# Y
quit testing with sane an kooka. until you get it to show up in
sane-find-scanner and scanimage -L, there is no point.
allan
On Wed, 2 Aug 2006, John Bird wrote:
> Hi
> first let me apologise for posting here but I have searched on the net and
> posted in two Linux user groups all to no avail.
Hi
first let me apologise for posting here but I have searched on the net and
posted in two Linux user groups all to no avail. I'm running Kubutu 6.06 64
bit using Kernel 26.15.26 and so installed Deb packets from this
distribution.
I'm trying (very trying at times) to get GIMP to Scan using a C
13 matches
Mail list logo
