SlackwareThis Forum is for the discussion of Slackware Linux.
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm currently setting up a complete Slackware network (server and desktop clients) in a local radio station. So far, the server is working great, and I have two desktop clients for a start. Eventually all ten machines will be migrated to Slackware. Currently the other client machines are running a mix of Windows XP and Ubuntu.
The Slackware clients are running crisp and clean with KDE as desktop and centralized authentication. Everything's perfect, and the only remaining problem is the darn printer.
It's not natively supported by CUPS, but Canon does provide drivers on its website for... Fedora and Ubuntu. So I downloaded the driver package, extracted the compressed archive, found various DEB and RPM packages for 32-bit and 64-bit, and decided to install the 64-bit RPMs with rpm -ivh --nodeps. (The PC does have a multilib layer installed). I did an rpm -ql to see what was installed, and all the files seemed to be in the right place. Except the printer won't even raise an eyebrow.
So my question to the CUPS gurus in this forum. Through which burning loop do I have to jump in order to get this thing to work? I'm clueless here.
Thanks everybody for all your numerous answers. I had to finish the install yesterday evening by any means, so in the end, I found a pragmatic solution. One of the desktop clients is supposed to remain with an Ubuntu LTS installation, so I simply connected the printer to this one client, installed the ready-made .deb drivers from Canon (which worked out of the box, well, sort of), activated printer sharing in Ubuntu's CUPS installation so all the Slackware clients can print to it. Not quite elegant, but it works. The folks at the radio station were happy, and I could go home at a decent hour.
Note to self: continue to boycott Canon for their crappy Linux support.
I had a lot of problems with Cannon multifunctional and Slackware 14. Drivers compiled from source without problems, but printer refuses to work. problem was with CUPS 1.5.4 usb backend and kernel module usblp. Blacklisting that module solved all problems. In Slackware current the usblp is blacklisted now.
i would have pluged the printer in the network (at least it is a network printer) and compile the driver from the sourcefiles in the zip.. that way no computer would have to be running to print.. oh well.. as long as the people at the radio are happy all is fine.
The advantage of this method is that it will continue to work even if the internal compression method changes (e.g. to XZ) because bsdtar allows globbing when extracting files (i.e. data.tar.*), while ar does not. Additionally, bsdtar can detect and handle automatic decompression of archives received through a pipe without having to specify the compression type, unlike GNU tar.
Last edited by ruario; 10-28-2013 at 02:16 AM.
Reason: Quoted too much initially