Re: ulpt problem (USB_ERR_IOERROR)

On Monday 06 July 2009 16:11:54 Patrick Lamaiziere wrote:
> Le Sun, 5 Jul 2009 10:39:18 +0200,
>
> Hans Petter Selasky <hselasky_at_c2i.net> a écrit :
> > 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: <vendor 0x04f9 product 0x001a, class 0/0, rev 1.00/1.00, addr 2> on
> usbus0 ulpt_attach:610: setting alternate config number: 0
> ulpt0: using bi-directional mode
> ulpt_write_callback:237: state=0x0 actlen=0
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=16384
> last message repeated 12 times
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x0 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x0 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=8173
> ulpt_write_callback:237: state=0x0 actlen=8173
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x0 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x0 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x0 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x0 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x0 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x0 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x0 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x0 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x0 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x0 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x0 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x0 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x0 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x0 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x0 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=16384
> ulpt_write_callback:237: state=0x1 actlen=16384
> ulpt_status_callback:369: error=USB_ERR_STALLED
> ulpt_write_callback:237: state=0x1 actlen=16384
> ulpt_write_callback:237: state=0x1 actlen=14989
> ulpt_status_callback:369: error=USB_ERR_IOERROR
> ulpt_write_callback:237: state=0x0 actlen=14989
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_status_callback:369: error=USB_ERR_IOERROR
> ulpt_write_callback:237: state=0x1 actlen=16384
> ulpt_write_callback:237: state=0x1 actlen=1563
> ulpt_status_callback:369: error=USB_ERR_IOERROR
> ulpt_status_callback:369: error=USB_ERR_IOERROR
> ulpt_write_callback:237: state=0x0 actlen=1563
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x0 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x0 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_status_callback:369: error=USB_ERR_IOERROR
> ulpt_write_callback:237: state=0x1 actlen=8192
> ulpt_write_callback:237: state=0x1 actlen=16384
> ulpt_write_callback:237: state=0x1 actlen=16384
> ulpt_status_callback:369: error=USB_ERR_IOERROR
> ulpt_write_callback:237: state=0x1 actlen=16384
> last message repeated 2 times
> ulpt_status_callback:369: error=USB_ERR_IOERROR
> ulpt_write_callback:237: state=0x1 actlen=16384
> last message repeated 2 times
> ulpt_status_callback:369: error=USB_ERR_IOERROR
> ulpt_write_callback:237: state=0x1 actlen=16384
> last message repeated 2 times
> ulpt_status_callback:369: error=USB_ERR_IOERROR
> ulpt_write_callback:237: state=0x1 actlen=16384
> ulpt_write_callback:237: state=0x1 actlen=16384
> ulpt_status_callback:369: error=USB_ERR_IOERROR
> ulpt_write_callback:237: state=0x1 actlen=16384
> ulpt_status_callback:369: error=USB_ERR_IOERROR
> ulpt_write_callback:237: state=0x1 actlen=16384
> ulpt_write_callback:237: state=0x1 actlen=16384
> last message repeated 2 times
> ulpt_status_callback:369: error=USB_ERR_IOERROR
> ulpt_write_callback:237: state=0x1 actlen=16384
> ulpt_write_callback:237: state=0x1 actlen=16384
> ulpt_status_callback:369: error=USB_ERR_IOERROR
> ulpt_write_callback:237: state=0x1 actlen=16384
> ulpt_status_callback:369: error=USB_ERR_IOERROR
> ulpt_write_callback:237: state=0x1 actlen=16384
> last message repeated 5 times
> ulpt_status_callback:369: error=USB_ERR_IOERROR
> ulpt_write_callback:237: state=0x1 actlen=16384
> last message repeated 2 times
> ulpt_status_callback:369: error=USB_ERR_IOERROR
> ulpt_write_callback:237: state=0x1 actlen=16384
> ulpt_write_callback:237: state=0x1 actlen=4836
> ulpt_status_callback:369: error=USB_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.

--HPS