linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Manuel A. McLure" <mmt@unify.com>
Cc: "'Axel Thimm'" <Axel.Thimm@physik.fu-berlin.de>,
	linux-kernel@vger.kernel.org
Subject: RE: Still IRQ routing problems with VIA
Date: Tue, 10 Apr 2001 13:01:07 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.3.96.1010410125456.26863A-100000@mandrakesoft.mandrakesoft.com> (raw)
In-Reply-To: <419E5D46960FD211A2D5006008CAC79902E5C1A1@pcmailsrv1.sac.unify.com>

On Tue, 10 Apr 2001, Manuel A. McLure wrote:
> This may be the difference - I always set "Plug-n-Play OS: No" on all my
> machines. Linux works fine and it doesn't seem to hurt Windows 98 any.

Correct, it's perfectly fine to do that on all machines (not just Via).
Users should also set "PNP OS: No" for Linux 2.2...

Other BIOS settings to verify:
Assign IRQ to VGA: no (optional, but you probably don't need a VGA IRQ)
Operating System: other (or Unix, depending on the BIOS)
Memory hole: no

Unless you are using ISA cards, make sure all your PCI plug-n-play
IRQ settings are set to "PCI/PnP" not "ISA/ICU".

hmmm, maybe I should write a Linux kernel BIOS guide/FAQ...

	Jeff




  reply	other threads:[~2001-04-10 18:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-10 17:52 Still IRQ routing problems with VIA Manuel A. McLure
2001-04-10 18:01 ` Jeff Garzik [this message]
2001-04-10 16:51   ` Still IRQ routing problems with VIA (was: VIA KT133 chipset P CI crazyness...) Manuel A. McLure
2001-04-10 17:31     ` Still IRQ routing problems with VIA Axel Thimm
2001-04-10 17:38       ` Jeff Garzik
2001-04-10 19:16         ` Axel Thimm
2001-04-11 15:13 ` Pierre Etchemaite
2001-04-10 21:05 Manuel A. McLure
2001-04-10 21:11 ` Jeff Garzik
2001-04-11 19:56   ` Axel Thimm
2001-04-10 21:24 Manuel A. McLure
2001-04-10 21:36 ` Jeff Garzik

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=Pine.LNX.3.96.1010410125456.26863A-100000@mandrakesoft.mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=Axel.Thimm@physik.fu-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmt@unify.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;
as well as URLs for NNTP newsgroup(s).