Hello, On Aug 19 07:05 Aaron wrote (shortened): > If possible upgrade to the current hplip release.
HPLIP 1.6.7 packages built for Suse Linux 10.1 for 32-bit Intel compatible (i586) and for 64-bit AMD (x86_64) are available for testing (and only for testing) at ftp://ftp.suse.com/pub/people/jsmeix/unsupported/hplip/ There are incompatibilities with our official HPLIP packages in Suse Linux 10.1. Be prepared that your existing configuration may no longer work with the new packages and/or that there may be no YaST support for the new packages, see for example https://bugzilla.novell.com/show_bug.cgi?id=184798 Note the "unsupported" and read the README: ftp://ftp.suse.com/pub/people/jsmeix/unsupported/hplip/10.1/RPMS/README > It sounds like YaST > configured the printer using the usb:// backend--for hplip to function > correctly the printer needs to be configured using the hp:// backend. YaST > can sometimes not configure the printer correctly. Have a look at http://en.opensuse.org/SDB:Set_up_a_HP_OfficeJet_%28%22all-in-one%22_device%29 We prefer not to start services by default which are not really needed but also have a look at https://bugzilla.novell.com/show_bug.cgi?id=184798 and the related reports, in particular https://bugzilla.novell.com/show_bug.cgi?id=175323 what we try to improve. At the moment YaST uses a selfmade fixed built-in list of all-in-one devices and for those devices the hplip services are started but see http://en.opensuse.org/SDB:Set_up_a_HP_OfficeJet_%28%22all-in-one%22_device%29 about the problems with such lists. A longer time ago I asked HP for an autodetection tool which works stand-alone (i.e. without the running hplip daemons) and which can distinguish a plain printer from an all-in-one device but I don't know about such a tool. At the moment all I know is to let YaST parse /usr/share/hplip/data/xml/models.xml to find out if it is a plain printer, a printer+scanner, or if there is even a fax included, see https://bugzilla.novell.com/show_bug.cgi?id=184798 but who guarantees that the syntax in models.xml will not change in newer HPLIP versions and let YaST fail to parse it? It would be better if we could run a stand-alone autodetection tool which queries the device directly. Perhaps /usr/sbin/hpiod could be run in a special non-daemon mode to do only device autodetection? > > ... I try to set > > up my HP Photosmart 2575 for scanning under SuSE Linux 10.1 (OpenSuSE). > > Setting up the printer with YAST was very straight and the printer works > > fine. My distribution provides me with hplip version 0.9.7. > > What I am absolutely missing is a HOWTO for setting up the scanner. The YaST scanner configuration does not support network scanners. Therefore you must set it up manually, see for example http://en.opensuse.org/SDB:Configuring_Scanners_from_SUSE_LINUX_9.3 Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: [EMAIL PROTECTED] 90409 Nuernberg, Germany WWW: http://www.suse.de/ ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ HPLIP-Help mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hplip-help
