From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Sean Middleditch <elanthis@awesomeplay.com>,
linux-kernel@vger.kernel.org
Subject: Re: Via Onboard Audio - Round #2
Date: Sun, 04 Nov 2001 08:56:10 -0500 [thread overview]
Message-ID: <3BE548FA.DEC6C2B3@mandrakesoft.com> (raw)
In-Reply-To: <3BE4CC20.5FFEC4B5@mandrakesoft.com> <1004849558.457.15.camel@stargrazer> <3BE4CC20.5FFEC4B5@mandrakesoft.com> <5.1.0.14.2.20011104131312.02bd8ae8@pop.cus.cam.ac.uk> <5.1.0.14.2.20011104134957.00bb5b60@pop.cus.cam.ac.uk>
Anton Altaparmakov wrote:
>
> At 13:44 04/11/2001, Jeff Garzik wrote:
> >Anton Altaparmakov wrote:
> > > Linux is not
> > > a PNP OS and hence problems like yours often get fixed by setting in the
> > > BIOS that you are not using a PNP OS.
> >
> >Incorrect. PCI IRQ routing (net effect of "PNP OS: Yes") works fine for
> >everybody except those with Sean's type of PCI IRQ routing table.
>
> Well, if I reboot set it to YES and boot into Linux my SB Live stops
> working. As does my wintv pci (or my network card, can't remember)... If I
> reboot, set it to NO and boot again then all is fine. Fully reproducible.
Can you do the same thing requested of Sean?
Set PNP OS: Yes in BIOS, enable debugging in
arch/i386/kernel/pci-i386.h, reboot, and post the 'dmesg' output.
--
Jeff Garzik | Only so many songs can be sung
Building 1024 | with two lips, two lungs, and one tongue.
MandrakeSoft | - nomeansno
prev parent reply other threads:[~2001-11-04 13:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-04 4:52 Via Onboard Audio - Round #2 Sean Middleditch
2001-11-04 5:03 ` Jeff Garzik
2001-11-04 5:30 ` Sean Middleditch
2001-11-04 13:45 ` Jeff Garzik
2001-11-04 13:48 ` Jeff Garzik
2001-11-04 16:09 ` Sean Middleditch
2001-11-05 3:34 ` Sean Middleditch
2001-11-04 13:20 ` Anton Altaparmakov
2001-11-04 13:44 ` Jeff Garzik
2001-11-04 13:54 ` Anton Altaparmakov
2001-11-04 13:56 ` Jeff Garzik [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=3BE548FA.DEC6C2B3@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=aia21@cam.ac.uk \
--cc=elanthis@awesomeplay.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox