This problem is a bit difficult for me to attempt because you are on 2.2.17, of which I have nil experience. However the problem seems somewhere between your lpd daemon and the kernel response.
Kernel 2.2.17 seems to be an okay kernel from the reports that I read, however, there has been one report on this list where the lp device just went non-functional on a running system which was not even rebooted.There were no takers for that post. That too was on 2.2.17 .. just kind of wondering, if John has managed to smell the rat ! Meanwhile, I am sending a detailed checklist in personal mail. Too long to place here... USM Bish On Thu, Sep 14, 2000 at 10:49:40PM -0700, John Gilger wrote: > USM Bish wrote: > > > > 2. LINUX: > > > > a) Do a dmesg. Check which device your printer is polled > > EpsonSC800 at /dev/lp0 > > > > b) Do a cat Txtfile > /dev/lpN (where N is the device polled) > > Prints fine (ascii text) > > > > > c) PrinterSetUp : If system installed properly, a printer > > software should have been installed (lpr or lprng): > > > > IS lpd daemon running ? > > YES > > > ELSE > > > > Try manually to get lpd to work and produce anything ! > > > > iii) Do a cat FileName | lpr > > IS something coming ? [Y/N] > > > > NO > > lpq returns: "Printer: [EMAIL PROTECTED] 'SC800L' > Queue: no printable jobs in queue > status: removing job '[EMAIL PROTECTED]' -ABORT at [time]" > > Debian 2.2 kernal 2.2.17 -- Bug in kernal? > > apsfilter with GS uniprint filters worked in SuSE, RH, Debian2.1, Slackware > ... > /etc/printcap looks same as prior setups. Again, bug in kernal 2.2.17? > > John >
