WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Recent Posts

Pages: 1 2 3 [4] 5 6 ... 10
31
TCB Q&A Forum / Video Acceleration is important???
« Last post by nixHobbyist on June 28, 2025, 02:45:19 AM »
   Hi guys (it's my first TCL post),  I have problem of missing H264 profile in vainfo (TCL 16.0 64bit) which shows me only MPEG2 profiles (vdpauinfo show similar results) but on the same (one and only computer that I have) there are also installations of Debian 12 and OpenSUSE Leap 15.5 and both of them have working profiles H.264 and VC1, with radeon driver with same parametars.
MPV player shows me this:
[ffmpeg/video] h264: No support for codec h264 profile 100.

Code: [Select]
tc@box:~$ vainfo
Trying display: wayland
Trying display: x11
libva info: VA-API version 1.22.0
libva info: User environment variable requested driver 'radeonsi'
libva info: Trying to open /usr/local/lib/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.22 (libva 2.22.0)
vainfo: Driver version: Mesa Gallium driver 24.1.7 for OLAND (radeonsi, , LLVM 19.1.0, DRM 2.50, 6.12.11-tinycore64)
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileNone                   : VAEntrypointVideoProc

  I also have 32 bit TCL which also gave identical vainfo, vdpauinfo result!

Maybe is a patent legal problem, for example on these links:
https://www.phoronix.com/news/Fedora-Disable-Bad-VA-API
https://forum.manjaro.org/t/libva-mesa-driver-pkgbase-mesa-regression-broken-support-for-video-hw-encoding-decoding/142835/2
https://forum.endeavouros.com/t/compiling-mesa-22-2-with-codec-support-the-easy-way/30390/17

Do I have to compile_mesa script?   (with h264dec)

32
General TC Talk / Re: I have achieved TinyCore Nirvana!
« Last post by PDP-8 on June 26, 2025, 08:38:14 PM »
Provided for your entertainment on this frankenbox:

Wifi at least is solved in this box.  I was following Vaguiner's thread about vaapi and so forth with his N100 cpu box.

I added intel-media.tcz to my onboot.  Now, with wifi.tcz in the onDEMAND arena, when I reboot, wifi comes right up without me having to actuate it.  Um, ok, what I wanted but not like this.

I have determined that the entire issue is not with TC, but that I might be in a parallel universe, where things are just slightly different.  :)
33
Other architectures / Re: Which board to support?
« Last post by Yleisajattelija on June 26, 2025, 04:56:10 PM »
Kernel ver. 6.12 has some very interesting RT-features:

https://kernelnewbies.org/Linux_6.12

Interrupt handlers are in kernel thread etc.:

https://www.linutronix.de/videos/introduction-to-realtime-linux.mp4?m=1586192378&

That VLSI Solutions board uses currently 6.1, but natural goal is 6,12 with RT.
34
Corepure64 / Re: No luck with vaapi
« Last post by Vaguiner on June 26, 2025, 11:17:51 AM »

Hi. Thanks for the replies. The problem really was outdated intel-media. I managed to update both intel-media and intel-gmmlib and it worked again:

