@flysurfer... I'm trying to determine if this bug affects the kernel in use within Max2play: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1136110?comments=all
uname -a returns "Linux max2play 3.8.13.23" which seems to be within the range of affected versions: -2) The version of the package used linux-image-3.5.0-26-generic linux-image-3.5.7-03050706-generic_3.5.7-03050706.201302221435_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.7.6-quantal/ linux-image-3.7.7-030707-generic_3.7.7-030707.201302111436_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7.7-raring/ linux-image-3.8.0-030800rc7-generic_3.8.0-030800rc7.201302081635_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc7-raring/ This bug had been confirmed appearing after the following kernel upgrade step: v3.5.0-25 > v3.5.0-26 ~ v3.5.0-27 v3.5.7.5 > v3.5.7.6 ~ v3.5.7.8 v3.7.6 > v3.7.7 ~ v3.7.10 v3.8.0-rc6 > v3.8.0-rc7 ~ v3.8.5 The v3.9 branch has been affected since its very first release. v3.9-rc1, v3.9-rc2, v3.9-rc3 v3.9-rc4 are all affected. - Although I could very easily be wrong.... There is a patch for the asynchronous DAC @ 96khz issue, but I'm extremely reluctant to meddle with this. Thanks, Jason ------------------------------------------------------------------------ doctor_big's Profile: http://forums.slimdevices.com/member.php?userid=15196 View this thread: http://forums.slimdevices.com/showthread.php?t=101856 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
