Posts by HiassofT

Looks like someone already started working on a DRM grabber Raspberry Pi 4 with Libreelec v19 / Kodi Matrix, no grabber is working · Issue #983 · hyperion-project/hyperion.ng · GitHub - progress seems to have stalled a bit though

so long,

Hias

The latest nightly enables 4kp60 by default in distroconfig.txt. Please try with the stock distroconfig, wait a few minutes after powerup, then you should be able to ssh in.

Then run "pastekodi" and "modetest | pastebinit" and post the URLs, this should help us find out what went wrong.

Testing with 4kp60 here was fine but if something went wrong in the video driver it can hang for a while so bootup can take a bit.

Instead of changing distroconfig.txt you can also just add "hdmi_enable_4kp60=0" to the end of config.txt - this will survive further updates.

so long,

Hias

Hopefully the next couple of days.

It's already in internal testing, RPi4 worked fine (I tested it a couple of days ago) and IIRC the other platforms were fine, too.

so long,

Hias

You have to replace start.elf and fixup.dat on the FAT partition - see here RE: LibreELEC (Leia) 9.2.5

Note: last time I tested that was more than half a year ago and you might have to use an older firmware version (from 6-9 months ago) as it's not guaranteed that newer firmwares work with older kernels (or vice versa).

so long,

Hias

LE 9.2 doesn't support the RPi 400 as it's firmware is too old. You probably manually replaced the firmware files on 9.2.6 and those got changed back to the stock (i.e. too old) LE ones when updating to 9.2.7/8.

You have to replace firmware files again, or switch to LE 10 (which is the better solution as that will also give you working bluetooth and wifi).

so long,

Hias

4kp60 isn't available in 9.95.5, it will be available in the next release though.

so long,

Hias

Try adding video=HDMI-A-1:1920x720M@60

so long,

Hias

The log shows that the video driver read an invalid edid from your projector and therefore refused to output via HDMI.

Did you have to use any hdmi_... config.txt settings with the older milhouse build?

Can you run "pastekodi" on the milhouse build as well and also run "tvservice -d edid.bin" on it and upload the resulting edid.bin file?

so long,

Hias

Can you please test with the latest LE10 beta version? LE 9.2 contains a rather old kernel and firmware.

so long,

Hias

Quote from Teddychen

Doesn't anyone have an idea, not even the developer?

Ah, this seems to be a quirk in the firmware handling/parsing of dt parameters - the dtoverlay scope of vc3-kms-v3d, which is loaded in distroconfig.txt on RPi2/3, seems to persist after the include in config.txt so the audio parameter applies to the overlay.

The solution is quite simple, clear the overlay scope with "dtoverlay=" or move the dtparam=audio=on statement up, before the include distroconfig.txt.

eg

dtoverlay=
dtparam=audio=on
audio_pwm_mode=1

so long,

Hias

Quote from Parf

One thing I did notice is that during the boot the red LED on the Pi was coming on and off which I havent seen before. It normally stays on permantently after power on.

The red LED must be permanently on. If it's going off it means you have a power supply problem which you need to solve first - if the power isn't stable the RPi won't run stable and it could well be that the odd crashes you are seeing are caused by that.

Disconnect all USB peripherals and everything else you might have attached (fans, HATs etc) and make sure everything's working fine. I also strongly recommend using the official RPi power supply as that's known to work just fine.

so long,

Hias

Can you connect with ssh when connected to the projector? If yes run "pastekodi" and "modetest | pastebinit" and post the URLs.

There's currently a bug in the video driver, if the HDMI cable isn't plugged in or the driver doesn't detect a display then RPi2/3 lock up during boot - this can also be caused by a broken (or not fully wired) HDMI cable, so testing with a different HDMI cable would be worth a try, too.

so long,

Hias

ntfs-3g is built in (as in the official LE images).

Better stay away from USB Y-cables, at best they won't help (RPi has a total limit it can draw from USB-C and provide to USB ports) - use the official RPi power supply and a powered USB HDD or a powered USB hub if your drive needs more power.

so long,

Hias

Quote from sa_ma

for me , things seems to be more stable, still testing but so far it is solid, usuallly it crash in 20 minutes and so far it is holding up nicely

by the way , are you going to keep making 64bit kernels from now on or this is just a quick test ?

Thanks for testing and reporting back!

It would be great if you - and other people with OOM issues - could do some extensive testing with this build, keeping an eye on issues (also seemingly unrelated ones), and tell us about the results.

For now it's only a quick test, but if the OOM issues are indeed resolved by the 64bit kernel and LE runs fine with it then we will consider switching official LE RPi4 builds to it in the future.

so long,

Hias

Modifying /flash/distroconfig.txt is the wrong approach - it will be replaced on every update. Commenting out the "include distroconfig.txt" in /flash/config.txt and replacing that with custom dtoverlay or other settings is even more dangerous as it could brick your installation on an upgrade - the stuff in distroconfig.txt is essential.

If you need to force a video mode you should add a video= parameter to /flash/cmdline.txt, eg video=HDMI-A-1:640x480M@60 - see the kernel docs for more info modedb default video mode support — The Linux Kernel documentation

It would help even more if you post why you need to change settings, which settings they are and provide pastekodi logs - then we would have a chance to look into it and if there's an issue we could fix it. If you don't report issue details and post logs they will never get fixed.

so long,

Hias

Parf can you please test this build? LibreELEC-RPi4.arm-10.0-devel-20210713215127-5ac3ead.img.gz - just copy it to the "Update" samba share (or to /storage/.update/ folder) and reboot.

It contains a 64bit kernel instead of the standard 32bit LPAE one which should hopefully fix the OOM issues (I suspect 32bit LPAE and HIGHMEM are causing the OOM issues as lowmem is rather small on these kernels).

so long,

Hias

Thanks for testing!

I checked the driver code and noticed it only supports 180° rotation and x/y mirroring, but not 90/270° rotation. And I vaguely remember one of the RPi devs stating that 90/270° rotation was only possible with the help of videocore code in the firmware of the old, proprietary RPi0-3 driver.

So this will be quite a bit more involved, kodi's GBM windowing code would need to be extended to support rotation, direct-to-plane rendering probably won't work but egl rendering should be possible.

so long,

Hias

Display rotation should be possible by using the rotate and/or panel_orientation options of the video kernel command line parameter.

eg add something like video=DSI-1:1920x1080@60,panel_orientation=left_side_up

See the kernel documentation for infos about the video parameter: modedb default video mode support — The Linux Kernel documentation

The RPi forums might be a better place to ask about DSI/DPI panels and KMS details (I never used DSI/DPI displays myself), I found eg this post there rotate display with DPI and vc4-kms-v3d - Raspberry Pi Forums

so long,

Hias