Date: Fri, 10 Feb 2006 22:56:33 GMT From: Steve Davidson <stevedav@sonic.net> To: freebsd-gnats-submit@FreeBSD.org Subject: usb/93155: /dev/ulpt0: device busy USB printer does not work Message-ID: <200602102256.k1AMuXgk082062@www.freebsd.org> Resent-Message-ID: <200602102300.k1AN0HMq025300@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 93155 >Category: usb >Synopsis: /dev/ulpt0: device busy USB printer does not work >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-usb >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Feb 10 23:00:17 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Steve Davidson >Release: 5.4 Release >Organization: >Environment: 5.4 Release USB printer attached -- this hardware works through Windows XP, so its not the cable or printer or USB port or power supply. >Description: Any attampt to write to /dev/ulpt0 or /dev/unlpt0 returns "device busy". Some dmesg output: lpt0: <Printer> on ppbus0 lpt0: Interrupt-driven port ulpt0: HP HP Business Inkjet 1000, rev 2.00/1.00, addr 2, iclass 7/1 ulpt0: using bi-directional mode The relevant devices: % ls -laq /dev/*lp* crw------- 1 root wheel 237, 0 Feb 10 13:53 /dev/lpt0 crw------- 1 root wheel 237, 128 Feb 10 13:53 /dev/lpt0.ctl crw-r--r-- 1 root operator 232, 0 Feb 10 13:53 /dev/ulpt0 crw-r--r-- 1 root operator 232, 64 Feb 10 13:53 /dev/unlpt0 Google research, bug searches, and FreeBSD usenet groups research suggests that MANY people have had this problem but no one has posted a solution. The printer prints correctly from the same hardware when running under Windows XP. >How-To-Repeat: Attach a USB printer and send some data to it: lptest > /dev/ulpt0 /dev/ulpt0: Device busy. lptest > /dev/unlpt0 /dev/unlpt0: Device busy. lptest > /dev/lpt0 /dev/lpt0: Device busy. >Fix: This could be a driver problem. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200602102256.k1AMuXgk082062>