Posts by HiassofT

Can you please run the commands in post #6 RE: Cannot get LE to run on Raspberry PI 4 4GB of RAM on your working and (if possible) on your non-working setups? It would be really interesting to see the logs, they might provide some more insight.

In addition to that also run the following command and post it's output, too.

vcdbg log msg 2>&1 | pastebinit

Concerning power supply: note that LE10 won't show the lightning bolt, undervoltage messages will be in dmesg / kernel log though

so long,

Hias

Have you tried a different HDMI cable?

Needing hdmi_force_hotplug indicates the RPi can't detect the presence of the TV - which is often caused by a bad (or not fully wired) cable. RPi firmware will then fall back to 1024x768 video mode.

You need to resolve this issue first, the new driver heavily relies on getting correct info from the TV - the EDID contains info about supported video and audio modes, which is crucial for correct operation.

BTW: if you add "ssh" to the end of cmdline.txt ssh will be activated (it's deactivated by default) then you should be able to connect with putty if it's up.

so long,

Hias

Quote from greycat

Would these steps also help troubleshoot 9.2 on RPi 4?

No, video configuration completely changed in LE10, using the standard linux methods instead of the legacy RPi specific config.txt method.

This bugreport read as it might be a video driver/mode issue while the issue you linked seems to be something completely different (also you seem to get video output on screen).

so long,

Hias

Please try with a clean installation of the latest LE10 beta, leave config.txt and distroconfig.txt as they are and add the following options to the end of cmdline.txt:

video=HDMI-A-1:1280x720M@60D drm.debug=0x04

This should give you working video output at 1280x720.

Then ssh in, run the following commands and post the URLs you got from them:

pastekodi
modetest | pastebinit

If video and audio are working fine you can then drop the drm.debug option and just keep the video option in cmdline.

so long,

Hias

What exactly were the "couple of config changes" you needed to do to get RPiOS running?

Both RPiOS and LE should run out-of-the-box (and actually they do here and for most users). Without knowing what your changes were, which TV/monitor you are using etc there's not much we can do about it.

so long,

Hias

Quote from mglae

/flash can never be unmounted but the message is not visible with a working reboot. No idea why it is hanging.

A driver crash can often lead to reboot hanging - if kernel is in a messed-up state driver may not shutdown cleanly and block forever (had that a couple of times with other drivers).

so long,

Hias

Yes, the config.txt HDMI/EDID settings have no effect in LE10 - that's now all handled by kernel/DRM drivers.

The easiest way to install a permanent edid is to connect the TV, boot LE and then run "getedid create" (like on x86) - that'll dump the edid to a file and perform the neceessary config steps.

so long,

Hias

You can configure the GPIO in the gpio-shutdown dtoverlay, then you can use one button connected to that GPIO for power-off and another one on GPIO 3 for power on.

so long,

Hias

You don't need rpi-tools, just use the gpio-shutdown dtoverlay and a button connected to GPIO 3 and GND.

See /flash/overlays/README for more details.

so long,

Hias

Thanks for the report. I could reproduce the issue and have informed the RPi video codec developer.

We've got reports of similar (but less pronounced) issues before and ATM it's a bit mysterious what exactly is going wrong - but there's definitely a bug somewhere and it'll be looked into.

BTW: as a temporary workaround you can disable "allow hardware acceleration with DRM PRIME" in settings->player-videos in LE10, then the file plays fine, too (with software decoding).

so long,

Hias

Quote from dippes

Is it possible to set the Raspi to boot from USB at startup and not to search for the sd card first?

You can do that by changing the bootloader's BOOT_ORDER setting to 0xf14 or 0xf4. On LE10 beta you can simply use "rpi-eeprom-config --edit" to change that.

Read through the official RPi docs for more info:

Raspberry Pi 4 bootloader configuration - Raspberry Pi Documentation

so long,

Hias

Quote from daflux

I can't seem to download this file is it offlilne?

Just use the latest official beta version, it includes all HDR changes.

I've removed the old testbuilds to avoid confusion and they are heavily outdated now as well.

so long,

Hias

Did you by chance change gpu_mem in config.txt? If yes: don't do that, keep it at the default of 76 or you will experience crashes - LE10 needs lots of CMA memory, not GPU memory.

so long,

Hias

Quote from marantz

I can reproduce forced reboot after jump/skipping backwards 2-3 times on a h265 remux files, I remember there was issues with jumping so maybe this is known?

Was that a file with a TrueHD audio track?

There are a couple of known issues with TrueHD in kodi, see eg here Crash while seeking video with TrueHD audio · Issue #16096 · xbmc/xbmc · GitHub

so long,

Hias

Crackling audio is a known issue with H264 hardware decoding, adding audio_pwm_mode=1 to config.txt will fix that but result in lower audio quality.

so long,

Hias

Quote from darkblaster77

Have fresh installed LE 9.2.6 on RPi3 and RPi4. Configured the same "for loop" script in autostart.sh on both setups.

Oddly, it only worked on RPi4.

I just had a look and, yes, it won't work on LE 9.2/RPi0-3 which uses the legacy graphics driver.

In order to save a bit of memory the console is unbound and the framebuffer reconfigured to 1 pixel size (via an ugly hack in kodi). This was added in ancient times and I completely forgot we had that in LE...

RPi4 on LE9 and also RPi2-4 on LE10 don't use the legacy graphics stack so /dev/console will work fine there.

so long,

Hias

Nothing unusual in the logs, no idea what's going wrong.

The script worked fine when I tested it on my LE 9.2.6 RPi4.

I'd suggest testing with a direct echo to the console with kodi stopped. eg "echo hello > /dev/console"

so long,

Hias

Check the journal or stop kodi ("systemctl stop kodi"), run the script manually and watch out for errors.

so long,

Hias