Printing with CUPS: Almost here ! (Finally HERE!)
Great work, but from previous experience I find that most people are lazy when it comes to doing things for themselves. Look we couldn't even get people to read the instructions for thw wifi dotpup even tho it pops up during the installation. So the only draw back I can see is people not willing to put the effort into finding the correct drivers for their printer, I know it sux bigtime but that's the way it is.
Just a note, if one is going to use Puppy as a print server only, ie other printers using the printer resources of puppy, the 'raw' driver will work as the other machines do all the printer specific formatting.
Just a note, if one is going to use Puppy as a print server only, ie other printers using the printer resources of puppy, the 'raw' driver will work as the other machines do all the printer specific formatting.
CUPS
Hi Rarsa,
I read the new instructions and everything fell into place ....except as shown on the last printscreen below.
(I'm not sure that they have been added in the correct order, but they are numbered correctly....if the number of each screenshot is attached - I don't see that #1 is attached I'll make another post and add it there.)
Printscreen1 = was the result of completing step #8 of the new instructions.
Printscreens 2 & 3 = These got me thru step #9 to the point that I requested that the test page be printed.
Printscreen 4 = This is where I'm at after trying various combinations of the steps in the instructions.
I have not tried the HP3320 printer yet.
This was a lot of work on your part...thank you, thank you, thank you!!!
I shall keep trying various combinations until it hits for each printer. If you can see something that I'm not doing correctly, let me know.
Dewdrop
I read the new instructions and everything fell into place ....except as shown on the last printscreen below.
(I'm not sure that they have been added in the correct order, but they are numbered correctly....if the number of each screenshot is attached - I don't see that #1 is attached I'll make another post and add it there.)
Printscreen1 = was the result of completing step #8 of the new instructions.
Printscreens 2 & 3 = These got me thru step #9 to the point that I requested that the test page be printed.
Printscreen 4 = This is where I'm at after trying various combinations of the steps in the instructions.
I have not tried the HP3320 printer yet.
This was a lot of work on your part...thank you, thank you, thank you!!!
I shall keep trying various combinations until it hits for each printer. If you can see something that I'm not doing correctly, let me know.
Dewdrop
Last edited by dewdrop on Sun 04 Sep 2005, 20:45, edited 1 time in total.
Dewdrop:
Good catch. I missed a parameter for the script. I've updated the instructions.
To restart CUPS you type "/etc/rc.d/rc.cups restart".
You need to restart CUPS in order to see the newly installed drivers.
So, for you the next steps are the following:
- Restart CUPS with the restart command.
- Delete the printer that you created. (you used the wrong driver as the right one didn't show in the list of drivers)
- Add a new printer. Please note that the printer must be connected to the computer.
- Select the appropriate driver. You will see one on the list that exactly matches your printer.
- Print a test page.
Your patient testing is helping a lot. Thank you for putting the time.
Good catch. I missed a parameter for the script. I've updated the instructions.
To restart CUPS you type "/etc/rc.d/rc.cups restart".
You need to restart CUPS in order to see the newly installed drivers.
So, for you the next steps are the following:
- Restart CUPS with the restart command.
- Delete the printer that you created. (you used the wrong driver as the right one didn't show in the list of drivers)
- Add a new printer. Please note that the printer must be connected to the computer.
- Select the appropriate driver. You will see one on the list that exactly matches your printer.
- Print a test page.
Your patient testing is helping a lot. Thank you for putting the time.
CUPS
Hi Rarsa,To restart CUPS you type "/etc/rc.d/rc.cups restart".
You need to restart CUPS in order to see the newly installed drivers.
So, for you the next steps are the following:
- Restart CUPS with the restart command.
- Delete the printer that you created. (you used the wrong driver as the right one didn't show in the list of drivers)
- Add a new printer. Please note that the printer must be connected to the computer.
- Select the appropriate driver. You will see one on the list that exactly matches your printer.
- Print a test page.
I did the adjustments as you instructed...still no go...this was a short test as I'm on my way to church in a bit. The listing of all of the printers did come up before..during one of the tests last night and I was able to select the correct printer from the list. However, note that the info I pass below as printscreens are what my results were after typing in the instructions as you sent them last evening.
I will get there...your instructions have been great so far.
Dewdrop
Last edited by dewdrop on Sun 04 Sep 2005, 20:46, edited 1 time in total.
Dewdrop:
Please do the following:
1. Delete the log file with the following command
2. Try to print the test page.
3. Tar the error_log file with the following command:
4. Send the log.tar.gz file as an attachment.
You don't need to send more screen prints.
Please do the following:
1. Delete the log file with the following command
Code: Select all
rm -f /var/log/cups/error_log.
3. Tar the error_log file with the following command:
Code: Select all
tar -czf /root/log.tar.gz /var/log/cups/error_log
You don't need to send more screen prints.
CUPS
Hi Guest,Dewdrop:
Please do the following:
1. Delete the log file with the following command
Code:
rm -f /var/log/cups/error_log.
2. Try to print the test page.
3. Tar the error_log file with the following command:
Code:
tar -czf /root/log.tar.gz /var/log/cups/error_log
4. Send the log.tar.gz file as an attachment.
You don't need to send more screen prints.
I believe that I've done as you have requested, and still no action from the printer. rather than attach the log file....which as you will see..the instructions didn't make...I've attached one more printscreen. I believe this will show either where I have erred in carrying out your request, or why it wouldn't prepare the requested error log.
Since the requested action is "way over my head" in terms of using the command line, I may very well have "goofed" in typing in the request. If I have please show me the error(s) of my ways, and I'll try get the error log so that you may be able to see what's happening.
Thanks for your interest and help.
Dewdrop
Last edited by dewdrop on Sun 04 Sep 2005, 20:47, edited 1 time in total.
Really, I don't need screen prints, actually they waste a lot of space on the server and make it very slow for other users on modem to read the thread.
You know: You can copy the text from the console if you highlight the console text with the mouse and press ctrl-C (Keep the Ctrl key in the keyboard pressed and press the "C" key), you can then paste it in the browser pressing Ctrl-V.
For the little I can see in your screen print and by the message you got, it seems that you forgot to press the <space > key between parameters.
Here is the command again with loooots of spaces so you can see where to inster the spaces:
Please don't post more screen prints unless I ask for one, OK? You can also edit the previous posts and remove the images. (That's only to be nice to the rest of the readers).
You know: You can copy the text from the console if you highlight the console text with the mouse and press ctrl-C (Keep the Ctrl key in the keyboard pressed and press the "C" key), you can then paste it in the browser pressing Ctrl-V.
For the little I can see in your screen print and by the message you got, it seems that you forgot to press the <space > key between parameters.
Here is the command again with loooots of spaces so you can see where to inster the spaces:
Code: Select all
tar -czf /root/log.tar.gz /var/log/cups/error_log
CUPS
Hi Rarsa,
I have deleted the printscreen as you requested. Being on a cable modem, I forget that other people don't have the luxury of the speed I have.
Now, that said, I went back to the beginning and downloaded your tarred file - cups-install.tar.gz. This time I noticed that there seemed to be an additional file - cupsconf.tar.gz...... along with the cups-install.sh, espgs-install.sh, and hpijs-install.sh files. Did you have the cupsconf.tar.gz inside of your original cups-install.tar.gz file? And should it have been untarred? --- I did untar it, and came up with 9 additional items.
I believe I have done as you instructed with the deletions and have a file called log.tar.gz which is attached. Hopefully, this is what you are looking for.
Finally, this is what the x-term window looked like after your deletion requests were executed:
`usr/share/ppd/HP/HP-OfficeJet_G55-hpijs.ppd.gz' -> `/usr/share/ppd/HP/HP-OfficeJet_G55-hpijs.ppd.gz'
`usr/share/ppd/HP/HP-DeskJet_632C-hpijs.ppd.gz' -> `/usr/share/ppd/HP/HP-DeskJet_632C-hpijs.ppd.gz'
# /etc/rc.d/rc.cups restart
cups: restarted scheduler.
# rm -f /var/log/cups/error_log.
# tar -czf /root/log.tar.gz /var/log/cups/error_log
tar: Removing leading `/' from member names
#
Are we getting any closer? I
Dewdrop
I have deleted the printscreen as you requested. Being on a cable modem, I forget that other people don't have the luxury of the speed I have.
Now, that said, I went back to the beginning and downloaded your tarred file - cups-install.tar.gz. This time I noticed that there seemed to be an additional file - cupsconf.tar.gz...... along with the cups-install.sh, espgs-install.sh, and hpijs-install.sh files. Did you have the cupsconf.tar.gz inside of your original cups-install.tar.gz file? And should it have been untarred? --- I did untar it, and came up with 9 additional items.
I believe I have done as you instructed with the deletions and have a file called log.tar.gz which is attached. Hopefully, this is what you are looking for.
Finally, this is what the x-term window looked like after your deletion requests were executed:
`usr/share/ppd/HP/HP-OfficeJet_G55-hpijs.ppd.gz' -> `/usr/share/ppd/HP/HP-OfficeJet_G55-hpijs.ppd.gz'
`usr/share/ppd/HP/HP-DeskJet_632C-hpijs.ppd.gz' -> `/usr/share/ppd/HP/HP-DeskJet_632C-hpijs.ppd.gz'
# /etc/rc.d/rc.cups restart
cups: restarted scheduler.
# rm -f /var/log/cups/error_log.
# tar -czf /root/log.tar.gz /var/log/cups/error_log
tar: Removing leading `/' from member names
#
Are we getting any closer? I
Dewdrop
- Attachments
-
- log.tar.gz
- (1.05 KiB) Downloaded 444 times
Dewdrop:
I don't know if its a read herring but there were some bad lines in the configuration file.
I didn't notice them because they didn't cause any problem for me.
And by the way, you didn't have to untar the cupsconfig.tar.gz. my installation script untars it to the appropriate location.
Please do the following:
1. Delete log files with
2. Download the installer again
3. Run the "sh cups-install.sh"
4. Try to print the test page
5. Tar the log files with
6. Send me the file
I don't know if its a read herring but there were some bad lines in the configuration file.
I didn't notice them because they didn't cause any problem for me.
And by the way, you didn't have to untar the cupsconfig.tar.gz. my installation script untars it to the appropriate location.
Please do the following:
1. Delete log files with
Code: Select all
rm /var/log/cups/*
3. Run the "sh cups-install.sh"
4. Try to print the test page
5. Tar the log files with
Code: Select all
tar -xvzf log.tar.gz /var/log/cups/*
6. Send me the file
CUPS
Rarsa,rm /var/log/cups/*
2. Download the installer again
3. Run the "sh cups-install.sh"
4. Try to print the test page
5. Tar the log files with
Code:
tar -xvzf log.tar.gz /var/log/cups/*
6. Send me the file
I tried the instructions noted above. No luck.
I only ran the sh cups-install.sh script...not the others that I've run in the past.
I tried to tar the log files as noted above, and as far as I know they were not generated since I couldn't find them on/in any of the directories. Thus, I'm not able to send them to you.
Here is the xterm window info that was produced - I'm in way over my head, but hopefully I'm being of some help as you try to figure this out for me. You will not that the first try I forgot the * at the end of the instructions...I don't even know if that might make a difference...a failed attempt, I mean.
Dewdrop
mime.convs
mime.types
ppds.dat
printers.conf
pstoraster.convs
modprobe printer
Note: /etc/modules.conf is more recent than /lib/modules/2.4.29/modules.dep
/etc/rc.d/rc.cups start
cups: started scheduler.
# tar -xvzf log.tar.gz /var/log/cups
tar (child): log.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: /var/log/cups: Not found in archive
tar: Error exit delayed from previous errors
#
# tar -xvzf log.tar.gz /var/log/cups/*
tar (child): log.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: /var/log/cups/access_log: Not found in archive
tar: /var/log/cups/error_log: Not found in archive
tar: Error exit delayed from previous errors
#
Oops, sorry its
the -x parameter is to extract the -c parameter is to create.
Code: Select all
tar -cvzf log.tar.gz /var/log/cups
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
Just to say am reading this - getting the Holy Grail of Cups working with much interest.
I hope to blow the dust off my old Canon BJC 210 and print something.
Sadly my first printer - a daisywheel with a print speed of 1 page in 5 minutes is no longer with me . . .
I also have a HP Deskjet 500 (monochrome only) that is sure to print.
Great team work - good luck
(Lobster cheering from the side lines and waving whiskers enthusiastically)
I hope to blow the dust off my old Canon BJC 210 and print something.
Sadly my first printer - a daisywheel with a print speed of 1 page in 5 minutes is no longer with me . . .
I also have a HP Deskjet 500 (monochrome only) that is sure to print.
Great team work - good luck
(Lobster cheering from the side lines and waving whiskers enthusiastically)
CUPS
Hi Lobster,
And welcome to the Puzzle Palace. It's fun being part of a team (although I'm a minor part, I believe). I remember as a kid doing picture puzzles with my Dad and friends. Then we were all in one room. Here we do the same activity....looking for the pieces that fit together... with a little more space involved.
Dewdrop
....and now to continue with the puzzle.....
And welcome to the Puzzle Palace. It's fun being part of a team (although I'm a minor part, I believe). I remember as a kid doing picture puzzles with my Dad and friends. Then we were all in one room. Here we do the same activity....looking for the pieces that fit together... with a little more space involved.
Dewdrop
....and now to continue with the puzzle.....
I'm answering this comment in a different thread: Why people don't read the instructionsbladehunter wrote:So the only draw back I can see is people not willing to put the effort into finding the correct drivers for their printer, I know it sux bigtime but that's the way it is.
As I said before, It's well known that we developers aren't good at testing our own creations. It does not matter how much time a developer puts into something if it does not work. So, I would say that your part is not minor. On the contrary, it's fundamental.dewdrop wrote: It's fun being part of a team (although I'm a minor part, I believe)
Funny thing. At work testers know how happy I am everytime they find a bug in my work. Better them than the client, eh?
CUPS
Hi Rarsa,
Thanks for the compliment.
I'm having a slight problem getting the localhost to connect this morning, so as I am waiting I decided I should check on the USB Connection area and see what I could see. This is what was listed for the printer as far as where the information is located (I guess).
/proc/bus/usb/devices
I have no idea if this is of any help or not.
Dewdrop
Thanks for the compliment.
I'm having a slight problem getting the localhost to connect this morning, so as I am waiting I decided I should check on the USB Connection area and see what I could see. This is what was listed for the printer as far as where the information is located (I guess).
/proc/bus/usb/devices
I have no idea if this is of any help or not.
Dewdrop
Last edited by dewdrop on Mon 05 Sep 2005, 22:02, edited 1 time in total.
CUPS
Hi Rarsa,
Trying to get a connection to localhost this morning is a real pain so I'm going to give it a rest for a couple hours or so.
I did notice a difference in your instructions for the tar
the first one was tar -xvzf log.tar.gz/var/log/cups/*
the second was tar -cvzf log.tar.gz/var/log/cups
I know about the x and c difference from your posts. My question has to do with the * - asterisk - is it there on not?
Dewdrop
Trying to get a connection to localhost this morning is a real pain so I'm going to give it a rest for a couple hours or so.
I did notice a difference in your instructions for the tar
the first one was tar -xvzf log.tar.gz/var/log/cups/*
the second was tar -cvzf log.tar.gz/var/log/cups
I know about the x and c difference from your posts. My question has to do with the * - asterisk - is it there on not?
Dewdrop
My mistake. It's with the *. As in DOS or windows or many other regular expresions, the * is a wild card meaning "everything"
This comamnd says
tar : execute the tar command
-c : Creating a new tar file
-v : verbose. Show me what you are doing.
-z : After taring the files, compress them with gzip
-f log.tar.gz : into a file called log.tar.gz
/var/log/cups/* : and include all the files under the /var/log/cups/ folder.
Code: Select all
tar -cvzf log.tar.gz /var/log/cups/*
tar : execute the tar command
-c : Creating a new tar file
-v : verbose. Show me what you are doing.
-z : After taring the files, compress them with gzip
-f log.tar.gz : into a file called log.tar.gz
/var/log/cups/* : and include all the files under the /var/log/cups/ folder.
CUPS
Rarsa,
Thanks for the explanation. I restarted the attempt to comply with your previous request and still got the unable to connect message. So, I thought to myself - why not see what comes up with a search of http:localhost:631.
Lo! and behold! I found this and it seems to be working.....so now it's back to the instructions with a fresh start.
Dewdrop
(what follows came off of some forum about localhost:631, but I'm just sending the part I found of help)
"I guess I would post this here instead of the slackware forum.
I have downloaded all drivers and filters I need for my printer but when I try to access the web interface I get this error.
quote:
The connection was refused when attempting to connect to http://localhost:631/
I'm assuming that because I'm behind a router that it denied the connection. Would need to forward the port for 631 to my linux box so I can access the web interface? If so I guess I will do that and then disable the option after I get that setup for security reasons. In all the guides and tutorials I've read none have nevered mentioned about having to do this.
localhost:631 is an internal web page on the machine you are at. The "connection refused" message usually means that cupsd is not running. To check this, open a terminal and su root. Then type "cupsd" to try to start the daemon. If it was not running before, you should just get a new bash prompt. If you get a "cupsd: Child exited with status 98!", then cups is running and there is something else wrong. If it does start ok, then you should be able to access localhost:631 using the root username and password."
In my case, I simply got the new bash prompt, so I assume for whatever reason my daemon was not running. - Newbie ? - what a daemon?
Dewdrop
Thanks for the explanation. I restarted the attempt to comply with your previous request and still got the unable to connect message. So, I thought to myself - why not see what comes up with a search of http:localhost:631.
Lo! and behold! I found this and it seems to be working.....so now it's back to the instructions with a fresh start.
Dewdrop
(what follows came off of some forum about localhost:631, but I'm just sending the part I found of help)
"I guess I would post this here instead of the slackware forum.
I have downloaded all drivers and filters I need for my printer but when I try to access the web interface I get this error.
quote:
The connection was refused when attempting to connect to http://localhost:631/
I'm assuming that because I'm behind a router that it denied the connection. Would need to forward the port for 631 to my linux box so I can access the web interface? If so I guess I will do that and then disable the option after I get that setup for security reasons. In all the guides and tutorials I've read none have nevered mentioned about having to do this.
localhost:631 is an internal web page on the machine you are at. The "connection refused" message usually means that cupsd is not running. To check this, open a terminal and su root. Then type "cupsd" to try to start the daemon. If it was not running before, you should just get a new bash prompt. If you get a "cupsd: Child exited with status 98!", then cups is running and there is something else wrong. If it does start ok, then you should be able to access localhost:631 using the root username and password."
In my case, I simply got the new bash prompt, so I assume for whatever reason my daemon was not running. - Newbie ? - what a daemon?
Dewdrop