Posts by chewitt

erbas I'm already on Linux 5.6 and will bump LE master to Linux 5.7 around 5.7-rc2 to keep the patch count under control. This means I am always working on a kernel one version ahead of working media_build support (which always lags) so there's no point in adding the drivers. Once video and audio things are more upstream (around 5.8) we can probably realign with the x86_64 kernel version and reintroduce those drivers.

NB: News on the DVB front is that I submitted the missing pinctrl change on behalf of afl1 (his first in-abstentia commit to the kernel) and those are now merged upstream for Linux 5.7 .. and we've been coaching Availink on their efforts to provide public and modernised sources for their demod and some related tuner drivers. The mainline codebase will need someone to write a new V4L2 compatible demux driver, but I think that can be done, maybe by the Availink folks. I wouldn't expect usable code anytime soon, but there's light at the end of yet another long dark tunnel.

vi7al FFmpeg rework is not done so video seeking doesn't work and at end of playback numerous codecs will lock up. Until that work is done I have little interest in video issues (because we know there a loads). No idea about the WiFi issues; in theory there shouldn't be any device-tree or firmware differences between LE images and Olegs. The dmesg log would help understand that.

I already did.. The world’s leading software development platform · GitHub <= mostly for code but you can share anything really.

Put Dropbox - u-boot.ext - Simplify your life in the root folder of the SD card and reboot and blue/green colours should go away. It's a hack to chain-load mainline u-boot, but it works until we figure out what the proper solution is. No idea what the issue with Enigma plugins is .. best to share log-files in the DVB section of the forums and someone might take a look.

Question .. is the TV/monitor that you've connected the device to a 1080p or 4K screen?

There is a bug in 9.0.2 (there is no 9.2.1 release for the Core) and while a few people claimed to have fixed it nobody ever shared the fix so there's never been a 9.0.3 to resolve it. Since then we switched our focus towards mainline kernel support for Amlogic devices, and this is not currently possible for Meson8* hardware (no HDMI driver). Not the best report card, but that's the situation. LE 8.2.5 should work .. stick to that.

"What you see is what you get" (today). I wouldn't expect any further changes/enhancements in the LE 9.2 codebase (first to support RPi4) as all the audio development is focussed on newer kernels and the codebase that will eventually become LE10. The goal is pass-through and high-bitrate support, but it's an entirely new SoC so everything has to be figured out from scratch without much prior-art or documentation to follow.

re-reading and noticing "failed: Host is down" .. is the "server" pi on a static DHCP reservation? .. or did the IP change?

NB: I use hostnames for mounts/sources and static IPs or static DHCP reservations for anything client devices need to access.

For kicks you could try this image on a spare SD card LibreELEC-AMLGX.arm-9.80-nightly-20200324-aeb6e84-box.img.gz - It won't be great for playback (still a bit experimental) but might help set the u-boot environment up better. I've had issues with other Beelink firmware; to make things boot quicker some of the normal wait points in the boot sequence are time-reduced which makes it harder to release the reset button at the right point to trigger the u-boot recovery mode (which is how the toothpick method works).

Read Compile [LibreELEC.wiki] .. checkout the "libreelec-9.2" branch and "PROJECT=Generic ARCH=x86_64 make image" to compile. Once you have a working image you need to edit packages/x11/driver/xf86-video-nvidia-legacy/package.mk and bump the driver (change version and remove the SHA256 hash) and re-run the build command. If you're lucky it will download/build/update the legacy driver. Test the image .. but don't get hopes up. You may actually be better off with an older driver version, but the best way to achieve that is to clean install and test older LE releases (9.0.2, 8.2.5) which will have older drivers embedded. NB: If you find that works you won't be able to simply revert the version in the current LE 9.2 package to much older versions as at some point the old driver will lose ABI compatibility with newer x11.

The board will likely be more stable without hdmi_enable_4kp60=1 but mostly it only enables 4K modes you don't need.

Can you create a sample file .. 100MB or so of the movie from a scene where you see skipping? - we are always on the search for bad media and/or things that stress playback for the Pi Foundation developers to look at.

Only PCM output is supported at the moment.

Nice. I recommend you upload the documents to GitHub or a maker website and share the link. Don't wait to be asked!

RPi4 does not support WOL because the board is completely unpowered when "off" so the Ethernet device is not awake to receive the WOL packets being sent. The exception is when using POE (Power Over Ethernet) as the HAT is both powered and responsible for powering the board (so can turn it on).

Nothing looks wrong with the .mount file. What OS/distro (and version of Samba) is the pi "server" running? LE or something else? .. If not LE, share the smb.conf for the server so we can see what SMB dialect(s) are being set (or defaulted).

Kodi web interface is on port 8080, e.g. http://192.16.2.20:8080 <= replace with whatever the IP is of the LE device. There's a remote control in the web interface so you can navigaate around. If you don't understand how to use Kodi read Official Kodi Wiki

I use Ethernet .. because I rip discs with a high quality level and WiFi is rarely a reliable medium for streaming large files. I like reliable.

WiFi issues are always part environmental in addition to hardware/software. I can't explain why your pi does not reach AC speeds. I'm not sure anyone else can either. I don't expect WiFi performance from an RPi4 though; the design priority on a pi board is basic connectivity so that kids can do "online" things and develop fun stuff.