LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-14-2014, 12:13 PM   #1
pchristy
Senior Member
 
Registered: Oct 2012
Location: South Devon, UK
Distribution: Slackware
Posts: 1,126

Rep: Reputation: Disabled
SANE is driving me insane!


System: Slackware64-current (up-to-date)
Scanner: Epson Perfection 1260 (identified as Plustek)

This all worked perfectly under 14.1, without any intervention on my part, but I can't get it working in current.

"sane-find-scanner" correctly locates and identifies the scanner. The USB port to which the scanner connects has the right permissions (root:lp). I am a member of the lp group.

"scanimage -L" as root finds the scanner. Repeating as user, it *doesn't* find the scanner. Re-running as root no longer finds the scanner! "xsane" can't find the scanner!

In other words, although initially "scanimage -L" as root can find the scanner, any attempt to access it as a user seems to delete the scanner from the system, and although sane-find-scanner can still find it, nothing else can.

Stumped!

--
Pete
 
Old 12-14-2014, 12:18 PM   #2
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,091

Rep: Reputation: Disabled
Try this as root:
Code:
gpasswd -a <username> scanner
 
Old 12-14-2014, 01:12 PM   #3
glorsplitz
Senior Member
 
Registered: Dec 2002
Distribution: slackware!
Posts: 1,327

Rep: Reputation: 375Reputation: 375Reputation: 375Reputation: 375
what Didier said, that's one of the things I did to get mine to work
 
Old 12-14-2014, 01:14 PM   #4
pchristy
Senior Member
 
Registered: Oct 2012
Location: South Devon, UK
Distribution: Slackware
Posts: 1,126

Original Poster
Rep: Reputation: Disabled
Hi Didier,

No joy - I'd already added myself to the scanner group via kuser (and logged in again!). But I tried it your way, just in case!

From dmesg:

Code:
2.406732] usb 3-10: New USB device found, idVendor=04b8, idProduct=011d
[    2.406762] usb 3-10: New USB device strings: Mfr=64, Product=77, SerialNumber=0
[    2.406778] usb 3-10: Product: EPSO￿￿￿￿￿￿￿￿￿￿￿￿￿￿
[    2.406793] usb 3-10: Manufacturer: EPSON
From sane-find-scanner:

Code:
found USB scanner (vendor=0x04b8 [EPSON], product=0x011d [EPSO]) at libusb:003:004
Code:
ls -l /dev/bus/usb/003/004
crw-rw-r-- 1 root lp 189, 259 Dec 14 19:04 /dev/bus/usb/003/004
As root:

Code:
 scanimage -L
