ludicolo

joined 9 months ago
[–] [email protected] 1 points 2 months ago* (last edited 2 months ago) (3 children)

I am using cloudflare tunnels as of right now. I would be very appreciative if I could take a look at your settings!

[–] [email protected] 143 points 2 months ago* (last edited 2 months ago) (2 children)

In other news, shit spewing liar spews more shit and lies to get more of your money.

He thinks they're on the wrong side of history my ass. He doesn't care. He never cared. He will never care. The open source you and I know is completely different than the "open source" this chucklefuck is probably selling you on. "We need to figure out a different open source strategy" should be the biggest indicator here. Take everything he and his circlejerk says with the biggest fucking mountain of salt you can dream of and double it.

[–] [email protected] 1 points 2 months ago* (last edited 2 months ago) (1 children)

No its got voice calls with jitsi implementation along with their own built in "element chat" that has been implemented or is still being tested to be implemented.

That and 1 on 1 calls work out of the box with no jitsi or element chat configuration. (Still need coturn)

[–] [email protected] 6 points 2 months ago* (last edited 2 months ago)

THANK YOU ALL!

It was a problem with my docker compose file! I didn't list the needed devices from the jellyfin documentation. I thought the Container was detecting the gpu but it wasn't. Docker exec nvidia-smi is your friend!

Edit: so now it doesnt kick me out saying the playback failed but its just a black screen with 4k media

Edit 2: my bad forgot to enable some transcoding settings in jellyfin lol

[–] [email protected] 1 points 2 months ago* (last edited 2 months ago)

This is what thay compose looks like now:

 services:
  jellyfin:
    image: jellyfin/jellyfin
    user: 1000:1000
    network_mode: 'host'
    volumes:
      - /DATA/AppData/jellyfin/config:/config
      - /DATA/AppData/jellyfin/cache:/cache
      - /DATA/AppData/jellyfin/media:/media
      - /mnt/drive1/media:/mnt/drive1/media
      - /mnt/drive2/Jellyfin:/mnt/drive2/Jellyfin
      - /mnt/drive3:/mnt/drive3
      - /mnt/drive4/media:/mnt/drive4/media
      - /mnt/drive5/jellyfin:/mnt/drive5/jellyfin
      - /mnt/drive6/jellyfin:/mnt/drive6/jellyfin
    runtime: nvidia
    deploy:
      resources:
        reservations:
          devices:
            - driver: cdi
              device_ids:
               - nvidia.com/gpu=all
            - /dev/nvidia-caps:/dev/nvidia-caps
            - /dev/nvidia0:/dev/nvidia0
            - /dev/nvidiactl:/dev/nvidiactl
            - /dev/nvidia-modeset:/dev/nvidia-modeset
            - /dev/nvidia-uvm:/dev/nvidia-uvm
            - /dev/nvidia-uvm-tools:/dev/nvidia-uvm-tools
              count: all
              capabilities: [gpu]

Edit: when I try and compose up it says "yaml: lin 30 mapping values are not allowed in this context" when I remove line 30 and 31 the output is "validating /DATA/AppData/jellyfin/docker-compose.yml: services.jellyfin.deploy.resources.reservations.devices.1 must be a mapping"

[–] [email protected] 2 points 2 months ago* (last edited 2 months ago)

Output of nvidia-smi on the host:

Output of nvdia-smi on the container:

OCI runtime exec failed: unable to start container process: exec: "nvidia-smi": executable file not found im $PATH: unknown

EDIT:

I tried it again with the jellyfin docker compose command and this is what I get:

Failed to initialize NVML: Unknown Error

Edit 2: I fixed it I am now getting the same output for both!

[–] [email protected] 1 points 2 months ago* (last edited 2 months ago) (1 children)

I tried this and it says:

OCI runtime exec failed: unable to start container process: exec: "nvidia-smi": executable file not found im $PATH: unknown

[–] [email protected] 1 points 2 months ago

I ran it as two commands instead of one before and still got that error message.

However, I tried again with a different jellyfin image and the command seems to have ran fine.

[–] [email protected] 1 points 2 months ago

Here is a pic of my nvidia-smi output:

[–] [email protected] 1 points 2 months ago (7 children)

I followed this guide and seemed to get it working.

https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html

However jellyfin transcoding sttill doesn't work. I have tried adding the "nvidia devices= all" environment variable, it still didn't work.

I tried using the docker conpose from here

https://jellyfin.org/docs/general/administration/hardware-acceleration/nvidia/#configure-with-linux-virtualization

But when I try and run this command: "docker exec -it jellyfin ldconfig sudo systemctl restart docker"

It says the container is restarting and to try again when the container has started.

[–] [email protected] 2 points 2 months ago* (last edited 2 months ago) (1 children)

Casaos is just a server ui for ubuntu to manage docker and other settings:

https://casaos.io/

