Puppy 5.x no print via USB
Posted: Tue 08 Jan 2013, 06:24
I'm trying to use this aging HP Pavilion a556x desktop. I say aging because the hard drive is dead. I booted from several Puppy live CDs and installed them to a flash drive, then booted from the flash drive.
I've tried Slacko 5.4, working now, Slacko 5.3.3, and Lucid 5.2.8, and I think a couple more.
All work perfectly, except for this:
The local printer, an HP 5610 AIO, installs normally, and files sent to it just disappear into a bitbucket. No response. Tried a different cable. No difference.
Tried a different USB port; no difference.
<later>
Other live CDs, and the CentOS6 that I have installed on the new hard drive, find the printer and work with it just fine. I.e., the problem is not in the cable, and not in the printer.
But all of the 5.x Puppies that I have tried work exactly the same way. They see the printer, install it normally, and print normally. ... but nothing comes out of the printer, and there is no sign that anything goes in, either. No flashing power light, no R2D2 noises, nothing.
Is there some disconnect in the data flow between the printing code and the USB port in Puppy 5.x?
Is there a way to track this problem down further?
I've tried Slacko 5.4, working now, Slacko 5.3.3, and Lucid 5.2.8, and I think a couple more.
All work perfectly, except for this:
The local printer, an HP 5610 AIO, installs normally, and files sent to it just disappear into a bitbucket. No response. Tried a different cable. No difference.
Tried a different USB port; no difference.
<later>
Other live CDs, and the CentOS6 that I have installed on the new hard drive, find the printer and work with it just fine. I.e., the problem is not in the cable, and not in the printer.
But all of the 5.x Puppies that I have tried work exactly the same way. They see the printer, install it normally, and print normally. ... but nothing comes out of the printer, and there is no sign that anything goes in, either. No flashing power light, no R2D2 noises, nothing.
Is there some disconnect in the data flow between the printing code and the USB port in Puppy 5.x?
Is there a way to track this problem down further?