[sane-devel] FC 2, hotplug and sane
Hi,
I've installed a FC2 and updated. I can use sane, but only as root. I've
been googling and reading and narrowed the problem to the USB interface
to my Epson scanner. According to
http://www.sane-project.org/README.linux, hotplug (which is compiled in
the kernel) and /etc/hotplug/usb/libusbscanner (pasted in below
signature) should enable useracces to the scanner, if
Usually you must just add the users that are allowed to access the scanner to
group scanner
I don't know how to do that.
If I unplug and plug the scanner, user acces is allowed, but not on boot up !
Any help will bee appriciated :-)
Regards Torben
Contents af libusbscanner:
#!/bin/bash
# $Id: libusbscanner,v 1.1 2004/05/04 13:05:27 twaugh Exp $
#
# /etc/hotplug/usb/libusbscanner
#
# Sets up newly plugged in USB scanner so that the user who owns
# the console according to pam_console can access it from user space
#
# Note that for this script to work, you'll need all of the following:
# a) a line in the file /etc/hotplug/usermap that corresponds to the
#camera you are using.
# b) a setup using pam_console creates the respective lock files
#containing the name of the respective user. You can check for that
#by executing echo `cat /var/{run,lock}/console.lock` and
#verifying the appropriate user is mentioned somewhere there.
# c) a Linux kernel supporting hotplug and usbdevfs
# d) the hotplug package (http://linux-hotplug.sourceforge.net/)
#
# In the usermap file, the first field usb module should be named
# libusbscanner like this script.
#
if [ ${ACTION} = add ] [ -f ${DEVICE} ]
then
# New code, using lock files instead of copying /dev/console permissions
# This also works with non-gdm logins (e.g. on a virtual terminal)
# Idea and code from Nalin Dahyabhai na...@redhat.com
if [ -f /var/run/console.lock ]
then
CONSOLEOWNER=`cat /var/run/console.lock`
elif [ -f /var/lock/console.lock ]
then
CONSOLEOWNER=`cat /var/lock/console.lock`
else
CONSOLEOWNER=
fi
if [ -n $CONSOLEOWNER ]
then
chmod ${DEVICE}
chown $CONSOLEOWNER ${DEVICE}
chmod 0600 ${DEVICE}
fi
fi
--
It's trivial to make fun of Microsoft products,
but it takes a real man to make them work,
and a god to make them do anything useful.
[sane-devel] FC 2, hotplug and sane
Hi, On Tue, Oct 26, 2004 at 03:30:00PM +0200, Torben Andersen wrote: I've installed a FC2 and updated. I can use sane, but only as root. I've been googling and reading and narrowed the problem to the USB interface to my Epson scanner. According to http://www.sane-project.org/README.linux, hotplug (which is compiled in the kernel) and /etc/hotplug/usb/libusbscanner (pasted in below signature) should enable useracces to the scanner, if Usually you must just add the users that are allowed to access the scanner to group scanner I don't know how to do that. man gpasswd man usermod man groups man group If I unplug and plug the scanner, user acces is allowed, In this case hotplug is set up correctly. but not on boot up ! I have heard rumors about this problem and was told that coldplug would help. But: #!/bin/bash # $Id: libusbscanner,v 1.1 2004/05/04 13:05:27 twaugh Exp $ This is not the libusbscanner script from the sane-backends package. It doesn't seem to work by using groups but by giving access to the scanner to anyone who is logged-in locally. Quite strange. Anyway, for details ask your distributor. I haven't looked at the details but if the device is plugged-in while nobody is logged in I guess only root can access it. Or do I misunderstand the script? Bye, Henning
[sane-devel] FC 2, hotplug and sane
Torben Andersen wrote: Hi, I've installed a FC2 and updated. I can use sane, but only as root. I've been googling and reading and narrowed the problem to the USB interface to my Epson scanner. According to http://www.sane-project.org/README.linux, hotplug (which is compiled in the kernel) and /etc/hotplug/usb/libusbscanner (pasted in below signature) should enable useracces to the scanner, if This is a known issue, see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=124053 Klaus
[sane-devel] Suse-Kernel 2.6.5 and umax astra 1220 S
Hello list, when I recently updated from Suse 8.2 (2.4er kernel) to Suse 9.1 with kernel 2.6.5, my scanner, a UMAX Astra 1220 S which had worked well troughout all the kernel-versons of the last years, was gone without the slightest trace. scanimage -L, sane-find-scanner and the other little helpers remainend silent about it. Maybe it's not a really sane-problem but a controller-problem. The controller in use is a Dawicontrol DC-2975-C which connected till now over the sym53c8xx/ncr53c8xx-module. The strange thing is that with the kernel 2.6.1 of the knoppix 3.4-distribution everthing works as usual. The Suse-Kernel still comes with the sym53c8xx-module, but something seems to be wrong with it. I wasn't very close to the list in the last few months, so perhaps I missed some relevant stuff - sorry if I ask those damn old questions. Is anybody out there who expierienced a similar kind of behaviour and has got a solution for it? Thanks in advance Wolfram Heider
[sane-devel] Suse-Kernel 2.6.5 and umax astra 1220 S
Wolfram Heider wrote: Hello list, when I recently updated from Suse 8.2 (2.4er kernel) to Suse 9.1 with kernel 2.6.5, my scanner, a UMAX Astra 1220 S which had worked well troughout all the kernel-versons of the last years, was gone without the slightest trace. scanimage -L, sane-find-scanner and the other little helpers remainend silent about it. Maybe it's not a really sane-problem but a controller-problem. yes, it's most likely a problem in the Linux SCSI system. To look for SCSI scanners, sane-find-scanner reads /proc/scsi/scsi, and the contents of this proc file is managed by the SCSI system of the kernel. The controller in use is a Dawicontrol DC-2975-C which connected till now over the sym53c8xx/ncr53c8xx-module. The strange thing is that with the kernel 2.6.1 of the knoppix 3.4-distribution everthing works as usual. The Suse-Kernel still comes with the sym53c8xx-module, but something seems to be wrong with it. Are you sure that the sym/ncr53c8xx module is indeed loaded? And if it loaded, do you get any error messages in /var/log/messages? The sym/ncr53c8xx drivers offer many parameters; perhaps it helps to play with some of them. The file kernel source dir/drivers/scsi/README.ncr53c8xx describes these parameters quite detailed. Abel
[sane-devel] FC 2, hotplug and sane - SOLVED
Torben Andersen wrote: Thanks to Klaus-Peter. His link had a solution: Put chmod 0666 $DEVICE in the bottom of the libusbscanner. I don't know if its a perfect solution, but it certainly worked. That's what I've done, and nobody ever gave me a good reason why this shouln't be done. Klaus
[sane-devel] Suse-Kernel 2.6.5 and umax astra 1220 S
Am Dienstag, 26. Oktober 2004 22:11 schrieben Sie: Wolfram Heider wrote: Hello list, when I recently updated from Suse 8.2 (2.4er kernel) to Suse 9.1 with kernel 2.6.5, my scanner, a UMAX Astra 1220 S which had worked well troughout all the kernel-versons of the last years, was gone without the slightest trace. scanimage -L, sane-find-scanner and the other little helpers remainend silent about it. Maybe it's not a really sane-problem but a controller-problem. yes, it's most likely a problem in the Linux SCSI system. To look for SCSI scanners, sane-find-scanner reads /proc/scsi/scsi, and the contents of this proc file is managed by the SCSI system of the kernel. The controller in use is a Dawicontrol DC-2975-C which connected till now over the sym53c8xx/ncr53c8xx-module. The strange thing is that with the kernel 2.6.1 of the knoppix 3.4-distribution everthing works as usual. The Suse-Kernel still comes with the sym53c8xx-module, but something seems to be wrong with it. Are you sure that the sym/ncr53c8xx module is indeed loaded? And if it loaded, do you get any error messages in /var/log/messages? The sym/ncr53c8xx drivers offer many parameters; perhaps it helps to play with some of them. The file kernel source dir/drivers/scsi/README.ncr53c8xx describes these parameters quite detailed. Abel Good evening; Abel thanks for your quick reply. The sym53c8xx modul isn't loadde at boottime. When loaded by hand via modprobe it takes suspiciously long time to come up - and finanally nothing has changed - everthing dead as the cemetry of Chicago. Only lspci gives a hint that there is something in the slot. I'll take your advice and play around a little bit with the driver parameters. See you later. Wolfram ( I first choosed the wrong reply address - sorry)
[sane-devel] feeder for scanner
Hi, I would like to buy a nice high end scanner that is supported that has a document feeder. Any suggestions? Any experiences? How do you handle a jam? What kind of speed. How many documents can fit? Herb Pathfinders Software
