Posts by chewitt

    From the descriptions it sounds like a kernel issue, but without some form of log evidence we really have nothing to research. If you remove "quiet" from kernel boot params in syslinux.cfg it will dump the system log onto the screen during boot. Record the screen as a slow-motion movie and as long as your hands are steady it's normally possible to play the resulting movie back and read the text to spot error messages. Upload load the movie to a sharing site somewhere and we can see it too.

    NB: If LE 12.0 works on the boxes (but not LE 12.2) stick on the earlier release until kodi-headless has a K22 release available. The diff between Kodi versions isn't large so it's not a 'must have' update.

    However I feel a utf-8 unzip would probably help others extracting downloads etc.

    I don't recall this issue coming up before despite umlaut and DVB loving Germans being our largest demographic, and there are multiple workarounds (7z, zipfile, etc.) so I don't see much need to replace busybox unzip with the full-fat version.

    If LE added everything that would 'probably help' it would be a 1.2GB distro download like Ubuntu :)

    This is a super-simple python script to unpack the NPVR.zip file:

    Code
    #!/usr/bin/env python3
    import zipfile
    with zipfile.ZipFile('NPVR.zip', 'r') as z:
        z.extractall('/storage/.kodi/addons/pvr.nextpvr/files/etc')

    Unlike busybox unzip, python 'zipfile' will preserve the filenames, e.g. after unpacking:

    Create /storage/.restore and place the backup file there and reboot. On restart it will be detected, the dirs that will be overwritten will be deleted (/storage/.kodi, /storage/.config, and /storage/.cache) and then the backup is decompressed to /

    You can also use the restore function in the GUI which will copy the file from wherever you have it to /storage/.restore then force a reboot to start the process.

    Or use tar commands to extract files and do other things with the backup file. It's just a standard tar archive.

    Use GParted for scan and repair. This tool can leave bad blocks out during formatting.

    If the device has failing cells it's only a matter of time (and usually not much time) before more cells or the entire card fails.

    If it was just corrupted then reformat with any tool will fix. No need to jump through extra hoops with GParted.

    If the partition UUID's detected do not match the value in cmdline.txt or are not readable for some reason, boot fails. The partition data on the SD card can be corrupted through sudden power loss, e.g. after pulling the power cord, or because the card has some kind of physical or memory problem. Cards can and will fail at some point and there's never a guarantee on how long they last, and sadly these days purchasing name brands from online sources like Amazon doesn't guarantee you'll receive a genuine card instead of an indistinguishable but inferior quality copy.

    OpenVPN works fine but lots of people (mostly folks that fell for the 'privacy' BS marketing of VPN services and have no real-world need for VPN in the first place) don't make the effort to learn basic commands and instead search for add-ons that allegedly make it easy (but under-the-hood mostly complicate it).

    In short:

    • Save/store/place your OpenVPN conf file (and if not embedded in the conf, the cert files) in /storage/.config
    • Create a systemd service for OpenVPN in /storage/.config/system.d/ that executes OpenVPN with an explicit path to the OpenVPN conf file in /storage/.config - You can use the wireguard example file to crib 95% of the required content.
    • Enable and then Start the systemd service and you should have a working and persistent OpenVPN connection

    This works for any OpenVPN service.

    /shrug

    ^ See above for some formatting fixes; formatting is important. Working?

    The 5c image in my test share now has the patches RadxaNaoki linked (inc. the audio fix) above. The previous image only has the &hdmi0_sound node added, not the i2c node.

    If gnarlsnishi confirms all is working I'll push a kernel/patches update to official LE nightlies. I've been holding off bumping the kernel to 6.18-rcX as there were PCI issues in the initial rc releases, but those seem to be resolved upstream now.

    f1gogata no idea what the problem is but I've updated the branch with current patches and it works for me. NB: I'm building on an older Ubuntu 22.04.5 (LTS) host.

    Nightlies are created on a "best efforts" basis so there is no guarantee or promise of one being created every night. If there is no nightly there is no real need to post about it because 99% of the time any cancelling of nightly builds is our doing so we already know about it, and if something is broken we get alerts and know about it, and if there are no changes and thus no nightly to be built, we're enjoying some downtime and don't need the distraction of forum posts.