Great, that's good help and a useful link As it turned out I did the most noob thing ever and was forgetting to type in -R so I had jackstart -v -d alsa -d hw:0 instead of jackstart -v -R -d alsa -d hw:0 It's 1:30am here and that's when I noticed. I typed it out wrong right from the onset and was using the consoles history to execute it. As a result I never noticed the absence of the -R! So now I have good recording power again but xmms still packs a sad. I'll try out the IRQ thing tomorrow (or is that today?) Thanks, everyone. Joe Hartley wrote: >On Sun, 26 Sep 2004 01:03:19 +1200 >Glenn McCord <clari_player@xxxxxxxxxxxxxxx> wrote: > > >>Is this good? >> >> > >No, it's not. > > > >>root@upstairs glenn # cat /proc/interrupts >> CPU0 >> 0: 16024 XT-PIC timer >> 1: 198 XT-PIC keyboard >> 2: 0 XT-PIC cascade >> 5: 4389 XT-PIC ICE1712 >> 8: 2 XT-PIC rtc >> 9: 0 XT-PIC acpi, usb-ohci, usb-ohci >> 11: 10635 XT-PIC eth0, nvidia >> 12: 6789 XT-PIC PS/2 Mouse >> 14: 10827 XT-PIC ide0 >> 15: 19 XT-PIC ide1 >> >> > >>From http://myweb.cableone.net/eviltwin69/Arcana.html#IRQs : > >Here's the order of interrupt priority on a non-APIC machine: > >0, 1, 8, 9, 10, 11, 12, 13, 14, 15, 3, 4, 5, 6, 7 > >0 is the highest priority >7 is the lowest priority > >5 is way down on the list, just about everything else has priority >over it. I have a Delta 1010, and rarely run into xruns. My IRQs are: > >xtc:~% cat /proc/interrupts > CPU0 > 0: 2947127195 XT-PIC timer > 1: 796739 XT-PIC keyboard > 2: 0 XT-PIC cascade > 8: 1 XT-PIC rtc > 9: 12759493 XT-PIC ICE1712 > 10: 195005487 XT-PIC eth0, nvidia > 12: 13312679 XT-PIC PS/2 Mouse > 14: 180887 XT-PIC ide0 > 15: 1987385 XT-PIC ide1 > >I've turned off the USB ports on my machine as well as acpi, which handles >OS-directed configuration and power management. > > >
