CUPS Administration Behaving Badly

[edoc]

Am rebuilding my laptop with Puppy 2.00.

Installed CUPS for my HP 4215 OfficeJet and the setup my Samsung ML-2251NP.

The HP is not responding and after deleting and reinstalling the HP setup a couple of times CUPS Adminstration has retained three deleted copies and also refuses to allow me to delete test jobs.

???

Thanks! doc

[dewdrop]

Am rebuilding my laptop with Puppy 2.00.

Installed CUPS for my HP 4215 OfficeJet and the setup my Samsung ML-2251NP.

The HP is not responding and after deleting and reinstalling the HP setup a couple of times CUPS Adminstration has retained three deleted copies and also refuses to allow me to delete test jobs.

???

Thanks! doc

Hey Doc,

This must be nerve-wrecking. You had them working with Puppy 2.0 before correct?

I know you are aware of my step-by-step found here -
http://www.murga.org/~puppy/viewtopic.php?t=8673

Please go thru the drill one more time, remembering especially to reboot the machines, and check the /etc/rc.d/rc.local file and be sure that it has the correct info listed ...

Also, be sure and use Rarsa's perl file...since the perl file in Barry's Puppy 2.0 is not correct. Even in Puppy 2.01, Barry's perl file is not correct so I had to use Rarsa's file so my printer would work (HP Deskjet 6540). Barry knows there is a problem with the perl file in both 2.0 and 2.01.

When you talk about the CUPS Admin you are talking about the http://localhost:631 site....correct?

As usual, get back to us if it is still not giving you what you expect.

dewdrop

[edoc]

check the /etc/rc.d/rc.local file and be sure that it has the correct info listed ...

#this file called from rc.local0
#you can edit this file
#When firewall is installed, will append lines to this file...
#
# Load Ethernet Card
modprobe forcedeth
# Load net-daemon
# rm /eth/dhcpcd-eth0.pid
dhcpcd
# Start Samba
/usr/sbin/smbd -D
/usr/sbin/nmbd -D
#Start USB for Printer
Modprobe usblp
# Start Cups
/etc/rc.d/rc.cups start
# Load the module for usb printers
modprobe printer

Also, be sure and use Rarsa's perl file...since the perl file in Barry's Puppy 2.0 is not correct. Even in Puppy 2.01, Barry's perl file is not correct so I had to use Rarsa's file so my printer would work (HP Deskjet 6540). Barry knows there is a problem with the perl file in both 2.0 and 2.01.

Done.

When you talk about the CUPS Admin you are talking about the http://localhost:631 site....correct? dewdrop

Correct.

I know you are aware of my step-by-step found here -
http://www.murga.org/~puppy/viewtopic.php?t=8673

Please go thru the drill one more time, remembering especially to reboot the machines, and ...

Here it is from the WIKI (with a few clarifying edits I made -- please check them for accuracy). My results are highlighted in Green.

Note: You must be logged into the Internet to perform the CUPS install.

Instructions:
1. Download the cups-install.tar.gz file
So you don't have to chase around blindly, here is the URL:
<http://www.murga.org/~puppy/viewtopic.php?t=2049∞>
Scroll down a few posts and you will see the box with the download link.
2. Open a console terminal and change folders to the folder where you downloaded the file.
3. Untar the cups-install.tar.gz with "tar -xvzf cups-install.tar.gz". This tar file includes the scripts to install cups. ESP Ghostscript and the hpijs driver.

Good to here.

4. From the console execute "sh cups-install.sh"
In Puppy 2.00 you *may* see this message after executing "sh cups-install.sh"

modprobe printer
FATAL: Module printer not found.
/etc/rc.d/rc.cups start
cups: started scheduler.

Ignore it and continue the CUPS setup process.

Is this correct? I seem to recall a prior instruction during some sort of install to ignore these sort of error messages.

5. If you are printing to a remote CUPS server go to step 9, otherwise continue with step 6.

Is someone is "printing to a remote CUPS server" does it do any harm if they perform the extra steps? Not relevant here, just wondering.

6. If your print drivers require ESP Ghost script, execute ""sh espgs-install.sh". (the hpijs driver needs it).
7. Install the CUPS drivers for the printers connected to your puppy computer according to your driver's instructions. Check in www.linuxprinting.org to find out the drivers required by your printer. These instructions include the hpijs, if your printer is suported just execute "sh hpijs-install.sh".

