1
CorePlus / Re: I'm a beginner. Can I play videos using the iGPU on Tiny Core Linux?
« Last post by sakusaku on Today at 08:22:50 AM »Thank you. I can't do it right now, but I'd like to try it when I'm able to!
cat 20-intel.conf
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "DRI" "crocus"
EndSection
vainfo
Trying display: wayland
Trying display: x11
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/local/lib/dri/iHD_drv_video.so
libva info: va_openDriver() returns -1
libva info: Trying to open /usr/local/lib/dri/i965_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: Intel i965 driver for Intel(R) Haswell Mobile - 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
i.e. H264 is supported.GPU #1
Active Yes
Description Mesa Intel(R) HD Graphics 4400 (HSW GT2)
...
Codec Support Information
Codec Name Software Decoding Hardware Decoding
H264 Supported SupportedAccording to http://repo.tinycorelinux.net/16.x/aarch64/tcz/src/neatvnc/compile_neatvnc, it's compiled with ffmpeg7.
However, its dependencies list libavfilter.tcz instead of libavfilter7.tcz.
* Remove [extension].tcz.md5.txt file
- tce-install will recreate it when installing new extensions that
depend on that extension and try to fix non-matching checksum.
- Have to create dummy extensions for deps you don't want installed
at all, which are used by other version of extensions:
eg.
ls -l llvm*
-r--rw-r-- 1 cnk staff 0 Feb 28 21:50 llvm19-bin.tcz
-r--rw-r-- 1 cnk staff 0 Feb 28 21:50 llvm19-bin.tcz.dep
-r--rw-r-- 1 cnk staff 0 Feb 28 21:50 llvm19-bin.tcz.tcz
-r--rw-r-- 1 cnk staff 0 Feb 28 21:50 llvm19-bin.tcz.tcz.dep
-r--rw-r-- 1 cnk staff 0 Feb 28 22:16 llvm19-dev.tcz
-r--rw-r-- 1 cnk staff 0 Feb 28 22:16 llvm19-dev.tcz.dep
-r--rw-r-- 1 cnk staff 0 Feb 28 21:50 llvm19-lib.tcz
-r--rw-r-- 1 cnk staff 0 Feb 28 21:50 llvm19-lib.tcz.dep
-r--rw-r-- 1 cnk staff 0 Feb 28 21:50 llvm19-lib.tcz.tcz
-r--rw-r-- 1 cnk staff 0 Feb 28 21:50 llvm19-lib.tcz.tcz.dep
- Then tce-install tries to replace them too!
* Make extension files read-only.
- permissions of files inside the tce directory get changed at start-up.
* Make extensions symlinks so they don't get replaced
- symlinks get replaced anyway.
* Add extensions to /etc/sysconfig/tcedir/tcz-black.lst which contains
regexps for grep.
- This may work for tce-update, but isn't checked by tce-install or
update-everything when processing dependencies.
Hi CNK... Both solutions get undone by tce-install, tce-update and tce-audit. ...I was under the impression that customized extensions will be left
unmolested if they don't include a .tcz.md5.txt file.