22 minutes ago, ich777 said:

Please try to use VAAPI instead of QSV if you are using QSV

I have always used VAAPI.

43 minutes ago, G0ku737 said:

For that part not so strange..but..it worked before..the exact same files.

What do you mean with before? Are you sure that this is caused by the update to 10.8.0?

 

Have you yet tried to disable transcoding to h265?

14 minutes ago, ich777 said:

What do you mean with before? Are you sure that this is caused by the update to 10.8.0?

 

Have you yet tried to disable transcoding to h265?

 

With before i mean that i watched the same files/episodes a few weeks ago and after i got the errors on newer episodes i tried older ones that i certainly knew worked before and got the same error.

 

in the screenshot are my settings:

13 hours ago, 9to5crypto said:

You're right, sorry about that. Here's the diagnotics zip file and a pastebin of Jellyfin's log file. 

Please remove this line from your go file:

modprobe i915

because you have installed the Intel-GPU-TOP plugin and it will actually enable your iGPU if needed.

 

I would strongly recommend that you upgrade to Unraid 6.10.3 too.

 

Please also post a screenshot from your Jellyfin Playback section.

13 hours ago, G0ku737 said:

With before i mean that i watched the same files/episodes a few weeks ago and after i got the errors on newer episodes i tried older ones that i certainly knew worked before and got the same error.

Can you post your Diagnostics please? On what Unraid version are you? What CPU are you using...?

 

I've now tested it on my i5-10600 and everything works as expected.

3 hours ago, ich777 said:

Please remove this line from your go file:

modprobe i915

because you have installed the Intel-GPU-TOP plugin and it will actually enable your iGPU if needed.

 

I would strongly recommend that you upgrade to Unraid 6.10.3 too.

 

Please also post a screenshot from your Jellyfin Playback section.

Thanks for the suggestions! I've removed the line from the go file and upgraded Unraid but that did not affect my problem, which is still there. Here are the screenshots of the playback section (I've already tried changing the tone mapping algorithm and disabling encoding to HEVC).

3 minutes ago, 9to5crypto said:

I've already tried changing the tone mapping algorithm and disabling encoding to HEVC

Please switch from QSV to VA-API and disable "Allow encoding in HEVC format".

27 minutes ago, ich777 said:

Please switch from QSV to VA-API and disable "Allow encoding in HEVC format".

It gives the same error as with QSV in the Jellyfin log file unfortunately. (ffmpeg exited with code 139)

1 minute ago, 9to5crypto said:

It gives the same error as with QSV in the Jellyfin log file unfortunately. (ffmpeg exited with code 139)

Can you send a log with VA-API, I really recommend to use VA-API instead of QSV!

 

Have you already upgraded to 6.10.3?

30 minutes ago, ich777 said:

Can you send a log with VA-API, I really recommend to use VA-API instead of QSV!

 

Have you already upgraded to 6.10.3?

Yes I've upgraded Unraid to 6.10.3 without issues. Here's the pastebin of the log with VA-API.

8 minutes ago, 9to5crypto said:

Yes I've upgraded Unraid to 6.10.3 without issues. Here's the pastebin of the log with VA-API.

You got a 139 Error, this actually means that ffMPEG crashed before it exited.

 

Have you yet tried the official Jellyfin container for testing purposes if it's the same there too?

Have you already tried another file too?

19 minutes ago, ich777 said:

You got a 139 Error, this actually means that ffMPEG crashed before it exited.

 

Have you yet tried the official Jellyfin container for testing purposes if it's the same there too?

Have you already tried another file too?

I've tried many files and I always get the same error but I haven't tried the official Jellyfin container yet. I'm going to try that and let you know if it works. Thanks a lot!

38 minutes ago, ich777 said:

You got a 139 Error, this actually means that ffMPEG crashed before it exited.

 

Have you yet tried the official Jellyfin container for testing purposes if it's the same there too?

Have you already tried another file too?

The official image seems to be working fine... I've found this line:

[AVHWDeviceContext @ 0x55e374aee140] QSV to OpenCL mapping not usable.

in the log of ffmpeg with your container, which could be the problem. I have no idea what causes that though.

17 minutes ago, 9to5crypto said:

in the log of ffmpeg with your container, which could be the problem. I have no idea what causes that though.

Can you please try to install a second instance from my container with different directories and a different name?

This wouldn't be the first time I see that some changes break the container and it wont transcode for whatever reason.

 

And please use VA-API and not QSV!

24 minutes ago, ich777 said:

Can you please try to install a second instance from my container with different directories and a different name?

This wouldn't be the first time I see that some changes break the container and it wont transcode for whatever reason.

 

And please use VA-API and not QSV!

I've just tried that and I always get the same ffmpeg crash. By the way I was already using VA-API when I got that error message about "QSV to OpenCL mapping not usable", while I don't get it in the default container, so that's why I think that might be the issue.

32 minutes ago, 9to5crypto said:

I've just tried that and I always get the same ffmpeg crash. By the way I was already using VA-API when I got that error message about "QSV to OpenCL mapping not usable", while I don't get it in the default container, so that's why I think that might be the issue.

Then I would recommend to stick with the official container, since they now also have AMD GPU support I think I will deprecate my container sometime in the near future since I've mainly created this container for the users with AMD GPUs because the official one hadn't support for that.

14 minutes ago, ich777 said:

Then I would recommend to stick with the official container, since they now also have AMD GPU support I think I will deprecate my container sometime in the near future since I've mainly created this container for the users with AMD GPUs because the official one hadn't support for that.

Got it. Thanks anyways for your help!

8 hours ago, ich777 said:

Can you post your Diagnostics please? On what Unraid version are you? What CPU are you using...?

 

I've now tested it on my i5-10600 and everything works as expected.

 

Here you go:

 

Unraid Version: 6.10.3

Jellyfin Version: 10.8.0

APU: AMD Ryzen 3 PRO 4350GE with Radeon Graphics

 

 

As i said it worked before with the same files.

One Evening i wanted to watch new episodes and then the issue was there.

Strangely not only on the new episodes but also on the ones i watched before without any issues.

 

Sadly i cant tell you what exacly was changed/done before the error first appeared.

Settings were not changed but updates might have been done.

 

g0ku737-diagnostics-20220623-1914.zip

5 minutes ago, G0ku737 said:

Sadly i cant tell you what exacly was changed/done before the error first appeared.

Can you please also try the official Jellyfin container too because the officially support now AMD GPUs and see if it is working there?

29 minutes ago, ich777 said:

Can you please also try the official Jellyfin container too because the officially support now AMD GPUs and see if it is working there?

Sure, i will try it out and give you feedback.

On 6/23/2022 at 7:26 PM, ich777 said:

Can you please also try the official Jellyfin container too because the officially support now AMD GPUs and see if it is working there?

 I tested the official container and get the same error when HW Acceleration ist enabled. 

Hi @ich777

 

First of all, big thanks for your version of Jellyfin. I use it on my new small Unraid media server build on an MinisForum HM90 mini PC. It uses an Renoir Zen 2 based Ryzen 9 4900H with Radeon RX Vega 8 Graphics.

 

After some issues with your default port mappings 8096 > 8096 and 8920 > 8920 I now have access to the WebUI. I had to adjust the Ports to 18096 and 18920 for me to have access. Not sure whats wrong with the default mappings and my network config. I tried bridged, br0 and a custom network, same problem on all of them with the default ports.

 

I installed the "Radeon TOP" and "GPU statistics" plugins to check the stats on the dashboard and with "radeontop" via terminal. Jellyfin statistics is showing the transcoding with 65fps.

 

GPU statistics 4k source:

 

 

radeontop idle:

 

radeontop transcoding 4K source file:

 

It looks like the GPU transcoding is working even without the adjustment of the go file. 👍

Jellyfin statistics is showing the transcoding with 65fps.

 