Good to here.

8. If your driver requires foomatic, you also need to install Perl. Don't use the Perl PupGet as it is a stripped down version. If you are using puppy 1.0.5 download the usr_devx.sfs file.
You may download it from here:
<http://www.murga.org/~puppy/viewtopic.php?t=2049∞>
Scroll down a few posts and you will see the box with the download link.
If you are using a puppy version prior to 1.0.5 downlad the attached perl installer, untar it and install with "sh perl-5.8.6-install.sh"

BIG QUESTION! What about all of the versions after 1.5 and what about 2.0x?

9. Restart cups with "sh /etc/rc.d/rc.cups restart"

Good here.

10. Open your browser and go to the following address http://localhost:631&#8734;
11. Add your printer following the links on that page. If you already have a CUPS server that allow browsing you will see the shared printers there.
12. Print the test page

I walked through the setup, powered the printer on and off, then rebooted the computer.
It accepts a print job without error but nothing happens.

??? Thanks! doc

[edoc]

Just remembered that I had modified rc.local following someone's suggestions.

Anything here that may be preventing me from using my HP USB printer?

#this file called from rc.local0
#you can edit this file
#When firewall is installed, will append lines to this file...
#
# Load Ethernet Card
modprobe forcedeth
# Load net-daemon
# rm /eth/dhcpcd-eth0.pid
dhcpcd
# Start Samba
/usr/sbin/smbd -D
/usr/sbin/nmbd -D
#Start USB for Printer
Modprobe usblp
# Start Cups
/etc/rc.d/rc.cups start
# Load the module for usb printers
modprobe printer

Thanks! doc

[Kal]

Hello, Edoc

The example you copied into your rc.local was never intended to be copied in whole. Sorry,
if you didn't understand.

Only the parts that applied to your hardware or operating system were to be used. This
happens to be for a motherboard with NVIDIA chip set and a full harddrive install, at the time. Do you have full Samba+server compiled and installed, as in that post? There were many problem with Puppy's 2.00 full harddrive install.

Many of the problems have been fixed in Puppy 2.01, but not all. I believe this resulted
because. not many testers installed the alpha and betas to their harddrive in a full install. "I'll install it to the harddrive, when it's final", I am guilty. So, if you are still using the full harddrive install, May I recommend, and as Barry did, that you save your data and reinstall with Puppy 2.01 or better yet, wait for Puppy 2.02. I also believe you were, maybe, not reading Dewdrop's latest instructions on Cups, he posted a link, he has worked hard on them.

Dewdrop's posts are much clearer than mine, so you might give them a try. Trying to write instructions can be very difficult.
Good Luck, Kal

[edoc]

Only the parts that applied to your hardware or operating system were to be used. This
happens to be for a motherboard with NVIDIA chip set and a full harddrive install, at the time. Do you have full Samba+server compiled and installed, as in that post? There were many problem with Puppy's 2.00 full harddrive install.

I have now commented-out "#" the two Samba lines, though I would be surprised if they
bothered anything.

Many of the problems have been fixed in Puppy 2.01, but not all. I believe this resulted
because. not many testers installed the alpha and betas to their harddrive in a full install. "I'll install it to the harddrive, when it's final", I am guilty. So, if you are still using the full harddrive install, May I recommend, and as Barry did, that you save your data and reinstall with Puppy 2.01 or better yet, wait for Puppy 2.02.

OK, will wait on 2.02

I also believe you were, maybe, not reading Dewdrop's latest instructions on Cups, he posted a link, he has worked hard on them. Dewdrop's posts are much clearer than mine, so you might give them a try. Trying to write instructions can be very difficult. Good Luck, Kal

I not only used his instructions I have added some additional detailed notes to them and
asked him to make sure they are accurate.

I respect that it is time-consuming to write instructions but my single greatest complaint
with Linux over many years has been critical gaps in most instructions. There is a tendency
in the Linux world to incorrectly presume reader knowlege -- instructions need to skip not
even the smallest detail and to document common anomalies.

Some examples of what is often forgotten:

1. Common error messages that may be ignored.

2. How to start an app (e.g. I have been unable to find anything that explains how to start
a tcl app).

3. Including the specific URL for something one must acquire in order to complete the
process. (And advising the user, before they start, that they must have a working Internet
connection in order to complete the process.)

