| View previous topic :: View next topic |
| Author |
Message |
rupeshforu3
n00b
Joined: 19 Aug 2024
Posts: 17
|
 Posted: Thu Oct 24, 2024 2:57 pm Post subject: execution of ffmpeg is taking more time in gentoo than other |
 |
|
Hi I am Rupesh from India and I brought a new PC with AMD Ryzen zen3 5500GT and Asus prime 450 MK2 motherboard. I installed four Linux Operating Systems including gentoo linux and one Windows 11 Operating System. I installed ffmpeg tool along with libaom. Everything is working fine except there is something wrong with ffmpeg execution in Gentoo Linux.
I love working with Linux and Unix Operating Systems and I have lot of disk space and so I have installed four Linux Operating Systems and they are
1) Debian Linux testing Trixie
2) Fedora 40
3) Arch Linux
4) Gentoo Linux with systemd and desktop stage 3
At first I have installed Zen kernel through genkernel utility passing the parameter all.
After installation I have compiled the same ffmpeg source code which is cloned from git and with the same options which includes the following
--enable opencl
--enable opengl
--enable libaom
--enable AMF
--enable gnutils
Etc.,
I have some h264 mp4 files and I want to convert them into aom codec through ffmpeg and libaom.
I tested to convert those same files into aom codec using the same ffmpeg script but ffmpeg in gentoo Linux is taking too much time compared to ffmpeg in remaining Linux Operating Systems.
During the compilation of ffmpeg in gentoo linux I have installed packages related to amdgpu and rocm but unfortunately rocm-opencl-headers failed in installation.
After that I installed clinfo and ran it and it is showing message as Full profile, platform AMD etc.,.
Ffmpeg in other distributions is taking 45 minutes to convert 110 MB h264 mp4 to aom codec mp4 but unfortunately ffmpeg in Gentoo Linux is taking more than 100 minutes.
I can't understand what's wrong with ffmpeg in Gentoo Linux.
Even I have installed amdgpu_top_gui and opened it and it is showing a lot of information about my APU.
If I have not installed anything which is required for ffmpeg to run properly it must fall in compilation but it compiled successfully but it is not working fine.
Kindly try to suggest how to make ffmpeg to work properly and I am ready to provide any diagnostic information of the commands provided by you.
Regards,
Rupesh.
_________________
Regards,
Rupesh. |
|
| Back to top |
|
 |
