Andrea Bondavalli

> Can someone point me to a tutorial? in general it depends on the distro you are using if they offer some easy way to change kernel. For example for...

I did some more tests and the XRUN issue starts from kernel 5.10.0 on. The issue happens for both X86 and ARM platforms. For this reason, for the time being,...

> Thanks, my problem is that is not working for the Raspberry Pi. No grub, for one. Nm, I'll get around it. yes, usually on ARM boards in addition to...

The problem reproduces on multiple audio cards by using the original latency application in alsa-lib. So it doesn't seem to be related to the RAVENNA driver.

[perexg](https://github.com/perexg) commented [11 minutes ago](https://github.com/alsa-project/alsa-lib/issues/285#issuecomment-1325538172) >I think that I found the upstream change between 5.9 and 5.10 kernels in the scheduler which causes this behavior: >https://lore.kernel.org/lkml/c596a06773658d976fb839e02843a459ed4c2edf.1479204252.git.bristot@redhat.com/ >See the patch description....

I will run some more tests and add this setting to the documentation and scripts. On kernel >= 5.10.x use the following setting to restore old kernel scheduler behaviour: `sysctl...

@MichalBury can you checkout branch i[issue-79](https://github.com/bondagit/aes67-linux-daemon/tree/issue-79) and verify if the latency test works for you ?

I didn't elaborate such a list. I created the project for fun and I own just a bunch of devices. The devices I tested personally are in the DEVICES.md document....

Apparently no one has ever tested with this device. Since it looks like it's compatible with Dante you can give it a try ;-)

The daemon is not limited to 48Khz but the sample rate configuration is a global setting. Since the driver does not perform any sample rate conversion once a rate is...