"lptcontrol -ei -d /dev/lpt0" during boot time fails with "device busy" if the printer is turned off at that time. # dmesg|grep lpt lpt0: <Printer> on ppbus0 lpt0: Interrupt-driven port Fix: unknown. How-To-Repeat: Turn printer off. Type "lptcontrol -i -d /dev/lpt0".
On Mon, 6 Oct 2003, Klaus-J.Wolf wrote: > >Description: > "lptcontrol -ei -d /dev/lpt0" during boot time fails with "device busy" > if the printer is turned off at that time. lptcontrol should be run on the control device (not /dev/lptN). Support for using the control device automatically was broken in rev.1.8 of lptcontrol.c. Existence of the documented control device was broken in FreeBSD-5 as part of devfs lossage. The documented control device is "/dev/lpctlN" (see lptcontrol(8), but devfs creates "/dev/lptN.ctl". The lpt driver also has support for control bits in the minor number. (The control device is a special case of this -- it uses bit 0x80.) There are 6 control bits, giving a total of 64 possible devices per unit. devfs only creates 2 of these. Bruce
From the manual page: -d device Set the mode of the printer device specified by device. The default value for device is /dev/lpt0. :-(
State Changed From-To: open->patched C code and man page were overhauled. Should be clearer now.
Hi, this seems still broken on at least 5.3-BETA5 The manpage now says this: -d device Set the mode of the printer device specified by device. The default value for device is /dev/lpt0. But nothing works: # lptcontrol -p lptcontrol: open: Device busy # lptcontrol -p -d /dev/lpt0 lptcontrol: open: Device busy # lptcontrol -p -d /dev/lpt0.ctl lptcontrol: ioctl: Operation not supported Note that there is a pause before the error message gets displayed. There is a Scanner attached to the parallel port, disconnecting the scanner yields the same results. Coupled with the fact, that acpi "claims" the ppc(4) device and ignores settings in /boot/device.hints, this is rather annoying :( Ulrich Spoerlein -- PGP Key ID: F0DB9F44 Encrypted mail welcome! PGP Fingerprint: F1CE D062 0CA9 ADE3 349B 2FE8 980A C6B5 F0DB 9F44 Ok, which part of "Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn." didn't you understand?
MARKED AS SPAM
@Reporter/Ulrich, If this is still an issue, please re-open with addition details (if different from the original report