Date: Sun, 6 Apr 2003 12:05:24 -0500 From: Marc Wiz <marc@wiz.com> To: freebsd-questions@freebsd.org Subject: Re: USB Printer Message-ID: <20030406170524.GB4490@freshaire.wiz.com> In-Reply-To: <16016.23766.995945.259510@guru.mired.org> References: <20030406161652.GA4518@freshaire.wiz.com> <16016.23766.995945.259510@guru.mired.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Apr 06, 2003 at 11:59:02AM -0500, Mike Meyer wrote: > In <20030406161652.GA4518@freshaire.wiz.com>, Marc Wiz <marc@wiz.com> typed: > > Now here comes the interesting part since I figured it would be a > > good idea to start debugging this with a simple setup (no printer > > spooler, etc.) I have tried to do echo "hello there" > /dev/ulpt0 > > and nothing happens. > > It takes about 30 seconds before the command ends. > > This was interpreted as meaning that this was a winprinter. However... Right :-) That's why I did what I did with another OS :-) > > > If I try the echo using Linux the printer works just fine. I.e. a page is > > printed with "hello there". > > That's not good. That sounds like it isn't a winprinter, but the > driver is just not working. I don't know anything about USB (yet :-) but I wonder why other USB printers work. > > > The code is compiled into the kernel (not a module) > > > > Any suggestions as to how to proceed? Are there any driver debug options > > that can be enabled either for USB or the printer code? > > You can enable USB_DEBUG at kernel build time, then use "gdb -k" to > set ulptdebug in ulpt.c to positive values - increasing values get you > increasing levels of debug information. Thanks! I will build a new kernel and try that. Marc -- Marc Wiz marc@wiz.com Yes, that really is my last name.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030406170524.GB4490>