Posts by g7ruh


    In case anyone wonders why there is no 7.90.010 build for Slice yet .. I have a cmake build issue with Kodi when patching support for the LED driver, and due to me being on the wrong continent doing family stuff for Christmas I don't have lots of time to spend looking at it.


    chewitt
    Family is way more important than .010 build issues (and my issue mentioned above), enjoy the break. I am sure folks will agree. BTW which continent are you on? Idle curiosity makes me wonder which one is wrong :D . If you are anywhere hot and sunny, maybe you need a re-think, (hot + sunny) != wrong :cool: Here on the south coast of England it is blustery and wet at present.


    Seasons Greetings
    Roger


    v7.90.009 is released.


    hi chewitt


    I think I may have managed to break this build. (that is what beta testing is for :D )


    Envionment is Slice running build .009 NTFS HDD WD Blue 1TB keyboard and mouse USB attached
    Music Library has about 715 items, alll FLAC from CDs which equates to 10757 tracks.


    The same fault exists in build .008 as I retested there too.


    I can crash this build every time if I do the following


    1) select CD to play (plays as expected)
    2) save playlist from blade works fine and carries on playing


    1) select CD to play (plays as expected)
    2) select CD to queue
    3) save playlist from blade works fine and carries on playing


    1) select CD to play (plays as expected)
    2) select CD to queue
    3) select CD to queue
    4) save playlist from blade, after entering name to save and 'OK' music still playing
    then pop up window appears "Scanning media info" and then disappears and a few
    seconds later: Slice reboots.


    Playlists are saved correctly.


    Alternate failure scenario:
    Go to music/playlists screen and select a playlist to play:
    Load playlists (created as above) 1,2,3,4 and 5 CDs in a playlist work fine and can select playlist from blade OK
    Load a playlist with 6 CDs (113 items in list), plays fine but when select playlist in blade I see the "scanning meda info" popup and it reboots.


    Happy to provide more testing as needed


    Roger

    Code
    1. Dec 07 11:12:01 nkdslice sh[1675]: dispmanx_vncserver: error while loading shared libraries: libssl.so.38: cannot open shared object file: No such file or directory


    Make sure your LE repository is up to date (force an update by clicking on "Check for updates" in the blade menu within the add-ons browser) and that you are then able to download 8.1.102.


    Milhouse,


    thanks, if you saw my earlier reply, I was wrong, I did the update on the earlier version so no wonder I was confused. ( have a bad head cold at present so I blame that!)


    Anyway, yes it works as you suggested, no need to reinstall the add-on, just did a manual update and it works fine again.


    thanks and kudos to you


    Roger
    [hr]
    hi Chewitt


    I have now loaded .009 and testing on my audio system, thanks to milhouse for helping get VNC working.


    I am impressed with the way Chorus 2 has matured, my reason for using VNC was to select music for playing, as the Slice is headless. I could not get on with any of the web based interfaces, they did not do what I wanted or were very slow (or both!). I tried early version of Chorus 2, it was OK and the best so far to that point but still slow. I suspect that the underlying slowness was caused by the earlier versions of Libre / Kodi. In the current version it is fast and is now on my list for further testing with a view to using it rather than VNC.


    I have a large collection of music, over 700 CDs converted to flac, so a fast interface is appreciated.


    Keep up the good work
    Roger


    Can you install 009, enable debug logging then try to install the VNC service. Then run:

    Code
    1. cat /storage/.kodi/temp/kodi.log | pastebinit
    2. journalctl -a | pastebinit


    and post the links.


    ABaW  
    MFJX
    after shutdown, remove power and reboot to retry install


    JhVD
    FgPe


    Log of process followed is below

    • Notes from install v .009 vnc test
    • Using UltraVNC Viewer version 1.2.0.9
    • VNC working in .008
    • Copy .009 tar to .update
    • Reboot Slice
    • .009 updated OK, verified version number on boot and in System Info
    • VNC try to connect: VNC failed to connect to server screen
    • Uninstall VNC add-on from Slice
    • Add-ons Services uninstall: OK
    • Enable debug logging
    • Install Raspberry Pi VNC 8.0.102 by Anton Voyl: does not give any indication of installing after select “install”, wait a few minutes. (install on v .008 shows an install message as soon as install is selected)
    • Turn off logging
    • ABaW
    • MFJX
    • Power off Slice, remove power
    • Turn on Slice, boot OK (no VNC add-on installed)
    • Enable logging
    • Select add on as above and click install. Same result, wait a minute, reselect and try to install again, same result.
    • New logs JhVD and FgPe


    Hope this helps
    Roger


    v7.90.009 is released.


    hi Chewitt


    I have installed the .009 version and I find that the Raspberry Pi VNC service no longer works. I uninstalled the service and it refuses to re-install. Did remove service, reboot device, then add service back in etc and still not working. Reverted to .008 build and it installs and runs as before.


    I use my test Slice headless and VNC to access the device for loading music.


    Happy to retest any suggestions / updates


    Roger


    I am using the following at the moment


    SC14059


    Its seems to have fixed the temp hitting 80C while updating the library, but i am still not happy with the temps i am getting, just sitting idle its hitting 57C


    Good point re CPU and board providing the flexibility. Gordon's solution of several sheets of thin copper and heatsink compound will help maintain that.


    Any chance you could try a solution like Gordon's as your quiescent temperature is fairly high? That would provide an indication of the efficiency of each solution at quiescent and load scenarios.


    Roger


    I used a standard small square heat sink that I trimmed and filed to fit between the chip and the lid, unfortunately, because the CM1 has the memory stacked on top, I suspect that the gap between chip and lid will change on CM3. :-(
    Regards, Kevin.


    Kevin, I suspect you are correct. My main concern for wanting a 'more exact' measurement is the need to ensure there is no mechanical strain on the CPU which could cause the solder joints to fracture during hot / cold cycling as the assembly expands and contracts. (These days manufacturing HAS to use the lead-free solder, which in my experience, is much less "flexible" than the good old lead-based stuff, and is much more likely to fracture or develop a 'dry joint'. Under a microscope lead-free solder has a much more crystaline structure than the good old stuff).


    The Five Ninjas may well have some prototype Slice cases which can be cut e.g. half way across the CPU to determine the thickness more accurately and then, if we are lucky and ask nicely (pretty please :) ), may be able to provide a CM3 and heatsink for the upgrade.


    A sticky thermal transfer pad would also work to help reduce mechanical strain, depending on the width of the gap, but not as efficient as a lump of copper and good quality heat sink compound.



    Another thought: have you a hard drive installed in the case? If so have you monitored the HD temperature after your Slice has been running hard for a while? I don't push my Slice hard, I only use it for audio playback and lower resolution video at present.


    Roger


    The CM3 will definitely need some form of heatsink, I get the temp gauge when updating the library, will have a test with some heatsinks this weekend


    Sent from my Nexus 6 using Tapatalk


    Mike, any update on experiments with heatsinks?


    *** edit
    Seems like the post before happened while I was posting here and over on the Five Ninjas forum!


    There should be some flexibility in the heatsink so that there is no undue strain on the soldered conections leading to mechanical breakage as the device is thermally cycled. IMHO :)


    Roger
    [hr]

    This is my solution to the CM3 heat problem... Its a few layers of copper sheet cut with heatsink compound between each layer and then araldite applied around the outside (not between the layers!). Finally some heatsink compound on the 2837 chip on the CM3 and you've got an awesome heatsink...




    Gordon


    Gordon, that seems like a good solution allowing mechanical flexibility and heat transfer, pretty much what I would do if I had an updated CM ! Of course I would be more than happy to test one :D
    Roger

    Hi Chewitt


    Slightly later than planned, caused by "unplanned sickness", an update for you:


    I have updated my main box and confirm that the audio plays fine using audio switcher (like bleep42). Video plays fine too.
    To clarify, for anyone who does not read the whole thread, my video is only TV series and stereo sound. I am saving the surround sound stuff for when I upgrade to a CM3.


    Thanks for the work on this..... looks good and is quite responsive when compared with the current Five Ninjas stable build (using older versions of Libreelec and Kodi).


    Roger


    would be great if you can do the full update test.





    I got back earlier than planned....


    Reloaded Five Ninjas Nightly build which booted and tested OK.


    Downloaded your rebuilt package (16 Oct 0740) and installed it. All works as it should. The only (obvious) difference is the LibreElec splash screen at boot time: it now says "LibreElec Alpha" not "LibreElec, just enough OS for kodi" Is this a planned update of the splash screen or a regression to earlier version?


    Apart from that I can confim the analogue audio and optical audio work as they should "out of the box".


    Thanks for assembling the package. I will test it for a bit longer on audio then install on my main Slice and test my video too, and report back on the results in a day or five.


    If you would like me to do any more testing, just ask.


    FYI (it should not make any difference functionally, although Gordon advised that it will likely reduce performance a bit) I am using NTFS partitions on both Slice boxes. I am just using the video to play old TV show box sets, not any serious decoding of surround sound tracks etc. I am waiting until CM update and may then revert to EXT4 partitons as well. I was testing the NTFS one a while ago for Gordon and saw no reason to change it.


    Roger