Date: Tue, 22 Jun 2004 23:08:08 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> To: le@FreeBSD.org Cc: current@FreeBSD.org Subject: Re: Testers wanted: USB printers Message-ID: <200406230608.i5N688qV053342@gw.catspoiler.org> In-Reply-To: <20040622191512.Y562@gravy.kishka.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 22 Jun 2004, Lukas Ertl wrote: > Hi, > > I'd like to merge a ulpt(4) patch from NetBSD, but since I don't have a > USB printer I'd be glad if someone out there owning such a piece of > hardware could test it: > > <http://people.freebsd.org/~le/ulpt.diff>; > > Thank you, > le I hadn't hooked my Epson ink jet printer to my -CURRENT box before, so I didn't know what bugs lurked there (the USB ports on my -CURRENT box weren't working at all until recently) prior to this patch. My printer only seems to get recognized if it is hooked up and powered on when the system boots. Jun 22 22:04:20 scratch kernel: uhci0: <VIA 83C572 USB controller> port 0xc800-0 xc81f irq 10 at device 7.2 on pci0 Jun 22 22:04:20 scratch kernel: uhci0: [GIANT-LOCKED] Jun 22 22:04:20 scratch kernel: usb0: <VIA 83C572 USB controller> on uhci0 Jun 22 22:04:20 scratch kernel: usb0: USB revision 1.0 Jun 22 22:04:20 scratch kernel: uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1. 00, addr 1 Jun 22 22:04:20 scratch kernel: uhub0: 2 ports with 2 removable, self powered Jun 22 22:04:20 scratch kernel: ulpt0: EPSON USB Printer, rev 1.10/1.00, addr 2, iclass 7/1 Jun 22 22:04:20 scratch kernel: ulpt0: using bi-directional mode Jun 22 22:04:20 scratch kernel: uhci1: <VIA 83C572 USB controller> port 0xcc00-0 xcc1f irq 10 at device 7.3 on pci0 Jun 22 22:04:20 scratch kernel: uhci1: [GIANT-LOCKED] Jun 22 22:04:20 scratch kernel: usb1: <VIA 83C572 USB controller> on uhci1 Jun 22 22:04:20 scratch kernel: usb1: USB revision 1.0 Jun 22 22:04:20 scratch kernel: uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1. 00, addr 1 Jun 22 22:04:20 scratch kernel: uhub1: 2 ports with 2 removable, self powered If I then power cycle the printer, the printer goes away and never comes back. Jun 22 22:05:25 scratch kernel: ulpt0: at uhub0 port 1 (addr 2) disconnected Jun 22 22:05:25 scratch kernel: ulpt0: detached This behaviour is the same with and without the patch. If I boot the system and then plug in the printer, it doesn't get recognized. The following message was printed when I powered the printer off in this state: Jun 22 22:01:44 scratch kernel: uhub0: device problem, disabling port 1 Jun 22 22:01:44 scratch kernel: uhub0: port error, restarting port 1 This happens both with and without the patch. I was more interested in the new capability to read data back from the printer which was added by this patch. I've been wanting this ability for a long time so that I can check the printer's ink levels. This isn't looking promising, though, since my attempt to retrieve the printer make and model information didn't work. The process hung for quite a while in the "usbsyn" state, and then failed with an EBUSY. # escputil -r /dev/ulpt0 -u -d Escputil version 4.2.6, Copyright (C) 2000-2001 Robert Krawitz Escputil comes with ABSOLUTELY NO WARRANTY; for details type 'escputil -l' This is free software, and you are welcome to redistribute it under certain conditions; type 'escputil -l' for details. Cannot open /dev/ulpt0 read/write: Device busy #ps lax | grep escp 0 718 638 0 -8 0 2620 1324 usbsyn D+ p0 0:00.01 escputil -r I can't print a nozzle test pattern either. #escputil -r /dev/ulpt0 -u -n Escputil version 4.2.6, Copyright (C) 2000-2001 Robert Krawitz Escputil comes with ABSOLUTELY NO WARRANTY; for details type 'escputil -l' This is free software, and you are welcome to redistribute it under certain conditions; type 'escputil -l' for details. Running nozzle check, please ensure paper is in the printer. Cannot open device /dev/ulpt0: Device busy I see this problem both with and without the patch. The printer works on my -STABLE box except for the features that require data to be retrieved from the printer. It looks like there are some bugs in uhci and/or ulpt in -CURRENT that prevent me from doing a meaningful test on your patch B-(
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200406230608.i5N688qV053342>