Printing with CUPS: Almost here ! (Finally HERE!)

Under development: PCMCIA, wireless, etc.
Message
Author
User avatar
rarsa
Posts: 3053
Joined: Sun 29 May 2005, 20:30
Location: Kitchener, Ontario, Canada
Contact:

#31 Post by rarsa »

dewdrop wrote: It's fun being part of a team (although I'm a minor part, I believe)
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.

Funny thing. At work testers know how happy I am everytime they find a bug in my work. Better them than the client, eh?

User avatar
dewdrop
Posts: 298
Joined: Tue 30 Aug 2005, 01:54
Location: Texas USA

CUPS

#32 Post by dewdrop »

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
Last edited by dewdrop on Mon 05 Sep 2005, 22:02, edited 1 time in total.

User avatar
dewdrop
Posts: 298
Joined: Tue 30 Aug 2005, 01:54
Location: Texas USA

CUPS

#33 Post by dewdrop »

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

User avatar
rarsa
Posts: 3053
Joined: Sun 29 May 2005, 20:30
Location: Kitchener, Ontario, Canada
Contact:

#34 Post by rarsa »

My mistake. It's with the *. As in DOS or windows or many other regular expresions, the * is a wild card meaning "everything"

Code: Select all

tar -cvzf   log.tar.gz   /var/log/cups/*
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.

User avatar
dewdrop
Posts: 298
Joined: Tue 30 Aug 2005, 01:54
Location: Texas USA

CUPS

#35 Post by dewdrop »

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

User avatar
dewdrop
Posts: 298
Joined: Tue 30 Aug 2005, 01:54
Location: Texas USA

CUPS

#36 Post by dewdrop »

Hi Rarsa,

Still a no go on the HP 6540 - the one I'll stick with, then once we get this one working, I expect the other one HP 3320 will work too.

As you will see from the information below, I had to do the "cupsd" to restart the daemon since I couldn't open the 631 site again.

I have no idea if this is what is keeping the operation from being a success or not....I kind of wish that some of the other people watching and trying to get their printers connected as they follow our adventures would chime in with success stories... :D

Anyway, I've attached the log file.

Thanks.

Dewdrop

I just realized that I didn't include the info from the xterm screen. Here it is:

`usr/share/cups/fonts/Courier-BoldOblique' -> `/usr/share/cups/fonts/Courier-BoldOblique'
`usr/share/cups/fonts/Courier-Bold' -> `/usr/share/cups/fonts/Courier-Bold'
`usr/share/cups/data/psglyphs' -> `/usr/share/cups/data/psglyphs'
`usr/share/cups/data/HPGLprolog' -> `/usr/share/cups/data/HPGLprolog'
`usr/share/cups/data/testprint.ps' -> `/usr/share/cups/data/testprint.ps'
classes.conf
client.conf
cupsd.conf
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.
# cupsd
# tar -cvzf log.tar.gz /var/log/cups/*
tar: Removing leading `/' from member names
var/log/cups/access_log
var/log/cups/error_log
Attachments
log.tar.gz
(1.86 KiB) Downloaded 455 times

User avatar
rarsa
Posts: 3053
Joined: Sun 29 May 2005, 20:30
Location: Kitchener, Ontario, Canada
Contact:

#37 Post by rarsa »

Let's do what the error_log says.

Open the configuration file with leafpad

Code: Select all

leafpad   /etc/cups/cupsd.conf
and change the line that says "LogLevel info" to "LogLevel debug". Close and save the file

Then do the following (same as previous instructions):
- Delete the log files,
- Try to print the test page,
- Tar the log files
- Send me the log files again.

Make sure that you pack the files just after trying to print the test page. I want to see the error that you get right after you try it.

By the way.

Are you available to do an online test tonight? we could join in the irc channel and try to speed things up. I'll be online about 9:00 PM EST (that is GMT -5)

User avatar
dewdrop
Posts: 298
Joined: Tue 30 Aug 2005, 01:54
Location: Texas USA

CUPS

#38 Post by dewdrop »

Hi Rarsa,

This really threw me for a loop. I have no idea how to carry out the instructions using leafpad.

Also, I'd be willing to tothe IRC Channel thing, but I've never done that before either.....

With my limited knowledge, would the IRC chat be productive for you?

I expect that the 9pm EST (GMT -5) do you mean EDT (Eastern Daylight Time?) .... that's 8pm CDT (Central Daylight Time) for me....in other words in approximately 18 minutes....I have 7:42pm here.

I'll see if I can get the IRC Channel in these remaining minutes before 8pm.

Dewdrop

User avatar
dewdrop
Posts: 298
Joined: Tue 30 Aug 2005, 01:54
Location: Texas USA

CUPS

#39 Post by dewdrop »

Hi Rarsa,

I believe that I'm hooked into the IRC Chat channel for puppy.

I have the IRC Chat set up on GAIM. Is that correct? It is now 8:26pm my time.....9:26pm EDT.

Dewdrop

User avatar
dewdrop
Posts: 298
Joined: Tue 30 Aug 2005, 01:54
Location: Texas USA

CUPS

#40 Post by dewdrop »

Rarsa,

Here's the log file.

Dewdrop
Attachments
log.tar.gz
(3.75 KiB) Downloaded 453 times

User avatar
dewdrop
Posts: 298
Joined: Tue 30 Aug 2005, 01:54
Location: Texas USA

CUPS

#41 Post by dewdrop »

Good morning Rarsa,

I have done another attempt with a new pristine install of Chubby Puppy, to no avail.

Here is my step by step from this morning, and an attached error log file after changing the LogLevel info to LogLevel debug with leafpad.

Let me know if I've skipped anything, or you want me to retry something.

Thanks for the direction last night on the IRC. What a learning experience.

Dewdrop

WHAT I DID

1.Downloaded the cups-install.tar.gz file, and put it into its own folder
Attachments
log.tar.gz
(2.03 KiB) Downloaded 457 times

User avatar
rarsa
Posts: 3053
Joined: Sun 29 May 2005, 20:30
Location: Kitchener, Ontario, Canada
Contact:

#42 Post by rarsa »

nice step by step.

You missed restarting cups after modifying the LogLevel

sh /etc/rc.d/rc.cups stop
sh /etc/rc.d/rc.cups start

Any way, It seems that the you got the same error regarding foomatic.

Actually this part is beyond my instructions as it seems that CUPS is correctly installed and working in your system.

If you remember my step 7 is "7. Install the CUPS drivers for the printers connected to your puppy computer according to your driver's instructions."

That is the tricky part with CUPS. In Mepis you may already had that driver installed and configured that's why you were able to use it. In Puppy's case, it does not have nearly as many drivers as other distributions in an effort to keep it small.

Then, what's next you may ask? Well, I'll thank you for your help testing the instructions and I'll move on... hehe, not really, I'll make my best to have your printers working.

This is what I found regarding foomatic:
http://www.linuxprinting.org/kpfeifle/L ... -user.html

But don't jump at it just yet. I have already done half of the steps shown on that page. I've already included the driver you need (hpijs).

We will have to go through the instructions starting on the section titled "Getting the configuration file for your spooler".

Please read them but don't follow them yet.

I will try to package the alternative method for using the foomatic tools.

I'll let you know when it's ready. (Maybe later today. I'm working right now).

User avatar
dewdrop
Posts: 298
Joined: Tue 30 Aug 2005, 01:54
Location: Texas USA

CUPS

#43 Post by dewdrop »

Hi Rarsa,

Darn!!! javascript:emoticon(':shock:')

I was sure I had everything covered.....:) So much for "sure-ness"

Now. I will get the information that you describe about foomatic and get it printed out so I have a paper copy. I'll read it over, but not jump at anything yet, paying special attention to the

User avatar
rarsa
Posts: 3053
Joined: Sun 29 May 2005, 20:30
Location: Kitchener, Ontario, Canada
Contact:

#44 Post by rarsa »

I think we are close.

Please send me the result of the following command:

Code: Select all

ls -la /usr/lib/cups/filter
I am 99.99% sure that the foomatic filter comes with the hpijs installation. The problem is that the foomatic tools are writen in Perl (a scripting language) and you don't have the Perl interpreter.

Try this command:

Code: Select all

perl -h
Does that show you the perl usage with all the parameters? or Does it say command not found?

If it is command not found, install Perl. Perl is a PupGet. You can install it through the Puppy start menu, under "Setup | PupGet package manager". Follow the instructions and install it.

After that try printing again the test page.

User avatar
dewdrop
Posts: 298
Joined: Tue 30 Aug 2005, 01:54
Location: Texas USA

CUPS

#45 Post by dewdrop »

Hi Rarsa,

I believe that I should be in the install from yesterday, so I loaded that onto my machine - in other words, this is not a pristine install.

I then went to the folder where I have the CUPS files located and opened the xterm terminal from inside that folder. I don't know if this procedure is what you were expecting, but here are the results of your requests.

Dewdrop



[quote]Please send me the result of the following command:
Code:
ls -la /usr/lib/cups/filter

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

# ls -la /usr/lib/cups/filter
drwxr-xr-x 2 root root 1024 Sep 6 09:02 .
drwxr-xr-x 6 root root 1024 Oct 14 2004 ..
lrwxrwxrwx 1 root root 21 Sep 6 09:02 foomatic-rip -> /usr/bin /foomatic-rip
-rwxr-xr-x 1 root root 4748 Jan 4 2005 gziptoany
-rwxr-xr-x 1 root root 43880 Jan 4 2005 hpgltops
-rwxr-xr-x 1 root root 24004 Jan 4 2005 imagetops
-rwxr-xr-x 1 root root 56868 Jan 4 2005 imagetoraster
-rwxr-xr-x 1 root root 689216 Jan 4 2005 pdftops
-rwxr-xr-x 1 root root 30664 Jan 4 2005 pstops
-rwxr-xr-x 1 root root 1888 Dec 15 2003 pstopxl
-rwxr-xr-x 1 root root 1856 Dec 15 2003 pstoraster
-rwxr-xr-x 1 root root 7872 Jan 4 2005 rastertodymo
-rwxr-xr-x 1 root root 12948 Jan 4 2005 rastertoepson
-rwxr-xr-x 1 root root 12500 Jan 4 2005 rastertohp
-rwxr-xr-x 1 root root 36516 Jan 4 2005 texttops
#
# perl -h
perl: No such file or directory
#


Per your instructions, I shall now install the Perl PupGet.

Dewdrop

User avatar
rarsa
Posts: 3053
Joined: Sun 29 May 2005, 20:30
Location: Kitchener, Ontario, Canada
Contact:

#46 Post by rarsa »

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.

User avatar
rarsa
Posts: 3053
Joined: Sun 29 May 2005, 20:30
Location: Kitchener, Ontario, Canada
Contact:

#47 Post by rarsa »

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.

User avatar
dewdrop
Posts: 298
Joined: Tue 30 Aug 2005, 01:54
Location: Texas USA

CUPS

#48 Post by dewdrop »

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

User avatar
rarsa
Posts: 3053
Joined: Sun 29 May 2005, 20:30
Location: Kitchener, Ontario, Canada
Contact:

#49 Post by rarsa »

No, just change the logLevel to debug (in /etc/rc.d/rc.cups), try to print the test page and send me the log.

User avatar
dewdrop
Posts: 298
Joined: Tue 30 Aug 2005, 01:54
Location: Texas USA

CUPS

#50 Post by dewdrop »

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.

Post Reply