From owner-freebsd-current@FreeBSD.ORG Mon Jul 6 15:51:04 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 96918106564A for ; Mon, 6 Jul 2009 15:51:04 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.swip.net [212.247.154.193]) by mx1.freebsd.org (Postfix) with ESMTP id D9BFC8FC19 for ; Mon, 6 Jul 2009 15:51:03 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=BQeo18V-fugA:10 a=MXw7gxVQKqGXY79tIT8aFQ==:17 a=8kQB0OdkAAAA:8 a=3Z1HSK4m8mWhRrFR_0EA:9 a=CtcdaOUG9Wt6lt26yf8A:7 a=a-aXMgJu9itIvJdfkB4L8J98DjgA:4 a=9aOQ2cSd83gA:10 Received: from [62.113.132.61] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe07.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 1269572606; Mon, 06 Jul 2009 17:51:02 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Mon, 6 Jul 2009 17:50:37 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-CURRENT; KDE/4.2.4; i386; ; ) References: <20090703172600.1971111e@baby-jane.lamaiziere.net> <200907051039.19584.hselasky@c2i.net> <20090706161154.06abb3cd@baby-jane.lamaiziere.net> In-Reply-To: <20090706161154.06abb3cd@baby-jane.lamaiziere.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200907061750.39084.hselasky@c2i.net> Cc: Patrick Lamaiziere 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 15:51:04 -0000 On Monday 06 July 2009 16:11:54 Patrick Lamaiziere wrote: > Le Sun, 5 Jul 2009 10:39:18 +0200, > > Hans Petter Selasky a =E9crit : > > Can you try the attached patch for 8-current. > > 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 > the 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 > ulpt_status_callback:369: error=3DUSB_ERR_IOERROR > ulpt_write_callback:237: state=3D0x1 actlen=3D16384 > ulpt_write_callback:237: state=3D0x1 actlen=3D1563 > ulpt_status_callback:369: error=3DUSB_ERR_IOERROR > ulpt_status_callback:369: error=3DUSB_ERR_IOERROR > ulpt_write_callback:237: state=3D0x0 actlen=3D1563 > 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_status_callback:369: error=3DUSB_ERR_IOERROR > 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_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 > last message repeated 2 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=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? Hi, urlpt was just for backwards compatibility. Could you try printing using /dev/unlpt0 ? And send me resulting dmesg? Power cycle your printer before testing. =2D-HPS