From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 7 12:55:12 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0240937B401 for ; Thu, 7 Aug 2003 12:55:12 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF4A443F75 for ; Thu, 7 Aug 2003 12:55:10 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9/8.12.9) with ESMTP id h77JsiM7096099; Thu, 7 Aug 2003 12:54:48 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200308071954.h77JsiM7096099@gw.catspoiler.org> Date: Thu, 7 Aug 2003 12:54:44 -0700 (PDT) From: Don Lewis To: frank@exit.com In-Reply-To: <200308061959.h76JxghJ068620@realtime.exit.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: hackers@FreeBSD.org Subject: Re: USB versus SMP and Epson printers. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Aug 2003 19:55:12 -0000 On 6 Aug, Frank Mayhar wrote: > On Monday I received my brand-new Epson C82, a replacement for a 900N with > a dead print head. I had already configured CUPS so I imagined that I would > just hook it up with USB and everything would be happy. > > Well, that's not how it turned out. > > I tried two different machines, both with Tyan dual-CPU motherboards. One > is a Thunder 2500 (S1867) with dual PIII 866, my gateway/fax/server > box and the one I preferred. The other is my main desktop box, a Tiger > MPX (2466N-4M) with dual Athlon MP 1900+. Both displayed essentially > the same problem, although the Tiger MPX seemed to come a little bit > closer to working than the Thunder 2500. > > Basically, although usbdevs would show the device, when I tried to do, > say, an 'escputil -s -r /dev/ulpt0' (to show the ink levels), the process > would seem to send something to the printer (I say "seem to" because I > saw no evidence of it on the printer side), then sit in the USB code > forever, timing out and looping. Unless someone snuck it in while I wasn't looking, our ulpt implementation doesn't support reading data from the printer, so it's not possible to check the ink levels. I've had to boot Linux in order to do this.