From: Brian Gerst <bgerst@quark.didntduck.org>
To: Ognen Duzlevski <ognen@kc.rr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: parport question
Date: Sat, 09 Nov 2002 17:15:11 -0500 [thread overview]
Message-ID: <3DCD88EF.20400@quark.didntduck.org> (raw)
In-Reply-To: Pine.LNX.4.44.0211091258440.1456-100000@gemelli.dyndns.org
Ognen Duzlevski wrote:
> Hi,
>
> I have sent this question to the people listed in the parport
> kernel directory (the maintainers) but have yet not received a reply and
> I am not sure if this is exactly a linux-kernel question.
>
> I have a printer that worked fine under linux (redhat/lexmark 3200) for a
> long time, then I switched over to 2.4.18 and debian and it stopped
> working. I compiled the parport support into the kernel, I did that with
> 2.4.19, I did it also as modules, I tried 2.5.45, still won't work, not
> even a cat test.txt > /dev/lp0
>
> The dmesg shows that the printer is recognized correctly:
>
> Nov 9 13:06:32 gemelli kernel: parport0: PC-style at 0x378 (0x778)
> [PCSPP,TRISTATE]
> Nov 9 13:06:32 gemelli kernel: parport0: irq 5 detected
> Nov 9 13:06:34 gemelli kernel: parport0: Printer, Lexmark Lexmark 3200
> lp0: using parport0 (polling).
> lp0: console ready
>
> The BIOS has a ton of settings such as "auto" or "normal" - I have tried
> them all, tried forcing the DMA / IRQ from the BIOS and then feeding these
> values to parport_pc, still won't work. I have tried all combinations of
> Normal, ECP, ECP+EPP or EPP solely, won't work.
>
> I then installed vmware and windows nt as a guest OS, under the same
> kernels. I set up parport0 to be used by vmware and, it prints from
> Windows nt (so I know the printer is fully functional).
>
> Any ideas, help would be appreciated. Sorry if this is not the place to
> post the question but I have tried google, linux-printing.org, usenet to
> no avail.
>
> CHeers,
> Ognen
It sounds like a userspace problem. The information about this printer
I've found on the web shows it to be a GDI printer (ie. all the smarts
are in the software driver, not in the printer), which means sending
text to it will never print anything. You will need to check the
configuration of ghostscript or whatever userspace printer driver debian
is using.
--
Brian Gerst
next prev parent reply other threads:[~2002-11-09 22:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-09 19:10 parport question Ognen Duzlevski
2002-11-09 22:15 ` Brian Gerst [this message]
2002-11-10 21:52 ` Fernando Fraga e Silva
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=3DCD88EF.20400@quark.didntduck.org \
--to=bgerst@quark.didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ognen@kc.rr.com \
/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