public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jack <ostroffjh@users.sourceforge.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] scanner problem
Date: Tue, 17 Jul 2018 10:23:06 -0400	[thread overview]
Message-ID: <IASS6FGI.HKYAH5XS.FNTLS3NB@NPVPAANW.LILULGKV.HL7C6BDS> (raw)
In-Reply-To: <20180717063853.GA1944@ca.inter.net> (from purslow@ca.inter.net on Tue Jul 17 02:38:53 2018)

On 2018.07.17 02:38, Philip Webb wrote:
> My scanner -- Epson Perfection V550 Photo -- is suddenly not detected  
> :
> when I enter 'xsane' (via the menu or Alt-F2), it says "no devices  
> available".
> 
> I last used it without any problem 180626.
> Since then, I've updated my kernel & some other pkgs.
> I've checked the USB physical connection ; the scanner 'ready' light  
> is on.
> I've remerged 'xsane' & 'sane-backends' & rebooted.
> 
> Following my notes, I've done :
> 
>   root:500 ~> sane-find-scanner
>   ...
>   found USB scanner (vendor=0x04b8 [EPSON], product=0x013b [EPSON  
> Scanner]) at libusb:001:004
>   # Your USB scanner was (probably) detected.
>   # It may or may not be supported by SANE.
>   # Try scanimage -L and read the backend's manpage.
> root:501 ~> scanimage -L
> device `epkowa:interpreter:001:004' is a Epson Perfection V550 Photo  
> flatbed scanner
> 
>   The first time I ran these commands (I don't remember which),
>   the scanner itself made the noises it usually does when starting.
> 
>   This model needs a driver which is not included in 'sane-backends'
>   & which I downloaded from Nvidia & installed when I got the scanner  
> 2017.
>   The 'epkowa' driver is installed :
> 
>   root:505 ~> locate epkowa
>     /etc/sane.d/epkowa.conf
>     /usr/lib64/sane/libsane-epkowa.la
>     /usr/lib64/sane/libsane-epkowa.so.1
>     /usr/lib64/sane/libsane-epkowa.so.1.0.15
>     /usr/lib64/sane/archive/libsane-epkowa.la
>     /usr/lib64/sane/archive/libsane-epkowa.so.1
>     /usr/lib64/sane/archive/libsane-epkowa.so.1.0.15
> 
> My user is a member of the 'scanner' group :
> 
>   scanner:x:104:purslow
> 
> I am puzzled : does anyone have a suggestion what to do next ?

Does the scanner currently show up if you do "lsusb" ?
Does dmesg say anything when you plug the scanner in?
Is it possible that the driver needs updating to deal with a newer  
kernel?

Jack

  parent reply	other threads:[~2018-07-17 14:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-17  6:38 [gentoo-user] scanner problem Philip Webb
2018-07-17 14:18 ` Steven Lembark
2018-07-17 14:23 ` Jack [this message]
2018-07-17 14:43   ` Mick
2018-07-18  8:16 ` Philip Webb
2018-07-18  9:50   ` Andrew Udvare
2018-07-19  6:03   ` Raffaele Belardi
2018-07-19  9:29   ` [gentoo-user] scanner problem : latest Philip Webb
2018-07-19 10:03     ` Mick
2018-07-19 16:08     ` [gentoo-user] " Ian Zimmerman
2018-07-20 13:04       ` Philip Webb
2018-07-20 13:25         ` [gentoo-user] Re: scanner problem : PS Philip Webb
2018-07-20 22:10         ` [gentoo-user] Re: scanner problem : latest Mick
2018-07-23 22:29         ` Neil Bothwick
2018-07-24 14:14           ` Philip Webb
2018-07-24 14:38             ` Mick
2018-07-26 14:30               ` Mick
2018-07-24 20:10             ` Neil Bothwick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=IASS6FGI.HKYAH5XS.FNTLS3NB@NPVPAANW.LILULGKV.HL7C6BDS \
    --to=ostroffjh@users.sourceforge.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox