ulpt can't attach Lexmark E120
System: Raspberry Pi uname: r245840M (Alie Tan's image from 25 January) By comparison, this Lexmark E120 printer attaches and prints with no difficulty on FreeBSD-9.1-RELEASE, but on CURRENT, it says: ugen0.5: at usbus0 ulpt1: addr 5> on usbus0 device_attach: ulpt1 attach returned 12 Also, an HP CM1015 attaches without a problem. What should I try next? -- George Mitchell ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ulpt can't attach Lexmark E120
On 08/22/13 13:24, George Mitchell wrote: As I was saying a few minutes ago ... On 01/27/13 17:32, George Mitchell wrote: On 01/27/13 14:07, Hans Petter Selasky wrote: [...] I need output when hw.usb.ulpt.debug=15 to say exactly. Could you ask the provider of the binaries to compile having USB_DEBUG set, also for the modules. --HPS I'm working on getting a debug build ... Thanks for your help so far. I notice that there seem to be only trivial differences between the 9.1 release ulpt and the 10.0 current ulpt driver. -- George (This is on a Raspberry Pi.) It took me a bit longer than anticipated, but here is the output, from an image built over last weekend: Hi, Could you run: usbdump -i usbusX -f Y -s 65536 To get a dump of the USB activity when you plug the device? The message in question is not important, and might be changed to not cancel the ulpt attach routine. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ulpt can't attach Lexmark E120
On 08/22/13 07:34, Hans Petter Selasky wrote: On 08/22/13 13:24, George Mitchell wrote: As I was saying a few minutes ago ... On 01/27/13 17:32, George Mitchell wrote: On 01/27/13 14:07, Hans Petter Selasky wrote: [...] I need output when hw.usb.ulpt.debug=15 to say exactly. Could you ask the provider of the binaries to compile having USB_DEBUG set, also for the modules. --HPS I'm working on getting a debug build ... Thanks for your help so far. I notice that there seem to be only trivial differences between the 9.1 release ulpt and the 10.0 current ulpt driver. -- George (This is on a Raspberry Pi.) It took me a bit longer than anticipated, but here is the output, from an image built over last weekend: Hi, Could you run: usbdump -i usbusX -f Y -s 65536 To get a dump of the USB activity when you plug the device? The message in question is not important, and might be changed to not cancel the ulpt attach routine. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" Here's the result: root@pi:/ # usbdump -i usbus0 -f 4 -s 65536 00:26:01.592494 usbus0.4 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0 00:26:01.593117 usbus0.4 DONE-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 00:26:01.593209 usbus0.4 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0 00:26:01.594146 usbus0.4 DONE-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 00:26:01.611621 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.614223 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0,ERR=0 00:26:01.614730 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.617595 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=20,IVAL=0,ERR=0 00:26:01.617758 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.620216 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 00:26:01.620313 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.622219 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 00:26:01.622326 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.624208 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 00:26:01.624305 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.631722 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=16,IVAL=0,ERR=0 00:26:01.631925 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.634217 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 00:26:01.634315 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.637220 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=44,IVAL=0,ERR=0 00:26:01.637334 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.639214 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 00:26:01.639312 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.641585 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=28,IVAL=0,ERR=0 00:26:01.641769 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.644209 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=12,IVAL=0,ERR=0 00:26:01.644316 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.651213 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=32,IVAL=0,ERR=0 00:26:01.651316 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.653219 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 00:26:01.653321 usbus0.4 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0 00:26:01.654584 usbus0.4 DONE-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 (at which point if I type control-c to stop usbdump, the system gets a fatal kernel mode translation fault, but that's another story.) Hope this helps. -- George ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ulpt can't attach Lexmark E120
On 08/23/13 02:29, George Mitchell wrote: On 08/22/13 07:34, Hans Petter Selasky wrote: Here's the result: root@pi:/ # usbdump -i usbus0 -f 4 -s 65536 00:26:01.592494 usbus0.4 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0 00:26:01.593117 usbus0.4 DONE-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 00:26:01.593209 usbus0.4 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0 00:26:01.594146 usbus0.4 DONE-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 00:26:01.611621 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.614223 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0,ERR=0 00:26:01.614730 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.617595 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=20,IVAL=0,ERR=0 00:26:01.617758 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.620216 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 00:26:01.620313 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.622219 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 00:26:01.622326 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.624208 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 00:26:01.624305 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.631722 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=16,IVAL=0,ERR=0 00:26:01.631925 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.634217 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 00:26:01.634315 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.637220 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=44,IVAL=0,ERR=0 00:26:01.637334 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.639214 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 00:26:01.639312 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.641585 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=28,IVAL=0,ERR=0 00:26:01.641769 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.644209 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=12,IVAL=0,ERR=0 00:26:01.644316 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.651213 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=32,IVAL=0,ERR=0 00:26:01.651316 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.653219 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 00:26:01.653321 usbus0.4 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0 00:26:01.654584 usbus0.4 DONE-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 (at which point if I type control-c to stop usbdump, the system gets a fatal kernel mode translation fault, but that's another story.) Hope this helps. -- George I would expect to see some messages ERR != 0 when you plug the device. Can you show both usbdump output and dmesg output which belongs together? --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ulpt can't attach Lexmark E120
On 08/23/13 02:18, Hans Petter Selasky wrote: On 08/23/13 02:29, George Mitchell wrote: On 08/22/13 07:34, Hans Petter Selasky wrote: Here's the result: [...] (at which point if I type control-c to stop usbdump, the system gets a fatal kernel mode translation fault, but that's another story.) Hope this helps. -- George I would expect to see some messages ERR != 0 when you plug the device. Can you show both usbdump output and dmesg output which belongs together? --HPS Not sure exactly how I would get the usbdump output and log output interspersed in the correct order, and the fact that the pi panics when I type control-C at usbdump doesn't help. Subjectively, the "ulpt0 attach returned 12" seemed to occur a fraction of a second later than the others. But I'll see what I can come up with this evening. -- George ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ulpt can't attach Lexmark E120
On 08/23/13 07:11, George Mitchell wrote: On 08/23/13 02:18, Hans Petter Selasky wrote: On 08/23/13 02:29, George Mitchell wrote: On 08/22/13 07:34, Hans Petter Selasky wrote: Here's the result: [...] (at which point if I type control-c to stop usbdump, the system gets a fatal kernel mode translation fault, but that's another story.) Hope this helps. -- George I would expect to see some messages ERR != 0 when you plug the device. Can you show both usbdump output and dmesg output which belongs together? --HPS Not sure exactly how I would get the usbdump output and log output interspersed in the correct order, and the fact that the pi panics when I type control-C at usbdump doesn't help. Subjectively, the "ulpt0 attach returned 12" seemed to occur a fraction of a second later than the others. But I'll see what I can come up with this evening. -- George Well, what I ended up doing is turning on ulpt debugging and then piping usbdump into logger, yielding the attachment. But I'm not 100% sure that the output is in the proper sequence. Give that the printer works fine with the same code on my amd64 machines, does this suggest we have a byte-ordering problem in the driver? -- George Aug 24 00:10:24 pi kernel: ugen0.5: at usbus0 Aug 24 00:10:24 pi kernel: ulpt_probe: Aug 24 00:10:24 pi kernel: ulpt_probe: Aug 24 00:10:24 pi kernel: ulpt_attach: sc=0xc2d46a00 Aug 24 00:10:24 pi kernel: ulpt0: on usbus0 Aug 24 00:10:24 pi kernel: ulpt_attach: setting alternate config number: 0 Aug 24 00:10:24 pi kernel: ulpt_attach: error=USB_ERR_INVAL Aug 24 00:10:24 pi kernel: ulpt_detach: sc=0xc2d46a00 Aug 24 00:10:24 pi kernel: device_attach: ulpt0 attach returned 12 Aug 24 00:10:24 pi george: 00:08:02.619534 usbus0.5 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.620189 usbus0.5 DONE-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.620282 usbus0.5 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.621186 usbus0.5 DONE-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.638617 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.640299 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.640802 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.643668 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=20,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.643831 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.646289 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.646389 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.648294 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.648404 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.650283 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.650380 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.658667 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=16,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.658783 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.661289 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.661386 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.664291 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=44,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.664404 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.666289 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.666387 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.668663 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=28,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.668850 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.671284 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=12,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.671411 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.678038 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=32,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.678144 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.680296 usbus0.5
Re: ulpt can't attach Lexmark E120
On 08/24/13 02:44, George Mitchell wrote: On 08/23/13 07:11, George Mitchell wrote: On 08/23/13 02:18, Hans Petter Selasky wrote: On 08/23/13 02:29, George Mitchell wrote: On 08/22/13 07:34, Hans Petter Selasky wrote: Give that the printer works fine with the same code on my amd64 machines, does this suggest we have a byte-ordering problem in the driver? -- George Hi, I looked at the code and your debug prints, and it looks like the usbd_transfer_setup() function is to blame. To get further debugging here, you need to enable hw.usb.debug=15 and hw.usb.dwcotg.debug=15 or something like that. error = usbd_transfer_setup(uaa->device, &iface_index, sc->sc_xfer, ulpt_config, ULPT_N_TRANSFER, sc, &sc->sc_mtx); I think this should be trivial to fix one the cause is found. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ulpt can't attach Lexmark E120
On 08/24/13 02:14, Hans Petter Selasky wrote: On 08/24/13 02:44, George Mitchell wrote: On 08/23/13 07:11, George Mitchell wrote: On 08/23/13 02:18, Hans Petter Selasky wrote: On 08/23/13 02:29, George Mitchell wrote: On 08/22/13 07:34, Hans Petter Selasky wrote: Give that the printer works fine with the same code on my amd64 machines, does this suggest we have a byte-ordering problem in the driver? -- George Hi, I looked at the code and your debug prints, and it looks like the usbd_transfer_setup() function is to blame. To get further debugging here, you need to enable hw.usb.debug=15 and hw.usb.dwcotg.debug=15 or something like that. error = usbd_transfer_setup(uaa->device, &iface_index, sc->sc_xfer, ulpt_config, ULPT_N_TRANSFER, sc, &sc->sc_mtx); I think this should be trivial to fix one the cause is found. --HPS Setting hw.usb.dwc_otg.debug to any value greater than 0 generates an unending stream of debug output and effectively locks up the chip scrolling the output on the display. Perhaps there are some specific debug messages I could put in ... -- George ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ulpt can't attach Lexmark E120
On 08/24/13 20:21, George Mitchell wrote: Setting hw.usb.dwc_otg.debug to any value greater than 0 generates an unending stream of debug output and effectively locks up the chip scrolling the output on the display. Perhaps there are some specific debug messages I could put in ... -- George Hi, Can you try this patch: http://svnweb.freebsd.org/changeset/base/254828 --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ulpt can't attach Lexmark E120
On 08/25/13 04:44, Hans Petter Selasky wrote: On 08/24/13 20:21, George Mitchell wrote: Setting hw.usb.dwc_otg.debug to any value greater than 0 generates an unending stream of debug output and effectively locks up the chip scrolling the output on the display. Perhaps there are some specific debug messages I could put in ... -- George Hi, Can you try this patch: http://svnweb.freebsd.org/changeset/base/254828 --HPS ___ [...] I started trying to do too many things at once, and as a result it's going to take me a little while to try this patch out. My apologies! -- George ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ulpt can't attach Lexmark E120
On 08/25/13 19:20, George Mitchell wrote: On 08/25/13 04:44, Hans Petter Selasky wrote: On 08/24/13 20:21, George Mitchell wrote: Setting hw.usb.dwc_otg.debug to any value greater than 0 generates an unending stream of debug output and effectively locks up the chip scrolling the output on the display. Perhaps there are some specific debug messages I could put in ... -- George Hi, Can you try this patch: http://svnweb.freebsd.org/changeset/base/254828 --HPS ___ [...] I started trying to do too many things at once, and as a result it's going to take me a little while to try this patch out. My apologies! -- George Now that I have put my RPi build environment back together, I hope to try your patch tonight. Sorry for the delay! -- George ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ulpt can't attach Lexmark E120
On 08/25/13 04:44, Hans Petter Selasky wrote: On 08/24/13 20:21, George Mitchell wrote: Setting hw.usb.dwc_otg.debug to any value greater than 0 generates an unending stream of debug output and effectively locks up the chip scrolling the output on the display. Perhaps there are some specific debug messages I could put in ... -- George Hi, Can you try this patch: http://svnweb.freebsd.org/changeset/base/254828 --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" Sorry, no more progress yet. My RPi build system is generating emptyimages for some reason, so I will start over with it. -- George ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ulpt can't attach Lexmark E120
On 08/25/13 04:44, Hans Petter Selasky wrote: On 08/24/13 20:21, George Mitchell wrote: Setting hw.usb.dwc_otg.debug to any value greater than 0 generates an unending stream of debug output and effectively locks up the chip scrolling the output on the display. Perhaps there are some specific debug messages I could put in ... -- George Hi, Can you try this patch: http://svnweb.freebsd.org/changeset/base/254828 --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" Finally my RPi build system is working again and I can happily report that my Lexmark printer attaches successfully! Thank you! (And I note the patch has been checked into the repository.) -- George ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ulpt can't attach Lexmark E120
On Sunday 27 January 2013 17:14:55 George Mitchell wrote: > System: Raspberry Pi > uname: r245840M (Alie Tan's image from 25 January) > > By comparison, this Lexmark E120 printer attaches and prints with no > difficulty on FreeBSD-9.1-RELEASE, but on CURRENT, it says: > > ugen0.5: at usbus0 > ulpt1: addr 5> on usbus0 > device_attach: ulpt1 attach returned 12 > > Also, an HP CM1015 attaches without a problem. What should I try next? > -- George Mitchell Hi, Can you make a trace using usbdump for both cases? Also output from usbconfig is relevant. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ulpt can't attach Lexmark E120
On Sunday 27 January 2013 17:14:55 George Mitchell wrote: > System: Raspberry Pi > uname: r245840M (Alie Tan's image from 25 January) > > By comparison, this Lexmark E120 printer attaches and prints with no > difficulty on FreeBSD-9.1-RELEASE, but on CURRENT, it says: > > ugen0.5: at usbus0 > ulpt1: addr 5> on usbus0 > device_attach: ulpt1 attach returned 12 > > Also, an HP CM1015 attaches without a problem. What should I try next? Also try to set: sysctl hw.usb.ulpt.debug=15 before attaching. Also try to attach one printer alone. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ulpt can't attach Lexmark E120
On Sunday 27 January 2013 19:06:36 George Mitchell wrote: > On 01/27/13 11:33, Hans Petter Selasky wrote: > > On Sunday 27 January 2013 17:14:55 George Mitchell wrote: > >> System: Raspberry Pi > >> uname: r245840M (Alie Tan's image from 25 January) > >> > >> By comparison, this Lexmark E120 printer attaches and prints with no > >> difficulty on FreeBSD-9.1-RELEASE, but on CURRENT, it says: > >> > >> ugen0.5: at usbus0 > >> ulpt1: >> addr 5> on usbus0 > >> device_attach: ulpt1 attach returned 12 > >> > >> Also, an HP CM1015 attaches without a problem. What should I try next? > > > > Also try to set: > > > > sysctl hw.usb.ulpt.debug=15 > > It's a non-debug build of ulpt, so that doesn't exist: > sysctl: unknown oid 'hw.usb.ulpt.debug': No such file or directory > > > before attaching. > > > > Also try to attach one printer alone. > > > > --HPS > > After unplugging the HP: > > root@pi:/home/george # usbconfig > ugen0.1: at usbus0, cfg=0 md=HOST spd=HIGH > (480Mbps) pwr=SAVE > ugen0.2: at usbus0, cfg=0 md=HOST > spd=HIGH (480Mbps) pwr=SAVE > ugen0.3: at usbus0, cfg=0 md=HOST > spd=HIGH (480Mbps) pwr=ON > ugen0.4: at usbus0, cfg=0 md=HOST > spd=FULL (12Mbps) pwr=ON > > I attached the usbdump output, though there seem to be quite a few > packets not connected with ulpt burying the interesting packets in > the noise. -- George Hi, I don't see any errors in the usbdump trace you sent. So we can at least rule that out. Hint: You can filter traffic using the -f option for usbdump. What does: usbconfig dump_device_desc dump_curr_config_desc output? Can you also get same output from working system? --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ulpt can't attach Lexmark E120
On 01/27/13 11:33, Hans Petter Selasky wrote: > On Sunday 27 January 2013 17:14:55 George Mitchell wrote: >> System: Raspberry Pi >> uname: r245840M (Alie Tan's image from 25 January) >> >> By comparison, this Lexmark E120 printer attaches and prints with no >> difficulty on FreeBSD-9.1-RELEASE, but on CURRENT, it says: >> >> ugen0.5: at usbus0 >> ulpt1: > addr 5> on usbus0 >> device_attach: ulpt1 attach returned 12 >> >> Also, an HP CM1015 attaches without a problem. What should I try next? > > Also try to set: > > sysctl hw.usb.ulpt.debug=15 It's a non-debug build of ulpt, so that doesn't exist: sysctl: unknown oid 'hw.usb.ulpt.debug': No such file or directory > > before attaching. > > Also try to attach one printer alone. > > --HPS > After unplugging the HP: root@pi:/home/george # usbconfig ugen0.1: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.3: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON I attached the usbdump output, though there seem to be quite a few packets not connected with ulpt burying the interesting packets in the noise. -- George ulpt.usbdump.xz Description: Binary data ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ulpt can't attach Lexmark E120
On 01/27/13 13:15, Hans Petter Selasky wrote: [...] Hi, I don't see any errors in the usbdump trace you sent. So we can at least rule that out. Hint: You can filter traffic using the -f option for usbdump. What does: usbconfig dump_device_desc dump_curr_config_desc output? Can you also get same output from working system? --HPS Attachment 1 from Raspberry Pi. Attachment 2 from 9.1-RELEASE on amd64. -- George [...] ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0010 idVendor = 0x043d idProduct = 0x00cc bcdDevice = 0x0100 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 <9947W2Z> bNumConfigurations = 0x0001 Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0020 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x bmAttributes = 0x00c0 bMaxPower = 0x0001 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x0007 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0002 iInterface = 0x Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0001 bmAttributes = 0x0002 wMaxPacketSize = 0x0040 bInterval = 0x bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0088 bmAttributes = 0x0002 wMaxPacketSize = 0x0020 bInterval = 0x bRefresh = 0x bSynchAddress = 0x [...] ugen0.2: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0010 idVendor = 0x043d idProduct = 0x00cc bcdDevice = 0x0100 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 <9947W2Z> bNumConfigurations = 0x0001 Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0020 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x bmAttributes = 0x00c0 bMaxPower = 0x0001 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x0007 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0002 iInterface = 0x Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0001 bmAttributes = 0x0002 wMaxPacketSize = 0x0040 bInterval = 0x bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0088 bmAttributes = 0x0002 wMaxPacketSize = 0x0020 bInterval = 0x bRefresh = 0x bSynchAddress = 0x ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ulpt can't attach Lexmark E120
On Sunday 27 January 2013 19:24:01 George Mitchell wrote: > On 01/27/13 13:15, Hans Petter Selasky wrote: > > [...] > > > > Hi, > > > > I don't see any errors in the usbdump trace you sent. So we can at least > > rule that out. > > > > Hint: You can filter traffic using the -f option for usbdump. > > > > What does: > > > > usbconfig dump_device_desc dump_curr_config_desc > > > > output? Can you also get same output from working system? > > > > --HPS > > Attachment 1 from Raspberry Pi. > Attachment 2 from 9.1-RELEASE on amd64. -- George Hi, These look identical. I suspect it is a problem to allocate memory for the USB transfers. I need output when hw.usb.ulpt.debug=15 to say exactly. Could you ask the provider of the binaries to compile having USB_DEBUG set, also for the modules. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ulpt can't attach Lexmark E120
On 01/27/13 14:07, Hans Petter Selasky wrote: On Sunday 27 January 2013 19:24:01 George Mitchell wrote: On 01/27/13 13:15, Hans Petter Selasky wrote: [...] Hi, I don't see any errors in the usbdump trace you sent. So we can at least rule that out. Hint: You can filter traffic using the -f option for usbdump. What does: usbconfig dump_device_desc dump_curr_config_desc output? Can you also get same output from working system? --HPS Attachment 1 from Raspberry Pi. Attachment 2 from 9.1-RELEASE on amd64. -- George Hi, These look identical. I suspect it is a problem to allocate memory for the USB transfers. I need output when hw.usb.ulpt.debug=15 to say exactly. Could you ask the provider of the binaries to compile having USB_DEBUG set, also for the modules. --HPS I'm working on getting a debug build ... Thanks for your help so far. I notice that there seem to be only trivial differences between the 9.1 release ulpt and the 10.0 current ulpt driver. -- George ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Re: ulpt can't attach Lexmark E120
As I was saying a few minutes ago ... On 01/27/13 17:32, George Mitchell wrote: On 01/27/13 14:07, Hans Petter Selasky wrote: [...] I need output when hw.usb.ulpt.debug=15 to say exactly. Could you ask the provider of the binaries to compile having USB_DEBUG set, also for the modules. --HPS I'm working on getting a debug build ... Thanks for your help so far. I notice that there seem to be only trivial differences between the 9.1 release ulpt and the 10.0 current ulpt driver. -- George (This is on a Raspberry Pi.) It took me a bit longer than anticipated, but here is the output, from an image built over last weekend: Aug 22 11:15:09 pi kernel: ugen0.5: at usbus0 Aug 22 11:15:09 pi kernel: ulpt_probe: Aug 22 11:15:09 pi kernel: ulpt_probe: Aug 22 11:15:09 pi kernel: ulpt_attach: sc=0xc2d43800 Aug 22 11:15:09 pi kernel: ulpt0: on usbus0 Aug 22 11:15:09 pi kernel: ulpt_attach: setting alternate config number: 0 Aug 22 11:15:09 pi kernel: ulpt_attach: error=USB_ERR_INVAL Aug 22 11:15:09 pi kernel: ulpt_detach: sc=0xc2d43800 Aug 22 11:15:09 pi kernel: device_attach: ulpt0 attach returned 12 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
