From: Axel Thimm <Axel.Thimm@physik.fu-berlin.de>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org, "Manuel A. McLure" <mmt@unify.com>,
Jens Dreger <Jens.Dreger@physik.fu-berlin.de>,
David Hansen <David.Hansen@physik.fu-berlin.de>
Subject: Re: Still IRQ routing problems with VIA
Date: Tue, 10 Apr 2001 21:16:05 +0200 [thread overview]
Message-ID: <20010410211605.A1052@pua.domain> (raw)
In-Reply-To: <419E5D46960FD211A2D5006008CAC79902E5C1A1@pcmailsrv1.sac.unify.com> <Pine.LNX.3.96.1010410125456.26863A-100000@mandrakesoft.mandrakesoft.com> <419E5D46960FD211A2D5006008CAC79902E5C1A0@pcmailsrv1.sac.unify.com> <20010410193125.A31792@pua.domain> <3AD34518.2A43A346@mandrakesoft.com>
In-Reply-To: <3AD34518.2A43A346@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Tue, Apr 10, 2001 at 01:38:32PM -0400
[-- Attachment #1: Type: text/plain, Size: 2783 bytes --]
On Tue, Apr 10, 2001 at 01:38:32PM -0400, Jeff Garzik wrote:
> Axel Thimm wrote:
> > 0.7.[2,3] are the usb devices. BIOS (and 2.2 kernels) had them at IRQ 5.
> > 2.4 somehow picks the irq of the ethernet adapter, iqr 11, instead.
> > At least usb is then unusable.
> > As you say that you have the same board, what is the output of dump_pirq -
> > are your link values in the set of {1,2,3,5} or are they continuous 1-4?
> > Maybe you are lucky - or better say, I am having bad luck :(
> Changing '#undef DEBUG' to '#define DEBUG 1' in arch/i386/kernel/pci-i386.h
> is also very helpful. Can you guys do so, and post the 'dmesg -s 16384'
> results to lkml? This includes the same information as dump_pirq, as well
> as some additional information.
OK, gzip-attached to this mail.
> Note that turning "Plug-n-Play OS" off in BIOS setup typically fixes many
> interrupt routing problems -- but Linux 2.4 should now have support for PNP
> OS:Yes. Clearly there appear to be problems with that support on some Via
> hardware.
I had the problems with both settings (but I have tried so many patches and
kernels, that I cannot be sure about the combinations).
> Note that you should have "Plug-n-Play OS: Yes" when generated the
> requested 'dmesg' output.
O.K.
On Tue, Apr 10, 2001 at 01:01:07PM -0500, Jeff Garzik wrote:
> 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)
left to yes then, to keep the same BIOS settings/errors.
> Operating System: other (or Unix, depending on the BIOS)
n/a
> Memory hole: no
O.K.
> Unless you are using ISA cards, make sure all your PCI plug-n-play
> IRQ settings are set to "PCI/PnP" not "ISA/ICU".
O.K.
> hmmm, maybe I should write a Linux kernel BIOS guide/FAQ...
Yes, please!
And here are my FAQs with what I think are the answers (which means they are
possibly wrong, but then you get the idea, what some ppl might misunderstand):
Q) What does Plug-and-Play BIOS setting do?
A) It allows the OS to reassign IRQ/ports to devices (?)
Q) When should I turn it on or off?
A) If your BIOS is doing the right thing for you it's safe to turn it
off. If you trust your OS more, turn it on. (?)
Q) Which OSes should I trust? What about multiboot systems?
A) Linux > 2.4.x, M$ xxx, etc. (?)
Q) What bad thing might happen, if a non P&P OS has in the BIOS a P&P setting
or vice versa?
A) ... (?)
Thanks, Axel.
--
Axel.Thimm@physik.fu-berlin.de
[-- Attachment #2: dmesg.2.4.3-puredebug.log.gz --]
[-- Type: application/x-gzip, Size: 3751 bytes --]
next prev parent reply other threads:[~2001-04-10 19:16 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
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 [this message]
2001-04-11 15:13 ` Pierre Etchemaite
-- strict thread matches above, loose matches on Subject: below --
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=20010410211605.A1052@pua.domain \
--to=axel.thimm@physik.fu-berlin.de \
--cc=David.Hansen@physik.fu-berlin.de \
--cc=Jens.Dreger@physik.fu-berlin.de \
--cc=jgarzik@mandrakesoft.com \
--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