Code: [Select]
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/local/lib/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0
Trying display: wayland
Trying display: x11
vainfo: VA-API version: 1.22 (libva 2.22.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 25.1.4 ()
vainfo: Supported profile and entrypoints
      VAProfileNone                   : VAEntrypointVideoProc
      VAProfileNone                   : VAEntrypointStats
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Simple            : VAEntrypointEncSlice
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointFEI
      VAProfileH264Main               : VAEntrypointEncSliceLP
      VAProfileH264High               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointEncSlice
      VAProfileH264High               : VAEntrypointFEI
      VAProfileH264High               : VAEntrypointEncSliceLP
      VAProfileVC1Simple              : VAEntrypointVLD
      VAProfileVC1Main                : VAEntrypointVLD
      VAProfileVC1Advanced            : VAEntrypointVLD
      VAProfileJPEGBaseline           : VAEntrypointVLD
      VAProfileJPEGBaseline           : VAEntrypointEncPicture
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline: VAEntrypointFEI
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
      VAProfileVP8Version0_3          : VAEntrypointVLD
      VAProfileHEVCMain               : VAEntrypointVLD
      VAProfileHEVCMain               : VAEntrypointEncSlice
      VAProfileHEVCMain               : VAEntrypointFEI
      VAProfileHEVCMain               : VAEntrypointEncSliceLP
      VAProfileHEVCMain10             : VAEntrypointVLD
      VAProfileHEVCMain10             : VAEntrypointEncSlice
      VAProfileHEVCMain10             : VAEntrypointEncSliceLP
      VAProfileVP9Profile0            : VAEntrypointVLD
      VAProfileVP9Profile0            : VAEntrypointEncSliceLP
      VAProfileVP9Profile1            : VAEntrypointVLD
      VAProfileVP9Profile1            : VAEntrypointEncSliceLP
      VAProfileVP9Profile2            : VAEntrypointVLD
      VAProfileVP9Profile2            : VAEntrypointEncSliceLP
      VAProfileVP9Profile3            : VAEntrypointVLD
      VAProfileVP9Profile3            : VAEntrypointEncSliceLP
      VAProfileHEVCMain12             : VAEntrypointVLD
      VAProfileHEVCMain12             : VAEntrypointEncSlice
      VAProfileHEVCMain422_10         : VAEntrypointVLD
      VAProfileHEVCMain422_10         : VAEntrypointEncSlice
      VAProfileHEVCMain422_12         : VAEntrypointVLD
      VAProfileHEVCMain422_12         : VAEntrypointEncSlice
      VAProfileHEVCMain444            : VAEntrypointVLD
      VAProfileHEVCMain444            : VAEntrypointEncSliceLP
      VAProfileHEVCMain444_10         : VAEntrypointVLD
      VAProfileHEVCMain444_10         : VAEntrypointEncSliceLP
      VAProfileHEVCMain444_12         : VAEntrypointVLD
      VAProfileHEVCSccMain            : VAEntrypointVLD
      VAProfileHEVCSccMain            : VAEntrypointEncSliceLP
      VAProfileHEVCSccMain10          : VAEntrypointVLD
      VAProfileHEVCSccMain10          : VAEntrypointEncSliceLP
      VAProfileHEVCSccMain444         : VAEntrypointVLD
      VAProfileHEVCSccMain444         : VAEntrypointEncSliceLP
      VAProfileAV1Profile0            : VAEntrypointVLD
      VAProfileHEVCSccMain444_10      : VAEntrypointVLD
      VAProfileHEVCSccMain444_10      : VAEntrypointEncSliceLP

iHD is required for:

Code: [Select]
    BDW (Broadwell)
    SKL (Skylake)
    BXTx (BXT: Broxton, APL: Apollo Lake, GLK: Gemini Lake)
    KBLx (KBL: Kaby Lake, CFL: Coffee Lake, WHL: Whiskey Lake, CML: Comet Lake, AML: Amber Lake)
    ICL (Ice Lake)
    JSL (Jasper Lake) / EHL (Elkhart Lake)
    TGLx (TGL: Tiger Lake, RKL: Rocket Lake, ADL-S/P/N: Alder Lake, RPL-S/P: Raptor Lake)
    DG1/SG1
    Alchemist(DG2)/ATSM
    MTLx (MTL: Meteor Lake, ARL-S/H: Arrow Lake)
    LNL (Lunar Lake)
    BMG (Battlemage)
35
Raspberry Pi / Re: gnupg.tcz missing deps in PiCore aarch64 16
« Last post by Rich on June 26, 2025, 11:09:22 AM »
Hi CNK
I added bzip2-lib.tcz and sqlite3.tcz to gnupg.tcz.dep in piCore16.

Thank you for reporting this.
36
Raspberry Pi / gnupg.tcz missing deps in PiCore aarch64 16
« Last post by CNK on June 26, 2025, 10:12:05 AM »
gpg from gnupg.tcz in PiCore 16 (aarch64) fails to start without bzip2-lib.tcz and sqlite3.tcz loaded:

Code: [Select]
$ ldd `which gpg`
        linux-vdso.so.1 (0x0000007fb14a5000)
        libz.so.1 => /usr/lib/libz.so.1 (0x0000007fb1420000)
        libbz2.so.1.0 => not found
        libsqlite3.so.0 => not found
        libgcrypt.so.20 => /usr/local/lib/libgcrypt.so.20 (0x0000007fb1350000)
        libgpg-error.so.0 => /usr/local/lib/libgpg-error.so.0 (0x0000007fb1310000)
        libreadline.so.8 => /usr/local/lib/libreadline.so.8 (0x0000007fb12a0000)
        libncursesw.so.6 => /usr/local/lib/libncursesw.so.6 (0x0000007fb1220000)
        libassuan.so.0 => /usr/local/lib/libassuan.so.0 (0x0000007fb11f0000)
        libc.so.6 => /lib/libc.so.6 (0x0000007fb1070000)
        /lib/ld-linux-aarch64.so.1 (0x0000007fb1460000)

I suggest that bzip2-lib.tcz and sqlite3.tcz are added to gnupg.tcz.dep for PiCore 16.
37
Corepure64 / Re: No luck with vaapi
« Last post by CNK on June 26, 2025, 04:15:00 AM »
i965 is not compatible with my integrated video, iHD is recommended.

For me it's the other way 'round, my GPU only works with the i965 VAAPI driver. However I need to load xf86-video-intel.tcz to get VAAPI to work, so try that if you haven't already got it installed.

I'm not sure if that would explain the error you get for iHD_drv_video.so though. For me iHD would load but init failed like you get with i965, but that was in an old TC version.

Also I ran the vainfo command as root, though I'm not sure if that was necessary.

Tips from my own VAAPI debugging:

Force using a particular VAAPI driver like this:
Code: [Select]
# LIBVA_DRIVER_NAME=i965 vainfo -a
# LIBVA_DRIVER_NAME=iHD vainfo -a

If the DISPLAY environment variable is set to a remote display (eg. "ssh -X"), vainfo shows drivers failing with "init failed". You need to unset DISPLAY like this:
Code: [Select]
# DISPLAY= LIBVA_DRIVER_NAME=i965 vainfo
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: can't connect to X server!
libva info: VA-API version 1.13.0
libva info: User environment variable requested driver 'i965'
libva info: Trying to open /usr/local/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_12
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.13 (libva 2.13.0)
vainfo: Driver version: Intel i965 driver for Intel(R) CherryView - 2.4.1
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Simple            : VAEntrypointEncSlice
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointEncSlice
      VAProfileH264High               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointEncSlice
      VAProfileH264MultiviewHigh      : VAEntrypointVLD
      VAProfileH264MultiviewHigh      : VAEntrypointEncSlice
      VAProfileH264StereoHigh         : VAEntrypointVLD
      VAProfileH264StereoHigh         : VAEntrypointEncSlice
      VAProfileVC1Simple              : VAEntrypointVLD
      VAProfileVC1Main                : VAEntrypointVLD
      VAProfileVC1Advanced            : VAEntrypointVLD
      VAProfileNone                   : VAEntrypointVideoProc
      VAProfileJPEGBaseline           : VAEntrypointVLD
      VAProfileJPEGBaseline           : VAEntrypointEncPicture
      VAProfileVP8Version0_3          : VAEntrypointVLD
      VAProfileVP8Version0_3          : VAEntrypointEncSlice
      VAProfileHEVCMain               : VAEntrypointVLD

It took me ages to figure that out, but I guess it's mainly a "just me" problem. Probably not many others trying to use VAAPI while connecting remotely with X windows displaying over the network.
38
Other architectures / Re: Which board to support?
« Last post by Yleisajattelija on June 26, 2025, 03:09:18 AM »
I received yesterday VLSI Solutions RISC-V32 CAT Board (VSRVE01). Very fast delivery, it ready for tc port right now.

At first glance this stuff is very pro, it is targeted  for mobile phone android coders, and documentation is very minimal and good. I suppose, linux kernel is installed in "raw format" and single core.

There is another operating system on board for codec, but  I think linux side can be operated stand alone.

There is discussion forum:

https://www.vsdsp-forum.com/phpbb/index.php

..and product pages

https://www.vlsi.fi/en/products/vsrves01.html

Unfortunatelly there might be some privilegies set for these pages.

I can recommend this board for tc port, is is very minimalistic and very professionally documented.
39
Corepure64 / Re: No luck with vaapi
« Last post by gadget42 on June 26, 2025, 12:52:30 AM »
another user mentions the n100 here regarding a potential heat dissipation deficiency with respect to an unintentional air gap between the cpu and heatsink:

https://forum.tinycorelinux.net/index.php/topic,21033.msg179070.html#msg179070
40
General TC Talk / Re: Noob ID10T question
« Last post by gadget42 on June 26, 2025, 12:42:55 AM »
also you might check out this short thread:

https://forum.tinycorelinux.net/index.php/topic,27625.0.html
Pages: 1 2 3 [4] 5 6 ... 10