4. Noting the Version of Linux and/or the Distro under which an app or proceedure has
been tested (most recently there are huge differences between the many versions of
Puppy within 6 months -- forgetting the Puppy version will frustrate users with bad info).

5. Noting if an app or proceedure has been tested on a HDD install, CD-boot, or both.

I am sure others may think of additional critical elements in complete instructions.

I will renew my request that a simple matrix be forced upon every Forum Post
Requiring: Puppy Version, HDD or CD, and Other to be filled before the Forum Post is
published. We need greater discipline on the Forum, and in the Wiki, if we are not
to frustrate ourselves and newbies with confusion!

IMHO ... doc

[Kal]

Hi, Edoc

I just re-read your earlier posts again for the tenth time. Goes to show, doesn't it. The lightbulb just came on, maybe!

Have you checked the Usbview in Menu>Control Panel>Usbview USB information. Is the
printer listed in black or is it red?
This is just an idea, please, Kal

[edoc]

Hi, Edoc

I just re-read your earlier posts again for the tenth time. Goes to show, doesn't it. The lightbulb just came on, maybe!

Have you checked the Usbview in Menu>Control Panel>Usbview USB information. Is the
printer listed in black or is it red?
This is just an idea, please, Kal

Red.

???

Thanks! doc

[Kal]

Hello, Edoc

We may be on a roll. Try adding toward the top of rc.local, I think you know where it is by now (/etc/rc.d just in case). Add:

# Load USB Main Modules
Modprobe ohci-hcd
Modprobe uhci-hcd
Modprobe ehci-hcd

Reboot and check usbview again, we can remove what's not used later. I hope it turns to black. I forgot in Puppy 2.00 the main usb modules are not loaded, they are in Puppy 2.01. as I use now.
Good Luck, Kal

[edoc]

Hello, Edoc

We may be on a roll. Try adding toward the top of rc.local, I think you know where it is by now (/etc/rc.d just in case). Add:

# Load USB Main Modules
Modprobe ohci-hcd
Modprobe uhci-hcd
Modprobe ehci-hcd

Reboot and check usbview again, we can remove what's not used later. I hope it turns to black. I forgot in Puppy 2.00 the main usb modules are not loaded, they are in Puppy 2.01. as I use now.
Good Luck, Kal

Still red.

Perhaps I should wait for 2.02 which I gather is due any day?

Seems 2.00 was rushed a little and 2.01 was a stop-gap patch so hopefully 2.02 will be
what 2.00 was intended to be?

Stated another way 2.00 was a functional Beta, 2.01 was a first-feedback effort to patch
discovered gaps in 2.00 and 2.02 should have benefitted from lots of folks pounding on
2.00 and 2.01 and address most of the gaps.

Yes?

Thanks! doc

[Kal]

I was so much in hope, at least we know it is a usb modules not loaded, my son keeps telling me. He didn't reboot, there is a typo or something in rc.local. I wish. I think, I'll gave up.
We did have one success with the development install, down in the bugs section. I think the waiting for Puppy 2.02 is sound advise still.
Sorry, we failed you, Kal

[edoc]

Should I download and install the 2.00 Service Pack & fixconfigure while I wait for 2.02?

<http://dotpups.de/puppy-releases/2.00/service-packs/>
[archive] Puppy-2.00-servicepack.pup 10662 13.06.06, 03:08
[archive] fixconfigure.pup 4668 17.06.06, 17:33

doc

[Kal]

No, it is best to wait. Because, it may all change with Puppy 2.02. Got another success in bugs, that helps.
We will keep trying, good luck, Kal

[dewdrop]

Hello, Edoc

We may be on a roll. Try adding toward the top of rc.local, I think you know where it is by now (/etc/rc.d just in case). Add:

# Load USB Main Modules
Modprobe ohci-hcd
Modprobe uhci-hcd
Modprobe ehci-hcd

Reboot and check usbview again, we can remove what's not used later. I hope it turns to black. I forgot in Puppy 2.00 the main usb modules are not loaded, they are in Puppy 2.01. as I use now.
Good Luck, Kal

Still red.

Perhaps I should wait for 2.02 which I gather is due any day?



Yes?

Thanks! doc

I edoc.

I'm just getting back online after a move back to Texas, so I'm a little bit behind on what's been happening with things Puppy.

I really haven't had a chance to look over your current challange, but it looks like your suggestion to wait for Puppy 2.02 is a good one.

Dewdrop