public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Waugh <twaugh@redhat.com>
To: "Michael B. Allen" <mballen@erols.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: parport not detected
Date: Sat, 17 Mar 2001 06:21:19 -0500	[thread overview]
Message-ID: <20010317062119.B13877@redhat.com> (raw)
In-Reply-To: <20010316185253.A865@nano.foo.net>
In-Reply-To: <20010316185253.A865@nano.foo.net>; from mballen@erols.com on Fri, Mar 16, 2001 at 06:52:53PM -0500

On Fri, Mar 16, 2001 at 06:52:53PM -0500, Michael B. Allen wrote:

> The parallel port is not being detected on my ABIT KT7A KT133 w/ Athlon

Need dmesg output to see what parport is being told and what is
finding out for itself.

> BIOS options are:
> 
> 728/IRQ5
  ^^^ 278, probably

> 378/IRQ7
> 3BC/IRQ7

But which one is it actually set to?

> Of the above what's optimal?

It depends what you're doing, really.

> I also tried an options line in modules.conf. I believe it was:
> 
> options parport_pc io=0x3bc irq=7

Take that out and see what happens.

> That was reflected in /proc but no difference in actually "detecting"
> the parallel port.

I don't know what you mean really.  Are you saying that you can't
print, or just that the device ID probe (to get the printer name)
isn't working?

> Also, if I build parpart into the kernel I get nothing but a
> hard lockup on 'Starting kswapd v 1.5'.

That's quite strange.

Which kernel version are you using?  Take a look at the
'troubleshooting' section of Documentation/parport.txt.

Tim.
*/

      parent reply	other threads:[~2001-03-17 11:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-16 23:52 parport not detected Michael B. Allen
2001-03-17  2:00 ` Tim Moore
2001-03-17  6:05   ` Michael B. Allen
2001-03-17 11:23     ` Tim Waugh
2001-03-17 11:21 ` Tim Waugh [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=20010317062119.B13877@redhat.com \
    --to=twaugh@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mballen@erols.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