Posts by chewitt

The "ptp_kvm" message on-screen is completely harmless. Does boot continue or is that the only issue? If no, does "live" or "run" modes work (running from USB)?

When building a package the build-system downloads and unpacks package sources, applies patches, then compiles the package. In this case it fails during patching because the patch contains changes that already exist in the source so the patch cannot be applied. In this specific case delete the patch with "rm packages/network/bluez/patches/bluez-12-fix-obexd-after-5_73.patch" then re-run the build command and compile should succeed. Beyond some point in the timeline of changes/commits between v5.72 and v5.73 the patch might be required again (the compile might fail) in which case you can restore the patch (undo the delete) by checking it out from git with "git checkout packages/network/bluez/patches/bluez-12-fix-obexd-after-5_73.patch" and re-running the image build command again.

What is the hardware?

Quote from Veda

I am actually powering it from the USB of my TV

^ that is a recipe for problems. RPi4 needs a stable 5V/3A supply and TV ports are probably giving 500mA (the default for USB).

DVB cards are often power sensitive/hungry and need good PSU's to avoid problems. You're lucky the adaptor has the extra berg connector.

Please boot and run "pastekodi" then share the URL. We enable "CONFIG_SND_OXYGEN=m" in kernel configuration so the drivers for the card exist. Perhaps there is some issue/error in the log?

moi952 I'd guess you installed an older nightly image and the 11.80.0 (alpha) repo it requires no longer exists. Update to 11.95.2 (LE12 beta2) and it will be using 11.80.6 which does exist.

Honestly.. no clue. I'd suggest reporting the problem to Linux audio developers via the alsa-devel mailing list. Feel free to CC me (chewitt@ le domain) if you do, then I'll see any replies. Tell them the kernel version you're using (distro is nice to know, but don't labour the point) and the hardware, and ask for guideance on how to provide debugging info.

[    5.798317] si2157: probe of 6-0060 failed with error -5
[    5.798332] cx23885: cx23885_dvb_register() dvb_register failed err = -22

error -5 is EIO and the error -22 is EINVAL; the latter is likely the result of the first. I've no idea what the issue is, just trying to save someone else some log reading..

It's a while since I needed to bisect something

RPi boards with 512MB RAM are best on LE 9.2.x which uses legacy hardware decoders like OMXplayer that are highly optimised for older hardware. LE10 and up use the GBM/V4L2 display pipeline which fundamentally needs more RAM; hence we dropped support for anything with less than 1GB in later LE versions.

We will drop the 4.2 (and 4.3) version once Tvheadend makes a 4.4 release. Making a 4.4 ffmpeg probably isn't hard, but when there is a single user in our entire userbase reporting an issue, it's not justified.

booster share a full debug log please.

Quote from mediatex

how the other frequencies affect the quality? In what cases I should try other frequencies?

Read: https://wiki.libreelec.tv/configuration/…#adjust-refresh and the section on interlaced media.

Quote from graham.reeds

How can I make the setting stick?

You can't, by design. If you broadcast a single SSID that supports 2.4Gz and 5Gz channels the drivers will auto-select frequencies and channels based on signal strength and neither ConnMan or IWD support locking to a specific frequency/channel. The only real-world way to prevent swapping between 2.4 and 5 is to have separate SSIDs for each and then config the Pi to use only the 5Ghz SSID.

Quote from ehoitinga

In stead of "updating" my current system I suppose I can also create a USB stick with the first bisected image on it and run it with the "run" option once and after that copy the next image to /storage/.update/ on the USB stick and run it and apply the "update".

Sure, we'll end up with the same result

You can find a couple of AMLMX test images here: https://chewitt.libreelec.tv/testing/

Code is here: https://github.com/chewitt/LibreELEC.tv/commits/amlogic-mx

Things are super-experimental and you will note from the date/time stamps on those files that I haven't worked up the enthusiasm to rebase anything onto LE12. And since I just started a new job, and accidentally ended up helping to manage the Tvheadend project too, and have a major Triathlon to train for later in the year .. I'm rather time poor these days so I wouldn't hold breath.

AMLMX really needs someone with some of those boxes to take the lead..

EDID data from the TV over HDMI advertises 1080p @ 60/59.94/50/30/29.97/25/24/23.976 (all the normal HD modes) so I would be trying to use 1080@60 not an odd resolution like 1360x768 (the kernel sees 1360x768 not 1366x768).

If you have video output which goes a little beyond the screen (and the TV auto-scan mode doesn't fix that) you can calibrate the TV output using Kodi (the wiki article was linked in an earlier post). Note that you need to calibrate each mode used, e.g. if using adjust-refresh to change from 1080@60 to [email protected] for better playback you will need to calibrate the [email protected] mode in addition to the default desktop mode.

I'd suggest updating to https://releases.libreelec.tv/LibreELEC-AMLG…h64-11.95.2.tar or https://chewitt.libreelec.tv/testing/LibreE…ch64-12.0.0.tar as there are some minor improvements for AMLGX in LE12/K21.