On Tuesday, 17 July 2018 15:23:06 BST Jack wrote: > 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
I've also had problems with my WiFi/bluetooth with all kernels after 4.9.95. The kernel binds and unbinds the USB device in a loop pegging the CPU. I'm mentioning it here in case it is related (the USB part), but sadly I have no solution for it yet. :-( -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
