Jump to content

robertoj

Members
  • Posts

    605
  • Joined

  • Last visited

Posts posted by robertoj

  1. The orange pi zero 2w is configured to only start u-boot from the microSD in the built-in microSD. You would have to:

     

    * recompile that uboot to load the initramfs and the kernel from your alternative storage (did you really mean HDD? which connector would you use?)

    or

    * load initramfs and kernel from the typical microsd /boot partition, but configure the kernel argument line to accept the HDD as the rootfs (make sure that the initramfs contains the kernel modules, and the hdd name is in the /etc/fstab file)

    or

    https://jamesachambers.com/orange-pi-zero-2-usb-ssd-boot-guide/

     

  2. Which kernel, debian, mesa and sway versions are running normally when you run a stock Armbian?

     

    Which new versions have you observed working together? (even if it's not ARM).

     

    If they are too different, they may not work together due to library functions expecting other parameters.

     

    You can try it with Ubuntu Noble, which has newer packages than Debian Trixie (build Armbian by yourself).

  3. On 11/11/2025 at 2:36 AM, usual user said:

    FWIW, HEVC support is queued for 6.19.

    With WIP patches on top, rkvdec2 is also available to me. With the gstreamer framework, this works for me out-of-the-box, as the necessary support has been available in mainline for quite some time. See video-pipeline.pdffor reference.

    I have already rebuilt the Huffman package with the patches mentioned above, but currently the developers of the distribution of my choice are busy rebuilding all packages that depend on it. As soon as the Huffman package is rolled out, I will start to see how HEVC performs with the FFMPEG framework.

     

    Usual User, the information you linked about Linux 6.19 seems like there's progress for Rockchip.

     

    However, is there any indication that Allwinner H618 could get H265/HEVC decoding acceleration working too?

  4. Can you repeat your amrbian OS version, Linux, and hardware?

     

    I can't give a confident advice for you, but have you tried:

    extraargs=cma=256M in armbianEnv.txt

    * turn off compositor, if using xfce (others have suggested it, and I found it unnecessary)

     

    In mpv, turn on verbosity by adding -v to the command. Then while it is running, close it and copy all the mpv text in a text editor.

    Search for the words h264, ffmpeg, v4l2, hardware, software

  5. Make sure you have ili9486.ko in your ko module folder: modinfo ili9486

     

    Can you use the DTS that I published in:

    https://forum.armbian.com/topic/47971-driving-the-ili9488-lcd-40-inch-cheap-chinese-clone/#findComment-208446

    But change the "compatible" line with waveshare,rpi-lcd-35 ,

    Delete the stuff under the "compatible" line, until the "}vsync-len = <0>;", and replace it with what you had in your DTS. Change these lines, if they are different:

                    spi-max-frequency = <24000000>;
                    rotate = <270>;
                    bgr;
                    fps = <30>;
                    buswidth = <8>;
                    regwidth = <16>;

     

    Reference:

    https://github.com/raspberrypi/linux/blob/rpi-6.12.y/arch/arm/boot/dts/overlays/piscreen-overlay.dts

  6. I just upgraded my Linux Mint from 22.2 to 22.3 "Zena" ... CLEAN INSTALL, with "git" installed

    I started a typical armbian build folder, as per:

    https://github.com/armbian/build?tab=readme-ov-file#quick-start

     

    But then I got this error:

    [🌱] Build host OS release [ zena ]
    [🌱] Build host architecture [ amd64 ]
    [💥] error! [ Unsupported build system: 'zena'  ]

     

    I know that Mint 22.3 was released just last month, but I needed something in the new Linux kernel.

     

    I can use Mint 22.2 in another computer (where armbian is working OK)... but what is the typical delay for a new Linux Mint to become supported?

     

    Then I tried with $ sudo apt install docker.io , and got a little further:

     

    $ ./compile.sh 
    [🚸] Docker is installed, but not usable [ can't use Docker; check your Docker config / groups / etc ]
    [💥] Problem detected [ Docker installed but not usable ]
    [💥] Exiting in 10 seconds [ Press <Ctrl-C> to abort, <Enter> to ignore and continue ]
    Counting down: 9... 8... 7... 6... 5... 4... 3... 2... 1... 0... 
    [💥] error! [ Exiting due to 'Docker installed but not usable'  ]
    [💥] Exiting with error 43 [ at /home/roberto/armbian-2026-feb/build/lib/functions/logging/traps.sh:1
                    exit_with_error() --> lib/functions/logging/traps.sh:1
       exit_if_countdown_not_aborted() --> lib/functions/general/countdown.sh:41
       cli_standard_relaunch_docker_or_sudo() --> lib/functions/cli/utils-cli.sh:261
         cli_standard_build_pre_run() --> lib/functions/cli/cli-build.sh:14
        armbian_cli_pre_run_command() --> lib/functions/cli/utils-cli.sh:122
                     cli_entrypoint() --> lib/functions/cli/entrypoint.sh:79
                               main() --> ./compile.sh:50

     

    More info: my docker is version 28.2.2

     

    $ apt list docker.io
    Listing... Done
    docker.io/noble-updates,now 28.2.2-0ubuntu1~24.04.1 amd64 [installed]

     

    docker v17.6 needed. Reference: https://docs.armbian.com/Developer-Guide_Building-with-Docker/

  7. 14 hours ago, BoringName said:

    I got emby installed and working. Made it launch with the ir remote, it was all perfect until I tried to play a video :(

     

    Oh :P so I stand corrected... I was going from information on the website: I don't see a Linux client, and in other sites: emby was open source but now it's not

  8. 16 hours ago, BoringName said:

    edit: Ok the instructions in that post did actually work, I just didn't notice one of the commands had not run properly when I first tried it. Video playback in mpv is buttery smooth, now I just need to figure out how to get emby to do the same. 

    You can't use emby and the h618 acceleration with ffmpeg-v4l2request... you need to make emby work under Debian, and tell emby to use mpv.

  9. On 1/31/2026 at 3:45 AM, jock said:

    the problem is not ffmpeg, which already is works totally fine on debian Trixie (and backwards), the problem is within mpv that changed in v0.4.0 carried by debian Trixie,  and at the moment I don't have enough motivation to carry on a custom mpv package for Debian Trixie.

     

    Thank you for the comment Jock :)

    Yes, I know that Trixie's mpv made some changes that made it incompatible with your ffmpeg+v4lrequest package.

     

    I tried to compile mpv, and I wasn't sure of how to do it.

    I asked for help in the mpv github, and someone told me to wait for ffmpeg to merge this function.

    https://github.com/mpv-player/mpv/pull/14690#issuecomment-3369553163

     

    Recently, I got more suggestions to build ffmpeg for Trixie :) https://github.com/mpv-player/mpv/pull/14690#issuecomment-3828170966

     

    Boringname... can you specify which Debian version, Linux kernel and graphical desktop (kde, xfce, gnome, plasma, labwc, sway)?

  10. There was a successful test with Debian Forky in RK3566

    On 11/18/2025 at 2:36 AM, usual user said:

    Backporting is possible, but you will have to deal with the consequences yourself that arise from your outdated versions lacking the functions required for your backport, and you may need to backport those as well.

     

    I saw some progress and success in the last 2 days. Someone made compiled ffmpeg 8.0+v4l2request and made it work in Debian Forky... which also carries ffmpeg 8.0

    https://github.com/mpv-player/mpv/pull/14690#issuecomment-3500141427

    Does this mean that I need to use Debian Forky too? (I was staying with Debian Bookworm because H264 hwaccel only worked there)

     

    References:

    https://code.ffmpeg.org/Kwiboo/FFmpeg/src/branch/v4l2request-v3

    https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20847

    https://tracker.debian.org/pkg/ffmpeg

     

     

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines