From owner-freebsd-questions@freebsd.org Sat Apr 15 19:07:17 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 55D2BD3FD59 for ; Sat, 15 Apr 2017 19:07:17 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay13.qsc.de (mailrelay13.qsc.de [212.99.187.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D111AC6 for ; Sat, 15 Apr 2017 19:07:16 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay13.qsc.de; Sat, 15 Apr 2017 21:07:06 +0200 Received: from r56.edvax.de (port-92-195-127-117.dynamic.qsc.de [92.195.127.117]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 0B4163CBF9; Sat, 15 Apr 2017 21:07:06 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v3FJ75wQ002014; Sat, 15 Apr 2017 21:07:05 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sat, 15 Apr 2017 21:07:05 +0200 From: Polytropon To: Manish Jain Cc: "freebsd-questions@freebsd.org" Subject: Re: hplip error: No module named sip Message-Id: <20170415210705.64a63ef0.freebsd@edvax.de> In-Reply-To: References: <20170415010533.d633e696.freebsd@edvax.de> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay13.qsc.de with 46253695F8D X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1315 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2017 19:07:17 -0000 On Sat, 15 Apr 2017 05:22:31 +0000, Manish Jain wrote: > > > > HP Deskjet 1110, I assume? > > Actually, it is HP DeskJet 1112, but it always identifies itself as HP > DJ 1110. It belongs to the same product family, so I assume internally several devices share a comparable firmware (which maybe even have zhe same code in parts). > > However, hplip support seems to be okay for this model: > > > > http://hplipopensource.com/hplip-web/models/deskjet/deskjet_1110_series.html > > This USB printer works fantastically with primary and secondary boxes > (both FreeBSD 10.3/11). I have never had a problem with this printer > printing with FreeBSD::hplip. Good combination - especially when you can actually _confirm_ that it works (better than "it should work"). > >> To the best of my knowledge, the printer does not show up in the output > >> of usbconfig. > > I checked the output of usbconfig by doing this : I ran usbconfig twice, > first time with the printer on; and then a second time with the printer > switched off. > > a) The first run does not produce identification for any HP/Hewlett > Packard device > b) Both runs produce exactly the same output. Did you check the dmesg output? When you attach (or power on) the printer, some new lines should be added. Depending on the printer, they could look like this: ugen4.3: at usbus4 ulpt0: on usbus4 ulpt0: using bi-directional mode This is a Samsung CLX-2160 color laser printer. You should be able to quickly spot similar lines in dmesg output. I'd say that is the easiest way to determine if the kernel did pick up the device correctly, which is the _requirement_ of other software components being able to do anything with it. (Sidenote: This printer doesn't work with CUPS, but I'm using the foo2zjs filter and pipe its output into /dev/ulpt0 from a PS source, and that works. With system lpd, it would easily be possible to add that printer, but as I'm using it as a printer only a few times a year, I'm too lazy to implement this properly.) > > So the printer actually gets recognized, and CUPS can configure > > it? It so, what's the point of using hp-setup additionally? > > Now it gets interesting. On neither my primary box nor my secondary box > have I succeeded in printing to this printer with CUPS. I have always > had to delete the CUPS queue and print with hplip. With current CUPS and hplip (and maybe hpijs?) it should work out of the box. I could achieve this recently with a new HP inkpee printer - CUPS detected it automatically, loaded the appropriate drivers and filters, and it worked immediately. > On this tertiary box, it turns out that printing with CUPS is cool : - ) It's not that bad. The only case that gets you headaches is when the autodetection does not work and you have no idea what to enter at the "device URI" input field. ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...