Date: Sun, 6 Apr 2003 11:59:02 -0500 From: Mike Meyer <mwm-dated-1050080343.49c58b@mired.org> To: Marc Wiz <marc@wiz.com> Cc: freebsd-questions@freebsd.org Subject: Re: USB Printer Message-ID: <16016.23766.995945.259510@guru.mired.org> In-Reply-To: <20030406161652.GA4518@freshaire.wiz.com> References: <20030406161652.GA4518@freshaire.wiz.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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... > 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. > 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. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16016.23766.995945.259510>