Hello, On Oct 10 11:45 Hans van der Merwe wrote (shortened): > I have this multifunction printer working (using the foo2xqx driver). > The scanner part is supported by hpljm1005, which is not yet in die sane > source. I added it and recompiled the sane sources. Also created a > dll.conf file with the string "hpljm1005" in it - as instructed by > someone on a forum somewhere.
Usually SANE looks into /etc/sane.d/dll.conf and therefore additional drivers (SANE backends) are usually added to this file. But your self-compiled SANE might do anything else depending on how you compiled and installed it. For general information how it usually works and how to do usually trouble-shooting see http://en.opensuse.org/SDB:Configuring_Scanners_from_SUSE_LINUX_9.2 > I can scanimage now, but only as root I guess the HP M1005 MFP is connected via USB. Then "lsusb" shows its current USB bus and device number, e.g.: ------------------------------------------------------------------ Bus 002 Device 003: ID 03f0:a1b2 Hewlett-Packard LaserJet 1005 ------------------------------------------------------------------ and then the device file via which it is accessed is ------------------------------------------------------------------ /dev/bus/usb/002/003 ------------------------------------------------------------------ and then "ls -l /dev/bus/usb/002/003" shows its permissions e.g.: ------------------------------------------------------------------ crw-r--r-- 1 root root ... /dev/bus/usb/002/003 ------------------------------------------------------------------ and then an appropriate "chmod" should help - but only until the scanner is re-connected or the system is re-booted because USB device files are created by udev on the fly for each boot and/or device connect. As you didn't mention which Suse Linux or openSUSE version you are using, I cannot tell you what exactly you need to do to set appropriate permissions via the udev/HAL/resmgr machinery (the details changed for each Suse Linux or openSUSE version). For openSUSE 10.2 see for example https://bugzilla.novell.com/show_bug.cgi?id=223875#c4 and for openSUSE 10.3 see for example https://bugzilla.novell.com/show_bug.cgi?id=250659 Even http://sourceforge.net/mailarchive/message.php?msg_name=Pine.LNX.4.64.0708141120210.25428%40nelson.suse.de and http://sourceforge.net/mailarchive/message.php?msg_name=Pine.LNX.4.64.0707040850200.22081%40nelson.suse.de may help you, see the "controllable permissions" section. The simplest solution is to use the saned and the net meta-backend on your local host to access the scanner, for example via "YaST scanner setup" -> "Other" -> "Scanning via Network". For general information how this usually works see http://en.opensuse.org/SDB:Configuring_Scanners_from_SUSE_LINUX_9.2 "Alternatively you can use 'saned'..." > Yast has no idea of the scanner The model list in YaST is derived from the *.desc scanner description files in our sane-backends RPM package. There is no other method in SANE how a scanner config tool could know about scanner models and which driver(s) match to a model. Don't confuse this with what "sane-find-scanner" does, see https://bugzilla.novell.com/show_bug.cgi?id=260991#c8 > obviously kooka (which I used in the past with my epson) > does not work. Why "obviously"? Any scanning frontend like scanimage, xscanimage (package sane-frontends), xsane (package xsane) and kooka should recognize all scanners which are shown by "scanimage -L", see http://en.opensuse.org/SDB:Configuring_Scanners_from_SUSE_LINUX_9.2 Only kooka seems to be sometimes a bit picky, see https://bugzilla.novell.com/show_bug.cgi?id=141079 Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
