This is a part of my lspci -v output:
00:0a.0 Multimedia audio controller: VIA Technologies Inc. ICE1712 [Envy24] PCI Multi-Channel I/O Controller (rev 02)
Subsystem: VIA Technologies Inc. M-Audio Delta Audiophile
Flags: bus master, medium devsel, latency 32, IRQ 177
I/O ports at d800 [size=32]
I/O ports at d400 [size=16]
I/O ports at d000 [size=16]
I/O ports at b800 [size=64]
Capabilities: [80] Power Management version 1
00:0d.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) (prog-if 10 [OHCI])
Subsystem: VIA Technologies, Inc. IEEE 1394 Host Controller
Flags: bus master, stepping, medium devsel, latency 32, IRQ 177
Memory at dd800000 (32-bit, non-prefetchable) [size=2K]
I/O ports at b400 [size=128]
Capabilities: [50] Power Management version 2
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5500] (rev a1) (prog-if 00 [VGA])
Flags: bus master, 66MHz, medium devsel, latency 248, IRQ 177
Memory at de000000 (32-bit, non-prefetchable) [size=16M]
Memory at e0000000 (32-bit, prefetchable) [size=256M]
[virtual] Expansion ROM at dffe0000 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Capabilities: [44] AGP version 3.0
Wow three hardware using the same IRQ. I thing that explains why i'm hearing a very deep "swizzzz" sound when i maximize or minimize any window. The same occurs when any visual plugins of Amarok or other applications work. Graphics and sound cars are on the same IRQ.
Any way of changing this IRQ settings ?
My kernel version is 2.6.18.8-86 so it's not this HELL thing. I'm glad.
I'll check for the IRQ and PCI then.
Thanks.On Feb 16, 2008 11:42 PM, James Stone <jamesmstone@gmail.com> wrote:
Thanks for the heads up.. This is clearly not an issue then..On Sat, Feb 16, 2008 at 04:30:36PM -0500, Paul Davis wrote:
>
> On Sat, 2008-02-16 at 21:27 +0000, James Stone wrote:
> > am not sure about your distro but you may also be affected by
> > "nptl hell", in which case I would suggest changing distro:
>
> NPTL Hell affects only 2.4 kernels or very very early 2.6 kernels. It is
> not and has never been an issue in distributions using kernels from the
> last 2 years or so.
>
The other thing I forgot to note was the pci latency settings. On
my system I have been using a script I got from this mailing
list (was it yours Paul?):
#!/bin/sh
case $1 in
start)
# "open up" the PCI bus by allowing fairly long bursts for
all devices, increasing performance
setpci -v -s "*:*.*" latency_timer=b0
# maximise latency for SBLive!, thus allowing
# more data per PCI transfer and minimizing xfuns
setpci -v -s 01:0a.0 latency_timer=ff
esac
exit 0
obviously requiring altering 01:0a.0 to match the results of lspci -v for the
soundcard in your system.
James--
Arda EDEN
Cumhuriyet University
Faculty of Fine Arts
Department of Music Technology