Darren Pilgrim wrote:
I believe the IEEE was involved. :)
That explains a lot :)
IRQ sharing is a known issue with many RAID cards and even some gigabit
ethernet cards. It seems to correlate to cards that push the
performance limit of the bus.
And here I am with both a RAID card and a giga
From: Brandon Fosdick [mailto:[EMAIL PROTECTED]
>
> Darren Pilgrim wrote:
> > Try switching slots with the RAID and video cards. It's silly, but
> > then so is PCI interrupt routing.
>
> Unbelievable. Who ever wrote the PCI spec should have been shot.
I believe the IEEE was involved. :)
> I
Darren Pilgrim wrote:
Try switching slots with the RAID and video cards. It's silly, but then
so is PCI interrupt routing.
Unbelievable. Who ever wrote the PCI spec should have been shot.
I switched the cards and now the network card is sharing an interrupt with the
video card, but neither s
Mike Jakubik wrote:
Forgot to mention. You can always buy a cheap pciE video card :)
You're a big help :)
I was fiddling and I noticed something odd. Previously, the ESCD screen at boot
showed the raid controller and network controller both at IRQ 5. The dmesg I
sent before showed both at IR
From: Brandon Fosdick
> Mike Jakubik wrote:
> >
> > The easiest thing would probably be to disable the onboard
> > sk card, and put in an em (intel gigabit card). The marvell
> > chipset and driver is known to be problematic.
>
> I had thought of that, but the motherboard only has 2
> non-express
On Sun, August 14, 2005 12:47 am, Brandon Fosdick said:
> I had thought of that, but the motherboard only has 2 non-express PCI
> slots and they're both currently filled by the video card and the raid
> card. I could take the video card out, but then I wouldn't be able to see
> what I was doing.
On Sun, August 14, 2005 12:47 am, Brandon Fosdick said:
> I had thought of that, but the motherboard only has 2 non-express PCI
> slots and they're both currently filled by the video card and the raid
> card. I could take the video card out, but then I wouldn't be able to see
> what I was doing.
Mike Jakubik wrote:
The easiest thing would probably be to disable the onboard sk card, and
put in an em (intel gigabit card). The marvell chipset and driver is known
to be problematic.
I had thought of that, but the motherboard only has 2 non-express PCI slots and
they're both currently fille
On Sat, August 13, 2005 8:02 pm, Brandon Fosdick said:
> So I'm having yet another problem with my AMD64x2/nforce4 system. Of the
> two builtin NICs 5.4-S is only recognizing the marvell gigabit chip,
> which wasn't a problem until I added a 3ware 9500S-12. With the 3ware
> card in the network does
