Canon Pixma G3501 at *Ubuntu 18.04 LTS: help needed to get the scanner running.

[Bas Roufs]

Thank you, dear Brian.
The solutions you propose sound totally reasonable. Gonna check them in the
coming day.
Yours.
Bas.

Op zo 13 sep. 2020 19:26 schreef

Brian <ad44 at cityscape.co.uk>

> On Sun 13 Sep 2020 at 15:56:59 +0200, Bas G. Roufs wrote:
>
> > Hello Brian,
> >
> > Before carrying out the tests you suggest in your latest mail, I first
> > explain what I have done in the mean time.
> >
> > I did install the exactly right print and scan drivers from Canon.....
> >
> > https://ijstartcanon.net/canon-pixma-g3501-drivers-download/
> >
> > I did so more or less along the lines of this tutorial....
> >
> >
> https://tutorialforlinux.com/2019/04/08/how-to-install-canon-g3500-g3501-driver-on-ubuntu-18-04-bionic-lts/2/
>
> What many users do not appreciate is that Canon do not supply drivers
> to use with SANE, so SANE hasn't anything to work with. See
>
>   https://wiki.debian.org/Scanner#canon
>
> 'scanimage -L' gives you
>
>   device `pixma:G3000_192.168.2.12' is a CANON Canon PIXMA G4000 Series
>
> This is sane-pixma, provided by the SANE project, not Canon. It is
> telling you it has found a device to use. The device doesn't work, but
> that is a different matter.
>
> > Now, let's carry out a few tests.....
>
> Ok as far as it goes, but the only hostname is Viaconsensus-iter.local
> and there is no hostname or IP address for the printer device. I will
> return to this later.
>
> [Snip]
>
> > Now, I carry on with the scan test:
> >
> > bas at Viaconsensus-iter:~$ avahi-browse -rt _uscan._tcp
> > bas at Viaconsensus-iter:~$
> >
> > Still no result, though I DID install also the scan software directly
> from
> > Canon.
>
> _uscan._tcp is a service provided by the MFD and nothing to do with the
> installed Canon packages. Maybe the MFD doesn't have a _uscan._tcp
> service to offer, but we haven't enough information from the avahi-browse
> outputs to make a judgement.
>
> > Now, another test. I try to scan something. I launch XSane from terminal.
> > The program starts and the device is being discovered instantly. I hit at
> > the scan button. Then, I hear the device reacting - so the wireless
> > connection is there, cause I did not connect it via the USB cable. Also
> > during the installation process, I have indicated that I want to use a
> > wireless connection. However, still no result. I get again this graphical
> > error report:
> >
> > "(....)
> >
> > Error during read. Error during device I/O.
>
> The pixma backend is not behaving itself properly. I do not have the
> skills to debug this and, in any case, have an easier potential solution.
>
> [Snip]
>
> > Skanlite delivers a similar non-result :-).
> >
> > OK, now I carry on with the tests in your latest message.
> >
> > On 13-09-2020 14:46, Brian wrote:
> > > On Sun 13 Sep 2020 at 12:01:49 +0200, Bas G. Roufs wrote:
> > >
> > > > OK, I have disconnected the USB cable at both sides. Interesting. I
> get
> > > > exactly the same result:
> > > >
> > > > bas at Viaconsensus-iter:~$ scanimage -L
> > > > device `pixma:G3000_192.168.2.12' is a CANON Canon PIXMA G4000 Series
> > > > multi-function peripheral
> > > > bas at Viaconsensus-iter:~$
> > > Lets continue checking that the 3501 is reachable.
> > >
> > > What do you get with 'ping -c 3 192.168.2.12'?
> >
> > bas at Viaconsensus-iter:~$ ping -c 3 192.168.2.12
> > PING 192.168.2.12 (192.168.2.12) 56(84) bytes of data.
> > 64 bytes from 192.168.2.12: icmp_seq=1 ttl=64 time=18.8 ms
> > 64 bytes from 192.168.2.12: icmp_seq=2 ttl=64 time=7.57 ms
> > 64 bytes from 192.168.2.12: icmp_seq=3 ttl=64 time=11.8 ms
> >
> > --- 192.168.2.12 ping statistics ---
> > 3 packets transmitted, 3 received, 0% packet loss, time 2003ms
> > rtt min/avg/max/mdev = 7.577/12.734/18.808/4.630 ms
> > bas at Viaconsensus-iter:~$
> >
> > > Can you access the 3501's
> > > web interface with http://192.168.2.12 in the address bar of a
> browser?
> >
> > Yes, I can - see attachment with a small version of the page I see there.
> > It's a page dedicated to the "Printer status" of my device. It tells also
> > that the printer is "in operation". Additionally, there are instructions
> > about the ink tank, etc.
>
> I think we can now be confident the MFD is network connected. You have
> also discovered the MFD's administration page. While you there would you
> look for settings involving "Bonjour"; it's probably under network or
> lan.
>
> If it is not enabled, please enable it and rerun both avahi-browse
> commands. You are looking for any sign of the 3501.
>
> > > Let's see what we get from what I have asked for. I do have some
> > > alternative software in mind, Bas.
> >
> > Good. Tonight, after 22.30 time in NL/ 21.30 time in Britain, I will
> check
> > your suggestions till that moment and get back to you. Friends are
> waiting
> > for me now.
>
> Download and install sane-airscan from
>
>   https://github.com/alexpevzner/sane-airscan
>
> A direct link to the file you want is
>
>
> https://download.opensuse.org/repositories/home:/pzz/xUbuntu_18.04/amd64/
>
> 100% of the users to whom I have recomended this backend have had great
> success with it. I would be very interested in what 'scanimage -L' gives
> you.
>
> Regards,
>
> Brian.
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20200913/a9ec3edd/attachment.html>