I'm embarrassed to say this I figured this one out on my own--my daughter pulled the USB cable out of the back of the scanner. Sorry for any inconvenience. I'll be more careful before my next post.
On Oct 25, 2005, at 12:57 PM, Darrell Styner wrote: > Hi, > > I've just installed the latest libusb and sane-backends packages > from ellert.se. When I run sane-find-scanner it sees my HP 6110 > AIO, but not my fi-4120C2. If I disconnect the HP then it doesn't > find anything on the USB ports. The 4120 works fine on my Windows > PC, so I know there's nothing wrong with the scanner. I'm running > Mac OS 10.4.2 on a Dual 2GHz G5. Any ideas? > > Here's some output: > > sane-find-scanner > > # 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=0x03f0 [Hewlett-Packard], product=0x2d11 > [OfficeJet 6100 Series]) at libusb:003:002-03f0-2d11-00-00 > # 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 > # necessary. > > > otool -L /usr/local/bin/scanimage > /usr/local/bin/scanimage: > /usr/local/lib/libsane.1.dylib (compatibility version > 2.0.0, current version 2.16.0) > /usr/local/lib/libusb-0.1.4.dylib (compatibility version > 9.0.0, current version 9.3.0) > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, > current version 88.2.1) > /System/Library/Frameworks/CoreFoundation.framework/ > Versions/A/CoreFoundation (compatibility version 150.0.0, current > version 363.0.0) > /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit > (compatibility version 1.0.0, current version 270.0.0) > /usr/lib/libmx.A.dylib (compatibility version 1.0.0, > current version 92.0.0) > > Darrell Styner > > Darrell Styner darr...@avanta.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20051025/95b6fea6/attachment.htm From o...@member.fsf.org Wed Oct 26 12:11:41 2005 From: o...@member.fsf.org (Olaf Meeuwissen) Date: Wed Oct 26 12:08:14 2005 Subject: [sane-devel] Sane doesn't create a scanner device In-Reply-To: <435e7fb5.9020...@gmx.net> (dark mail's message of "Tue, 25 Oct 2005 20:55:49 +0200") References: <435d62fa.9070...@gmx.net> <d6f70394-6571-4471-97b6-06f955f48...@khk.net> <871x29j19l....@zpost.plala.or.jp> <435e7fb5.9020...@gmx.net> Message-ID: <87ll0g5vgi....@zpost.plala.or.jp> CC:ing sane-devel for the benefit of archival purposes. dark_m...@gmx.net writes: > Actually, I already have switched to udev. So gathering from your > answer I guess iscan and udev don't work together. Let me put it this way, iscan does not have any udev support so when you plug in your device udev may not recognise it as a scanner. The upshot of that is that the device node may not get the permissions needed iscan and other SANE frontends to access it. You will need read and write access to the device for it to work. Just to make sure, check that the /proc/bus/usb/###/### entry that corresponds to your RX420 has read/write access for everyone. If it doesn't, then, as root, do # chmod 0666 /proc/bus/usb/###/### and give it another try. # For the security conscious boys and girls out there, I know that # this is not a good idea in general, but we're just trying to get # the damn thing to work here first. > I tried again to make the scanner work, without result. It makes no > difference if I'm a normal user or root, neither the with epson- nor > with the iscan-backend I get it to work. Now, if it also doesn't work when you are root, then there may be something else that is getting in your way because root normally can do anything to the device. i say normally, because SELinux and the like may throw a spanner in the works here. For now I'm assuming you are using the good old Unix ACL mechanism. > The node at /proc/bus/usb/001/ is there, but I can't use it in any way. > Creating a link from the respective node to something in /dev/ didn't > help me, either. With /proc being a virtual file system, I'm surprised you managed to make it a symlink to anywhere else to begin with. > But I can't believe I'm the only one not able to make it work! Actually, there is another thread going on (started by russbucket, IIRC) that just may be related to this (at least as far as iscan is concerned). > What do you think: Is udev the reason? Is it something else? Is it me? Nah, it's probably the weather or the phase of the moon ;-) Seriously, sane-backends should have reasonably working udev support, but I vaguely recall seeing some udev related commits recently. You may want to check CVS for the latest scoop on this. > I have updated my sane-backend to version 1.0.16, didn't help. That version introduced a locking mechanism which may or may not be enabled by default on Gentoo. I don't know the details (yet). Any one else care to jump in? Henning? BTW, the epson backend in that version should support your scanner out of the box. In 1.0.15 it did not, but you could force support for it by adding usb 0x04b8 0x080f to your /etc/sane.d/epson.conf. > I even installed iscan from rpm (which normally isn't a good idea when > you use portage for all other packages). > > I'm close to despair! I can tell from your installation from RPM ;-) > Olaf Meeuwissen wrote: >> Karl Heinz Kremer <k...@khk.net> writes: >> >> >>>You need to configure your hotplug system - this will then create the >>>scanner device for you once the scanner is connected to the system. >>>I'm not familiar with Gentoo, so I don't know how this is done with >>>your system. >> >> >> There most likely will be a dynamically created device by the name of >> >> /proc/bus/usb/001/004 >> >> but it may not have the correct permissions. You need read and write >> permissions for the user that wants to use the scanner. >> >> Note that when you re-plug or power cycle the device it will change >> "names" (probably to /proc/bus/usb/001/005, 006 and so on). Unless >> you set up hotplug (or udev, which I still have to look into myself) >> to do this for you, you will need to do this manually every time you >> re-plug, power cycle the device or reboot. >> >> For USB scanners with a recent enough libusb (>= 0.1.6) and kernel (>= >> 2.4.12-ish. IIRC) there is no real need to muck with /dev/usb/scanner* >> anymore. For 2.6.x kernels /dev/usb/scanner* is not an option, really. >> >> >>>On Oct 24, 2005, at 6:40 PM, dark_m...@gmx.net wrote: >>> >>> >>>>I'm using an Epson Stylus Photo RX 420 (scanner-printer-combo) on a >>>>Gentoo machine (Kernel 2.6.13). >>>> >>>>Sane is version 1.0.15 (back- and frontend). >>>> >>>>My problem is the following: >>>> >>>>sane-find-scanner detects my scanner correctly: >>>> >>>>found USB scanner (vendor=0x04b8 [EPSON], product=0x080f [USB MFP]) at >>>>libusb:001:004 >>>> >>>>But I don't find a device for the scanner anywhere. I even created a >>>>/dev/usb/scanner0 by hand, but that didn't help me, either. >>>> >>>>I also tried iscan, but it only says that it can't connect to the >>>>scanner and that I should make sure the scanner is on. >> >> >> What version? If you take care of the hotplug support it provides, >> most of the EPSON scanners should work out-of-the-box (unless your >> system has already switched to udev in favour of hotplug). >> >> >>>>[snip] >> >> >> Hope this helps, > > > -- Olaf Meeuwissen FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 30EF893A/2774 815B DE83 06C8 D733 6B5B 033C C857 30EF 893A Penguin's lib! -- I hack, therefore I am -- LPIC-2
