2 hours ago, ich777 said:

No worries, both of your cards are detected:

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation AD107 [GeForce RTX 4060] [10de:2882] (rev a1)
    Subsystem: Gigabyte Technology Co., Ltd Device [1458:4116]
    Kernel driver in use: nvidia
    Kernel modules: nvidia_drm, nvidia
01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:22be] (rev a1)
    Subsystem: Gigabyte Technology Co., Ltd Device [1458:4116]
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA102GL [RTX A4500] [10de:2232] (rev a1)
    Subsystem: NVIDIA Corporation Device [10de:163c]
    Kernel driver in use: nvidia
    Kernel modules: nvidia_drm, nvidia
02:00.1 Audio device [0403]: NVIDIA Corporation GA102 High Definition Audio Controller [10de:1aef] (rev a1)
    Subsystem: NVIDIA Corporation GA102 High Definition Audio Controller [10de:163c]

 

However, you have a lot of ACPI errors in your syslog:

Sep 27 02:45:52 Tower kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477)
Sep 27 02:45:52 Tower kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529)
Sep 27 02:45:52 Tower kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184)

 

Which usually indicates an error/bug in your BIOS which I can do nothing about.

Please make sure that you've enabled Resizable BAR and Above 4G Decoding in your BIOS (it could be also called Extended Address Space or similar in your PCI sub menu in the BIOS).

 

In which slots do you have the cards? Maybe try to swap the cards in their slots.

 

May I ask why do you need two cards for that?

Seems a bit overkill since the A4500 has unlimited transcodes IIRC (you can also check here).

 

Are you sure that you've assigned the right card with the right UUID in the Plex Docker template?

 

As said, I think the message that spawns your syslog is the cause of the issue and that indicates a BUG in the BIOS. Please note that you use consumer hardware which is in most cases not designed for multiple GPUs anymore (with the fall from SLI) and so on.

Seems to work on plex and tdarr i feel dumb lol. returning the 4060 LP And gunna sell my A4500 just bought a A5000  Should be good enough for all my dockers instead of mutiple GPU's 😹

Finally giving in and asking for help. Been struggling to get this working for a while. I am looking to use my Nvidia GeForce 1070 FE to HW transcode 4k HEVC 10 Bit files. Was going to use the skylake igpu, but it doesn't look like it supports it. Will instead use the skylake igpu for VMs once I get it working using the Intel GVT-g plug-in. Want to get this working first then will post in that forum topic for help on that if needed.

 

System specs:
Motherboard: Gigabyte ga-z170x-gaming7 updated to the latest bios.
CPU: Intel 6700k skylake
Memory: 64 GB DDR4
GPU: Nvidia GeForce 1070 FE

This Nvidia GPU was used in a bare metal machine and also can be passed through to a VM using its vbios rom. In the VM I was able to install jellyfin and watch 4k HEVC 10 Bit files using my Firefox browser. It is installed in the PCIEx16 slot. PCIe ACS override is disabled. So far, I have the Nvidia-Driver installed and this is what shows up on the settings page and with 'watch nvidia-smi'.

 

Here is my container dialog.

When I try to play a 4k HEVC 10 Bit file, this is the error that shows up. Other video files as well as flac music files don't work either. I get the same playback error.

Here is the jellyfin dashboard. It looks like it says it's trancoding, but the above playback error shows up after several seconds.

Here is my diagnostics after getting the playback error.

bluedragon-diagnostics-20230928-1139.zip

 

Any help on this would be greatly appreciated!

 

Edited September 28, 20233 yr by Kinspappy
Deleted a duplicate image.

1 hour ago, Kinspappy said:

Finally giving in and asking for help. Been struggling to get this working for a while. I am looking to use my Nvidia GeForce 1070 FE to HW transcode 4k HEVC 10 Bit files.

What container are you using?

 

BTW, you've deleted the wrong duplicate image, I can't open your docker run image.

 

1 hour ago, Kinspappy said:

Want to get this working first then will post in that forum topic for help on that if needed.

This seems more like a configuration error in Jellyfin itself than an issue with the Nvidia Driver plugin since everything is working from what I can see from your Diagnostics.

 

Please try the official container first from Jellyfin and see if this is working.

Here is my diagnostics. bluedragon-diagnostics-20230928-1139.zip

 

