Has this been fixed in the meanwhile? Would you recommend the 6000V/B or 6010n for a 64bit Debian/Ubuntu? I will most certainly not install another computer with PSU and CPU to act as printing nurse for the Xerox machine.
I think I found a workaround. Using the generic postscript driver from all the 64 bit Fedora 17 clients, the print jobs go to a F14 32bit machine setup as a print server and prints over USB. The 32 bit F14 driver works, so the client test pages using the generic ps driver and printing from apps work okay.
So all you need to make the 6010N work with 64 bit linux is a second computer running a 32 bit linux as an intermediary. What's that - maybe $400 extra to compensate for a broken driver.
I guess I know why Xerox keeps their drivers to themselves and does not release them for use in every mainstream distro - they are junk. I'm sure the inside reason is that they are very proprietary or it's licensed and all very complicated. But the out of the box experience with this Xerox 6010N - not very good guys.
On to the windows clients.
I just received my Phaser 6010N printer today from NewEgg. I pulled down the drivers from Xerox this afternoon. I set the printer up using a 32 bit Fedora 14 computer as a print server with the 6010N connected with USB. All the printing works fine from the local machine - test page, text docs, images, etc. So far, so good.
All of the clients on the network are Fedora 17 64 bit. the rpms installed find on the machines and the system-config-printer worked fine for setting up the clients with the correct driver using ipp - but the printouts are garbage. All the debug searches point to the driver being bad. All of the printed outputs look like this:
@JPL SET STRINGCODESET=UTF8
the test pages give this garbage, as do text files, images, and everything else I can attempt to print. Completely unusable.
Is there a workaround for this - or do you think this printer should going back to NewEgg?