Mailinglist Archive: yast-devel (101 mails)

< Previous Next >
Re: [yast-devel] Printer
  • From: Johannes Meixner <jsmeix@xxxxxxx>
  • Date: Thu, 7 Jan 2010 15:36:44 +0100 (CET)
  • Message-id: <alpine.LNX.2.00.1001071525130.10922@xxxxxxxxxxxxxx>

Hello,

On Dec 27 18:19 Donn Washburn wrote (shortened):
I have a Bother MFC-7840W USB laser printer that according to www.linuxprinter.org it works with Brothers drivers - I have them installed. lsusb and hwinfo --usb find it. And modprobe has all the modules required. But Yast2>Hardware>Printer under Add connection wizard USB will not show any devices or my USB printer. Why would this be the case.

yast2-printer shows the devices which CUPS knows
which is in this case what the CUPS 'usb' backend
/usr/lib[64]/cups/backend/usb autodetected.
Run it as root to see what it results (see my example below).

USB devices which cannot be autodetected by the CUPS 'usb' backend
will not work for printing with the CUPS 'usb' backend.

Therefore it would be plain wrong to show devices in yast2-printer
which will not work for CUPS, see "Strict Compliance With CUPS" at
http://en.opensuse.org/YaST/Development/Printer_Enhancement

yast2-printer is not there to fool you with nice looking
but non-working 'lsusb' or 'hwinfo --usb' output.

I don't know why the CUPS 'usb' backend cannot autodetect
your particular printer.
One possible reason is when the usblp kernel module is not loaded.
For my printer it works for example like this:
------------------------------------------------------------------
root@host# rmmod usblp
root@host# /usr/lib/cups/backend/usb
root@host# modprobe usblp
root@host# /usr/lib/cups/backend/usb
direct usb://HP/LaserJet%201220 "HP LaserJet 1220" ...
------------------------------------------------------------------

Kind Regards
Johannes Meixner
--
SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany
AG Nuernberg, HRB 16746, GF: Markus Rex
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups