Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
There is less than 12 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have seen many similar complaints around on the web but no suggestion which actually works.
I have ubuntu 8.10 amd64 2.6.27-11 kernel, xsane & friends installed. Everything works perfectly when I scan as root. Scanner is detected as non-root as well:
# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.
# No SCSI scanners found. If you expected something different, make sure that
# you have loaded a kernel SCSI driver for your SCSI adapter.
found USB scanner (vendor=0x04a9, product=0x2213, chip=GL841?) at libusb:002:010
# Your USB scanner was (probably) detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.
# You may want to run this program as root to find all devices. Once you
# found the scanner devices, be sure to adjust access permissions as
but scanimage does not work:
siim@Shiva:~$ scanimage -L
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
when i strace the process, I see a lot of messages like:
Here is the letter from Linux Format May 2009 Issue 118:
"It sounds like your scanner device is being created with unsuitable permissions A simple test is to run these two commands, both as root and a normal user.
The first should discover the scanner no matter who runs it, whereas the second can only access the scanner if it has permission. If this one fails as your user, you definatly have a permission problem.
With USB scanners, the device name varies each time you connect it, so you cannot simply run a chown or chmod command from your startup scripts. You'll have to get dirty with udev, but its not really that hard. First you need to identify your scanner - you can do this with dmesg, which will include something like this:
usb 2-1: New USB device found,
usb 2-1: New USB device strings: Mfr=1,
usb 2-1: Product: CanoScan
usb 2-1: Manufacturer: Canon
Or you can use lsusb
Bus 002 Device 002: ID 04a9:221c Canon, Inc.
CanoScan LiDE 60
Or the tool that comes with Sane
All of these will give you the vendor and product codes of the scanner. These examples are with a Canon scanner, so you should expect to get different values with your HP. Now you create a udev rule in /etc/udev/rules.d/10-scanner.rules
The name must end in .rules and the leading 10 ensures its processed before default rules. Substitute your own numbers in here:
This makes the scanner device node readable and writeable by members of the scanner group. You then need to create the group and add yourself to it, as root, with:
groupadd -r scanner
gpasswd -a YOUR_USERNAME scanner
Alternatively, if you're the only user of the computer, put your own group name in the udev rule instead of scanner. Udev will pick up the changes immediatly; you only need to reconnect or power-cycle your scanner. If you made group changes you will need to logout and back in."
Hope that helps, that was a lot of typing, many thanks to Linux Format, if it works, why not buy their next issue
seems like there is a bit more than that. After a reboot I started to get weird errors, related to wrong device permissions (e.g. /dev/null was owned by scanner and not allowed to write to for the world). So I modified the rules