2014-10-20, 20:37
(2014-10-18, 23:47)Milhouse Wrote:(2014-10-18, 13:48)slomovizion Wrote: I can reliably get the digi to work again by downgrading to #1006. Has anybody else come across this problem?
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
I included that bit to indicate that I don't think my issues are due to a shoddy soldering job (which btw wouldn't be unlikely - I'm an economist by trade and soldering the connector to the rpi was the first time I've soldered anything to anything).
(2014-10-18, 23:47)Milhouse Wrote: Just an idea, could you boot a #1006 system with the start.elf firmware from #1007 and see if it has any effect:
1. Copy #1007 tar to Update folder, boot into #1007
2. cp /flash/start.elf /storage
3. Copy #1006 tar to Update folder, boot into #1006
4. mount -o remount,rw /flash
5. cp /storage/start.elf /flash
6. mount -o remount,ro /flash
7. reboot
8. Confirm if Hifiberry hardware becomes "unreliable", or not.
I tried the above. Both my rpi and the digi works as normal when I boot into the 'hybrid'. But I'm not really sure what to do / test with this combination? And is it correct that the output from "uname -a" should still say that I'm running #1006, ie.:
Code:
OpenELEC:~ # uname -a
Linux OpenELEC 3.16.3 #1 PREEMPT Mon Oct 6 21:27:26 BST 2014 armv6l GNU/Linux
Anyways, output from dmesg & lsmod follows below:
dmesg: http://sprunge.us/DDIO
lsmod: http://sprunge.us/BCjU
Best regards