this post was submitted on 10 Nov 2023
2 points (100.0% liked)

Self-Hosted Main

515 readers
1 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
 

I have a media server based on Ubuntu server 22.03LTS with Kernel updated to the latest stable 6.5.7 running on Proxmox 8 as a VM. My machine is a Beelink EQ12 with an intel N100. Im using Jellyfin server 10.8.

My obstacle is that I cannot activate the transcoding on Jellyfin because I cannot see the renderD128 in /dev/dri. I thought It was because my processor is quite new so I needed the latest kernel but.. after installing the latest kernel and rebooting... I still don't see the renderD128.

It's frustrating. I don't know what else to do.

top 3 comments
sorted by: hot top controversial new old
[–] lilolalu@alien.top 1 points 1 year ago

So, open a terminal and check if the device is there on your system?

[–] tenekev@alien.top 1 points 1 year ago

The others gave you a solution but note the following:

Jellyfin in a VM means that once you passthrough the GPU to the VM, you will lose graphical capabilities on the host. That could be a dealbreaker. Segmenting the GPU is inefficient.

I host my Jellyfin in a LXC because I can passthrough the GPU without reserving it to the LXC.

[–] thekrautboy@alien.top 1 points 1 year ago

It's frustrating. I don't know what else to do.

Follow the excellent Jellyfin documentation for hardware-transcoding.

The /dev/dri doesnt magically appear when you run Jellyfin inside a VM. You should also ask /r/Proxmox if you need help to passthrough your device to the VM.