Posts by chewitt

  • New Install, can't adjust display size on TV screen

    It's called 'Calibration' and it still exists. You might need to enable advanced or export mode in Kodi settings (can't remember as it's been a few years since I used it). Remember that you need to calibrate each resolution/refresh combo that you will use, it doesn't auto-apply the same change to all.

    Do you have a TV card? .. system logs will show tvheadend state and any errors. Look there (or share them with the build-in paste function).

  • NAS Storage

    I'm not going to spoon-feed changes. If you edit the files you can see the format. The only difference will be adding a share and it will use "smb://server/share" format instead of a local "file://path/to/share" entry. There's also this thing called Google and the Kodi wiki. Inexperience and/or age do not limit initiative.

  • NUC10 + LE13 + HEVC

    smp logged the same issue here: https://github.com/xbmc/xbmc/issues/23699

    The log in this thread also shows the same issue (no insights in the threads, only whinging):

    Does bumping ffmpeg to 6.1.1 help? .. I'm expecting 'no' but it would be good to eliminate the idea.

    Can you also enable ffmpeg component logging in Kodi settings and then regenerate a 'bad' log. I'm wondering if ffmpeg will show more internal info.

  • HDMI Audio too fast before silence

    BIOS updates are always a good thing but updating some ancient old laptop to be a marginally less ancient old laptop probably doesn't achieve anything.

    Have you tried setting the whitelist to 1080@60 and enabling 3:2 pulldown in video settings? .. It might need advanced or expert mode enabling to see all the options.

    I'd also see if things are different on a newer TV that has more display modes. This looks like an old HD-Ready set which only has one weird 1080p mode available. Or perhaps try the VGA output.

  • S905W2 device-trees

    Quote from guerrero2694

    There is no DTB available

    That's because S905W2 chips are based on a newer Amlogic hardware generation (S4) that is not supported in the upstream Linux kernel that LE uses. Amlogic engineers started to submit support for S4 devices, but they have low experience with kernel standards so each subsystem they submit is initially full of low quality code and takes a large number of rework/resubmit iterations before it comes up to scratch and can be merged. Progress is .. slow.

    CE have images that should work on the board (AFAIK) but for help with that you need to post in their forum.

  • Bricked MXQ Pro 4K

    Quote from deimos

    I've decided to use this an a opportunity to refresh my micro soldering skills and attempt to transplant the eMMC

    You need to be a whizz with a hot air gun to do that, and you need to read/write content from the chip to 'fix' things which will be a major undertaking. I'd go find/test a bunch of Android ROMs first, as the chances of success will be a lot higher.

  • HDMI Audio too fast before silence

    Code
    If you are asked for a log - assume the request is for a debug log and for the entire log file, not just the small snippet you think is useful (often we need to see and understand the configuration too).

    ^ Quoting from the wiki article that you didn't read, resulting in a series of log snippets that tell us nothing.

    Try again..

  • N2 kernel issue

    There's a drip-feed of bindings changes and other unimportant things to DRM code; nothing of any real meaning was changed in aeons. I also have an N2+ running here for boot testing LE changes and I'd notice kernel splats (none seen).

  • N2 kernel issue

    I've moved the post into its own thread as the UART log shared shows the system boot from SD card without any errors (and thus whatever the issue is, it's not the same thing the C2 thread is about). Something goes wrong when it boots the kernel. The splat suggests something with the HDMI driver (so something in the display chain).

    Can you successfully boot from an eMMC module to prove it really is SD related (which it almost certainly isn't)?

    Can you successfully boot this image? https://chewitt.libreelec.tv/testing/LibreE…droid-n2.img.gz

  • HDMI Audio too fast before silence

    Please provide a full debug log.

    How to post a log (wiki)

    1. Enable debugging in Settings>System Settings>Logging
    2. Restart Kodi
    3. Replicate the problem
    4. Generate a log URL (do not post/upload logs to the forum)

    use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

  • NUC10 + LE13 + HEVC

    The error is reported by FFMpeg though since it's in codec code (and switching to software decode works around it) the problem could equally be in the underlying Intel drivers. If you are into self-building images and experimenting there are pull-requests for kernel bumps to Linux 6.9.5 and 6.10-rc3/4 open on our GitHub repo. Bumping FFMpeg to something newer is harder as Kodi has hard API dependencies; v7.x won't be possible but a later 6.x release might work. `At some point we'll move LE13 to Kodi 'P' which will bring a bump to FFMpeg v7.x too, but until then there's not much to do I think. I would be very surprised if it had anything to do with BIOS as that's low-level and codec things are some way above.

    NB: The whitelist suggestions here would help your overall config https://wiki.libreelec.tv/configuration/4k-hdr but will make no difference to the reported problem.

  • NAS Storage

    The format in /storage/.kodi/userdata/sources.xml and /storage/.kodi/userdata/passwords.xml is simple to crib so I never bother adding sources from the GUI these days; it's much faster to do it from the SSH console using nano.