On Friday 29 April 2005 11:01, Joel Webb wrote:
We are having major problems with our Athlon 64 system that is being used as a desktop.
We are running a Brother printer that is not listed in the drivers list, but has been printed to using the gimp-print driver. (known to work the largest number of printers)
Now Brother doesn't "support" linux, but they do provide linux drivers for some of their other printers. Also the printer is similar to our HP laserjet, and it runs flawlessly.
It seems most of the issues are coming from printing from OpenOffice, which seems weird. But it gets even weirder. Now looking at the print queue it looks like this:
krusty:~ # lpq mfc7820n is ready and printing Rank Owner Job File(s) Total Size active brian 4 (stdin) 6144 bytes 1st brian 5 Untitled1 26624 bytes 2nd brian 6 Job Report - KJobViewer 56320 bytes 3rd brian 7 file:/// 232448 bytes 4th brian 8 file:/// 232448 bytes 5th brian 9 file:/// 232448 bytes
But nope, it isn't printing. Any suggestions?? We have removed the printer, and re-added it. Hooked it up directly through USB, and also had it networked as well. While the printer was networked, we could only get one page to be sent to the printer and then the CUPS server said the printer "wasn't ready" any more.
Any suggestions??
--
Hi Joel, You do not say what model your printer is. Brother has quite a few, and they are very different. At least the post script models should work fine under Linux (mine did). Also gimp-print includes drivers for many many printers. And you do not mention which SuSE version you're using. Therefore only general suggestions are possible, sorry. Did you have a look at the output of "dmesg" or checked if there are any error messages in /var/log/messages ? - For dmesg, open a konsole and type "dmesg" and enter, right after you connected your printer, and after you did send a print job, like the ones waiting in your queue. - For /var/log/messages, open a konsole, type "su" and enter to change to root, and then issue a "tail /var/log/messages" + enter. If that does not show enough, change it to "tail -n 50 /var/log/messages" or "tail -n 80 /var/log/messages" etc. Check that at the same time as dmesg, right after you connected your printer, and after you did send a print job, like the ones waiting in your queue. in such cases error messages can usually be found there . Post them here, if needed. HTH, Matt PS. Please do not crosspost to several lists.