Ready to smash Epson-c80

[mhoskins]

I've had this printer working for months now. It was working well when my wife printed a bunch of web pages. In the middle of one of them, it lost its mind. I can't get the darn thing to behave. I can print one job, and that doesn't print right. A two line text file uses about five pages and prints garbage. After that, any other job blinks the data/power light for a few short seconds and prints nothing.

A longer text test print causes even odder behavior. It stops mid-page with the data light still blinking.

I have left the darn thing unplugged overnight with no change. I have deleted and reconfigured the printer from CUPS. I have used the Epson C80 config, or the generic/postscript config - which I think it was using at the time of the trainwreck.

That was two days ago. I'm about ready to sell it for scrap.

Help.

[mhoskins]

Response from the device is inconsistent.

puter:mike:$ escputil -q -s -m c80 --raw-device=/dev/printers/0
Read from printer timed out
Read from printer timed out

puter:mike:$ escputil -q -s -m c80 --raw-device=/dev/printers/0
Read from printer timed out

puter:mike:$ escputil -q -s -m c80 --raw-device=/dev/printers/0
Read from printer timed out
@BDC ST
ST:03
IQ:4726282A
AI:CW:0232323232,MI:00
INK:1101,3202,4304,5408
IG:0108NA


Here's what's installed:

uter:mike:$ qpkg -v -I | egrep "cups|gimp|print"
gnome-base/libgnomeprint-2.6.0 *
gnome-base/libgnomeprintui-2.6.0 *
media-gfx/gimp-1.2.5 *
media-gfx/gimp-2.0.0 *
media-gfx/gimp-print-4.2.6 *
net-print/foomatic-db-engine-3.0.1 *
net-print/cups-1.1.20-r1 *
net-print/foomatic-db-20040302 *
net-print/cups-pdf-1.3.1 *
net-print/libgnomecups-0.1.6 *
net-print/foomatic-3.0.1 *
net-print/gnome-cups-manager-0.17 *
net-print/foomatic-filters-3.0.1 *
app-doc/gimp-user-manual-2.0 *

It's like something in the data stream from the last HTML page that was printing reprogrammed something somewhere: parallel port should be bone stupid, the printer? Is there a factory default reset for this beast?
_________________
--
To know even one life has breathed easier because you have lived.
This is to have succeeded. -Bessie Stanely, 1905

[mhoskins]

Response from the device is inconsistent.

puter:mike:$ escputil -q -s -m c80 --raw-device=/dev/printers/0
Read from printer timed out
Read from printer timed out

puter:mike:$ escputil -q -s -m c80 --raw-device=/dev/printers/0
Read from printer timed out

puter:mike:$ escputil -q -s -m c80 --raw-device=/dev/printers/0
Read from printer timed out
@BDC ST
ST:03
IQ:4726282A
AI:CW:0232323232,MI:00
INK:1101,3202,4304,5408
IG:0108NA


Here's what's installed:

uter:mike:$ qpkg -v -I | egrep "cups|gimp|print"
gnome-base/libgnomeprint-2.6.0 *
gnome-base/libgnomeprintui-2.6.0 *
media-gfx/gimp-1.2.5 *
media-gfx/gimp-2.0.0 *
media-gfx/gimp-print-4.2.6 *
net-print/foomatic-db-engine-3.0.1 *
net-print/cups-1.1.20-r1 *
net-print/foomatic-db-20040302 *
net-print/cups-pdf-1.3.1 *
net-print/libgnomecups-0.1.6 *
net-print/foomatic-3.0.1 *
net-print/gnome-cups-manager-0.17 *
net-print/foomatic-filters-3.0.1 *
app-doc/gimp-user-manual-2.0 *

It's like something in the data stream from the last HTML page that was printing reprogrammed something somewhere: parallel port should be bone stupid, the printer? Is there a factory default reset for this beast?
_________________
--
To know even one life has breathed easier because you have lived.
This is to have succeeded. -Bessie Stanely, 1905

[mhoskins]

It's well again. I don't know what fixed it, but something was out of whack and is now back in whack. It's been working for about two weeks now through several emerges without incident.

Go figure.

That's why my computer science degree is a BA - because it is definately an art.

Thanks to all who sympathized on the way by.
_________________
--
To know even one life has breathed easier because you have lived.
This is to have succeeded. -Bessie Stanely, 1905