I shipped mine to HiassofT some time ago so I'm out of the Slice game.
Posts by chewitt
-
-
Just out of curiosity would it have to be Chrome? Possibly a light weight plain jane browser?
It has to run under GBM, and so far the only one I heard of is Ozone, which is Chrome derived.
-
This experimental change was added: https://github.com/chewitt/linux/…ebdc0f2c772d153 and there's a fix for VP9 @ 59.94 (already merged upstream) but otherwise no changes. What kind of media are you playing?
Direct to Plane should be used always.
-
Even if we identify a problem in LE11 the fix will put into LE12 so the first thing to do is update to LE12b2 and test again.
It would be useful to see the system log, so use "pastekodi" not manual copy/paste to pastebin.
-
Then you need to calibrate Kodi as described (twice) previously
-
Are there any plans in the future to replace X11 with a more up to date window system?
Wayland is the only choice out there, but since it doesn't support dynamic refresh rate switching it's not an option. Hence we already moved towards GBM with no Windowing environment. It should be possible to compile the Ozone (Chromium on GBM) browser for LE, but it's probably a large work.
-
The pi devs are currently looking into an issue related to loss of HDMI sync. It's not specifically about 4K60, but you never know, it might be related
-
2024-04-26 23:20:02.187 T:1340 info <general>: CAESinkALSA::InitializeHW - Your hardware does not support AE_FMT_FLOAT, trying other formats
^ This is harmless and will be seen on all LE installs because almost nothing supports that audio (not video) output format.
First update to LE12b (newer kernels and everything). I would also "mv /storage/.kodi/userdata/guisettings.xml /storage/" and reboot to see if a default Kodi config solves anything? (resolutions are stored in a few places).
-
The update process does not touch the bootloader or partitioning/filesystems so for an LE11 > LE12 update to fail something would have to go wrong during kernel boot; which is normally visible on-screen (the kernel outputs something).
If not, reinstall LE11 then make /flash read-write with "mount -o remount,rw /flash" and then edit /flash/syslinux.cfg to remove "quiet" from params, then save/exit and reboot. You should now see the system log on-screen during boot. Next redo the LE12 update and take a video using a smartphone in slow-motion mode to see errors (or the point boot stops) on screen. Upload/share the video somewhere so we can review it.
-
Yes, delete the patch for this test. Just be aware that later tests may require you to reinstate (checkout) the patch again.
NB: "PROJECT=Generic ARCH=x86_64 scripts/unpack bluez" will only unpack/patch the package and "scripts/build bluez" will build the package without requiring the full "walk the tree" process of the buildsystem. It might help speed up the initial "get the patches right" process. If all is good the "make image" command will then package everything into an image.
-
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?
-
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.
