crushleorey
-
Posts
12 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by crushleorey
-
-
6 hours ago, Jacon said:
Happens with every file...HEVC 4K, VC1 1080p, etc.
Plex mods recommend I downgrade to 510.85.02 but that's obviously not an option with the plugin.
What model is your graphics card?
Is there an encoder?
For Nvidia, you can visit here:
https://developer.nvidia.com/video-encode-and-decode-gpu-support-matrix-new -
8 minutes ago, ich777 said:
I have already posted how to do it here (a few posts above):
Please don‘t forget to reboot after you‘ve added the lines to the go file.
Thank you, I will try
Also wait for the new BIOS to be released- 1
-
11 minutes ago, ich777 said:
No, that means this is a hardware combination issue, it may be possible that another card eg: PCIe Sound Card, PCIe TV Card, PCIe USB Card,... can cause such messages too.
This is actually a bug in the firmware (BIOS) from your motherboard and need to be fixed by the manufacturer.
It is also possible that a T600 from another manufacturer or OEM is working just fine.
My graphics card manufacturer is DELL
Thank you
Looking forward to your solutionThis problem has been bugging me for a week
-
36 minutes ago, ich777 said:
This is a hardware combination bug and has strictly nothing to do with the QUADRO brand, this could theoretically also happen with any other PCIe card.
This will hide the message entirely from the log so it will use no space in the log directory.
I'm currently not at home but I will post how to do that when I'm at my place in front of my PC, will take a few hours.
In addition, I would like to ask you about the hardware combination bug, does it mean that my motherboard will produce errors only with this T600, or that all T600 series will produce errors?
-
10 minutes ago, ich777 said:
This is a hardware combination bug and has strictly nothing to do with the QUADRO brand, this could theoretically also happen with any other PCIe card.
This will hide the message entirely from the log so it will use no space in the log directory.
I'm currently not at home but I will post how to do that when I'm at my place in front of my PC, will take a few hours.
Thank you very much, I will always wait for you
Looking forward to your solution -
Just now, ich777 said:
The main issue here is the bleeding edge hardware that you are using.
In your case I blame the manufacturer from the Motherboard because this seems some kind of firmware bug which needs to be fixed in your case by ASUS.
Maybe try to contact ASUS about that issue, hopefully they will release a new BIOS with a fix.
There is also another way around this and you can hide the message from your syslog, but keep in mind this is not a real solution, this is more of a workaround.
thank you for your reply
My graphics card is old, but the platform is very new, but when I use GT1030 there is no problem, the BIOS seems to have no support for Quadro graphics cards
Because this error is generated every second, it will quickly fill up my memory (about 12 hours), causing my Unraid to crash directly
Will the hidden log you mentioned actually record this log and not display it? This does not seem to solve the problem, because my memory will still be full.
In other words, how to set not to record this log that does not seem to affect my normal use?
Looking forward to your reply, thanks
-
-
59 minutes ago, ich777 said:
I really can't tell what's going on there but from my perspective this is some bug in the BIOS.
From what I see you are booting with UEFI, can you try legacy boot (CSM) and see if it's the same?
In the motherboard, if the CMS is enabled, the Resizable BAR will be disabled. Now there is no way to solve my error problem. Can I just wait for a new driver or a new BIOS?
Would like to ask what motherboard and driver your T400 uses?
Looking forward to your reply, thanks
-
1 hour ago, ich777 said:
Please post your Diagnostics if possible since I have to investigate further if this is even related to the transcoding.
This seems to me from the information that I have from your post somewhat related to the BIOS, please update your BIOS to the latest version if not already done, turn on Above 4G Decoding and Resizable BAR.
Hi, my diagnostic log is as follows,
I also uploaded a Jellyfin transcoding log for you
I confirmed that Above 4G Decoding and Resizable BAR is enabled in the BIOS
The driver version I am currently using is
525.53
When transcode is in progress, the error seems to be stopped at Nov 25 17:49:40
Looking forward to your reply
-
Thank you so much for the plugin, I have a question
My graphics card is Nvidia T600
I installed your plugin correctly and can use it to transode in Jellyfin
But my syslog keeps reporting the errorNov 25 16:15:03 LeoreyHome kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184)
Nov 25 16:15:03 LeoreyHome kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477)
Nov 25 16:15:03 LeoreyHome kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529)My Unriad version is 6.11.5
My motherboard model is
ASUSTeK COMPUTER INC. PRIME Z690M-PLUS D4
The version of BIOS is the latest version (2014)My Cpu is 13600K
Errors are happening every second. They have seriously affected my normal use of Unraid. They will fill up the log memory and cause the system to go down.
I've tried the following, but all to no avail:
Replace each version of the graphics card driver, v525.53, v515.86.01, v520.56.06I even observed a strange phenomenon,When the graphics card is in transode , the error message stops briefly
I still have a GT1030, but it cannot be encoded, it is normal under the v525.53 driver and no error is reported.
Your help is requested, many thanks
Raptor Lake 13600K Integrated graphics passthrough
in VM Engine (KVM)
Posted
The compatibility of Raptor Lake is very bad now. I use 13600K, and there are many kernel exception errors in the log, which greatly affects the stable use of the NAS. I plan to wait for Unraid to upgrade the 6.0 version of the linux kernel and upgrade my motherboard BIOS to solve the compatibility problem.