Does anything look wrong with this that would case IRQ conflicts/routing table errors?
- From: jonfaquit@xxxxxxxxx
- Date: 28 Mar 2006 13:08:04 -0800
I have an ATI Rage Mobility PCI card that, on POST, gives a "IRQ
Routing Table Error [00:05:00]" and video is terribly slow (I'm not a
gamer so slow for me = "super super" slow for you gamers out there).
Matter of fact I can't even install Windows 2k (tells me BIOS Is not
ACPI compliant). Windows XP installs fine but video is pretty much the
same (horrible). It's like I can see the video card painting scanline
by scanline like I was downloading a jpeg & displaying it as it came on
a dialup connection. CPU utilization also runs up 70-90% when scrolling
a simple window.
My system is Debian 3.1 Sarge, AMD64 Athlon, MSI K8T Neo-V (MS-7032),
AMI BIOS, VIA K8T800/VT8237 chipset.
I never had a problem with this card on my normal 32bit Athlon so I'm
hoping it's not a 64-bit compatibility issue (I've dismissed the idea
of going x86-64 linux or x64 Windows).
More useless info here about the mobo:
http://www.msicomputer.com/product/p_spec.asp?model=K8T_Neo-V&class=mb
But with the following lspci on that specific bus/slot (0:05), does
anything look wrong that would cause an irq routing table error, make
windows or any other OS believe the bios isn't ACPI compliant (even
though the mobo link says "ACPI & PC2001 compliant enhanced power
management"), and cause the video to be very crappy? If you want the
full lspci, let me know - cause I wouldn't wanna read pages & pages of
nonrelevant data.
My main questions:
1) Why does it say AGP when this is a PCI card?
2) pin A routed to IRQ 0? Is that normal? I thought IRQ 0 was the
timer?
# lspci -vvv -s 0:05.0
0000:00:05.0 VGA compatible controller: ATI Technologies Inc Rage
Mobility P/M AGP 2x (rev 64) (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc Rage Mobility P/M AGP 2x
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: 64 (2000ns min), Cache Line Size: 0x10 (64 bytes)
Interrupt: pin A routed to IRQ 0
Region 0: Memory at fd000000 (32-bit, non-prefetchable)
[size=16M]
Region 1: I/O ports at e800 [size=256]
Region 2: Memory at febff000 (32-bit, non-prefetchable)
[size=4K]
Expansion ROM at febc0000 [disabled] [size=128K]
Capabilities: [50] AGP version 1.0
Status: RQ=256 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64-
HTrans- 64bit- FW- AGP3- Rate=x1,x2
Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit-
FW- Rate=<none>
Capabilities: [5c] Power Management version 1
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
.
- Follow-Ups:
- Prev by Date: Re: please critique these two Athlon X2 3800+ configs
- Next by Date: Re: Does anything look wrong with this that would case IRQ conflicts/routing table errors?
- Previous by thread: DataTraveler + RH9 = trouble
- Next by thread: Re: Does anything look wrong with this that would case IRQ conflicts/routing table errors?
- Index(es):
Relevant Pages
|
