[sane-devel] Re: Build system changes -- please test!

[Paul Smedley]

Hi All,
On Sun, 30 Oct 2005 17:26:46 UTC, "Franz Bakan"  
wrote:

> On Sat, 29 Oct 2005 22:14:32 +0200, Henning Meier-Geinitz wrote:
> 
> >I have just committed some changes regarding the Makefiles to the
> >sane-backends CVS. Please test if sane-backends can still be built and
> >installed on your system (especially OpenBSD and MacOS X).
> 
> still builds on OS/2 :-)

Also confirmed here as still OK on OS/2 :)

-- 
Cheers,

Paul.

[sane-devel] Canon CanoScan LiDE 35

[Pierre Willenbrock]

Cameron Harris schrieb:
> Fantastic! I just messed around with the lock button on the bottom of
> the scanner, locking and unlocking a few times, then tilting it to the
> side a bit.. and it works now!
> 
> All I can guess is that someone picked up the scanner when it was
> unlocked and I wasn't looking and it made the scanner head lock in a
> funny position... but now it works, so that's cool. :D It was the
> bulkin patch that seemed to actually make it scan.
> 
> Thanks for your help :)

Thanks for your valuable input. I commited the change.

Regards,
  Pierre

[sane-devel] Canon CanoScan LiDE 35

[Cameron Harris]

On 10/30/05, Pierre Willenbrock  wrote:
> Cameron Harris schrieb:
> > On 10/30/05, Pierre Willenbrock  wrote:
> >
> >>
> >>Thanks for the log.
> >>
> >>Please try the attached patch.
> >>I don't know if it helps. The backend is trying to read 156 bytes
> >>from the scanner, but libusb does not provide that much. We need to find
> >>out where the data is lost. The patch addresses one possible cause.
> >>
> >>Regards,
> >>  Pierre
> >>
> >
> > U.. well... good and bad news.
> >
> > The patch made it get past where it was stopping before, and now loads
> > of rubbish appears on the terminal when I do scanimage. I ran xsane to
> > see if it was scanning anything, hit acquire preview.
>
> The "loads of rubbish" actually are the requested image. scanimage
> outputs on stdout per default.
>
> >
> > The scanner made a few noises, then went "bp"
> > until the scan was done. While it was beeping, the scanner head was
> > lit green.
>
> Did the head move? xsanes default is to scan in grey mode, which is
> translated into a monochrome green scan.
>
> >
> > The image produced was just grey lines on a black-ish background. One
> > good thing is that if I open the scanner lid mid-scan, it seems to
> > have an effect on the image appearing on screen.
> >
> > Sane Screenshot: http://htsc01.b3ta.org/scan.png
> >
> > Where it gets lighter is where I opened the lid, and darker again when
> > I closed it.
> >
>
> I guess the calibration step failed.
>
> Each scan should look like this:
> - (optionally)move head home
> - blink lamp
> - move head away from home
> - blink lamp
> - move head home
> - (maybe) blink lamp
> - move head away from home
> - blink lamp
> - move head home
> - do a short scan
> - move head home
> - do the real scan
>
> If the head moved in the "short scan" part, please compress and send me
> black_white_shading.pnm. That image should be generated while using
> scanimage with SANE_DEBUG_GENESYS=255.
>
> > I'll try getting it onto a Windows system and actually making sure the
> > scanner works properly :|, maybe I could get a USB snoop while I'm at
> > it, just in case.
> >
>
> Regards,
>   Pierre
>
Fantastic! I just messed around with the lock button on the bottom of
the scanner, locking and unlocking a few times, then tilting it to the
side a bit.. and it works now!

All I can guess is that someone picked up the scanner when it was
unlocked and I wasn't looking and it made the scanner head lock in a
funny position... but now it works, so that's cool. :D It was the
bulkin patch that seemed to actually make it scan.

Thanks for your help :)
--
Cameron Harris

[sane-devel] Canon CanoScan LiDE 35

[Pierre Willenbrock]

Cameron Harris schrieb:
> On 10/30/05, Pierre Willenbrock  wrote:
> 
>>
>>Thanks for the log.
>>
>>Please try the attached patch.
>>I don't know if it helps. The backend is trying to read 156 bytes
>>from the scanner, but libusb does not provide that much. We need to find
>>out where the data is lost. The patch addresses one possible cause.
>>
>>Regards,
>>  Pierre
>>
> 
> U.. well... good and bad news.
> 
> The patch made it get past where it was stopping before, and now loads
> of rubbish appears on the terminal when I do scanimage. I ran xsane to
> see if it was scanning anything, hit acquire preview.

