Posts by chewitt

    Code
    2023-03-16 15:31:48.335 T:140209459025664 WARNING: Attempt to use invalid handle 535
    2023-03-16 15:31:50.581 T:140208469178112 WARNING: Attempt to use invalid handle 541
    2023-03-16 15:31:52.427 T:140209459025664 WARNING: Attempt to use invalid handle 545
    2023-03-16 15:31:59.165 T:140208469178112 WARNING: Attempt to use invalid handle 558
    2023-03-16 15:32:04.821 T:140209459025664 WARNING: Attempt to use invalid handle 571
    2023-03-16 15:32:06.693 T:140209467418368   ERROR: GetDirectory - Error getting
    2023-03-16 15:32:06.693 T:140209459025664 WARNING: Attempt to use invalid handle 576

    ^ this is in the Kodi log.

    Code
    Mar 16 15:32:07 LibreELECmini kernel: EXT4-fs (sda1): error count since last fsck: 1
    Mar 16 15:32:07 LibreELECmini kernel: EXT4-fs (sda1): initial error at time 1676930944: ext4_check_bdev_write_error:217
    Mar 16 15:32:07 LibreELECmini kernel: EXT4-fs (sda1): last error at time 1676930944: ext4_check_bdev_write_error:217

    ^ this is in the kernel log. In my experience this sort of error message points to disk corruption, and with SSDs the main reason for that is cell errors (integrity problems in the memory chips) from a drive that's starting to fail.

    Sample clips so we can repeat the issue (or prove it's something local to your device) are useful. Pictures of artefacts aren't useful. I suspect it's something unusual about the media because stats show a stable and increasing number of C2 boards running the image and while I've deliberately tried to set people's expectations low since there are missing things and it's not perfect, I'm surprised (and pleased) at the overall lack of user issues being reported.

    I have recollection that some of the early iterations of the S905 have silicon bugs which can result in artefacts; back in 2016 the folks behind WeTek made a big deal out of their boxes only using revised silicon with fixes, but I forget the specifics now.

    If you can share sample clips of media with artefacts I'd be interested in testing/comparing with a C2 and WP2; although my C2 is from one of the last production batches so might also have later S905 silicon. I don't see any issues with 1080p H264 on a WP2 box the kids use, and seek works well. HEVC shouldn't have playback issues but does have some known seek issues (as stated in release notes). SMB vs. NFS shouldn't make any difference (unless using over WiFi, which is always rubbish for streaming).

    You are using the Generic (GBM/V4L2) image which does not support Hyperion. You would need to crossgrade to the Generic-Legacy image which still uses X11 windowing. Crossgrade will require you to uninstall any binary add-ons that depend on OpenGLES, then clean the local package cache, before 'updating' to Generic-Legacy and reinstalling OpenGL compatible versions.

    In the long-term the X11 image will be discontinued (GBM is the future technical direction) so you might want to think about adapting your Hyperion setup to use an external HDMI grabber.

    All of the "errors" you are showing log snippets from are harmless and simply the result of code probing to find a DRM device and setting up the initial OpenGLES context. It would be more useful to show us the entire logfiles (run "pastekodi" and share the URL). This will also show the cmdline/config txt files where you probably used legacy options that don't work on LE10+ graphics.

    i do same proccess with librelec 9 with other sd card and its booting ok.

    The LE11 release announcement clearly states the boot process is different and provides a helpful link to the Amlogic wiki article where the instructions have been documented. I've also told you multiple times to read the same article. Why? .. because the process is different.

    PEBKAC /shrug

    but everytime i boot from weos..whats i m doing wrong?

    I'd guess that you haven't set the DTB name in uEnv.ini .. but since you provide zero technical evidence or detail of what you did to create the SD card (and from what image) I can only guess blindly at the issue. Stats show a steadily increasing number of active installs so other users are able to follow the instructions and install, so the image(s) are good.