stefantalpalaru
n00b
Joined: 11 Jan 2009
Posts: 59
Location: Italy
|
| Posted: Thu Oct 24, 2024 5:16 pm Post subject: |
|
|
Make sure you have this set up: https://wiki.gentoo.org/wiki/CPU_FLAGS_*
Since you manually built ffmpeg from source, instead of using an ebuild, I'm going to assume you're a beginner and tell you to also make sure you have sane CFLAGS and CXXFLAGS (like "-O3 -march=native"). |
|
| Back to top |
|
|
molletts
Tux's lil' helper
Joined: 16 Feb 2013
Posts: 129
|
| Posted: Thu Oct 24, 2024 6:09 pm Post subject: |
|
|
Hi Rupesh,
From the magnitude of the difference, I doubt it's related to compiler flags unless you've built the system with "-O0"!
What CPU frequency governor are you using on Gentoo?
To check, use:
| Code: | | # cpupower -c all frequency-info |
(If you get "command not found", you will need to install cpupower with 'emerge sys-power/cpupower'.) This will return a lot of information about your CPU clock frequency, including its current value, which driver is controlling it, which frequency governors are available and which one is in use.
I suspect you may be using the "powersave" governor, which locks the CPU at its slowest speed.
If so, you will need to switch to a different one. If "schedutil" is available, that generally works quite well:
| Code: | | # cpupower -c all frequency-set -g schedutil |
As it's a Zen system, however, there is an AMD-specific cpufreq driver available; I don't know whether this may take over the function of the governor too as the intel_pstate driver does. I don't have access to modern AMD hardware to test it so someone else may have to advise you on how to configure it if this is in use.
Let us know what you find.
Hope this helps,
Stephen |
|
| Back to top |
|
|
rupeshforu3
n00b
Joined: 19 Aug 2024
Posts: 17
|
| Posted: Fri Oct 25, 2024 11:07 am Post subject: |
|
|
Hi I am providing the outputs of the commands specified by you below
| Code: |
build@localhost ~ $ sudo cpupower -c all frequency-info
Password:
analyzing CPU 0:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 4.46 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 4.46 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 4.44 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
Boost States: 0
Total States: 3
Pstate-P0: 3600MHz
Pstate-P1: 1700MHz
Pstate-P2: 1400MHz
analyzing CPU 1:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 4.46 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 4.46 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 4.44 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
Boost States: 0
Total States: 3
Pstate-P0: 3600MHz
Pstate-P1: 1700MHz
Pstate-P2: 1400MHz
analyzing CPU 2:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 2
CPUs which need to have their frequency coordinated by software: 2
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 4.46 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 4.46 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 4.44 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
Boost States: 0
Total States: 3
Pstate-P0: 3600MHz
Pstate-P1: 1700MHz
Pstate-P2: 1400MHz
analyzing CPU 3:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 3
CPUs which need to have their frequency coordinated by software: 3
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 4.46 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 4.46 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 4.44 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
Boost States: 0
Total States: 3
Pstate-P0: 3600MHz
Pstate-P1: 1700MHz
Pstate-P2: 1400MHz
analyzing CPU 4:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 4
CPUs which need to have their frequency coordinated by software: 4
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 4.46 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 4.46 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 4.43 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
Boost States: 0
Total States: 3
Pstate-P0: 3600MHz
Pstate-P1: 1700MHz
Pstate-P2: 1400MHz
analyzing CPU 5:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 5
CPUs which need to have their frequency coordinated by software: 5
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 4.46 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 4.46 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 4.44 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
Boost States: 0
Total States: 3
Pstate-P0: 3600MHz
Pstate-P1: 1700MHz
Pstate-P2: 1400MHz
analyzing CPU 6:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 6
CPUs which need to have their frequency coordinated by software: 6
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 4.46 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 4.46 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 4.44 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
Boost States: 0
Total States: 3
Pstate-P0: 3600MHz
Pstate-P1: 1700MHz
Pstate-P2: 1400MHz
analyzing CPU 7:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 7
CPUs which need to have their frequency coordinated by software: 7
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 4.46 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 4.46 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 4.44 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
Boost States: 0
Total States: 3
Pstate-P0: 3600MHz
Pstate-P1: 1700MHz
Pstate-P2: 1400MHz
analyzing CPU 8:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 8
CPUs which need to have their frequency coordinated by software: 8
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 4.46 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 4.46 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 4.44 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
Boost States: 0
Total States: 3
Pstate-P0: 3600MHz
Pstate-P1: 1700MHz
Pstate-P2: 1400MHz
analyzing CPU 9:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 9
CPUs which need to have their frequency coordinated by software: 9
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 4.46 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 4.46 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 4.44 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
Boost States: 0
Total States: 3
Pstate-P0: 3600MHz
Pstate-P1: 1700MHz
Pstate-P2: 1400MHz
analyzing CPU 10:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 10
CPUs which need to have their frequency coordinated by software: 10
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 4.46 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 4.46 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 4.44 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
Boost States: 0
Total States: 3
Pstate-P0: 3600MHz
Pstate-P1: 1700MHz
Pstate-P2: 1400MHz
analyzing CPU 11:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 11
CPUs which need to have their frequency coordinated by software: 11
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 4.46 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 4.46 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 4.44 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
Boost States: 0
Total States: 3
Pstate-P0: 3600MHz
Pstate-P1: 1700MHz
Pstate-P2: 1400MHz
|
| Code: |
build@localhost ~ $ sudo cpupower -c all frequency-set -g schedutil
Setting cpu: 0
Error setting new values. Common errors:
- Do you have proper administration rights? (super-user?)
- Is the governor you requested available and modprobed?
- Trying to set an invalid policy?
- Trying to set a specific frequency, but userspace governor is not available,
for example because of hardware which cannot be set to a specific frequency
or because the userspace governor isn't loaded?
build@localhost ~ $
|
_________________
Regards,
Rupesh. |
|
| Back to top |
|
|
Goverp
Advocate
Joined: 07 Mar 2007
Posts: 2159
|
| Posted: Fri Oct 25, 2024 11:21 am Post subject: |
|
|
| molletts wrote: | ...
From the magnitude of the difference, I doubt it's related to compiler flags unless you've built the system with "-O0"!
... |
ffmpeg is particularly sensitive to cpu flags, as there are lots of hardware instructions tailored for the sort of vector processing involved (SSE4.2, and host of other flags).
It's almost certainly worth (a) getting good CFLAGS suitable for the hardware and use-case (a whole discussion in itself, visible all over the forums), and (b) using the output of cpuid2cpuflags to tailor make.conf, as ffmpeg is dependent on them too.
_________________
Greybeard |
|
| Back to top |
|
|
Ralphred
l33t
Joined: 31 Dec 2013
Posts: 623
|
| Posted: Fri Oct 25, 2024 12:40 pm Post subject: |
|
|
| molletts wrote: | | As it's a Zen system, however, there is an AMD-specific cpufreq driver available; I don't know whether this may take over the function of the governor too as the intel_pstate driver does. I don't have access to modern AMD hardware to test it so someone else may have to advise you on how to configure it if this is in use. |
For zen3 and later, when using the amd p-state driver you'll get the best results using the powersave governor.
It's worth enabling perfcore on the kernel command line too<< I don't know how many of the p-state features were backported to the 6.6 series of kernels, so I stick to >=6.9.1.
Do not enable any bios overclock of the CPU it gimps the drivers boost function, it will dynamically overclock each core to it's individual capabilities itself. The time boost frequencies can be applied is related to individual core temperature, so a well (thermally) connected cooler that can quickly remove thermal gradients becomes a performance factor (read: don't use the stock cooler for best results). |
|
| Back to top |
|
|
rupeshforu3
n00b
Joined: 19 Aug 2024
Posts: 17
|
| Posted: Fri Oct 25, 2024 1:38 pm Post subject: |
|
|
Hi I am providing the contents of /etc/portage/make.conf below
| Code: |
# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /usr/share/portage/config/make.conf.example for a more
# detailed example.
CHOST="x86_64-pc-linux-gnu"
COMMON_FLAGS="-march=znver3 -O2 -pipe"
CFLAGS="${COMMON_FLAGS}"
CXXFLAGS="${COMMON_FLAGS}"
FCFLAGS="${COMMON_FLAGS}"
FFLAGS="${COMMON_FLAGS}"
MAKEOPTS="--jobs 10 --load-average 9"
VIDEO_CARDS="amdgpu radeonsi"
LICENSE_ACCEPT="*"
# NOTE: This stage was built with the bindist USE flag enabled
# This sets the language of build output to English.
# Please keep this setting intact when reporting bugs.
LC_MESSAGES=C.utf8
GENTOO_MIRRORS="https://mirrors.nxtgen.com/gentoo-mirror/gentoo-source/ \
http://mirrors.nxtgen.com/gentoo-mirror/gentoo-source/ \
rsync://ftp.iij.ad.jp/pub/linux/gentoo/ \
http://ftp.iij.ad.jp/pub/linux/gentoo/"
USE="X systemd elogind udev extras classic upower gtk qt contrib vaapi"
|
Upto now I have not used cpuid2cpuflags but now I installed it and I am providing its output below
| Code: |
build@localhost ~ $ cpuid2cpuflags
CPU_FLAGS_X86: aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt rdrand sha sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 vpclmulqdq
build@localhost ~ $
|
For your reference I am providing the output of commands entered in Fedora 40 below so that you may find the reason. Ffmpeg is working properly in this Linux.
| Code: |
work@fedora:~$ sudo cpupower -c all frequency-info
analyzing CPU 0:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 3.60 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 3.60 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 3.57 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: no
AMD PSTATE Highest Performance: 166. Maximum Frequency: 4.46 GHz.
AMD PSTATE Nominal Performance: 134. Nominal Frequency: 3.60 GHz.
AMD PSTATE Lowest Non-linear Performance: 88. Lowest Non-linear Frequency: 2.36 GHz.
AMD PSTATE Lowest Performance: 15. Lowest Frequency: 400 MHz.
analyzing CPU 1:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 3.60 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 3.60 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 3.57 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: no
AMD PSTATE Highest Performance: 166. Maximum Frequency: 4.46 GHz.
AMD PSTATE Nominal Performance: 134. Nominal Frequency: 3.60 GHz.
AMD PSTATE Lowest Non-linear Performance: 88. Lowest Non-linear Frequency: 2.36 GHz.
AMD PSTATE Lowest Performance: 15. Lowest Frequency: 400 MHz.
analyzing CPU 2:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 2
CPUs which need to have their frequency coordinated by software: 2
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 3.60 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 3.60 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 3.57 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: no
AMD PSTATE Highest Performance: 166. Maximum Frequency: 4.46 GHz.
AMD PSTATE Nominal Performance: 134. Nominal Frequency: 3.60 GHz.
AMD PSTATE Lowest Non-linear Performance: 88. Lowest Non-linear Frequency: 2.36 GHz.
AMD PSTATE Lowest Performance: 15. Lowest Frequency: 400 MHz.
analyzing CPU 3:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 3
CPUs which need to have their frequency coordinated by software: 3
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 3.60 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 3.60 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 3.57 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: no
AMD PSTATE Highest Performance: 166. Maximum Frequency: 4.46 GHz.
AMD PSTATE Nominal Performance: 134. Nominal Frequency: 3.60 GHz.
AMD PSTATE Lowest Non-linear Performance: 88. Lowest Non-linear Frequency: 2.36 GHz.
AMD PSTATE Lowest Performance: 15. Lowest Frequency: 400 MHz.
analyzing CPU 4:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 4
CPUs which need to have their frequency coordinated by software: 4
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 3.60 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 3.60 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 3.56 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: no
AMD PSTATE Highest Performance: 166. Maximum Frequency: 4.46 GHz.
AMD PSTATE Nominal Performance: 134. Nominal Frequency: 3.60 GHz.
AMD PSTATE Lowest Non-linear Performance: 88. Lowest Non-linear Frequency: 2.36 GHz.
AMD PSTATE Lowest Performance: 15. Lowest Frequency: 400 MHz.
analyzing CPU 5:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 5
CPUs which need to have their frequency coordinated by software: 5
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 3.60 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 3.60 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 3.57 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: no
AMD PSTATE Highest Performance: 166. Maximum Frequency: 4.46 GHz.
AMD PSTATE Nominal Performance: 134. Nominal Frequency: 3.60 GHz.
AMD PSTATE Lowest Non-linear Performance: 88. Lowest Non-linear Frequency: 2.36 GHz.
AMD PSTATE Lowest Performance: 15. Lowest Frequency: 400 MHz.
analyzing CPU 6:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 6
CPUs which need to have their frequency coordinated by software: 6
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 3.60 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 3.60 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 3.57 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: no
AMD PSTATE Highest Performance: 166. Maximum Frequency: 4.46 GHz.
AMD PSTATE Nominal Performance: 134. Nominal Frequency: 3.60 GHz.
AMD PSTATE Lowest Non-linear Performance: 88. Lowest Non-linear Frequency: 2.36 GHz.
AMD PSTATE Lowest Performance: 15. Lowest Frequency: 400 MHz.
analyzing CPU 7:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 7
CPUs which need to have their frequency coordinated by software: 7
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 3.60 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 3.60 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 3.57 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: no
AMD PSTATE Highest Performance: 166. Maximum Frequency: 4.46 GHz.
AMD PSTATE Nominal Performance: 134. Nominal Frequency: 3.60 GHz.
AMD PSTATE Lowest Non-linear Performance: 88. Lowest Non-linear Frequency: 2.36 GHz.
AMD PSTATE Lowest Performance: 15. Lowest Frequency: 400 MHz.
analyzing CPU 8:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 8
CPUs which need to have their frequency coordinated by software: 8
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 3.60 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 3.60 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 3.57 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: no
AMD PSTATE Highest Performance: 166. Maximum Frequency: 4.46 GHz.
AMD PSTATE Nominal Performance: 134. Nominal Frequency: 3.60 GHz.
AMD PSTATE Lowest Non-linear Performance: 88. Lowest Non-linear Frequency: 2.36 GHz.
AMD PSTATE Lowest Performance: 15. Lowest Frequency: 400 MHz.
analyzing CPU 9:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 9
CPUs which need to have their frequency coordinated by software: 9
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 3.60 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 3.60 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 3.57 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: no
AMD PSTATE Highest Performance: 166. Maximum Frequency: 4.46 GHz.
AMD PSTATE Nominal Performance: 134. Nominal Frequency: 3.60 GHz.
AMD PSTATE Lowest Non-linear Performance: 88. Lowest Non-linear Frequency: 2.36 GHz.
AMD PSTATE Lowest Performance: 15. Lowest Frequency: 400 MHz.
analyzing CPU 10:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 10
CPUs which need to have their frequency coordinated by software: 10
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 3.60 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 3.60 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 3.57 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: no
AMD PSTATE Highest Performance: 166. Maximum Frequency: 4.46 GHz.
AMD PSTATE Nominal Performance: 134. Nominal Frequency: 3.60 GHz.
AMD PSTATE Lowest Non-linear Performance: 88. Lowest Non-linear Frequency: 2.36 GHz.
AMD PSTATE Lowest Performance: 15. Lowest Frequency: 400 MHz.
analyzing CPU 11:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 11
CPUs which need to have their frequency coordinated by software: 11
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 3.60 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 3.60 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 3.57 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: no
AMD PSTATE Highest Performance: 166. Maximum Frequency: 4.46 GHz.
AMD PSTATE Nominal Performance: 134. Nominal Frequency: 3.60 GHz.
AMD PSTATE Lowest Non-linear Performance: 88. Lowest Non-linear Frequency: 2.36 GHz.
AMD PSTATE Lowest Performance: 15. Lowest Frequency: 400 MHz.
work@fedora:~$
|
| Code: |
work@fedora:~$ sudo cpupower -c all frequency-set -g schedutil
Setting cpu: 0
Error setting new values. Common errors:
- Do you have proper administration rights? (super-user?)
- Is the governor you requested available and modprobed?
- Trying to set an invalid policy?
- Trying to set a specific frequency, but userspace governor is not available,
for example because of hardware which cannot be set to a specific frequency
or because the userspace governor isn't loaded?
work@fedora:~$
|
Kindly try to suggest how to make ffmpeg properly work in Gentoo.
_________________
Regards,
Rupesh. |
|
| Back to top |
|
|
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 5007
Location: Bavaria
|
| Posted: Fri Oct 25, 2024 2:45 pm Post subject: |
|
|
| rupeshforu3 wrote: | | Kindly try to suggest how to make ffmpeg properly work in Gentoo. |
If an application in your Gentoo Linux has performance problems, this can have two possible causes: The application itself has been “badly” compiled, or your Linux system / kernel is “unfavorably” configured. For example, you have a setting that is impossible (because the two use flags are mutually exclusive = you can only activate one of them):
| Code: | | USE="... systemd elogind ..." |
We need a lot more information to be able to check your configuration comprehensively:
1. Give us all 3 files mentioned here:
https://wiki.gentoo.org/wiki/User:Pietinger/Overview_of_System_Information
(note the reference to wgetpaste for your "dmesg"-output)
2. If you have configured the kernel yourself manually, we need its .config (also with wgetpaste)
3. The output of (also with wgetpaste):
| Code: | | # grep -r --exclude-dir=savedconfig "" /etc/portage |
_________________
https://wiki.gentoo.org/wiki/User:Pietinger |
|
| Back to top |
|
|
sam_
Developer
Joined: 14 Aug 2020
Posts: 1926
|
| Posted: Fri Oct 25, 2024 2:50 pm Post subject: |
|
|
| To elaborate on what others have said, this essentially can't be Gentoo "specific" other than kernel configuration if you're building manually from source and not using the ebuilds. |
|
| Back to top |
|
|
stefantalpalaru
n00b
Joined: 11 Jan 2009
Posts: 59
Location: Italy
|
|
| Back to top |
|
|
Ralphred
l33t
Joined: 31 Dec 2013
Posts: 623
|
| Posted: Fri Oct 25, 2024 3:08 pm Post subject: |
|
|
| stefantalpalaru wrote: | | You are, obviously, wrong. |
You obviously haven't read the kernel docs on the amd p-state driver.
| stefantalpalaru wrote: | | Linking articles about kernels before the driver was implemented |
Yes, excellent. |
|
| Back to top |
|
|
stefantalpalaru
n00b
Joined: 11 Jan 2009
Posts: 59
Location: Italy
|
| Posted: Fri Oct 25, 2024 3:32 pm Post subject: |
|
|
| Ralphred wrote: | | Do not enable any bios overclock of the CPU it gimps the drivers boost function, it will dynamically overclock each core to it's individual capabilities itself. |
You need to stop trolling that poor guy who doesn't understand USE flags yet. This is not 4chan. |
|
| Back to top |
|
|
rupeshforu3
n00b
Joined: 19 Aug 2024
Posts: 17
|
| Posted: Fri Oct 25, 2024 3:45 pm Post subject: |
|
|
I haven't compiled kernel source code manually.
After extraction of stage 3 tarball I installed kernel sources bin package and installed other packages like iwd, dhcpcd etc ,.
After that I booted successfully into my system and in non root account
1) I installed Zen kernel package and genkernel utility.
2) I made a symbolic link as linux-->zen sources under /usr/src directory.
3) I issued the command sudo genkernel all
4) Finally the above utility compiled and installed Zen kernel 6.10
But at that time it shown error as something went wrong but I neglected.
_________________
Regards,
Rupesh. |
|
| Back to top |
|
|
rupeshforu3
n00b
Joined: 19 Aug 2024
Posts: 17
|
| Posted: Fri Oct 25, 2024 3:55 pm Post subject: |
|
|
output of commands through wgetpaste
build@localhost ~ $ wgetpaste --command 'emerge --info'
Your paste can be seen here: https://bpa.st/LJPA
build@localhost ~ $ wgetpaste --command 'dmesg'
Your paste can be seen here: https://bpa.st/2BRA
build@localhost ~ $ wgetpaste --command 'lspci -nnk'
Your paste can be seen here: https://bpa.st/LF7A
build@localhost ~ $
_________________
Regards,
Rupesh. |
|
| Back to top |
|
|
stefantalpalaru
n00b
Joined: 11 Jan 2009
Posts: 59
Location: Italy
|
| Posted: Fri Oct 25, 2024 4:01 pm Post subject: |
|
|
| rupeshforu3 wrote: | | Kindly try to suggest how to make ffmpeg properly work in Gentoo. |
Add the output of "cpuid2cpuflags" to "/etc/portage/make.conf", then rebuild all affected packages with "emerge -uDUav @world". |
|
| Back to top |
|
|
|
Kernel & Hardware
