From owner-freebsd-questions@freebsd.org Fri Apr 14 23:05:39 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 33E95D3DFEF for ; Fri, 14 Apr 2017 23:05:39 +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 9D04793A for ; Fri, 14 Apr 2017 23:05:38 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay13.qsc.de; Sat, 15 Apr 2017 01:05:35 +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 480163CCD5; Sat, 15 Apr 2017 01:05:33 +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 v3EN5XHU002134; Sat, 15 Apr 2017 01:05:33 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sat, 15 Apr 2017 01:05:33 +0200 From: Polytropon To: Manish Jain Cc: "freebsd-questions@freebsd.org" Subject: Re: hplip error: No module named sip Message-Id: <20170415010533.d633e696.freebsd@edvax.de> In-Reply-To: References: 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 821376A03B0 X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1302 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: Fri, 14 Apr 2017 23:05:39 -0000 On Fri, 14 Apr 2017 22:30:45 +0000, Manish Jain wrote: > Hi, > > I have been using hplip with great comfort for over a year. But when I > tried to install my HP 1110 printer on my tertiary box with FreeBSD > Current (12, r316508), I get a strange error upon trying to run hp-setup > : "error: No module named sip". HP Deskjet 1110, I assume? I don't know in which context hp-setup uses "sip", but that abbreviation is often used for "Session Initiation Protocol" and used in combination with VoIP phone applications and services. It's possible that the printer supports some specific communication feature, but hp-setup doesn't have support for it - or vice versa. However, hplip support seems to be okay for this model: http://hplipopensource.com/hplip-web/models/deskjet/deskjet_1110_series.html > To the best of my knowledge, the printer does not show up in the output > of usbconfig. That sounds incorrect. If the printer is a USB printer (which I assume because you didn't say otherwise, and "modern" printers are always USB), it should show in the output of usbconfig as well as in dmesg; however, depending on make and model, it will show up as ugen (USB generic device) or ulpt (USB printer). The identification text _might_ contain the printer maker and model, so grepping for "HP" could reveal the desired result. Anyway, the printer _needs_ to identify to the system somehow in order to be accessible. > If I remember correctly, this printer always shows up in > FreeBSD named as a device of either HP or Hewlett Packard. This is how it usually shows up in the CUPS administration web interface. The connection URI can contain parts like usb://HP/... or other make / model / driver specific text. > Which is even > more strange considering that, even on this box, CUPS recognizes the > printer and I managed to add a queue for it in the CUPS web interface. So the printer actually gets recognized, and CUPS can configure it? It so, what's the point of using hp-setup additionally? If the printer really _really_ doesn't show in dmesg or usbconfig, check the USB connection on both sides. Sometimes it is just that easy. ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...