Hello, On May 29 06:46 dwelch91 wrote (shortened): > OK... I am out of ideas. ... > > > On 5/27/07, na bob <[EMAIL PROTECTED]> wrote: > > > > i'm working with Suse 10.2 and tried to get Hplip > > > > 1.7.4a,run running but my printer (Officejet 635) > > > > was not recognized (=parrallel printer).
In the meantime you may like to try out my readymade RPMs: I provide for testing HPLIP 1.7.4a for the released openSUSE 10.2 and Suse Linux 10.1 and Suse Linux Enterprise 10 (SLE 10) and for the openSUSE development version openSUSE "factory" for 32-bit Intel compatible (i586) and 64-bit AMD (x86_64) via the openSUSE build service at http://software.opensuse.org/download/home:/jsmeix/ The packages are * only for testing * without any guarantee or warranty * without any support As an extreme example, this means that if your complete computer center crashes because of these packages, it is only your problem. Nevertheless, I am very interested in your feedback because the more people test it, the more problems (even hidden problems) are revealed. To send me feedback or bug reports, please follow the instructions in http://en.opensuse.org/Submitting_Bug_Reports Choose the component "Printing" (also for scanning/faxing with HPLIP). Make it obvious which package, which package version, which hardware architecture and which openSUSE version you are talking about - e.g.: "Feedback regarding hplip-1.7.4a-2.1.i586.rpm and hplip-hpijs-1.7.4a-2.1.i586.rpm from http://software.opensuse.org/download/home:/jsmeix/ for openSUSE 10.2 used on 64-bit AMD hardware." Ideally provide the "rpm -q --changelog hplip | head" output to make it obvious which exact package release you have. Regarding the parallel port: There are some bug reports about problems with the parallel port in our Novell/Suse Bugzilla. A good report to start is https://bugzilla.novell.com/show_bug.cgi?id=185135 See also the other bug reports which are mentioned there. The current workaround is to experiment with various BIOS settings and explicite additional settings in /etc/modprobe.conf to find a setup, which actually works in a particular problematic case. Note that e.g. for scanning you may have to use a higher-level parport mode (some kind of fast bidirectional mode) and additionally the kernel module ppdev may have to be loaded for all-in-one devices, see http://hplip.sourceforge.net/tech_docs/overview.html regarding "MLC/1284.4". Note that those modes (EPP or even ECP) normally require an interrupt and ECP additionally requires DMA. To activate the interrupt mode, set in /etc/modprobe.conf something like "options parport_pc io=0x378 irq=7" where io and irq must match to your BIOS settings. Make sure that the IRQ which you use for the parallel port is not used by any other stuff (check /proc/interrupts) and see our online documentation (package suselinux-manual_en or opensuse-manual_en) chapter "Printer Operation", section "Troubleshooting", sub-section "Parallel Ports". Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ HPLIP-Help mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hplip-help
