S Glasoe wrote:
On Monday 01 May 2006 11:35 am, Hylton Conacher (ZR1HPC) wrote:
S Glasoe wrote:
Moving eth0 to another PCI slot may change its IRQ but the system and OS may keep it at 5 anyway. Again, don't bother. Unless there is a known conflict you can actually 'prove' is happening because sound and eth0 are sharing an IRQ it doesn't matter. It used to matter about 10 years ago...
Tnx, Now I feel old as the knowledge I have is about 10-15yrs old.
I'll have a look at the BIOS but otherwise I hope it is not going to be problems.
Know exactly how that feels. How old is this hardware?..... Hardware is 3-4years old and motherboard has a single ISA slot, rest are PCI. Realtek NIC is in a PCI slot. Sound os on motherboard.
....You mention that it matters in Windows which IRQ is set so which version of Windows was that and was it running on this same hardware? Thankfully Windows has never touched this machine. I remembered it from the dark days waaay back.
You may have hardware and BIOS that require setting IRQs but that, in general, is going to be more than 6-8 years old.... 2001/11/03 date of purchase.
... Back in the day when ISA/EISA was transitioning to PCI, IRQ settings mattered because most add-in cards had hardware jumpers for IRQ. Had a look in the BIOS and didn't see specific settings for the sound IRQ and te networking IRQ. I did say that the BIOS must monitor the IRQ's, whatever that means as even after reboot the NIC and Sound still had the same IRQ.
PCI allowed those hardware settings to be put into firmware on the cards and the system/BIOS and discovered by operating systems so physical intervention and its risk of static electricity death could be avoided, conflicts over sharing of limited IRQs could be resolved via software, less labor intensive, more automation via operating system, etc.
In conclusion it would seem I have bad hardware but then the IRQ's being the same doesn't if I am not using the ISA slot, and Linux 9.2 right?