The "loads of rubbish" actually are the requested image. scanimage
outputs on stdout per default.

> 
> The scanner made a few noises, then went "bp"
> until the scan was done. While it was beeping, the scanner head was
> lit green.

Did the head move? xsanes default is to scan in grey mode, which is
translated into a monochrome green scan.

> 
> The image produced was just grey lines on a black-ish background. One
> good thing is that if I open the scanner lid mid-scan, it seems to
> have an effect on the image appearing on screen.
> 
> Sane Screenshot: http://htsc01.b3ta.org/scan.png
> 
> Where it gets lighter is where I opened the lid, and darker again when
> I closed it.
> 

I guess the calibration step failed.

Each scan should look like this:
- (optionally)move head home
- blink lamp
- move head away from home
- blink lamp
- move head home
- (maybe) blink lamp
- move head away from home
- blink lamp
- move head home
- do a short scan
- move head home
- do the real scan

If the head moved in the "short scan" part, please compress and send me
black_white_shading.pnm. That image should be generated while using
scanimage with SANE_DEBUG_GENESYS=255.

> I'll try getting it onto a Windows system and actually making sure the
> scanner works properly :|, maybe I could get a USB snoop while I'm at
> it, just in case.
> 

Regards,
  Pierre

[sane-devel] Canon CanoScan LiDE 35

[Cameron Harris]

On 10/30/05, Pierre Willenbrock  wrote:
> Cameron Harris schrieb:
> >
> >
> > Right.. got a full compressed log, attached it to this message.
> >
> > Thanks :)
> >
>
> Thanks for the log.
>
> Please try the attached patch.
> I don't know if it helps. The backend is trying to read 156 bytes
> from the scanner, but libusb does not provide that much. We need to find
> out where the data is lost. The patch addresses one possible cause.
>
> Regards,
>   Pierre
>
>
>

U.. well... good and bad news.

The patch made it get past where it was stopping before, and now loads
of rubbish appears on the terminal when I do scanimage. I ran xsane to
see if it was scanning anything, hit acquire preview.

The scanner made a few noises, then went "bp"
until the scan was done. While it was beeping, the scanner head was
lit green.

The image produced was just grey lines on a black-ish background. One
good thing is that if I open the scanner lid mid-scan, it seems to
have an effect on the image appearing on screen.

Sane Screenshot: http://htsc01.b3ta.org/scan.png

Where it gets lighter is where I opened the lid, and darker again when
I closed it.

I'll try getting it onto a Windows system and actually making sure the
scanner works properly :|, maybe I could get a USB snoop while I'm at
it, just in case.

Thanks again :) .
--
Cameron Harris

[sane-devel] Canon CanoScan LiDE 35

[Pierre Willenbrock]

Cameron Harris schrieb:
> 
> 
> Right.. got a full compressed log, attached it to this message.
> 
> Thanks :)
> 

Thanks for the log.

Please try the attached patch.
I don't know if it helps. The backend is trying to read 156 bytes
from the scanner, but libusb does not provide that much. We need to find
out where the data is lost. The patch addresses one possible cause.

Regards,
  Pierre
-- next part --
A non-text attachment was scrubbed...
Name: bulkin.diff
Type: text/x-patch
Size: 514 bytes
Desc: not available
Url : 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20051030/cd1d1128/bulkin.bin
From fba...@gmx.net  Sun Oct 30 17:26:46 2005
From: fba...@gmx.net (Franz Bakan)
Date: Sun Oct 30 18:27:18 2005
Subject: [sane-devel] Build system changes -- please test!
In-Reply-To: <20051029201432.ga1...@meier-geinitz.de>
Message-ID: 

On Sat, 29 Oct 2005 22:14:32 +0200, Henning Meier-Geinitz wrote:

>I have just committed some changes regarding the Makefiles to the
>sane-backends CVS. Please test if sane-backends can still be built and
>installed on your system (especially OpenBSD and MacOS X).

still builds on OS/2 :-)

Franz

[sane-devel] Nikon LS50/5000

[Spiro Angeli]

