Am Tue, 18 Sep 2012 12:50:32 +0200
schrieb Thomas Orgis :
> And, having read up a bit ... AHCI seems to be known to cause audio
> issues
I must admit that the box seems to be stable now. And it is always
using AHCI enforced via kernel, regardless of BIOS setting. So that is
ruled out as source o
Am Tue, 18 Sep 2012 12:37:21 +0200
schrieb Ralf Mardorf :
> > Change the config to
> > RTIRQ_NAME_LIST="rtc [and add anything as it was before, excepted of a
> > second rtc entry]"
>
> PS: After editing the config stop and start might not do the job and a
> reboot could be required
No biggie .
> I'm short in time and can't read your email right now, so I only take a
> look at the output of rtirq status.
> Usually you can't do anything against the shared IRQ, however it's ok,
> since firewire and snd_hda are head of the IRQs. But the first IRQ,
> before firewire has to be the timer rtc0.
On Tue, 2012-09-18 at 11:39 +0200, Thomas Orgis wrote:
> rtirq:
>
> PID CLS RTPRIO NI PRI %CPU STAT COMMAND
> 302 FF 90 - 130 0.6 Sirq/18-firewire
> 994 FF 83 - 123 0.0 Sirq/16-snd_hda_
>84 FF 80 - 120 0.0 Sirq/17-ehci_hcd
>
Am Mon, 17 Sep 2012 15:30:49 +0200
schrieb Thomas Orgis :
> > Please post the output of
> > $ /etc/init.d/rtirq status
>
> Will try to get to that tonight.
Well ... this is interesting. I tried AVLinux and this also showed
massive xruns, with the added twist of ffado giving up on the device
aft
Am Mon, 17 Sep 2012 15:15:58 +0200
schrieb Ralf Mardorf :
> PS: CPU frequency scaling?
I noted that it is independent of that. I switched to 'performance'
governor and nothing changed. Also, my experience with working setups
is that frequency scaling does not matter to them. That might be
except
PS: CPU frequency scaling?
--
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Hi,
the subject says it all ... I had an install of 10.04 that worked. Only
issue seemed to be instability when recording while a USB drive is
connected. So, considering that perhaps this is a sign to replace a
mainboard with broken onboard USB (used a PCI add-on card, which might
have worsened th