Posts by HiassofT

  • RPI4 - does not obey config.txt set resolution

    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

  • CM3+ with LT070ME0500 DSI display

    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

  • CM3+ with LT070ME0500 DSI display

    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

  • CM3+ with LT070ME0500 DSI display

    The lockup seems to be HDMI related, it happens both on LE and RPiOS with latest rpi-update kernel/firmware kernel: drm/vc4: More CPU Stall Fixes · Hexxeh/rpi-firmware@9dbcd6d · GitHub (LE uses the same fw/kernel version as this rpi-update commit) when booting without a HDMI monitor connected.

    I already chatted with RPi devs, they'll look at it next week (popcornmix and I also confirmed it still happens with current rpi-5.10.y kernel which contains some fixes in that area).

    Concerning LE kernel config changes: it'd be best if you change the panel driver to "y", so it's available right after boot (otherwise you won't get splash and update notifications on screen).

    Also drop the gpu_mem change from config.txt (that's not needed and only wastes memory) and you can also drop the vc4-kms-v3d dtoverlay line (that's already in distroconfig.txt).

    Better wait with further testing until RPi devs have a kernel fix, serial console won't help too much ATM as you'll only see the kernel is locking up before the vc4 hdmi line should appear (other than that a serial console is really helpful).

    so long,

    Hias

  • CM3+ with LT070ME0500 DSI display

    deltasjimmy can you test if the display is working on RPi OS with the latest rpi-update kernel (currently 5.10.46-v7+)?

    I built an LE image with the missing drivers included, but it just locks up on my RPi3B+ when I add the vc4-kms-dsi-lt070me05000 dtoverlay - and the same happens on RPiOS with latest kernel as well. I don't have any DSI displays here so not sure if that's the cause - the DSI driver is still under heavy development so it could be an issue in latest kernel, too.

    so long,

    Hias

  • CM3+ with LT070ME0500 DSI display

    Thanks for the logs!

    I just noticed our kernel configs don't include CONFIG_DRM_PANEL_JDI_LT070ME05000 - so the dtoverlay can't work.

    I'll have a look at what other options might be needed, this will take a bit (not sure if I find time this week), but I'll get back to you when I have something for you to test.

    so long,

    Hias

  • LE10 network boot (PXE) with Pi4/B 4GB doesn't work

    Which tftp server are you using, is it by chance the netkit one ("tftpd" package in debian/raspbian)? If yes, don't use it, it doesn't work (just tested that here locally) and even the package description warns that it has issues:

    Code
    hias@camel2:~$ apt-cache show tftpd
...
 Warning: Does not support 'tsize', which is required by some tftp clients,
 especially PXE, and various other network boot clients. For those, use atftpd
 or tftpd-hpa.
...

    Both atftpd (which I usually use) and tftpd-hpa work fine here.

    so long,

    Hias

  • LE10 network boot (PXE) with Pi4/B 4GB doesn't work

    Hmm, I use the same bootloader version but with a flat layout (firmware etc in TFTP root) it looks very different. I see one request to SERIAL/start4.elf and another one to SERIAL/start.elf, then bootloader falls back to root:

    Your log however shows SERIAL/start4.elf requests repeating in 2 second intervals - and tftpd serving it (?)

    Might be worth digging into the tftp config/setup, something seems to be odd there (maybe permissions or timeouts).

    For reference here's my bootloader config (basically default settings, except for boot uart and order)

    so long,

    Hias

  • Cant play 4K MKV files without crashing

    Unfortunately the kodi crash logs are again empty and the other ones don't show you playing a file.

    It looks though that mount.ntfs triggered the OOM killer - which makes me guess you played the video from an NTFS formatted USB drive. Can you try if copying the video to SD card and playing from there works?

    so long,

    Hias