public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Ben-Gershon <mybg@netvision.net.il>
To: linux-kernel@vger.kernel.org
Cc: Tim Waugh <twaugh@redhat.com>
Subject: Re: lpr to HP laserjet stalls
Date: Wed, 05 Sep 2001 00:17:22 +0300	[thread overview]
Message-ID: <3B9544E2.654F3945@netvision.net.il> (raw)
In-Reply-To: <3B93E289.7F121DE9@netvision.net.il> <20010903221142.J20060@redhat.com> <3B94B4E7.701C76FA@netvision.net.il> <20010904121523.Q20060@redhat.com> <3B94B93B.2B907DCF@netvision.net.il> <20010904122751.S20060@redhat.com> <3B94D58B.180860A2@netvision.net.il> <20010904142755.V20060@redhat.com> <3B94DA02.9F6E9184@netvision.net.il> <20010904144814.W20060@redhat.com>

Tim Waugh wrote:
> 
> On Tue, Sep 04, 2001 at 04:41:22PM +0300, Michael Ben-Gershon wrote:
> 
> > Building it as a module meant I didn't have to reboot for every time
> > I wanted to retest it with different parameters.
> 
> I understand.  But I'm looking at the differences between a broken
> system and a working system.  It seems from what you say to be:
> 
> - CONFIG_PARPORT_PC_FIFO
> - Parport built as modules
> 
> So it seems as though it's either one of these, or the combination.

The modules side could possibly be explained by a possible h/w clash, with
the printer support loaded later than something which it may be clashing
with if loaded first - although I am a bit out of my depth in terms of
my understanding of the kernel boot process here. However, what is
interesting is that I originally had the problems when I upgraded to
the 2.4 kernel (and RH 7.1). I subsequently upgraded the h/w from a
PII 333 on a Tyan m/b to a P4 1.5G on an Asus m/b. The former was a mixed
PCI/ISA board, with both types of cards installed, whereas the latter
was all PCI. I had the same printer problem on both boards with kernel 2.4,
which makes the possibility of a h/w clash being the cause a bit remote.

The 2 changes above (I have not yet had a chance to try each in isolation)
fixed the problem.

Michael Ben-Gershon
mybg@netvision.net.il

      reply	other threads:[~2001-09-04 21:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-03 20:05 lpr to HP laserjet stalls Michael Ben-Gershon
2001-09-03 21:11 ` Tim Waugh
2001-09-04  0:20   ` Horst von Brand
2001-09-04  8:36     ` Tim Waugh
2001-09-04  0:56   ` Patrick Dreker
2001-09-04  8:50     ` Tim Waugh
2001-09-04 12:07       ` Patrick Dreker
2001-09-04 11:05   ` Michael Ben-Gershon
     [not found]   ` <3B94B4E7.701C76FA@netvision.net.il>
     [not found]     ` <20010904121523.Q20060@redhat.com>
2001-09-04 11:21       ` Michael Ben-Gershon
2001-09-04 11:27         ` Tim Waugh
2001-09-04 13:22           ` Michael Ben-Gershon
2001-09-04 13:27             ` Tim Waugh
2001-09-04 13:41               ` Michael Ben-Gershon
2001-09-04 13:48                 ` Tim Waugh
2001-09-04 21:17                   ` Michael Ben-Gershon [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=3B9544E2.654F3945@netvision.net.il \
    --to=mybg@netvision.net.il \
    --cc=linux-kernel@vger.kernel.org \
    --cc=twaugh@redhat.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