All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Kruger <krugerb@benning.army.mil>
To: linux-kernel@vger.kernel.org
Subject: PROBLEM
Date: Wed, 14 Aug 2002 10:20:43 -0400	[thread overview]
Message-ID: <3D5A673B.1000702@benning.army.mil> (raw)

1.  Printing output corrupted using kernel 2.4.19.
2.  Print output from three Linux servers corrupted.  These servers are 
running Samba 2.2.5, and are Slackware 8.0 or 8.1 systems.  Print output 
from Windows platforms, especially .pdf files, gets corrupted.  Half 
pages are printed.  Pages are repeated, etc.  Drop back to the 2.4.18 
kernel, and the problem goes away.  Kernel on all systems compiled 
locally, e.g. on each system.  Print daemon is from the LPRng package. 
 Printers include TCP/IP printers (LPRng redirect using printcap) and 
those attached via parallel ports.  Windows systems include XP, 2000, 
and 98.  Regardless of the OS, the printer output is corrupted w/ 2.4.19 
kernel, but works fine when kernel 2.4.18 is run.
3.  Kernel, printing
4.  Kernel version - 2.4.19
5.  Output - no error messages reported
6.  Shell Script - not applicable.
7.  Environment:
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
 
Linux wdbbl080104 2.4.19 #2 SMP Mon Aug 12 10:31:39 EDT 2002 i586 unknown
 
Gnu C                  2.95.3
Gnu make               3.79.1
util-linux             2.11r
mount                  2.11r
modutils               2.4.16
e2fsprogs              1.19
reiserfsprogs          3.x.0b
pcmcia-cs              3.1.33
PPP                    2.4.1
Linux C Library        2.2.5
Dynamic linker (ldd)   2.2.5
Procps                 2.0.7
Net-tools              1.60
Kbd                    1.06
Sh-utils               2.0
Modules Loaded         bsd_comp ppp_generic slhc slip

No module info necessary, as lp is compiled as part of the kernel.

If any other info is needed, please let me know.

As always, my thanks for your hard work.  

Regards - Bob Kruger


             reply	other threads:[~2002-08-14 14:12 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-14 14:20 Bob Kruger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-27 22:38 Problem Michael Salman
2024-07-29 21:52 ` Problem brian m. carlson
2015-02-20  0:10 Problem Jeffrey O'Hara
2014-07-13  2:39 PROBLEM Michael P
2011-01-11 10:58 Problem Marco Sarzi Madidini
2011-01-11 13:37 ` Problem solarflow99
2011-01-11 15:38 ` Problem Frank Cox
2009-01-21 13:50 problem Csaba Dobo
2007-04-27  1:35 PROBLEM Thomas Kayser
2007-01-21  2:05 Problem Alessio Palmero Aprosio
2006-02-03 12:02 PROBLEM Badri Pillai
2004-12-24  4:22 PROBLEM Scott Mollica
2004-12-27  3:28 ` PROBLEM Adrian Bunk
2004-12-20 12:10 problem nikolai
2004-12-20 12:45 ` problem Jesper Lund
2004-06-17 17:16 problem Admin
2003-12-19 18:10 PROBLEM Federico Freire
2003-12-19 18:25 ` PROBLEM Jean-Philippe Woot de Trixhe
2003-12-19 19:29   ` PROBLEM Jose Luis Domingo Lopez
2003-11-30  4:07 PROBLEM Mike Morrell
2003-11-30  6:05 ` PROBLEM Chris Ernst
2003-11-10  3:13 problem cemal
2003-11-10  3:17 ` problem Justin Zygmont
2003-10-21 13:39 PROBLEM laurent.miaille
2003-06-12 14:12 Problem Hector M Sanchez M
2003-05-09  1:26 problem useless
2003-03-17 21:07 Problem Pontus Falk
2003-03-17 21:43 ` Problem pa3gcu
2003-03-17 22:09   ` Problem Pontus Falk
2003-03-17 23:12     ` Problem Shane Deering
2003-03-18 15:50     ` Problem pa3gcu
2003-03-25  6:41       ` Problem Henk Remijn
2003-03-25 16:42         ` Problem bernard pidoux
2003-03-25 17:25           ` Problem Jarmo
2003-03-27 12:01             ` Problem bernard pidoux
2003-03-25 20:45           ` Problem pa3gcu
2003-03-26  0:46           ` Problem M Taylor
2003-03-13 21:40 Problem Smiler
2003-03-09 11:49 PROBLEM Kósa Ferenc
2003-03-09 12:55 ` PROBLEM John Bradford
2003-01-26  0:07 problem Mark Ryan
2003-01-26  1:41 ` problem Arnt Karlsen
2002-12-31 16:19 Problem Amar Lior
2002-12-31 17:38 ` Problem Hugh Dickins
2002-12-31 16:18 PROBLEM Amar Lior
2002-08-29 19:55 Problem Ryan White
2001-09-11 23:16 Problem George Lloyd

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=3D5A673B.1000702@benning.army.mil \
    --to=krugerb@benning.army.mil \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.