From owner-freebsd-current@FreeBSD.ORG Mon Jul 6 14:11:59 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 310431065836 for ; Mon, 6 Jul 2009 14:11:59 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from smtp.lamaiziere.net (net.lamaiziere.net [91.121.44.19]) by mx1.freebsd.org (Postfix) with ESMTP id A92CA8FC2F for ; Mon, 6 Jul 2009 14:11:58 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from baby-jane.lamaiziere.net (105.10.87-79.rev.gaoland.net [79.87.10.105]) by smtp.lamaiziere.net (Postfix) with ESMTPA id 55BD963352C; Mon, 6 Jul 2009 16:11:57 +0200 (CEST) Received: from baby-jane.lamaiziere.net (localhost [127.0.0.1]) by baby-jane.lamaiziere.net (Postfix) with ESMTP id BF939B933; Mon, 6 Jul 2009 16:11:55 +0200 (CEST) Date: Mon, 6 Jul 2009 16:11:54 +0200 From: Patrick Lamaiziere To: Hans Petter Selasky Message-ID: <20090706161154.06abb3cd@baby-jane.lamaiziere.net> In-Reply-To: <200907051039.19584.hselasky@c2i.net> References: <20090703172600.1971111e@baby-jane.lamaiziere.net> <200907040945.41153.hselasky@c2i.net> <20090704164341.0acd0271@baby-jane.lamaiziere.net> <200907051039.19584.hselasky@c2i.net> X-Mailer: Claws Mail 3.7.1 (GTK+ 2.16.2; i386-portbld-freebsd7.2) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: ulpt problem (USB_ERR_IOERROR) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jul 2009 14:12:02 -0000 Le Sun, 5 Jul 2009 10:39:18 +0200, Hans Petter Selasky a =E9crit : > Can you try the attached patch for 8-current.=20 > Please provide ulpt > debug prints in either failing or succeeding case. Thanks a lot. I've commented the ulpt_reset(sc) in urlpt_open() because it does not work at all with it and I have to use unlpt. But no luck. I'm still using cups because I have to figure how I can get th= e PCL file sent to the printer. I'm using /dev/urlpt. ulpt0: on = usbus0 ulpt_attach:610: setting alternate config number: 0 ulpt0: using bi-directional mode ulpt_write_callback:237: state=3D0x0 actlen=3D0 ulpt_write_callback:237: state=3D0x1 actlen=3D8192 ulpt_write_callback:237: state=3D0x1 actlen=3D16384 last message repeated 12 times ulpt_write_callback:237: state=3D0x1 actlen=3D8192 ulpt_write_callback:237: state=3D0x0 actlen=3D8192 ulpt_write_callback:237: state=3D0x1 actlen=3D8192 ulpt_write_callback:237: state=3D0x0 actlen=3D8192 ulpt_write_callback:237: state=3D0x1 actlen=3D8192 ulpt_write_callback:237: state=3D0x1 actlen=3D8192 ulpt_write_callback:237: state=3D0x1 actlen=3D8173 ulpt_write_callback:237: state=3D0x0 actlen=3D8173 ulpt_write_callback:237: state=3D0x1 actlen=3D8192 ulpt_write_callback:237: state=3D0x0 actlen=3D8192 ulpt_write_callback:237: state=3D0x1 actlen=3D8192 ulpt_write_callback:237: state=3D0x0 actlen=3D8192 ulpt_write_callback:237: state=3D0x1 actlen=3D8192 ulpt_write_callback:237: state=3D0x0 actlen=3D8192 ulpt_write_callback:237: state=3D0x1 actlen=3D8192 ulpt_write_callback:237: state=3D0x0 actlen=3D8192 ulpt_write_callback:237: state=3D0x1 actlen=3D8192 ulpt_write_callback:237: state=3D0x0 actlen=3D8192 ulpt_write_callback:237: state=3D0x1 actlen=3D8192 ulpt_write_callback:237: state=3D0x0 actlen=3D8192 ulpt_write_callback:237: state=3D0x1 actlen=3D8192 ulpt_write_callback:237: state=3D0x0 actlen=3D8192 ulpt_write_callback:237: state=3D0x1 actlen=3D8192 ulpt_write_callback:237: state=3D0x0 actlen=3D8192 ulpt_write_callback:237: state=3D0x1 actlen=3D8192 ulpt_write_callback:237: state=3D0x0 actlen=3D8192 ulpt_write_callback:237: state=3D0x1 actlen=3D8192 ulpt_write_callback:237: state=3D0x0 actlen=3D8192 ulpt_write_callback:237: state=3D0x1 actlen=3D8192 ulpt_write_callback:237: state=3D0x0 actlen=3D8192 ulpt_write_callback:237: state=3D0x1 actlen=3D8192 ulpt_write_callback:237: state=3D0x0 actlen=3D8192 ulpt_write_callback:237: state=3D0x1 actlen=3D8192 ulpt_write_callback:237: state=3D0x0 actlen=3D8192 ulpt_write_callback:237: state=3D0x1 actlen=3D8192 ulpt_write_callback:237: state=3D0x0 actlen=3D8192 ulpt_write_callback:237: state=3D0x1 actlen=3D8192 ulpt_write_callback:237: state=3D0x0 actlen=3D8192 ulpt_write_callback:237: state=3D0x1 actlen=3D8192 ulpt_write_callback:237: state=3D0x1 actlen=3D16384 ulpt_write_callback:237: state=3D0x1 actlen=3D16384 ulpt_status_callback:369: error=3DUSB_ERR_STALLED ulpt_write_callback:237: state=3D0x1 actlen=3D16384 ulpt_write_callback:237: state=3D0x1 actlen=3D14989 ulpt_status_callback:369: error=3DUSB_ERR_IOERROR ulpt_write_callback:237: state=3D0x0 actlen=3D14989 ulpt_write_callback:237: state=3D0x1 actlen=3D8192=20 ulpt_status_callback:369: error=3DUSB_ERR_IOERROR ulpt_write_callback:237: state=3D0x1 actlen=3D16384 ulpt_write_callback:237: state=3D0x1 actlen=3D1563=20 ulpt_status_callback:369: error=3DUSB_ERR_IOERROR ulpt_status_callback:369: error=3DUSB_ERR_IOERROR ulpt_write_callback:237: state=3D0x0 actlen=3D1563=20 ulpt_write_callback:237: state=3D0x1 actlen=3D8192=20 ulpt_write_callback:237: state=3D0x0 actlen=3D8192=20 ulpt_write_callback:237: state=3D0x1 actlen=3D8192=20 ulpt_write_callback:237: state=3D0x0 actlen=3D8192=20 ulpt_write_callback:237: state=3D0x1 actlen=3D8192=20 ulpt_status_callback:369: error=3DUSB_ERR_IOERROR ulpt_write_callback:237: state=3D0x1 actlen=3D8192=20 ulpt_write_callback:237: state=3D0x1 actlen=3D16384 ulpt_write_callback:237: state=3D0x1 actlen=3D16384 ulpt_status_callback:369: error=3DUSB_ERR_IOERROR ulpt_write_callback:237: state=3D0x1 actlen=3D16384 last message repeated 2 times =20 ulpt_status_callback:369: error=3DUSB_ERR_IOERROR ulpt_write_callback:237: state=3D0x1 actlen=3D16384 last message repeated 2 times =20 ulpt_status_callback:369: error=3DUSB_ERR_IOERROR ulpt_write_callback:237: state=3D0x1 actlen=3D16384 last message repeated 2 times =20 ulpt_status_callback:369: error=3DUSB_ERR_IOERROR ulpt_write_callback:237: state=3D0x1 actlen=3D16384 ulpt_write_callback:237: state=3D0x1 actlen=3D16384 ulpt_status_callback:369: error=3DUSB_ERR_IOERROR ulpt_write_callback:237: state=3D0x1 actlen=3D16384 ulpt_status_callback:369: error=3DUSB_ERR_IOERROR ulpt_write_callback:237: state=3D0x1 actlen=3D16384 ulpt_write_callback:237: state=3D0x1 actlen=3D16384 last message repeated 2 times ulpt_status_callback:369: error=3DUSB_ERR_IOERROR ulpt_write_callback:237: state=3D0x1 actlen=3D16384 ulpt_write_callback:237: state=3D0x1 actlen=3D16384 ulpt_status_callback:369: error=3DUSB_ERR_IOERROR ulpt_write_callback:237: state=3D0x1 actlen=3D16384 ulpt_status_callback:369: error=3DUSB_ERR_IOERROR ulpt_write_callback:237: state=3D0x1 actlen=3D16384 last message repeated 5 times ulpt_status_callback:369: error=3DUSB_ERR_IOERROR ulpt_write_callback:237: state=3D0x1 actlen=3D16384 last message repeated 2 times ulpt_status_callback:369: error=3DUSB_ERR_IOERROR ulpt_write_callback:237: state=3D0x1 actlen=3D16384 ulpt_write_callback:237: state=3D0x1 actlen=3D4836 ulpt_status_callback:369: error=3DUSB_ERR_IOERROR last message repeated 31 times last message repeated 121 times last message repeated 544 times ... Shall I setup another box with current to be sure that's a problem with the printer and not with the hardware? Regards.