Here is my docker run.

 

I have the linuxserver version installed. Don't know how to install the official jellyfin version as I don't see it in Community Applications. Thank you for the help!

3 minutes ago, Kinspappy said:

Don't know how to install the official jellyfin version as I don't see it in Community Applications.

You can change the repository to jellyfin/jellyfin but be aware that you then have to set up Jellyfin from scratch.

 

I would recommend that you create a post in the Support thread from the container since this seems not like a Nvidia Driver issue at all.

 

As said above, everything seems to work fine and over here with my Nvidia T400 transcoding is working in the official container.

Good to know that I have the Nvidia-Driver set up correctly. I thought I did. I will uninstall the jellyfin app and reinstall it with the official repository. Wiil also post in one of the container thread as needed and report back if I get it working. Thanks again for your help!

Hi

I have an issue were my GPU is not found. Im not certain if this is caused by an update of the plugin and (or) driver version. This used to work in an earlier driver version. Or could this be caused by a faulty card?

 

 

Thanks alot for any help.

/P

peelow-diagnostics-20231010-2219.zip

28 minutes ago, PeeLoW said:

Or could this be caused by a faulty card?

Did you change anything to your system (BIOS changes/updates, swap the PCIe slot,…)?

Your GPU fails to initialize.

8 hours ago, ich777 said:

Did you change anything to your system (BIOS changes/updates, swap the PCIe slot,…)?

Your GPU fails to initialize.

I did swap the slot (and back again). So there is a slight chans i fucked up...

18 minutes ago, PeeLoW said:

I did swap the slot (and back again). So there is a slight chans i fucked up...

This seems to me that the card don't work in all slots:

Oct 10 21:53:02 PeeLoW kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x24:0xffff:1211)
Oct 10 21:53:02 PeeLoW kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
Oct 10 21:53:03 PeeLoW kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000a0000-0x000dffff window]
Oct 10 21:53:03 PeeLoW kernel: caller _nv000720rm+0x1ad/0x200 [nvidia] mapping multiple BARs
Oct 10 21:53:03 PeeLoW kernel: NVRM: GPU at PCI:0000:01:00: GPU-8e555b0d-adbf-c913-e46f-820a8f9ad65e
Oct 10 21:53:03 PeeLoW kernel: NVRM: Xid (PCI:0000:01:00): 62, pid=14325, 0a7b(14c8) 00000000 00000000
Oct 10 21:53:15 PeeLoW kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x25:0x65:1241)
Oct 10 21:53:15 PeeLoW kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
Oct 10 21:53:15 PeeLoW kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000a0000-0x000dffff window]
Oct 10 21:53:15 PeeLoW kernel: caller _nv000720rm+0x1ad/0x200 [nvidia] mapping multiple BARs
Oct 10 21:53:23 PeeLoW kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x25:0x65:1241)
Oct 10 21:53:23 PeeLoW kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
Oct 10 21:53:23 PeeLoW kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000a0000-0x000dffff window]
Oct 10 21:53:23 PeeLoW kernel: caller _nv000720rm+0x1ad/0x200 [nvidia] mapping multiple BARs
Oct 10 21:53:23 PeeLoW kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x24:0xffff:1211)
Oct 10 21:53:23 PeeLoW kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

 

These are the eroors, seems like a BIOS issue.

Please also make sure that you have Above 4G Decoding enabled in your BIOS.

29 minutes ago, ich777 said:

This seems to me that the card don't work in all slots:

Oct 10 21:53:02 PeeLoW kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x24:0xffff:1211)
Oct 10 21:53:02 PeeLoW kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
Oct 10 21:53:03 PeeLoW kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000a0000-0x000dffff window]
Oct 10 21:53:03 PeeLoW kernel: caller _nv000720rm+0x1ad/0x200 [nvidia] mapping multiple BARs
Oct 10 21:53:03 PeeLoW kernel: NVRM: GPU at PCI:0000:01:00: GPU-8e555b0d-adbf-c913-e46f-820a8f9ad65e
Oct 10 21:53:03 PeeLoW kernel: NVRM: Xid (PCI:0000:01:00): 62, pid=14325, 0a7b(14c8) 00000000 00000000
Oct 10 21:53:15 PeeLoW kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x25:0x65:1241)
Oct 10 21:53:15 PeeLoW kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
Oct 10 21:53:15 PeeLoW kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000a0000-0x000dffff window]
Oct 10 21:53:15 PeeLoW kernel: caller _nv000720rm+0x1ad/0x200 [nvidia] mapping multiple BARs
Oct 10 21:53:23 PeeLoW kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x25:0x65:1241)
Oct 10 21:53:23 PeeLoW kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
Oct 10 21:53:23 PeeLoW kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000a0000-0x000dffff window]
Oct 10 21:53:23 PeeLoW kernel: caller _nv000720rm+0x1ad/0x200 [nvidia] mapping multiple BARs
Oct 10 21:53:23 PeeLoW kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x24:0xffff:1211)
Oct 10 21:53:23 PeeLoW kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

 

