• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Intel 875P chipset and AGP Problem?????

M

MystiKal

Member
I was wondering if anyone has had a problem with the 875P chipset and conflicts in Windows XP/2k/2k3 with the Intel 82875P Processor to AGP Controller and the video card. The video card shows up in device manager with "Not enough resources available" and when I look at the I/O and Memory, the Intel 82875P Processor to AGP Controller shows up as I/O conflicts at: 03B0-03BB and 03C0-03DF and a Memory Conflict at: 000A0000-000BFFFF. I'm using the latest Intel chipset drivers as well. The video card I'm using is an ATI All-In-Wonder Radeon 8500. I even disabled everything onboard the motherboard including the IDE controllers hoping some resources would free up, but still nothing. Oh, I have a LSI MegaRAID Elite 1600 SCSI RAID controller, so disabling the IDE in the BIOS just turns off my CDROM. I searched google and I did find a posting in a forum that someone is having a similar problem on a different brand motherboard, although still an Intel 875P chipset, and a different brand video card. I contacted Gigabyte, my mobo brand, and they say the problem is not with the BIOS (eg, the BIOS assigning IRQs since XP, or ACPI, overrides the BIOS in terms of IRQs). If anyone had this problem, please let me know. I've reinstalled XP and 2k3 about 50 times already and still the same problem of the video card not having enough resources available. Below are the core parts of my setup that may help:

-Gigabyte GA-8KNXP mobo (Intel 875P chipset)
-Corsair XMS TwianX DDR 400 2x512MB matched
-ATI All-In-Wonder Radeon 8500 128MB
-LSI MegaRAID Elite 1600 SCSI RAID
-Quantum Atlas IV 72GB 10k U160
-Koolance water-cooled case (Had to mention that 😉
:|
 
The problem is obviously the SCSI RAID controller. Why don't you send that to me, and I'll trade you for a nice Adaptec 19160 😉

😀


Seriously, though... if you haven't done so already, try moving your RAID card to different PCI slots and see what happens. Gigabyte's manual doesn't seem to spill the beans on the IRQ-sharing assignments at the board level 🙁 but in times past, I've seen this make the difference, even though it shouldn't in theory.

You may also want to try disabling AGP 8X capability and Fast Writes. Good luck! 🙂
 
hehe...the LSI MegaRAID Elite 1600 with 128MB WB battery backed cache is fast!!!

But, yes, I did try every combination of PCI slots for the RAID controller and reinstalling XP in each slot. What I found is that in any pci slot other then the slot right next to the AGP slot, the BIOS assigns the Display Controller and the RAID controller the same IRQ of 11. But when I install the RAID controller in the PCI slot next to the AGP, the two cards are on different IRQs. But IRQs do not seem to be the problem since XP assigns the RAID controller to something like IRQ 22. It seems its a resource conflict with the I/O range and/or Memory range. What makes things even more weird is that I borrowed a GeForce 5600 and poped it in and everything worked all well. The AIW 8500 is a 4x AGP card so its already running in 4x mode. I'll try turning off AGP Fast Write to see if that is the cause, but I'd like to have AGP fast write enabled in the long run. I emailed Intel, Gigabyte and ATI for support on this problem. I'm hoping its something with the chipset drivers since someone else is having the same problem with a different brand mobo and video. But if anyone has/had this problem...please explain
 
yes...I installed the lastest Intel chipset drivers everytime I reinstalled. I'm still going crazy over this problem
 
I figured out the problem. After a lot of searching and reading on google about BIOS settings, it turned out the AGP Apeture Soze setting was to blame. The mobo was defaulted to 128MB. Te general rule is to have at least twice the RAM on your video card for the AGP Apeture size. I changed it to 256MB and everything worked perfectly. It turns out that the 128MB setting just so happened to reserve RAM where the RAID BIOS installed itself. So when the AGP bus went to install in its memory range, it found something there already. I also tested with 64MB AGP Apeture size as well, and it worked too. But given I have 1gig of ram, I decided to go with the 256MB AGP Apeture setting.
 
I was just wondering, why even install the raid controller when your Gigabyte 8KNXP already has a faster on board integrated raid controller for both SATA and IDE? You could avoid the slow PCI slot alltogether.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top