Hi Ariel,

thank you so much for your effort.

I implemented the patch, under Gentoo and got this error:

# emerge sane-backends
Calculating dependencies ...done!
>>> emerge (1 of 1) media-gfx/sane-backends-1.0.15 to /
>>> md5 files   sane-backends-1.0.15.ebuild
>>> md5 files   sane-backends-1.0.13-r3.ebuild
>>> md5 files   sane-backends-1.0.15-r1.ebuild
>>> md5 files   sane-backends-1.0.15-r2.ebuild
>>> md5 files   sane-backends-1.0.15-r3.ebuild
>>> md5 files   sane-backends-1.0.16-r1.ebuild
>>> md5 files   sane-backends-1.0.16-r2.ebuild
>>> md5 files   sane-backends-1.0.15.ebuild.bk
>>> md5 files   files/digest-sane-backends-1.0.15
>>> md5 files   files/canoscan-focus.patch
>>> md5 files   files/cs2-ls50-full.patch
>>> md5 files   files/lide25.patch
>>> md5 files   files/digest-sane-backends-1.0.13-r3
>>> md5 files   files/digest-sane-backends-1.0.15-r1
>>> md5 files   files/digest-sane-backends-1.0.15-r2
>>> md5 files   files/libusbscanner-device-r1.patch
>>> md5 files   files/libusbscanner-device.patch
>>> md5 files   files/linux_sg3_err.h
>>> md5 files   files/digest-sane-backends-1.0.15-r3
>>> md5 files   files/sane-backend-1.0.15-gt68xx-update67.patch
>>> md5 files   files/digest-sane-backends-1.0.16-r1
>>> md5 files   files/digest-sane-backends-1.0.16-r2
>>> md5 src_uri  sane-backends-1.0.15.tar.gz
>>> md5 src_uri  sane-backends-1.0.15-brothermfc.patch.bz2
>>> Unpacking source...
>>> Unpacking sane-backends-1.0.15.tar.gz 
to /var/tmp/portage/sane-backends-1.0.15/work
>>> Unpacking sane-backends-1.0.15-brothermfc.patch.bz2 
to /var/tmp/portage/sane-backends-1.0.15/work
>>> Unpacking sane-backends-1.0.15-brothermfc.patch.bz2 
to /var/tmp/portage/sane-backends-1.0.15/work
 * Applying canoscan-focus.patch ...
 
[ ok ]
 * Applying cs2-ls50-full.patch ...

 * Failed Patch: cs2-ls50-full.patch !
 *  ( /usr/portage/media-gfx/sane-backends/files/cs2-ls50-full.patch )
 *
 * Include in your bugreport the contents of:
 *
 *   /var/tmp/portage/sane-backends-1.0.15/temp/cs2-ls50-full.patch-15359.out


!!! ERROR: media-gfx/sane-backends-1.0.15 failed.
!!! Function epatch, Line 363, Exitcode 0
!!! Failed Patch: cs2-ls50-full.patch!
!!! If you need support, post the topmost build error, NOT this status 
message.


Do you happend to know anything about this or did I do something wrong?

thank you,
Spiro

[sane-devel] Canon CanoScan LiDE 35

[Pierre Willenbrock]

Cameron Harris schrieb:
> On 10/30/05, Pierre Willenbrock  wrote:
> 
>>
>>Does it always stop there? It looks like the usb connection somehow
>>broke while transfering data. Does the scanner re-register with your
>>system at the moment the transmission stops? There will be some kernel
>>messages about a new usb device in that case.
>>
> 
> Yeah it always stops there, nothing in dmesg about it.

Then i would like to have a full log, with SANE_DEBUG_GENESYS=255,
SANE_DEBUG_GENESYS_GL841=255, SANE_DEBUG_SANEI_USB=255. That log will
get large. Please compress it and send it to me(The list won't accept
messages larger than 50k). If the compressed log is larger than 4MB we
need to find a different transport channel.

Regards,
  Pierre

[sane-devel] Re: Build system changes -- please test!

[Michael Piotrowski]

Henning Meier-Geinitz  writes:

> I have just committed some changes regarding the Makefiles to the
> sane-backends CVS. Please test if sane-backends can still be built and
> installed on your system (especially OpenBSD and MacOS X).

I don't know about these platforms, but I can say that it doesn't
break anything on NetBSD (2.0.2 on i386).

