[sane-devel] CanoScan 9000F code compilation

[Al Bogner]

Am So, 03 Jul 2011 09:54:31 CEST schrieb Stefan Polakowski:

> Al,
> 
> no success here under Ubuntu 10.10, also after waiting almost one
> day... I compiled Gernot's sane backend and added the udev rule as
> well. sane-find-scanner does find the scanner, but scanimage -L does
> not find it.

I tried it with Natty (11.04). First I thought it is necessary to
reboot, but with another machine, I had to wait only a few hours and
the scanner was recognized then, without doing anything. I was shopping
in the meantime.

> I tried as root,

Did you install the driver as root or with sudo? Try as root.

I mean
sudo passwd root
...
su -

> and also changed the access rights to the USB
> device /dev/bus/usb/002/00x (I know it's not the right way, just
> experimental).
> sane-find-scanner is checking various device files
> like /dev/usb/scanner0..15 and /dev/usbscanner0..15 (as shown when
> using the -v option), but all without success. Finally it prints:
> found USB scanner (vendor=0x04a9 [Canon], product=0x1908 [CanoScan])
> at libusb:002:006
> This makes me think: Should there be a special device file for the
> scanner, like sane-find-scanner is looking for?

Maybe you contact Gernot privately. Gernot helped me a lot, but he is
very busy.

Al

[sane-devel] CanoScan 9000F code compilation

[Al Bogner]

Am Fr, 01 Jul 2011 21:40:59 CEST schrieb Stefan-bkk:

> 
> Hi Al,
> 
> any progress? My 9000F is rusting on my desk and one of the few
> reasons to keep an XP partition on my HD.
> Also Gernot's blog is not accessible. Where can I get instructions and
> Gernot's code?

For "normal" use, Gernot's driver works fine for me. I didn't test
negative scans.

For instructions see my mail to this list:

Sun, 5 Jun 2011 02:15:19 +0200
[sane-devel] CanoScan 9000F code compilation

There is only 1 strange thing with my Suse and Ubuntu machines, 32bit
and 64bit. Wait a few hours with Ubuntu and wait 1 day with Suse to test
if the scanner is recognized.

After the compilation the scanner was not recognized and after a while
it was. Maybe there is a cronjob, which does the "rest".


To use the scanner as a user, you have to add

/lib/udev/rules.d/40-libsane.rules

#in 1 line
ATTRS{idVendor}=="04a9", ATTRS{idProduct}=="1908",
ENV{libsane_matched}="yes"

Thanks Gernot for your great work and I hope one day, there will be an
option for line-art, as discussed privately.

Al

[sane-devel] CanoScan 9000F code compilation

[Gernot Hassenpflug]

On Sat, Jul 2, 2011 at 1:40 PM, Stefan-bkk  wrote:
>
> Hi Al,
>
> any progress? My 9000F is rusting on my desk and one of the few reasons to
> keep an XP partition on my HD.
> Also Gernot's blog is not accessible. Where can I get instructions and
> Gernot's code?
Hi, I'll send you a private mail with the code and instructions.
Sorry, I cannot keep my site up continuously.
Cheers,
Gernot

[sane-devel] CanoScan 9000F code compilation

[Stefan-bkk]

Hi Al,

any progress? My 9000F is rusting on my desk and one of the few reasons to
keep an XP partition on my HD.
Also Gernot's blog is not accessible. Where can I get instructions and
Gernot's code?

Thanks!
Stefan
-- 
View this message in context: 
http://old.nabble.com/CS9000F-code-tp31765437p31978055.html
Sent from the SANE - Dev mailing list archive at Nabble.com.

[sane-devel] CanoScan 9000F code compilation

[Al Bogner]

Am So, 05 Jun 2011 06:19:24 CEST schrieb Gernot Hassenpflug:

> On Sun, Jun 5, 2011 at 5:54 AM, Al Bogner 
> wrote:
> > Am Sa, 04 Jun 2011 08:12:06 CEST schrieb Gernot Hassenpflug:
> >
> > Hi Gernot,
> >
> > I tried hours ago and now:
> >
> > date
> > Sa 4. Jun 22:52:13 CEST 2011
> >
> > ping -c3 aikishugyo.dnsdojo.org
> > PING aikishugyo.dnsdojo.org (219.160.114.155) 56(84) bytes of data.
> > --- aikishugyo.dnsdojo.org ping statistics ---
> > 3 packets transmitted, 0 received, 100% packet loss, time 2001ms
> >
> > Unfortunately it doesn't work. Could you copy the text of the howto
> > in an email and send it to me?
> 
> Mail sent.

Thanks Gernot,

I use Ubuntu 11.04 Natty and things look more or less fine, when I
compile the code for the CanoScan 9000F, but at the end it doesn't work.

What I did:

apt-get install git autoconf automake libusb-dev

mkdir ~/src
cd ~/src

git clone git://git.debian.org/sane/sane-backends.git

