From: Peter Buckingham <peter@pantasys.com>
To: "Hodle, Brian" <BHodle@harcroschem.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: FW: PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped
Date: Tue, 21 Jun 2005 11:41:05 -0700 [thread overview]
Message-ID: <42B85F41.3030009@pantasys.com> (raw)
In-Reply-To: <D9A1161581BD7541BC59D143B4A06294021FAA68@KCDC1>
Hi Brian,
Hodle, Brian wrote:
> I am experiencing exactly the same problem. I am using an ASUS
> K8N-DL MB with the x86_64 kernel. My PCIX devices are not allocated
> correctly. I tried using the 'pci=routeirq' option to no avail. Disabling
> ACPI in the BIOS does not help the situation either. X will not use my PCIX
> for GLX since none of the extra txture memory has been allocated! Anyone
> have any ideas?
well my system is using PCIe instead so it's a little different. It
seems that the PCIe fixups are enough to get the BAR regions assigned
correctly. prior to loading the nvidia driver the BARs are listed as
disabled in lspci -vvx, but after loading the BARs are not disabled and
I am able run X on both GPUs fine. I haven't tried running any OpenGL
type tests yet on the system.
pci=routeirq is a red herring, this is about the interrupts and
shouldn't affect the bar allocation.
it might be useful for you to post a dmesg with PCI_DEBUG enabled and
specify which kernel version you are using. My system only worked with
the most recent 2.6.12 (but i think that's due to some of the pci
express changes and some of the bridge handling since our system is a
little unique...)
peter
next prev parent reply other threads:[~2005-06-21 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 13:58 FW: PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped Hodle, Brian
2005-06-21 18:41 ` Peter Buckingham [this message]
2005-06-25 19:40 ` Karim Yaghmour
[not found] ` <1119729766.9540.0.camel@oscar.metro1.com>
2005-06-25 20:05 ` Sean Bruno
2005-06-25 21:07 ` Karim Yaghmour
2005-06-26 18:09 ` Sean Bruno
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=42B85F41.3030009@pantasys.com \
--to=peter@pantasys.com \
--cc=BHodle@harcroschem.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