From: David Riley <oscar@the-rileys.net>
To: linux-kernel@vger.kernel.org
Subject: Bus mastering troubles with AGP Voodoo3
Date: Thu, 22 Feb 2001 21:52:14 -0500 [thread overview]
Message-ID: <3A95D05E.43DBBB73@the-rileys.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
I knew my performance hit had to be coming from somewhere...
I'm using an MSI K7T Pro mtherboard (KT133 chipset) and a Voodoo3 2000.
I can't seem to set bus mastering on the AGP card at all. This does not
work:
setpci -s 01:00.0 4.w=0007 (setpci -s 01:00.0 4.w gives me 0003)
Nor does:
setpci -s 01:00.0 COMMAND=0007
No permutation of this works. No error messages are returned, but the
register remains unchanged at 3. I have tried using -H1 and -H2, to no
avail (-H2 doesn't even get there, complaining about something on the
normal PCI bus). I have tried this with the BIOS set on "PnP OS" and
off, with no difference. My guess is that this is a motherboard
specific problem (broken BIOS, anyone), though I don't think I've heard
of a broken BIOS causing unwriteable PCI config registers. For what
it's worth, I've attached the output of 'lspci -vv -s 0:1.0' (the AGP
host bridge) and 'lspci -vv -s 1:0.0' (the card).
Thanks for any help you may have...
[-- Attachment #2: foobar --]
[-- Type: text/plain, Size: 1237 bytes --]
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: d0000000-d3ffffff
Prefetchable memory behind bridge: d4000000-d5ffffff
BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
Capabilities: <available only to root>
01:00.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo 3 (rev 01) (prog-if 00 [VGA])
Subsystem: 3Dfx Interactive, Inc. Voodoo3 AGP
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR+
Interrupt: pin A routed to IRQ 9
Region 0: Memory at d0000000 (32-bit, non-prefetchable) [size=32M]
Region 1: Memory at d4000000 (32-bit, prefetchable) [size=32M]
Region 2: I/O ports at c000 [size=256]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: <available only to root>
reply other threads:[~2001-02-23 2:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3A95D05E.43DBBB73@the-rileys.net \
--to=oscar@the-rileys.net \
--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
all inboxes | Powered by JetHome®