cd ~/canon9000fpatch
unzip canoscan900f_mp150-files.zip
cp -v ~/canon9000fpatch/mp150-files/* ~/src/sane-backends/backend

cd ~/src/sane-backends

~/src/sane-backends$ autoconf 
aclocal.m4:16: warning: this file was generated for autoconf 2.66.

I use autoconf 2.67-2ubuntu1

~/src/sane-backends$ autoreconf 
Can't exec "libtoolize": Datei oder Verzeichnis nicht gefunden
at /usr/bin/autoreconf line 196. Use of uninitialized value in pattern
match (m//) at /usr/bin/autoreconf line 196. configure.in:511: warning:
LTOPTIONS_VERSION is m4_require'd but not m4_defun'd m4/libtool.m4:69:
LT_INIT is expanded from... m4/libtool.m4:107: AC_PROG_LIBTOOL is
expanded from... configure.in:511: the top level
configure.in:511: warning: LTSUGAR_VERSION is m4_require'd but not
m4_defun'd configure.in:511: warning: LTVERSION_VERSION is m4_require'd
but not m4_defun'd configure.in:511: warning: LTOBSOLETE_VERSION is
m4_require'd but not m4_defun'd configure.in:511: warning:
LTOPTIONS_VERSION is m4_require'd but not m4_defun'd m4/libtool.m4:69:
LT_INIT is expanded from... m4/libtool.m4:107: AC_PROG_LIBTOOL is
expanded from... configure.in:511: the top level
configure.in:511: warning: LTSUGAR_VERSION is m4_require'd but not
m4_defun'd configure.in:511: warning: LTVERSION_VERSION is m4_require'd
but not m4_defun'd configure.in:511: warning: LTOBSOLETE_VERSION is
m4_require'd but not m4_defun'd configure.in:511: warning:
LTOPTIONS_VERSION is m4_require'd but not m4_defun'd m4/libtool.m4:69:
LT_INIT is expanded from... m4/libtool.m4:107: AC_PROG_LIBTOOL is
expanded from... configure.in:511: the top level
configure.in:511: warning: LTSUGAR_VERSION is m4_require'd but not
m4_defun'd configure.in:511: warning: LTVERSION_VERSION is m4_require'd
but not m4_defun'd configure.in:511: warning: LTOBSOLETE_VERSION is
m4_require'd but not m4_defun'd configure.in:509: error: possibly
undefined macro: AC_LIBTOOL_WIN32_DLL If this token and others are
legitimate, please use m4_pattern_allow. See the Autoconf documentation.
configure.in:510: error: possibly undefined macro: AC_DISABLE_STATIC
configure:10167: error: possibly undefined macro: m4_ifval
configure:12828: error: possibly undefined macro: _LT_SET_OPTIONS
configure:12828: error: possibly undefined macro: LT_INIT
: /usr/bin/autoconf failed with exit status: 1

So I did:

rm -rf ~/src

and started from the beginning

Now I did _not_ do "autoreconf", only autoconf and ignored the warning.

automake
backend/Makefile.am:52: `%'-style pattern rules are a GNU make extension
po/Makefile.am:17: shell if test -r $(srcdir: non-POSIX variable name
po/Makefile.am:17: (probably a GNU make extension)
po/Makefile.am:18: shell if test -r $(srcdir: non-POSIX variable name
po/Makefile.am:18: (probably a GNU make extension)
po/Makefile.am:20: shell LINGUAS="$(PO_LINGUAS: non-POSIX variable name
po/Makefile.am:20: (probably a GNU make extension)
po/Makefile.am:21: shell LINGUAS="$(PO_LINGUAS: non-POSIX variable name
po/Makefile.am:21: (probably a GNU make extension)
tools/Makefile.am:59: wildcard ${top_srcdir}/doc/descriptions/*.desc:
non-POSIX variable name tools/Makefile.am:59: (probably a GNU make
extension) tools/Makefile.am:59: wildcard
${top_srcdir}/doc/descriptions-external/*.desc: non-POSIX variable name
tools/Makefile.am:59: (probably a GNU make extension)
tools/Makefile.am:63: wildcard ${top_srcdir}/doc/descriptions/*.desc:
non-POSIX variable name tools/Makefile.am:63: (probably a GNU make
extension) tools/Makefile.am:63: wildcard
${top_srcdir}/doc/descriptions-external/*.desc: non-POSIX variable name
tools/Makefile.am:63: (probably a GNU make extension)
tools/Makefile.am:67: wildcard ${top_srcdir}/doc/descriptions/*.desc:
non-POSIX variable name tools/Makefile.am:67: (probably a GNU make
extension) tools/Makefile.am:67: wildcard
${top_srcdir}/doc/descriptions-external/*.desc: non-POSIX variable name
tools/Makefile.am:67: (probably a GNU make extension)
tools/Makefile.am:71: wildcard ${top_srcdir}/doc/descriptions/*.desc:
non-POSIX variable name tools/Makefile.am:71: (probably a