These are the eroors, seems like a BIOS issue.

Please also make sure that you have Above 4G Decoding enabled in your BIOS.

I have changed back to the old slot which has been working before and the bios is at the same version it worked before.

1 minute ago, PeeLoW said:

I have changed back to the old slot which has been working before and the bios is at the same version it worked before.

So I assume it is not working?

Can you please post update Diagnostics with the card installed in the old slot?

 

Did you add any other cards or make any other changes?

Please make sure that you've enabled Above 4G Decoding and Resizable BAR support in the BIOS.

35 minutes ago, ich777 said:

So I assume it is not working?

Can you please post update Diagnostics with the card installed in the old slot?

 

Did you add any other cards or make any other changes?

Please make sure that you've enabled Above 4G Decoding and Resizable BAR support in the BIOS.

Thanks for the help so far! I can't check the bios right now but will later today. Here is the diagnostics.

peelow-diagnostics-20231011-0856.zip

45 minutes ago, PeeLoW said:

Thanks for the help so far! I can't check the bios right now but will later today. Here is the diagnostics.

Please look at this table: Click

 

The syslog lists Xid error 62 (second line):

Oct 11 08:13:56 PeeLoW kernel: NVRM: GPU at PCI:0000:01:00: GPU-8e555b0d-adbf-c913-e46f-820a8f9ad65e
Oct 11 08:13:56 PeeLoW kernel: NVRM: Xid (PCI:0000:01:00): 62, pid=18862, 0a7b(14c8) 00000000 00000000
Oct 11 08:14:08 PeeLoW kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x25:0x65:1241)
Oct 11 08:14:08 PeeLoW kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

 

Which means:

Internal micro-controller halt, which seems to be caused by a HW Error, Driver Error or Thermal Issue.

 

But keep in mind that this can be also caused by your BIOS and conflicting resources which too me seems more likely to be the case.

24 minutes ago, ich777 said:

Please look at this table: Click

 

The syslog lists Xid error 62 (second line):

Oct 11 08:13:56 PeeLoW kernel: NVRM: GPU at PCI:0000:01:00: GPU-8e555b0d-adbf-c913-e46f-820a8f9ad65e
Oct 11 08:13:56 PeeLoW kernel: NVRM: Xid (PCI:0000:01:00): 62, pid=18862, 0a7b(14c8) 00000000 00000000
Oct 11 08:14:08 PeeLoW kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x25:0x65:1241)
Oct 11 08:14:08 PeeLoW kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

 

Which means:

Internal micro-controller halt, which seems to be caused by a HW Error, Driver Error or Thermal Issue.

 

But keep in mind that this can be also caused by your BIOS and conflicting resources which too me seems more likely to be the case.

Thanks for the insights i will look in to this! Really appriciate your help!

Hi all,

 

this might be a stupid question since I am new to Unraid. My setup is HPE Microserver Gen10+ v2 Xeon processor and Nvidia GPU T400 via PCIe.

 

I run Home Assistant as a VM and Plex as Docker.

In Home Assistant I have Frigate as Plugin, which needs the GPU for decoding/encoding video stream of my cameras.

Plex needs the GPU for that as well.

 

Do I need the driver now or since the card should work on VM and Docker, not recommended?

 

Thank you and warm regards

Sebastian

5 hours ago, tischer.s said:

Do I need the driver now or since the card should work on VM and Docker, not recommended?

 

you would need the driver to run it in docker/s, for VM's you only passthrough the card ... (see page 1, post 1)

 

