Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I ran into a strange problem.
- I run OpenSuse 11.0 and I am trying to install my Xerox 6110printer (which used to run fine on the same computer under OpenSuse 10.0).
- Cups is running fine and it recognizes the printer
- It just gave me a message saying that to change more elaborate option, I need to install the proprietary driver. Correct, I don't have a lot of printing options.
- I went to xerox's website and downloaded the correct linux print driver
- Unpacked it
- Changed correct permissions, including chmod +x
- If I open a terminal and su: ./setup.sh nothing happens, it jumps back to a new command prompt.
It's really driving me crazy, I am root, it is executable, and it doesn't work...
Any ideas on what I can try next to get the driver software installed?
If I open a terminal and su: ./setup.sh nothing happens, it jumps back to a new command prompt.
With linux commands, and shell scripts are "commands" too, if "nothing happens", then it is usually a good sign that things went OK.
"Error messages" are a bad sign.
You have run the script, it has done its thing, there were no error messages.
Try going back to cups, and maybe installing another instance of your printer, you could call it Xerox6110-new, maybe you'll get an option to use the Xerox driver this time. If it works better, set Xerox6110-new as your default printer.
I just tried the same program on another computer with OpenSuse 10.3 and it worked like a charm. After running the setup.sh, a graphical installer from Xerox popped up.
I think I will check in the script file to see if I might be missing some packages needed for this graphical installer...
Great, it seems that the 64 bit folders of the installer are empty. Probably has something to do with that...
And even better, it appears that this is by one of the only models in the series that doesn't support postscript.
I contacted the Xerox people about it, since they put Suse 7.1 > support on the features page.
Thanks everyone for your help.
I did copy the ppd file manually to the /usr/share/cups/model/xerox directory and was able to add the printer that way. However, cups gave me an error "Filter "ppmtosplc" for printer "phaser6110" not available: No such file or directory". When I went looking for the file, I noticed the 86_64 diretories were empty. Hence. Maybe I could take the 32 bit file and place it somewhere, but where does cups keep the filters?
I just tried the same program on another computer with OpenSuse 10.3 and it worked like a charm.
Would that have been a computer running a 32-bit kernel?
64-bit systems still seem to be having trouble with lots of things - flash, plugins, you name it.
Quote:
Maybe I could take the 32 bit file and place it somewhere
I don't think that you can do that, but am ready to be corrected.
Whilst the attractions of a 63-bit kernel are huge, there are currently so many inconsistencies, I'm sticking with a 32-bit install (well, I have only a 32-bit CPU, so my options are limited!), but if you just want "things to work" please try installing a 32-bit kernel. Currently, it is working better, and is better maintained. I hope this will change and improve in the future. The performance (64- vs. 32-bit) doesn't seem that different.
It's all a bit like IPV6: Great ideas, great potential, but it will not work until we all bite the bullet and move forwards.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.