• 11 Posts
  • 54 Comments
Joined 8 months ago
cake
Cake day: July 8th, 2024

help-circle
  • My bad sorry should have thought about making an official matrix account and testing there. Based off of what I can tell my ntfy container is working because it works flawlessly with an official matrix account.

    That leaves me with two ideas so far, there is something wrong with matrix dendrite container, or my vps coturn server (which I forgot to mention). It looks like traffic is coming through just fine on my co turn server though. I am curious if this is a firewall issue with my co turn server. That would make the most sense given that element call is also not working on element x.

    It’s weird though because calling works on seperate networks just fine so I had assumed that my co turn server just worked. Odd.

    Edit: I think it is the turn server even though my calls are going through. I went to my maytrix url with “/_matrix/client/r0/voip/turnServer” to diagnose webrtc and it says “errcode: ‘M_MISSING_TOKEN’” "error: ‘missing access token’ "










  • 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”







  • ludicolo@lemmy.mltoGames@lemmy.worldSteamOS expands beyond Steam Deck
    link
    fedilink
    English
    arrow-up
    15
    ·
    edit-2
    2 months ago

    Bro do some research before you come in making outrageous statements.

    There are absolutely a wide variety of plug-n-play headsets that just work. Take the valve index for example. I have heard that headset works just fine out of the box. Same with any steamvr relient headset if I am not mistaken.

    When you use a headset that depends on third party software that’s when a little more setup is required. However we still have options that won’t be a massive headache.

    Like the cv1 for example, you can use something like openhmd and use your cv1 just fine on steamvr.

    And that’s also not to say that something like a quest 2/3 isn’t hard either. Alvr is easy to install it’s just about tweaking proper settings for your network. Which you may alrwady need to do if you’ve used virtual desktop.

    Then there is wivrn. But you get my point.

    Linux is more than gaming ready. Ever heard of protondb? Maybe give it a look. If an online game doesn’t work that is of fault of the dev/publisher not making the anticheat compatible. Valve has consistently worked with anti-cheat devs like battle eye and easy anti-cheat to make it easy on the dev side to make their anti-cheat version support proton. Yet somehow we have large companies like rockstar not putting in that simple effort.

    https://www.engadget.com/arma-3-dayz-proton-battleye-support-224625719.html?guccounter=1

    https://www.theverge.com/2024/9/18/24248585/gta-v-steam-deck-battleye

    Please stop spreading misinformation. It harms the absolute mountainload of work put in by people who have gotten linux to be where it is now. Get mad and point blame at your game devs/publishers for being so uncooperative.



  • So I seem to have gotten it up and running with the guide the only issue is It seems really slow (compared to conduit, conduwuit, dendrite and synapse on sqlite). Also when I pick up calls on element x on graphene os I cannot hear the other user (this is on the same network both devices running graphene I did configure my coturn server but didn’t try out of network calls.). When I was trying to sign up it would error on me. In order to bypass the error I just kept clicking sign up/sign in and it worked on the second or 3rd try. Device verification seems to work but you have to be really slow about working through the steps.

    Any ideas on how to fix this?