Thomas Gellekum
2010-May-21 08:55 UTC
[8-STABLE] USB printer disconnecting when trying to print
Moin, my new machine doesn't have a physical connector for a parallel printer anymore, so I'm now connecting my Brother HL-1250 through the USB port. The printer is recognized when it powers up: ugen0.4: <vendor 0x04f9> at usbus0 ulpt0: <vendor 0x04f9 product 0x0007, class 0/0, rev 1.00/1.00, addr 4> on usbus0 ulpt0: using bi-directional mode and it starts warming up when I try to print, but no page is coming out. After setting hw.usb.debug.ulpt=1, hw.usb.debug.ugen=1, I do a echo "hallo" > /dev/ulpt0 and get lots of lines starting with the same usbd_transfer_submit shown below (are these actually related to the printer? I'm guessing they are mouse events): May 21 10:17:23 siegel kernel: usbd_transfer_submit: xfer=0xc9c70220, endpoint=0xc7ab3878, nframes=2, dir=read May 21 10:17:23 siegel kernel: usb_dump_endpoint: endpoint=0xc7ab3878 edesc=0xc7ab3b30 isoc_next=0 toggle_next=0 bEndpointAddress=0x00 May 21 10:17:23 siegel kernel: usb_dump_queue: endpoint=0xc7ab3878 xfer: May 21 10:17:23 siegel kernel: usbd_pipe_enter: enter May 21 10:17:23 siegel kernel: usbd_pipe_start: start May 21 10:17:23 siegel kernel: usbd_transfer_done: err=USB_ERR_NORMAL_COMPLETION May 21 10:17:23 siegel kernel: usbd_callback_wrapper_sub: xfer=0xc9c70220 endpoint=0xc7ab3878 sts=0 alen=9, slen=9, afrm=2, nfrm=2 May 21 10:17:37 siegel kernel: ulpt_write_callback: state=0x0 actlen=0 May 21 10:17:37 siegel kernel: ulpt_status_callback: error=USB_ERR_STALLED May 21 10:17:37 siegel kernel: ugen0.4: <vendor 0x04f9> at usbus0 (disconnected) [terminate command with ^C] May 21 10:20:22 siegel kernel: ulpt0: at uhub2, port 2, addr 4 (disconnected) May 21 10:20:22 siegel kernel: ulpt_detach: sc=0xca008b00 May 21 10:20:22 siegel kernel: ulpt_write_callback: state=0x2 actlen=0 May 21 10:20:23 siegel kernel: ugen0.4: <vendor 0x04f9> at usbus0 May 21 10:20:23 siegel kernel: ulpt0: <vendor 0x04f9 product 0x0007, class 0/0, rev 1.00/1.00, addr 4> on usbus0 May 21 10:20:23 siegel kernel: ulpt_attach: setting alternate config number: 0 May 21 10:20:23 siegel kernel: ulpt0: using bi-directional mode I've also tried to set up CUPS instead of using LPD, but that doesn't even find the printer. The board is an Intel DH55HC with a i3-530; system is a recent 8-STABLE (see attached dmesg). Any ideas on how to debug this are welcome. tg -------------- next part -------------- A non-text attachment was scrubbed... Name: dmesg.boot Type: application/octet-stream Size: 8528 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20100521/64458898/dmesg.obj
Torfinn Ingolfsen
2010-May-21 09:05 UTC
[8-STABLE] USB printer disconnecting when trying to print
On Fri, 21 May 2010 10:29:04 +0200 Thomas Gellekum <Thomas.Gellekum@gmx.de> wrote:> echo "hallo" > /dev/ulpt0 > [...] > Any ideas on how to debug this are welcome.Most of todays printers do NOT understand plain text, usually you need a driver which transforms whatever you want to print into the language the printer understands. See http://www.openprinting.org/printer/Brother/Brother-HL-1250 for more info. HTH -- Torfinn Ingolfsen
Warren Block
2010-May-21 16:13 UTC
[8-STABLE] USB printer disconnecting when trying to print
On Fri, 21 May 2010, Thomas Gellekum wrote:> my new machine doesn't have a physical connector for a parallel printer > anymore, so I'm now connecting my Brother HL-1250 through the USB port. > The printer is recognized when it powers up: > > ugen0.4: <vendor 0x04f9> at usbus0 > ulpt0: <vendor 0x04f9 product 0x0007, class 0/0, rev 1.00/1.00, addr 4> on usbus0 > ulpt0: using bi-directional mode > > and it starts warming up when I try to print, but no page is coming out. > After setting hw.usb.debug.ulpt=1, hw.usb.debug.ugen=1, I do a > > echo "hallo" > /dev/ulpt0 > > and get lots of lines starting with the same usbd_transfer_submit shown > below (are these actually related to the printer? I'm guessing they are > mouse events):openprinting.org says that printer does support plain text, so the first thing to try would be using the unlpt0 device. -Warren Block * Rapid City, South Dakota USA