we actually have a Xerox Phaser 6010 and we are looking for use it with cups.
The problem is that the cups server is running on a debian 64 bit OS and the Xerox website only provide 32 bit driver .deb
(there is also a .rpm driver tag as 32 and 64 bits, but after convert it with "alien" command line we still have a driver 32 bits)
Is it possible to have Phaser 6010 driver .deb 64 bits version or source to compile it ourself ?
Regards, and thanks in advance,
Solved! Go to Solution.
I have a similar problems to run recommended driver for cups under Red Hat 6 (64 bit).
(Driver not recognized with cups 1.4.2, does not printing with cups 1.5.0, reported at grayscale ...)
Could you update us about planned new releases or when it will work with RH 6 ?
Driver for redhat will work in linux 32bit mode.
One way to do so is to modify startup in /etc/init.d/cups
and install 32bit-libs by starting linux32-shell with "linux32" and install 32bit-libs of cups by "yum install cups-libs". restart cups afterwards.
Note: After this change cups cannot be stopped correctly.
Simple pdfs will work. Some complex pdfs might fail.
Any hope of getting the 64 bit Linux drivers any time soon? Especially drivers for amd64 would be most appreciated by all Linux users in our company.
When I had an older 64 bit Ubuntu (with possibly CUPS 1.5.0) I just manually extracted the contents of the provided 32 bit DEB archive to their proper places and surprisingly it just worked. No such luck with my current Debian installation (I've tried lots of different CUPS versions) so I'm using my crappy old inkjet printer once again.
With my current Debian installation I always just get /usr/lib/cups/filter/xrhkazmf failed :(
Fortunately we had an old 32 bit Linux machine lying around and connected to our LAN. After installing the printer drivers, adding the printer (remembering to check the 'shared' checkbox in CUPS) and also enabling sharing in the CUPS Administration main page our 64 bit machines discovered the shared printer immediately and now work without a hitch.
I have a 6015NI and got the 32 bit deb driver running under 64 bit Ubuntu 11.04, cups ver 1.4.6-5ubuntu1.4. This was done by manually copying the .deb package contents to their respective directories. To make life easier, I started a file manager session as root.
I got the idea from here but I diidn't run into any the issues he/she found. It might have worked well because files that existed in both .deb and .rpm were the same size - not sure. The .rpm is listed as being 64 bit compatible so at first I tried to convert it with alien which didn't work. All I got was a "this is a i386 package error" or words to that effect
Having an NI, I configured my printer for wireless and that worked also. I just had to select network printer and wait for the printer to autodetect (when the icon in the lower left of the dialog stopped spinning) Clicking "Find Network Printer" asked me for a login which was a red herring.
Don't know if I'll hit ranezu's issue though if I move beyond cups 1.4.6-5
I had gotten a 6015NI to work using a similar method as Elwood on 12.04LTS x64, but I never tested color images. after upgrading to 12.10, the method still works for hte test page and normal black and white text docs, but color images come out looking like thermal imaging camera vision but more random. the printer works fine from windows XP, which I run in a virtual machine. it's kind of anoying to have to boot my vm just to print something in color.
I got this printer for home, but I'm head of IT for a small company, and being able to print from linux is something that's important to our production there. If Xerox can't make a reliable linux print driver, it's going to be difficult for me to even consider them. I don't really like having to stick with HP's just because they're the only ones with solid and reliable linux support across their product lines.
Time to step up Xerox, I really want to love this little printer, but you're making it hard for me to do so.
I have shared your post with our driver developers. They have asked that I find out which drivers you are using and which version of Linux you are on.