2014-10-20, 20:51
(2014-10-20, 20:37)slomovizion Wrote:(2014-10-18, 23:47)Milhouse Wrote: Can you explain exactly what the problem is? You say it's not "reliable" - does this mean it's working some of the time? What is the output of "aplay -l"? Is the Hifiberry visible to XBMC, or not? If it is, how is it not reliable?
Sorry for being unclear - what I meant was, that I've tested every build since #1006 (fingers crossed) to see whether my issue would disappear (which it hasn't) and that the digi would resume working as normal when I downgraded to #1006 again. So not really the digi being unreliable as much as me being able to get it to work again every time
Can you provide the output of "aplay -l" when using the #1007 build (not the hybrid build) although I'm pretty sure you won't get anything output.
The fact the "hybrid" (#1006 with #1007 firmware) works suggests that it's not a firmware issue. What would be useful to know is whether the OS "sees" the hardware, hence the output of aplay.
The Wolfson commits have now been dropped from the 3.17.y kernel which should remove one more variable from the kernel that might explain the Hifiberry breakage. If the next build doesn't improve the situation you might need to contact Hifiberry for support as they may need to supply updates for the 3.17 kernel, or give some clues as to what kernel config options are required by their driver(s).