but you CANT run this simultan .... either the card is passed to a VM (while running in a ONE VM the card is vfio bound and not useable for the host, dockers, other VM's ...) OR you run it on the host for host usage, docker/s, ... also, page 1 ...

 

so you have to decide if you want to use it in your HA VM ... OR .... for docker/s like Plex.

 

may as note, you can use the card for multiply Dockers simultan ... that would work, sample Plex, Emby, Jelly, ... could simultan make use of your ONE GPU ... but VM's ... ONLY 1 VM simultan ... no 2nd VM, no docker/s, no ... at least while its running.

 

in the end, either look if HA Docker could make use of frigate with NVENC (i assume not) or get a 2nd card for your usecase ...

 

or may read into Coral TPU ... may that would help too in your usecase with Frigate ...

https://docs.frigate.video/frigate/hardware/

6 hours ago, alturismo said:

you would need the driver to run it in docker/s, for VM's you only passthrough the card ... (see page 1, post 1)

 

Thanks a lot for the extensive reply and your explanation  I will do it like you said...

 

- VM with HASS and Frigate Proxy Addon

- Docker for Frigate (with Coral & GPU usage), Plex etc.

 

I will need another Windows VM but since the HP Microserver doesn't support Bifurcation of the INTEL processor gpu this need to run just on the processor. I only need that for KNX ETS, so that should be no problem I hope

2 hours ago, tischer.s said:

 

- VM with HASS and Frigate Proxy Addon

Why not use HomeAssistant in a Docker container or in a LXC container? This would solve your problems because you then can use the GPU for both containers or even more containers.

 

A VM is most certainly for HomeAssistant a waste of resources.

On 10/14/2023 at 2:41 PM, ich777 said:

Why not use HomeAssistant in a Docker container or in a LXC container? This would solve your problems because you then can use the GPU for both containers or even more containers.

 

A VM is most certainly for HomeAssistant a waste of resources.

 

The problem with HASS as docker is, that it doesn't support AddOns which are partly necessary

 

I will check it when I have all my hardware available  

6 minutes ago, tischer.s said:

The problem with HASS as docker is, that it doesn't support AddOns which are partly necessary

Which addons?

I'm assuming addons are working on Hass Core correct? If yes, you can install everything in a LXC container.

15 minutes ago, ich777 said:

Which addons?

I'm assuming addons are working on Hass Core correct? If yes, you can install everything in a LXC container.

Right now it is:

VSCodeServer (tightly integrated)

SkyConnect Zigbee

Cloudflared

MQTT (this can be easily excluded :D)

HASS Google Drive Backup

24 minutes ago, tischer.s said:

VSCodeServer (tightly integrated)

Why not on Unraid?

 

25 minutes ago, tischer.s said:

SkyConnect Zigbee

Why not pass that over to a Docker?

 

25 minutes ago, tischer.s said:

Cloudflared

Why not on Unraid?

 

25 minutes ago, tischer.s said:

MQTT (this can be easily excluded :D)

Can be also done on Unraid (but let's exclude it here )?

 

26 minutes ago, tischer.s said:

HASS Google Drive Backup

Why not with Unraid (rclone)?

 

 

I don't understand why someone is doing it like that, Unraid has apps for all of your things and you are basically wasting a lot of resources with a VM...

 

 

 

Anyways, this should not be part of this support thread.

7 hours ago, ich777 said:

I don't understand why someone is doing it like that, Unraid has apps for all of your things and you are basically wasting a lot of resources with a VM...

 

I am really thankful for your help and opinion - I am totally new to Unraid to be honest, so you are totally right I will definitely test the docker version, no doubt.

The only thing I am not sure about, is the GoogleDrive Backup addon, since it is not "just" a file copy but a specific HomeAssistant restorable backup. But I can find a solution for that

1 hour ago, tischer.s said:

I am totally new to Unraid to be honest, so you are totally right I will definitely test the docker version, no doubt.

If you are using the HA VM and use their addons these are basically are also all Dockers, I even think that the MQTT one is completely the same as in the CA App.

 

1 hour ago, tischer.s said:

The only thing I am not sure about, is the GoogleDrive Backup addon, since it is not "just" a file copy but a specific HomeAssistant restorable backup.

I think you can also install that through HACS which is also compatible with the Docker version from HA, however it is usually a simple file copy thing to driver, maybe it is zipped or something like that but the principle is basically the same.