Cups 1.4.2 and common problems
Since 1.4.x Cups no longer prefers usblp, and is built with libusb as the only backend. If your printer is not found by cups, you can try to remove usblp, and restart cups.
Code:
rmmod usblp This worked for our Epson IJP printers. If your printer is not supported by libusb, you can rebuild cups to use usblp instead of libusb. Add --disable-libusb to the SlackBuild and rebuild cups. There is a patch on the cups bug list to enable both backends, but does not apply cleanly on 1.4.2. Debian has a mega patch, which includes a patch to enable both backends. For HP printers (which I do not own). There have been threads here about new cups and hplip. Hplip has had some changes to the configure script as well. Code:
--enable-pp-build enable parallel port build (default=no) The --enable-pp-build was changed from default=yes to default=no in version 3.9.6 |
Thanks, this is very useful information.
One question, though: How do I know, if my printer is supported by libusb? EDIT: or if my problems are caused by something else... gargamel |
Who knows the real solution for this:
Code:
Mar 7 17:57:31 zielony hp[1289]: io/hpmud/musb.c 1026: bulk_write failed buf=0xbfa03424 size=50 len=-5: Success It's HP printer connected via USB. What hplip options could help? |
I looked for a list, but all I found were bug reports against cups and usblp.
HP has this to say http://hplipopensource.com/node/128 Quote:
|
Quote:
EDIT: Any reliable method to find out, if a particular model is supported, would be equally good, of course! The problem with trial and error is, that it (1) is very time-consuming and (2) is only useful in case of positive results. If your printer works, you know it's supported. But if it doesn't the causes can be manifold, and you won't know, if it's lack of libusb support or something else, why it's not working. gargamel |
I would like to share my experience with my Brother DCP-110C scanner/printer on -current with CUPS-1.4.2.
With the standard Slackware CUPS package, then scanning worked but printing did not work. To get printing to work, I needed to blacklist usblp in /etc/modprobe.d and recompile CUPS by adding --disable-libusb (or --enable-libusb=no) to the cups.Slackbuild script. I also needed to change the group on the device entry /dev/bus/usb/<Bus>/<Device> from 'scanner' to 'lp'. This is a problem for multifunction devices. At boot, udev will assign the device to the 'scanner' group due to the rules in /lib/udev/rules.d/80-libsane.rules. CUPS will not recognise the printer unless the group on the device is changed to 'lp', at which point the scanner is not available to skanlite or xsane until the group is changed back to 'scanner'. Any ideas on how to make both scanning and printing available without reverting to CUPS 1.3.1 where everything worked? |
For me even compiling CUPS with '--disable-usb' doesn't help, though I have lp group at the printer USB port set by udev.
|
Quote:
Quote:
BTW, I find the new web UI of CUPS confusing. Not exactly what I had expected from UI expert Apple... gargamel |
Having slept on it, I now have the answer to my own question.
Copy /lib/udev/rules.d/80-libsane.rules to /etc/udev/rules.d. Add OWNER="lp" to the line for the scanner device in /etc/udev/rules.d/80-libsane.rules. Quote:
|
Two questions:
1. Is blacklisting usblp still required with this solution? 2. Is the order of parameters important? Because, I added OWNER="lp" at the end of the ATTR line, not before the GROUP, as you did. It doesn't yet work here, the answers to the questions above would help me to track it further down. Thanks! gargamel |
Quote:
Quote:
|
Great, it works now!
I just had to reinstall the driver files provided by Brother and to manually select the PPD file. Excellent! Thanks! gargamel |
Quote:
Phil |
All times are GMT -5. The time now is 08:14 AM. |