device `test:0' is a Noname frontend-tester virtual device
device `test:1' is a Noname frontend-tester virtual device
device `plustek:libusb:003:004' is a Epson Perfection 1260/Photo flatbed scanner
As user:

Code:
scanimage -L
device `test:0' is a Noname frontend-tester virtual device
device `test:1' is a Noname frontend-tester virtual device
Now as root again:

Code:
scanimage -L
device `test:0' is a Noname frontend-tester virtual device
device `test:1' is a Noname frontend-tester virtual device
As you can see, the scanner has now disappeared - but sane-find-scanner still finds it as above!



--
Pete
 
Old 12-14-2014, 02:48 PM   #5
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,391

Rep: Reputation: 2765Reputation: 2765Reputation: 2765Reputation: 2765Reputation: 2765Reputation: 2765Reputation: 2765Reputation: 2765Reputation: 2765Reputation: 2765Reputation: 2765
Have you installed the Linux driver from Epson? http://download.ebz.epson.net/dsc/du...038ddc9fc14ff3
The rpm version can be converted using rpm2txz.

It has been reported that Epson drivers can require the creation of a symlink
Code:
ln -s /lib/ld-linux.so.2 /lib/ld-lsb.so.3
to work correctly in Slackware.
 
Old 12-14-2014, 03:02 PM   #6
pchristy
Senior Member
 
Registered: Oct 2012
Location: South Devon, UK
Distribution: Slackware
Posts: 1,126

Original Poster
Rep: Reputation: Disabled
allend: I've never needed to load an Epson driver for it before - internally its a Plustek, and just works off the usual plustek sane backend. I'll bear this in mind, but my old machine, running 14.1 "just worked", so I'm a little puzzled why -current doesn't!

The other point is that I'm running 64-bit (no multi-lib), so the 386 rpm isn't going to work. I would have to compile it from source, which I'm quite prepared to do if necessary, but I know it ought to work with the existing sane drivers.

Thanks for the link!
 
Old 12-14-2014, 10:58 PM   #7
mlslk31
Member
 
Registered: Mar 2013
Location: Florida, USA
Distribution: Slackware, FreeBSD
Posts: 210

Rep: Reputation: 77
Just for now: Do you have to add yourself to the lp group? That's who has the group ownership of /dev/bus/usb/003/004 above. The advice above is supposed to work, but there may be some udev magic that needs to be in play as well.

Last edited by mlslk31; 12-14-2014 at 10:58 PM. Reason: add word "group"
 
Old 12-15-2014, 03:33 AM   #8
pchristy
Senior Member
 
Registered: Oct 2012
Location: South Devon, UK
Distribution: Slackware
Posts: 1,126

Original Poster
Rep: Reputation: Disabled
Hi, mlslk31: Yes, I am a member of the lp group. I've been round this loop many times in the past - most recently with Slack-14.0, but it all seemed to have been fixed in 14.1, which needed no intervention on my part. But this seems to be more than just a simple permissions issue, as the scanner "disappears" - even from root - once any attempt is made to run it as a user. Its almost as if trying to access the scanner as a user unloads a module somewhere or other.

I did wonder if it was something to do with my home-brew kernel, but I have the same issue with the slack-generic kernel that I used for the install.

I have to go out for a while today (I'm in the UK, so a few hours ahead of the US), but I'll come back and have another session on it later.....

Thanks everyone for your help and suggestions!

--
Pete
 
Old 12-15-2014, 12:56 PM   #9
pchristy
Senior Member
 
Registered: Oct 2012
Location: South Devon, UK
Distribution: Slackware
Posts: 1,126

Original Poster
Rep: Reputation: Disabled
Well I've got a little further with this, but not to the extent its working!

Firstly, its not just running scanimage -L as a user that makes the scanner disappear - ANY use of scanimage -L makes it disappear! In other words, I can run scanimage once and it will detect the scanner. If I run it again, it won't, either as root or user!

Secondly, if I wait long enough (like 10 mins or so!) xsane does eventually appear with the scanner correctly identified. However, any attempt to *use* it produces an error message: "Failed to start scanner: error during device I/O"

Now bear in mind that this is a blisteringly fast desktop (8-core i7 with 16GB ram running from an SSD), so what is it doing for 10 mins waiting for xsane to come up??? Top doesn't show any significant load, and running xsane from a command prompt delivers no useful info.

The scanner still works perfectly on my wife's machine, so its not a hardware fault.

Hmmm! Nearly night time here - I must go and sleep on this further....

--
Pete
 
Old 12-15-2014, 03:59 PM   #10
ppr:kut
Slackware Contributor
 
Registered: Aug 2006
Location: Netherlands
Distribution: Slackware
Posts: 631

Rep: Reputation: 463Reputation: 463Reputation: 463Reputation: 463Reputation: 463
If you're on a reasonably recent machine I suspect you're also connecting the scanner on a usb3 port? If so, try to connect it on a USB2 port, if you have one. Sane doesn't like usb2 scanners connected to usb3 ports. They're working on fixing it, but for now, it's a no-go.
Alternatively, you could try downgrading the kernel to the one in 14.1 and see if that fixes things.
 
Old 12-16-2014, 03:42 AM   #11
pchristy
Senior Member
 
Registered: Oct 2012
Location: South Devon, UK
Distribution: Slackware
Posts: 1,126

Original Poster
Rep: Reputation: Disabled
ppr:kut - I think you might be on to something there! Yes, the scanner is plugged into a USB-3 port, and I did wonder if it was a compatibility issue, so I tried it on a USB-2 port, but to no avail. However, since you mentioned it, I've done a Google search for scanners and USB-3, and the symptoms others are describing seem very much like mine.

I did wonder if, once the scanner had locked up under usb-3, it needed power cycling before reconnecting as usb-2, but this doesn't seem to help either. My systems has four usb-3 and two usb-2 ports on the rear (the usb-2 ports currently occupied by keyboard and mouse) plus one of each on the front. So far I've only tried connecting to the front usb-2 port. Perhaps I should try it on the rear ones in case there's something odd about the way the front one is implemented. However, this will mean a complete power down and a lot of rummaging at the rear, so it may take a while!

The motherboard is a Gigabyte GA-Z97X-SLI (Intel chipset), if this is relevant.

This sounds like the most promising line so far. I will investigate further and report back.......

Cheers,

--
Pete
 
Old 12-16-2014, 05:14 AM   #12
Marcelo_Belfalas
Member
 
Registered: Apr 2012
Location: Brazil
Distribution: Slackware64-current multilib
Posts: 32

Rep: Reputation: 18
I had a similar problem with usb 3.0 using a headset, try pluggin the scanner at a usb hub and pluggin the hub in the 3.0 port
 
Old 12-16-2014, 06:03 AM   #13
pchristy
Senior Member
 
Registered: Oct 2012
Location: South Devon, UK
Distribution: Slackware
Posts: 1,126

Original Poster
Rep: Reputation: Disabled
OK, finally got somewhere! Plugging the scanner into a USB-2 port doesn't help because the system still tries to connect via the xhci driver rather than the ehci driver. The only way I've found to prevent this is to disable USB-3 in the BIOS. All the ports (both USB-3 and USB-2) then use the ehci driver, and the scanner works perfectly, whether I plug it into a USB-3 or USB-2 port.

This tells me that the issue here is a software compatibility issue between the SANE backends and the xhci driver, rather than a hardware issue.

Unfortunately, this doesn't help me much as I need USB-3 for some external drives (I do a lot of video work, and need everything as fast as possible!). Looks like I'm going to have to wait for the SANE developers to sort this out. It seems that they are already aware of the issue, but does anyone know the best way of flagging my findings up to them? I probably ought to flag this up to Pat as well, even though there's not a lot he can do about it until the sane guys find a fix - but at least he'll be aware!

Marcelo: I'll have a go with a USB hub - I think I have one in a junk-box somewhere, but I'm not holding my breath! In the meantime, I can still connect the scanner to my wife's machine and use that for scanning, if I have to.

Thanks everyone for your input. I'm going to mark this thread as "solved" - even though it isn't really - we just know what the issue is now!

Cheers,

--
Pete
 
Old 12-16-2014, 10:30 AM   #14
ppr:kut
Slackware Contributor
 
Registered: Aug 2006
Location: Netherlands
Distribution: Slackware
Posts: 631

Rep: Reputation: 463Reputation: 463Reputation: 463Reputation: 463Reputation: 463
No need to bother Pat with this really, as indeed there's not much he can do at this point. I'm personally affected by this as well with my Canon scanner, so I'm on top of this already. As soon as a fix becomes apparent (and is working for me) I'll have it up in my queue ready for Pat to pick up
 
Old 12-16-2014, 10:44 AM   #15
pchristy
Senior Member
 
Registered: Oct 2012
Location: South Devon, UK
Distribution: Slackware
Posts: 1,126

Original Poster
Rep: Reputation: Disabled
ppr:kut: I found a bug report about this up on the sane bug tracker and added some comments about my experiences. I've had a message from the developer assigned to the bug saying he's committed work-around for the kernel bug at the heart of this (his words, not mine!) which is working for him. He's asked for us to try it by downloading from the git repository. Unfortunately, every time I try, it tells me I'm downloading an empty repository! Any ideas where this might be hiding?

He also says it should be in the snapshot tomorrow, but I can't find where they keep their snapshots either!

--
Pete
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Emerge driving me insane kahlil88 Linux - Distributions 2 03-09-2009 05:21 AM
snd_hda_intel driving me insane TrevorBradley Linux - Hardware 1 02-11-2007 08:18 PM
SANE to INSANE mikeghet Linux - Newbie 2 06-16-2005 11:11 PM
Sendmail is driving me insane. Please help me. ecroskey Linux - Newbie 1 03-02-2003 06:02 AM
Sane or insane? Johng Linux - Software 76 12-25-2002 05:12 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:43 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration