[comp.unix.questions] Why has my printer died?

HCART%VAX.OXFORD.AC.UK@cunyvm.cuny.edu (10/16/89)

    I have a malibu printer on an IRIS 3130. The printer has been working
OK for some time, but now refuses to print. lpstat -t gives the
error message

    disabled by scheduler: can't open /dev/ttyd3

    As far as I can see, all the permissions are as they always were
and resetting them to their old values does not trigger the
scheduler. Stopping and starting the print queue has no effect.

    Could this be a hardware problem? When the scheduler complains
that it cannot open ttyd3 can it only be referring to the file /dev/ttyd3,
or could it be referring to the physical line? Would I get a different
message from lpstat if it couldn't activate the printer? Any help
much appreciated.

Hugh Cartwright, Oxford University.

cpcahil@virtech.UUCP (Conor P. Cahill) (10/17/89)

In article <21162@adm.BRL.MIL>, HCART%VAX.OXFORD.AC.UK@cunyvm.cuny.edu writes:
>     Could this be a hardware problem? When the scheduler complains
> that it cannot open ttyd3 can it only be referring to the file /dev/ttyd3,
> or could it be referring to the physical line? Would I get a different

It can refer to both.  Look at the possible errors you can expect from 
open(2) for a complete list.

> message from lpstat if it couldn't activate the printer? Any help
> much appreciated.

The first thing I would try is "(stty baudrate;echo hello)> /dev/ttyd3 <&1"
to verify that the port can't be opened.  If you get a "cant open ...", then
I would try to reboot the system (make sure you power cycle the machine). 
If the printer port still won't work, switch the printer to another port (make
sure you turn off any applicable gettys that may be running on the second port).

If the printer works on the second port, the problem is probably in the 
serial port hardware.

If it still doesn't work, try a new cable.  If it still doesn't work, 
try another printer or substitute a terminal just to see if you get
any data on the line.

-- 
+-----------------------------------------------------------------------+
| Conor P. Cahill     uunet!virtech!cpcahil      	703-430-9247	!
| Virtual Technologies Inc.,    P. O. Box 876,   Sterling, VA 22170     |
+-----------------------------------------------------------------------+

draeger@uunet.uu.net (Frank Draeger) (10/19/89)

> 
> error message
> 
>     disabled by scheduler: can't open /dev/ttyd3
> 
>     Could this be a hardware problem? When the scheduler complains
Yes and no. If someone turned the printer off to feed to the next page
the interface couldn't reach the printer. So the printer will be disabled.
This will also happen if the line has been dropped.
In these cases it would be enough to enable the device again after 
reconnecting the printer .

		I hope this was it  .
> 
> Hugh Cartwright, Oxford University.
> 

_______________________________________________________________________________
| Frank Draeger,Dortmund,W-Germany     |     Snoopy wrote his own book :      |
+--------------------------------------+                                      |
| UseNet:	draeger@quando.uucp    |        " The adventures of           |
| UUCP  :	..!unido!quando!draeger|          Hucklebeagle Finn "         |
_______________________________________________________________________________