I have also installed the "Dynamix System Temperature" and your "Nuvoton NCT6687 Driver" plugin. Unfortunately the temperature plugin doesn't find any drivers, so I have no fan or CPU temp monitoring available. Any ideas what I'am missing? If I shoud test some stuff for you, please let me know. Maybe you can add the 4900H to the list of supported hardware. 😉

 

 

9 minutes ago, bastl said:

even without the adjustment of the go file.

Exactly, that does the RadeonTOP plug for you.

 

10 minutes ago, bastl said:

Unfortunately the temperature plugin doesn't find any drivers, so I have no fan or CPU temp monitoring available. Any ideas what I'am missing?

Nope, those newer chips can be a bit complicated on Linux…

Research the forum for your exact chip and see if others have got it to work and of course what they‘ve did.

19 minutes ago, ich777 said:

Research the forum for your exact chip

Thanks for the quick answer. I already searched the forums. 😂

searching for "4900H" brings up nothing.

"HM90" only a single guy with boot issues

"minisforum" a couple people asking for compatibility, passthrough and setup for unraid, nothing related

 

not sure where to start.

 

"sensors" gives me the following output

root@mini:~# sensors
amdgpu-pci-0600
Adapter: PCI adapter
vddgfx:      699.00 mV 
vddnb:       874.00 mV 
edge:         +45.0°C  
slowPPT:     1000.00 uW 

k10temp-pci-00c3
Adapter: PCI adapter
Tctl:         +61.0°C  

nvme-pci-0100
Adapter: PCI adapter
Composite:    +47.9°C  (low  =  -0.1°C, high = +84.8°C)
                       (crit = +94.8°C)

 

"k10temp-pci-00c3" might be the CPU temp sensor for the 4900H. If i stress the CPU it spikes up. Question is how to load/unload the driver and set it up correctly for the plugin to register and how do I find the fan sensor.

 

questions questions question 🙄

 

running "sensors-detect"

root@mini:~# sensors-detect
# sensors-detect version 3.6.0
# System: BESSTAR TECH LIMITED HM90 [Default string]
# Kernel: 5.15.46-Unraid x86_64
# Processor: AMD Ryzen 9 4900H with Radeon Graphics (23/96/1)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): YES
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): YES
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      Yes
Found `ITE IT8613E Super IO Sensors'                        Success!
    (address 0xa30, driver `to-be-written')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): YES
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): yes
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): YES
Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus
Module i2c-dev loaded successfully.

Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0)
Do you want to scan it? (yes/NO/selectively): yes
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No
Client found at address 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)

Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-1)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: SMBus PIIX4 adapter port 1 at 0b20 (i2c-2)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AMDGPU DM i2c hw bus 0 (i2c-3)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AMDGPU DM i2c hw bus 1 (i2c-4)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AMDGPU DM i2c hw bus 2 (i2c-5)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AMDGPU DM i2c hw bus 3 (i2c-6)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AMDGPU DM aux hw bus 1 (i2c-7)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AMDGPU DM aux hw bus 2 (i2c-8)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AMDGPU DM aux hw bus 3 (i2c-9)
Do you want to scan it? (yes/NO/selectively): yes


Now follows a summary of the probes I have just done.
Just press ENTER to continue: 

Driver `to-be-written':
  * ISA bus, address 0xa30
    Chip `ITE IT8613E Super IO Sensors' (confidence: 9)

Note: there is no driver for ITE IT8613E Super IO Sensors yet.
Check https://hwmon.wiki.kernel.org/device_support_status for updates.

No modules to load, skipping modules configuration.

Unloading i2c-dev... OK

 

Just now, bastl said:

Thanks for the quick answer. I already searched the forums. 😂

searching for "4900H" brings up nothing.

You should search for the exact Nuvoton chip, you should be able to see it on your Motherboard, if it is a Nuvoton chip.

But from what I see you have a ITE chip on your Motherboard and this is another manufacturer.

 

Also this is completely OT and not the right thread for this, please post in the SystemTemp plugin support thread.