I recently bought a new video card (a whole new set up, actually) and now am trying to install my old AGP card into my brother's machine. My brother's motherboard is the same as my old one, for the record.
He currently has an OLD GeForce MX400 AGP card installed in his machine. He also has a PCI SATA controller card, which his one and only hard drive uses. When I remove his old video card and replace it with my old card (GeForce 6600GT), suddenly I get a PnP/PCI checksum ROM error on the SATA controller card -- nothing I've done has been able to remedy it. We've tried checking every single BIOS setting, flashing the BIOS, everything. Something must be escaping me.
A couple of people said it may be an IRQ conflict, but isn't the IRQ assigned to the AGP bus itself? In that case, wouldn't his previous AGP card give the same error? Once I replace my old card with his previous MX400, it boots fine. Anyone have any idea what the problem might be?
I'm looking for explanation of the problem, specifically. I'm not looking for "try reinstalling windows" or anything like that -- I'm hoping someone knows what's going on and can explain in detail why this is happening. Thanks!
ID:182885
 Jan 4 2008, 1:55 pm
|
|
Alathon wrote:
IRQ's will be shuffled around by Windows. Some IRQs are pretty static though (system timer, math co-processor, etc). I was pretty sure that bus IRQs were just as static. You missed out some rather important information; what motherboard is it? Well that doesn't really come into play in this particular case -- his motherboard is the same as my old one (the one I used with the mentioned video card), so that shouldn't be a problem. Older motherboards share an interrupt code between the AGP slot and the PCI slot closest to it. We've tried moving the controller card to the other PCI slots with no luck, unfortunately. However, given the circumstance, I'd be willing to bet this is Windows doing - You can check for that conflict yourself. You can see each devices IRQ information in Windows, and see where the conflict is occuring. The thing is we can't get into windows with the new card, so we can't see what IRQ it's using (if it is indeed changing the IRQ when we install the new card) to compare it to other resources to see where the conflict is. Thanks for the reply, we appreciate it. | |
Try firing up a Linux live-CD, just to check whether this is Windows causing the conflict or something else.
The reason I asked for more specific details, is that I was planning to ask a co-worker tomorrow about this - And the first thing he'll ask is what exact components. Would've also been nice with the exact error message provided ;) It wasn't clear whether this was a POST error, or a Windows error either. That changes things somewhat. | |
You missed out some rather important information; what motherboard is it?
Older motherboards share an interrupt code between the AGP slot and the PCI slot closest to it.
However, given the circumstance, I'd be willing to bet this is Windows doing - You can check for that conflict yourself. You can see each devices IRQ information in Windows, and see where the conflict is occuring.