-- 
Michael Piotrowski, M.A.   
Public key at 

[sane-devel] Canon CanoScan LiDE 35

[Cameron Harris]

On 10/30/05, Pierre Willenbrock  wrote:
> Cameron Harris schrieb:
> >
> > Well... I checked out experimental, copied the experimental/genesys/*
> > over to the backend/ directory, then make clean/make/make install...
> >
> > Gets slightly further in the scanning this time.
> >
> > # SANE_DEBUG_GENESYS=255 scanimage -d genesys
> > outputs lots of stuff and my scanner's head moves a little bit,
> > flashes a few different colours.. but then it gets to...
> >
> > [genesys] sanei_genesys_read_data_from_scanner (size = 156 bytes)
> > [genesys] genesys_read_valid_words
> > [genesys] sanei_genesys_read_register (0x44, 0x00) completed
> > [genesys] sanei_genesys_read_register (0x43, 0x00) completed
> > [genesys] sanei_genesys_read_register (0x42, 0x00) completed
> > [genesys] genesys_read_valid_words: 0 words
> > [genesys] genesys_read_valid_words
> > [genesys] sanei_genesys_read_register (0x44, 0x84) completed
> > [genesys] sanei_genesys_read_register (0x43, 0x2b) completed
> > [genesys] sanei_genesys_read_register (0x42, 0x00) completed
> > [genesys] genesys_read_valid_words: 11140 words
> >
> > Where it stops for about 30 seconds, then...
> >
> > [genesys] sanei_genesys_read_data_from_scanner: reading bulk data
> > failed: Error during device I/O
> > [genesys] genesys_black_white_shading_calibration: Failed to read
> > data: Error during device I/O
> > [genesys] genesys_flatbed_calibration: failed to do dark+white shading
> > calibration: Error during device I/O
> > [genesys] genesys_start_scan: failed to do flatbed calibration: Error
> > during device I/O
> > scanimage: sane_start: Error during device I/O
> > [genesys] sane_cancel: start
> >
> > Any ideas?
> >
> > Thanks :)
> >
> Does it always stop there? It looks like the usb connection somehow
> broke while transfering data. Does the scanner re-register with your
> system at the moment the transmission stops? There will be some kernel
> messages about a new usb device in that case.
>
>

Yeah it always stops there, nothing in dmesg about it.
--
Cameron Harris

[sane-devel] Canon CanoScan LiDE 35

[Pierre Willenbrock]

Cameron Harris schrieb:
> 
> Well... I checked out experimental, copied the experimental/genesys/*
> over to the backend/ directory, then make clean/make/make install...
> 
> Gets slightly further in the scanning this time.
> 
> # SANE_DEBUG_GENESYS=255 scanimage -d genesys
> outputs lots of stuff and my scanner's head moves a little bit,
> flashes a few different colours.. but then it gets to...
> 
> [genesys] sanei_genesys_read_data_from_scanner (size = 156 bytes)
> [genesys] genesys_read_valid_words
> [genesys] sanei_genesys_read_register (0x44, 0x00) completed
> [genesys] sanei_genesys_read_register (0x43, 0x00) completed
> [genesys] sanei_genesys_read_register (0x42, 0x00) completed
> [genesys] genesys_read_valid_words: 0 words
> [genesys] genesys_read_valid_words
> [genesys] sanei_genesys_read_register (0x44, 0x84) completed
> [genesys] sanei_genesys_read_register (0x43, 0x2b) completed
> [genesys] sanei_genesys_read_register (0x42, 0x00) completed
> [genesys] genesys_read_valid_words: 11140 words
> 
> Where it stops for about 30 seconds, then...
> 
> [genesys] sanei_genesys_read_data_from_scanner: reading bulk data
> failed: Error during device I/O
> [genesys] genesys_black_white_shading_calibration: Failed to read
> data: Error during device I/O
> [genesys] genesys_flatbed_calibration: failed to do dark+white shading
> calibration: Error during device I/O
> [genesys] genesys_start_scan: failed to do flatbed calibration: Error
> during device I/O
> scanimage: sane_start: Error during device I/O
> [genesys] sane_cancel: start
> 
> Any ideas?
> 
> Thanks :)
> 
Does it always stop there? It looks like the usb connection somehow
broke while transfering data. Does the scanner re-register with your
system at the moment the transmission stops? There will be some kernel
messages about a new usb device in that case.

[sane-devel] Canon CanoScan LiDE 35

[Cameron Harris]

On 10/27/05, Regin LARSEN  wrote:
> Cameron Harris skribis/wrote:
> > Today, I checked out a CVS copy of the sane-backends, and compiled it
> > all with genesys support. Unfortunately it hangs when i try scanimage
>
> you've to use the genesys-sources from the experimental directory
>
>
> regin
>

Well... I checked out experimental, copied the experimental/genesys/*
over to the backend/ directory, then make clean/make/make install...

Gets slightly further in the scanning this time.

# SANE_DEBUG_GENESYS=255 scanimage -d genesys
outputs lots of stuff and my scanner's head moves a little bit,
flashes a few different colours.. but then it gets to...

[genesys] sanei_genesys_read_data_from_scanner (size = 156 bytes)
[genesys] genesys_read_valid_words
[genesys] sanei_genesys_read_register (0x44, 0x00) completed
[genesys] sanei_genesys_read_register (0x43, 0x00) completed
[genesys] sanei_genesys_read_register (0x42, 0x00) completed
[genesys] genesys_read_valid_words: 0 words
[genesys] genesys_read_valid_words
[genesys] sanei_genesys_read_register (0x44, 0x84) completed
[genesys] sanei_genesys_read_register (0x43, 0x2b) completed
[genesys] sanei_genesys_read_register (0x42, 0x00) completed
[genesys] genesys_read_valid_words: 11140 words

Where it stops for about 30 seconds, then...

[genesys] sanei_genesys_read_data_from_scanner: reading bulk data
failed: Error during device I/O
[genesys] genesys_black_white_shading_calibration: Failed to read
data: Error during device I/O
[genesys] genesys_flatbed_calibration: failed to do dark+white shading
calibration: Error during device I/O
[genesys] genesys_start_scan: failed to do flatbed calibration: Error
during device I/O
scanimage: sane_start: Error during device I/O
[genesys] sane_cancel: start

Any ideas?

Thanks :)

--
Cameron Harris

[sane-devel] Still trying to get Epson CX6600 to work.

[russbucket]

On Thursday 27 October 2005 00:27, Johannes Meixner wrote:
> Hello,
>
> On Oct 25 13:09 russbucket wrote (shortened):
> > On Monday 24 October 2005 23:55, Johannes Meixner wrote:
> > > On Oct 24 15:49 russbucket wrote (shortened):
> > > > I tried iscan 17.0, Iscan-free 17.0 and the iscan that came with
> > > > my SuSE 10.0 DVD.

> and
> http://portal.suse.com/sdb/en/2005/09/jsmeix_scanner-setup-100.html
> for Suse Linux 10.0
>
>
> Kind Regards
> Johannes Meixner
> --
> SUSE LINUX Products GmbH, Maxfeldstrasse 5  Mail: jsm...@suse.de
> 90409 Nuernberg, GermanyWWW: http://www.suse.de/
I final have the scanner working but I need to ask a couple of questions.

SuSe is using udev and I found the usb and its info in /sys/ .

I got it working by disabling epkowa in the dll.conf file and enabling epson. 
sane-find-scanner & Scanimage -L reported:

linux:/home/finemanruss # sane-find-scanner

  # No SCSI scanners found. If you expected something different, make sure 
that
  # you have loaded a SCSI driver for your SCSI adapter.

found USB scanner (vendor=0x04b8 [EPSON], product=0x0813 [USB2.0 MFP]) at 
libusb:001:002
  # Your USB scanner was (probably) detected. It may or may not be supported 
by
  # SANE. Try scanimage -L and read the backend's manpage.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.
linux:/home/finemanruss # scanimage -L
device `epson:libusb:001:002' is a Epson Unknown model flatbed scanner

I added the correct vendor ID: 0x04b8 and product ID: 0x0813 to 
libsane.usermap but it still reports Unknown model. 

I don't care if Iscan works, should I use iscan-free instead of iscan 
1.15.0.2-4.1 and is sane rpm -q sane 
sane-1.0.15-20.1 OK. 

Should I get sane 1.0.16 Also what do i need to do  to make this a unknown 
device?

The scanner does scan with xsane and koola. 

Again thanks for all your help. I will try to help with the project as soon as 
I learn more.