Posts by chewitt

  • [S905X3] How to correctly compile own DTS

    Fork my amlogic-6.16.y branch on GitHub then checkout a branch for your change, and then add your device tree file to arch/arm64/boot/dts/amlogic/ with a matching entry in the Makefile. Commit the change to your branch and then generate a patch with “git format-patch HEAD~1” and then rename from 0001-* to 9999-* and copy the patch file to projects/Amlogic/devices/AMLGX/patches/linux/ .. then rebuild the image and it should be compiled. If there are issues compile will fail with line/char references to the first failing problem. Note that you will not be able to just reuse a dts from CE as their kernels are diverged from upstream.

  • [x86-64] Video Crash on Intel NUC N100

    I forget whether the SMB chunk size changes are in K21 or K22, but to keep things simple use an LE13 (K22) nightly and experiment with the settings a little. You can force SMB v2 (2.0) vs. 'v2 and Large MTU' (2.1+ and 3.0) which might help. You can also force the client to use a larger or smaller chunk size; the default should work for most configurations, but there are exceptions.

    Also see if Samba on the router can run in debug mode or can create enhanced logging? - In client/server relationships there are two sides that can have issues, and the kernel splat shows the router having problems. No idea whether it's a related issue or not.

    The workaround would be to locally mount the remote SMB shares from the LE device using system.d mount files and then use the local mount points for your Kodi sources. This has the advantage of allowing you to create an SMBv1 connection to the router, and a separate SMBv2/3 connection to Win10, whereas the Kodi SMB client forces you to use the same config for all connections it makes.

    See: https://wiki.libreelec.tv/how-to/mount_network_share

  • LE13 Testing for RK3288, RK3328, RK3399, RK3566, RK3568, RK3576, RK3588

    ozarks I've updated the first post with info on media capabilities; VP9 is known and possibly a partial leak of RK3399 capabilities to the newer SOC, it's been flagged to Collabora. Regarding OPi5 and USB-C, if you can point me to patches on a mailing list I can pick them, but I don't think I see anything for that board. Or if you can figure out the patch (there is maybe prior art for the Rock5 boards) I can send the patch upstream on your behalf.

  • VNC server?

    Correct, the zero-copy video pipeline (and no desktop environment) arrangement used in LE10+ doesn't allow for software-copying video data to anything so VNC and Ambilight installs aren't possible. External (hardware based) KVM devices will still work as those have no dependency on software internals.

  • LE13 Testing for RK3288, RK3328, RK3399, RK3566, RK3568, RK3576, RK3588

    I've pushed Rockhip images based on the RK356X/RK3576/RK3588 enablement PR: https://github.com/LibreELEC/LibreELEC.tv/pull/10420 to my test share.

    Download here: https://chewitt.libreelec.tv/testing/

    Images are versioned 12.90.1 in premature preparation for an LE13 alpha1 release. Don't get too excited at the version; there are no timescales and it's just a number. I use static versioning because it makes download URL's predicatable vs. having random githashes in filenames. If I push updated images to my test share the date/time of the image changes, not the version number.

    Images are experimental "minimum viable product" not "finished product" state with 15+ different kernel patchsets (some merged, most are in-flight). There is huge scope for bugs and issues. You should expect to find some problems.

    Media capabilities: H264 and HEVC should work. 4K modes should work, but there is no HDR and I don’t expect this to be added in the short-term. VP9 is software decoded at 1080p but hardware decoded at 4K (which is a bug as it should be software decoded) so 4K currently fails. AV1 is software decoded; the kernel driver exists but the corresponding FFMpeg hwaccel has not been written yet.

    CEC should work although I never test this myself as too many identical devices are connected to the AVR and it gets confused.

    HDMI audio is limited to PCM output. There is no pass-through and I have no idea what is missing or needed to enable that.

    Feedback on issues related to distro packaging and specific boards (boot issues, missing hardware etc.) is useful. Feedback that includes fixes is particularly welcomed. If you want to be a "tester" posting "H264 working, HEVC working" levels of detail each time I post an update please keep quiet. The core image has already been through basic sanity testing and we have general knowledge of what works (and media capabilities are still very much work-in-progress) so that kind of feedback is noise and quickly becomes annoying. Of course, if you have technical knowledge on kernel and codec development we are keen to have your meaningful feedback!

    p.s. If for any reason you need to share a log file, please use the built-in paste function or upload to pastebin.com and then share the URL generated. If you attach files to your post do not expect me to look at them.

    Enjoy :)

  • NTFS Access Unreliable

    NTFS support has come a long way in recent times but we still see issues (similar to what you describe) reported with the in-kernel drivers. You can also install the older NTFS-3G driver which runs via FUSE (so a lot slower) which might be more reliable.

    If you want to eliminate the shenanigans do a rolling reformat to a native Linux filesystme like EXT4 or XFS. My personal preference is EXT4 as this allows filesystem shrinking in the event you ever need to juggle partitions (XFS only allows expansion) but that's not a frequent requirement for a media box.

    Better still, shuck the drives into a Synology NAS case and avoid all those cables attaching USB drives. The ease of use and features and proper hardware design are worth the $$.

  • [x86-64] No HDMI Audio

    LE uses alsa. Pulse is present and running but only used for BT output, unless you manually reconfigure it and then it's a layer on-top of alsa, so it won't solve anything (you only add to the layers of problem) if alsa isn't working.

    Please share a proper debug log not snippets of what you think is revelant. You omitted all the stuff that's actually useful. Use the built-in log paste function (uploaded zip files are a pain in the rear).

  • [x86-64] LE 12.2 is missing the Broadcom-wl WiFi driver completely

    Quote from jim_p

    Is it the same for le too?

    IIRC the breakage occurred earlier than Linux 6.16 but there were no patches to be found anywhere when it occured and we waited a while before moving to drop the driver. As exorcising external drivers with no hope of ever moving upstream has been a long-term initiative, even if patches for 'wl' did appear now, we have no plans to reinstate support. Sadly the 'b43' driver is not in great shape either and we're a little surprised it's not been purged from the kernel due to its equally unmaintained state; hence why we didn't enable that as a replacement.

  • Add sysfsutils

    Bash
    #!/bin/bash
for param in $(ls /sys/module/btusb/parameters/*); do
  value=$(cat $param)
  printf '%-20s= %s\n' "$(basename $param)" "$value"
done

    Gives output like:

    Code
    disable_scofix      = N
enable_autosuspend  = N
force_scofix        = N
reset               = Y

    Repeat the same four lines for other modules and their paths and you're done. Tweak the %-20s= value to change the = offset.

  • Add sysfsutils

    The latest sysfsutils code appears to have been released and last updated in 2006 so whatever it is or does is probably superseded by other tools by now. It's also the first time I heard of anyone requesting it (in the decade+ time I've been hanging around the project) so the number of users who might think it's handy is probably you and .. (don't hold breath).

    Step back a level. What were you trying to do?