trackrat Posted July 4, 2005 Report Share Posted July 4, 2005 Referring to a post I put on earlier.http://forums.neoplanet.co.uk/index.php?ac...82&t=19784&st=0I have found the fault to be the Programmable interrupt controller, what is this and where do I get drivers for it?. Quote Link to comment Share on other sites More sharing options...
-pops- Posted July 4, 2005 Report Share Posted July 4, 2005 I think this is a fundamental part of the motherboard and BIOS. Interrupts are to do with device allocation (as in IRQ = Interrupt ReQuest).So, if there's any chance of finding drivers (?) I think the place to look on the motherboard disk.I've a feeling that things aren't looking good here, though, sorry. Quote Link to comment Share on other sites More sharing options...
trackrat Posted July 4, 2005 Author Report Share Posted July 4, 2005 It is very strange, I reinstalled the mobo drivers and set the BIOS back to defaults and now in Device manager/system devices it is no longer listed.Tried running a live CD again and still got the same error.So it looks like the Dual boot ( XP & SuSe ) will be put on hold till I contact Abit technical services.What puzzles me is XP Home is running faultlessly. Quote Link to comment Share on other sites More sharing options...
korgg Posted July 4, 2005 Report Share Posted July 4, 2005 What I did when I encountered this kind of IRQ problem, was to see what devices use that IRQ... On an old Gigabyte 7VA there was the IDE controller, sound (on-board), network controller (on-board) and i think the video card were using the same IRQ (14)... This should be no problem in normal use, but a little play with a program written by me managed to destroy a partition totally... Oki.. IRQ's are of two kinds: maskable and un-maskable.The fisrt one means that two devices (or more) access that same IRQ they get along just fine. That kind of IRQ can be accessed by multiple devices.The un-maskable ones are the ones that cannot be shared at a given moment of time. An example is the one for floppy access. You may notice that when you write to a floppy the whole system is for a moment locked (unusable). On old computers this is more obious.Now if the PIC controller needs an un-maskable IRQ you may need a BIOS update. Normally the BIOS should know these things, but it seems they share sometimes un-maskble IRQ's. You could see what IRQ it uses and go into BIOS and set that IRQ to reserved. That solved my problem.Sorry if this might not be so correct, but it's quite long since I graduated :) Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.