From: "S. Barret Dolph" <wheds8@ms66.hinet.net>
To: "linux-newbie@vger.kernel.org" <linux-newbie@vger.kernel.org>
Subject: Re: Printing
Date: 06 Apr 2003 23:32:26 +0800 [thread overview]
Message-ID: <1049643149.16033.10.camel@localhost.localdomain> (raw)
In-Reply-To: <5.1.0.14.1.20030401085644.01e9c520@celine>
My apologies for incomplete answers. I am trying to figure how to find
the answers to your questions.
>
> 1. How is your printer physically connected to the system? (parport,
> serial, USB, network?) If it is a parport printer, do you have all the
> right modules installed?
The printer is connected by a cable to the computer but it is not USB.
>
> 2. Which lpd daemon does Mandrake 9 use?
I don't know but will look this up.
>
> 3. What printer is it? Does the Linux printer site (I've misplaced the URL,
> so you'll need to search for it) report anything special about it and Linux?
HP Laserjet 1100 but there is nothing special listed on the Linux
printer site about the printer.
>
> 4. What does its entry in /etc/printcap look like?
# This file was automatically generated by cupsd(8) from the
# /etc/cups/printers.conf file. All changes to this file
# will be lost.
Printer:
>
> 5. How are you trying to print under Linux? (What apps are you printing from?)
Gnome Ximian Evolution, KWord, Kspread, Mozilla.
>
> 6. What happens if you try to dump a file directly to the printer? (How you
> do this depends on the answer to Q1, but an example would be: "cat
> /etc/passwd >/dev/lp0").
Don't understand but I am checking on this.
>
> 7. Assuming you are using a typical lpd daemon, what do these result in?
>
> A. lpr -pdefault /etc/passwd
> B. lpq
>
> (Change "default" if the printer use a different printcap entry.)
Checking this out. (Ie. Don't understand.)
>
> 8. Did this printer work under any other version fo Linux, or is this your
> first try using it with a Linux system? If the first, please provide details.
Worked ok under an older version of Mandrake.
>
> 9. Does your general description of the problem conceal any pattern you've
> seen? For example, after a boot/init, the first attempt to print works but
> not later ones? Or power-cycling the printer causes printing temporarily to
> resume? Or ... ???
I still can't find a pattern. I haven't been able to figure out when the
printing finally comes.
>
> (BTW, there is nothing special about /etc/passwd except that it is a file
> that I know must be present on your system. Feel free to substitute any
> plain-text file that you prefer.)
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
prev parent reply other threads:[~2003-04-06 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 9:23 Printing S. Barret Dolph
2003-04-01 17:08 ` Printing Ray Olszewski
[not found] ` <1049541317.1761.7.camel@localhost.localdomain>
2003-04-05 16:22 ` Printing Ray Olszewski
2003-04-06 15:32 ` S. Barret Dolph [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1049643149.16033.10.camel@localhost.localdomain \
--to=wheds8@ms66.hinet.net \
--cc=linux-newbie@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox