Hi, 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. I can scanimage now, but only as root and only if I am in the same directory as the dll.conf file? Yast has no idea of the scanner and obviously kooka (which I used in the past with my epson) does not work. Any tips, forums, readmes I can follow up on to get the scanner seen. Hans E-mail Disclaimer http://www.sunspace.co.za/emaildisclaimer.htm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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.070814... and http://sourceforge.net/mailarchive/message.php?msg_name=Pine.LNX.4.64.070704... 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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2007-10-10 at 12:46 +0200, Johannes Meixner wrote:
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
For openSUSE 10.2 see for example https://bugzilla.novell.com/show_bug.cgi?id=223875#c4
I use 10.2, will check it out
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'..."
Good idea
Kind Regards Johannes Meixner
Thanks for all the help, this will keep me up tonight :) Hans E-mail Disclaimer http://www.sunspace.co.za/emaildisclaimer.htm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2007-10-10 at 14:21 +0200, Hans van der Merwe wrote: Along these lines I have an HP3300 MFP and I can print from any user and I can scan as root but I cannot scan as a regular user and can find nothing regarding any special group or device perms. Any help appreciated. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/10/2007 10:45 PM, Kenneth Schneider wrote:
On Wed, 2007-10-10 at 14:21 +0200, Hans van der Merwe wrote:
Along these lines I have an HP3300 MFP and I can print from any user and I can scan as root but I cannot scan as a regular user and can find nothing regarding any special group or device perms. Any help appreciated.
Did you setup the scanner via Yast? -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello, I didn't follow the whole thread but just picked up this snippet:
Along these lines I have an HP3300 MFP and I can print from any user and I can scan as root but I cannot scan as a regular user and can find nothing regarding any special group or device perms.
I guess the HP 3300 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 3300 MFP ------------------------------------------------------------------ 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 device 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 I don't see which Suse Linux or openSUSE version is used, I cannot tell what exactly to do to set appropriate permissions via the udev/HAL/resmgr machinery because the details change 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 In particular for HPLIP in openSUSE 10.3 http://sourceforge.net/mailarchive/message.php?msg_name=Pine.LNX.4.64.070814... and http://sourceforge.net/mailarchive/message.php?msg_name=Pine.LNX.4.64.070704... should help, 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". Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2007-10-11 at 15:19 +0200, Johannes Meixner wrote:
Hello,
I didn't follow the whole thread but just picked up this snippet:
Along these lines I have an HP3300 MFP and I can print from any user and I can scan as root but I cannot scan as a regular user and can find nothing regarding any special group or device perms.
I guess the HP 3300 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 3300 MFP ------------------------------------------------------------------ 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 ------------------------------------------------------------------
Mine are: crw-rw-r-- 1 root lp 189, 3 2007-10-10 20:00 /dev/bus/usb/001/004
and then an appropriate "chmod" should help - but only until the device 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 I don't see which Suse Linux or openSUSE version is used,
openSUSE 10.3 GM (sorry)
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".
This did the trick, thank you very much. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello, On Oct 11 09:50 Kenneth Schneider wrote (shortened):
Mine are: crw-rw-r-- 1 root lp 189, 3 2007-10-10 20:00 /dev/bus/usb/001/004
When you set up the scanner unit with YaST, it runs /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions which does some magic to determine the USB device ID and write it to /etc/hal/fdi/policy/10osvendor/80-scanner.fdi so that the udev/HAL/resmgr machinery could do its magic to set an appropriate ACL for the /dev/bus/usb/xxx/yyy device file. But the udev/HAL machinery doesn't notice changed *.fdi files in the running system, see https://bugzilla.novell.com/show_bug.cgi?id=218393#c28 so that only a restart of HAL helps (or a reboot). Or the magic in test_and_set_scanner_access_permissions may not work for your particular model so that there is no entry in 80-scanner.fdi. In this case see http://sourceforge.net/mailarchive/message.php?msg_name=Pine.LNX.4.64.070704... for several ways how to do it manually - perhaps you like it more to add the users who should be allowed to scan to the "lp" group.
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".
This did the trick, thank you very much.
But the little drawback is that now scanning-frontends for root will "see" the scanner twice. Once directly as "hpaio:..." and a duplicate via the net meta-backend as "net:localhost:hpaio:..." (compare the "scanimage -L" output as root and as normal user). Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2007-10-11 at 16:24 +0200, Johannes Meixner wrote:
Hello,
On Oct 11 09:50 Kenneth Schneider wrote (shortened):
Mine are: crw-rw-r-- 1 root lp 189, 3 2007-10-10 20:00 /dev/bus/usb/001/004
When you set up the scanner unit with YaST, it runs /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions which does some magic to determine the USB device ID and write it to /etc/hal/fdi/policy/10osvendor/80-scanner.fdi so that the udev/HAL/resmgr machinery could do its magic to set an appropriate ACL for the /dev/bus/usb/xxx/yyy device file.
But the udev/HAL machinery doesn't notice changed *.fdi files in the running system, see https://bugzilla.novell.com/show_bug.cgi?id=218393#c28 so that only a restart of HAL helps (or a reboot).
Or the magic in test_and_set_scanner_access_permissions may not work for your particular model so that there is no entry in 80-scanner.fdi. In this case see
http://sourceforge.net/mailarchive/message.php?msg_name=Pine.LNX.4.64.070704...
for several ways how to do it manually - perhaps you like it more to add the users who should be allowed to scan to the "lp" group.
This would seem to be a much simpler method especially for new comers.
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".
This did the trick, thank you very much.
But the little drawback is that now scanning-frontends for root will "see" the scanner twice. Once directly as "hpaio:..." and a duplicate via the net meta-backend as "net:localhost:hpaio:..." (compare the "scanimage -L" output as root and as normal user).
True, but I very rarely login as root. Most of root's work is done through su/sudo. And the side effect is I should be able to scan using my laptop without having to be physically connected to the scanner. :-) -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2007-10-11 at 10:52 -0400, Kenneth Schneider wrote:
for several ways how to do it manually - perhaps you like it more to add the users who should be allowed to scan to the "lp" group.
This would seem to be a much simpler method especially for new comers.
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".
This did the trick, thank you very much.
But the little drawback is that now scanning-frontends for root will "see" the scanner twice. Once directly as "hpaio:..." and a duplicate via the net meta-backend as "net:localhost:hpaio:..." (compare the "scanimage -L" output as root and as normal user).
True, but I very rarely login as root. Most of root's work is done through su/sudo. And the side effect is I should be able to scan using my laptop without having to be physically connected to the scanner. :-)
Verified, I am able to scan using my laptop with the scanner physically attached to my desktop. And it was extremely easy to do using YaST. I will say here that overall I am very impressed with 10.3. Sure I have had a couple of problems, but they have been overcome with the help of people on the list. Hooray to the openSUSE developers. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2007-10-11 at 19:23 +0800, Joe Morris (NTM) wrote:
On 10/10/2007 10:45 PM, Kenneth Schneider wrote:
On Wed, 2007-10-10 at 14:21 +0200, Hans van der Merwe wrote:
Along these lines I have an HP3300 MFP and I can print from any user and I can scan as root but I cannot scan as a regular user and can find nothing regarding any special group or device perms. Any help appreciated.
Did you setup the scanner via Yast?
Yes. It works for the root user but not as a regular user. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Hans van der Merwe -
Joe Morris (NTM) -
Johannes Meixner -
Kenneth Schneider