Mailinglist Archive: opensuse (5130 mails)

< Previous Next >
Re: [SLE] Changing hardware IRQ's
  • From: "Hylton Conacher (ZR1HPC)" <hylton@xxxxxxxxxxxx>
  • Date: Sun, 07 May 2006 14:03:03 +0200
  • Message-id: <445DE1F7.8080305@xxxxxxxxxxxx>
S Glasoe wrote:
On Friday 05 May 2006 1:29 pm, Hylton Conacher (ZR1HPC) wrote:

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.

Nothing in the ISA slot?
Nope nothing.

I would _guess_ that the BIOS would reserve an IRQ for the ISA slot once it knows what IRQ the ISA card wants/has/requires. That may be the only IRQ action this BIOS does.

2001/11/03 date of purchase.

New enough. Having the ISA slot is something. Once the system knows which IRQ the ISA slot/card has then I'd guess that all PCI slots and devices would share the remaining IRQs.
I'd follow that thinking too except that I do not know what IRQ is allocated to the ISA slot, nor do I care to use, or have the means to use the ISA slot.

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.

Standard PCI, BIOS, IRQ interaction.

<snip>

I'd say it wasn't bad hardware. You just haven't figured out the unique challenge presented by this combination of hardware, BIOS and PCI cards. Newer Linux versions will help.
mmm, I figured this too. Waiting for 10.1 to be officially released ie not RC, mentioned on the list a bit, and I probably get it a month or so after release, depending on postage.


I keep coming back to one of my first questions though. Think there has been 3 different threads based on IRQ settings. Can't keep them straight anymore. Does it matter if your devices share an IRQ? Or are you just fixated on trying to get each PCI or onboard device _not_ to share an IRQ? I know you may be getting an error message stating something about unknown parameters (IRQ being one of them) when loading a driver but my experience tells me that is just an old generic error message that can't be more specific. Its giving you a hint as to what to troubleshoot.
Oooh, time for the deeep stuff :)
I am more fixated on getting each device to have a single IRQ as I seem to remember from my past that having the same IRQ, on a Windows system anyway, would render either one or both of the devices inoperable ie they cannot both have the same request number to query the cpu.

Whilst I realise it probably doesn't matter on Linux and that a newer version would help and that it seems that both the network card and sound are basically operating, although not fantastically, there must be something in this IRQ thing as cpu's have not changed their operating habits since Linux arrived, I don't think?

I know its thinking outside of the box but it is interesting.


< Previous Next >
Follow Ups