Mailinglist Archive: opensuse (5130 mails)

< Previous Next >
Re: [SLE] Changing hardware IRQ's
  • From: S Glasoe <srglasoe@xxxxxxxxxxx>
  • Date: Mon, 1 May 2006 14:19:00 -0500
  • Message-id: <200605011419.00555.srglasoe@xxxxxxxxxxx>
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? 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? You may have hardware and BIOS
that require setting IRQs but that, in general, is going to be more than
6-8 years old. Back in the day when ISA/EISA was transitioning to PCI, IRQ
settings mattered because most add-in cards had hardware jumpers for 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.


< Previous Next >