Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sun 23 Nov 2014, 20:34
All times are UTC - 4
 Forum index » Advanced Topics » Cutting edge
Printing with CUPS: Almost here ! (Finally HERE!)
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 4 of 16 [229 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, ..., 14, 15, 16 Next
Author Message
rarsa


Joined: 29 May 2005
Posts: 3053
Location: Kitchener, Ontario, Canada

PostPosted: Wed 07 Sep 2005, 12:06    Post subject:  

That's the result I was expecting. As you can see on this line

"lrwxrwxrwx 1 root root 21 Sep 6 09:02 foomatic-rip -> /usr/bin /foomatic-rip"

Foomatic-rip is installed. The Log shown that it had failed running it. foomatic-rip is a Perl script, so installing Perl should solve this issue. hopefully there will be no more issues.
Back to top
View user's profile Send private message Visit poster's website 
rarsa


Joined: 29 May 2005
Posts: 3053
Location: Kitchener, Ontario, Canada

PostPosted: Wed 07 Sep 2005, 12:16    Post subject:  

That's the result I was expecting. As you can see on this line

"lrwxrwxrwx 1 root root 21 Sep 6 09:02 foomatic-rip -> /usr/bin /foomatic-rip"

Foomatic-rip is installed. The Log you sent me before shows that it had failed running foomatic-rip. foomatic-rip is a Perl script, so installing Perl should solve this issue. hopefully there will be no more issues.
Back to top
View user's profile Send private message Visit poster's website 
dewdrop


Joined: 29 Aug 2005
Posts: 298
Location: Texas USA

PostPosted: Wed 07 Sep 2005, 12:27    Post subject: CUPS  

Hi Rarsa,

Hummmmm....

Here is a step by step on what I just did.

Dewdrop

Step by Step for Perl install.

1.Did the PupGet request, and installed Perl-5.8.0 – Perl Language & Libraries.
2.I re-booted Puppy.
3.I then returned to the CUPS folder, requested xterm, and requested the perl -h command.
4.The results of the BEFORE printing request are below.


BusyBox v0.60.5 (2004.09.18-02:04+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

# perl -h

Usage: perl [switches] [--] [programfile] [arguments]
-0[octal] specify record separator (\0, if no argument)
-a autosplit mode with -n or -p (splits $_ into @F)
-C enable native wide character system interfaces
-c check syntax only (runs BEGIN and CHECK blocks)
-d[:debugger] run program under debugger
-D[number/list] set debugging flags (argument is a bit mask or alphabets)
-e 'command' one line of program (several -e's allowed, omit programfile)
-F/pattern/ split() pattern for -a switch (//'s are optional)
-i[extension] edit <> files in place (makes backup if extension supplied)
-Idirectory specify @INC/#include directory (several -I's allowed)
-l[octal] enable line ending processing, specifies line terminator
-[mM][-]module execute `use/no module...' before executing program
-n assume 'while (<>) { ... }' loop around program
-p assume loop like -n but print line also, like sed
-P run program through C preprocessor before compilation
-s enable rudimentary parsing for switches after programfile
-S look for programfile using PATH environment variable
-T enable tainting checks
-t enable tainting warnings
-u dump core after parsing program
-U allow unsafe operations
-v print version, subversion (includes VERY IMPORTANT perl info)
-V[:variable] print configuration summary (or a single Config.pm variable)
-w enable many useful warnings (RECOMMENDED)
-W enable all warnings
-X disable all warnings
-x[directory] strip off text before #!perl line and perhaps cd to directory

#


5.I restarted CUPS using the restart command
/etc/rc.d/rc.cups restart
6.I used the delete command to delete any printers...just to be sure.
7.I went thru the install printer routine again.
8.I clicked on the print test page button...... nothing happened.
9.The “Show Completed Jobs button indicated that the job had been aborted.


Shall I do a pristine install of Puppy again, only this time make sure that Perl is loaded?


Dewdrop
Back to top
View user's profile Send private message 
rarsa


Joined: 29 May 2005
Posts: 3053
Location: Kitchener, Ontario, Canada

PostPosted: Wed 07 Sep 2005, 13:49    Post subject:  

No, just change the logLevel to debug (in /etc/rc.d/rc.cups), try to print the test page and send me the log.
Back to top
View user's profile Send private message Visit poster's website 
dewdrop


Joined: 29 Aug 2005
Posts: 298
Location: Texas USA

PostPosted: Wed 07 Sep 2005, 16:20    Post subject: CUPS  

Hi Rarsa,

I'm thinking that the following Step by step will be useful for now and in the future. Please read it over and see if I have left anything important out.

The words in all caps would be the command line instructions and I'm not sure if they need to be in small letters or if it makes any difference one way or the other.

Dewdrop

Begin with a pristine install - I use Chubby Puppy on a Pocket CD-R (Mini CD - 210 Megabytes)
This means I do not have a pup001 file on my C Drive of WindowsXP - FAT32, but that one is created when I run the CD Install of Chubby Puppy.

After Puppy is running, use the PupGet and install the Perl program. Once perl is installed execute
the following from a Command Line:

PERL -H

This is to confirm that perl has indeed been installed. If it is installed, you should see many
lines of information.

I now believe that I have completed all necessary steps to begin trying to get CUPS up and running on my machine using Chubby Puppy.

The CUPS install begins:

1. Download the CUPS-INSTALL.TAR.GZ FILE.

2. Untar with TAR -XVZF CUPSINSTALL.TAR.GZ.

3. Open console and execute SH CUPS-INSTALL.SH

4. Execute SH ESPGS-INSTALL.SH

5. Execute SH HPIJS-INSTALL.SH

6. Restart CUPS with /ETC/RC.D/RC.CUPS RESTART

7. Open the browser and go to: http://localhost:631

8. Install the printer you have connected to your machine.
Follow the instructions on the localhost page to do the install.

9. Print a test page. ----- IF IT DID NOT PRINT --- DO THE FOLLOWING.

10. Tar the error_log file with the following command - from a command line:
TAR -CVZF LOG.TAR.GZ /VAR/LOG/CUPS/*

11. Delete the log file with the following command - from a command line:
RM -F /VAR/LOG/CUPS/ERROR_LOG

12. To open the CONFIGURATION file - from a command line:

LEAFPAD /ETC/CUPS/CUPSD.CONF

change the lines in the file as follows: locate the words "LogLevel info" and change that
to "LogLevel debug". Save and close the file.

13. Delete the log file with the following command - from a command line:
RM -F /VAR/LOG/CUPS/ERROR_LOG

14. Repeat steps 6 and 7 above.

15. Once at the localhost page, delete the printer that you previously installed by clicking on the
delete printer button and completing the steps.

16. Install a new printer and print a test page. If not successful, repeat the process from Step 10
thru Step 13.
Back to top
View user's profile Send private message 
rarsa


Joined: 29 May 2005
Posts: 3053
Location: Kitchener, Ontario, Canada

PostPosted: Wed 07 Sep 2005, 16:52    Post subject:  

Here are some comments about your step by step instructions:

The linux command line is case sensitive so PERL and perl are not the same thing. The same with file names, folder names, parameters, etc.

This is:
- PERL -H ---> won't work
- Perl -h ---> won't work
- perl -H ---> won't work
- perl -h ---> will work.

When reading instructions or giving instructions, always make sure that you follow the correct case.

Deleting the log is so only the the steps after you delete it are included in the log you send me. You shouldn't routinelly delete them. Deleting the log does not improve or impair the printing.

The tar-ing of the file is just so you can post it to the forum when I need to see it. It has nothing to do with CUPS or with printing. If you are not planning to send the log to someone, there is no poing on tar-ing it.

When I request to change the LogLevel to debug is so I can get more detailed information about the problem. Changing the LogLevel does not improve or impair the printing in any way. You should normally set it to LogLevel info (or none) to prevent the log from growing too fast.

Step 15 is superfluous unless you select the wrong printer. At the point we are at, deleting and adding the same printing does nothing to improve the situation. We already know that you have CUPS and the drivers installed correctly. We are just trying to figure out if you are missing something else (like perl) or if you need different configuration parameters.

A very important step to understand is step 6. It is required after changes to the configuration file or after installing a new driver so CUPS is aware of the new configuration or drivers.

So these instructions don't really belong to the CUPS instructions, but they may be a nice reference for you as it's faster for me to say : "tar the file and send it to me" than always giving the command, specially now that you understand what each command does.
Back to top
View user's profile Send private message Visit poster's website 
dewdrop


Joined: 29 Aug 2005
Posts: 298
Location: Texas USA

PostPosted: Wed 07 Sep 2005, 18:09    Post subject: CUPS  

Hi Rarsa,

At the risk of being "hung by the neck until dead!" I'll tell you that the attached log file is from a new pristine install. I believe it is easier and faster for me to go thru the entire procedure with each attempt...it re-inforces the learning I'm experiencing, and I don't mind the repetitions.

I appreciate your comments on the step by step too. what we have embarked upon is a learning experience for me that you cannot imagine, so correct repetition of any of these tasks is important. Repeating them correctly is especially important for me right now....although it may very well be driving you bonkers.

Attached is the latest error log file.

Dewdrop
log.tar.gz
Description 
gz

 Download 
Filename  log.tar.gz 
Filesize  3.87 KB 
Downloaded  247 Time(s) 
Back to top
View user's profile Send private message 
rarsa


Joined: 29 May 2005
Posts: 3053
Location: Kitchener, Ontario, Canada

PostPosted: Wed 07 Sep 2005, 19:05    Post subject:  

Please change the LogLevel to info, try to print the test page and send me the log.
Back to top
View user's profile Send private message Visit poster's website 
dewdrop


Joined: 29 Aug 2005
Posts: 298
Location: Texas USA

PostPosted: Wed 07 Sep 2005, 23:06    Post subject: CUPS  

"Please change the LogLevel to info, try to print the test page and send me the log."

Rarsa,

I think I did what you requested.....see info from xterm...as follows:


BusyBox v0.60.5 (2004.09.18-02:04+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

# leafpad /etc/cups/cupsd.conf
# /etc/rc.d/rc.cups restart
cups: restarted scheduler.
# tar -cvzf log.tar.gz /var/log/cups/*
tar: Removing leading `/' from member names
var/log/cups/access_log
var/log/cups/error_log
#
#

And here is the log as an attachment.

Dewdrop
log.tar.gz
Description 
gz

 Download 
Filename  log.tar.gz 
Filesize  1.77 KB 
Downloaded  246 Time(s) 
Back to top
View user's profile Send private message 
rarsa


Joined: 29 May 2005
Posts: 3053
Location: Kitchener, Ontario, Canada

PostPosted: Wed 07 Sep 2005, 23:37    Post subject:  

Try getting the status and printing from the command line with the following commands
Code:
lpstat -h localhost -t
echo "test" | lp
echo "Test1" > /dev/usb/lp0

And send me the result. (both the xterm and the log)

Last edited by rarsa on Thu 08 Sep 2005, 00:10; edited 1 time in total
Back to top
View user's profile Send private message Visit poster's website 
rarsa


Joined: 29 May 2005
Posts: 3053
Location: Kitchener, Ontario, Canada

PostPosted: Wed 07 Sep 2005, 23:55    Post subject:  

By the way... What printer are you using?

Are you using the HP3320? If you have more than one printer, please send me the models, we may try with another one.
Back to top
View user's profile Send private message Visit poster's website 
dewdrop


Joined: 29 Aug 2005
Posts: 298
Location: Texas USA

PostPosted: Thu 08 Sep 2005, 10:19    Post subject: CUPS  

Hi Rarsa,

Let me start with a couple of questions.

1.I have the CUPS folder in the following path.

/root/my-applications/CUPS/

Does where I have the folder make any difference?

2.The log file ends up in the CUPS folder after I create it. Should it end up there? And, is it okay to delete it from that folder after I've sent it to you?


3.I am using the HP6540...and have been for the last 4 or 5 days. The other printer I have is the HP3320.
4.Here is the Xterm info........

BusyBox v0.60.5 (2004.09.18-02:04+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

# lpstat -h localhost -t
scheduler is running
system default destination: HP
device for HP: usb://6540?serial=MY49K3Q1MP040J
HP accepting requests since Jan 01 00:00
printer HP is idle. enabled since Jan 01 00:00
# echo "test" | lp
request id is HP-1 (1 file(s))
# echo "Test1" > /dev/usb/lp0
#
# tar -cvzf log.tar.gz /var/log/cups/*
tar: Removing leading `/' from member names
var/log/cups/access_log
var/log/cups/error_log
#

5.Something interesting just happened....
A. It sounded like the printer's carriage return activated, then nothing happened, but the on/off button began blinking.
B. Then after about a minute it sounded like the printer cycled thru a series of steps, but nothing happened. The on/off button continued to blink.
C. I then did the log proceedure...noted above in the Xterm info, and the printer then ejected a piece of paper with the word “Test1”.....without the quote marks, printed on it, and the blinking on/off light stopped blinking.

I say that's progress!!!

Dewdrop

Log file is attached.
log.tar.gz
Description 
gz

 Download 
Filename  log.tar.gz 
Filesize  676 Bytes 
Downloaded  249 Time(s) 
Back to top
View user's profile Send private message 
rarsa


Joined: 29 May 2005
Posts: 3053
Location: Kitchener, Ontario, Canada

PostPosted: Thu 08 Sep 2005, 13:21    Post subject:  

Quote:
1.I have the CUPS folder in the following path.

If you mean that you have the installation scripts in that folder, then it does not make any difference. CUPS does not look at those files, those are only used during the installation.
If you you mean something else, please let me know.

Quote:
2.The log file ends up in the CUPS folder after I create it.
As you are not specifying a full path for the log.tar.gz file when you careate it, it will be created in the 'current folder'. That is the expectd behaviour and it really does not matter where it is as long as you know the location so you can send it.

Quote:
3.I am using the HP6540
Please try the full procedure with the HP3320. It's not uncommon that one printer will print OK while the other one just refuses. When you name your printers in CUPS, please name it as HP6540 or HP3320 so I know which one you used when looking at the log, right now you are naming it just HP.

Are you connecting the HP3320 trhough USB or paralell?

Quote:
5.Something interesting just happened...
Running the risk of sounding silly I have to ask: Is the printer "ON" when you are testing? I'm asking this because in windows you don't have to 'turn on' the printer, when you print it turns on automatically. This may not be the same in Linux. Make sure that the printer is ON.

I'm running out of options. I want you to try the HP3320 as I think that there is another way (the puppy way) to have the 6450 printing without CUPS.
Back to top
View user's profile Send private message Visit poster's website 
dewdrop


Joined: 29 Aug 2005
Posts: 298
Location: Texas USA

PostPosted: Thu 08 Sep 2005, 23:20    Post subject: CUPS  

Hi Rarsa,

I shall answer your questions first.

1. The CUPS folder question/answer. I was thinking that perhaps the location of the folder might have an effect on it's actions. In effect, the installation files once used could be deleted.

2. I use the xterm from the CUPS window, and that is why the log file ends up there. At first I didn't know where it would be, but once I learned that if I kept the Xterm window open during the procedure, the log file would end up in the CUPS folder (current folder) as you call it.

3. I am in the process of doing the full procedure on the HP3320, and the initial attempt failed. I am attaching the log file of that attempt to this posting. I have used the name HP3320 during the printer setup process on localhost:631, so that is the name I would expect you will see inside the log.

3a. The HP3320 is connected thru the USB port, as is the HP6540.

4. "Is the printer on?" - my response has to be "I think so". The ON/OFF button is illuminated, so I take that as meaning it is on.

I shall now go thru the process of deleting the log file, opening the configuration file and doing the leafpad procedure, restarting cups with that procedure and doing the lpstat -h localhost -t procedure....and the echo lines. Then I'll send you the results of that test in the next post.

Dewdrop
log.tar.gz
Description 
gz

 Download 
Filename  log.tar.gz 
Filesize  1.37 KB 
Downloaded  231 Time(s) 
Back to top
View user's profile Send private message 
dewdrop


Joined: 29 Aug 2005
Posts: 298
Location: Texas USA

PostPosted: Thu 08 Sep 2005, 23:40    Post subject: CUPS  

Hi Rarsa,

Here is my information from the second procedure. The log file is attached.

This time there was no activity from the printer during the second "Test1" procedure.

When I got to the leafpad information the LogLevel info was still there – it had not changed back to debug during the re-start with a pristine install, or the change in printers from the HP6540 to the HP3320.

Therefore I didn't change it. Simply closed the window and executed the restart command.

Then I did the lpstat command....and following.

The Xterm info follows:

`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.
# tar -cvzf log.tar.gz /var/log/cups/*
tar: Removing leading `/' from member names
var/log/cups/access_log
var/log/cups/error_log
# rm -f /var/log/cups/error_log
# leafpad /etc/cups/cupsd.conf
# rm -f /var/log/cups/error_log
# /etc/rc.d/rc.cups restart
cups: restarted scheduler.
# lpstat -h localhost -t
scheduler is running
system default destination: HP3320
device for HP3320: usb://hp/deskjet%203320?serial=TH2CN340F943
HP3320 accepting requests since Jan 01 00:00
printer HP3320 is idle. enabled since Jan 01 00:00
# echo "test" | lp
request id is HP3320-2 (1 file(s))
# echo "Test1" > /dev/usb/lp0
# tar -cvzf log.tar.gz /var/log/cups/*
tar: Removing leading `/' from member names
var/log/cups/access_log
var/log/cups/error_log
log.tar.gz
Description 
gz

 Download 
Filename  log.tar.gz 
Filesize  1.18 KB 
Downloaded  240 Time(s) 
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 4 of 16 [229 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, ..., 14, 15, 16 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Cutting edge
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1071s ][ Queries: 12 (0.0058s) ][ GZIP on ]