After much head scratching and throwing most of a ream of paper into the trash, I just found and solved the problem.
Thinking that perhaps I have a cable issue, I was re-seating the usb cable that connects my Xerox Phaser 3250 printer to the computer and realized that the printer was plugged into a USB 3.0 port on my computer. When I moved it to a USB 2.0 port, the printer immediately started working properly using the Xerox Phaser 3150 driver that comes with cups, just like it always did under Centos 6.
The computer must have been pushing data to the printer too quickly over the USB 3.0 port; the printer got a garbled postscript instruction and everything went downhill from there.
Now I'm pretty happy -- my printer works again. I've taped a note to the printer to be damn sure that I remember to always plug it into a USB 2.0 port in the future.
On Wed, Jul 30, 2014 at 11:03:03PM -0600, Frank Cox wrote:
After much head scratching and throwing most of a ream of paper into the trash, I just found and solved the problem.
Thinking that perhaps I have a cable issue, I was re-seating the usb cable that connects my Xerox Phaser 3250 printer to the computer and realized that the printer was plugged into a USB 3.0 port on my computer. When I moved it to a USB 2.0 port, the printer immediately started working properly using the Xerox Phaser 3150 driver that comes with cups, just like it always did under Centos 6.
The computer must have been pushing data to the printer too quickly over the USB 3.0 port; the printer got a garbled postscript instruction and everything went downhill from there.
Now I'm pretty happy -- my printer works again. I've taped a note to the printer to be damn sure that I remember to always plug it into a USB 2.0 port in the future.
Frank, et al: FYI, and this may or may not be related...
I bought a Venus DS3R PRO2 storage box a while back. this device offers USB-3 or eSata connectivity. I quickly found that when using a USB-3 cable and connecting to the USB-3 ports on my motherboard, that it would work for a short while then the system could no longer access it, the /dev/<node> would disappear and the only way to get it back was to reboot. (note that eSata worked fine, and still does).
incidentally, using USB2 appears to work even when connected to the USB-3 connector on the mommyboard.
I tried a rawhide live cd and it had the same issue, but I reported it to Fedora (I know, we're on a Cenots list right now) and in a while a fix came down. So perhaps it would work on C7, haven't tried it yet.
Fred
-- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 7/30/2014 10:03 PM, Frank Cox wrote:
The computer must have been pushing data to the printer too quickly over the USB 3.0 port; the printer got a garbled postscript instruction and everything went downhill from there.
that doesn't compute. USB 3 uses a different (new) set of 5 pins on the same connector, but the original 4 pins are still there and support USB 1 and 2. A more likely explanation is that the device driver for this printer isn't enumerating USB devices correctly, or isn't handling some additional usb3 related port-specific status information correctly, so its getting confused.
The whole USB spec is a ungawdly mess now with layers and layers of BS piled up on a shakey foundation, and complicated APIs to access all this.
John R Pierce wrote:
On 7/30/2014 10:03 PM, Frank Cox wrote:
The computer must have been pushing data to the printer too quickly over the USB 3.0 port; the printer got a garbled postscript instruction and everything went downhill from there.
that doesn't compute. USB 3 uses a different (new) set of 5 pins on the same connector, but the original 4 pins are still there and support USB 1 and 2. A more likely explanation is that the device driver for this printer isn't enumerating USB devices correctly, or isn't handling some additional usb3 related port-specific status information correctly, so its getting confused.
The whole USB spec is a ungawdly mess now with layers and layers of BS piled up on a shakey foundation, and complicated APIs to access all this.
Is that why my DD-WRT router keeps forgetting about my USB printer? <g>
mark
PS Out of here for a while, on vacation