Here is the output of nvidia-smi (sorry for the picture if my monitor. It's late and I blanking on my lemmy pass and cannot sign in on the pc itself to send a screen cap lol):

I used several different jellyfin images posted in casaos appstore along with the official nvidia documentation. It still does not want to work:

services:
 jellyfin:
   image: jellyfin/jellyfin
   user: 1000:1000
   network_mode: 'host'
   volumes:
     - /DATA/AppData/jellyfin/config:/config
     - /DATA/AppData/jellyfin/cache:/cache
     - /DATA/AppData/jellyfin/media:/media
     - /mnt/drive1/media:/mnt/drive1/media
     - /mnt/drive2/Jellyfin:/mnt/drive2/Jellyfin
     - /mnt/drive3:/mnt/drive3
     - /mnt/drive4/media:/mnt/drive4/media
     - /mnt/drive5/jellyfin:/mnt/drive5/jellyfin
     - /mnt/drive6/jellyfin:/mnt/drive6/jellyfin
   runtime: nvidia
   deploy:
     resources:
       reservations:
         devices:
           - driver: nvidia
           - /dev/nvidia-caps:/dev/nvidia-caps
           - /dev/nvidia0:/dev/nvidia0
           - /dev/nvidiactl:/dev/nvidiactl
           - /dev/nvidia-modeset:/dev/nvidia-modeset
           - /dev/nvidia-uvm:/dev/nvidia-uvm
           - /dev/nvidia-uvm-tools:/dev/nvidia-uvm-tools
             count: all
             capabilities: [gpu] ```
[–] [email protected] 4 points 2 months ago* (last edited 2 months ago) (1 children)

Yes it is a container on ubuntu, it seems to be the official container on the casa os store. It is labled "jellyfin (nvidia gpu)". The gpu seems to be working fine on the host. Ubuntu 20.04

Yeah i have tried tollowing that guide already.

 

Hello friends! I am back with another issue.

Recently I have taken on the task to get non steam games working on Proton. I have noticed that the performance is significantly worse with them on Linux then on Windows. More frequent stutterings and such. 100 fps consistently on Windows vs linux which it dips below 50 fps. Other "better performing" non-steam games get consistent micro stutters. I am using native steam because the flathub version because after installing dependencies with protontricks the game still would not launch.

The only possible thing I can think of is the games are on NTFS partition (yet steam regular games installed on it run just dandy). I dualboot with windows and access this particular drive between both os'. I am at a complete loss, any help would be appreciated oh Linux brotheren and sisteren.

Thank you!

(also the games drop audio consistently as well sometimes it wont come back unless I alt tab and come back to the game.)

EDIT: Hello everyone! thank you again for the help I think I have come to the conclusion that some of you suggested already. Wayland seems to be having the game perform significantly better than x11 but it still isnt quite up to par as windows. When I had tried it before I thought to myself "yeah this is better but it isn't up to par with my windows partition" so I kept searching for an answer. the conclusion I have come to is, I think this just comes down to the particular game being unoptimized. Thank you all for your suggestions! You all are truly moving mountains when helping people swap to this wonderful operating system. Hopefully one day I can get rid of my windows partition fully. (too bad I am a VR dweeb that needs windows for some applications to function 😭).

 

so I recently dualbooted arch and windows. I have noticed the longer I play game the more the fps drops.

Deadlock for example, I will be getting 110-120 fps then as the match goes on (usually at the 20-40 min mark) it gradually drops to 50fps (I don't know if it will keep going, that is just the lowest I have been able to see it drop)

the outlast trials also gets pretty bad micro stutters.

I have tried reinstalling drivers removing two sticks of ram that seem to be faulty, and reinstalling arch completely with archinstall just to see if I flubbed something up around manual install, I tried the nvidia-open drivers (the ones released by nvidia) and the proprietary drivers. Nothing seems to be working.

When I launch into windows games stay at pretty consistant framerates.

specs:

rtx 3070 ryzen 7 3700x 16gb ram 1tb ssd 2tb ssd 1440p 144hz monitor

Any help is very much appreciated!!

(off topic question but I figured I would ask here as to not create another post. I cannot for the life of me get wayland kde to work properly. It efuses to let me change the resolution and refresh rate. the solution I seem to be finding is that wayland doesnt play nice with nvidia. So I have just been using x11. is this assesment incorrect?)

 

I have been trying to set this up for the past 2 days and I am losing my mind.

The issue I seem to be having is that synapse cannot find the necessary postgres information in the the database. I have been trying to setup a docker container for it but to no avail. The container just continues to restart. When I check docker logs it seems like it cannot find the database info it needs but its there. I deleted the sqlite3 info so it most certainly isn't still using that.

Is there possibly a casaos friendly version of matrix? Is there an easy to follow tutorial for docker matrix and duckdns? Any help would be appreciated.

view more: ‹ prev next ›