From owner-freebsd-questions@FreeBSD.ORG Thu Mar 27 14:22:25 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5437D1065671 for ; Thu, 27 Mar 2008 14:22:25 +0000 (UTC) (envelope-from itz@mushinsky.net) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.184]) by mx1.freebsd.org (Postfix) with ESMTP id C73F48FC1A for ; Thu, 27 Mar 2008 14:22:23 +0000 (UTC) (envelope-from itz@mushinsky.net) Received: by mu-out-0910.google.com with SMTP id w9so6097139mue.6 for ; Thu, 27 Mar 2008 07:22:21 -0700 (PDT) Received: by 10.78.138.6 with SMTP id l6mr4470611hud.71.1206627730432; Thu, 27 Mar 2008 07:22:10 -0700 (PDT) Received: by 10.78.139.1 with HTTP; Thu, 27 Mar 2008 07:22:10 -0700 (PDT) Message-ID: Date: Thu, 27 Mar 2008 10:22:10 -0400 From: "Isaac Mushinsky" To: freebsd-questions@freebsd.org In-Reply-To: <200803270300.27032.amistry@am-productions.biz> MIME-Version: 1.0 References: <200803260021.12249.itz@mushinsky.net> <200803270300.27032.amistry@am-productions.biz> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Anish Mistry Subject: Re: hplip setup problems X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Mar 2008 14:22:25 -0000 Anish Mistry (the port maintainer) has answered below. It seems that this is a printer defect after all then. I'll try to patch the code to fill in the missing serial id with some fake string, and shall report if I get the thing to work. Is the hp backend the only entry point to libusb, or should I have to patch libusb? e.g. cups or sane apps, can they call libusb directly, or only through hpaio backend? I would rather have a patch to hplip distribution only, because libusb correctly throws an error code for the missing serial id. But if some apps query the device directly, the missing serial id may be a problem, they will all have to all be patched separately. > It looks like there is some problem with the C42XX printers that is > causing the serial numbers to no be reported. I got a similar report > about a HP Photosmart C4200 series a couple weeks ago. Unfortunately > I'm VERY busy right now. It will be a couple of week before I can > dive into the issue. If you do happen to find a solution, please let > me know so I can integrate it into the port and notify others. > Thanks, > -- > Anish Mistry > amistry@am-productions.biz > AM Productions http://am-productions.biz/ >