Epson USB scanner permissions in 9.2
I fear we may have done this in the three weeks I've been away, but, extensive googling hasn't got me where I'm going yet: Epson Perfection 2450 Photo scanner, problem free with 2.4 kernel series, problems with 9.1, partly resolved with kind help of many, partic Kastus and Sid. Now different prob, maybe easier? Kooka works absolutely fine as root, so I am assuming not much is broken and thus not posting scads of logs. But will not work as user. Over what should I shake a rubber chicken to allow users to scan, or is it the full horror again searching through 25,000 nameless files? Cheers Fergus
Hello, On Nov 22 14:42 Fergus Wilde wrote (shortened):
Kooka works ... as root ... But will not work as user.
USB scanner access for normal users should work well since 9.2, see http://portal.suse.com/sdb/en/2004/10/jsmeix_scanner-setup-92.html Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On Monday 22 November 2004 15:27, Johannes Meixner wrote:
Hello,
On Nov 22 14:42 Fergus Wilde wrote (shortened):
Kooka works ... as root ... But will not work as user.
USB scanner access for normal users should work well since 9.2, see http://portal.suse.com/sdb/en/2004/10/jsmeix_scanner-setup-92.html
Hi Johannes - thanks for the link. My scanner isn't working out of the box for regular users, certainly: the problem seems to be soluble by changing the ownership of the proc files: pc11:/home/fergus # ls -l /proc/bus/usb/001/* -rw-r--r-- 1 root root 43 2004-11-23 08:34 /proc/bus/usb/001/001 -rw-r--r-- 1 root root 50 2004-11-23 08:37 /proc/bus/usb/001/002 and after I do pc11:/home/fergus # chown fergus:users /proc/bus/usb/001/* I can then access the scanner via Kooka just fine. So something about the PAM / resmgr part of the setup isn't working right in the default install? Here's /var/log/messages while I start kooka as a user before modifying permissions of the above files: Nov 23 08:36:29 pc11 kooka: resmgr: server response code 502 Nov 23 08:36:29 pc11 last message repeated 8 times Nov 23 08:36:29 pc11 kooka: resmgr: server response code 500 Nov 23 08:36:29 pc11 last message repeated 2 times Nov 23 08:36:29 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:29 pc11 last message repeated 3 times Nov 23 08:36:29 pc11 kooka: resmgr: server response code 500 Nov 23 08:36:30 pc11 last message repeated 3 times Nov 23 08:36:30 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:30 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:30 pc11 kooka: resmgr: server response code 500 Nov 23 08:36:30 pc11 last message repeated 2 times Nov 23 08:36:30 pc11 kooka: resmgr: communication failure: Broken pipe Nov 23 08:36:30 pc11 kooka: resmgr: server response code 500 Nov 23 08:36:30 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:30 pc11 last message repeated 3 times Nov 23 08:36:30 pc11 kooka: resmgr: server response code 500 Nov 23 08:36:30 pc11 last message repeated 3 times Nov 23 08:36:30 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:30 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:30 pc11 kooka: resmgr: server response code 500 Nov 23 08:36:30 pc11 last message repeated 4 times Nov 23 08:36:30 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:30 pc11 last message repeated 3 times Nov 23 08:36:30 pc11 kooka: resmgr: server response code 500 Nov 23 08:36:30 pc11 last message repeated 3 times Nov 23 08:36:30 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:30 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:30 pc11 kooka: resmgr: server response code 500 Nov 23 08:36:30 pc11 last message repeated 4 times Nov 23 08:36:30 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:30 pc11 last message repeated 3 times Nov 23 08:36:30 pc11 kooka: resmgr: server response code 500 Nov 23 08:36:30 pc11 last message repeated 3 times Nov 23 08:36:30 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:30 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:30 pc11 kooka: resmgr: server response code 500 Nov 23 08:37:06 pc11 kernel: usb 1-2: bulk timeout on ep1in Nov 23 08:37:06 pc11 kernel: usb 1-2: usbfs: USBDEVFS_BULK failed ep 0x81 len 1 ret -110 And it doesn't work. Here's me starting kooka once I have modified the ownership of proc/bus/usb/001/*: things start ok for me and I can scan, but it takes about a minute and resmgr still looks unhappy: Nov 23 08:58:48 pc11 kooka: resmgr: server response code 502 Nov 23 08:58:48 pc11 last message repeated 8 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 500 Nov 23 08:58:48 pc11 last message repeated 2 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 last message repeated 3 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 500 Nov 23 08:58:48 pc11 last message repeated 3 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 kooka: resmgr: server response code 500 Nov 23 08:58:48 pc11 last message repeated 4 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 last message repeated 3 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 500 Nov 23 08:58:48 pc11 last message repeated 3 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 kooka: resmgr: server response code 500 Nov 23 08:58:48 pc11 last message repeated 4 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 last message repeated 3 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 500 Nov 23 08:58:48 pc11 last message repeated 3 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 kooka: resmgr: server response code 500 Nov 23 08:58:48 pc11 last message repeated 4 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 last message repeated 3 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 500 Nov 23 08:58:48 pc11 last message repeated 3 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 kooka: resmgr: server response code 500 Nov 23 08:59:01 pc11 /usr/sbin/cron[5869]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Nov 23 08:59:18 pc11 kernel: usb 1-2: bulk timeout on ep1in Nov 23 08:59:18 pc11 kernel: usb 1-2: usbfs: USBDEVFS_BULK failed ep 0x81 len 1 ret -110 Nov 23 08:59:18 pc11 kernel: ehci_hcd 0000:00:1d.7: qh dde71180 (#17) state 1 despite the 'failed' message, I can still work ... but would have to manually reset ownership of these files each time I boot, or set things up to modify them in boot.local, or somewhere ... presumably this isn't the safe or cool way to do it. Any other thoughts? For now I am going to implement Miquel Noguera's suggestion of doing this in /etc/fstab to see if it fixes the problem: usbfs /proc/bus/usb usbfs defaults,devmode=0666 0 0 But I imagine this isn't as secure as what you outline in your support article. I don't think I know enough about PAM or resmgr to fix that without help though. Cheers Fergus
Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
Hello again Johannes / interested parties, On Tuesday 23 November 2004 09:13, Fergus Wilde wrote:
On Monday 22 November 2004 15:27, Johannes Meixner wrote:
Hello,
On Nov 22 14:42 Fergus Wilde wrote (shortened):
Kooka works ... as root ... But will not work as user.
USB scanner access for normal users should work well since 9.2, see http://portal.suse.com/sdb/en/2004/10/jsmeix_scanner-setup-92.html
Hi Johannes - thanks for the link. My scanner isn't working out of the box for regular users, certainly: the problem seems to be soluble by changing the ownership of the proc files:
pc11:/home/fergus # ls -l /proc/bus/usb/001/* -rw-r--r-- 1 root root 43 2004-11-23 08:34 /proc/bus/usb/001/001 -rw-r--r-- 1 root root 50 2004-11-23 08:37 /proc/bus/usb/001/002
and after I do pc11:/home/fergus # chown fergus:users /proc/bus/usb/001/*
I can then access the scanner via Kooka just fine. So something about the PAM / resmgr part of the setup isn't working right in the default install?
<snip all posted logs>
For now I am going to implement Miquel Noguera's suggestion of doing this in /etc/fstab to see if it fixes the problem:
usbfs /proc/bus/usb usbfs defaults,devmode=0666 0 0
But I imagine this isn't as secure as what you outline in your support article. I don't think I know enough about PAM or resmgr to fix that without help though.
Changing the devmode to the devmode of the beast as outlined above produces the following result: kooka now starts working _exactly every other time_ it is started. on occasions A,C,E, etc, it starts in seconds and doesn't work. On occasions B,D,F, etc it starts after struggling for about a minute and then I can scan. So something somewhere is toggling its ability to function correctly on each instance of being started and exited - who, what where, how do I fix this? What a pity the perfect functioning of the 2.4 series was binned. Cheers Fergus
Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On Tuesday 23 November 2004 09:44, Fergus Wilde wrote: An updated version of resmgr just became available via YOU - doesn't make any difference to the problem, scanner function starts exactly every other time that kooka is started.
Hello again Johannes / interested parties,
On Tuesday 23 November 2004 09:13, Fergus Wilde wrote:
On Monday 22 November 2004 15:27, Johannes Meixner wrote:
Hello,
On Nov 22 14:42 Fergus Wilde wrote (shortened):
Kooka works ... as root ... But will not work as user.
USB scanner access for normal users should work well since 9.2, see http://portal.suse.com/sdb/en/2004/10/jsmeix_scanner-setup-92.html
Hi Johannes - thanks for the link. My scanner isn't working out of the box for regular users, certainly: the problem seems to be soluble by changing the ownership of the proc files:
pc11:/home/fergus # ls -l /proc/bus/usb/001/* -rw-r--r-- 1 root root 43 2004-11-23 08:34 /proc/bus/usb/001/001 -rw-r--r-- 1 root root 50 2004-11-23 08:37 /proc/bus/usb/001/002
and after I do pc11:/home/fergus # chown fergus:users /proc/bus/usb/001/*
I can then access the scanner via Kooka just fine. So something about the PAM / resmgr part of the setup isn't working right in the default install?
<snip all posted logs>
For now I am going to implement Miquel Noguera's suggestion of doing this in /etc/fstab to see if it fixes the problem:
usbfs /proc/bus/usb usbfs defaults,devmode=0666 0 0
But I imagine this isn't as secure as what you outline in your support article. I don't think I know enough about PAM or resmgr to fix that without help though.
Changing the devmode to the devmode of the beast as outlined above produces the following result: kooka now starts working _exactly every other time_ it is started. on occasions A,C,E, etc, it starts in seconds and doesn't work. On occasions B,D,F, etc it starts after struggling for about a minute and then I can scan.
So something somewhere is toggling its ability to function correctly on each instance of being started and exited - who, what where, how do I fix this?
What a pity the perfect functioning of the 2.4 series was binned. Cheers Fergus
Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
El Lunes, 22 de Noviembre de 2004 15:42, Fergus Wilde escribió:
Epson Perfection 2450 Photo scanner [...] works absolutely fine as root, so I am assuming not much is broken and thus not posting scads of logs. But will not work as user.
Simply modify your /etc/fstab in that way: usbfs /proc/bus/usb usbfs defaults,devmode=0666 0 0 Miquel
On Tuesday 23 November 2004 07:28, Miquel A. Noguera wrote:
El Lunes, 22 de Noviembre de 2004 15:42, Fergus Wilde escribió:
Epson Perfection 2450 Photo scanner [...] works absolutely fine as root, so I am assuming not much is broken and thus not posting scads of logs. But will not work as user.
Simply modify your /etc/fstab in that way:
usbfs /proc/bus/usb usbfs defaults,devmode=0666 0 0
Thanks Miquel, kind of you to take the time. I implemented your suggestion, with mixed results (!) - if still interested, please see my replies to Johannes Meixner.
Miquel
On Monday 22 November 2004 11:28 pm, Miquel A. Noguera wrote:
El Lunes, 22 de Noviembre de 2004 15:42, Fergus Wilde escribió:
Epson Perfection 2450 Photo scanner [...] works absolutely fine as root, so I am assuming not much is broken and thus not posting scads of logs. But will not work as user.
Simply modify your /etc/fstab in that way:
usbfs /proc/bus/usb usbfs defaults,devmode=0666 0 0
Miquel
You may want to look at the following document on the SuSE knowledge base, it is called configuring scanners from SuSE Linux 9.2. It should help with other versions also. http://portal.suse.com/sdb/en/2004/jsmeix_scanner-setup-92.html If this link does not work go to www.suse.com and search their knowledge base. Hopefully this will help, I'm in the same boat with a new scanner from Epson but I'm on 9.1 and its slightly different. -- Russ
On Tuesday 23 November 2004 15:42, Russ wrote:
On Monday 22 November 2004 11:28 pm, Miquel A. Noguera wrote:
El Lunes, 22 de Noviembre de 2004 15:42, Fergus Wilde escribió:
Epson Perfection 2450 Photo scanner [...] works absolutely fine as root, so I am assuming not much is broken and thus not posting scads of logs. But will not work as user.
Simply modify your /etc/fstab in that way:
usbfs /proc/bus/usb usbfs defaults,devmode=0666 0 0
Miquel
You may want to look at the following document on the SuSE knowledge base, it is called configuring scanners from SuSE Linux 9.2. It should help with other versions also.
http://portal.suse.com/sdb/en/2004/jsmeix_scanner-setup-92.html
Thanks Russ, Johannes sent me this version of the link to his article, which works: http://portal.suse.com/sdb/en/2004/10/jsmeix_scanner-setup-92.html And I have read it - but I can't figure out yet how to get rid of the access problems without manually resetting permissions. Miquel's advice (quoted above) worked to a point, but the scanner is still completely hit and miss. Not as bad as 9.1 though, but bad enough that I can't install 9.2 onto my main desktop yet. There is something quite sick about resmgr: here it is trying to process my various requests to get the **** scanner working: Nov 23 15:55:17 pc11 kooka: resmgr: server response code 502 Nov 23 15:55:17 pc11 last message repeated 8 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 500 Nov 23 15:55:17 pc11 last message repeated 2 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 last message repeated 3 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 500 Nov 23 15:55:17 pc11 last message repeated 3 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 kooka: resmgr: server response code 500 Nov 23 15:55:17 pc11 last message repeated 4 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 last message repeated 3 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 500 Nov 23 15:55:17 pc11 last message repeated 3 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 kooka: resmgr: server response code 500 Nov 23 15:55:17 pc11 last message repeated 4 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 last message repeated 3 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 500 Nov 23 15:55:17 pc11 last message repeated 3 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 kooka: resmgr: server response code 500 Nov 23 15:55:17 pc11 last message repeated 4 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 last message repeated 3 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 500 Nov 23 15:55:17 pc11 last message repeated 3 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 kooka: resmgr: server response code 500 Nov 23 15:55:18 pc11 kernel: ehci_hcd 0000:00:1d.7: qh def5a700 (#17) state 1 Nov 23 15:56:04 pc11 kernel: usb 4-2: bulk timeout on ep1in Nov 23 15:56:04 pc11 kernel: usb 4-2: usbfs: USBDEVFS_BULK failed ep 0x81 len 1 ret -110 Nov 23 15:56:54 pc11 kernel: usb 4-2: bulk timeout on ep1in Nov 23 15:56:54 pc11 kernel: usb 4-2: usbfs: USBDEVFS_BULK failed ep 0x81 len 1 ret -110 Nov 23 15:57:06 pc11 xsane: resmgr: server response code 502 Nov 23 15:57:06 pc11 last message repeated 8 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 500 Nov 23 15:57:06 pc11 last message repeated 2 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 last message repeated 3 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 500 Nov 23 15:57:06 pc11 last message repeated 3 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 xsane: resmgr: server response code 500 Nov 23 15:57:06 pc11 last message repeated 4 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 last message repeated 3 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 500 Nov 23 15:57:06 pc11 last message repeated 3 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 xsane: resmgr: server response code 500 Nov 23 15:57:06 pc11 last message repeated 4 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 last message repeated 3 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 500 Nov 23 15:57:06 pc11 last message repeated 3 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 xsane: resmgr: server response code 500 Nov 23 15:57:06 pc11 last message repeated 4 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 xsane: resmgr: communication failure: Broken pipe Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 xsane: resmgr: server response code 500 Nov 23 15:57:06 pc11 last message repeated 3 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 xsane: resmgr: server response code 500 Nov 23 15:57:36 pc11 kernel: usb 4-2: bulk timeout on ep1in Nov 23 15:57:36 pc11 kernel: usb 4-2: usbfs: USBDEVFS_BULK failed ep 0x81 len 1 ret -110 Nov 23 15:57:36 pc11 kernel: ehci_hcd 0000:00:1d.7: qh def5a780 (#17) state 1 Nov 23 15:59:01 pc11 /usr/sbin/cron[8573]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Nov 23 15:59:08 pc11 xsane: resmgr: server response code 502 Nov 23 15:59:08 pc11 last message repeated 8 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 500 Nov 23 15:59:08 pc11 last message repeated 2 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 last message repeated 3 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 500 Nov 23 15:59:08 pc11 last message repeated 3 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 xsane: resmgr: server response code 500 Nov 23 15:59:08 pc11 last message repeated 4 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 last message repeated 3 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 500 Nov 23 15:59:08 pc11 last message repeated 3 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 xsane: resmgr: server response code 500 Nov 23 15:59:08 pc11 last message repeated 4 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 last message repeated 3 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 500 Nov 23 15:59:08 pc11 last message repeated 3 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 xsane: resmgr: server response code 500 Nov 23 15:59:08 pc11 last message repeated 4 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 last message repeated 3 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 500 Nov 23 15:59:08 pc11 last message repeated 3 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 xsane: resmgr: server response code 500 Nov 23 15:59:38 pc11 kernel: usb 4-2: bulk timeout on ep1in Nov 23 15:59:38 pc11 kernel: usb 4-2: usbfs: USBDEVFS_BULK failed ep 0x81 len 1 ret -110 Nov 23 15:59:38 pc11 kernel: ehci_hcd 0000:00:1d.7: qh def5a800 (#17) state 1 Even when the device can be made to work, by setting very easy permissions on ls -ld /proc/bus/usb/001: drwxrwxrwx 2 root root 0 2004-11-23 13:46 001 (manually set) ls -l /proc/bus/usb/001/* -rw-rw-rw- 1 root root 43 2004-11-23 13:46 /proc/bus/usb/001/001 (created by Miquel's dodge with /etc/fstab) you can see how resmgr struggles, and it takes the machine at least a full minute to find the scanner. Wassup?
If this link does not work go to www.suse.com and search their knowledge base. Hopefully this will help, I'm in the same boat with a new scanner from Epson but I'm on 9.1 and its slightly different. -- Russ
On Tuesday 23 November 2004 08:28 am, Fergus Wilde wrote:
On Tuesday 23 November 2004 15:42, Russ wrote:
On Monday 22 November 2004 11:28 pm, Miquel A. Noguera wrote:
El Lunes, 22 de Noviembre de 2004 15:42, Fergus Wilde escribió:
Epson Perfection 2450 Photo scanner [...] works absolutely fine as root, so I am assuming not much is broken and thus not posting scads of logs. But will not work as user.
Simply modify your /etc/fstab in that way:
usbfs /proc/bus/usb usbfs defaults,devmode=0666 0 0
Miquel
You may want to look at the following document on the SuSE knowledge base, it is called configuring scanners from SuSE Linux 9.2. It should help with other versions also.
http://portal.suse.com/sdb/en/2004/jsmeix_scanner-setup-92.html
Thanks Russ, Johannes sent me this version of the link to his article, which works:
http://portal.suse.com/sdb/en/2004/10/jsmeix_scanner-setup-92.html
And I have read it - but I can't figure out yet how to get rid of the access problems without manually resetting permissions. Miquel's advice (quoted above) worked to a point, but the scanner is still completely hit and miss. Not as bad as 9.1 though, but bad enough that I can't install 9.2 onto my main desktop yet. There is something quite sick about resmgr: here it is trying to process my various requests to get the **** scanner working:
Nov 23 15:55:17 pc11 kooka: resmgr: server response code 502 Nov 23 15:55:17 pc11 last message repeated 8 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 500 Nov 23 15:55:17 pc11 last message repeated 2 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 last message repeated 3 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 500 Nov 23 15:55:17 pc11 last message repeated 3 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 kooka: resmgr: server response code 500 Nov 23 15:55:17 pc11 last message repeated 4 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 last message repeated 3 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 500 Nov 23 15:55:17 pc11 last message repeated 3 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 kooka: resmgr: server response code 500 Nov 23 15:55:17 pc11 last message repeated 4 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 last message repeated 3 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 500 Nov 23 15:55:17 pc11 last message repeated 3 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 kooka: resmgr: server response code 500 Nov 23 15:55:17 pc11 last message repeated 4 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 last message repeated 3 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 500 Nov 23 15:55:17 pc11 last message repeated 3 times Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 kooka: resmgr: server response code 501 Nov 23 15:55:17 pc11 kooka: resmgr: server response code 500 Nov 23 15:55:18 pc11 kernel: ehci_hcd 0000:00:1d.7: qh def5a700 (#17) state 1 Nov 23 15:56:04 pc11 kernel: usb 4-2: bulk timeout on ep1in Nov 23 15:56:04 pc11 kernel: usb 4-2: usbfs: USBDEVFS_BULK failed ep 0x81 len 1 ret -110 Nov 23 15:56:54 pc11 kernel: usb 4-2: bulk timeout on ep1in Nov 23 15:56:54 pc11 kernel: usb 4-2: usbfs: USBDEVFS_BULK failed ep 0x81 len 1 ret -110 Nov 23 15:57:06 pc11 xsane: resmgr: server response code 502 Nov 23 15:57:06 pc11 last message repeated 8 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 500 Nov 23 15:57:06 pc11 last message repeated 2 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 last message repeated 3 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 500 Nov 23 15:57:06 pc11 last message repeated 3 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 xsane: resmgr: server response code 500 Nov 23 15:57:06 pc11 last message repeated 4 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 last message repeated 3 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 500 Nov 23 15:57:06 pc11 last message repeated 3 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 xsane: resmgr: server response code 500 Nov 23 15:57:06 pc11 last message repeated 4 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 last message repeated 3 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 500 Nov 23 15:57:06 pc11 last message repeated 3 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 xsane: resmgr: server response code 500 Nov 23 15:57:06 pc11 last message repeated 4 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 xsane: resmgr: communication failure: Broken pipe Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 xsane: resmgr: server response code 500 Nov 23 15:57:06 pc11 last message repeated 3 times Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 xsane: resmgr: server response code 501 Nov 23 15:57:06 pc11 xsane: resmgr: server response code 500 Nov 23 15:57:36 pc11 kernel: usb 4-2: bulk timeout on ep1in Nov 23 15:57:36 pc11 kernel: usb 4-2: usbfs: USBDEVFS_BULK failed ep 0x81 len 1 ret -110 Nov 23 15:57:36 pc11 kernel: ehci_hcd 0000:00:1d.7: qh def5a780 (#17) state 1 Nov 23 15:59:01 pc11 /usr/sbin/cron[8573]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Nov 23 15:59:08 pc11 xsane: resmgr: server response code 502 Nov 23 15:59:08 pc11 last message repeated 8 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 500 Nov 23 15:59:08 pc11 last message repeated 2 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 last message repeated 3 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 500 Nov 23 15:59:08 pc11 last message repeated 3 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 xsane: resmgr: server response code 500 Nov 23 15:59:08 pc11 last message repeated 4 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 last message repeated 3 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 500 Nov 23 15:59:08 pc11 last message repeated 3 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 xsane: resmgr: server response code 500 Nov 23 15:59:08 pc11 last message repeated 4 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 last message repeated 3 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 500 Nov 23 15:59:08 pc11 last message repeated 3 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 xsane: resmgr: server response code 500 Nov 23 15:59:08 pc11 last message repeated 4 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 last message repeated 3 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 500 Nov 23 15:59:08 pc11 last message repeated 3 times Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 xsane: resmgr: server response code 501 Nov 23 15:59:08 pc11 xsane: resmgr: server response code 500 Nov 23 15:59:38 pc11 kernel: usb 4-2: bulk timeout on ep1in Nov 23 15:59:38 pc11 kernel: usb 4-2: usbfs: USBDEVFS_BULK failed ep 0x81 len 1 ret -110 Nov 23 15:59:38 pc11 kernel: ehci_hcd 0000:00:1d.7: qh def5a800 (#17) state 1
Even when the device can be made to work, by setting very easy permissions on
ls -ld /proc/bus/usb/001:
drwxrwxrwx 2 root root 0 2004-11-23 13:46 001 (manually set)
ls -l /proc/bus/usb/001/* -rw-rw-rw- 1 root root 43 2004-11-23 13:46 /proc/bus/usb/001/001
(created by Miquel's dodge with /etc/fstab)
you can see how resmgr struggles, and it takes the machine at least a full minute to find the scanner. Wassup?
If this link does not work go to www.suse.com and search their knowledge base. Hopefully this will help, I'm in the same boat with a new scanner from Epson but I'm on 9.1 and its slightly different. -- Russ
Your alittle ahead of me. Iscan and Koola work if I start my system as root. If I start with my user ID neither work even if I su then try it. There is something missing. -- Russ
participants (4)
-
Fergus Wilde -
Johannes Meixner -
Miquel A. Noguera -
Russ