Posts by realcam

  • [RPi4B] Argon One Case Shutdown

    Thank you for engaging with me on this first of all.

    No I dont have any overclocking and no third party software installed, very standard, very vanilla: RPI4 model b 4GB ram in argonone.v2.m2.sata case and 256GB sata ssd. Also I have the argon remote.

    Very basic LE installation using ssh starting with SD boot. After that...

    • 'dd' LE12 image to argon.m2.sata drive.
    • remove SD card
    • 2 boots & minimal/network configuration
    • install rpi tools & system tools kodi add-ons
    • boot
    • install 'libreelec_argondevice_1.1.1.zip', default config
    • install media library via shared 'mariadb' on other RPI4 server (advancedsettings.xml)
    • some kodi customization
    • finished

    I have a couple of good case kodi.logs collected with debug log setting on. Now I am waiting for the bad case to happen again to collect another kodi.log. But since then the bad case didn't happen again. :)

    I will report back when it does with any findings from the kodi logs.

  • [RPi4B] Argon One Case Shutdown

    This is whats confusing me. The symptoms described under known issue is nothing like what I am experiencing.

    Whats described in the known issue is the board powerdown outracing the Kodi shutdown leaving potential inconsistencies - I don't know maybe uncommitted db transactions or maybe filesystems not unmounted cleanly or whatever. But in my bad case Kodi and LE arent shutting down at all using the hardware trigger. I have to use the soft shutdown from Kodi.

    So I think yes its a 'new behaviour'.

  • [RPi4B] Argon One Case Shutdown

    Hello this is nice work, thank you.

    I have a question however as I'm seeing intermittent problems with shutdown. Maybe I missed some important part on the shutdown and red LED discussion.

    I have an RPI4 with a Argon v2 m2.sata case and I'm using the Argon remote with LE12 booting/running from sata ssd.

    Good case: When I press the remote's power button it brings up Kodi's shutdown/reboot dialog but the shutdown proceeds without dialog confirmation needed. After the tv screen going dark (CEC) the red LED stays on for a few seconds then blinks a few times then turns off. The RPI4 is shut down and can be turned back with the remote power button.

    Bad case: When I press the remote's power button it brings up Kodi's shutdown/reboot dialog and the shutdown does NOT proceed on its own from here. I need to confirm 'Power off system' (OK) with the remote and Kodi will now shut down. After the tv screen going dark (CEC) the red LED will stay on forever and the RPI4 cannot be turned back on with the remote. Also the RPI4 will not react to the power button at the back. I will need to make the device powerless pulling the power supply cable.

    With me this happens intermittently but frequently. I say about 80% good case vs 20% bad case. I have so far not found any hint why the bad case happens.

    Any ideas what log files I should be looking at or what debug settings I should turn on?

    thx R

  • Install to internal

    Really sorry to dig up an old thread. But I'm having difficulties to understand this device tree business. And I'm stuck on this last step - installtointernal. And I guess this thread was my starting point. I'll try...

    ...

    I have a lovely working system (8.2.3.1) with Krypton that boots from USB. All I want is Kodi and where the preinstalled Nougat w 17.4 crashed the box at random times with whatever Kodi version I tried this system just does what it's supposed to do. Wifi, ethernet, remote control is working fine, it's a keeper and I want to install it to internal flash rom.

    The box in question is a cheapie S905W w 2GB DDR3 RAM & 16 GB FLASHROM. Sold as 2018 Mecool M8S Pro w.

    So I ssh'ed into the box and ran the installtointernal command and now I don't know what device tree I'm supposed to dd in there. The one on the USB stick seems lovely, but it won't work because its USB stick which is different from the internal flash, correct?

    I've been reading the howto's of course which point to some device tree folders and it simply says you need to download a 'proper' one. I guess that means trial and error unless you know what a proper device tree for your device is? How do I know what the right one is? Should the original device tree not work which was created as backup during installtointernal?

    Of course I've also been reading up on device trees and I get what they are, but from what I gather nobody compiles these themselves. Everybody just seems to be using whatever is in the links, no?

    Sorry so many question. And in an old thread. People in the know probably sick of it... ;)

    Thanks for reading