ok allot of you know that i have been having problems well i have found out that my pci-e controler my 6800unltra, intell host controler something, my realtek giga bit eathernet nic and my realked HD audio codes are all on irc 16 under confics and sharing, you where right then, i guess so what u are saying here is that reinstall windows will fix these conficts and reset irqs?
what operating system are you using? there is a option in the bios that lets the bios handle the irq and dma settings or let the os handle it.
i am using windows 2k where do i find this setting in the bios and if i do set it to that will it ummm un fuk my irq's????? plz further egicate my about this, im sorta a noob on this topic
i have no idea but its in my bios under advanced settings. it might be different for yours. i 'm really tired to the point i can barely type sorry, been up since 5am
any1 else that isnt tired (no offence) ok i want to know if i set it to bios will it become more fubared (beause there allready fubard) or will it just ezly fix them and i get on with my life also plz tell me more about this topic if you can...
well win2k is a plug and play os (i think). setting it to bios wouldnt have a negative effect that you wont be able to reservse so i say go ahead and do it. just set the irq to be handle by the bios.
ok...if it ****'s my system its your head!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! jk or am i??? ok ill do that but i need 1 more person to give me the ok so i can 100% ahhem i mean 58% sure that i can do this if i do this then both windows and the BIOS will be fighting over IRQ handaling is the gona be a problem????
well if its your audio and ethernet that are on the same irq there should be no problem with the gfx card, but other then that if you go into your my computer > proporties there should be a hardware configuration so you can choose irq addresses for the different pieces of hardware. i would suggest useing 9 or 1 if their open. but if anyone knows more feel free to elaborate.
ummm my IRQ's are messed up and your telling me there fine when ive been haveing all sorts of problems!!!!!!!! no i dont know all the IRQ stuff i just wish there was a tool that could untange this mess for me
IRQ's im haveing problems with mine, plz dont tell me that the current line 16 is fine beacuse simply ITS NOT, beause IM HAVEING problems thank you i just wanted to get that out edit: sry dont take this personal. its late ive been woking on this problem for a long time i just want to know if it tell the bios to set the irqs is it gona see the confitcs and fix them or is it gona just messthem up more or leave them the same, im tierd i want to relax but i cant beause i have this problem. i know there is someone here who has the answer
In win2k and XP it shouldnt matter if they are all on the same IRQ (and they commonly are) XP and 2k use interupt sharing. Its perfecty normal.
ok ppl plz dont post stuff like its normal and its ok, can you just try to answer the questions im asking im getting really pissed now beacuse im haveing a problem and every1ns telling me its fine, but as you can see its not
ok is no ones gona help then i guess gona format my drive the only person who help told me to do that....................
javaboy, I think you need to learn to chill out. You've repeat posted enough in here already - replying to your own posts with a 4minute gap in between. Thats annoying enough to make people that know their IRQ stuff to not post! Really, you're just coming across as being nasty, people are trying to help, but think of it logically - if you change a setting in the bios and windows doesnt work - change it back and it will be fine. Now my 2 cents - Back everything you need to up. Set the bios so that IRQs are controlled and set by Bios. Format. Install Windows (preferably XP). Enjoy a working system. And if you dare reply back saying you're going to hang me or something if it goes wrong, then fcuk you, you take a risk - but you wont end up with a worse performing system than the currently buggered one youve got now!
lol....sry yes im gona ummmmmmmmm...let see............. ok the bios is like preconfigured for that(i juse noticed when i went in this morning), so i guess all i have to do now is format ok when its done ill let you all know how it went
The whole idea of IRQ conflicts is a dead and gone era, unless you have an ISA or EISA bus. PCI, PCI-X, and PCI-E are all DESIGNED to share interrupts. Its nice if they don’t HAVE to share interrupts, its even preferred, but every ad-on device, your sound card, video card, NIC, if they are PCI devices, they can share interrupts WITHOUT A DISASTEROUS effect. It is all up to the design of the MoBo in question. More likely, if there is a REAL IRQ problem, its because the BIOS is reporting an incorrect IRQ mapping or something similar to that (the OS gets IRQ routing information from the BIOS in all x86 cases). This, however, is completely different thing than an IRQ conflict. IRQ conflicts happened with ISA devices simply because IBM had no idea their system would be so wildly popular. It was designed to have a market life of 5 years at the most (what its at now 23 years?). Ergo, they didn’t realize there would be so many devices that would be created for the ISA bus. They assumed 3-4 IRQ lines would be plenty and the ISA bus was designed in a simple/cheap fashion to handle that situation. So, when people designed some ISA device, they may have it fixed to use a specific IRQ or have a jumper so you could set it between 2-3 IRQ settings. There was no way for the devices (or the system at large) to know if two or more devices where on the same IRQ. If then, say there were two cards trying to use the same IRQ, the one who answered the interrupt first would get control and all other devices on that IRQ would be ignored. This is where an IRQ conflict comes from. PCI is a completely different design. It doesn’t mind if everyone is on the same IRQ. If one or more devices are on the same IRQ, the only issue might be performance. That is, two important parts of the PCI specification is an IRQ map and the PCI host controller (which is programmable as to how interrupts are distributed). The map merely specifies which devices (or PCI slots) are assigned to each specific IRQ trace. This trace can go to up to 32 devices (the bus is limited to 32 devices per bus). So a device can be on the trace alone or share it with 32 other devices, the system doesn’t care. The performance issue comes in because what will happen is the system will poll every device on the specified trace and ask it if it needs attention (ask if it has an interrupt that needs servicing). This can create a lot of extra work especially if the last device checked is the one causing the most interrupts. So these shared interrupts are not the same as an interrupt conflict as you could find with an ISA device. They are just shared interrupts to allow a person to add more than 3 devices to the system. Additionally, the PCI host controller (as I mentioned earlier) can be programmed to dole out (assign) a different system IRQ to each PCI IRQ trace (otherwise known as a PIRQ). Thus, say you have 4 PCI devices and two are using the same PIRQ trace and the other two are using different PIRQ traces (A, A, B, and C respectively). If there are 4 IRQ available, the first two devices will still get the same IRQ assignment because they are physically using the same PIRQ (A in this case). So the hub could assign A= IRQ 10, B= IRQ 13, C= IRQ 9. In that case, the first two devices are going to share IRQ 10. But maybe, all the IRQ’s have been assigned to other devices (like the keyboard controller which is not a PCI device). The host controller may only have one IRQ to dole out, so in that case it will simply assign a= IRQ 10, b= IRQ 10, C= IRQ 10 – and obviously all four devices will have to share the same interrupt (which is a performance issue, but not a stability issue). Now what CAN happen with PCI is the map can be wrong or the host controller may be misinformed as to the available IRQ’s it can assign to PIRQ’s. This can only be fixed with a BIOS update from the manufacturer. However, I would suspect that you just have a faulty device driver. The thing to do is remove the devices, add them back one at a time and see if the problems go away and when they come back. At any rate, there is no question that you do NOT have an IRQ conflict. That is just a misunderstanding.
ok so pull them out and turn it on or pull them out and put them back ina turn it on? 1 more thing, this started happaning when i pullled out a gfx and put a new 1 that i got for xmas back in
